An upload policy determines which files and directories to upload from the user endpoint to the CVD in the data center. You must define upload policies before you activate endpoints because the activation process selects an existing upload policy for the endpoint.

A CVD is assigned only one upload policy at a time.

You can create upload policies by defining whether files are unprotected or local to the endpoint, or protected. Protected files are uploaded to the Mirage server in the data center.

To simplify the task, you identify only files and directory names or patterns that are not uploaded to the CVD. The remaining files are considered part of the CVD and are protected.

The list of files that are not protected is defined by a set of rules and exceptions.

You define two upload policy areas that the system uses according to the relevant system flow.

Table 1. Upload Policy Areas

Upload Policy Area


Unprotected area

Lists files and directories on the endpoint device that are not protected, but with a subset of exceptions defined as protected. By default, Mirage protects all other files and directories.

User area

Lists end-user files and directories, such as document files, that are excluded from the restoration and that are kept on the endpoint devices in their current state when the Restore System Only option is used to revert a CVD. See Restore a Device to a CVD Snapshot

Additionally, the user area is used to filter out information from the base and app layers.

The user area cannot be downloaded or viewed by the end user.

The upload policy that is applied to the CVD consists of various items.

  • A selected built-in factory policy that VMware provides to assist the administrator with first time deployment

  • Administrator modifications to that policy to address specific backup and data protection needs

The built-in factory policy is a reference for further customization and includes all the mandatory rules that the system needs to function. The administrator cannot modify the mandatory rules.

Before you use a built-in policy, evaluate it to be sure it meets backup policy and data protection needs. The built-in policies, for example, do not upload .MP3 and .AVI files to the CVD.

You can use one of the following customizable built-in upload policies, to help manage mixed Mirage and View systems:

Mirage default upload policy

Use on Mirage servers that manage CVDs on distributed physical devices.

View optimized upload policy

Use on Mirage servers that manage CVDs on virtual machines. This upload policy is provided for convenience. It is identical to the Mirage default upload policy, except that the Optimize for Horizon View check box is selected.