Supported Platforms

NAKIVO Backup & Replication provides data protection for the following platforms:

  • VMware vSphere v5.5 - v8.0d

  • VMware Cloud Director v10.2.1 - v10.6

  • Microsoft Server 2022, 20H2, 2019, 2016, 2012R2, 2012, 20H1 with a Hyper-V role7

  • Amazon EC2

  • Nutanix AHV v6.5 (LTS) - Nutanix AHV v6.10 (LTS)

  • Proxmox VE 8.x

  • Microsoft Windows Server 2025, 2022, 20H2, 2019, 2016, 2012R2, 2012

  • Microsoft Windows 10 Pro, Windows 10 Home, Windows 10 Enterprise, Windows 11

  • Linux Servers and workstations (see Physical machine requirements)

  • Microsoft 365 (Exchange Online, OneDrive for Business, SharePoint Online, Teams)

  • Oracle Database (RMAN)

  • File shares with the following protocols: NFS 3.x, SMB 1.x, SMB 2.x, SMB 3.x

Notes

  • To learn about the limitations of NAKIVO Backup & Replication related to supported platforms, refer to the Platform Limitations section of the latest Release Notes.

  • To add a supported platform to NAKIVO Backup & Replication, make sure that your system has been updated with the latest patch and all the necessary requirements are met.

  • The support for sub-versions that are not stated in the user guide can be clarified with the support team.

Find the necessary requirements below:

Hypervisor Requirements

To provide data protection for your virtual environments, make sure the following requirements are met:

VMware vSphere

  • Full administrative permissions (recommended), or limited permissions are required.

  • VPXA service must be running.

Microsoft Hyper-V

  • Full GUI installation of Windows Server is required.

  • Full administrative permissions are required.

  • Default administrative shares must be enabled on Hyper-V hosts.

  • The "File server" role must be enabled on Hyper-V hosts.

  • The SMB (1.x, 2.x, 3.x) protocol should be enabled on Hyper-V hosts.

  • 2019, 2022 Hyper-V Server Core (with the Server Core App Compatibility Feature on Demand package) is supported.

Nutanix AHV

  • User admin or cluster admin permissions are required.

Proxmox VE

  • For more details, refer to Proxmox VE versions table.

  • Admin account used to discover Proxmox VE cluster/host must have root privileges.

Physical Machine Requirements

To provide data protection for Windows and Linux physical machines, make sure they meet the following hardware and software requirements:

Hardware

  • CPU: x86_64

  • RAM: At least 2 GB

  • Firmware: BIOS or UEFI

  • Partition table: MBR or GPT

  • Disk space:

    • Windows: 500 MB for Transporter/Physical agent

    • Linux: 100 MB for Physical agent, 300 MB for Transporter

      Note

      The disk space requirements listed above apply specifically to auto-injected Physical Agent and Transporter.

