Recover an AHV VM within VPC
The recovery of VMs on VPC comes with certain limitations listed below:
For alternate restores, the restore operation is successful if check box is selected. However, attributes like Project, category, owner information, and VPC-related information are not restored.
If there was a network configured in VM when backup was triggered and user tries alternate restore with this backup image keeping check box not selected, then restore operation fails.
If a VM had Project configured, when the backup was triggered but the project did not exist when the restore was triggered, the restore job fails.
If a VM had Category configured, when the backup was triggered but the category did not exist when the restore was triggered, the restore job fails.
If VMs user is not present in the Nutanix Prism Central server or in Project at the time of restore, then restore operation fail.
Only IP addresses with type ASSIGNED is considered for restore. Learned IP type is ignored and user must manually configure the IP after restore.
If the VM has NIC with span port enabled, then after restore this is ignored. You must manually add and configure span on the NIC with Nutanix CLI.
A VM is restored with Project, Category, Owner details, and other VPC-related attributes, if the original location restore has been performed.
An undefined behavior is observed when trying to backup/restore the VMs of a cluster which have been moved from one Prism Central to another.
A backup host with version 10.2 or later is required to backup/restore project, category and other Virtual Private Cloud (VPC) related attributes. If a backup host with version lesser than 10.2 is used, backup/restore will complete without capturing VPC related attributes if a VM is not present in VPC environment. If a VM is in VPC environment and if restore is triggered through a backup host with version lesser than 10.2, then the restore might fail.