Best Practices for Implementing Virtual Machine Protection

Backup sets provide an organizational and management point for each class of VM. Use a separate backup set for each protection method. For example, use one backup set for Tier 1 VMs with IntelliSnap plus Backup Copy, and another for Tier 3 VMs with traditional VADP protection.

Use a small number of subclients per backup set, each including similar classes of virtual machines across datastores, with separate subclients for large, critical, and high transaction VMs. This approach provides greater scalability and simplifies management; it also requires less intervention as the environment grows and changes (for example, removing or adding datastores or moving a VM to a different datastore).

Organize high transaction VMs in separate datastores. This approach is recommended for application performance; it also enables the use of hardware snapshots for data protection without processing too many snapshots for each datastore. Do not include VMs that are backed up using traditional VADP on the same datastore as VMs that are backed up using IntelliSnap plus Backup Copy.

Use naming patterns and filters to automatically include or exclude datastores, hosts, and virtual machines in a subclient.

All virtual machines in a single datastore should be protected as part of the same storage policy to minimize the number of snapshots.

Last modified: 7/5/2018 9:13:58 PM