What Is New in NAKIVO Backup & Replication 11.2.2?

NAKIVO Backup & Replication 11.2.2 is primarily a compatibility and reliability release. Rather than introducing a completely different backup architecture, it focuses on keeping backup, replication and recovery workflows aligned with newer virtualization platforms and operating systems.

That makes the release particularly relevant to administrators upgrading VMware infrastructure to vSphere 9.1 or operating Proxmox VE environments that need support for newer 9.x releases. It is also useful for organizations protecting a mixture of virtual machines, physical servers and NAS-based repositories.

NAKIVO lists the release date as August 13, 2026, with an End of Fix date of August 13, 2027 and End of Support date of August 13, 2029.

NAKIVO 11.2.2 Adds Full VMware vSphere 9.1 Support

One of the most important changes in NAKIVO Backup & Replication 11.2.2 is full support for VMware vSphere 9.1.

This matters because backup software must remain compatible with the virtualization layer it protects. When an organization upgrades vCenter Server and ESXi hosts, backup and recovery operations need to remain supported rather than relying on an uncertain compatibility configuration.

For organizations planning a vSphere 9.1 upgrade, this means NAKIVO 11.2.2 belongs on the compatibility checklist before moving production hosts and vCenter infrastructure to the newer release.

Real-Time Replication for vSphere 9.1

NAKIVO also extended Real-Time Replication support to vSphere 9.1. This is particularly relevant for workloads where traditional scheduled replication intervals are not sufficient for the desired recovery-point objective.

According to NAKIVO’s official announcement, Real-Time Replication can provide continuous replica updates with RPOs as low as one second. The feature is designed for rapid failover scenarios where minimizing the amount of lost transactional data is important.

NAKIVO 11.2.2 and Proxmox VE 9.1 / 9.2

Proxmox VE is increasingly important in virtualization environments looking for an open-source alternative or complement to VMware. NAKIVO’s official v11.2.2 announcement states that the release adds full backup and recovery support for Proxmox VE 9.1 and 9.2.

This is especially useful for organizations operating mixed VMware and Proxmox environments because backup operations can be managed through the same NAKIVO platform instead of maintaining completely separate backup products.

Practical Proxmox Improvements

The Proxmox-related changes are not limited to version compatibility. NAKIVO’s v11.2.2 release notes list fixes for several Proxmox-related scenarios.

• Fixed an issue where network mapping for Proxmox VE replication could fail with some configurations.
• Fixed an issue where a Proxmox VE Transporter could receive an inaccessible IP address under certain configurations.
• Continued support for native change tracking on Proxmox VE, subject to the underlying VM disk format and platform conditions.

These changes are important because backup reliability is often determined by operational edge cases rather than headline features. Network mapping, Transporter connectivity and change-tracking behavior can directly affect the reliability and performance of backup jobs.

Expanded Physical Machine Operating-System Support

NAKIVO 11.2.2 also expands the operating-system versions supported for physical-machine backup.

This is useful for organizations protecting mixed environments where virtual machines are not the only workloads requiring backup and disaster recovery.

NAS Backup and Storage Improvements

NAKIVO 11.2.2 also includes several storage-platform updates. The official release notes list support for HPE StoreOnce VSA Gen4 version 4.3.13, HPE StoreOnce VSA Gen5 version 5.2.0, QuTS hero h6.0.0.3500 and QTS 5.2.9.3499.

NAKIVO’s official v11.2.2 announcement also highlights updated NAS backup licensing with TB-based subscription SKUs and a licensing interface intended to make purchased and consumed capacity easier to track.

For organizations using NAS platforms as backup infrastructure, these changes can make capacity planning and deployment easier to manage as protected file-share data grows.

Bare Metal Recovery Adds RAID Volume Targets

Another practical improvement in v11.2.2 is support for RAID volumes as targets during Bare Metal Recovery.

This matters in physical-server recovery scenarios where the destination system uses RAID storage. Recovery workflows should always be validated against the actual hardware and storage configuration before being considered production-ready.

Security and Reliability Improvements

Backup software is part of an organization’s security boundary, so security fixes are particularly important when evaluating maintenance releases.

The release also contains reliability fixes affecting job scheduling, shared-mailbox licensing, configuration exports, tenant alarms, Nutanix backup behavior and linked-job scheduling.

NAKIVO 11.2.2 Support Lifecycle

NAKIVO also notes that updating this specific release version is not supported after its lifecycle conditions require moving to another supported release. Administrators should therefore review the current release and upgrade policy before standardizing on an older maintenance version.

Why This Release Matters for Hybrid Virtualization Environments

The biggest practical advantage of NAKIVO 11.2.2 is not a single feature. It is the ability to keep backup operations aligned with rapidly changing virtualization infrastructure.

Many organizations now operate heterogeneous environments containing VMware, Proxmox, physical servers and NAS storage. A backup platform that supports multiple infrastructure types can reduce operational fragmentation and make recovery procedures easier to standardize.

The vSphere 9.1 and Proxmox VE 9.1/9.2 support is therefore particularly relevant for infrastructure teams planning platform upgrades, VMware-to-Proxmox migration projects or long-term hybrid virtualization strategies.

Should You Upgrade to NAKIVO 11.2.2?

If you are specifically running VMware vSphere 9.1 or Proxmox VE 9.1/9.2, v11.2.2 provides important compatibility improvements. Existing NAKIVO deployments should be reviewed against the official compatibility matrix and release documentation before upgrading.

However, because NAKIVO released v11.2.3 after v11.2.2, organizations performing a new installation today should not automatically choose 11.2.2 simply because this article covers that release.

Backup Best Practices After the Upgrade

Updating backup software is only one part of a reliable data protection strategy. After upgrading NAKIVO, administrators should verify the actual recovery process.

1. Run a successful backup job against representative workloads.
2. Verify that incremental backup chains continue working correctly.
3. Perform a test file-level recovery.
4. Test complete VM recovery for critical workloads.
5. Validate replication and failover workflows where they are used.
6. Confirm repository health and available capacity.
7. Review backup immutability and access controls.
8. Keep backup infrastructure separated from ordinary production administrative access where possible.

A backup job being marked successful is not the same as proving that an organization can recover its workloads during an outage. Periodic recovery testing remains essential.

Conclusion

NAKIVO Backup & Replication 11.2.2 is a compatibility-focused release aimed at keeping modern backup environments aligned with newer virtualization and operating-system platforms.

Full VMware vSphere 9.1 support is the headline change, while Proxmox VE 9.1 and 9.2 support, Real-Time Replication for vSphere 9.1, expanded physical-machine OS coverage, NAS improvements and reliability fixes make the release relevant to a broader range of infrastructure teams.

For VMware and Proxmox administrators, the practical lesson is straightforward: backup compatibility should be part of every virtualization upgrade plan. Before upgrading production infrastructure, verify the supported NAKIVO version, test backups and confirm that critical recovery procedures still work.