Data Aging and Retention Operations for VMware VM-Centric Operations
Note the following regarding data aging and retention for Virtual Server Agent (VSA) for VMware:
- Once all child VM jobs for a given parent are aged, the parent job will be aged unless the user manually retains the parent job.
- If virtual machines are backed up using a storage policy with spool copy settings (no retention), you must run data aging after creating a backup copy. If you do not run a data aging job after creating a backup copy, browse and restore operations fail when they try to access the default copy of backup data.
- 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). Ensure that backup copy jobs complete before the VM client is de-configured. 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 Commvault packages are installed on a VM, the VM client is not marked for de-configuration after the VM is deleted from the vCenter. You can deconfigure the VM client from the CommCell Console to release licenses.
If a VM is configured as a VMware virtualization client, you cannot delete the VM or the VM client. You can de-configure the Virtual Server instance under the virtualization client, which also de-configures the associated VMware instance.
Last modified: 11/11/2019 4:27:10 PM