Limitations

The following limitations are known to exist in the current release:

• The monitor server for Virtual Standby to Nutanix needs to be a virtual machine on same Nutanix hypervisor. The virtual machine should have Windows 2016 or higher version.
• The inconsistency in the snapshot provided by Nutanix causes the failure of Catalog job. You can experience similar issue with Recovery Point Check or Assured Recovery Jobs
• If CD-ROM in AHV VM includes a CD, the VM recovery job creates the CD-ROM but does not attach any disks/ISO that is attached to the source VM.
• In Nutanix AHV the ISO of operating system is attached to a CD-ROM for installing OS in the VM. For OS installation you must select the boot device as per Nutanix priority. After the OS installation, change the boot device to disk in which the OS is installed. Otherwise, the VM configuration saved during the backup includes CD-ROM as the boot device and the recovered VM fails to boot pointing to an empty CD-ROM. In such case you have to explicitly select the boot disk for the recovered VM.
• If the VM is configured with affinity, only the alternate location affinity of the VM is set in recovered VM. The original location affinity is not set.
• When imported, a Nutanix agentless node name displays only IP address. If VM is powered off, name of nodes is displayed as VM (name_of_VM).
• To fetch the OS details, need to install NGT. Even after starting installed NGT and service, fetching OS details may require extra time.
• Nutanix CVM cannot be protected using Host-based backup for the Nutanix AHV solution.
• When the UUID for a VM is already created, it cannot be changed and you can only create a clone of the VM on the cluster.

Examples of this limitation:

• Two virtual machines, VM1 and VM2, with same UUID (called as Instance UUID for Nutanix) in the Nutanix Cluster are managed by different Nutanix Clusters NC1 and NC2. When you import VM1 in to the console, it displays in the node list view of the console. Subsequently, when you import VM2 into the console, the node list displays VM2 as VM1 is overwritten.
• Two virtual machines, VM1 and VM2, with same UUID (called as Instance UUID for Nutanix) in the Nutanix Cluster are managed by different Nutanix Clusters NC1 and NC2. When you import VM1 in to the console, you also import at least one VM from the Nutanix NC2 so that both NC1 and NC2 are added into the Node Directory list. While node discovery runs, it initially connects to NC1 and detects VM1 by the UUID and the Hypervisor column is updated with information of NC1. Subsequently, when it connects to NC2, it detects VM2 by the same UUID and the NC1 information in the Hypervisor column is overwritten and updated with information of NC2.