Supported Platforms

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

  • Microsoft Windows Server 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)

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:

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

Software

  • Supported Windows operating systems:

    • 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)

  • Supported Windows File Systems:

    • NTFS

    • ReFS

  • Supported Recovery Destinations:

    • VMware vSphere version 6.7 or later

  • TPM module and Bitlocker are supported.

    Note

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

  • Physical machines should be accessible over the network.

  • 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.1 (x64)

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

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

    • SLES v12 SP1 - v15 SP4 (x64)

    • Oracle Linux v7.4 - v9.3 (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

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.

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 (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)