Software

  • Supported Windows operating systems:

    • Microsoft Windows Server 2025 (x64)

    • Microsoft Windows Server 2022 (21H2) (x64)

    • Microsoft Windows Server 20H2 (x64)

    • Microsoft Windows Server 2019 (x64)

    • Microsoft Windows Server 2016 (x64)

    • Microsoft Windows Server 2012R2 (x64)

    • Microsoft Windows Server 2012 (x64)

  • Supported workstations:

    • Windows 11 (21H2/22H2/23H2) (x64)

    • Microsoft Windows 10 Enterprise (x64)

    • Microsoft Windows 10 Pro (x64)

    • Microsoft Windows 10 Home (x64)

    • Windows 8 Professional (x64)

  • Supported Windows File Systems:

    • NTFS

    • ReFS

  • Supported Recovery Destinations:

    • VMware vSphere version 6.7 or later

  • TPM module and Bitlocker are supported.

    Notes

    • It is possible to recover to a target VM/machine with or without TPM module.

    • If a volume is locked while the backup is ongoing, after the machine is recovered, such volume is restored in the locked state.

    • If a volume is unlocked while the backup is ongoing, after the machine is recovered, such volume is restored in the unlocked state

    • Recovery of the unlocked volume does not preserve the BitLocker configuration.

    • It is not possible to perform granular recovery for a locked volume.

  • Physical machines should be accessible over the network.

  • Physical machines must have WMIC installed.

  • Administrative credentials should be provided to the physical machine.

  • PowerShell must be installed.

  • SMB v1 or higher version of SMB protocol must be enabled. In case a firewall is enabled, the corresponding rule for SMB-in needs to be enabled too.

  • Selected users should have permissions to "Log on as a batch job".

  • Default administrative shares must be enabled on the physical machine and accessible over the network.

  • The dm_snapshot kernel module must be loaded to use app-aware mode.

  • Supported Linux operating systems:

    • Rocky Linux v8.3 - v9.4 (x64)

    • Debian v10.1 - v12.8 (x64)

    • Ubuntu (Server) v16.04 - v24.04 LTS (x64)

    • RHEL v7.4 - v9.5 (x64)

    • SLES v12 SP3 - v15 SP6 (x64)

    • Oracle Linux v7.4 - v9.4 (x64)

    • CentOS v7.0 - v8.5 (x64)

    • CentOS Stream v8 - v9 (x64)

    • AlmaLinux 8.7 - v9.4 (x64)

    • Supported workstations:

    • Ubuntu 18.04 (Desktop) LTS, 64-bit

    • Ubuntu 20.04 (Desktop) LTS, 64-bit

    • Ubuntu 22.04 (Desktop) LTS, 64-bit

    • Ubuntu 24.04 (Desktop) LTS, 64-bit

  • Supported Linux File Systems:

    • NTFS

    • Ext2

    • Ext3

    • Ext4

    • FAT32

    • XFS

    • Linux SWAP

    • ReiserFS

  • Connection to the following TCP ports should be allowed by the firewall of the target system:
    22 – Used by SSH for secure logins, file transfers (scp, sftp) and port forwarding.
    9446 – Used by NAKIVO Backup & Replication to communicate with the server.

  • openssh-server package should be installed.

  • sshd service should be running.

  • parted utility should be installed.

  • root login over ssh should be enabled if you use the root user. Check the /etc/ssh/sshd_config file to have a line: PermitRootLogin yes. Refer to Linux vendor documentation for more details.

  • /etc/pam.d/bhsvc file with special permissions provided to the Transporter service is required. Refer to the Required Permissions for Linux Recovery Server knowledge base article for details.

  • selinux configuration should be set to disabled if present. Refer to the File Recovery: Empty Disk knowledge base article for details.

  • PasswordAuthentication should be set to "Yes".

  • $ExecutionContext.SessionState.LanguageMode in PowerShell must be set to FullLanguage.

  • If you add a physical machine to the NAKIVO Backup & Replication inventory with a non-root account, the following is required:

    • sudo must be installed on the physical machine.

    • The sudo lecture must be disabled on the physical machine.

    • For private key authentication, public key must be added to the authorized_keys file in the .ssh/ directory on the Linux server.

    • Root or a user with enabled NOPASSWD:ALL setting in /etc/sudoers must be used.

Note:

For the member of the sudo group, %sudo ALL=(ALL:ALL) ALL can take precedence over ALL=(ALL:ALL) NOPASSWD: ALL, so you will need to remove the user from the sudoers group.

Public Cloud Requirements

Note

NAKIVO Backup & Replication does not support the following:

  • Backblaze deltas that are larger than 4 TiB

  • AWS/Wasabi/S3-compatible deltas that are larger than 20 TiB

  • Azure deltas that are larger than 800 TiB

Amazon EC2

Refer to Required AWS IAM Permissions for Amazon EC2 for details.

Note
There is also an option for granting full IAM permissions for NAKIVO Backup & Replication.

Amazon S3 and Backblaze

Refer to Required AWS IAM Permissions for Amazon S3 and Backblaze for details.

Note
There is also an option for granting full IAM permissions for NAKIVO Backup & Replication.

Microsoft Azure

NAKIVO Backup & Replication supports the following storage account types:

Storage account type

Supported services

Supported access tiers

Standard general-purpose v2

Blob storage (including Data Lake Storage), Queue Storage, Table storage, and Azure Files

Hot, Cool

Standard general-purpose v1

Blob storage (including Data Lake Storage), Queue Storage, Table storage, and Azure Files

N/A

Refer to Configuring a Microsoft Azure Storage Account for more information.

Microsoft 365 Requirements

To provide data protection for your Microsoft 365, the following requirements must be met:

  • Exchange Online must be purchased as a part of the Microsoft 365 plan or a standalone service.

  • The required API permissions must be provided to NAKIVO Backup & Replication. Refer to Required API Permissions for Microsoft 365.

  • For automatic enabling of the "Site Collection Administrator" role, a Microsoft 365 account user must have the "SharePoint admin" or "Global admin" role. This is required for backing up and recovery of SharePoint Online sites.

  • Microsoft 365 account must be accessible over the network.

  • Conditional Access must be disabled in Azure portal. Alternatively, the account must be added as "excluded" from the Conditional Access.

  • When recovering from an incremental with full repository, the /nakivo/transporter/java/tmp folder on the installed transporter must have more space than the size of 3 largest items being recovered, otherwise recovery may fail.

  • To backup and restore Microsoft 365 services, a Transporter should be installed on one of the following operating systems:

Windows

  • Windows Server 2022 (21H2) (x64)

  • Windows Server 20H2 (x64)

  • Windows Server 2019 Standard (x64)

  • Windows Server 2016 Standard (x64)

  • Windows Server 2012 R2 Standard (x64)

  • Update for Windows Server 2012 R2 (KB3179574)

  • Windows Server 2012 Standard (x64)

  • Windows 11 (x64)

  • Windows 10 Enterprise (x64)

  • Windows 10 Home (x64)

  • Windows 10 Pro (x64)

  • Windows 8 Pro (x64)

