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

Supported Hypervisors and Clouds

NAKIVO Backup & Replication supports the following hypervisors and clouds:

  • AWS EC2
  • Microsoft Hyper-V 2016, 2012(R2), 2012
  • VMware vSphere v4.1 - v6.5

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

Hypervisor Requirements

VMware: 

The LAN data transfer mode is not supported by default for vSphere vv4.1, 5.0, and 5.1. Please learn how to enable it here.

 Microsoft Hyper-V:

  • 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

Cloud Requirements

AWS

You have two options: either grant full IAM permissions to NAKIVO Backup & Replication or grant only permissions listed below:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "ec2:DescribeAvailabilityZones",
                "ec2:DescribeVpcs",
                "ec2:DescribeSubnets",
                "ec2:DescribeSecurityGroups",
                "ec2:DescribeInstances",
                "ec2:DescribeInstanceAttribute",
                "ec2:DescribeInstanceStatus",
                "ec2:DescribeVolumes",
                "ec2:DescribeVolumeAttribute",
                "ec2:DescribeVolumeStatus",
                "ec2:DescribeNetworkInterfaces",
                "ec2:DescribeNetworkInterfaceAttribute",
                "ec2:DescribeImages",
                "ec2:DescribeImageAttribute",
                "ec2:DescribeSnapshots",
                "ec2:DescribeSnapshotAttribute",
                "ec2:DescribeKeyPairs"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:AttachClassicLinkVpc",
                "ec2:DetachClassicLinkVpc",
                "ec2:GetConsoleScreenshot",
                "ec2:RunInstances",
                "ec2:StartInstances",
                "ec2:StopInstances",
                "ec2:RebootInstances",
                "ec2:TerminateInstances",
                "ec2:ModifyInstanceAttribute",
                "ec2:ModifyInstancePlacement",
                "ec2:ImportInstance"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": "ec2:CreateTags",
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateKeyPair",
                "ec2:DeleteKeyPair"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateSecurityGroup",
                "ec2:DeleteSecurityGroup"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": "ec2:AuthorizeSecurityGroupIngress",
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": "ec2:DescribeRouteTables",
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateVpc",
                "ec2:DeleteVpc"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateSubnet",
                "ec2:DeleteSubnet",
                "ec2:ModifySubnetAttribute"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:DescribeInternetGateways",
                "ec2:CreateInternetGateway",
                "ec2:DeleteInternetGateway",
                "ec2:AttachInternetGateway"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:DescribeRouteTables",
                "ec2:CreateRouteTable",
                "ec2:DeleteRouteTable",
                "ec2:AssociateRouteTable"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateVolume",
                "ec2:DeleteVolume",
                "ec2:AttachVolume",
                "ec2:DetachVolume",
                "ec2:ModifyVolumeAttribute"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:CreateSnapshot",
                "ec2:DeleteSnapshot",
                "ec2:ModifySnapshotAttribute",
                "ec2:CopySnapshot"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": [
                "ec2:DeregisterImage",
                "ec2:RegisterImage",
                "ec2:CreateImage",
                "ec2:DeleteImage"
            ],
            "Effect": "Allow",
            "Resource": "*"
        },
        {
            "Action": "iam:GetUser",
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

 

Deployment Requirements

Hardware

VM or Physical Machine

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

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

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

Operating System

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

  • Windows:
    • Windows Server 2016
    • 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 16.04 Server (x64)
    • 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 Operating System Localizations

NAKIVO Backup & Replication can be installed on a supported OS with the following OS localization:

  • English
  • Italian
  • German
  • French
  • Spanish

Ports

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

TCP Port  #
(Default)
Where
Description
NAKIVO Backup & Replication  
4443DirectorUsed to access the Director web UI. Must be opened on the Director machine.
9446TransporterUsed by Director and Transporters to communicate with the Transporter. Must be opened on the Transporter machine.
9448-10000TransporterUsed by Transporters for cross-Transporter data transfer. Must be opened on the Transporter machine.
VMware
443vCenter Server,
ESXi hosts

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

902ESXi hosts

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

Hyper-V
137-139Hyper-V hostsUsed by Director to upload files and install configuration service. Must be opened on Hyper-V servers.
445Hyper-V hostsUsed by Director to upload files and install configuration service. Must be opened on Hyper-V servers if Active Directory is used.
5986 (opened automatically)Hyper-V hostsUsed by Transporter to add a host to inventory and establish a connection with it.
9445 (opened automatically)Hyper-V hostsUsed by Director to upload files and install configuration service. Must be opened on Hyper-V host if NAKIVO Backup & Replication is installed on a host and this host is added to inventory at the same time.
9446 (opened automatically)Hyper-V hostsUsed by Director and Transporters to communicate with the Transporter. Must be opened on the Transporter machine.
9448-10000 (opened automatically)Hyper-V hostsUsed by Transporters for cross-Transporter data transfer. Must be opened on the Transporter machine.

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: 1 Mb/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 hosts in order for the automatic Transporter selection feature to function properly.

Web Browsers

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

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

Feature Requirements and Limitations

VM Backup and Replication

NAKIVO Backup & Replication provides limited support for the following VMware 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.

Skip Swap Files and Partitions

Skipping swap files is not supported for Windows dynamic disks. 

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 has the following limitations:

  • If hot-add cannot be enabled for at least one disk of a source VM (even if the disk is deselected in the job), then Hot-add will be unavailable for all disks of the VM.
  • The Hot Add feature is not available for VMs that contain IDE disks.
  • A SCSI controller on the VM hosting NAKIVO Backup & Replication can support up to 15 disks. This includes the disk of the VM with NAKIVO Backup & Replication and mounted disks of the Backup Repository. If you need to process VMs with the total number of disks that is larger than that limit, you need to install one or more additional SCSI controllers.

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

The following 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
  • If you use the ReiserFS file system, you need to install the linux-image-extra-virtual package: apt-get -y install linux-image-extra-virtual for Ubuntu.
  • 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 and Log Truncation for Microsoft Exchange

NAKIVO Backup & Replication supports the following versions of Microsoft Exchange for object recovery and log truncation:

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

The following requirements should be met for log truncation:

  • NAKIVO Backup & Replication requires providing a domain user account that belongs to the following groups:
    • Administrators
    • Organization Management
  • NAKIVO Backup & Replication requires PowerShell v2 or later to be available on the Exchange machine.

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 AWS 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 AWS EC2 Instances

Default administrative shares in Windows-based AWS EC2 Instances should be enabled in order for application awareness to work.

Requirements for Security Groups of Source EC2 Instances

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

Requirements for the Director Machine 

If the Director is installed in an AWS 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.

Application Awareness for Hyper-V VMs

Refer to the Knowledge Base article.

  • No labels