Known Issues for VMware VM-Centric Operations
VM-centric operations are available for streaming backups performed for the Virtual Server Agent with VMware.
The following operations are not supported with Indexing Version 2 for the Virtual Server Agent:
- File and folder information is not collected during backups.
- File indexing for virtual machines is not supported.
- 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.
Note: As a workaround, use the disk library for one of the copies (primary or secondary) and perform a live browse from it.
- Specifying encryption settings using VM-level settings.
You can specify encryption settings through the storage policy.
- End users can use Command Center to perform VM-centric operations. Web Console does not support VM-centric operations.
- For a VM instance client, the Browse and Restore Options dialog box shows options for Virtual Machine files and Attach Disks to Existing VM, but those types of restores can be performed only from a backup set under the virtualization client.
- If a virtual machine is deleted from the vCenter, the VM client remains in the CommCell Console. To avoid errors for the deleted VM, delete the VM client manually and remove the corresponding VM from all subclients where it is included as content.
Note: 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.
- If you restore files from a virtual machine that has a File System Agent installed, the Virtual Server Agent backup might not have the most recent backup data. To ensure that you are restoring from the most recent backup, initiate the restore from the job history for the virtual machine.
- You cannot use the virtual machine archiving feature for virtualization clients that use Indexing Version 2.
- Job-based browse from a VSA subclient will fail if the most recent job is a synthetic full backup job for the VM.
- Secondary copy operations from a snapshot replica are not supported with Indexing Version 2.
- 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.
- 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 8:14:07 PM