Replay Manager Version 7.7 Administrator’s Guide

Guidelines for Backup Sets in VMware Datacenters

Modifying components or options, moving or deleting components, and renaming source components requires the creation of a new backup set.

To avoid needing to frequently re-create backup sets to account for component changes, create a separate backup set for VMware components that are likely to be deleted, moved, or renamed.

• Renaming source components breaks the association between source data and backup set. If a source component included in a backup set is renamed, the backup set will fail. For this reason, when source components are renamed in any way (renamed server or datastore, renamed database, renamed VM, and so on), create a new backup set that includes the renamed components.
• Moving components between VMware datacenters causes backups to fail. If a component included in a backup set is moved between VMware datacenters, the backup set is unable to backup data at the original location and the backup job fails. Moving source components within a VMware datacenter will not cause failures.
• The existence of VMs with non—unique names within the same datacenter cause backups to fail. If two or more source components included in a backup set have the same name, the backup set will fail. For this reason, make sure all source components in each datacenter have unique names.