Copy Operations and IntelliSnap Backups for VM-Centric Operations with VMware
When you perform IntelliSnap backup operations and backup copy operations for a virtualization client that uses Indexing Version 2, some options are different from the options that are available with Indexing Version 1.
- If you back up the same VM using both streaming and IntelliSnap backups, configure separate backup sets for streaming and IntelliSnap backups. If the same VM is backed up using different methods under the same backup set, browse and restore results might not be consistent.
- With Indexing Version 2, trigger backup copy operations through a storage policy. The storage policy should use a backup copy schedule or schedule policy to process all of the parent and child jobs for a backup copy operation.
For the storage policy, ensure that VM clients that might need to be restored are not skipped for backup copy operations. You can only restore VMs from a backup copy that was performed for the VM client. If a backup copy operation runs against only the parent subclient, data for VMs are not written to the copy, and you cannot restore the VMs from the copy.
The same considerations apply when performing an auxiliary copy operation to create a secondary copy for a streaming backup.
- To perform a live browse operation from an IntelliSnap backup job, the MediaAgent that is used for the live browse operation must have the VSA package installed.
With Indexing Version 2, the VSA package is not automatically installed on the MediaAgent when that package is required to support a live browse operation.
- Guest file restores from tape are not supported with Indexing Version 2, because file details are not collected in backups and live browse operations are not supported from tape copies.
- 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.
- Deleting a VM from the vCenter affects data retention and backup copy operations for the VM. For more information, see Data Aging and Retention Operations.
IntelliSnap Backup Process with Indexing Version 2
- When you run IntelliSnap backup operations from a subclient under a virtualization client (parent), the operation also creates child jobs for each VM. Both the parent and child jobs are associated with the parent job ID.
By default, the first backup of a VM subclient is a full backup.
By default, the first backup for the parent VSA subclient is an incremental backup. For any VM that is included in the subclient but has not been backed up previously, the resulting child job is a full backup.
- You cannot suspend IntelliSnap backup jobs.
- For a backup operation that includes multiple VMs, the backup job takes a hardware snapshot and uses that hardware snapshot to create the IntelliSnap backup for each VM.
- The mapping between the parent and child jobs makes it possible to pick or skip IntelliSnap backup jobs for individual VMs during backup copy operations.
- Each parent and child job is indexed independently.
- For the parent IntelliSnap backup job, only the index is copied during a backup copy operation. VMs can only be recovered from a backup copy for the VM.
- Child jobs that are excluded from backup copy operations can be aged when they meet data aging criteria, independently of the data aging criteria that are specified for the parent job and the child jobs that are picked for backup copy operations.
- Data aging operations for IntelliSnap backup operations do not delete a hardware snapshot until all parent and child jobs that use the hardware snapshot have aged.
- You can perform snapshot management operations from a VM client, including operations such as listing snapshots, mounting or unmounting snapshots, and deleting a snapshot.
- If you run a backup operation for a VM from the VM client, a browse operation that is performed from the job history returns the data from the most recent backup job.
This issue occurs because the Job Manager runs the backup operation using the ID of the parent subclient, instead of running the operation using the ID of the VM client.
- For streaming backup operations and backup copy operations, job retention settings that are specified on the Media tab of the Advanced Backup Options dialog box do not apply to the associated child VM jobs. The job retention settings apply only to the parent job.
- Job priority settings apply to streaming backup operations and backup copy operations.
You can run an auxiliary copy job to create a secondary copy based on the storage policy copy configuration.
When you configure a storage policy to create a secondary copy, you can specify the content of the secondary copy by selecting the following entities on the Associations tab of the Storage Policy Copy properties dialog box:
- Virtualization client: The secondary copy includes the backup jobs for the virtualization client and for all of the virtual machines included in subclients under the virtualization client.
Selecting the virtualization client is the best practice for secondary copies, unless you need to provide different handling for specific subclients or VMs.
- Subclient: The secondary copy includes the backup jobs for the subclient and for all of the virtual machines included in that subclient.
- VM clients: The secondary copy includes the backup jobs for the virtual machines you select, and the backups jobs for the parent subclients of those VMs.
The following considerations apply for secondary copies:
- Retention and data aging settings for a secondary copy apply to the parent entity (virtualization client or subclient) and all of the VMs under the parent entity.
- Differences in how backup copy operations work also apply to secondary copies from streaming backups.
- Secondary copy operations from a snapshot replica are not supported with Indexing Version 2.
- If you configure a secondary copy on a storage policy and select only the virtualization client or subclient on the Associations tab of the Storage Policy Copy properties dialog box, the virtual machines that are under the virtualization client or subclient are not shown as selected. The secondary copy that is created does include the jobs for the parent (virtualization client or subclient) and the jobs for each VM. This is only a display issue.
- If you configure a secondary copy for a subclient and perform a backup, the secondary copy includes the backup job for the subclient and each of the VMs in the subclient content. If a VM subsequently moves to a different subclient, backup jobs for the VM continue to be associated with the original subclient and secondary copy, and are not available from the new subclient. You can still recover data from any backup job by initiating a restore from the job history for the VM client.
Last modified: 8/20/2019 9:17:14 PM