You can create backup jobs that include which virtual machines to backup, where to store the backups, and for how long.

Data Recovery uses the backup window to create new backups and the retention policy to remove specific older ones. For more information on how the deduplication store processes of integrity checks and reclaim operations support this functionality, see Deduplication Store Benefits.

You can specify collections of virtual machines, such as all virtual machines in a datacenter, or select individual virtual machines. If an entire resource pool, host, datacenter, or folder is selected, any new virtual machines in that container are included in subsequent backups. If a virtual machine is selected, any disk added to the virtual machine is included in the backup. If a virtual machine is moved from the selected container to another container that is not selected, it is no longer part of the backup.


Using Data Recovery to back up the Data Recovery backup appliance is not supported.

You can store backups in VMDKs, on RDMs, or on network shares. If you are storing backups on a network share and the network share on which you want to store the backup is not available, you can add a network share. For more information, see Add a Network Share. You must format VMDKs and RDMs to store backups. You can format destinations that are not yet formatted or partitioned. For more information, see Formatting a Volume.

By default, backup jobs run at night on Monday through Friday and at any time on Saturday and Sunday. Data Recovery attempts to back up each virtual machine in a job once a day during its backup window. If the backup timeframe for the backup window passes while the backup is in progress, the backup is stopped. The backup restarts when the backup window opens. This means that if there are too many virtual machines for Data Recovery to back them all up during the first specified window, some virtual machines may not be backed up. Eventually Data Recovery will complete backup of all virtual machines and subsequent backups typically fit within one backup window. If some machines are not backed up during a window, those machines are given higher priority during subsequent backup windows. This helps ensure that all virtual machines are backed up as often as the backup windows and resources allow, and prevents the case where some virtual machines are always backed up and some are never backed up.

Data Recovery backups are preserved for a variable period of time. You can choose to keep more or fewer backups for a longer or shorter period of time. Keeping more backups consumes more disk space, but also provides more points in time to which you can restore virtual machines. As backups age, some are automatically deleted to make room for new backups. You can use a predefined retention policy or create a custom policy. For more information on how different backup periods are assessed, see Criteria for Determining Different Types of Backups.

If the deduplication store is less than 80% full, the retention policy is run once each week. If the deduplication store is more than 80% full, the retention policy is run once each day. If the deduplication store is full, the retention policy is run immediately if the policy has not been run within the last 12 hours.

Review the settings for the backup job. This page includes information including:

Which virtual machines will be backed up by this job.

Where the backups for the specified virtual machines will be stored.

The schedule on which virtual machines will be backed up.

The number of backups that will be kept for the segments of time. For example, the number of backups that will be kept for each month.