Page tree
Skip to end of metadata
Go to start of metadata

Deployment Requirements

Virtual/Physical Machine

NAKIVO Backup & Replication can be installed on a virtual or physical machine with the following characteristics:

  • Director and Onboard Transporter:
    • CPU: x86-64, 2 cores  
    • RAM: 4 GB RAM + 250 MB RAM for each concurrent job
    • Free space: 1GB
  • Transporter:
    • CPU: x86-64, 2 cores
    • RAM: 2 GB RAM + 250 MB RAM for each concurrent job
    • Free space: 1GB

Supported Operating Systems

NAKIVO Backup & Replication can be fully installed on the following operating systems:

  • Windows:
    • Windows Server 2012 R2 Standard (x64)
    • Windows Server 2012 Standard (x64)
    • Windows Server 2008 R2 Standard (x64)
    • Windows 10 Professional (x64)
    • Windows 8 Professional (x64)
    • Windows 7 Professional (x64)
  • Linux:
    • Ubuntu 12.04 Server (x64)
    • SUSE Linux Enterprise Server 11 SP3 (64-bit)
    • Red Hat Enterprise Linux 6.3 (64-bit)
  • NAS:
    • Synology DSM v5.2
    • Synology DSM v6.0
    • WD MyCloud firmware 2.10.302

Supported OS Localizations

NAKIVO Backup & Replication supports the following OS localizations:

  • English
  • Italian
  • German
  • French
  • Spanish

Network Attached Storage (NAS)

NAKIVO Backup & Replication can be installed on a NAS with the following minimum hardware characteristics:

  • CPU: x86-64, 2 cores
  • RAM: 1 GB RAM
  • Free space: 1GB

NAKIVO Backup & Replication can be installed on the following NAS models:

Synology

  • RS18016xs+
  • RS3614xs+
  • RC18015xs+
  • RS3614xs
  • RS3614RPxs
  • DS3615xs 
  • RS2416+
  • RS2416RP+
  • RS815+
  • RS815RP+
  • DS2415+
  • DS1815+
  • DS1515+
  • DS415+
  • DS412+
  • RS2414+
  • RS2414RP+
  • DS2413+
  • DS1813+
  • DS1513+
  • DS716+
  • DS716+II
  • DS713+
  • DS216+
  • DS216+II
  • DS916+

Western Digital

  • My Cloud DL2100  

  • My Cloud DL4100  

Supported Web Browsers

NAKIVO Backup & Replication can be accessed from the following Web browsers:

  • Google Chrome v26 or later
  • Mozilla Firefox v21 or later

Supported Hypervisors

  • NAKIVO Backup & Replication supports the following editions of VMware vSphere v4.1 - v6.0:
    • Essentials
    • Essentials Plus
    • ROBO
    • ROBO Advanced
    • Standard
    • Enterprise
    • Enterprise Plus
  • Required VMware vSphere permissions:

IMPORTANT: Make sure that your hypervisor is updated with the latest patch. 

Network

NAKIVO Backup & Replication has been tested to work in the following minimal network conditions:

  • Latency (RTT): Up to 250 ms
  • Packet loss: Up to 1%
  • Bandwidth: 1Mb/s or higher

ICMP ping traffic should be allowed on all hosts where NAKIVO Backup & Replication components are installed as well as on all source and target ESX(i) hosts in order for the automatic Transporter selection feature to function properly.

Required Ports

NAKIVO Backup & Replication requires the following TCP ports to be open for successful operation:

TCP Port  #
(Default)
Where
Description
443vCenter Server
ESXi hosts

Used by Director and Transporters to access VMware infrastructure. Must be open on vCenter Servers and ESXi hosts.

902ESXi hosts

Used by Transporters to access VMware infrastructure. Must be open on ESXi hosts.

4443DirectorUsed to access the Director web UI. Must be open on the Director machine.
9446TransporterUsed by Director and Transporters to communicate with the Transporter. Must be open on the Transporter machine.
9448-10000TransporterUsed by Transporters for cross-Transporter data transfer. Must be open on the Transporter machine.

Feature Requirements

VM Backup and Replication

