Examples of VM Archiving for VMware
You can use VM archiving to reclaim space and to control pruning.
Using Power Management and Archiving to Reclaim Space
Virtual machines that consume storage but are rarely used can be archived automatically. You can use resource management rules to power off virtual machines that are underused, then archive powered off virtual machines to reclaim space. You can use Performance graphs in vCenter to get an idea of whether specific virtual machines are likely to be powered off and archived based on the VM Management rules.
The following scenarios show examples of space savings.
In the following vCenter displays, the virtual machine docs_vs_Vm1 is powered on. It has about 426 GB of provisioned space, most of it unused, and the CPU usage is negligible.
The VM Management settings for the subclient that backs up this virtual machine can be used to power off any virtual machines for which the CPU usage is less than 10% for 10 days.
Archiving this virtual machine saves about 426 GB in storage.
The following vCenter screens show an ESX with around 50 virtual machines and 4 datastores. The total capacity is around 4.55 TB and the total used space is about 3.5 TB.
About 16 virtual machines are powered off and can be archived or migrated immediately.
Archiving these virtual machine saves about 1 TB (900GB) of disk space.
Pruning Archived Data to Reclaim Space
Archived data is pruned and secondary storage space is reclaimed based on the subclient retention setting and the storage policy cycle-based retention criteria. Running a synthetic full backup reduces space on secondary storage for deleted virtual machines that meet the expiration criteria. Running data aging reclaims space on the secondary storage by pruning the expired backup jobs. The following sections describe scenarios for space reclamation.
To configure retention settings:
- Configure the subclient:
- Navigate to Client Computers > virtualization_client > VMware > backup_set.
- Right-click the subclient and click Properties.
- In the Subclient Properties dialog box, click the VM Management tab and the Retention subtab.
- Under the For archived VMs deleted by user in vCenter, prune data from MediaAgent heading, set the retention to After 100 days.
- Click OK.
- Configure the storage policy:
- Navigate to Policies > Storage Policies > storage_policy (the storage policy that is used for the subclient).
- Right-click the storage policy copy and click Properties, then click the Retention tab.
- Verify that the Enable Data Aging option is selected.
- Select Retain for under Basic Retention Rule for All Backups and set the period to 15 days and 2 cycles.
- Click OK.
The following process describes how deleted data are dropped from the synthetic full backup, enabling the reclamation of secondary storage space.
- Run a few backup jobs. This archives virtual machines based on the defined archiving rules.
- Delete a few virtual machines in vCenter.
- Run an incremental backup job.
- After the above incremental job is performed, the deleted virtual machines expire after 100 days.
- Run a synthetic full backup. The Storage Policy Default option is selected by default in the Advanced Backup Options dialog box, on the Media tab.
Running a synthetic full backup starts a new backup cycle.
- From the backup job history of the synthetic full job, verify the list of archived virtual machines. Ensure that the deleted virtual machines and their corresponding data are no longer included.
Running a synthetic full backup has freed space on secondary storage by pruning expired virtual machines and their data.
- Run more incremental backup jobs and again perform a synthetic full backup. Running the synthetic full backup again starts the third backup cycle. Since the storage policy retention was set for 2 cycles and 15 days, the first cycle becomes prunable.
- Run a data aging job.
The secondary storage space occupied by the first backup cycle is reclaimed.
To reclaim space on secondary storage by completely removing the archived virtual machines and their files, follow the steps given below.
- Retention has been set to n days in the subclient properties.
- Storage Policy retention has been set to x cycles and y days.
- A few backup cycles have been completed.
Take the following steps:
- In the Subclient Properties dialog box, click the VM Management tab and the Retention subtab, and then change the retention to a minimum of 1 day.
- Change the storage policy retention setting to 1 cycle and 0 days.
- Delete the unwanted virtual machines from vCenter.
- Perform an incremental backup.
- After 1 day, perform a synthetic full backup with the Storage Policy Default option selected (the default) in the Advanced Backup Options dialog box, on the Media tab.
The synthetic full backup image does not retain the deleted virtual machines and prunes their data.
- Running a synthetic full backup initiates a new backup cycle. Since the storage policy retention is set for 1 cycle, all the previous backups have expired.
- Run a data aging job.
All older backups prior to the synthetic full backup are pruned. All deleted virtual machines and their corresponding data are pruned and space on secondary storage is freed. All previous backups are pruned.
Last modified: 3/13/2019 8:21:12 PM