Tips for data protection tagging
Backup policies are determined by the data protection tag assignments on vSphere inventory objects. The performance for processing data protection tags can also be affected by the number of tags that are applied to the vSphere inventory and where the tags are applied.
Consider taking the following actions when you define the backup policy for objects in the
vSphere inventory:
- Take advantage of the order of precedence for tagging inventory objects. Create a
general policy configuration for an organization by setting backup policies (or tags) on the highest
container in the vSphere inventory hierarchy. The policies are inherited by child containers and
their virtual machines. In general, you do not need to set policies on individual virtual machines.
Then, create exceptions by changing the policy on a child container or individual virtual machines to override the inherited policy setting.
Alternatively, if you do not want to configure an overall backup policy, do not assign data protection tags to any high-level objects. Assign the data protection tags to lower-level objects.
- For ease of maintenance, performance, and usability, avoid assigning tags to too many inventory objects.
- For ease of maintenance and reduced complexity, avoid assigning tags to different object types. For example, assign tags to clusters, hosts, host folders and VMs only, or to VM folders and VMs only, but not both at the same time.
- With tagging support, you can assign multiple schedules to multiple data movers. However, do not overlap the schedules for a data mover. Otherwise, some schedules will be skipped.
- For ease of use, administrators can use IBM Spectrum Protect™ Operations Center Version 8.1 to create schedules that are compatible with tagging.