NetBackup 10.5 Fails After Nutanix AOS 7.5 Upgrade

If NetBackup 10.5.0.1 stops protecting Nutanix AHV virtual machines immediately after an AOS 7.5 upgrade, check compatibility before changing credentials, ports, or storage. The current NetBackup Software Compatibility List shows Nutanix AOS 7.5 with a minimum NetBackup level of 11.1.

That lines up with a recent test-cluster case. A team upgraded Nutanix to AOS 7.5.1.2 and NetBackup 10.5.0.1 stopped backing up the small set of AHV VMs, while AOS 7.3 had been the supported path they were using before.

Does NetBackup 10.5 support AOS 7.5?

The current compatibility list should be the deciding source, and it shows AOS 7.5 requiring NetBackup 11.1. That means a 10.5.0.1 environment should not be treated as a supported combination simply because the cluster is discoverable or some API calls still work.

This is the most important troubleshooting result because it changes the question. If the version combination is unsupported, spending days tuning NFS, iSCSI, credentials, or resource limits may produce temporary behavior without creating a supportable production design.

The administrator in the source case already suspected this. They noted that NetBackup 11.1 was shown as compatible, but upgrading NetBackup would require newer media-server hardware and management was reluctant to spend the money.

That is an infrastructure lifecycle problem, not a hidden checkbox.

Why can an AOS upgrade break backup even when the VMs still run?

Backup products integrate with the hypervisor and storage APIs, not only with the guest VMs. An AOS upgrade can change API behavior, snapshot behavior, storage access, authentication requirements, or other implementation details that the backup product must explicitly qualify.

The production VMs can continue running because AHV itself supports the new AOS release. NetBackup can still fail because its integration layer was built and tested against earlier versions.

This is common across virtualization ecosystems. A hypervisor or storage release and a backup release form one compatibility stack. Each can be healthy alone while the combination is unsupported.

That is why upgrade planning should include backup software before the cluster maintenance window. The Proxmox backup comparison covers another virtualization platform, but the lesson is the same: a hypervisor upgrade is incomplete until protection and restore workflows are validated against the new version.

What changed at NetBackup 11.1 for Nutanix support?

The compatibility list is the key evidence: AOS 7.5 appears at a minimum NetBackup level of 11.1. NetBackup 11.1 documentation also describes the current AHV access-host architecture and the supported Web UI management workflow.

An AHV access host is a NetBackup client or media server that performs backups on behalf of AHV virtual machines. It must have access to the relevant storage container, and the protected VMs themselves do not need a NetBackup client for the image-level AHV workflow.

That architecture explains why an upgrade can have hardware consequences. If the existing media or access hosts cannot run the NetBackup release required for the new AOS version, compatibility forces an infrastructure decision.

You can delay the AOS upgrade, upgrade NetBackup and supporting hosts, or accept an unsupported configuration. Only the first two are good production choices.

Should you downgrade Nutanix back to AOS 7.3?

A rollback can restore the previous compatibility combination if Nutanix supports the downgrade path and the environment has not crossed a point that makes rollback unsafe. But the Reddit discussion raised a second problem: the older AOS branch was approaching the end of its maintenance window.

That makes rollback a bridge, not a strategy. Staying on an older AOS release can preserve backup compatibility while creating a shrinking patch horizon and future upgrade pressure.

If management needs time to approve NetBackup hardware, a temporary supported AOS version may be the least risky option. Document the date by which the environment must move again.

Do not choose a version only because "backups work." The supported lifecycle of Nutanix, NetBackup, server operating systems, and media-host hardware all need to overlap.

What should be checked after upgrading to NetBackup 11.1?

Once the software stack is supported, validate the AHV access host, cluster credentials, network paths, storage-container access, and resource limits. NetBackup documentation lists required connectivity between the access host and AHV, including the Prism REST API and storage-related ports.

Test discovery first. Then run one small VM backup. After that, restore the VM to an alternate location or isolated test network before declaring the upgrade complete.

Also review concurrency. NetBackup 11.1 exposes AHV resource limits for backup jobs, snapshot jobs, clusters, hosts, and storage containers. Start conservatively after a platform upgrade, then increase parallelism after the cluster and backup infrastructure show stable behavior.

The Proxmox Backup Server guide is useful as a cross-platform reminder that backup throughput and restore verification are separate. A supported version is the starting point, not proof of recovery.

What if management will not buy new media servers?

Translate the compatibility gap into business risk instead of presenting it as a backup-team preference. The current choices are concrete: keep the Nutanix cluster on a version supported by NetBackup 10.5.0.1, fund the NetBackup upgrade and required hosts, or run AOS 7.5 without vendor-qualified backup support.

Attach consequences to each option. Staying on an older AOS branch can affect security and maintenance. Upgrading NetBackup costs hardware and project time. Running unsupported can make failures harder to diagnose and support during an incident.

Then estimate the cost of an unprotected or unrecoverable AHV workload. That puts the media-server purchase in the same decision frame as the data it protects.

Infrastructure lifecycle mismatches are rarely free. The bill appears either before the upgrade as planned hardware, or after the upgrade as operational risk.

What would I do with AOS 7.5 and NetBackup 10.5 today?

I would not spend much time trying to make 10.5.0.1 work around the compatibility list. I would either keep the Nutanix environment on the newest AOS release that is still supported by the installed NetBackup level, or upgrade NetBackup to at least 11.1 and refresh the access or media hosts required to run it.

After the supported stack is in place, I would test discovery, backup, and restore before rolling the AOS change to every production cluster.

The key lesson is simple: backup compatibility belongs in the hypervisor upgrade plan. A cluster upgrade is not successful if the applications stay online but the recovery path quietly disappears.