Linux

  • Debian 12.1 (64-bit)

  • Debian 11.7 (64-bit)

  • Debian 11.6 (64-bit)

  • Debian 11.5 (64-bit)

  • Debian 11.4 (64-bit)

  • Debian 11.3 (64-bit)

  • Debian 11.2 (64-bit)

  • Debian 11.1 (64-bit)

  • Debian 11.0 (64-bit)

  • Debian 10.13 (64-bit)

  • Debian 10.12 (64-bit)

  • Debian 10.11 (64-bit)

  • Debian 10.10 (64-bit)

  • Debian 10.9 (64-bit)

  • Debian 10.8 (64-bit)

  • Debian 10.7 (64-bit)

  • Debian 10.6 (64-bit)

  • Debian 10.5 (64-bit)

  • Debian 10.4 (64-bit)

  • Debian 10.3 (64-bit)

  • Debian 10.2 (64-bit)

  • Debian 10.1 (64-bit)

  • Ubuntu 22.04 Server (x64)

  • Ubuntu 20.04 Server (x64)

  • Ubuntu 18.04 Server (x64)

  • Ubuntu 16.04 Server (x64)

  • SUSE Linux Enterprise Server 12 SP1 – 15 SP4 (x64)

  • Red Hat Enterprise Linux v7.0 – v9.2 (x64)

  • CentOS v7.0 – v8.4 (x64)

  • CentOS Stream 8 – 9 (x64)

NAS
Refer to Deployment Requirements to see the list of supported NAS devices.

Note
ARM-based NAS devices are not supported for backup and recovery of Microsoft 365 accounts.

Oracle Database Requirements

To provide data protection for your Oracle database, make sure of the following:

  • Oracle database is accessible over the network.

  • Provided Oracle database credentials have necessary permissions to be used by the product:

    • Users must have SYSDBA privileges (example: `sys` user)

  • Provided OS credentials for the Oracle database have sufficient permissions to be used by the product:

    • User accounts and groups must have system administration privileges to manage Oracle software (example: `oracle` user, `oinstall`, `dba` group)

  • Oracle database must be set to ARCHIVELOG mode to create backups.

Supported operating systems:

  • Windows Server 2016 Standard (x64)

  • Windows Server 2012 R2 Standard (x64)

  • Update for Windows Server 2012 R2

  • Windows Server 2012 Standard (x64)

  • Windows Server 2008 R2 Standard (x64)

  • Red Hat Enterprise Linux 7.4 - 9.0 (x64)

  • Oracle Linux 7 - 9 (x64)

  • SUSE Linux Enterprise Server 12 SP3/SP4/SP5 (x64)

  • SUSE Linux Enterprise Server 15 SP1/SP2/SP3/SP4/SP5/SP6 (x64)

  • CentOS 7.0 - 7.9 (x64)

  • CentOS Stream 8 - 9 (x64)

Supported Oracle Database release versions:

  • Oracle database 23c Free

  • Oracle database 21c

  • Oracle Database 19c

  • Oracle Database 18c

  • Oracle Database 12c R2

  • Oracle Database 11g R2

Cloud Region Requirements

For Amazon S3 or Amazon EC2, NAKIVO Backup & Replication supports the following regions:

  • AWS GovCloud (US-West)

  • AWS GovCloud (US-East)

  • US East (Ohio)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • Africa (Cape Town)

  • Asia Pacific (Hong Kong)

  • Asia Pacific (Hyderabad)

  • Asia Pacific (Jakarta)

  • Asia Pacific (Malaysia)

  • Asia Pacific (Melbourne)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Osaka)

  • Asia Pacific (Seoul)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Asia Pacific (Tokyo)

  • Canada (Calgary)

  • Canada (Central)

  • EU (Frankfurt)

  • EU (Zurich)

  • EU (Ireland)

  • EU (London)

  • EU (Milan)

  • EU (Spain)

  • EU (Paris)

  • EU (Stockholm)

  • Israel (Tel Aviv)

  • Middle East (Bahrain)

  • Middle East (UAE)

  • South America (Sao Paulo)

For Wasabi, NAKIVO Backup & Replication supports the following regions:

  • Wasabi US East 1 (N. Virginia)

  • Wasabi US East 2 (N. Virginia)

  • Wasabi US Central 1 (Texas)

  • Wasabi US West 1 (Oregon)

  • Wasabi CA Central 1 (Toronto)

  • Wasabi EU West 1 (London)

  • Wasabi EU West 2 (Paris)

  • Wasabi EU Central 1 (Amsterdam)

  • Wasabi EU Central 2 (Frankfurt)

  • Wasabi AP Northeast 1 (Tokyo)

  • Wasabi AP Northeast 2 (Osaka)

  • Wasabi AP Southeast 1 (Singapore)

  • Wasabi AP Southeast 2 (Sydney, Australia)