Skip to main content

Nutanix AHV FAQs

Nutanix AHV FAQs

What is the auto-configuration feature for Nutanix AHV?

The Auto-Configuration feature allows you to create rules that automatically discover and assign Nutanix AHV virtual machines (VMs) to backup policies. These rules use "categories" (key-value metadata) assigned to VMs in Nutanix Prism Central to filter and configure them for backup. This automates the setup process and ensures your VMs are protected according to your policies.

What do I need to use the auto-configuration feature for my Nutanix VM?

You will need the following:

  • Prism Central: This feature is supported only for Nutanix environments managed by Prism Central. It is not available for Prism Element setups.

  • Proxy Version 6.3.9 or later: At least one backup proxy in your proxy pool must be updated version 6.3.9, or later, to use this feature.

  • Categories in Nutanix: You must have categories assigned to your VMs in Prism Central to use as a basis for the rules.

How frequently are new VMs discovered?

Discovery for new VMs runs once in every 24 hours.

How many auto-configuration rules can I create?

You can create any number of rules as required. There is no limit to the number of rules that can be created.

I have a Prism Element. Can I use auto-configuration for my VMs?

No. Auto-configuration of VMs is dependent on Categories. Nutanix AHV does not support categories for Prism Elements. You can only use auto-configuration for a Prism Central.

Why is there an error in fetching the list of my VMs?

Make sure that the names of the categories do not contain special characters such as #, &, :, %, and more.

Does Druva support Nutanix AHV backups with TPM enabled?

Yes, backing up Nutanix AHV VMs with vTPM (virtual Trusted Platform Module) enabled is supported. During alternate restore via Prism Central, vTPM is automatically attached to the restored VM. If restoring via Prism Element (PE) only, manual vTPM attachment in Nutanix is required after the restore completes.

I received an End-of-Life (EOL) email notification for Agents and Proxies. Does this apply to my Nutanix AHV Backup Proxies?

Yes. EOL notifications apply to both local server agents (e.g., MS SQL, File Server) and dedicated appliance VMs like the Druva Backup Proxy for Nutanix AHV. While your server agents might be up to date, you should always check the status of your environment's proxies to ensure uninterrupted backup functionality.

How can I check if my Nutanix AHV Backup Proxy requires an upgrade?

You can verify the status of your proxy directly within the Enterprise Workloads Management Console on the Agents and Proxies page, or on the All Backup Proxies page in Nutanix AHV, under the Agent Version column.

My Nutanix AHV Proxy is only one minor version behind the latest release. Do I need to upgrade it immediately?

Not necessarily. If your current version is only one version behind and has no known active issues, it will continue to function normally. However, to maintain optimal security, performance, and compliance with Druva’s support lifecycle, it is highly recommended to plan an upgrade to the latest version at your earliest convenience.

Will my backups fail if I choose not to upgrade an eligible proxy right away?

No, your backups will not immediately fail if the proxy is fully functional and only trailing by a minor version. Upgrades can be deferred if you choose, but staying too far behind may eventually trigger compatibility issues or place the appliance out of the official support window.

Where can I find instructions on how to upgrade the Nutanix AHV backup proxy?

You can find step-by-step guidance here.

Can I restore files or VMs from Nutanix AHV without any registered Prism?

No. Both file-level and full VM restore require at least one active, registered Prism with a connected backup proxy.

My primary Prism is down. Can I register a new one temporarily?

Yes. Register an alternate Prism Element, deploy a backup proxy, and use it to restore from existing recovery points. Existing backup data is not affected.

What is the difference between original location and alternate location VM restore?

Original location overwrites the existing VM in place (same UUID, same node, same settings). Alternate location creates a brand-new VM on a specified cluster/node with a new UUID.

Will registering a new Prism affect my existing backups or recovery points?

No. Recovery points are stored in Druva Cloud storage. Registering a new Prism only provides a path to execute the restore operation.

Can I restore a VM to a different Prism cluster than the one it was originally backed up from?

Yes, use the Alternate Location restore option. The target cluster must have a registered Prism with connected backup proxies.


Did this answer your question?