NAKIVO Backup & Replication provides limited support for the following VM disk types:

  • RDM disks are supported only in virtual compatibility mode. RDM disks in physical compatibility mode are not supported (since such disks are not affected by snapshots).
  • Backed up RDM disks in virtual compatibility mode are recovered as thin disks.
  • Replicas of source VMs with RDM disks in virtual compatibility mode are created with thin disks.
  • Independent disks are not supported.
  • A Transporter installed on Linux should be used to back up and replicate VMs with SATA disks.

Flash VM Boot

ESX/ESXi hosts enable binding the software iSCSI adapter (HBA) to VM Kernel network(s). If such a binding is configured for an ESX/ESXi host that is used as a target for Flash VM Boot, the connectivity between the host and the Transporter might not be available at the iSCSI layer.

If an iSCSI binding is configured for a host which you plan to use as a target for Flash VM Boot, verify or configure the connectivity at the iSCSI layer (either by selecting a host without binding, removing binding on a host, or adding dedicated VM Kernel network to the binding that allows the connectivity).

File Recovery

While NAKIVO Backup & Replication supports all VM file systems for backup, replication, and full VM recovery, only the following VM file systems are supported for file recovery:

  • If a Transporter is installed on Windows:
    • NTFS
    • FAT32
  • If a Transporter is installed on Linux:
    • NTFS
    • FAT32
    • EXT3
    • EXT4
    • XFS
  • File recovery from Windows dynamic disks and Linux LVM volumes is available only in case the Transporter assigned to the Backup Repository is installed on a Linux OS.
  • File recovery is not supported for independent, encrypted, and RAID disks.
  • File recovery from LVM volumes is not available if the Transporter that is assigned to a backup repository is installed on a NAS (such as Synology, QNAP, or Western Digital). 
  • File recovery from systems that use Windows-only features, such as Windows Data Deduplication or DFS, is available only in case the Transporter assigned to a backup repository is installed on Windows machine with such features enabled.

Object Recovery for Microsoft Exchange

NAKIVO Backup & Replication supports the following versions of Microsoft Exchange for objects recovery:

  • Microsoft Exchange 2016
  • Microsoft Exchange 2013
  • Microsoft Exchange 2010
  • Microsoft Exchange 2007

Log Truncation for Microsoft Exchange

NAKIVO Backup & Replication supports the following versions of Microsoft Exchange for logs truncation:

  • Microsoft Exchange 2016
  • Microsoft Exchange 2013
  • Microsoft Exchange 2010
  • Microsoft Exchange 2007

Object Recovery for Microsoft Active Directory

NAKIVO Backup & Replication supports the following versions of Microsoft Active Directory for objects recovery:

  • Windows 2012 R2
  • Windows 2012
  • Windows 2008 R2
  • Windows 2008 

Application Awareness for Windows-based Amazon EC2 Instances

Application awareness is supported for Amazon EC2 Instances running the the following operating systems:

  • Windows Server 2008 R2 Standard (x64)
  • Windows Server 2012 Standard (x64)
  • Windows Server 2012 R2 Standard (x64)

Requirements for Windows-based Amazon EC2 Instances

The following features should be enabled in Windows-based Amazon EC2 Instances in order for application awareness to work:

  • Windows Server 2008: The File Services role should be enabled in the OS
  • Windows Server 2012: The File and Storage Services role should be enabled in the OS
  • Default administrative shares should be enabled in the Windows OS
  • The SMB v1 protocol should be enabled in the Windows OS

Requirements for Security Groups of Source EC2 Instances

Ports 445 and 9446 should be added to the security group of source Amazon EC2 Instances (those that you plan to back up or replicate).

Requirements for the Director Machine 

If the Director is installed in an Amazon EC2 Instance, the following requirements should be met:

  • OS firewall should allow access to the TCP port 9446 on the machine where the Director is installed.

  • The security group of the Instance where the Director is installed should allow access to TCP ports 445 and 9446.

Hot Add

In order for the Hot Add feature to work for VM backup, replication, and recovery, the following requirements must be met:

  • The Transporter that will be reading or writing data from/to the VM disks should run on a VM.
  • The Transporter VM should:
    • Be available in the product's Inventory.
    • Run on a host that has access to the datastore(s) with the VM disks.
    • Run in the same datacenter as the VM to be processed.

The Hot Add feature is not available for VMs that contain IDE disks. 

  • No labels