Data Aging and Retention Operations for VMware VM-Centric Operations
Data aging and retention is controlled by the storage policy that is associated with a subclient.
Individual VMs inherit data aging and retention settings from the subclient. You cannot associate child VMs with different storage policies.
With 11.20 and more recent service packs, you can access backup data for each child VM, even if the VM Admin job for the subclient is not available, but VM Admin jobs are not marked as aged until all associated child VM jobs are marked as aged.
Note the following considerations for data aging and retention for Virtual Server Agent (VSA) for VMware:
- Prior to SP15, deleting VMs from the vCenter also de-configured VM clients in the CommCell Console, causing IntelliSnap backup copy operations to fail. With SP15 and more recent service packs, VM clients are de-configured only after the period specified in the Number of days to keep deleted VMs setting for Media Management/Data Aging (defaults to 30 days). After a VM client is de-configured, the VM client is retained for another 30 days and then deleted.
- To receive notification when virtual machines are decommissioned, you can configure an alert using the Virtual Machine has been decommissioned rule.
- If you remove a VM from all subclients, the VM is automatically deconfigured, and the backup data for the VM is marked for data aging.
If you delete a VM from the vCenter, but the VM is explicitly added to subclient content (rather than being selected by an automatic discovery rule), the VM is not automatically deconfigured. As a result, a backup job for the VM fails, and the parent job for the subclient is marked as completed with errors. Before the VM can be marked as deconfigured, you must remove it from the subclient.
Last modified: 6/4/2020 7:30:02 PM