The following issues exist for the current release.
Disks filtered by container not honored
Disks that are filtered by container are not honored. Therefore, all disks are backed up. This limitation applies to filters that are created both from the CommCell Console and from the Command Center.
Each VM must be in a separate consistency group
To perform application-consistent backups, each virtual machine must be in a separate consistency group. If a subclient includes a consistency group that contains multiple VMs, then the backup for those VMs fails.
Quiesced snapshot failures
An attempt to create a snapshot of a quiesced VM might fail for the following reasons:
- The virtual machine cannot be reached.
- The snapshot cannot be completed within the required time. Hardware providers should take snapshots within 10 seconds. Non-Nutanix VSS writers should complete quiescing within 30 seconds.
If the Nutanix VSS snapshot capability is disabled or if quiescing fails, then a crash-consistent snapshot is taken, the snapshot is marked as not application-consistent, and an alert is generated.
Reconciliation not supported
If you manually delete a snapshot, then there is no reconciliation support to mark the corresponding snapshot as invalid. If you must delete snapshots manually, use the CommCell Browser. For more information, see Deleting Snapshots.
VM names that contain special characters
VM names that contain the character ‘\’ might be truncated during the backup, which causes restore operations to fail. Do not use special characters in VM names.
Volume groups are not backed up
Volume groups are not supported in the current release, so they are not backed up.
Backup fails with error "Cannot attach Virtual Machine Disk. VM is not found."
A backup can fail when the wrong GUID or UUID is returned during virtual machine discovery for the Linux proxy VM that is performing the backup.
To resolve this issue, see article RHV0001.
Last modified: 2/1/2019 9:02:50 PM