NAKIVO 

Backup & Replication v10.2

User Guide for VMware

-1-
Table of Contents
NAKIVO Backup & Replication Overview 5

Deployment Options 7

Data Protection 8

Data Recovery 18

Disaster Recovery 25

Backup Size Reduction 32

Reliability 36

Performance 44

Administration 62

Automation 66

Integration 70

BaaS 75

Licensing 80

Getting Started 83

Logging in to NAKIVO Backup and Replication 84

First Steps with NAKIVO Backup & Replication 88

Web Interface Components 91

Managing Jobs and Activities 96

Deployment 126

Architecture 127

System Requirements 136

Deployment Scenarios 171

-2-
 Installing NAKIVO Backup and Replication 187

Updating NAKIVO Backup and Replication 248

Uninstalling NAKIVO Backup and Replication 277

Settings 281

General 282

Inventory 329

Transporters 339

Backup Repositories 364

Tape 418

Virtual Appliance Configuration 444

Multi-Tenant Mode Configuration 448

Support Bundles 457

Built-in Support Chat 459

Replacing License 466

Backup 467

Creating VMware Backup Jobs 468

Creating Backup Copy Jobs 497

Backing Up to Tape 519

Staging (Seeding) Initial Backup 536

Deleting Backups 537

Recovery 542

Granular Recovery 543

Full Recovery 592

Recovery From Tape 630

Planning Disaster Recovery 639

-3-
 Failover VMware VMs: VMs 667

Failover VMware VMs: Options 668

Failback VMware VMs: VMs 669

Failback VMware VMs: Location 669

Failback VMware VMs: Options 671

Replication 694

Creating VMware Replication Jobs 695

Staging (Seeding) VM Replication 729

Multi-Tenant Mode 730

Tenant Creation 731

Tenant Configuration 738

Tenant Management 739

Granting Self-Service Access 750

Integration and Automation 751

Command Line Interface 752

Automation with HTTP API 764

Aptare IT Analytics Integration 765

-4-
NAKIVO Backup & Replication Over-
view
NAKIVO Backup & Replication offers backup, replication, failover, backup to the cloud, backup to tape, backup copy,
backup data reduction, instant verification, granular restore and disaster recovery orchestration for virtual, physical,
cloud and SaaS environments - all in one convenient web interface.

The product provides image-based, application-aware, incremental backup and replication. You can easily schedule jobs
using the calendar in the product's web interface and save up to 1,000 recovery points for each backup, rotating them
on a GFS basis. You can also protect your VMs and instances more efficiently by taking advantage of Changed Block
Tracking (for VMware), Resilient Change Tracking (for Hyper-V), or Changed Regions Tracking (for Nutanix), LAN-Free
Data Transfer, and Network Acceleration.
The solution includes an advanced disaster recovery (DR) functionality. It allows you to automate and orchestrate DR
activities across multiple sites. Build advanced site recovery workflows to failover an entire site in just a few clicks,
perform non-disruptive recoverability testing, and make sure you have a workable DR plan in place to help minimize
downtime and prevent loss of revenue or data.
NAKIVO Backup & Replication allows you to simplify data protection management through the automation of core
tasks such as backup, replication, and backup copy. Instead of tracking every change in your environment and
manually adding VMs or physical machines to jobs, you can set up policies based on a VM/physical machine name, tag,
size, location, power state, configuration, or other parameters. NAKIVO Backup & Replication can regularly scan your
infrastructure and automatically protect VMs, physical machines, and Amazon EC2 instances that match policy rules.

-5-
With NAKIVO Backup & Replication, you can also ensure the safety and integrity of your Microsoft Office 365 data. The
product allows you to reliably protect Microsoft Exchange mailboxes, OneDrives for Business, and SharePoint Online
sites. All backup data can be instantly recovered for uninterrupted workflow and productivity.

-6-
Deployment Options
NAKIVO Backup & Replication is a versatile solution that can be installed on most modern operating systems and
hardware solutions. For details, refer to the following topics:
l “Installing on Windows” on page 210
l “Installing on Linux” on page 217
l “Deploying Amazon Machine Image in Amazon EC2” on page 209
l “Installing on FreeNAS” on page 246
l “Installing on Synology NAS” on page 224
l “Installing on QNAP NAS” on page 230
l “Installing on Western Digital NAS” on page 240
l “Installing on ASUSTOR NAS” on page 235
l “Installing on NETGEAR ReadyNAS” on page 242
l “Installing on Generic ARM-based Device” on page 245
l “Installing on Raspberry Pi” on page 247
For the full list of supported systems and devices, refer to “Deployment Requirements” on page 140.

-7-
Data Protection
Data protection is the process of safeguarding business-critical information from loss, corruption or compromise.
NAKIVO Backup & Replication offers a complete suite of backup features to protect physical, virtual, and cloud
environments. By providing you with great flexibility and multiple automation options, the product can save you time
and resources. For more information about the data protection offered by NAKIVO Backup & Replication, refer to the
following topics:
l “Backup Copy” on page 9
l “Backup to Cloud” on page 13
l “Container Protection” on page 15
l “Virtual Machine Backup” on page 17

-8-
Backup Copy
Backups can be lost on account of a number of reasons, so having more than one copy of your business-critical backups
is vital for ensuring that your data can be recovered in case of disaster. Backup Copy jobs provide a simple yet powerful
way to create and maintain copies of your backups. Backup copy jobs copy backups from one Backup Repository to
another without affecting the source ESXi hosts, VMs, Amazon EC2 instances, or physical machines. This way, your
source VMs, physical machines or Amazon EC2 instances are read-only once while backups can be copied to one or
multiple locations.
l Create Mirrored Copy of your Backup Repository
l Copy Most Important Backups
l Copy Backups Created by Particular Backup Jobs
l Save Storage Space with Variable Data Compression
l Copy Backups Offsite
l Copy Backups to Amazon Cloud
l Copy Recovery Points that You Need
l Schedule Backup Copy to Suit Your Needs

Create Mirrored Copy of your Backup Repository

With a Backup Copy job, you can create and maintain a mirrored copy of your primary Backup Repository, which is the
simplest and the most reliable way to protect all your backups. Think of it as a Backup Repository replication: all
backups and recovery points that appear in the Backup Repository A will be automatically sent to Backup Repository B:

Copy Most Important Backups

To save storage space on your secondary Backup Repository and to speed up data transfer, you can choose to create a
Backup Copy job for only the most important backups:

-9-
This way, only the selected backups (and their recovery points) will be transferred to the secondary Backup Repository.

Copy Backups Created by Particular Backup Jobs

NAKIVO Backup & Replication enables you to create and maintain copies of backups created by particular Backup jobs:

This way, you can ensure that all backups created by important Backup jobs are copied to a secondary Backup
Repository.

Save Storage Space with Variable Data Compression

In addition to global data deduplication, NAKIVO Backup & Replication automatically compresses backed up data to
reduce the amount of space that backups occupy in storage. By default, the compression level in the new Backup
Repositories is set to “Fast,” so that your Backup jobs will run faster. When creating a secondary Backup Repository,
you can set the compression level to “Best,” which uses more CPU, but delivers better compression levels. This way, the
strongest compression algorithm will be used to compress backup data, resulting in smaller backups in your secondary
Backup Repository.

- 10 -
Copy Backups Offsite
While you can keep copies of your backups locally, having at least one copy of your most critical backups offsite can
save you a lot of trouble in case a local disaster should wipe your primary backups. The secondary Backup Repository
can be placed in any location that has a connection to the Internet, since backup data can be transferred via AES 256
encrypted link, and your secondary backup repository can be encrypted as well.

Copy Backups to Amazon Cloud

Amazon provides one of the most reliable and affordable cloud services in the industry. With NAKIVO Backup &
Replication, you can use Amazon's fast, reliable, and affordable cloud to store copies of your backups.

Copy Recovery Points that You Need

Each backup can contain up to 4,000 recovery points, which are saved based on recovery point retention policy, i.e.
how many recovery points you want to have and for how long you want to keep them. With Backup Copy jobs, you can
choose to create a mirrored copy of each backup: all recovery points that are available in Backup Repository A will be
copied to Backup Repository B.

- 11 -
However, Backup and Backup Copy are different jobs, so you can set different retention policies for your primary
backups and their copies in a different Backup Repository. This way, for example, you can store several daily backups
onsite, and keep (archive) weekly, monthly, and yearly copies of backups in a secondary Backup Repository for long-
term storage.

Also, you can use fast storage for a subset of backups and use slower, but more reliable storage for long-term archiving.

Schedule Backup Copy to Suit Your Needs

Backup Copy jobs have their own schedule, so you can set them up to run whenever it suits your needs. For example,
you can set up a Backup Copy job to run every night on workdays, or set it up to run on weekends to send all backups
made during the week to a secondary Backup Repository.
 To learn how to create and run backup copy jobs with NAKIVO Backup & Replication, refer to “Creating Backup Copy
Jobs” on page 497.

- 12 -
Backup to Cloud
NAKIVO Backup & Replication provides a great way for safeguarding your business-critical data by letting you send
backup copies to Amazon EC2, Amazon S3, and Wasabi Hot Cloud Storage.

Keeping backups in the cloud provides a number of benefits, including:

l Safe Backup Storage – storing backups in the cloud keeps them safe even if local infrastructure becomes
unavailable.
l Flexible Backup Storage – cloud environments allow for expanding storage space as required, eliminating the
need to choose, order, install, and configure new servers or hard drives for your growing environment.
l Easy and quick Data Recovery – backups can be accessed at any time and from anywhere.
l Affordable Backup Storage – instead of buying and configuring offsite backup infrastructure, you can simply use
your existing hardware.
l Simple Backup Management – the "set it and forget it" approach in NAKIVO Backup & Replication allows for
scheduling regular "backup to cloud" jobs.
While cloud providers offer cloud storage at an affordable price, NAKIVO Backup & Replication helps reduce offsite
backup costs with features like incremental backup, skip swap files and partitions, backup deduplication, backup
compression, and other. Using NAKIVO Backup & Replication, you can keep the entire environment in the cloud or only
use Amazon EC2, Amazon S3, or Wasabi as a storage for backups.

Technology Behind "Backup to Cloud"

A backup represents a point-in-time copy of a VM or physical machine that is stored in the Backup Repository. A Backup
Repository is a destination designated for data storage. NAKIVO Backup & Replication allows you to send backups or
their copies to private/public clouds such as Amazon EC2, Amazon S3, or Wasabi. In NAKIVO Backup & Replication, a
backup job is performed as follows:
1. The product automatically creates temporary snapshots of the source VMs/physical machine.
2. The data that was changed (since the last backup) is identified and sent to the Backup Repository.
3. The temporary snapshots created in the process are removed.

- 13 -
However, backups can also get lost or damaged as a result of unexpected events. With NAKIVO Backup & Replication,
you can run backup copy jobs, which allow you to create and manage copies of your VMware, Hyper-V, Amazon EC2 or
physical machine backups. Creating copies of critical backups serves as an additional level of data protection.
NAKIVO Backup & Replication enables you to copy backups from one Backup Repository to another without touching
the source hosts or VMs. This decreases backup time and reduces network load. The process is entirely automatic,
meaning that you are only required to create and set up a backup copy job. After the initial configuration, your
secondary Backup Repository is automatically updated with all backups and recovery points from the primary Backup
Repository.
NAKIVO Backup & Replication includes an automated backup verification feature, which reads backups at the block
level, compares the data written to the Backup Repository with the data from the source machine, then checks whether
the data on both sites is identical and can be recovered in case of disaster.

For more details, refer to the following topics:

l “Backup Repository in Amazon EC2” on page 380
l “Backup Repository in Amazon S3” on page 385
l “Backup Repository in Wasabi Hot Cloud Storage” on page 388

- 14 -
Container Protection
VMs can be organized into containers, such as resource pools, clusters, and folders. This form of organization allows
you to easily add resources upon request and unload them when they are no longer necessary. NAKIVO Backup &
Replication allows you to add an entire container to a backup or replication job. All changes in the container (i.e. adding
to or removing from) are automatically reflected in a backup or replication job. Thus, all important VMs are
continuously protected. If certain VMs inside a container are not required to be backed up or replicated frequently, you
can exclude them from a backup or replication job. The container will still be protected but will not include less
important VMs. This will save space in the Backup Repository and increase the speed of backup or replication jobs. For
example, you set up a backup job for a cluster to run daily, but this cluster contains a couple of rather massive VMs that
do not require frequent backups; you can edit the job by excluding those VMs. NAKIVO Backup & Replication will ask
you whether to keep or remove backups made on previous job runs.
l Day 1

- 15 -
l Day 2

- 16 -
Virtual Machine Backup
NAKIVO Backup & Replication works in a virtual environment and uses an image-based approach to VM backup. It is an
agentless application that does not require you to install any additional software inside the VM guest OS to retrieve VM
data. It exploits virtualization platforms' snapshot capabilities to back up VMs. When you initiate a VM backup, NAKIVO
Backup & Replication requests a virtualization platform to create a VM snapshot which is basically a point-in-time copy
of a VM including its configuration, OS, applications, associated data, system state, and so on. The snapshot is used as
a source of data for backup. Copying of the data from the source datastore is performed at a block level. NAKIVO
Backup & Replication fetches the VM data, performs compression and deduplication, and finally stores the backup files
in the repository.
In NAKIVO Backup & Replication, backing up is performed via a job that must be created and configured prior to the
backup itself. A backup job is a configuration unit of the backup activity that defines when, what, how and where is to
be backed up. One or several VMs can be processed by a single backup job. A job can be started manually or scheduled
for execution. The initial job's run always produces a complete backup of the VM image. The following sessions can
create full or incremental backups. During incremental backups, NAKIVO Backup & Replication copies only blocks of
data that have changed since the last backup job session. Tracking of changed data blocks is performed using the
virtualization platforms' capabilities (CBT/RCT/CRT) or with NAKIVO Backup & Replication's proprietary method.
Technically, the VM backup process is performed according to the following flow depicted below:

To learn how to create VM backups with NAKIVO Backup & Replication, refer to “Backup” on page 467.

- 17 -
Data Recovery
One of the key elements of an effective protection strategy is ensuring that data can be restored quickly after any
corruption or loss. NAKIVO Backup & Replication provides several recovery options for maintaining the operational
backup of data and business continuity/disaster recovery:
Refer to the following topics for more information about data recovery:
l “Cross-Platform Recovery” on page 24
l “Instant File Recovery to Source” on page 19
l “Instant Object Recovery” on page 20
l “Instant VM Recovery - Flash VM Boot” on page 21
l “Universal Object Recovery” on page 23

- 18 -
Instant File Recovery to Source
The Instant File Recovery to Source feature allows you to recover files and folders to their original location (or any
custom location) in a single click. NAKIVO Backup & Replication can instantly recover files right from compressed and
deduplicated backups. Files can be recovered from both Windows and Linux-based machines. With the push of a
button, the selected files can be reinstated in their original location or in a new custom location on any VM/physical
machine, downloaded to the local machine, or sent via email. When restoring files back to the original location, the file
permissions are all restored as well. The Instant File Recovery feature works both via LAN and WAN. Thus, even if local
backups are unavailable, you can recover from a backup copy located, for example, in an Amazon EC2 cloud a thousand
miles away.
The file recovery process is simple and straightforward. First, select a backup and recovery point from which you wish to
recover files. The files and folders available for recovery are displayed right in the NAKIVO Backup & Replication web
interface. Browse or search for files, select the files you wish to recover, specify where you want them, click the button,
and behold! The files are instantly recovered.

To learn how to recover files with NAKIVO Backup & Replication, refer to “File Recovery” on page 544.

- 19 -
Instant Object Recovery
NAKIVO Backup & Replication provides you with the ability to instantly browse, search, and recover Microsoft Active
Directory, Microsoft Exchange, and Microsoft SQL Server directly from compressed and deduplicated backups. The
objects can be restored to the source server, to a different server, or exported to a custom location. The feature
streamlines, automates, and speeds up the process of restoring your data, and is available out-of-the-box in NAKIVO
Backup & Replication. For more information, refer to “Granular Recovery” on page 543.

- 20 -
Instant VM Recovery - Flash VM Boot
The Flash VM Boot feature allows you to boot a VM directly from compressed and deduplicated backups for fast
recovery during an outage. When a business-critical machine goes down, every minute of downtime has costly and
damaging consequences. With NAKIVO Backup & Replication, you can recover entire machines from their backups in
minutes. The Flash Boot feature allows you to boot machines directly from compressed and deduplicated backups
without recovering entire machines first. This feature works right out of the box without any special setup. Just choose
a backup, a recovery point, and a recovery location (a host, a resource pool, or a cluster where you want to run the
recovered machine). Then press the button and your machine is booted in no time.
Once the machine is running, you can migrate it to production for permanent recovery. Note that the backup from
which the VM is booted is not affected. Changes you make to the running VM will not modify or remove the data in
your VM backup. In addition to the VM recovery capabilities, the Flash VM Boot feature offers other useful functions.
For example, it allows you:
l Access the files, folders, and application objects of any application on any OS.
l Test system updates and application patches before applying them to your production machine.
l Verify the backup to ensure that the OS and applications run properly.
l Copy a VMDK or VHDX file, and then delete the virtual machine.
This is how the Flash VM Boot feature works:
NAKIVO Backup & Replication consists of two main components: the Director, which is the management component,
and the Transporter, which performs actual data protection and recovery tasks. By default, both components are
automatically installed to enable all features out of the box.
When you run a Flash VM Boot job, the Director creates a new VM without any disks on the target server, then
commands the Transporter to expose the machine disks from the Backup Repository as iSCSI targets. Finally, the
Director mounts the exposed disks to the newly created VM.

This process is fully automated and takes mere seconds to complete, after which the machine OS boot is started. Once
booted, the machine can be migrated to the production environment using the hypervisor’s native live migration
feature.

- 21 -
With NAKIVO Backup & Replication you can also perform Flash VM Boot to run VMware VMs directly from physical
machine backups. If a business-critical physical machine goes down, you can use Cross-Platform Flash Boot for instant
recovery without having to manually install a new OS and applications on the new machine. The machine recovered this
way can be used as a testing environment and can later be migrated for permanent use.
To learn how to create recovery jobs using the Flash VM Boot feature, refer to “Performing Flash VM Boot Recovery” on
page 606 .  

- 22 -
Universal Object Recovery
The Universal Object Recovery feature allows you to recover any object in the infrastructure – whatever the application
or file system – in a matter of minutes by mounting the appropriate backup to a VM or physical machine and then
recovering the necessary data using the native application tools.
Universal Object Recovery provides multiple recovery options, increases the flexibility of the recovery process, and
saves a significant amount of time.
l Versatility – with Universal Object Recovery, you are not limited to certain applications or file systems: you can
recover any object at any time (provided you have a recent backup). Moreover, the feature allows you to recover
individual objects back to the source, to another VM or instance, or even to a physical machine.
l Lower Overhead – Universal Object Recovery lets you restore individual objects without having to recover the
entire VM or physical machine. Thus, the feature eliminates the complexity of full machine recovery, saving you
time that can be better used for other important tasks.
l Faster Recovery – recovering an entire machine from a deduplicated and compressed backup takes time,
affecting your ability to meet your RTOs. With Universal Object Recovery, you can instantly mount disks from a
backup, decreasing recovery time and ensuring minimal interruptions in your business operations.
You can use NAKIVO Backup & Replication to recover application objects in a few simple steps: just open the Universal
Object Recovery Wizard and select the appropriate recovery point. Once you choose the disks you wish to be mounted,
NAKIVO Backup & Replication attaches said disks to the specified VM or physical machine. All you need to do after the
mount is log into the corresponding VM or physical machine and use native application tools to recover the data.

To learn how to create object recovery jobs with NAKIVO Backup & Replication, refer to the corresponding topics of the
“Granular Recovery” on page 543 section. 

- 23 -
Cross-Platform Recovery
With Cross-Platform Recovery, you can seamlessly protect VM/physical machine data across multiple platforms and
virtualized environments. You can also benefit from the following other advantages:
l Data Migration – whether a disaster renders one of your hypervisors/physical servers unavailable, or you simply
make the decision to switch to a single-platform virtualized environment, Cross-Platform Recovery can be of
help. Export your VM or physical machine backup data in the desired format, and know that you can recover on
a different platform without encountering any incompatibility issues.
l Long-Term Data Archiving – the specifics of your line of business or legislative requirements may require you to
store backups for years. With NAKIVO Backup & Replication, you can easily export and store data offsite for as
long as you need. Moreover, if your choice of virtualization software changes over time, you shouldn't have any
problems recovering from your old backups in the new environment.
l Recoverability Testing – the fact that you have a backup does not automatically mean you can recover from that
backup. Cross-Platform Recovery gives you the freedom to test different scenarios of recoverability in multiple
environments, thus helping ensure business continuity. With Cross-Platform Recovery, no disaster can catch you
off guard.
You  can export VM/physical machine data from any backup into the format of your choice in four simple steps:
1. Select a backup (VMware, Hyper-V, Nutanix AHV or physical server).
2. Choose one or multiple virtual disks that you would like to export.
3. Specify the target location and export format (VMDK, VHD, or VHDX).
4. Click a button and have the data of each selected disk exported into a separate file.

Once exported, the files can be used for recovery or long-term storage. Cross-Platform Recovery allows for unrestricted
data protection across different hypervisors, physical machines and cloud platforms. Whether one of your hypervisors
or physical machines is down or you need to migrate data from one platform to another, Cross-Platform Recovery gives
you the necessary tools for seamless cross-platform data protection and recovery.

- 24 -
Disaster Recovery
Disaster Recovery (DR) is a practice intended to support an organization's ability to remain fully operational after an
emergency event. DR serves to limit risks by getting an organization's infrastructure to run as close to normal as
possible after an abrupt intermission. NAKIVO Backup & Replication allows you to address all major DR planning points
by creating automated DR workflows for VMware, Microsoft Hyper-V, Nutanix AHV and Amazon EC2 environments. The
application allows you to protect VMs running within a cluster, replicate VMs, and fail over to replicas. 
When utilizing Site Recovery, you can include up to 200 actions to a single job, including failover, failback, start/stop
VMs and instances, run/stop jobs, run script, attach or detach repository, send email, wait, and check condition. By
arranging actions and conditions into one automated algorithm, you can create Site Recovery jobs of any complexity
level.
This section contains the following topics:
l “Replication From Backup” on page 26
l “Replication Types” on page 27
l “Site Recovery” on page 29

- 25 -
Replication From Backup
The Replication From Backup feature allows for offloading the production environment by replicating VMs directly from
backups.
Step 1 - Create a backup

Step 2 - Replicate VM from backup

Setting up a replication from backup job for VMware and Hyper-V environments is no more time-consuming than
setting up a traditional replication job. Once you launch a new replication job wizard and select VM backup as the
source, NAKIVO Backup & Replication proceeds to read the data from the repository and injects it into the replica. 
To learn how to create replication jobs with NAKIVO Backup & Replication, refer to “Replication” on page 694.

- 26 -
Replication Types
NAKIVO Backup & Replication allows you to replicate virtual machines and Amazon EC2 instances. 
l VM Replication
l Amazon EC2 Replication

VM Replication
A VM replica is an exact copy of an entire VMware, Hyper-V or Nutanix VM created on a target host. VM replication
ensures business continuity as it lets you immediately power on the replica of any failed primary VM at any time.

Replicas are stored on the target hosts in a powered-off state, and so do not consume any resources. If the source VM
has been damaged, you simply need to power the replica without NAKIVO Backup & Replication. NAKIVO Backup &
Replication provides you with the ability to add both individual VMs and all VMs within selected VMware containers
(such as resource pools, folders, hosts, clusters, etc.) to a replication job. That is to say, all your new VMs that are
created in or moved to a protected container are automatically added to your replication job. You can store up to 30
recovery points for each replica. Even if the source VM was replicated after an error, you can always revert to the last
working copy.

Amazon EC2 Replication

Amazon EC2 replication creates identical copies (i.e. replicas) of your Amazon EC2 instances as AMIs, ensuring business
continuity in case primary instances or the whole region become unavailable. NAKIVO Backup & Replication allows for
replicating instances either inside the same region or to another one.

- 27 -
In the case of same region replication, NAKIVO Backup & Replication first initiates the creation of snapshots of selected
source volumes and then creates AMIs from the source instance configuration and created snapshots. In case of cross-
region replication, NAKIVO Backup & Replication initiates the creation of snapshots of selected source volumes in the
source region. Then the product copies those snapshots to the target region and creates AMI from source instance
configuration and copied snapshots. Finally, NAKIVO Backup & Replication deletes the snapshots in the source region.
To learn how to create VMware, Hyper-V, and Amazon EC replication jobs, refer to the corresponding topics in
“Replication” on page 694.

- 28 -
Site Recovery
With Site Recovery Jobs introduced, NAKIVO Backup & Replication allows you to automate the execution of one or
more actions. An action refers to a single task that can be included in a Site Recovery Job. Refer to “Site Recovery Job
Wizard: Actions” on page 664 for the list of available actions.

Special Actions that are used in recovering your IT environment with a Site Recovery Job are Failover and Failback:
l Failover switches workloads from the primary location to a secondary recovery location. With Failover action,
you can temporarily suspend workloads on the primary location, and start them from the recovery location.
l Failback is the process of synchronizing data that has changed since Failover finished, back to the primary
location. With Failback action, you can stop workloads on the secondary location and switch them back to the
primary location.
Failover and Failback actions are applicable to replicas, and switch replica states
from Failover to Normal correspondingly. The Site Recovery Job can be executed in one of the following modes:
l Test mode is designed to verify the Site Recovery Job workflow and results. You can execute a Site Recovery Job
in the test mode on demand or on schedule. Refer to “Running Site Recovery Job in Test Mode” on page 691 for
details.
l Production mode is designed to recover the environment from a disaster. You can execute a Site Recovery Job in

- 29 -
 the production mode on demand only. Refer to “Running Site Recovery Job in Production Mode” on
page 692 for details.
When the Site Recovery Job is run in the production mode, Failover may be either of the following types:
l Planned failover is designed to achieve zero data loss when disaster happens. The application will sync replica
data with the source VM before switching workloads to the replica.
l Emergency failover is designed to minimize downtime. The application will switch workloads from the source VM
to the replica immediately.
The topic includes the following sections:
l Workflow of Site Recovery Job
l Cleanup of Site Recovery Job Testing

Workflow of Site Recovery Job

If your Site Recovery Job contains a Failover action, the action will be executed as follows:
l Site Recovery Job is executed in production mode as Emergency Failover is being carried out:
1. Replication from the source VM to the replica will be disabled.
2. The replica will be rolled back to a specified recovery point (optional, as the latest recovery point is used by
default).
3. The replica will be connected to a new network (optional).
4. The static IP address of the replica will be modified (optional).
5. The source VM will be powered off (optional).
6. The replica will be powered on.
7. The replica will be switched to the Failover state.
l Site Recovery Job is executed in production mode as Planned Failover is being carried out:
1. Replication from the source VM to the replica will be disabled.
2. An incremental replication from the source VM to the replica will be run once.
3. The source VM will be powered off.
4. An incremental replication from the source VM to the replica will be run once more.
5. The replica will be connected to a new network (optional).
6. The static IP address of the replica will be modified (optional).
7. The replica will be powered on.
8. The replica will be switched to the Failover state.
l Site Recovery Job is executed in test mode:
1. Replication from the source VM to the replica will be disabled.
2. An incremental replication from the source VM to the replica will be run once.
3. The replica will be connected to an isolated network (optional).
4. The static IP address of the replica will be modified (optional).

- 30 -
 5. The replica will be powered on.
6. The replica will be switched to the Failover state.
If your Site Recovery Job contains a Failback action, the action will be executed as follows:
l Site Recovery Job is executed in the production mode:
1. The source VM will be powered off (if it exists and is powered on).
2. A protective snapshot of the source VM will be created.
3. An incremental or full replication from the replica to the source VM will be run once.
4. The replica will be powered off (optional).
5. An incremental replication from replica to the source VM will be run once more.
6. The source VM will be connected to a new network (optional).
7. The static IP address of the source VM will be modified (optional).
8. The source VM will be powered on.
l Site Recovery Job is executed in test mode:
1. The source VM will be powered off (if it exists and is powered on).
2. A protective snapshot of the source VM will be created.
3. An incremental or full replication from replica to the source VM will be run once.
4. The source VM will be connected to an isolated network (optional).
5. The static IP address of the source VM will be modified (optional).
6. The source VM will be powered on.

Cleanup of Site Recovery Job Testing

After executing a Site Recovery Job in test mode, the cleanup will be carried out as follows:
1. VMs that have been powered on during the Site Recovery Job testing will be powered off, and vice versa.
2. Repositories that have been attached during the Site Recovery Job testing will be detached, and vice versa.
3. Jobs that have been enabled during the Site Recovery Job testing will be disabled, and vice versa.
4. If the Failover action was part of the Site Recovery Job testing:
a. The replica will be powered off.
b. The replica will be reverted to the pre-Failover state via the snapshot.
c. The replica will be switched to the Normal state.
d. Replication from the source VM to the replica will be enabled.
5. If the Failback action was part of the Site Recovery Job testing:
a. The source VM will be removed (if it did not exist before the Site Recovery Job testing), or else:
b. The source VM will be reverted to the protective snapshot.
c. The source VM will be powered on (if it exists and was powered off).
d. The protective snapshot will be removed from the source VM.

- 31 -
Backup Size Reduction
NAKIVO Backup & Replication utilizes multiple methods, such as deduplication and compression, to optimize the size of
stored backups. The main purpose of these methods is to reach the correct balance between the amount of data read
and transferred during backup.
This section contains the following topics:
l “Global Data Deduplication and Compression” on page 33
l “Skipping Swap Files and Partitions” on page 34
l “Skipping Unused Blocks” on page 35

- 32 -
Global Data Deduplication and Compression
Backup deduplication is a method for reducing backup size by excluding duplicate data blocks from the backup. In any
given organization, VMs contain duplicates of data, such as VMs deployed from the same template, VMs with the same
OS, and VMs that have some (semi) identical files, such as database entries. Block-level data deduplication enables you
to reduce backup size by saving only unique data blocks to the Backup Repository while replacing duplicated blocks
with references to existing ones.

NAKIVO Backup & Replication automatically deduplicates all backups across an entire Backup Repository. This means
that all data blocks are taken into account by backup deduplication, even if you back up your VMware VMs, Hyper-V
VMs, and Amazon EC2 instances to the same backup repository. While backup deduplication is turned on by default,
you can disable it if, for example, you want to use a hardware-based data deduplication device such as an EMC Data
Domain.
VM backup deduplication can provide a 10X to 30X reduction in storage capacity requirements. For example, you have
10 VMs running Windows Server 2016, which occupies 10 GB each. While the total amount of data is 100 GB, only one
copy of OS data (10 GB) will be written to a backup repository with data deduplication, which provides 10 to 1 storage
space savings.
More efficient disk space utilization allows for storing more recovery points per VM backup. In addition, lower storage
space requirements save money on direct storage costs (as fewer disks are needed to store the same amount of
information) and on related costs (such as cooling, electricity, and maintenance).

- 33 -
Skipping Swap Files and Partitions
Swap files on Windows OS and swap partitions on Linux OS serve as “virtual memory” and store temporary runtime
data that is not in use by RAM. Swap files and partitions improve OS performance: Once the physical memory is full, the
OS can send less frequently used data to a swap file/partition and use the freed-up physical memory to perform high
priority tasks. While this approach is great for OS and application performance, it has a negative effect on VM backup
and replication.
The contents of the swap file change constantly, so each time you run a VM backup or VM replication, the swap
file/partition is included in the backup/replica. Since the swap file can automatically grow up to 3x the size of RAM,
gigabytes of unnecessary data are processed, transferred and stored each time you back up a VM. The impact of swap
files and partitions on backup and replication is significant even in small environments. For example, if you run a backup
for 10 VMs and each VM has just 2 GB of swap data, you will transfer and store: 10 VMs x 2 GB x 22 working days = 440
GB of useless data in one month alone. 
NAKIVO Backup & Replication automatically skips swap files and partitions in VMware VMs, Hyper-V VMs, and Amazon
EC2 instances, which results in faster and smaller backups and replicas. Note that the application-aware mode instructs
applications and databases running inside VMs to flush their data from memory to disk, which means that all important
data will be included in your VM backups and replicas. This option can be enabled on a per-job basis.

- 34 -
Skipping Unused Blocks
In addition to skipping swap files and partitions, NAKIVO Backup & Replication allows you to skip unused disk blocks
during the backup or replication process. This includes the following fragments within the file system:
l Never used volume area.
l File area used by deleted files (without hard reference).
Enabling this option reduces the size of backups and replicas, ensuring that only relevant data is copied. Skipping these
blocks of data also means that less processing power and time are required for the workflow to finish.
This option can be configured on a per-job basis on the Options page of backup and replication jobs and is enabled by
default. The feature supports processing source objects running on Windows OS. It is available for the NTFS file system.

- 35 -
Reliability
NAKIVO Backup & Replication employs various techniques to ensure that data is stored, transferred and recovered
correctly and consistently.
This section contains the following topics:
l “Application and Database Support” on page 37
l “Encryption in Flight and at Rest” on page 38
l “Log Truncation” on page 40
l “Self-Backup Feature” on page 42
l “VM Verification” on page 43

- 36 -
Application and Database Support
When you back up a VM that runs Active Directory, Microsoft SQL Server, Microsoft Exchange, or any other application
or database, it is crucial to ensure that all data inside of those applications remain consistent in the backup. This is
important because portions of data and some transactions kept in memory may be incomplete when the VM backup is
made. If you take no actions to flush memory and I/O operations, the backups will be crash-consistent. It is similar to
pulling the plug on a physical server and then powering it back on. Therefore, most modern applications and databases
offer ways to recover from this state. However, in most cases you'll still need to spend some time on manual restore
operations and run the risk of losing important data.
To ensure that all data is consistent in the backups, NAKIVO Backup & Replication allows you to use the application
awareness feature which is called app-aware mode. To perform consistent backups and replicas of Windows-based
environments, the product relies on the Microsoft Volume Shadow Copy (VSS) service running inside VMs. If your
application is not VSS-aware or runs on Linux, it provides you with the ability to run custom pre-freeze and post-thaw
scripts to enable application-consistent VM backup and replication. A pre-freeze script is executed before a snapshot of
a VM is taken, and post-thaw script is executed after the snapshot has been taken.
With the app-aware mode turned on, your backups and replicas will contain consistent application and database data,
so you won't need to take any extra configuration steps. As a result, you will be able to instantly recover not only
full VMs, but also Microsoft Exchange and Active Directory objects, such as emails or users, directly from a compressed
and deduplicated backup.  If app-aware mode is disabled, NAKIVO Backup & Replication will create normal (standard)
snapshots of source volumes instead of quiesced ones. In case of failure, the product will copy data directly from source
volumes without displaying an error.
The app-aware mode can be enabled/disabled on the Options page of the backup and replication job wizard of all
supported platforms. 

- 37 -
Encryption in Flight and at Rest
VM backup encryption uses a mathematical algorithm that transforms source information into a non-readable cipher
text. The goal of VM backup encryption is to make your data unintelligible to unauthorized readers and impossible to
decipher when attacked. VM backups that are sent over the Internet should be encrypted before the first bit leaves
your organization and travels over the WAN (backup encryption in flight). If the destination is not secure, your data
should remain encrypted as well (backup encryption at rest).

NAKIVO Backup & Replication uses AES 256 encryption to protect VM backups, which is the de facto worldwide
encryption standard that secures online information and transactions by financial institutions, banks, and e-commerce
sites.
l VM Backup Encryption in Flight
l VM Backup Encryption at Rest

VM Backup Encryption in Flight

VM backup encryption in flight is performed by a pair of Transporters. The Transporter is a component of NAKIVO
Backup & Replication that performs all data protection and recovery tasks: data read, compression, deduplication,
encryption, transfer, write, verification, granular and full VM recovery, and so on.
The source Transporter for the offsite backup encrypts and sends the encrypted data. The target Transporter receives
and decrypts data. For example, when you back up VMs over the WAN to an offsite location, the Transporter installed in
the source site compresses and encrypts VM data before transferring it over WAN. Then, the Transporter installed in the
Target site receives and unencrypts the data prior to writing it to the Backup Repository.

VM Backup Encryption at Rest

It is equally important for the data at rest to be secured by encryption. NAKIVO Backup and Replication provides you
with the ability to encrypt Backup Repositories so that backup data at rest, housed in the repository itself, is secure.
You can set up encryption on the Options page of the repository creation wizard. For details, refer to the following
topics:
l “Local Backup Repository” on page 366
l “Backup Repository on CIFS Share” on page 370

- 38 -
l “Backup Repository on NFS Share” on page 375
l “Backup Repository in Amazon EC2” on page 380
l “Backup Repository on Deduplication Appliance” on page 391

- 39 -
Log Truncation
With NAKIVO Backup & Replication, you can remove (truncate) transaction log files of Microsoft Exchange and
Microsoft SQL servers which will allow you to reduce the size of backups and, as a result, to optimize the use of storage
space. Log truncation can be enabled on the Options page of backup and replication jobs. 
l Microsoft Exchange Server Log Truncation
l Microsoft SQL Server Log Truncation

Microsoft Exchange Log Truncation

Microsoft Exchange is the industry's leading platform for email, calendaring, and messaging services. To protect data
from undesired deletion or modification, each change that is made to a Microsoft Exchange server database is recorded
in transaction logs. These logs can be replayed to recover data that was removed or changed in the database. While this
approach improves data protection, it has a downside. Since the Microsoft Exchange database is constantly changing
(as data is written and removed in the database), transaction logs grow over time. If not periodically removed, they will
eventually fill up the disk and may crash the entire server.
NAKIVO Backup & Replication can create consistent backups of VMware and Hyper-V VMs as well as remove transaction
log files of Microsoft Exchange 2016, 2013, 2010, and 2007 servers. After creating a successful backup, NAKIVO Backup &
Replication connects to your Microsoft Exchange server, identifies which transaction log files have already been written
to the database and removes or truncates those log files.

As a result, NAKIVO Backup & Replication creates regular, application-consistent backups of your Microsoft Exchange
server and also removes the transaction log files so they don't consume all free disk space on the server.

- 40 -
Microsoft SQL Server Log Truncation
Any Microsoft SQL server tracks all database transactions (modifications) completed by the server and records them to
the transaction logs. Transaction log files (identified with the .ldf extension) are very important, as they are used to
ensure database integrity and allow restoring data by replaying the changes. However, these files grow over time and
can eventually fill all the free space. This may result in the Microsoft SQL Server crash, or loss of valuable data. That is
where Transaction Log Truncation might help.
On one hand, you need to keep the transaction logs, so you can recover Microsoft SQL Server data in case any data
deletion, undesired modification, or corruption occurs. On the other hand, you need to remove transaction logs to
save space, but without any transaction records you will be unable to successfully recover, should any unpredictable
situation occur.
The best practice is to first back up the whole VMware or Hyper-V VM running Microsoft SQL Server and all log files
stored therein, and then delete or truncate those files on the source VM freeing up the storage space.
NAKIVO Backup & Replication supports transaction log truncation for Microsoft SQL Server 2008 and later. The product
follows the best practice of performing the log truncation process while ensuring ease of use and simplicity. NAKIVO
Backup & Replication can automatically truncate transaction log files after successful VM backup and replication. All you
need to do is just set it and forget it.
To free up the VM storage space, NAKIVO Backup & Replication performs the following operations:
l Backs up/replicates the entire VMware or Hyper-V VM running Microsoft SQL Server.
l After completing a successful backup/replication, identifies Microsoft SQL Server transaction log files, which were
already committed to the database.
l Truncates (deletes) the committed transaction log files on the source VM, thus freeing up storage space.
Consequently, you get a VM backup/replica with all transaction log files. Even though the backed up log files can be
pretty large, NAKIVO Backup & Replication easily reduces the size of the VM backup by using backup deduplication and
compression features. In its turn, the original VM is left logs-free and can be recovered at a certain recovery point using
the aforementioned VM backup/replica, should something go wrong.

- 41 -
Self-Backup Feature
The Self-Backup feature provides automated protection of everything you have configured in NAKIVO Backup &
Replication.
A truly complete data protection solution needs to back up not only your VMs, but also itself. There are good reasons
for that. For example, the VM running the product may become corrupted, struck by a virus attack, or accidentally
deleted. Regardless of the cause, you will need to restore the disrupted product as quickly as possible. Fortunately, a
new instance of NAKIVO Backup & Replication can be installed in less than one minute. However, you will still need to
restore the product configuration (such as jobs). Also, you do not want to lose the backup history. To save you time,
NAKIVO Backup & Replication automatically backs up the entire configuration, including all jobs, inventory, information
about connected Transporters, Backup Repositories and other.
The Self-Backup feature is enabled by default, and NAKIVO Backup & Replication sends daily self-backups to the first five
backup repositories available in the product. Each self-backup is kept for five days, by default. Should you like to, you
can fine-tune the backup targets, schedule, and retention policy.

If you accidentally make some undesired changes in the product, you can easily roll back to a previous system state
from the backup. Migrating the system configuration to a new product instance is simple: just install a new copy of
NAKIVO Backup & Replication, import a Backup Repository that contains a self-backup, and select a recovery point. The
previous product configuration is restored along with all settings.
The Self-Backup feature saves you time and brings you peace of mind, ensuring reliable protection of everything you
configure in NAKIVO Backup & Replication.
For information on the Self-Backup configuration, refer to “Self-Backup Configuration” on page 292.

- 42 -
VM Verification
VM verification is a process of checking the integrity of a backup or replica by booting a VM from a backup or starting a
replica and interacting with it. With the VM verification feature, you have proof that your VM backups or replicas are
usable, and can rest assured that your VMs can be recovered in case of disaster. VM backups and replicas can be
corrupted or not bootable, even if the data protection software performed properly. The worst time to find out that
your backup is bad is when your VM is down. If you don't have backup copies or VM replicas at an offsite location, you
are left without any viable means of quickly restoring business processes.
VM verification involves the following entities:
l Source Object: Backup recovery point or replica recovery point which is used as a source of data for VM
verification.
l Target Object: An entity that is subject to VM verification. It can be a replica or a temporary VM created via Flash
VM Boot.
l Guest OS Agent: An entity in the target object which allows remote interaction with the guest OS of this object
(VMware Tools for VMware vSphere; Hyper-V integration services for Microsoft Hyper-V). Guest OS agent is
required to be installed on the target object in order to perform VM verification.
There are two VM verification methods:
l Boot Verification: Verifying the target VM via starting target VM and checking whether hypervisor tools are
running.
l Screenshot Verification: Verifying the target VM via starting the target VM and taking a screenshot of the VM
screen.
To verify VMware and Hyper-V backups, NAKIVO Backup & Replication relies on the Flash VM Boot feature. After a VM
backup job has completed the data transfer, the product performs the following actions:
1. Instantly runs the VM from the newly created backup (with networking turned off).
2. Waits until the OS has booted.
3. Checks if guest OS agents are run successfully (if Boot Verification is selected).
4. Makes a screenshot of a running VM (If Screenshot Verification is selected).
5. Discards the test-recovered VM.
You can view the results of the verification procedure in the Dashboard or choose to receive an email report. VM
verification, being an option for the jobs listed below, can be run on demand or scheduled to run automatically, saving
you time and effort. VM verification option is available for the following jobs:
l VMware VM Backup Job
l VMware VM Replication Job
l VMware Flash VM Boot Job
l Backup Copy Job

- 43 -
Performance
A backup process can handle a huge amount of data, thus it is imperative to ensure that the data flow is efficient, and
every resource used in the backup process is optimized. NAKIVO Backup & Replication provides the following
techniques to increase performance:
l “Advanced Bandwidth Throttling” on page 45
l “Deduplication Appliance Support” on page 52
l “Full Synthetic Data Storage” on page 54
l “Incremental Jobs” on page 56
l “Jobs and Concurrent Tasks” on page 57
l “LAN-Free Data Transfer” on page 58
l “Network Acceleration” on page 61

- 44 -
Advanced Bandwidth Throttling
NAKIVO Backup & Replication was designed to transfer data at the maximum available speeds for the purposes of
completing VM backup, replication, and recovery jobs as quickly as possible. However, if you run data protection jobs
during business hours, your LAN or WAN networks risk being overloaded. This can affect the performance of
applications and degrade user experience (think of email messages taking too long to be sent, excessive load times for
websites, etc.). NAKIVO Backup & Replication addresses this issue with the flexible Advanced Bandwidth Throttling
feature. With Advanced Bandwidth Throttling, you can set limits for your data protection jobs and make sure they
don't take more bandwidth than you can afford to allocate.
Advanced Bandwidth Throttling allows you to set global rules that limit the data transfer speeds of your backup
processes. Such rules can apply to different jobs and on different schedules. For instance, you can create a global rule
preventing your backup jobs from consuming more than 50 MByte/s during business hours, but leave the bandwidth
unrestricted for Sunday backups. You can also create bandwidth throttling rules on a per-job basis, if you want to have
more granular control over the whole process. Individual limits override global rules, sparing you the need to adjust the
global rule for every job.
The Advanced Bandwidth Throttling feature of NAKIVO Backup & Replication is an effective means of optimizing backup
operations and controlling your network traffic. With global and individual limits on data transfer speeds, the feature
can help you ensure the performance of your business applications is never affected by backup workloads – even if you
have little bandwidth to spare. With bandwidth rules, usage of LAN/WAN bandwidth by NAKIVO Backup & Replication
jobs may be restricted to a specific amount. For more information, refer to the following sections:
l About Bandwidth Rules

l Distributing Bandwidth Between Tasks

About Bandwidth Rules

A bandwidth rule specifies the bandwidth amount that can be used by one job, by multiple jobs, or by all applicable
jobs.
A bandwidth rule can be:
l Global Rule – a bandwidth rule applied to all applicable Jobs.
l Per Job Rule – a bandwidth rule only applied to specific Jobs.
Per Job rules have higher priority than Global Rules. A per job rule will be applied to the job when both the per job rule
and a global rule are active for the same job. In case multiple per job rules are active for the same job, the bandwidth
rule with the lowest bandwidth amount will be applied. In case there are multiple global rules – and no per job
bandwidth rules,– the global rule with the lowest bandwidth amount will be applied. When a NAKIVO Backup &
Replication job is running and a bandwidth rule is applied to this job, the job will get bandwidth amount that is allowed
by the bandwidth rule (for example 10 Mbit/s).

- 45 -
When a NAKIVO Backup & Replication job is running with a bandwidth rule applied and the bandwidth rule becomes
disabled for this job – and there are no other bandwidth rules applied to the job,– the job will get unlimited bandwidth.

Bandwidth rules may be always active, active on schedule, or disabled. Refer to “Bandwidth Throttling” on page 283 for
details.
When a job containing multiple VMs starts running with a bandwidth rule active, the rule divides bandwidth between
tasks. Incremental backup tasks receive significantly less bandwidth than full backup tasks; this ensures that no tasks
receive too little bandwidth to be processed in a reasonable time. When the Transporter is ready and there is enough
unallocated bandwidth, the tasks start to be processed. Any change to the bandwidth amount will only be applied to
the tasks not yet started for processing. Once started for processing, the tasks do not change the consumed bandwidth
amount. It means there will be no dynamic change in the bandwidth amount for the tasks already being processed.
Bandwidth rules are applicable to the following types of NAKIVO Backup & Replication jobs:
l Backup Job
l Backup Copy Job
l Replication Job
l Recovery Job
l Failover Job

Distributing Bandwidth Between Tasks

To illustrate distribution of bandwidth between tasks, one can take a backup job – Job A,– of 5 VMs; the 3rd VM backup
is a full backup and the rest are incremental backups.
Job A starts running with the 30 Mbit/s bandwidth rule activated  as follows:

- 46 -
1. The bandwidth amount is split into 3 chunks 10 Mbit/s each.

2. VM 1 and VM 2 backups receive 10 Mbit/s each. One bandwidth chunk remains unassigned since the full
backup usually requires all the bandwidth to start.
3. The remaining bandwidth is distributed from the start of the queue, so VM 1 backup receives additional 10
Mbit/s.
4. VM 1 backup and VM 2 backup start running.

Note
The Transporter can process a limited number of concurrent tasks.
5. When VM 1 backup finishes execution, it frees two bandwidth chunks 10 Mbit/s each. However, VM 3 full backup
still cannot start because it requires all the available bandwidth to start running. Hence, these two bandwidth
chunks are left idle.

- 47 -
6. When VM 2 backup finishes running, it frees another bandwidth chunk, and full backup of VM 3 starts running
with all the bandwidth assigned.

7. When full backup of VM 3 is finished, three bandwidth chunks are now available for the two remaining VM
backups.
8. VM 4 backup receives the 20 Mbit/s bandwidth in total and VM 5 backup receives a 10 Mbit/s bandwidth chunk.

- 48 -
When the rule changes the bandwidth to 80 Mbit/s and is also activated for another Job B consisting of two VM
incremental backups, the Transporter starts distributing bandwidth as follows:
1. The 80 Mbit/s amount is split into 4 chunks of 20 Mbit/s.

2. VM 6 backup and VM 7 backup of Job B receive a 20 Mbit/s bandwidth chunk each and start running, with 10
Mbit/s remaining unassigned.

- 49 -
 3. When VM 4 backup and VM 5 backup of Job A are finished, two 20 Mbit/s bandwidth chunks are freed. However
there are no queued tasks to assign them to, so the bandwidth is left idle.

When the bandwidth rule changes the bandwidth amount back to 30 Mbit/s and is also activated for another Job C
consisting of one VM incremental backup, the Transporter starts distributing bandwidth as follows:
1. The 30 Mbit/s amount is split into three chunks of 10 Mbit/s.
2. The currently running tasks occupy 40 Mbit/s of bandwidth, which is three 10 Mbit/s bandwidth chunks and one
10 Mbit/s bandwidth chunk over the limit. Therefore, there is no free bandwidth for VM 8 backup of Job C to use.

Note
Jobs and tasks may wait for a long time until bandwidth is available for them to start.
3. When VM 6 backup is finished, freeing up 20 Mbit/s of bandwidth, of which 10 Mbit/s was exceeding the 30

- 50 -
Mbit/s limit, VM 8 backup of Job C starts executing using another 10 Mbit/s bandwidth chunk.

- 51 -
Deduplication Appliance Support
Deduplication appliances are solutions that implement specialized data reduction techniques to eliminate duplicate
copies of repeated data. Deduplication appliances are leveraged across a range of data protection solutions, regardless
of whether network-attached storage, disk, and/or tape is used. The biggest advantage of deduplication appliances is
their ability to reduce datastore space used – sometimes by ratios of 20:1 or more. 
NAKIVO Backup & Replication supports integration with deduplication appliances. For details, refer to the following
sections:
l NAKIVO Optimization for Deduplication Appliances

l Deduplication Appliance Configuration Details

NAKIVO Optimization for Deduplication Appliances

NAKIVO Backup & Replication provides a special type of Backup Repository (stream repository) optimized for high
performance with deduplication appliances. With this type of Backup Repository, NAKIVO Backup & Replication
supports virtually any type of deduplication appliance as a primary or a secondary backup destination. The architecture
of such Backup Repository is based on sequential block write operations through a restricted number of data streams
and storing backup blocks in dedicated data files. Data blocks are stored in incremental backup files and full backup
files. This means that the repository stores VM backup chains consisting of periodic full backups and several increments
between these full backups.

In terms of integration with deduplication appliances, a stream repository:

l Creates fewer data streams in read/write operations during VM backup and recovery;
l Does not leverage the global data deduplication feature of NAKIVO Backup & Replication.

- 52 -
Deduplication Appliance Configuration Details
When a Backup Repository is created on a deduplication appliance, NAKIVO's built-in data deduplication functionality is
disabled. Additionally, the incremental-with-full-backups option is enabled by default. This configuration ensures that
no extra resources are spent for double deduplication and reclaiming repository space is not required.

- 53 -
Full Synthetic Data Storage
With forever incremental Backup Repositories, NAKIVO Backup & Replication uses the full synthetic mode to store
backups: all unique data blocks are stored in a single pool, while recovery points serve as references to the data
blocks that are required to reconstruct a machine at a particular moment in time. 
Example
You run the first backup of a VM on Sunday. For the sake of simplicity, let's say that the VM consists only of 2 data
blocks: A and B. Then on Monday, you run an incremental backup, which finds that the block A has been deleted, but a
new block C has been added. Then on Tuesday, the incremental backup finds that the block B has been deleted and a
new block D has been added. Here's how the VM would look like during the three days:

And here's how the data will be stored in the forever incremental Backup Repository if the job is set to keep 3 or more
recovery points:

- 54 -
As you can see from above, each unique data block is stored only once to save space, while recovery points are just
references to data blocks that are required to reconstruct the VM as of a particular moment in time. If, for example, you
delete Monday's recovery point, then no actual data removal will occur, as its data blocks (B and C) are required for
recovery points of Sunday and Tuesday. If, on the other hand, you change the recovery point retention policy to keep
only the last two recovery points (Mon and Tues in our case), then only block A will be deleted, as it's not being used
anywhere else. 
The full synthetic data storage approach provides a number of benefits:
l Smaller backups: Unique data blocks are stored only once and can be referenced by multiple recovery points, as
opposed to storing the same data again in different increments.
l Faster backups: There is no need to run full backups periodically or transform legacy increments into virtual full
backups, as each recovery point already "knows" which data blocks should be used to reconstruct an entire
machine. 
l Safer backups: With a legacy incremental backup approach, losing one increment in a chain means losing the
entire chain of recovery points after that increment. With NAKIVO Backup & Replication losing a data block or an
increment (such as A or B in the example above) can still leave you with recoverable increments. 
l Faster recovery: A legacy incremental backup consists of a chain of increments that you must apply one by one
in order to get to a particular machine state. With NAKIVO Backup & Replication, each recovery point already
"knows" which data blocks should be used to reconstruct an entire machine.

- 55 -
Incremental Jobs
NAKIVO Backup & Replication allows you to create in incremental backup and replication jobs. For more information
refer to:
l Backup Jobs
l Replication Jobs

Backup Jobs
l When a forever incremental Backup Repository is utilized as a destination, the full backup will be performed only
on the first backup job run. All consequent job runs will send only changed data (increments) to the Backup
Repository. This approach reduces backup time and network load. For example, if NAKIVO Backup & Replication
determines that the amount of data that has been changed on a 100 GB VM is just 1 MB, only 1 MB of data will
be transferred to the Backup Repository, but the created recovery point will reference all data blocks (from
previous job runs) which are required to restore the entire 100 GB VM. With this approach, each recovery point
"knows" all data blocks that are needed for recovery, so there is no need to apply increments one by one to get
to a particular point or periodically transform backed up data blocks.
l When an incremental with full backups  Backup Repository is utilized as a destination, NAKIVO Backup &
Replication performs a full backup on the first backup job run. Consequently, NAKIVO Backup & Replication runs
incremental backups and periodically creates full backups according to the specified settings. Every VM backed
up to said Backup Repository will produce full backup files and incremental backup files.

Replication Jobs
Replication jobs in NAKIVO Backup & Replication are forever incremental. This means that after the initial full replication,
all subsequent job runs will send only changed data (increments) to the replica. This approach reduces the replication
time and network load. For example, if NAKIVO Backup & Replication determines that the amount of changed data on a
100 GB VM constitutes just 1 MB, only 1 MB of data will be transferred to the replica VM.

- 56 -
Jobs and Concurrent Tasks
Job is a data protection activity that is performed by NAKIVO Backup & Replication in accordance with a distinct
configuration. These are the main types of NAKIVO Backup & Replication jobs:
l Backup jobs
l Replication jobs
l Recovery Jobs
In NAKIVO Backup & Replication, a job can have one or more job objects to process. Depending on your preferences,
job objects may be reordered for processing within a job. See the example below.

Each job object may consist of one or more machine disks, Oracle databases, Exchange Online mailboxes, OneDrive for
Business instances or SharePoint Online sites that have to be processed within a job run. Data processing that is related
to a specific VM disk or service constitutes a single task, in the scope of the corresponding job. Such tasks are processed
by a Transporter. For the sake of managing the load over the infrastructure, any Transporter is configured to process a
limited number of concurrent tasks. When a task is processed, the Transporter starts processing another task if
available. A task can be one disk, file or recovery session, Oracle database, Exchange Online mailbox, OneDrive instance,
or a SharePoint Online site. By default, NAKIVO Backup & Replication is set to process 6 concurrent tasks per one
Transporter. Refer to “Editing Transporters” on page 342 to learn how to change the Transporter maximum load.

- 57 -
LAN-Free Data Transfer
NAKIVO Backup & Replication automatically uses a LAN-free data transfer mode for VMware backup, Hyper-V backup,
Nutanix AHV backup, VMware replication, and Hyper-V replication. The LAN-free data transfer mode boosts VM backup
and replication speed in addition to reducing the load on your network.
On the VMware platform, this is achieved with the Hot Add and Direct SAN Access features.
l “Direct SAN Access for VMware” on page 59
l “Hot Add for VMware” on page 60

- 58 -
Direct SAN Access for VMware
If your VMs are located on a Fiber Channel or iSCSI Storage Area Network (SAN) device, NAKIVO Backup & Replication
can use direct SAN access for data retrieval. Using this storage access mode can significantly increase the speed of
backup and replication while decreasing the load on your production network.

NAKIVO Backup & Replication relies on the VMware VDDK library that provides SAN support and does not make any
write/modification operations on the SAN LUNs. That is to say, the product will not compromise data integrity or
interfere with the data of running VMs on your SAN datastores.
For information about Transporter deployment requirements as well as recommendations on setting up the SAN
access, refer to Transporter Deployment for SAN Access.

- 59 -
Hot Add for VMware
The Hot Add Data Transfer mode significantly improves VM backup and replication speed and reduces the load on the
network. NAKIVO Backup & Replication can read data directly from VM datastores, bypassing the host's TCP/IP stack
that would otherwise impact every VM on the host, and slow down the data transfer. NAKIVO Backup & Replication can
mount (Hot Add) VM snapshots, and read VM data directly from VM datastores through the host's storage I/O stack.

By default, NAKIVO Backup & Replication will automatically attempt to use the Hot Add mode for VM backup and
replication jobs. Please check the appropriate feature requirements section for prerequisites and limitations. 

- 60 -
Network Acceleration
Whether you run VM backup and replication jobs during business hours or send VM backups and replicas offsite over
the Internet, saving network bandwidth is of the essence. NAKIVO Backup & Replication provides the Network
Acceleration feature to speed up VM backup and replication jobs, shorten backup windows, and reduce network load
at the same time. With network acceleration enabled, you can increase VM backup, replication, and recovery speed by
2X in WAN and busy LAN networks.
Network acceleration is achieved by the use of two instances of Transporter. Transporter is the product component
that performs all data protection and recovery tasks, such as backup, replication, recovery, encryption, and so on. To
simplify deployment and configuration, one instance of Transporter is automatically installed with NAKIVO Backup &
Replication
To enable Network Acceleration, you just need to install another Transporter instance locally or offsite and then enable
Network acceleration in your job. When the job is executed, the source Transporter will read the data, compress and
optimize it, and then send the data to the target Transporter. By using Network Acceleration, you can reduce the
amount of data that is transferred over the network, which also means that your jobs will complete faster.
Network Acceleration for Backup

Network Acceleration for Replication

- 61 -
Administration
NAKIVO Backup & Replication strives to make the user experience as intuitive and easy-to-use as possible, and provides
users with the following features:
l “Calendar” on page 63
l “Global Search” on page 64
l “Policy-Based Data Protection” on page 65

- 62 -
Calendar
Backing up VMs is a resource-intensive process, which places extra load on your infrastructure, be it VMware, Hyper-V,
or AWS. This is particularly noticeable when it comes to large environments with thousands of VMs. Too many backup
jobs running concurrently on the same host or on the same network may affect the performance of your virtual
environment and slow down your VMs. To reduce the load on your resources, you need to carefully schedule and
structure your backup jobs, to ensure the shortest backup windows possible.
Scheduling data protection jobs may be tricky in large virtual environments, where you need to fit multiple jobs into a
backup window and avoid possible overlaps. To resolve this issue, NAKIVO Backup & Replication features the Calendar
dashboard, which is aimed at greatly improving job scheduling. The Calendar dashboard displays all your jobs in the
calendar view, the time it took different jobs to run in the past, and the predicted job duration in the future. Here you
can get a bird's eye view of all your jobs, and you can easily find open time slots for new jobs, which you can create right
in the dashboard. You can also visit past jobs to view the status and details of the jobs that have been completed and
drill down to their details. The Calendar dashboard has an intuitive interface and navigation, similar to those of the
most popular calendar applications.

- 63 -
Global Search
NAKIVO Backup & Replication includes the powerful global search feature that allows you to find any item quickly by
entering the name of the item (or part of the name) into the search box. You can refine the search results by using filters
(for example, choose to view only VM backups). In addition, you can select items in the search results and instantly
perform mass actions on them, such as creating a new job for unprotected VMs or adding items to an existing job. The
ability to perform such actions simplifies the management of your backup infrastructure.
With the global search feature, you can:
l Search: Instantly search for VMs, backups, replicas, jobs, groups, Backup Repositories, Transporters, tape
cartridges, and tape devices.
l Filter: Choose to view a subset of results – for example, unprotected VMs only.
l Get information: View item details, such as size, host, datastores, networks, and protection status.
l Act: After finding what you were looking for, you can take an action – add multiple unprotected VMs to a job,
start a recovery, run a job, etc.
The global search feature in NAKIVO Backup & Replication is an easy-to-use tool that helps you manage large backup
infrastructures and saves you time.

- 64 -
Policy-Based Data Protection
Policy-Based Data Protection relieves you of the need to chase new VMs or changes in your infrastructure. Once a policy
is created, all the matching VMs are protected automatically. Whenever a VM's status changes, the policy recognizes
this change and excludes or adds the VM to jobs accordingly. The feature is designed to reduce complexity and add
more flexibility to data protection processes such as backup, replication, or backup copy. You can set rules based on the
VM name, tag, size, location, VM configuration, power state, or any combination of these parameters. A newly-created
VM or instance is automatically added to data protection jobs if they match your policy rules; you don't have to keep
track of all the changes in your infrastructure or manually manage data protection for new VMs. You can add as many
new VMs and instances as you need because NAKIVO Backup & Replication can automatically protect all of them for
you, as long as you have policy-based jobs in place.
This functionality can be a great time-saver if your virtualized infrastructure is actively expanding, includes numerous
VMs and instances, or has a complex multilayer architecture. The Policy-Based Data Protection feature contributes
greatly to the overall usability of NAKIVO Backup & Replication, making it an even more efficient data protection
tool. Policies can be created for VM backup, replication, and backup copy jobs in just a few steps. Simply select the
criteria (e.g., a VM's name, size, tag, etc.), enter the necessary search parameters, and have all the matching items
included in the job automatically. For instance, you can choose to back up all VMware VMs tagged "Accounting" which
exceed 100 GB in size and have more than 2 GB of allocated RAM. Once the policy has been created, NAKIVO Backup &
Replication recognizes newly added VMs or instances with the same characteristics and automatically includes them
into the existing job.
Refer to the following topics to know how to use the feature:
l “Managing Job Policies” on page 108
l “Managing Policy Rules” on page 110

- 65 -
Automation
The following features help users eliminate repetitive routine work and automate their activities:
l “HTTP APIs” on page 67
l “Job Chaining” on page 68
l “Pre and Post Job Scripts” on page 69

- 66 -
HTTP APIs
NAKIVO Backup & Replication provides a simple HTTP API that lets you automate and orchestrate VM backup,
replication, and recovery tasks. The API provides complete coverage of the product features, that is, you can use the
API to perform all tasks that are available in the product's Web interface.

The API allows you to easily integrate NAKIVO Backup & Replication with monitoring, automation, and orchestration
solutions to reduce time spent on backup management and reduce data protection costs. To speed up integration
time, the API comes as part of an Integration Kit, which includes API documentation and code examples.
By using the API, you can:
l Save time on backup administration by automating the data protection process from VM provisioning to VM
decommissioning.
l Ensure an uninterrupted backup process by monitoring the health status of the product components.
l Prevent failed jobs and out of space errors by monitoring backup repositories.
l Reduce storage space by automating backup decommissioning.
l Improve compliance by automating data protection reporting.
l Align data protection with your business processes by triggering VM backup and replication jobs with your
orchestration and automation tools.
l Increase recovery speed by automating recovery.

- 67 -
Job Chaining
Job Chaining allows you to link jobs so that they run one directly after another. For example, you can set up a VM
backup job, which saves backups locally and then starts a Backup Copy job, which copies the newly created backups to
Amazon cloud.

You can link any type of jobs together – backup, backup copy, replication and recovery – and add any number of jobs
to the chain. For instance, you can set up a series of backup jobs that trigger one another in the order of priority, or set
up a series of Backup Copy jobs, which first send weekly backups to a DR repository and then send monthly backups to
Amazon cloud for archiving.

- 68 -
Pre and Post Job Scripts
NAKIVO Backup & Replication provides you with the ability to run a script before a job begins (a pre-job script) and after
the job has been completed (a post-job script).

By running your pre- and post- job scripts, you can do just about anything: start custom pre-freeze and post-thaw
scripts on Linux systems to create application-aware backups and replicas, wake servers, establish connections, mount
volumes, start and stop services, send commands to 3rd-party reporting, monitoring and automation tools, and etc.

- 69 -
Integration
NAKIVO Backup & Replication provides support for enterprise-grade deduplication appliances, such as EMC Data
Domain and NEC HYDRAstor. Deduplication appliances are servers designed to reduce data size, and can be used as
backup targets. Deduplication appliances operate best with sequential large block I/O from backup software. Therefore,
when backing up your VMs to a deduplication appliance, it is important to make sure that the architecture of your
Backup Repository is optimized for these devices and your VM backups have a large block I/O. Only by doing this, you
will be able to maximize your VM backup speeds.
NAKIVO Backup & Replication offers you two different types of backup repositories to choose from:
l The regular Backup Repository, which is optimized for generic storage systems and performs forever-incremental
VM backups along with global data deduplication and compression.
l The special Backup Repository with an architecture optimized for efficient operation on deduplication appliances.
This is known as “Incremental with full backups”, and the name truly speaks for itself. The repository performs
incremental-with-full VM backups, and proprietary VM backup deduplication and compression by NAKIVO
Backup & Replication are turned off. The file structure is also improved, and each backup with its recovery points
is stored in a separate folder for easier manageability.
When tested in a customer environment on a high-end NEC HYDRAstor deduplication appliance, the product's special
Backup Repository demonstrated a 53X boost in backup speed over the regular Backup Repository. NAKIVO Backup &
Replication backed up the customer's VMs at an incredible 3.2 GByte/s. NAKIVO Backup & Replication ensures that you
can use existing storage hardware while achieving top VM backup performance.
Integration with the following solutions allow NAKIVO Backup & Replication to further increase backup speed and save
storage space:
l “Active Directory” on page 71
l “EMC DD Boost” on page 72
l “HPE StoreOnce Catalyst” on page 73

- 70 -
Active Directory
Microsoft Active Directory is a leading directory service, which provides you with the ability to authenticate and
authorize users and computers in a Windows domain type network. To simplify user management, NAKIVO Backup &
Replication provides integration with Microsoft Active Directory. You can easily map Active Directory groups to NAKIVO
Backup & Replication user roles, which will allow domain users to log in to NAKIVO Backup & Replication with their
domain credentials. With this feature, you can align NAKIVO Backup & Replication with your company's security policy
and seamlessly provide Admin and Guest access to NAKIVO Backup & Replication.
For more information, refer to the following topics:
l “Configuring Active Directory Integration” on page 307
l “Managing Active Directory Users” on page 304

- 71 -
EMC DD Boost
The Dell/EMC Data Domain Boost technology allows for the reduction of storage consumption by up to 17X, greatly
accelerating the VM backup process. The aggregate quantity of business data produced has drastically increased in
recent years, which results in two major problems for modern companies. The first is the amount of storage space that
backups occupy, and the second is the significant load on the production network created by backup operations,
especially if they are run during business hours.
NAKIVO Backup & Replication and Dell/EMC Data Domain Boost offer a combined solution for both of these challenges.
By using NAKIVO Backup & Replication along with source-side deduplication of Dell/EMC Data Domain Boost, you can
perform VM backups 50% faster while reducing the size of your backups by up to 94%. This means that you can offload
your network and save storage space at the same time.
For more information about the integration of NAKIVO Backup & Replication with EMC DD Boost, refer to the following
articles:
l “Storage Integration Requirements” on page 138
l Integrating with EMC DD Boost
l “Backup Repository on Deduplication Appliance” on page 391

- 72 -
HPE StoreOnce Catalyst
HPE StoreOnce Systems from Hewlett Packard Enterprise provide a disk-based data protection platform. This platform
addresses data growth by applying HPE StoreOnce deduplication software for efficient and long-term backup data
retention. HPE StoreOnce Catalyst, a data protection protocol optimized for disk-based data protection, is the most
efficient way to transfer data to a StoreOnce System. When using HPE StoreOnce Catalyst for your Backup Repository,
you get the following advantages:
l Reduction in network bandwidth as only unique chunks of data are transferred
l Lower physical storage space requirements with data deduplication
l Better backup copy job performance between HPE StoreOnce storage devices.
Starting from NAKIVO Backup & Replication version 10.1, you can create a Backup Repository on a StoreOnce appliance
with HPE StoreOnce Catalyst support. Refer to the following topics for details:
l “Deduplication Appliance Support” on page 52
l “Storage Integration Requirements” on page 138
l “Backup Repository on Deduplication Appliance” on page 391

- 73 -
NEC HYDRAstor
HYDRAstor is an award-winning product developed by the NEC Corporation. It is a disk-based grid storage platform
offering long- term data retention through its maximized capacity of legacy storage solutions and scalability of
performance. A HYDRAstor storage system can be composed of multiple nodes – from one to over 100. Each node
consists of standard hardware including disk drives, memory, CPU, and network interfaces. The system is integrated
with the HYDRAstor software, thus creating a single storage pool. The software incorporates multiple features of
distributed storage systems. The features include content-addressable storage, variable block size, inline global data
deduplication, erasure codes, data encryption, Rabin fingerprinting, and load balancing.
HYDRAstor can be scaled from one node to 165 in a multi-rack grid appliance. Its bandwidth and capacity can be scaled
separately by using different types of nodes:
l Hybrid nodes: add both performance and capacity.
l Storage nodes: add capacity.
HYDRAstor supports online expansion with automatic data migration and zero downtime. With a standard
configuration, the product provides resiliency up to 3 concurrent disk/node failures. Failures are detected
automatically, and data reconstruction is also performed automatically. This means that if the time between failures is
sufficient for reconstructing data, the system will withstand any number of them. For more information about NEC
HYDRAstor, refer to the NEC official website. 
To know more about the integration of NAKIVO Backup & Replication with NEC HYDRAstor, refer to the following
articles: 
l “Storage Integration Requirements” on page 138
l Integrating with NEC HYDRAstor
l “Backup Repository on Deduplication Appliance” on page 391

- 74 -
BaaS
NAKIVO Backup & Replication allows for creating and managing multiple isolated tenants within one product instance.
This section contains the following topics:
l “Branding” on page 76
l “License Delegation” on page 77
l “Multi-Tenancy” on page 78
l “Self-Service” on page 79

- 75 -
Branding
Whether you plan to use NAKIVO Backup & Replication internally or provide backup/DR-as-a-Service to external
customers, you may find it beneficial to align the product's look and feel with your company's brand.
NAKIVO Backup & Replication provides a simple way to customize your product's interface so that it looks like an
integral part of your organization. You can customize:
l Product: Product title and product logo.
l Company information: Company name and website URL.
l Contact information: Email, support email, and contact phone.
l Look and feel: Bookmark icon and page background.
For information on branding configuration, refer to “Branding Configuration” on page 286.

- 76 -
License Delegation
In Multi-tenant mode, NAKIVO Backup & Replication enables you to create multiple isolated tenants in a single copy of
the product. The tenants can represent branch offices/departments in enterprise environments or clients in Cloud
Provider environments.
Since tenants are isolated and need to have a limit as to how many licenses each of them can use, NAKIVO Backup &
Replication has provided the License Delegation feature. In Multi-tenant mode, a Master Admin (tenant manager) can
install one multi-socket license in the product and then assign or delegate a specific number of licenses to each tenant.
For example, the Master Admin can install a 20-socket license in the Multi-tenant mode of NAKIVO Backup &
Replication, and assign 3 licenses to Tenant A, 2 licenses to Tenant B, and 4 licenses to Tenant C, and let 11 licenses
remain unused.

At any moment, the Master Admin can redistribute licenses: revoke any number of licenses from any tenant, which will
return them to the Master License Pool, and add licenses to another tenant. The License Delegation feature makes
license management simple and manageable in large and distributed environments.

- 77 -
Multi-Tenancy
Multi-tenancy enables you to create and manage up to 1,000 isolated tenants within a single copy of the product.
Tenants can represent business units, branch offices, departments, customers, and any other entities.

In Multi-tenant mode, each tenant can access their own environment through a self-service portal, and perform all data
protection and recovery tasks. At the same time, tenants are isolated from each other and cannot access the
environment and jobs of other tenants.
With Multi-tenancy, you can:
l Deliver Backup-as-a-Service, Replication-as-a-Service, and Disaster-Recovery-as-a-Service, for VMware, Hyper-V
and AWS EC2 environments more efficiently and cost-effectively.
l Reduce complexity by managing multiple tenants in a single pane of glass.
l Offload data protection and recovery tasks to tenants.
l Reduce footprint by managing tenants in a single instance of the product.

- 78 -
Self-Service
In the multi-tenant mode, you can provide tenants with access to their dashboards. By default, a tenant admin account
is automatically created when you create a new tenant. If you assign the Self-service administrator role to the tenant
admin, the tenant admin has full control over all product features inside the tenant dashboard. This includes editing
and updating tenant inventory, Transporters, and Backup Repositories, creating and managing jobs and groups, as well
as managing local users and user roles. For each tenant, one guest account can be created. The tenant guest usually has
limited permissions inside the tenant.
To provide a tenant with access to the self-service interface, send them the following information:
l Link to NAKIVO Backup & Replication Director
l Tenant login
l Tenant password

- 79 -
Licensing
Choose the licensing type that best suits your business needs. For details, refer to the topics below:
l Licensing Types
l Perpetual Licensing

l Per-Workload Licensing

l Subscription Licensing for Microsoft 365

l Licensing Rules
l NAKIVO Support

Licensing Types
NAKIVO Backup & Replication offers the following licensing types:

Perpetual Licensing
For VMware, Hyper-V, and Nutanix AHV infrastructures, NAKIVO Backup & Replication can be licensed on a per-socket
basis. A license is required for each socket on a host where you plan to back up or replicate VMs. Licenses are required
only for the source side of backup and replication, that is, you do not need to license target servers for your replicas or
the servers on which you want to recover VMs.
Perpetual licenses are also available for physical machines on a per server or workstation basis and Oracle databases
(Enterprise Plus edition only) on a per Oracle database basis.
Notes
l Perpetual licenses for physical servers can't be applied for physical workstations and vice versa.
l Physical machines with unsupported OS are treated as physical servers.

Per-workload Subscription Licensing

NAKIVO Backup & Replication can be licensed on a per-workload basis. A workload can be a VMware VM, Microsoft
Hyper-V VM, Nutanix AHV VM, physical machine (1 physical server or 3 workstations), Oracle database (Enterprise Plus
edition only), or AWS EC2 instance that you plan to back up or replicate. Regardless of the type, each item is counted as
one workload. Licenses are required only for the source side of backup and replication, that is, you do not need to
license target servers for your replicas or the servers on which you want to recover workloads. Subscription licenses
include 24/7 Support.

- 80 -
Subscription Licensing for Microsoft 365
Backup and Recovery for Microsoft 365 is licensed on a per-user, per-month basis. The license can be purchased
together with any edition (Basic, Pro Essentials, Enterprise Essentials, Pro, Enterprise, or Enterprise Plus) and combined
with any license type (Perpetual or Subscription). Subscription licenses for Backup and Recovery for Microsoft 365
include 24/7 Support. The minimum number of licenses per order is 10.
When combined with a perpetual license, the support end date of the perpetual license and subscription license for
Backup and Recovery for Microsoft 365 must be aligned. The support level may be Standard for perpetual sockets and
24/7 for Microsoft 365 Subscription. Optionally, the support level for perpetual sockets can be upgraded to 24/7
Support.
The table below provides information on licensing options.

Nutanix Amazon Physical Microsoft Oracle

License Type VMware Hyper-V
AHV EC2 Machine 365 Database

Perpetual + + + - + - +

Subscription + + + + + + +

Licensing Rules
l Perpetual and subscription licenses cannot be combined in one license.
l Subscription license for Backup and Recovery for Microsoft 365 can be combined with both perpetual and
subscription (per-workload) licenses.
Note
For the most recent information about licensing, refer to the NAKIVO's pricing page.

NAKIVO Support 
NAKIVO Backup & Replication offers two levels of technical support:
l Standard Support
l 24/7 Support

- 81 -
Standard Support provides coverage from Monday to Friday during business hours as defined in the Customer Support
Policy. One year of Standard Support is included in all new perpetual license purchases. 24/7 Support provides 24/7/365
coverage via phone, chat or email. To switch from Standard to 24/7 Support, you need to purchase a support Upgrade.
Customers who upgrade to a higher-tier edition and have purchased additional years of support are required to
upgrade their support too. 
If a support agreement has been expired for more than 1 month, it can be extended with Expired Support Renewal. 
For more information about the terms and conditions of using NAKIVO Customer Support services, refer to the
following resources:
l NAKIVO Customer Support Policy
l NAKIVO Customer Support Agreement
l End-User License Agreement

- 82 -
Getting Started
When deployed, NAKIVO Backup & Replication is ready for use. The topics below will provide you with information on
how to start working with the application.
l “Logging in to NAKIVO Backup and Replication” on page 84
l “First Steps with NAKIVO Backup & Replication” on page 88
l “Web Interface Components” on page 91
l “Managing Jobs and Activities” on page 96

- 83 -
Logging in to NAKIVO Backup and Rep-
lication
l Getting to Login Page
l Creating User Account
l Resetting Password
l Default Password in Amazon EC2

Getting to Login Page 

You can get to the NAKIVO Backup & Replication login page by opening the following URL in your web browser:
https://machine_IP_or_DNS:4443
Note
If you have selected a custom HTTPS port during installation, replace 4443 with the corresponding value.

Creating User Account

When you open the NAKIVO Backup & Replication login page for the first time, you will be prompted to create a new
user account. This is an admin account that will be used to access your instance of the application. Fill out the fields in
the form:
Note
If NAKIVO Backup & Replication is deployed in an EC2 instance, you will first be prompted to enter the EC2 instance ID.
1. Name: Provide your real name.
2. Username: Enter an admin username to log in to the application.
3. Email: Provide an email address that you will use to identify yourself in the application.
4. Password: Enter a password for logging in to the application.
5. Repeat password: Repeat the password you’ve entered in the Password field above.
When you are ready to create your NAKIVO Backup & Replication account, click Proceed.

- 84 -
The application opens in your browser displaying the configuration wizard. 
Refer to “First Steps with NAKIVO Backup & Replication” on page 88 to learn how to start using NAKIVO Backup &
Replication.
To log out of the application, click Logout in the main menu, and then click Log out.

Resetting Password
If you forget the password used to log in to NAKIVO Backup & Replication, you can restore it by following the steps
below:
1. Open the NAKIVO Backup & Replication login page.
2. Type in incorrect credentials. The notification Incorrect credentials will appear on the display.
3. Click the Forgot password link.

- 85 -
4. Do either of the following:
l If you have set up email settings in NAKIVO Backup & Replication, enter your email address in the field and
click Done. The password will be sent to your email address.
l If you have not set up email settings in NAKIVO Backup & Replication:
a. Enter your username and click Done.
b. Go to the product installation folder and locate the “forgot_password.txt” file.
Important
For security reasons, only root (Linux) or a member of the Administrators group (Windows) are
allowed to access the installation folder and the "forgot_password.txt" file.
c. Paste the security string from the file in the appropriate field.
d. Click Done.
Notes
l If you are using the Virtual Appliance (VA), go to the VA console, then go to the command line and

enter:
cat /opt/nakivo/director/forgot_password.txt
The security string will be displayed on the screen. You can copy-paste it into the web interface.
l If you are using a NAS, open an SSH connection to your device and read the forgot_password.txt file

in the following folders:

l For ASUSTOR NAS: /usr/local/AppCentral/NBR

l For FreeNAS (inside the jail): /usr/local/nakivo/director

l For NETGEAR NAS: /apps/nbr

l For QNAP NAS: /share/CACHEDEV1_DATA/.qpkg/NBR

- 86 -
 l For Raspberry PI: /opt/nakivo/director
l For Synology NAS: /volume1/@appstore/NBR
l For Western Digital NAS: /mnt/HD/HD_a2/Nas_Prog/NBR

l To learn how to open an SSH connection to your NAS device and read text files, refer to the cor-
responding NAS vendor documentation.

Default Password in Amazon EC2

If you have deployed NAKIVO Backup & Replication as an EC2 instance in AWS EC2, use the following default credentials
to log in:
l Username: admin
l Password: The password is the ID of the NAKIVO Backup & Replication instance in Amazon EC2.

- 87 -
First Steps with NAKIVO Backup & Replication
When you log in to NAKIVO Backup & Replication for the first time, the initial configuration wizard opens.
Proceed as follows:
1. On the Inventory page of the wizard, click Add New.
2. Select one of the options below:
l VMware vCenter or ESXi host
l Microsoft Hyper-V host or cluster
l Physical machine(s)
l Microsoft 365 account
l Nutanix AHV cluster
l AWS/Wasabi account
l Oracle database

3. Proceed with adding items as described in the Inventory article. 

4. On the Transporters page of the wizard, you will find information about the Transporter component of the
NAKIVO Backup & Replication.
5. To deploy a new Transporter or add an existing one, click Got it and proceed as described in the Transporters
article.
6. To move to the next page of the wizard, click Next.

- 88 -
7. On the Repositories page of the wizard, you can add a local or a remote Backup Repository to your application
by clicking Add Backup Repository. 

8. Click Finish. 
9. The Dashboard of the application opens. Proceed with creating your backup and replication jobs.

- 89 -
If your current license type is Free and the Trial license has not yet been applied to the current deployment of NAKIVO
Backup & Replication, a dialog box appears. Using this dialog box, you can contact the sales team to change your license
type or try the full functionality of the solution for 15 days. If you do not want to upgrade your license type right away,
you can do it at any time in the Help menu.
Note
If you switch the license type to Trial, the product will automatically go back to using your Free license after expiration.

- 90 -
Web Interface Components
The interface of NAKIVO Backup & Replication consists of the following components:
l Main Menu

l Dashboard

l Activities

l Calendar

l Search

l Settings

l Help Menu

l Online Chat Dialog

l Special Offers Toolbar

l Tenants Dashboard

Main Menu
The main menu of NAKIVO Backup & Replication is located on the left side of the product interface. It provides access to
the jobs dashboard, activities, calendar, global search, and product settings. It also contains the Help menu and Log
Out button. 

Dashboard
Using the Dashboard, you can:
l View, run, and stop jobs on demand
l Recover files, objects and entire sites
l Manage jobs
l Create backup and replication jobs

- 91 -
 l Create and manage job groups 

Activities
The Activities page displays a list of all running and past activities, such as:
l Job run
l Repository Self-Backup
l File download
l Application object download
l Universal object recovery
l Repository space reclaim
l Repository self-healing
l Repository backup verification
l Backup export
l Tape-specific activities, namely: Tape scan, Tape erase, reading Tape
l Other
For further details and information, refer to “Managing Activities” on page 117 .

- 92 -
Calendar 
The Calendar allows you to schedule jobs and to view the history of all job runs right from the calendar. For more
information, refer to “Using Calendar” on page 121.

Search
The Search page allows you to search for items within the entire N AKIVO Backup & Replication – in the inventory,
Transporters, Backup Repositories, tape devices, jobs, backups, replicas, and other. Refer to “Using Global Search” on
page 122 for more details. 

- 93 -
Settings
On the Settings page, you can configure NAKIVO Backup & Replication general settings,
inventory, Transporters, Backup Repositories, Tape, and licensing.  Refer to “Settings” on page 281 for more details. 

Help Menu
Use the Help menu to request technical support and access the NAKIVO online help center. If you are evaluating
NAKIVO Backup & Replication, you can use the How to Buy section of the Help menu to view pricing, upgrade your Free
license to Trial for 15 days with the Try full functionality option, and request a live demo or a quote. 

Online Chat Dialog

The NAKIVO Support online chat is located in the right bottom corner of the application. It enables you to quickly
request help from a sales or technical support representative.

- 94 -
Special Offers Toolbar
This element of the interface is located to the left of the NAKIVO Backup & Replication dashboard. The toolbar contains
special offers. If you click the button, a dialog opens displaying information about a specific offer. If needed, the Special
Offers toolbar can be disabled. Refer to“System Settings” on page 298 for details.

Tenants Dashboard
If you use NAKIVO Backup & Replication in a multi-tenant mode, the Tenants dashboard allows you to create, manage,
and configure tenants.

- 95 -
Managing Jobs and Activities
Using NAKIVO Backup & Replication interface, you can manage jobs and tasks. This section covers the following topics:
l “Running Jobs on Demand” on page 97
l “Managing Jobs” on page 100
l “Managing Job Policies” on page 108
l “Managing Policy Rules” on page 110
l “Jobs Alarms and Notifications” on page 115
l “Managing Activities” on page 117
l “Using Calendar” on page 121
l “Using Global Search” on page 122

- 96 -
Running Jobs on Demand
Use the Dashboard to start and stop jobs on demand.
l Starting Jobs
l Stopping Jobs

Starting Jobs
To start a job, follow the steps below:
1. Go to the Dashboard, select the job from the list of jobs, and click Run Job.
a. Choose one of the following options:
l Run for all VMs/backups/physical machines: The job will run for all VMs/backups/physical
machines.
l Run for selected VM/backups/physical machines: The job will run for the VMs/backups/physical
machines you select.
l Run for failed VMs/backups/physical machines: The job will run for previously failed
VMs/backups/physical servers only.
b. If the type of the Backup Repository for your job is Incremental with full backups, you will have to choose
between the following backup types:
l Incremental: Your job will create an incremental backup.
l Full: Your job will create a full backup. If you choose this option, please choose the full backup
mode:
l Synthetic full: The application will first perform an incremental backup – that is, will transfer
only the VM data that changed since the last backup, – and will then transform the available
data into a full backup.
l Active full: Will read all source VM data and transfer it to the backup repository.
2. In the dialog that opens, define the scope of your job:

- 97 -
 3. Click the Run button to confirm your operation.

The product will close the dialog box and start running your job.

Stopping Jobs
To stop a job that is currently running, follow the steps below:
1. Go to the Dashboard, select the job from the list of jobs, and click Stop Job.
2. In the dialog that opens, choose either of the following:
l Stop for all VMs/backups/physical servers: Your job will stop for all VMs/backups/physical servers.
l Stop for selected VMs/backups/physical servers: Your job will stop for the jobs you select.

- 98 -
 3. Click the Stop button in the dialog to confirm your operation.

The product will close the dialog box and stop your job.

- 99 -
Managing Jobs
Using the Dashboard, you can easily manage your jobs. Go to the Manage menu to rename, edit, delete and
enable/disable jobs. 
l Renaming Jobs
l Editing Jobs
l Cloning Jobs
l Deleting Jobs
l Disabling and Enabling Jobs
l Grouping Jobs
l Creating Groups

l Creating Job Reports

Renaming Jobs
1. From the list of jobs, select the job you wish to rename.
2. On the Dashboard, click Manage.
3. Click Rename.
4. In the dialog box that opens, specify the new name for the job.
5. Click Rename.

Note
You can also rename jobs by right-clicking on a job and selecting Rename from the Manage Job menu. 

- 100 -
Editing Jobs
To edit a job, follow the steps below:
1. Select the job you wish to edit from the list of jobs.
2. On the Dashboard, click Manage.
3. Click Edit.

4. In the Edit wizard, click the necessary page to open it for editing.

5. Make the required changes and then click Save or Save & Run.
Notes
l You can edit the job while it is running, but the changes will be applied only when the job run has completed.
l You can also edit jobs by right-clicking on a job and selecting Edit from the Manage Job menu. 

Cloning Jobs
To clone a job, follow the steps below:
1. Select the job you would like to clone from the list of jobs.
2. On the Dashboard, click Manage.

- 101 -
 3. Click Clone.

Note
You can also clone jobs by right-clicking on a job and selecting Clone from the Manage Job menu.

Deleting Jobs 
To delete a job follow the steps below:
1. Select the job you want to delete from the list of jobs.
2. On the Dashboard, click Manage.

- 102 -
 3. Click Delete.

Note
You can also delete jobs by right-clicking on a job and selecting Delete from the Manage Job menu. 

Disabling and Enabling Jobs

NAKIVO Backup & Replication provides you with the ability to disable jobs. A disabled job does not run on a schedule,
nor can it be run on demand.
To disable a job, follow the steps below
1. From the list of jobs, select the job you want to disable.
2. On the Dashboard, click Manage.

- 103 -
 3. Click Disable.

To enable a job, select Enable from the Manage menu.

Note
You can also disable/enable jobs by right-clicking on a job and selecting Disable/Enable from the Manage Job menu. 

- 104 -
Grouping Jobs
Groups are folders which allow you to:
l Logically arrange jobs (to represent organizations, locations, services, etc.).
l Perform bulk actions with all or selected jobs in a group.

Creating Groups

To create a group, follow the steps below:

1. On the Dashboard, click Create and then click Job group.
2. Type in the group name in the dialog box that appears and click OK.

The following actions are available to manage groups:

l To add a job to a group, simply drag the job into the group.
l To remove a job from the group, drag the job outside the group.
l To delete a group, right-click the group and choose Delete from the shortcut menu that appears. Confirm the
group deletion when prompted to do so. Note that when deleting a group, its jobs are not deleted and are
moved to the parent group (or Overview).
l To rename a group, double-click the group and enter a new name.
l To enable or disable all jobs inside a group, click the Enable/Disable switch.
l To run jobs available in a group, click Run/Stop and then click Run Jobs. In the dialog box that appears, select the
jobs you wish to run and click Run Jobs.

- 105 -
 l To stop running the jobs available in a group, click Run/Stop and then click Stop Jobs. In the dialog box that
appears, select the jobs you would like to stop and click Stop Jobs.

Creating Job Reports

To create a general report for all your jobs:
1. Select Overview on the Dashboard.
2. Click Create.
3. Choose one of the following reports in the Report section:
l Overview report: Contains information about the status and errors of all your jobs.
l Protection coverage report: Contains information about all VMs and instances protected by backup
and/or replication jobs, as well as about all unprotected VMs and instances. Choose either PDF or CSV
formats for your Protection coverage report and click Create.
l Failed machine protection report: Contains information about all VMs and instances which had failed to
be protected by backup and/or replication jobs, and the error message. Select the date range for your
Failed machine protection report and click Create.
4. Choose a location to save the report and click Save.

To generate reports from for an individual job, do the following:

1. Go to the list of jobs.
2. Select the job that you need to generate a report for and right-click on it.
3. Select one of the following reports from the Create report menu:

- 106 -
l Last-run report: Provides data on the last run of the job.
l Point-in-time Report: Provides data on a particular job run. To generate a report, pick a date in the popup
that appears and click Create.
l Job history report: Provides data on job runs that occurred during a specified time period. To generate a
report, pick a start date on the left and finish date on the right in the popup that appears and click Create.
l Protection coverage report:Contains information about all VMs and instances protected by backup
and/or replication jobs, as well as about all unprotected VMs and instances.
l Failed machine protection report: Contains information about job objects processing of which were failed
during the last job run. Only backup and replication jobs included.
l Site Recovery Job report: Contains a summary of the Site Recovery Job, including the result of passing the
Recovery time objective value, information about all actions performed, and all registered alarms and
notifications.

- 107 -
Managing Job Policies
With policies, you can create rules that easily add matching items to NAKIVO Backup & Replication jobs. For example,
you can create a backup job that meets the following criteria: (a) size of VM is more than 4 GB, (b) number of VM CPU
sockets is more than 2, and (c) VM name contains "Ubuntu". Any policy is applied to a single job. In the NAKIVO Backup
& Replication job wizard, job policy is accessible from the Policy view of the Source page.

Every job policy contains at least one rule. Refer to “Managing Policy Rules” on page 110 for details.
Job policies are available for the following job types:
l Backup jobs
l Replication jobs
l Backup copy jobs
l Failover jobs
l Failback jobs
l Several actions of the Site Recovery job
Learn how to save, edit, and remove job policies in these sections:
l Saving Job Policy
l Editing Job Policy
l Removing Job Policy

Saving Job Policy

Follow the steps below to save a policy rule:
1. Make sure your job is opened in the Policy view.
2. Choose either of the following Condition for your job policy:

- 108 -
 l Include items if ALL rules are matched: If selected, the logical AND will be applied to the set of policy rules.
l Include items if ANY rule is matched: If selected, the logical OR will be applied to the set of policy rules.
3. Provide the necessary policy rules. Refer to “Managing Policy Rules” on page 110 for details. Make sure that at
least one item matches the available set of policy rules.
4. Save your job.

Editing Job Policy

Follow the steps below to edit a job policy:
1. Make sure your job is opened in the Policy view.
2. Change the necessary parameters of your job policy:
1. Condition.
2. Add, edit or delete policy rules. Refer to “Managing Policy Rules” on page 110 for details.
3. Save your job.

Removing Job Policy

Follow the steps below to remove an entire job policy:
1. Make sure your job is opened in the Policy view.
2. Switch to any other inventory view available on the list.
3. A dialog opens warning you that switching to a different view will reset your selection for the current job. Click
Switch View to confirm your operation.
4. Save your job.

- 109 -
Managing Policy Rules
Policy rules are an integral part of job policies. Refer to the following sections for details:
l About Policy Rules
l Editing Policy Rules
l Adding Policy Rule
l Removing Policy Rule

About Policy Rules

In the Policy view of the inventory tree, policy rules are numbered by NAKIVO Backup & Replication for your
convenience.
Every policy rule contains the following options:
1. Search by: A drop-down list with the following search criteria:
l VM name / Instance name / Backup name: The rule is to be applied based on the name of the object. 
l VM tag / Instance tag: The rule is to be applied based on the tag of the object. 
l VM location / Instance location: The rule is to be applied based on the location of the object.
l Name of VM datastore / VM Path: The rule is to be applied based on the name of the VM datastore or
the VM path.
l Name of VM network / Name of Subnet: The rule is to be applied based on the name of the VM network
or instance network.
l Size of VM / Size of instance: The rule is to be applied based on the size of the object.
l Amount of VM/Instance RAM: The rule is to be applied based on the amount of VM/Instance RAM.
l Number of VM CPU sockets / Number of VM processors / Number of Instance virtual CPUs: The rule is
to be applied based on the number of VM CPU sockets, VM processors, or Instance virtual CPUs
correspondingly.
Note
The criteria are available as follows:
l Number of VM CPU sockets: This is for your VMware backup and replication jobs.
l Number of VM processors: This is for your Hyper-V backup and replication jobs.
lNumber of instance virtual CPUs: This is for your Amazon EC2 backup and replication jobs.
l VM power state / Instance power state: The rule is to be applied based on the power state of the object.

- 110 -
 l IP Address: The rule is to be applied based on the IP address of the object.

2. Search parameter: You can choose either of the following:

l For VM name / Instance name / Backup name, Name of VM network / Name of subnet, Name of VM
datastore / VM Path, VM tag / Instance tag, and IP Address:
l Contains

l Does not Contain

l Equals (always applied to the VM tag)

l Does not equal

l Starts with

l Ends with

l For Amount of VM/Instance RAM, Number of VM CPU sockets / Number of VM processors / Number
of Instance virtual CPUs, and Size of VM / Size of Instance, you can choose any of the following search
parameters:
l Is more than

l Is less than

l Equals

l Does not equal

- 111 -
 l For VM Power State / Instance power state and VM Location / Instance location:
l Is

l Is not

3. Search criteria: A text string or a numeric value to be used by the policy rule.
When you enter or edit parameters, the changes are immediately reflected in the list of selected items.

Editing Policy Rule

Follow the steps below to edit a policy rule:
1. Make sure your job is opened in the Policy view.
2. Locate your policy rule in the left pane of the view. If necessary, use the scroll bar.
3. Change the necessary parameters of your policy rule. Make sure that at least one item matches an available set of
policy rules.
4. Click Next.

Adding Policy Rule

Follow the steps below to add a policy rule:
1. Make sure your job is opened in the Policy view.
2. In the left pane of the wizard, click Add another rule.
3. The wizard displays a new policy rule, Rule #N. Provide the necessary parameters of your policy rule. Make sure
that at least one item matches the available set of policy rules.

- 112 -
 4. Click Next when all parameters are set.

Removing Policy Rule

Follow the steps below to remove a policy rule:
1. Make sure your job is opened in the Policy view.
2. Locate your policy rule in the left pane of the view. If necessary, use the scroll bar.
3. Click Remove.

- 113 -
 4. Click Next when all parameters are set.

Note
You cannot remove all policy rules. A job policy must have at least one rule.

- 114 -
Jobs Alarms and Notifications
NAKIVO Backup & Replication displays:
l Alarms: Job failures
l Notifications: Infrastructure changes and minor errors that do not lead to processing failure
For details, refer to the following sections: 
l Viewing Alarms and Notifications
l Dismissing Alarms and Notifications

Viewing Alarms and Notifications 

To view alarms and notifications, click the red box in the Job info widget:

Dismissing Alarms and Notifications

To dismiss all alarms and notifications in a job, click Dismiss All. To dismiss an individual alarm or notification, hover the
mouse pointer over the alarm or notification and click Dismiss.

- 115 -
- 116 -
Managing Activities
The Activities page displays current and past tasks performed by NAKIVO Backup & Replication. From this dashboard,
the following actions can be done:
l Viewing Activities
l Searching for Activities
l Viewing Activity Details
l Stopping Running Activities
l Running Activities Again
l Removing Activities
Past activities are stored for the number of days specified in the Store job history for the last X days setting in the
General tab.

Viewing Activities
The Activities dashboard allows viewing all your current and past activities in the application.

Searching for Activities

Find activity by typing in part of its name in the Search field. 

- 117 -
Viewing Activity Details
View the details of an activity by selecting an activity name.

Stopping Running Activities

To stop a running activity, select the checkbox next to the activity and click Stop in the toolbar at the top. Optionally,
you can stop multiple activities by selecting the checkboxes next to them or stop all running activities by clicking
Select/Deselect all.

- 118 -
Running Activities Again
To run an activity again (if possible), select the checkbox next to the activity and click Start in the toolbar at the top.
Optionally, you can run multiple activities by selecting the checkboxes next to them or run all stopped activities by
clicking Select/Deselect all.

- 119 -
Removing Activities
Remove an activity from the list by selecting the checkbox next to the activity and clicking Remove in the toolbar.

- 120 -
Using Calendar
The Calendar allows you to schedule and view the history of past job runs.
l Creating Jobs with Calendar
l Editing Jobs with Calendar

Creating Jobs with Calendar

To create a job:
1. Click on the date and time when you’d like to run the job 
2. Select the type of job you need.
3. On the Schedule page of the wizard, the time you've selected in the Calendar will be selected.

Editing Jobs with Calendar

If you click on the job title on the Calendar dashboard, the Job Actions menu will appear. 
Using this menu, you can:
l Run a job overriding the schedule.
l Edit a job.
l Clone a job
l Delete the job. If the job is repeated, this action will affect all job runs.
l Disable/Enable a job. If the job is repeated, this action will affect all job runs.
l Open the Dashboard.
l Create a report.

- 121 -
Using Global Search
Using the Global Search dashboard, search for items within the entire inventory of NAKIVO Backup & Replication,
Transporters, Backup Repositories, jobs, backups, and replicas.
l Opening Global Search
l Running Global Search
l Filtering Search Results
l Applying Bulk Action
l Viewing Object Info
Note
When the multi-tenant mode is enabled, Global Search will operate within a specific tenant. For more information about
multi-tenancy in NAKIVO Backup & Replication, please consult with the following resources:
l “Multi-Tenant Deployment” on page 174
l “Multi-Tenancy” on page 78
l “Multi-Tenant Mode” on page 730

Opening Global Search

To open Global Search, click the Search icon in the main toolbar of the application.

Running Global Search

When the Global Search dashboard opens, you can enter your search string into the search box.
The string you have entered will be immediately followed by a display of the search results in the form of a list.
To help you fine-tune your search, the following wildcards are applicable:
l "?" representing a single character.
l "*" representing zero or more characters.

- 122 -
Please note the following:
l Search is case insensitive.
l Search results are grouped by categories.

Filtering Search Results

By default, your search results are unfiltered. This means that the search is applied to all categories of NAKIVO Backup &
Replication objects.
To narrow your search results, deselect some categories in the categories list:
l Backups
l Replicas
l Jobs & Groups
l Protected Items
l Unprotected Items
l Backup Repositories
l Transporters
The filtered search results will be displayed immediately in the search results list.

- 123 -
To get back to the default filtering settings, click Select all below the categories list.

Applying Bulk Action

With NAKIVO Backup & Replication Global Search, you can apply a bulk action to objects belonging to the same
category and of the same type.
Proceed as follows to apply a bulk action:
1. In the search result list, select similar objects.
2. The Bulk Action button becomes active in the upper right corner of the dialog. Click Bulk Action.

A dialog opens with the list of actions applicable to the selected items. To proceed with the necessary action, click the
corresponding item in the list of actions.
Note
Bulk actions are not applicable to NAKIVO Backup & Replication dissimilar objects.

- 124 -
Viewing Object Info
To view info on a specific object available in the search result, click the object.

A dialog opens displaying object info, along with the list of typical actions applicable to the object.

- 125 -
Deployment
This section contains the following topics:
l “Architecture” on page 127
l “System Requirements” on page 136
l “Deployment Scenarios” on page 171
l “Installing NAKIVO Backup and Replication” on page 187
l “Updating NAKIVO Backup and Replication” on page 248
l “Uninstalling NAKIVO Backup and Replication” on page 277

- 126 -
Architecture
l What is NAKIVO Backup & Replication?
l Solution Components

What is NAKIVO Backup & Replication?

NAKIVO Backup & Replication is an all-in-one solution designed to back up, replicate, and recover virtual machines and
cloud instances. The product can also back up and recover physical machines.

Solution Components
NAKIVO Backup & Replication is a server application that can be installed on a virtual or physical machine. The
application is designed to achieve top speeds for CPU and RAM to achieve the top speed of VM backup, replication, and
recovery. Thus, NAKIVO Backup & Replication components should be installed on a machine designated for backup and
replication so it does not interfere with the performance of other applications.
NAKIVO Backup and Replication consists of the following components:
l “Director” on page 128
l “Transporter” on page 130
l “Backup Repository” on page 134
All components can be installed on a single machine or can be distributed across multiple machines and geographical
locations.

- 127 -
Director
l What is Director?
l How Many Directors Should be Deployed?

What is Director?
Director is the central management instance of the product. It provides Web interface, locates and maintains the
inventory, provides users with the ability to create and run jobs, manages Backup Repositories, Transporters, and
other product elements.

How Many Directors Should be Deployed

Only one instance of the Director should be installed per customer. As a central management point for data protection,
one instance of the Director can manage multiple geographically distributed virtual and cloud environments, Backup
Repositories, and Transporters. See the example below.

- 128 -
- 129 -
Transporter
l What is Transporter?
l How many Transporters Should be Deployed?
l How Transporters are Selected for Jobs
l Transporter as a VMware Appliance

What is Transporter?
Transporter is the component of the product that does all of the heavy lifting. It performs backup, replication, and
recovery, as well as data compression, deduplication, and encryption. An instance of the Transporter is automatically
installed along with the Director to enable backup, replication, and recovery out of the box. The default Transporter is
called "Onboard Transporter" and cannot be removed from the product.

A single Transporter can back up, replicate, and recover multiple VMs and cloud instances.

One Transporter can simultaneously process multiple source disks (6 by default) during backup, replication, and
recovery. If jobs contain more disks than the Transporter is set to process simultaneously, the disks will be put in a
queue and will be processed once the Transporter frees up.

- 130 -
How Many Transporters Should be Deployed?
In most cases, it is sufficient to deploy only one Transporter per site. In large environments, where multiple source
items need to be processed simultaneously, multiple Transporters can be deployed to distribute the workload.

Deploying multiple Transporters also enables network acceleration and AES 256 encryption of traffic between a pair of
Transporters. For example, if VMs are replicated over WAN between two sites, the Transporter installed in the source
site can compress and encrypt data before transferring it over WAN, and the Transporter installed in the Target site can
unencrypt and decompress the data prior to writing it to the target server.

If you plan to transfer data over WAN without a VPN connection from your source site to the target site, make sure the
source and target Transporters are added to the product using external IP addresses or DNS names that can be
properly resolved in WAN, so that the two Transporters can connect to each other.

- 131 -
How Transporters are Selected for Jobs
In large and geographically distributed environments multiple Transporters can be deployed to distribute the data
protection workload, optimize network traffic, and improve data transfer speeds. Thus, if more than one Transporter is
deployed for NAKIVO Backup & Replication, it is important to determine which one should be used to read data from a
particular source and which one should be used to write data to a target.
By default, the product automatically determines which Transporter should be used based on the proximity of a
Transporter to the source or target server. The proximity is measured by using the ping round trip time.

In the example above, Transporter 1 will be selected to read data from the Source ESXi, and Transporter 2 will be
selected to write data to the Target ESXi.
The Transporter selection can also be configured manually during job creation.

Transporter as a VMware Appliance

Since VMware does not provide a VDDK library for ARM-based processors, the NAKIVO Onboard Transporter may not
support VMware as some functionality necessary for working with VMware is missing for such ARM-based NAS devices.
In this case, you will need to deploy an additional Transporter as a VMware appliance to allow NAKIVO Backup
& Replication to work with VMware vCenters and ESXi hosts, and protect your virtual infrastructure.

- 132 -
Once deployed, the additional Transporter allows the application to retrieve necessary data via Transporter-to-
Transporter communication.

- 133 -
Backup Repository
l What is a Backup Repository?
l How Much Data Can Be Stored in a Backup Repository?
l How is a Backup Repository Managed?

What is a Backup Repository?

A Backup Repository is a folder used by NAKIVO Backup & Replication to store backups. When you add a Backup
Repository to the product, NAKIVO Backup & Replication creates a folder named “NakivoBackup” in the specified
location and keeps all backed up data and Backup Repository metadata in that folder.
Important
l Do not modify or delete any files inside the “NakivoBackup” folder. Modifying or deleting any file inside the
“NakivoBackup” folder may irreversibly damage an entire Backup Repository.
l To avoid disrupting NAKIVO Backup & Replication processes and data corruption, add the application to the
whitelist/exclusions list of the antivirus software running on the machine on which the NAKIVO Backup Repository
is set up.
By default, a Backup Repository is created when the full solution (both Director and Transporter) is installed. The default
Backup Repository is named “Onboard repository”.

How Much Data Can Be Stored in a Backup Repository?

NAKIVO Backup & Replication can store up to 128 TB of data in a single Backup Repository. The number of Backup
Repositories per installation is unlimited.By default, backups are compressed and deduplicated at the block level across
the entire Backup Repository to save storage space.

How is a Backup Repository Managed?

Each Backup Repository is managed by a single Transporter called an Assigned Transporter. In other words, only one
Transporter can read data from and write data to a particular Backup Repository.

- 134 -
The Assigned Transporter is responsible for all interaction with its Backup Repository. A single Transporter can be
assigned to and manage multiple Backup Repositories.

- 135 -
System Requirements
Before you start using NAKIVO Backup & Replication, make sure that the servers or machines that you plan to use as
backup infrastructure components meet the requirements listed in the following topics:
l “Supported Platforms” on page 137
l “Storage Integration Requirements” on page 138
l “Deployment Requirements” on page 140
l “Feature Requirements” on page 162

- 136 -
Supported Platforms
NAKIVO Backup & Replication provides data protection for the following platforms:
l VMware vSphere v4.1 - v7.0U1
To add a supported platform to the NAKIVO Backup & Replication, make sure that your system has been updated with
the latest patch and all the necessary requirements are met:
l Hypervisor Requirements
l VMware vSphere

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

VMware vSphere

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

- 137 -
Storage Integration Requirements
NAKIVO Backup & Replication can be integrated with many deduplication appliances by using a stream repository. The
product also offers advanced integration with Dell EMC Data Domain, NEC HYDRAstor, and HP StoreOnce Catalyst
appliances. Deduplication appliances are servers designed to reduce data size and can be used as backup targets.
Deduplication appliances operate best with sequential large block I/O from backup software. Therefore, when backing
to a deduplication appliance, it is important to make sure that the architecture of your Backup Repository is optimized
for these devices and your backups have a large block I/O. Only by doing this, you will be able to maximize your backup
speed. NAKIVO Backup & Replication provides advanced integration with the following storage solutions:

Dell-EMC Data Domain

Supported versions:
l Dell-EMC Data Domain 6.1
l Dell-EMC Data Domain 6.2

NEC HYDRAstor
Supported systems:
l NEC HYDRAstor v 5.5.1
l NEC Storage HS Universal Express I/O Module Version 1.8.0

HP StoreOnce Catalyst
Supported versions:
l HPE StoreOnce 3.18.18
l HPE StoreOnce 4.2.3
Integration requirements:
NAKIVO Backup & Replication installed on Windows (x64) and Linux (x64) machines must have HPE StoreOnce Catalyst
API Library.
Supported Maximums

Maximum Transporter
StoreOnce Model Maximum Sessions Maximum Recovery Points
Load

VSA

VSA Gen 4
128-256 6 7
(128+sessions)

HPE ProLiant Gen 10 (StoreOnce 4.2.3)

3620 128 6 7

- 138 -
3640 192 6 14

5200 512 10 21

5250 512 10 21

5650 1024 16 30

HPE ProLiant Gen 9 (StoreOnce 3.18.18)

3500 192 6 14

5100 320 10 14

5500 1000 16 30

6600 1024 16 30

HPE ProLiant Gen 8 (StoreOnce 3.18.18)

4500 128 6 7

4700 192 6 14

4900 500 10 21

6500 512 10 21

- 139 -
Deployment Requirements
NAKIVO Backup & Replication can be deployed as a virtual appliance (VA) or installed directly onto a supported machine
or network-attached storage (NAS). Below is the list of deployment requirements.
l Hardware
l VM of Physical Machine

l Network Attached Storage

l Operating Systems
l Networking Requirements
l Required TCP Ports

l Network Conditions

l Web Browsers

Hardware

VM or Physical Machine

NAKIVO Backup & Replication can be installed on a machine with the following minimum hardware characteristics:
Director and Onboard Transporter:
l CPU: x86-64, 2 cores 
l RAM: 4 GB + 250 MB for each concurrent task
l For SaaS Backup Repository-related activities:

l additional 2 GB

l additional 100 MB for each concurrent Java Transporter task

l Free space: 10 GB
Transporter only:
l CPU: x86-64, 2 cores
l RAM: 2 GB + 250 MB for each concurrent task
l For SaaS Backup Repository-related activities:

l additional 2 GB

l additional 100 MB for each concurrent Java Transporter task

l Free space: 5 GB

Network Attached Storage

NAKIVO Backup & Replication can be installed on supported NAS with the following minimum hardware characteristics:
Director and Onboard Transporter:

- 140 -
 l CPU: x86-64, 2 cores 
l RAM: 1 GB
l For SaaS Backup Repository-related activities:

l minimum total RAM: 4 GB

l additional 100 MB for each concurrent Java Transporter task

l Free space: 10 GB
Transporter only:
l CPU: x86-64, 2 cores
l RAM: 512 MB
l For SaaS Backup Repository-related activities:

l minimum total RAM: 4 GB

l additional 100 MB for each concurrent Java Transporter task

l Free space: 5 GB
NAKIVO Backup & Replication supports the following NAS models:
Note
Onboard Transporters installed on NAS devices with ARM CPU do not support VMware infrastructures. Refer to
Transporter Does Not Support VMware vSphere for a solution.

Supported NAS Devices

l Synology. For a full list of supported models, refer to “Supported Synology NAS Devices” on page 157
l QNAP. For a full list of supported models, refer to “Supported QNAP NAS Devices” on page 151
l ASUSTOR. For a full list of supported models, refer to “Supported ASUSTOR NAS Devices” on page 146
l NETGEAR. For a full list of supported. For a full list of supporter models, refer to “Supported NETGEAR NAS
Devices” on page 148.
l Western Digital. For a full list of supported models, refer to “Supported Western Digital NAS Devices” on
page 161.
Generic ARM-based NAS devices
The device for installing NAKIVO Backup & Replication should meet the following requirements:
l Single-board computer with ARMv7/ARMv8 CPU (e.g. Raspberry Pi 3 Model B+)
l 32/64-bit Linux-based OS supported by NAKIVO Backup & Replication
l Minimum 16 GB of onboard memory or microSD card for OS & software installation
l RAM: minimum 512 MB for Transporter-only installation; minimum 1 GB for full installation
l Separate microSD/HDD/SSD card for Repository storage
l Open ports for Director and Transporter (see Required TCP Ports)
l Enabled SSH protocol
l Active network connection

Raspberry Pi
NAKIVO Backup & Replication can be installed on a Raspberry Pi 3 Model B+ machine with the following minimum
hardware characteristics:

- 141 -
Director and Onboard Transporter:
l RAM: 1 GB + 250 MB for each concurrent task
l Free space: 16 GB
Transporter only:
l RAM: 512 MB + 250 MB for each concurrent task
l Free space: 16 GB

Operating Systems
NAKIVO Backup & Replication can be installed on the following operating systems:
Windows
l Windows Server 2019 Standard (x64)
l Windows Server 2016 Standard (x64)
l Windows Server 2012 R2 Standard (x64)
l Windows Server 2012 Standard (x64)
l Windows Server 2008 R2 Standard (x64)
l Windows 10 Professional (x64)
l Windows 8 Professional (x64)
l Windows 7 Professional (x64)
Linux
l Ubuntu 18.04 Server (x64)
l Ubuntu 16.04 Server (x64)
l SUSE Linux Enterprise Server 12 SP3 (x64)
l SUSE Linux Enterprise Server 12 SP2 (x64)
l SUSE Linux Enterprise Server 12 SP1 (x64)
l Red Hat Enterprise Linux 7.6 (x64)
l Red Hat Enterprise Linux 7.5 (x64)
l Red Hat Enterprise Linux 7.4 (x64)
l CentOS Linux 7.6 (x64)
l CentOS Linux 7.5 (x64)
l CentOS Linux 7.4 (x64)
l CentOS Linux 7.3 (x64)
l CentOS Linux 7.2 (x64)
l CentOS Linux 7.1 (x64)
l CentOS Linux 7.0 (x64)
NAS
l ASUSTOR ADM v3.0
l ASUSTOR ADM v3.1
l ASUSTOR ADM v3.2
l FreeNAS 11.3
l Netgear ReadyNAS OS v6.9
l Netgear ReadyNAS OS v6.10.3

- 142 -
 l Synology DSM v6.0
l Synology DSM v6.1
l Synology DSM v6.2
l QNAP QTS v4.3
l QNAP QTS v4.4
l WD MyCloud v3
Supported Operating System Localizations
NAKIVO Backup & Replication can be installed on a supported OS with the following OS localization:
l English
l Italian
l German
l French
l Spanish

Networking Requirements

Required TCP Ports

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

TC Port #
Where Description
(Default)

NAKIVO Backup & Replication

Used to access the Director web UI. Must be opened on the Director
4443 Director
machine.

Used by Director and Transporters to communicate with the Transporter.

9446 Transporter
Must be opened on the Transporter machine.

Used by Transporters for cross-Transporter data transfer. Must be opened

9448 - 10000 Transporter
on the Transporter machine.

VMware

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

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

902 ESXi hosts
ESXi hosts.

Hyper-V

- 143 -
 Used by Director to upload files and install configuration service. Must be
137 - 139 Hyper-V hosts
opened on Hyper-V servers.

445 Hyper-V hosts Used by Director to upload files and install configuration service.

5986 (opens Used by Transporter to add a host to inventory and establish a connection
Hyper-V hosts
automatically) with it.

Used by Director to upload files and install configuration service. Must be

9445 (opens
Hyper-V hosts opened on Hyper-V host if NAKIVO Backup & Replication is installed on a
automatically)
host and this host is added to inventory simultaneously.

Used by Director and Transporters to communicate with the Transporter.

9446 (opens Must be opened on Used by Transporters for cross-Transporter data
Hyper-V hosts
automatically) transfer. Must be opened on the Transporter machine. the Transporter
machine.

9448 -10000
Used by Transporters for cross-Transporter data transfer. Must be opened
(opens Hyper-V hosts
on the Transporter machine.
automatically)

Physical machine (Windows)

Windows
445 Used by Director to upload files and install configuration service via SMB.
machine

9446 (opens Windows

Used to create the Transporter installed by default.
automatically) machine

Physical machine (Linux)

22 Linux machine Used by Director to access a Linux physical machine via SSH.

9446 (opens auto-

Linux machine Used to create the Transporter installed by default.
matically)

Network Conditions

NAKIVO Backup & Replication has been tested to work in the following minimal network conditions:
l Latency (RTT): Up to 250 ms
l Packet loss: Up to 1 %
l Bandwidth: 1 Mb/s or higher
l ICMP ping traffic: It should be allowed on all hosts on which NAKIVO Backup & Replication components are
installed as well as on all source and target hosts.

- 144 -
Web Browsers
NAKIVO Backup & Replication user interface can be accessed through the following web browsers:
l Google Chrome: Version 80
l Mozilla Firefox: Version 74

- 145 -
Supported ASUSTOR NAS Devices
NAKIVO Backup & Replication supports the following ASUSTOR NAS devices:

Director and Onboard Transporter

l AS3102T
l AS3102T v2
l AS3104T
l AS3202T
l AS3204T
l AS3204T v2
l AS4002T
l AS4004T
l AS5202T
l AS5304T
l AS5002T
l AS5004T
l AS5008T
l AS5010T
l AS6102T
l AS6104T
l AS6302T
l AS5102T
l AS5104T
l AS5108T
l AS5110T
l AS6202T
l AS6204T
l AS6208T
l AS6210T
l AS6404T
l AS6204RS / AS6204RD
l AS-609RS / AS-609RD
l AS7004T
l AS7008T
l AS7010T
l AS6212RD
l AS7009RD / AS7009RDX
l AS7012RD / AS7012RDX
l AS-602T
l AS-604RS / AS-604RD

- 146 -
 l AS-604T
l AS-606T
l AS-608T
l AS6508T
l AS6510T
l AS7110T
l AS6602T
l AS6604T
l AS7116RDX
l AS7112RDX

Transporter Only

l AS1002T
l AS1002T v2
l AS1004T
l AS1004T v2
For minimum hardware requirements, refer to “Network Attached Storage” on page 140.

- 147 -
Supported NETGEAR NAS Devices
NAKIVO Backup & Replication supports the following NETGEAR NAS devices:

Director and Onboard Transporter

l RN51600
l RN51661D
l RN51661E
l RN51662D
l RN51662E
l RN51663D
l RN51663E
l RN51664E
l ReadyNAS 524X
l ReadyNAS 526X
l ReadyNAS 528X
l ReadyNAS 626X
l ReadyNAS 628X
l RN716X
l RN628X
l RN626X
l RN528X
l RN526X
l RN524X
l RN31600
l RN31661D
l RN31661E
l RN31662D
l RN31662E
l RN31663D
l RN31663E
l RN31664E
l ReadyNAS 422
l ReadyNAS 424
l ReadyNAS 426
l ReadyNAS 428
l RN516
l RN426
l RN424
l RN422
l RN31400

- 148 -
l RN31421D
l RN31441D
l RN31441E
l RN31442D
l RN31442E
l RN31443D
l RN31443E
l RN316
l RN31200
l RN31211D
l RN31212D
l RN31221D
l RN31221E
l RN31222D
l RN31222E
l RN31223D
l RN314
l RN312
l RN322121E
l RN322122E
l RN322123E
l RN322124E
l RN32261E
l RN32262E
l RN32263E
l RN4220S
l RN4220X
l RN422X122
l RN422X123
l RN422X124
l RN422X62E
l RN422X63E
l RN422X64E
l RR2304
l RN21241D
l RN21241E
l RN21243D
l RN21243E
l RN3130
l RN31342E
l RN3138
l RN3220
l RR2312

- 149 -
 l RR3312
l RN4220
l RR4312X
l RR4312S
l RR4360X
l RR4360S

Transporter Only

l RN102
l RN10200
l RN10211D
l RN10221D
l RN10222D
l RN10223D
l RN104
l RN10400
l RN10421D
l RN10441D
l RN10442D
l RN10443D
For minimum hardware requirements, refer to “Network Attached Storage” on page 140

- 150 -
Supported QNAP NAS Devices
NAKIVO Backup & Replication supports the following QNAP NAS Devices:

Director and Onboard Transporter

l HS-251+
l HS-453DX
l TS-251
l TS-251+
l TS-251A
l TS-251B
l TS-253Be
l TS-328
l TS-332X
l TS-351
l TS-431P
l TS-431P2
l TS-431X
l TS-431X2
l TS-431XeU
l TS-432XU
l TS-432XU-RP
l TS-451
l TS-451+
l TS-451A
l IS-400 Pro
l IS-453S
l TBS-453A
l TBS-453DX
l TS-128A
l TS-131P
l TS-231P
l TS-231P2
l TS-253 Pro
l TS-253A
l TS-253B
l TS-228A
l TS-451U
l TS-453 mini
l TS-453 Pro
l TS-453A

- 151 -
l TS-453B
l TS-453Be
l TS-453Bmini
l TS-453BT3
l TS-453BU
l TS-453BU-RP
l TS-453U
l TS-453U-RP
l TS-463U
l TS-463U-RP
l TS-463XU
l TS-463XU-RP
l TS-473
l TS-563
l TS-653 Pro
l TS-653A
l TS-653B
l TS-653B
l TS-673
l TS-677
l TS-832X
l TS-832XU
l TS-832XU-RP
l TS-853 Pro
l TS-853A
l TS-853BU
l TS-853BU-RP
l TS-853U
l TS-853U-RP
l TS-863U
l TS-863U-RP
l TS-863XU
l TS-863XU-RP
l TS-873
l TS-873U
l TS-873U-RP
l TS-877
l TS-877XU
l TS-877XU-RP
l TS-883XU
l TS-883XU-RP
l TS-932X
l TS-963X

- 152 -
l TS-977XU
l TS-977XU-RP
l TS-983XU
l TS-983XU-RP
l TS-1232XU
l TS-1232XU-RP
l TS-1253BU
l TS-1253BU-RP
l TS-1253U
l TS-1253U-RP
l TS-1263U-RP
l TS-1263U
l TS-1263XU
l TS-1263XU-RP
l TS-1273U
l TS-1273U-RP
l TS-1277
l TS-1277XU-RP
l TS-1283XU-RP
l TS-1635AX
l TS-1673U
l TS-1673U-RP
l TS-1677X
l TS-1677XU-RP
l TS-1683XU-RP
l TS-1685
l TS-2477XU-RP
l TS-2483XU-RP
l TVS-463
l TVS-471
l TVS-472XT
l TVS-473e
l TVS-473
l TVS-663
l TVS-671
l TVS-672XT
l TVS-673
l TVS-673e
l TVS-682
l TVS-682T
l TVS-863
l TVS-863+
l TVS-871

- 153 -
l TVS-871T
l TVS-871U-RP
l TVS-872XT
l TVS-872XU
l TVS-872XU-RP
l TVS-873e
l TVS-873
l TVS-882
l TVS-882T
l TVS-882ST2
l TVS-882BR
l TVS-882BRT3
l TVS-882ST3
l TVS-951X
l TVS-972XU
l TVS-972XU-RP
l TVS-1271U-RP
l TVS-1272XU-RP
l TVS-1282
l TVS-1282T
l TVS-1282T3
l TVS-1582TU
l TVS-1672XU-RP
l TVS-2472XU-RP
l SS-EC1279U-SAS-RP
l SS-EC1879U-SAS-RP
l SS-EC2479U-SAS-RP
l TDS-16489U
l TES-3085U
l TES-1885U
l TS-EC880U
l TS-EC880U R2
l TS-EC1280U
l TS-EC1280U R2
l TS-EC1680U
l TS-EC1680U R2
l TS-EC2480U
l TS-EC2480U R2
l TVS-EC880
l TVS-EC1080
l TVS-EC1080+
l TVS-EC1280U-SAS-RP
l TVS-EC1580MU-SAS-RP

- 154 -
l TVS-EC1680U-SAS-RP
l TVS-EC1680U-SAS-RP R2
l TVS-EC2480U-SAS-RP
l TVS-EC2480U-SAS-RP R2
l TVS-EC2480U-SAS-RP R2
l TVS-EC1580MU-SAS-RP R2
l TVS-EC1280U-SAS-RP R2
l TDS-16489U-SE1-R2
l TDS-16489U-SE2-R2
l TDS-16489U-SF2-R2
l TDS-16489U-SF3-R2
l TS-2888X-W2195-512G
l TS-2888X-W2195-256G
l TS-2888X-W2195-128G
l TS-2888X-W2175-512G
l TS-2888X-W2175-256G
l TS-2888X-W2175-128G
l TS-2888X-W2145-512G
l TS-2888X-W2145-256G
l TS-2888X-W2145-128G
l TS-2888X-W2133-64G
l TS-2888X-W2123-32G
l ES2486dc
l TS-1886XU-RP
l TS-230
l TS-251C
l TS-251D
l TS-253D
l TS-451DeU
l TS-453D
l TS-653B
l TS-653D
l TS-h1277XU-RP
l TS-h1283XU-RP
l TS-h977XU-RP
l TVS-472XT-PT
l TVS-672N
l TVS-872N
l TVS-EC2480U-SAS-RP-R2
l TS-431P3
l TS-231P3
l TS-431X3
l TS-h686-D1602

- 155 -
 l TS-h886-D1622
l TS-873AU
l TS-873AU-RP
l TS-1273AU-RP
l TS-1673AU-RP
l TS-932PX
l GM-1001
l TS-432PXU
l TS-432PXU-RP
l TS-832PXU
l TS-832PXU-RP
l TS-1232PXU-RP
l TS-451D2
l TS-h2490FU-7232P-64G
l TS-h2490FU-7302P-128G

Transporter Only

l TS-131P
l TS-231P
l TS-431P
l TS-431X
For minimum hardware requirements, refer to “Network Attached Storage” on page 140.

- 156 -
Supported Synology NAS Devices
NAKIVO Backup & Replication supports the following Synology NAS devices:

Director and Onboard Transporter

l FS3017
l FS2017
l FS1018
l RS18017xs+
l RS18016xs+
l RS10613xs+
l RS4017xs+
l RS3618xs
l RS3617xs+
l RS3617RPxs
l RS3617xs
l RS3614xs+
l RS3614RPxs
l RS3614xs
l RS3413xs+
l RS3412RPxs
l RS3412xs
l RS3411RPxs
l RS3411xs
l RS2818RP+
l RS2418RP+
l RS2418+
l RS2416RP+
l RS2416+
l RS2414RP+
l RS2414+
l RS2212RP+
l RS2212+
l RS2211RP+
l RS2211+
l RS1619xs+
l RS1219+
l RS818RP+
l RS818+
l RS816
l RS815RP+

- 157 -
l RS815+
l RS815
l RS814RP+
l RS814+
l RS814
l RS812RP+
l RS812+
l RS812
l RS810RP+
l RS810+
l RC18015xs+
l DS3617xs
l DS3615xs
l DS3612xs
l DS3611xs
l DS3018xs
l DS2415+
l DS2413+
l DS2411+
l DS2015xs
l DS1819+
l DS1817+
l DS1817
l DS1815+
l DS1813+
l DS1812+
l DS1618+
l DS1517+
l DS1517
l DS1515+
l DS1515
l DS1513+
l DS1512+
l DS1511+
l DS1010+
l DS918+
l DS916+
l DS718+
l DS716+II
l DS716+
l DS715
l DS713+
l DS712+

- 158 -
l DS710+
l DS418
l DS418play
l DS418j
l DS416
l DS416play
l DS415+
l DS414
l DS412+
l DS411+II
l DS411+
l DS218+
l DS218
l DS218play
l DS216+II
l DS216+
l DS216play
l DS215+
l DS214+
l DS118
l DS116
l DS1019+
l DS2419+
l DS420+
l DS420j
l DS620slim
l DS720+
l DS920+
l FS3400
l FS3600
l FS6400
l RS819
l RS820+
l RS820RP+
l SA3200D
l SA3400
l SA3600
l DS1520+
l DS1621+
l DS1621xs+

- 159 -
Transporter Only

l RS217
l RS214
l DS416slim
l DS416j
l DS414slim
l DS414j
l DS218j
l DS216
l DS216j
l DS215j
l DS214
l DS213j
l DS115
l DS114
l DS220j
l DS419slim
Important
Backup and recovery of Microsoft 365 accounts is not supported on Synology NAS devices with ARMv8 CPU
architecture.
For minimum hardware requirements, refer to “Network Attached Storage” on page 140.

- 160 -
Supported Western Digital NAS Devices
NAKIVO Backup & Replication supports the following Western Digital NAS devices for Director and Onboard installation:
l MyCloud DL2100
l MyCloud DL4100
l MyCloud PR2100
l MyCloud PR4100
For minimum hardware requirements, refer to “Network Attached Storage” on page 140.

- 161 -
Feature Requirements
Some NAKIVO Backup & Replication features require certain conditions in order to function properly. To learn about the
limitations of NAKIVO Backup & Replication, refer to the Feature Limitations section of the latest Release Notes. The
requirements for product features are listed below.
l Hot Add
l File Recovery
l Object Recovery and Log Truncation for Microsoft Exchange Server
l Object Recovery and Log Truncation for Microsoft SQL Server
l Object Recovery for Microsoft Active Directory
l Site Recovery
l Cross-Platform Recovery
l App-Aware Mode
l Encrypted Backup Repository
l Native Tape Support

Hot Add
In order for the Hot Add feature to work for VMware VM backup, replication, and recovery, the following requirements
must be met:
l The Transporter that will be reading or writing data from/to the VM disks should run on a VM.
l The Transporter VM should:
l Be available in the product Inventory,

l Run on a host that has access to the datastore(s) with the VM disks, Run in the same datacenter as the VM

that is to be processed.
A single SCSI controller on the VM hosting NAKIVO Backup & Replication can support up to 15 disks including the
system disk of the VM with NAKIVO Backup & Replication and mounted disks of the Backup Repository. To process VMs
with a total number of disks that is larger than that limit, it is necessary to install one or more additional SCSI
controllers.

File Recovery
Recovered files can be downloaded or sent via email. They can also be recovered to a server. Below are the
requirements which must be met for every recovery method.

Downloading Files to Browser or Sending Files via Email

l The following file systems are supported:

If the Transporter assigned to the backup repository is installed on Windows:
l NTFS

l FAT32

- 162 -
 l ReFS

If the Transporter assigned to the backup repository is installed on Linux:

l NTFS

l FAT32

l EXT3

l EXT4

l XFS

l For the ReiserFS file system, it is necessary to install the linux-image-extra-virtual package: apt-
get -y install linux-image-extra-virtualfor Ubuntu.
l Linux VMs where Transporter is deployed should have the lvm2 package installed to allow mounting LVM
volumes.
l The ntfs-3g package should be installed along with Transporter on Linux to allow recognizing NTFS par-
titions.

Recovering Files to Server

To recover files to a server, make sure you meet the following requirements:
Supported OS
l Windows
l Windows Server 2019 Standard (x64)

l Windows Server 2016 Standard (x64)

l Windows Server 2012 R2 Standard (x64)

l Windows Server 2012 Standard (x64)

l Windows Server 2008 R2 Standard (x64)

l Windows Server 2008 R2 Standard 32-bit

l Windows 10 Professional (x64)

l Windows 8 Professional (x64)

l Windows 8 Professional (x32)

l Windows 7 Professional (x64)

l Windows 7 Professional (x32)

l Linux
l Ubuntu 18.04. Server (x64)

l Ubuntu 16.04 Server (x64)

l Ubuntu 16.04 Server (x32)

l Ubuntu 12.04 Server (x64)

l Ubuntu 12.04 Server (x32)

l SUSE Linux Enterprise Server 12 SP3 (x64)

l SUSE Linux Enterprise Server 12 SP2 (x64)

l SUSE Linux Enterprise Server 12 SP1 (x64)

l SUSE Linux Enterprise Server 11 SP4 (x64)

l SUSE Linux Enterprise Server 11 SP4 (x32)

l SUSE Linux Enterprise Server 11 SP3 (x64)

- 163 -
 l SUSE Linux Enterprise Server 11 SP3 (x32)
l Red Hat Enterprise Linux 7.4 (x64)
l Red Hat Enterprise Linux 7.3 (x64)
l Red Hat Enterprise Linux 7.2 (x64)
l Red Hat Enterprise Linux 7.1 (x64)
l Red Hat Enterprise Linux 7.0 (x64)
l CentOS Linux 7.6 (x64)
l CentOS Linux 7.5 (x64)
l CentOS Linux 7.4 (x64)
l CentOS Linux 7.3 (x64)
l CentOS Linux 7.2 (x64)
l CentOS Linux 7.1 (x64)
l CentOS Linux 7.0 (x64)
TCP Ports
Connection to the following TCP ports should be allowed by the firewall of the target system:
l 22 – Used by SSH for secure logins, file transfers (scp, sftp) and port forwarding.
l 9445 – Used by NAKIVO Backup & Replication to communicate with the VM.
l 10000 – Used by NAKIVO Backup & Replication for iSCSI communication.
Note
ICMP Ping traffic should be allowed by the firewall of the target system.
Services and packages
The following packages and services should be installed/running:
Microsoft Windows
l Net Security package should be installed
l Microsoft iSCSI Initiator service should be installed and running
l net.exe utility should be installed
l SMB 2 / CIFS File Sharing Support feature should be turned on
l PowerShell should have version 2.0 or above
l PowerShell ISE should be available
Ubuntu Linux
l openssh-server package should be installed
l sshd service should be running
l parted utility should be installed
l fdisk utility should be installed
l open-iscsi package should be installed
l iscsiadm utility should be installed
l iscsid utility should be installed
l iscsid service should be running (for v16.04 and v18.04)
SUSE Linux Enterprise Server (SLES)

- 164 -
 l openssh-server package should be installed
l sshd service should be running
l parted utility should be installed
l fdisk utility should be installed
l open-iscsi package should be installed
l iscsiadm utility should be installed
l iscsid utility should be installed
l iscsid service should be running (for v12)
Red Hat Enterprise Linux (RHEL)
l openssh-server package should be installed
l sshd service should be running
l parted utility should be installed
l fdisk utility should be installed
l iscsi-initiator package should be installed
l iscsiadm utility should be installed
l iscsid utility should be installed
l iscsid service should be running
Permissions
The following permissions for Microsoft Windows VMs should be granted:
l Users should be members of a local Administrators group.
l Users should have access to default administrative shares.
l Users should have permissions to access the corresponding folder\file.
l Users should have executive permissions for running some utilities, for example, net.exe utility.
l User Account Control (UAC) remote restrictions should be disabled for some Microsoft Windows versions.
l Users should have permissions to "Log on as a batch job".
The following permissions and settings should be set up for Linux VMs:
l Users should belong to the sudo group to complete recovering files to server successfully.
l Users should have executive permissions for running some utilities, for example, /sbin/parted, /sbin/fdisk, /sbin
/iscsiadm, /sbin/iscsid.
l PasswordAuthentication should be set to "yes".
l Provide special permissions to NAKIVO recovery service. For more details, refer to Required Permissions for Linux
Recovery Server.

Object Recovery and Log Truncation for Microsoft Exchange

To successfully perform object recovery and log truncation for Microsoft Exchange, make sure you meet the following
requirements:
Supported Microsoft Exchange versions
NAKIVO Backup & Replication supports the following versions of Microsoft Exchange for object recovery and log
truncation:

- 165 -
 l Microsoft Exchange 2019
l Microsoft Exchange 2016
l Microsoft Exchange 2013
Permissions
The following requirements should be met for log truncation:
l Selected users should have permissions to "Log on as a batch job".
l The following user permissions should be provided:
l If NAKIVO Backup & Replication uses the administrator user account, it should belong to the following

groups:
l Administrators

l Domain Users

l Organization Management

l If NAKIVO Backup & Replication uses accounts other than the administrator user account:

l The user should belong to the following groups:

l Administrators

l Domain Users

l Organizational Management

l The user should have the Full control permission granted for the folder in which the Exchange data-

base is located.
Services and Settings
NAKIVO Backup & Replication requires PowerShell v2 or later to be available on the Microsoft Exchange machine.
l VMware VM must be running on VMware ESXi 5.0 and later.
l VMware Tools or Hyper-V Integration Services must be running on VMware or Hyper-V VMs correspondingly.

Object Recovery and Log Truncation for Microsoft SQL Server

To successfully perform object recovery and log truncation for a Microsoft SQL Server, you must meet general
requirements as well as requirements for object recovery and log truncation.
General Requirements
To successfully perform object recovery and log truncation for a Microsoft SQL Server, make sure you meet the
following general requirements:
Supported Versions of Microsoft SQL Server
NAKIVO Backup & Replication supports the following versions of Microsoft SQL Server for object recovery and log
truncation:
l Microsoft SQL Server 2019
l Microsoft SQL Server 2017
l Microsoft SQL Server 2016
l Microsoft SQL Server 2014
l Microsoft SQL Server 2012
l Microsoft SQL Server 2008 R2
l Microsoft SQL Server 2008

- 166 -
Permissions
l A user logging in to Microsoft SQL Server must have a sysadmin role.
l The user running Microsoft SQL Service should have permissions to "Log on as a batch job".
Services and Settings
l NAKIVO Backup & Replication requires PowerShell v2 or later.
l VMware Tools or Hyper-V Integration Services must be running on VMware or Hyper-V VMs correspondingly.
l sqlcmd utility must be installed on the machine running Microsoft SQL server.
l Ports 137-139 must be opened for cifs.
l The SMB 2 protocol should be enabled.

Requirements for Microsoft SQL Server Object Recovery

l The user running Microsoft SQL service must have executive permissions to the Data folder and all other folders
in which the databases are located.
l If "Rename recovered item if such item exists" option is selected during the recovery, NAKIVO Backup & Rep-
lication skips keys, constraints, indexes, and statistical properties when recovering a table to an original location.
l If "Overwrite the original item if such item exists" option is chosen, all the above properties are preserved. Tables
that contain a foreign key cannot be recovered with this option.
l Full administrative permissions are required.
l Default administrative shares must be enabled.
l The "File server" role must be enabled.
l Ports 445 and 9445 must be opened on the instance.

Requirements for Microsoft SQL Server Log Truncation

l VMware VM must be running on VMware ESXi 5.0 and later.

l System databases are skipped during the log truncation.
l Databases with the "Simple" recovery model are skipped during the log truncation.
l A database must be in the "online" state.
l The SMB 2 protocol should be enabled.

Object Recovery for Microsoft Active Directory

Supported Versions

NAKIVO Backup & Replication supports the following versions of Microsoft Active Directory for objects recovery:
l Windows Server 2019
l Windows Server 2016
l Windows Server 2012 R2 Windows Server 2012
l Windows Server 2008 R2

- 167 -
Requirements for Object Recovery for Microsoft Active Directory

l The ISCI Initiator service must be running on the recovery server.

l The vc_redist.x86.exe (v.2015) file must be installed on the recovery server.

Site Recovery
To successfully perform a site recovery, make sure you meet the following requirements:
Run Script Action
The list of supported operating systems where the Run Script action may be run can be found in the Recovering Files to
Server subsection above.
TCP ports
Connection to the following TCP ports should be allowed by the firewall of the target system:
l 22 – Used by SSH for secure logins, file transfers (scp, sftp) and port forwarding.
l 9445 – Used by NAKIVO Backup & Replication to communicate with the VM.
Note
ICMP ping traffic should be allowed by the firewall of the target system.
Required permissions for Microsoft Windows VMs:
l Users should be members of a local Administrators group.
l Users should have access to default administrative shares.
l Users should have permissions to access the corresponding folder/file.
l User Account Control (UAC) remote restrictions should be disabled for some Microsoft Windows versions.
l Users should have permissions to "Log on as a batch job".
Services and Settings
l For Windows source VMs, the SMB 2 / CIFS File Sharing Support feature should be turned on.
l For Linux VMs, users should belong to the sudo group.
l VMware Tools or Hyper-V Integration Services must be running on VMware or Hyper-V VMs, respectively.

Cross-Platform Recovery
The following scenarios are supported if a VM is exported from backup and imported into a different hypervisor:

Target Platforms

Source Platforms VMware vSphere 6.7 Microsoft Hyper-V 2016/2019

l Windows Server 2016/2019 l Windows Server 2016/2019

VMware vSphere 6.7 l Ubuntu Server 18.04 l Ubuntu Server 18.04
l RHEL 7 l RHEL 7*

l Windows Server 2016/2019 l Windows Server 2016/2019

Microsoft Hyper-V 2016/2019
l Ubuntu Server 18.04 l Ubuntu Server 18.04

- 168 -
 l RHEL 7 l RHEL 7

l Windows Server 2016/2019 l Windows Server 2016/2019

Physical Machines l Ubuntu Server 18.04 l Ubuntu Server 18.04
l RHEL 7 l RHEL 7

* To run a VM with RHEL 7 on Microsoft Hyper-V 2016/2019, the following option must be configured in grub boot
parameters:
ata_piix.prefer_ms_hyperv=0
As an alternative, the source machine can be pre-configured with the command below:
mkinitrd -f -v --with=hid-hyperv --with=hv_utils --with=hv_vmbus --with=hv_storvsc --with=hv_netvsc /boot/initramfs-
$(uname -r).img $(uname -r)

App-aware Mode
To enable application awareness for source objects, make sure the following requirements are met:

VMware

l VMware Tools should be installed, running, and up to date on all source VMs.

Encrypted Backup Repository

To enable encryption, the following requirements should be met:
l The Transporter assigned to the encrypted backup repository must be installed on Ubuntu, SLES or RHEL. Cur-
rently, Transporters installed on other Linux versions, Windows, and NAS do not support this feature.
l For certain SLES and RHEL versions, only full device/partition encryption is available. Learn more.

Native Tape Support

NAKIVO Backup & Replication supports tape environments with the following configurations:
l Robotic tape libraries and standalone devices of LTO3 and later generations.
l AWS Storage Gateway service with a Tape Gateway that functions as a Virtual Tape Library (VTL).
l Only VTLs connected to Linux are currently supported.
l  The gateway VM deployed on-premises needs to have the following minimum resources:
l Four virtual processors.

l 16 GiB of reserved RAM.

l 80 GiB of disk space for the installation of VM image and system data.

l According to the requirements for Amazon EC2 instances, when deploying the gateway on Amazon EC2, the
instance size should be at least 2xlarge for the compute-optimized instance family.
l The instance type should be c4 or c5 instance types. The 2xlarge instance size or higher can be chosen to meet the
required RAM requirements.
l All physical tape cartridges must have barcodes.

- 169 -
l Installation is supported on all Windows OS and Linux OS, as listed on the Supported Platforms page.
l Installation on NAS OS is not supported.

- 170 -
Deployment Scenarios
NAKIVO Backup & Replication is a modular solution that can be fully installed on a single machine to protect small and
mid-sized environments, as well as scale out horizontally and support large distributed environments. Refer to the
sections below to learn more about the product deployment scenarios.
l “Single Site Deployment” on page 172
l “Distributed Deployment” on page 173
l “Multi-Tenant Deployment” on page 174

- 171 -
Single Site Deployment
For a single site deployment, it is often sufficient to install both the Director and Transporter on a single VM/physical
machine within your infrastructure.

This deployment provides you with the ability to back up, replicate, and recover multiple VMs from multiple source
hosts.

- 172 -
Distributed Deployment
If you have multiple sites and need to back up and/or replicate over WAN, install the Director and Transporter on one
site, and at least one Transporter on all other sites.

Note
Make sure the required ports are open on the appropriate endpoints. The full list of required ports can be found in
Deployment Requirements.

- 173 -
Multi-Tenant Deployment
Installation of a multi-tenant solution of NAKIVO Backup & Replication allows you to create multiple isolated tenants
within a single product deployment and manage them from a single pane of glass. In the Multi-Tenant mode, tenants
can access the self-service portal to offload backup, replication, and recovery tasks from the service provider.
For more information, refer to these topics:
l “Backup from a Remote Site to a Master Site” on page 175
l “Replication from a Remote Site to a Master Site” on page 177
l “Local Backup at Remote Site” on page 179
l “Local Replication at Remote Site” on page 181
l “Backup at Master Site” on page 183
l “Replication at Master Site” on page 185
l “Multi-Tenant Mode” on page 730

- 174 -
Backup from a Remote Site to a Master Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running at remote sites and are backed up to a single master site.
Example
A service provider needs to back up customers' VMs to the service provider’s datacenter so that the customers don’t
see each other’s backups and can recover their own files and emails through a self-service interface.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

Deployment Steps

To deploy the above scenario, perform the following steps:

- 175 -
 1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at the master site.
3. Install at least one Transporter at each remote site.
4. For each tenant, prepare a separate folder at the master site for creating separate Backup Repositories.

Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
A source VMs at remote sites. The port used for communication with vCenter servers and ESXi hosts (443 by
default) is open in firewalls.

Connection from the machine on which the Director is installed to machines at remote sites on which Trans-
B porters are installed. The port used for communication with the Transporters (9446 by default) is open in fire-
walls.

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts at the
C master site where VM replicas will be created. The port used for communication with vCenter servers and
ESXi hosts (443 by default) is open in firewalls.

Connection from the machine on which the Director is installed to the machine at the master site where the
D Transporter is installed. The port used for communication with the Transporters (9446 by default) is open in
firewalls.

Connection from the machine at the Master site where the Transporter is installed to ESXi hosts at the mas-
E
ter site where VM replicas will be created.

Connection from the machine at the Master site where the Transporter is installed to machines at remote
F sites where Transporters are installed. The ports used for data transfer between a pair of Transporters are
open in firewalls.

At remote sites, connections from machines on which Transporters are installed to vCenter servers and
G
ESXi hosts running source VMs.

Note
For security purposes, a VPN connection should be established between the master site and remote sites.

- 176 -
Replication from a Remote Site to a Master Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running at remote sites and are replicated to a single master site.
Example
A service provider wants to introduce Replication-as-a-Service to customers and replicate their VMs to the service
provider’s datacenter.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

Deployment Steps

To deploy the above scenario, perform the following steps:

- 177 -
 1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at the master site.
3. Install at least one Transporter at each remote site.
4. For each tenant, prepare a separate ESXi host that will serve as a replication target.

Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
A source VMs at remote sites. The port used for communication with vCenter servers and ESXi hosts (443 by
default) is open in firewalls.

Connection from the machine on which the Director is installed to machines at remote sites on which Trans-
B porters are installed. The port used for communication with the Transporters (9446 by default) is open in fire-
walls.

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts at the
C master site where VM replicas will be created. The port used for communication with vCenter servers and
ESXi hosts (443 by default) is open in firewalls.

Connection from the machine on which the Director is installed to the machine at the master site where the
D Transporter is installed. The port used for communication with the Transporters (9446 by default) is open in
firewalls.

Connection from the machine at the master site where the Transporter is installed to ESXi hosts at the mas-
E
ter site where VM replicas will be created.

Connection from the machine at the master site where the Transporter is installed to machines at remote
F sites where Transporters are installed. The ports used for data transfer between a pair of Transporters are
open in firewalls.

At remote sites, connections from machines on which Transporters are installed to vCenter servers and
G
ESXi hosts running source VMs.

Note
For security purposes, a VPN connection should be established between the master site and remote sites.

- 178 -
Local Backup at Remote Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running and backed up locally at the remote sites.
Example
An Enterprise has two branch offices running VMware virtual infrastructure. The IT manager located at the
headquarters is responsible for the Enterprise data protection and needs to back up VMs locally at their branch offices
to ensure fast operational recovery. Employees of the branch offices should have access to their VM backups and be
able to recover their files and emails.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

- 179 -
Deployment Steps

To deploy the above scenario, perform the following steps:

1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at each remote site.
3. For each tenant, prepare a separate folder at a remote site for creating a Backup Repository.

Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
A source VMs at remote sites. The port used for communication with vCenter servers and ESXi hosts (443 by
default) is open in firewalls.

Connection from the machine on which the Director is installed to machines at remote sites where the Trans-
B porters are installed. The port used for communication with the Transporters (9446 by default) is open in fire-
walls.

Connection from the machines on which the Transporters are installed at remote sites to vCenter servers
C
and ESXi hosts running source VMs.

Note
For security purposes, a VPN connection should be established between the master site and remote sites.

- 180 -
Local Replication at Remote Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running and replicated locally at the remote sites.
Example
An Enterprise has two branch offices running VMware virtual infrastructure. The IT manager located at the
headquarters is responsible for the Enterprise data protection and needs to replicate business critical VMs locally at the
branch offices for high availability.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

Deployment Steps

To deploy the above scenario, perform the following steps:

1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at each remote site.
3. For each tenant, prepare a separate folder at the remote site for creating a Backup Repository.

- 181 -
Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
A source VMs at remote sites. The port used for communication with vCenter servers and ESXi hosts (443 by
default) is open in firewalls.

Connection from the machine on which the Director is installed to machines at remote sites where Trans-
B porters are installed. The port used for communication with the Transporters (9446 by default) is open in fire-
walls.

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts where
C VM replicas will be created at remote sites. The port used for communication with vCenter servers and ESXi
hosts (443 by default) is open in firewalls.

At remote sites, connections from machines where Transporters are installed to vCenter servers and ESXi
D
hosts running source VMs.

At remote sites, connections from machines where Transporters are installed to vCenter servers and ESXi
E
hosts where VM replicas will be created.

Note
For security purposes, a VPN connection should be established between the master site and remote sites.

- 182 -
Backup at Master Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running at the master site and the backing up of tenant VMs is also performed at the
master site.
Example
A service provider runs VMs of customer A and customer B in the service provider’s datacenter. The Service Provider
seeks to offer Backup-as-a-Service to both customers. The customers should be able to recover their files and emails
through a self-service interface without being able to see each other’s backups.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

Deployment Steps

To deploy the above scenario, perform the following steps:

1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at the master site.

- 183 -
 3. For each tenant, prepare a separate folder at the master site for creating a Backup Repository.

Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to the machine on which the Transporter is
A
installed. The port used for communication with the Transporters (9446 by default) is open in firewalls.

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
B source VMs. The port used for communication with vCenter servers and ESXi hosts (443 by default) is open
in firewalls.

Connection from the machine on which the Transporter is installed to vCenter servers and ESXi hosts run-
C
ning source VMs.

Connection from the machine on which the Transporter is installed to the folders where tenant Backup
D
Repositories will be created.

Note
For security purposes, a VPN connection should be established between the master site and remote sites.

- 184 -
Replication at Master Site
l Deployment Scenario
l Deployment Diagram
l Deployment Steps
l Connections

Deployment Scenario

In this scenario, tenant VMs are running at the Master site and the replication of tenant VMs is also performed at the
Master site.
Example
A service provider runs customers' VMs in the service provider’s datacenter. To ensure high availability of tenant VMs,
the service provider seeks to replicate customer VMs to a different server.

Deployment Diagram

The deployment diagram for the above scenario is as follows:

Deployment Steps

To deploy the above scenario, perform the following steps:

1. Install the Director in multi-tenant mode at the master site.
2. Install at least one Transporter at the master site.
3. For each tenant, prepare a separate ESXi host that will serve as a replication target.

- 185 -
Connections

The implementation of the above scenario requires that the following connections be available:
Connection Description

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts that run
A source VMs. The port used for communication with vCenter servers and ESXi hosts (443 by default) is open
in firewalls.

Connection from the machine on which the Director is installed to the machine on which the Transporter is
B
installed. The port used for communication with the Transporters (9446 by default) is open in firewalls.

Connection from the machine on which the Director is installed to vCenter servers and ESXi hosts where
C VM replicas will be created. The port used for communication with vCenter servers and ESXi hosts (443 by
default) is open in firewalls.

Connection from the machine on which the Transporter is installed to vCenter servers and ESXi hosts run-
D
ning source VMs.

Connection from the machine on which the Transporter is installed to vCenter servers and ESXi hosts where
E
VM replicas will be created.

- 186 -
Installing NAKIVO Backup and Replication
Refer to the sections below to learn how to install NAKIVO Backup & Replication:
l “Deploying VMware Virtual Appliance” on page 188
l “Deploying Nutanix AHV Virtual Appliance” on page 202
l “Installing on Windows” on page 210
l “Installing on Linux” on page 217
l “Installing on Synology NAS” on page 224
l “Installing on QNAP NAS” on page 230
l “Installing on Western Digital NAS” on page 240
l “Installing on ASUSTOR NAS” on page 235
l “Installing on NETGEAR ReadyNAS” on page 242
l “Installing on Generic ARM-based Device” on page 245
l “Deploying Amazon Machine Image in Amazon EC2” on page 209
l “Installing on FreeNAS” on page 246
l “Installing on Raspberry Pi” on page 247

- 187 -
Deploying VMware Virtual Appliance
l Deploying Virtual Appliance with vSphere Web Client
l Deploying Virtual Appliance with vSphere Client
l Virtual Appliance OS and Credentials
l Web Interface Login
NAKIVO Backup & Replication offers the following VA deployment options:
l Full Solution
l Full Solution without Backup Repository
l Transporter-only
l Transporter with Backup Repository
l Multi-tenant Director  
The Virtual Appliance (VA) has two disks: the first (30 GB) contains a Linux OS with NAKIVO Backup & Replication, and the
second (500 GB) is used as a Backup Repository. If you deploy the Virtual Appliance disks using the Thin
Provision option, then the disks will not reserve space on your datastore and will only consume space when actual data
(such as your backups) is written to disks.

Deploying Virtual Appliance with vSphere Web Client

1. Download NAKIVO Backup & Replication VA. 
2. Log in to your vSphere vCenter with the vSphere Web Client.
3. Select Deploy OVF Template from the Actions menu. Note that the Client Integration Plug-in must be installed
to enable OVF functionality. 

4. On the Select an OVF template page of the Deploy OVF Template wizard, select Local file and upload the VA file
(.ova) you've downloaded. Click Next. 

- 188 -
5. On the Select a name and folder page, specify a unique name and target location for the Virtual Appliance.
Click Next.

6. On the Select a computer resource page, select the resource pool within which you would like to deploy the
Virtual Appliance and click Next.

- 189 -
7. On the Review details page, review the template details and click Next.

8. On the License agreements page, read the end-user license agreement (EULA). If you agree to its terms, select I

- 190 -
 accept all license agreements and then click Next.

9. On the Select storage page, select a datastore in which you would like to keep the Virtual Appliance disk, virtual
disk format (Thin Provisioning is recommended), VM storage policy and click Next.
Important
If you use thick provisioning instead of thin provisioning, keep in mind that NAKIVO Backup & Replication can
take up to 0,5 TB of data. Check to see if it is 0,5 TB by default for all cases.

- 191 -
10. On the Select networks page, select a network to which the Virtual Appliance will be connected. Opting for a
network with DHCP and Internet access is recommended. Click Next.

- 192 -
 11. On the Ready to complete page, review the summary of the setups you have configured and click Finish to
complete deployment.

After the Virtual Appliance is deployed, you may need to configure it.
Important
If you plan to expose the Virtual Appliance to the Internet, change the default credentials and set up a login and
password for the Web interface

Deploying Virtual Appliance with vSphere Client

1. Download NAKIVO Backup & Replication VA. 
2. Log in to your vSphere vCenter with the vSphere Client, go to File in the top menu and select Deploy OV
Template.

- 193 -
3. On the Source page of the Deploy OVF Template wizard, select and locate the file with the template. Click Next.
4. On the OVF Template Details page, review the template details and click Next.

5. On the End User License Agreement page, read the license agreement. If you agree to its terms, click Accept and

- 194 -
 then click Next.

6. On the Name and Location page, specify a name and location for the deployed VA and click Next.

- 195 -
7. On the Host/Cluster page, select the host or cluster on which you wish to run the deployed template and
click Next.

- 196 -
8. On the Storage page, select a datastore where you would like to keep the VA disk and click Next.

- 197 -
9. On the Disk Format page, select a virtual disk format (Thin Provision is recommended) and click Next.
Important
If you wish to select one of the Thick Provision options instead of Thin Provision, keep in mind that NAKIVO
Backup & Replication can take 0,5 TB of data. Check to see if it is 0,5 TB by default for all cases.

- 198 -
10. On the Network Mapping page, select a network to which the VA will be connected. It is recommended that you
choose a network with DHCP and Internet access. Click Next.

- 199 -
11. On the Ready to Complete page, review the summary of the options you have configured and select the Power
on after deployment option.

- 200 -
 12. Click Finish to complete the deployment.
13. After the Virtual Appliance is deployed, configure it if necessary.
After the installation is complete, you can log in to NAKIVO Backup & Replication by opening the following URL in your
web browser: https://machine_IP_or_DNS:director_https_port

Virtual Appliance OS and Credentials

The appliance runs Ubuntu 18.04, 64-bit. Use the following credentials to log in to the appliance:
l Username: root
l Password: QExS-6b%3D
For the versions of NAKIVO Backup & Replication older than 7.2, the password is root.
Important
If you plan to expose the Virtual Appliance to the Internet, change the default VA credentials and set up a login and
password for the Web interface.

Web Interface Login

Open the following URL to access the product's web interface: https://Appliance_VM_IP:4443.
Refer to the  Getting Started section to better understand how to continue working with NAKIVO Backup & Replication. 

- 201 -
Deploying Nutanix AHV Virtual Appliance
l Deploying Nutanix AHV Virtual Appliance
l Virtual Appliance OS and Credentials
l Web Interface Login

Deploying Nutanix AHV Virtual Appliance

The NAKIVO Backup & Replication instance must be deployed in a Nutanix AHV cluster in order to enable backup and
recovery functions.
NAKIVO Backup & Replication offers the following solutions:
l Full Solution (Single Tenant) - requires a 100 GB thin provisioned disk
l Transporter-only - requires a 20 GB thin provisioned disk
To deploy a virtual appliance via the Nutanix Prism application, follow the steps below:
1. Download the .VMDK file with a full or transporter-only image from the Nakivo website and store it locally.
2. Log in to the Prism console.
3. From the Configurations menu, select Image Configuration.

4. In the Image Configuration dialog, click Upload Image.

- 202 -
5. In the Create Image dialog, fill in the following options:
l Name: Enter a name for the new image.
l Image Type: From the drop-down list, select DISK.
l Storage Container: Select the storage container you wish to use from the drop-down list. The list includes
all storage containers created for this cluster. If there are no storage containers currently available, a Create
Storage Container link is displayed.
l Image Source: Click the Upload a file radio button to upload a file from your workstation. Click the Choose

- 203 -
 File button and then select the file to upload from the file search window.

6. When all fields are correct, click the Save button.

After the file uploading completes, the Create Image window closes and the Image Configuration window
reappears with the new image present in the list.

Note
Make sure the status of the disk is Active before proceeding to the next step.

- 204 -
7. Close the Image Configuration window, go to the VM view and click Create VM.

8. In the Create VM dialog, fill in the following options:

l Name: Enter a name for the VM.
l vCPU(s): Enter the number of virtual CPUs to allocate to this VM (minimum 1).
l Number of Cores per vCPU: Enter the number of cores assigned to each virtual CPU (minimum 2).
l Memory: Enter the amount of memory (in GBs) to allocate to this VM (minimum 4 GB + 250 MB for each
concurrent job for full solution/minimum 2 GB + 250 MB for each concurrent job Transporter-only
solution).
l In the Disk section, click Add New Disk, and specify the following settings in the Add Disk dialog:
a. Type: Select Disk.
b. Operation: Select Clone from Image Service.
c. Bus Type: Select SCSI.

- 205 -
 d. Image: Select your uploaded image from the list.

l In the Network Adapters (NIC) section, click Add New NIC and select an available VLAN from the list.
9. Click Save.

- 206 -
10. Wait until the process of VM creation is complete and locate your newly-created VM on the list.
11. Select your VM and click Power On.

- 207 -
 12. After the Virtual Appliance is deployed and powered on, you may need to configure it.
After the installation is complete, you can log in to NAKIVO Backup & Replication by opening the following URL in your
web browser: https://machine_IP_or_DNS:director_https_port.

Virtual Appliance OS and Credentials

The appliance runs Ubuntu 18.04, 64-bit. Use the following credentials to log in to the appliance:
l Username: root
l Password: QExS-6b%3D
Important
If you plan to expose the Virtual Appliance to the Internet, change the default VA credentials and set up a login and
password for the Web interface.

Web Interface Login

Open the following URL to access the product's web interface: https://Appliance_VM_IP:4443.
 Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication. 

- 208 -
Deploying Amazon Machine Image in Amazon EC2
You can deploy NAKIVO Backup & Replication as a pre-configured Amazon Machine Image (AMI) in Amazon EC2. After
you fill out our download form, you will get a link to the AWS marketplace page where you can download the AMI.
Configure the following AMI parameters:
1. Instance Type: More powerful instances can process tasks faster and run more tasks simultaneously. The
minimum requirement for NAKIVO Backup & Replication is the t2.micro instance type; the t2 medium instance
type is recommended. 
2. Instance Details: Assign a public IP to the instance if you wish to access the instance from the Internet.
3. Security Group: Either use the "All Traffic" rule or create a set of rules listed below:

Type Port Range Source Description

SSH 22 0.0.0.0/0 Enables remote SSH access to the Instance

Custom TCP 80 0.0.0.0/0 Enables access to the Web interface

Custom TCP 443 0.0.0.0/0 Required for local Transporter import

Custom TCP 902 0.0.0.0/0 Required for local Transporter import

Custom TCP 4443 0.0.0.0/0 Enables access to the Web interface

Custom TCP 9446 0.0.0.0/0 Enables access to a remote Transporters

Custom TCP 9448-10000 0.0.0.0/0 Enables access to a remote Transporters

All ICMP  0-65535 0.0.0.0/0 Enables access to a remote Transporter

4. Key pair: Select an existing key pair or create a new key pair for your instance. If you select an existing key pair,
make sure you have the access to the private key file.
Refer to “Getting Started” on page 83 to understand better how to continue working with NAKIVO Backup &
Replication. 

- 209 -
Installing on Windows
NAKIVO Backup & Replication offers the following installation options for Windows machines:
l Full Solution
l Transporter-only Solution
l Multi-Tenant Solution
After successful product installation, refer to “Getting Started” on page 83 to learn how to continue working with
NAKIVO Backup & Replication. 
l Installing Full Solution on Windows
l Installing Transporter on Windows
l Transporter Installation Prerequisites

l Transporter Installation

l Installing Full Solution in Multi-Tenant Mode on Windows

l Silent Installation on Windows

Installing Full Solution on Windows

To install NAKIVO Backup & Replication with default options, simply run the NAKIVO Backup & Replication installer for
Windows and click Install. This will install all product components (Director, Transporter, Backup Repository), and you
will be able to use all product features after installation.
You can also change the installation options as follows:
1. Set the installation options as follows:
l Installation type: Leave the Full solution option selected to install the key product components 
(Director and Transporter).
l Create repository: Leave the checkbox selected to create a Backup Repository on the machine on which
NAKIVO Backup & Replication is installed.
2. Click Options to set up more installation options:
l Installation path: The location where NAKIVO Backup & Replication will be installed.
l Director Web UI port: The default port that will be used to connect to the Web UI of NAKIVO Backup &
Replication. Make sure the port you specify is open in your firewall.
l Transporter port: The default port that will be used by the Director to communicate with the Onboard
Transporter. Make sure the port you specify is open in your firewall.
l Send support bundles during evaluation: If this option is selected, NAKIVO Backup & Replication will
automatically create, encrypt, and upload support bundles once a day to a NAKIVO support server during
the evaluation period. NAKIVO Support team may use this information to improve the product experience

- 210 -
 and may be able to identify and resolve product issues faster.

3. Click Install and then click Finish once the installation is complete.

4. To prevent unauthorized access to the product, create your user account:  

l Name: Provide your name.
l Username: Create a username.
l Email: Provide your corporate email.
l Password: Create a password to access your NAKIVO Backup & Replication account.

- 211 -
 l Repeat password: Repeat the password.

You can log in to NAKIVO Backup & Replication by opening the following URL in your web browser:
https://machine_IP_or_DNS:Director_Web_UI_port

Installing Transporter on Windows

If you have already installed the full solution (both Director and Transporter) and wish to deploy an additional
Transporter, run the NAKIVO Backup & Replication installer for Windows and follow the steps below:

Transporter Installation Prerequisites

Prior to installing a Transporter, make sure the following prerequisites are met:
l Make sure the machine on which you plan to install the Transporter has a connection to the relevant items
below:
l The machine on which the Director is installed.
l VMware/Hyper-V servers on which you plan to back up or replicate VMs (provided you are planning to
retrieve VM data using the Transporter you are about to install)
l Machines on which you have installed other Transporters (provided you are planning to set up data
transfer between an existing Transporter and the one you are about to install) 
l Backup repository (provided you are planning to assign the Transporter you are going to install to a
Backup Repository)
l VMware/Hyper-V servers which you plan to use as a destination for replicated VMs (assuming you plan to
write data to the target servers and datastores using the Transporter you are about to install)
l For VMware/Hyper-V servers discovered with DNS names, make sure those DNS names can be resolved on the
machine on which to install the Transporter.

- 212 -
Transporter Installation

1. Run the NAKIVO Backup & Replication installer.

2. Choose Transporter only from the Installation type drop-down list.

3. Click Options and set up the following:

l Installation path: The location where the Transporter will be installed.
l Transporter port: The default port that will be used by the Director to communicate with the Onboard
Transporter. Make sure the port you specify is open in your firewall.

4. Click Install.
5. Click Finish once the installation is complete. 

- 213 -
 6. Add the Transporter to NAKIVO Backup & Replication.

Installing Full Solution in Multi-Tenant Mode on Windows

To install the full solution in multi-tenant mode on a Windows OS, run the NAKIVO Backup & Replication installer for
Windows and follow the steps below:
1. Choose Multi-tenant solution from the Installation type drop-down list.

2. Click Options to set up more installation options:

l Installation path: The location where NAKIVO Backup & Replication will be installed.
l Director Web UI port: The default port that will be used to connect to the Web UI of NAKIVO Backup &
Replication. Make sure the port you specify is open in your firewall.
l Transporter port: The default port that will be used by the Director to communicate with the Onboard
Transporter. Make sure the port you specify is open in your firewall.
l Send support bundles during evaluation: If this option is selected, NAKIVO Backup & Replication will
automatically create, encrypt, and upload support bundles once a day to a NAKIVO support server during
the evaluation period. The NAKIVO Support team may use this information to improve the product

- 214 -
 experience and may be able to identify and resolve product issues faster.

3. Click Install and then click Finish once the installation is complete. 

You can log in to NAKIVO Backup & Replication by opening the following URL in your web
browser: https://machine_IP_or_DNS:Director_Web_UI_port.
Credentials are not required to log in as a Master Admin after installation. However, the default credentials are required
to log into the product after the first tenant is created. To log in as a Master admin, specify “admin” as the username
and leave the password field empty. You can change credentials in the product configuration.

Silent Installation on Windows 

You can install NAKIVO Backup & Replication in silent mode via a command line by running the following
command: installer.exe -f --eula-accept This will install all product components
(Director, Transporter, Backup Repository), and you will be able to use all product features after installation.
The following arguments are available:

- 215 -
Argument Description

-h Displays the list of available arguments without starting the installation.

--eula-accept, -e Indicates that you have read and agree to the End User License Agreement.

Shall perform the silent installation of the full solution (Director and
-f
Transporter).

-t Shall perform the silent installation of Transporter only.

-m Shall perform the silent installation of the full solution in multi-tenant mode.

-u Shall perform the silent update of the installed product components

- 216 -
Installing on Linux
l Linux Installation Prerequisites
l Silent Installation on Linux
l Installing Full Solution on Linux
l Installing Transporter on Linux
l Transporter Installation Prerequisites

l Transporter Installation

l Installing Full Solution in Multi-Tenant Mode on Linux

Linux Installation Prerequisites

In order to install and use NAKIVO Backup & Replication on a Linux OS, make sure the following requirements are met:
l On Ubuntu and SLES, NAKIVO Backup & Replication relies on the following packages:
l cifs-utils
l open-iscsi
l ntfs-3g
l On RedHat Enterprise Linux, NAKIVO Backup & Replication relies on the following packages:
l cifs-utils
l iscsi-initiator-utils
l ntfs-3g

Silent Installation on Linux

You can install NAKIVO Backup & Replication in silent mode via a command line. To install the full solution, simply run
the following command: installer.sh -f --eula-accept This will install all product components
(Director, Transporter, Backup Repository) and you will be able to use all product features after installation.
The following arguments are available:

Argument Description

-h, -help, help Display the list of available arguments without starting the installation.

--eula-accept, -ea Indicates that you have read and agree to the End User License Agreement.

-f Shall perform the silent installation of the full solution (Director and Transporter).

-t Shall perform the silent installation of Transporter only.

-m Shall perform the silent installation of the full solution in multi-tenant mode.

-u Shall perform the silent update of the installed product components.

- 217 -
 Argument Description

Shall install Transporter for Amazon EC2, or update Transporter installed for Amazon
-e
EC2. Refer to Updating on Amazon EC2 for details.

Shall enable uploading support bundles to support team server (Call Home). Refer to
-a
System Settings for details.

-y Shall accept limitations silently.

-i <install_path> Shall install to the specified installation path.

-d <director_port> Shall provide a custom Director port.

-p <transporter_port> Shall provide a custom Transporter port.

-r <port1>-<port2> Shall provide a custom transporter data ports range.

-C Shall suppress creating the repository.

-c <repo_path> Shall create the repository. The <repo_path> parameter is optional.

Shall create a repository of the specified type. The <repo_type> parameter may accept
the following values: 1 – "Forever incremental with deduplication"; 2 – "Forever
--rt <repo_type>
incremental without deduplication"; 3 – "Incremental with full backups (deduplication
devices)".

Shall specify the repository compression level. The parameter may accept the following
--rc <compress_level>
values: Disabled; Fast; Medium; Best. Refer to Creating Backup Repositories for details.

--pnp-cleanup Shall clean up the database of the device manager for the Linux kernel.

Installing Full Solution on Linux

Follow the steps below to install all components of NAKIVO Backup & Replication (both Director and Transporter) on a
Linux OS:
1. Upload the installer file to the machine on which you want to install NAKIVO Backup & Replication in the binary
transfer mode. For example:
l Upload the installer from a Windows-based machine.
l Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO_Backup_&_Replication_TRIAL.sh'
2. Log in to the Linux machine and allow the execution of the installer file.
For example: chmod +x NAKIVO_Backup_&_Replication_TRIAL.sh
3. Execute the installer file with root privileges.

- 218 -
 For example: sudo ./NAKIVO_Backup_&_Replication_TRIAL.sh
4. Review the license agreement (press Space to go to the next page of the agreement). If you agree to the terms of
the license agreement, press "Y" and then press Enter.
5. Type "S" to install the full solution and press Enter.
6. Specify the installation path for the product: Press Enter to accept the default installation path "/opt/nakivo" or
enter a custom path and press Enter.
7. Specify the Director HTTPS port (which will be used to access the Web UI of NAKIVO Backup & Replication):
Press Enter to accept the default port "4443" or enter a custom port number and press Enter. Make sure the port
you specify is open in your firewall.
8. Specify whether to allow the product to automatically send support bundles to a NAKIVO server during the
evaluation period (Call Home). If this option is enabled, NAKIVO Backup & Replication will automatically create,
encrypt, and upload support bundles once a day to a NAKIVO support server during the evaluation period.
NAKIVO Support team may use this information to improve the product experience and will be able to identify
and resolve product issues faster.
9. Specify the Transporter port (which will be used to connect to the Transporter that is installed by default with the
Director): Press Enter to accept the default port "9446" or enter a custom port number (1 to 65535) and
press Enter. Make sure the port you specify is open in your firewall.
10. Specify a range of port numbers (from 1 to 65535) that will be used to transfer data by the Onboard Transporter
(default are 9448-10000). The range you specify should contain at least 100 ports. Make sure that the ports you
specify are open in your firewall.
11. Specify a path to the default Backup Repository: Press Enter to accept the default path "/opt/nakivo/repository"
or enter a custom path and press Enter to begin the installation process.
After the installation is complete, you can log in to NAKIVO Backup & Replication by opening the following URL in your
web browser: https://machine_IP_or_DNS:director_https_port
By default, login name and password are not required to access NAKIVO Backup & Replication. To prevent unauthorized
access to the product, you can set up credentials in Configuration.

Installing Transporter on Linux

If you have already installed the full solution (both Director and Transporter) and want to deploy an additional
Transporter, run the NAKIVO Backup & Replication installer for Windows and follow the steps below:

Transporter Installation Prerequisites

Prior to installing a Transporter, make sure the following prerequisites are met:
1. Make sure the machine on which you plan to install the Transporter has a connection to the relevant items
below:
l The machine on which the Director is installed
l VMware/Hyper-V servers on which you plan to back up or replicate VMs (if you plan to retrieve VM data

- 219 -
 using the Transporter you are about to install)
l Machines on which you have installed other Transporters (if you plan to set up data transfer between an
existing Transporter and the one you are about to install) 
l Backup repository (if you plan to assign the Transporter you are about to install to a Backup Repository)
l VMware/Hyper-V servers which you plan to use as a destination for replicated VMs (if you plan to write
data to the target servers and datastores using the Transporter you are about to install)
2. If you have discovered VMware/Hyper-V servers using DNS names, make sure those DNS names can be resolved
on the machine on which you plan to install the Transporter.

Transporter Installation

1. Upload the installer file to the machine on which you wish to install NAKIVO Backup & Replication in the binary
transfer mode. For example:
l Upload the installer from a Windows-based machine.
l Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO_Backup_&_Replication_TRIAL.sh'
2. Allow the execution of the installer file. For example: chmod +x NAKIVO_Backup_&_Replication_
TRIAL.sh
3. Execute the installer file with root privileges. For example:sudo ./NAKIVO_Backup_&_Replication_
TRIAL.sh
4. Review the license agreement (press Space to go to the next page of the agreement). If you agree to the terms of
the license agreement, press "Y" and then press Enter.
5. Type "T" to install only the Transporter and press Enter.
Note
Alternatively, you can use the -t argument to install the Transporter silently:
sudo ./NAKIVO_Backup_&_Replication_TRIAL.sh -t
6. Specify the installation path for the product: Press Enter to accept the default installation path "/opt/nakivo" or
enter a custom path and press Enter.
7. Specify the Transporter port (used to connect to the Transporter): Press Enter to accept the default port "9446" or
enter a custom port number and press Enter to begin the installation process. Make sure the port you specify is
open in your firewall.
After the installation is complete, add the Transporter to NAKIVO Backup & Replication.

Installing Full Solution in Multi-Tenant Mode on Linux

Follow the steps below to install the full solution in multi-tenant mode on a Linux OS:
1. Upload the installer file to the machine on which you want to install NAKIVO Backup & Replication in the binary
transfer mode. For example:

- 220 -
 l Upload the installer from a Windows-based machine.
l Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO_Backup_&_Replication_TRIAL.sh'
2. Log in to the Linux machine and allow the execution of the installer file.
For example: chmod +x NAKIVO_Backup_&_Replication_TRIAL.sh
3. Execute the installer file with root privileges.
For example: sudo ./NAKIVO_Backup_&_Replication_TRIAL.sh
4. Review the license agreement (press Space to go to the next page of the agreement). If you agree to the terms of
the license agreement, press "Y" and then press Enter.
5. Type “M” to install the Director in Multi-tenant mode and press Enter.
Note
Alternatively, you can use the -m argument to install the solution in multi-tenant mode silently:
sudo ./NAKIVO_Backup_&_Replication_TRIAL.sh -m
6. Specify the installation path for the product: Press Enter to accept the default installation path “/opt/nakivo” or
enter a custom path and press Enter.
7. Specify the Director HTTPS port (which will be used to access the Web UI of NAKIVO Backup & Replication): Press
Enter to accept the default port “4443” or enter a custom port number and press Enter. Make sure the port you
specify is open in your firewall.
8. Specify whether to allow the product to automatically send support bundles to a NAKIVO server during the
evaluation period. If this option is enabled, NAKIVO Backup & Replication will automatically create, encrypt, and
upload support bundles once a day to a NAKIVO support server during the evaluation period. NAKIVO Support
team may use this information to improve the product experience and will be able to identify and resolve product
issues faster.
9. Specify the Transporter port (which will be used to connect to the Transporter that is installed by default with the
Director): Press Enter to accept the default port “9446” or enter a custom port number (1 to 65535) and press
Enter. Make sure the port you specify is open in your firewall.
10. Specify a range of port numbers (from 1 to 65535) that will be used to transfer data by the Onboard Transporter 
(default are 9448-10000). The range you specify should contain at least 100 ports. Make sure that the ports you
specify are open in your firewall.
11. Specify a path to the default backup repository: Press Enter to accept the default path
/opt/nakivo/repository or enter a custom path and press Enter to begin the installation process.
After the installation is complete, you can log in to NAKIVO Backup & Replication by going to the following URL in your
web browser: https://machine_IP_or_DNS:director_https_port.
Refer to “Getting Started” on page 83 to know how to continue working with NAKIVO Backup & Replication. 

- 221 -
Uploading Installer from Windows Machine to Linux Machine
To upload the installer from a Windows-based machine, follow the steps below:
1. Download the free WinSCP client from http://winscp.net, install, and run it.
2. Choose SCP from the File protocol list.
3. Specify the IP address or the hostname of the Linux machine on which you would like to install the product in
the Host name field.
4. Specify the username and password to the Linux machine in the appropriate boxes.
5. Leave other options as is and click Login.

6. Click Yes in the dialog box that opens.

7. In the left pane, find the folder that contains the Linux installer, in the right pane, go up to the root folder.
8. Drag and drop the installer from left to the right pane.
9. Choose Binary from the Transfer settings drop-down list in the Copy dialog box that opens.

- 222 -
10. Click Copy.

- 223 -
Installing on Synology NAS
NAKIVO Backup & Replication can be installed directly on a supported Synology NAS to create your own, high-
performance backup appliance. With the appliance, all VM data protection components are unified in a single system
that is fast to deploy and easy to manage, while also not consuming your environment's valuable resources. Moreover,
you are getting an all-in-one backup hardware, backup software, backup storage, and data deduplication in a single
box. This results in a zero VMware footprint, less power and cooling, less required maintenance, time, money, and –
most of all – higher VM backup performance.
You can install a Synology package with either all NAKIVO Backup & Replication components (Director, Transporter,
Backup Repository) or a Transporter only. The product can be installed via Package Center or manually. For more
details, refer to the corresponding topics below:
l “Installing on Synology NAS via Package Center” on page 225
l “Installing on Synology NAS Manually” on page 227

- 224 -
Installing on Synology NAS via Package Center
To automatically install a NAKIVO Backup & Replication application on a Synology NAS, do the following:
1. Log in to your Synology account and open Package Center in the management interface.
2. Use the search box to find NAKIVO Backup & Replication packages.

3. Click Install on one of the following:

l NAKIVO Backup and Replication to install all product components. 
l NAKIVO Transporterto install a Transporter only. 

4. Select the I accept the terms of the license agreement checkbox and click Next.
5. In the Confirm settings dialog box, click Apply.

- 225 -
 Note
If you installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be
added to your application outside of the ARM-based NAS to allow it to work with VMware vCenters and ESXi
hosts. Please refer to the “Adding VMware vCenters and ESXi hosts” on page 335 topic for details.
Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication. 

- 226 -
Installing on Synology NAS Manually
If for any reason installation of NAKIVO Backup & Replication via Package Center is not available for your Synology NAS,
you can install it manually.
The following packages are available for manual installation:
l Synology package
l Synology Transporter package
l Synology ARM package
l Synology ARM Transporter package
To manually install NAKIVO Backup & Replication on a Synology NAS, do the following:
1. Download a Synology NAS package.
2. Log in to your Synology account and open the Package Center in the management interface.

3. Click Manual Install. 

4. Click Browse, navigate to the Synology NAS package that you have downloaded, select it, and click Open.

- 227 -
5. Click Yes to proceed.

6. After reading through the License Agreement, check I accept the terms of the license agreement and click Next.

7. Optionally check Run after installation to start NAKIVO Backup & Replication immediately after the install

- 228 -
 process is finished. Click Apply.

8. Now NAKIVO Backup & Replication is installed on your NAS. To open the  NAKIVO Backup & Replication Web
interface, go to the following address in your web browser: https://NAS_IP_address:4443, or click the
NAKIVO Backup & Replication icon in the main menu of the NAS. 

Note
If you installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be
added to your application outside of the ARM-based NAS to allow it to work with VMware vCenters and ESXi
hosts. Please refer to the “Adding VMware vCenters and ESXi hosts” on page 335 topic for details.
Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication. 

- 229 -
Installing on QNAP NAS
You can install a QNAP package with either all NAKIVO Backup & Replication components (Director, Transporter, Backup
Repository) or a Transporter only.
NAKIVO Backup & Replication can be installed directly on a supported QNAP NAS to create your own, high-performance
backup appliance. With this appliance, all VM data protection components are unified in a single system that is quick to
deploy and easy to manage, while also not consuming your environment's valuable resources. Moreover, you are
getting an all-in-one backup hardware, backup software, backup storage, and data deduplication in a single box. This
results in a zero VMware footprint, less power and cooling, less required maintenance, time, money, and – most of all –
higher VM backup performance.
You can install NAKIVO Backup & Replication either via QNAP store or manually.
l “Installing on QNAP NAS via QNAP Store” on page 231
l “Installing on QNAP NAS Manually” on page 233

- 230 -
Installing on QNAP NAS via QNAP Store
Check to see if your NAS model is supported before you begin installing NAKIVO Backup & Replication on a QNAP NAS.
To install NAKIVO Backup & Replication take the following steps:
1. Open the QNAP Desktop in your browser by entering the IP address of your QNAP NAS.

2. Go to App Center.
3. Select the Backup/Sync category and locate NAKIVO Backup & Replication. Alternatively, you can use the search
bar at the top of the App Center window. Click on the magnifying glass icon and enter 'Nakivo'.

4. Click Install.
5. Wait till the installation is completed.
By default, NAKIVO Backup & Replication interface is available by the IP address of your QNAP NAS on the port
4443: https://<IP_address_of_QNAP_NAS>:4443.

- 231 -
Note
If you installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be added to
your application outside of the ARM-based NAS to allow it to work with VMware vCenters and ESXi hosts. Please refer to
the “Adding VMware vCenters and ESXi hosts” on page 335 topic for details.
Refer to “Getting Started” on page 83 to know how to continue working with NAKIVO Backup & Replication. 

- 232 -
Installing on QNAP NAS Manually
Before you begin installing NAKIVO Backup & Replication on a NAS, make sure your NAS model is supported and you
have downloaded the installer (.qpkg file) for QNAP NAS.
To install NAKIVO Backup & Replication on a NAS:
1. Open the QNAP Desktop in your browser by entering the IP address of your QNAP NAS.

2. Go to App Center.
3. Click the Install Manually icon.

4. Click Browse in the window that appears and locate the installer (.qpkg file) on your computer.

- 233 -
 5. Click Install.
6. Wait until the installation is complete.
By default, NAKIVO Backup & Replication interface is available at the IP address of your QNAP NAS on the port
4443: https://<IP_address_of_QNAP_NAS>:4443.
Note
If you installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be added to
your application outside of the ARM-based NAS to allow it to work with VMware vCenters and ESXi hosts. Please refer to
the Adding VMware vCenters and ESXi Hosts topic for details.
Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication.

- 234 -
Installing on ASUSTOR NAS
You can install an ASUSTOR package with either all NAKIVO Backup & Replication components (Director, Transporter,
Backup Repository) or a Transporter only.
NAKIVO Backup & Replication can be installed directly on a supported ASUSTOR NAS to create your own, high-
performance backup appliance. With the appliance, all VM data protection components are unified in a single system
that is fast to deploy and easy to manage, while also not consuming your environment's valuable resources. Moreover,
you are getting an all-in-one backup hardware, backup software, backup storage, and data deduplication in a single
box.
l “Installing on ASUSTOR NAS via App Central” on page 236
l “Installing on ASUSTOR NAS Manually” on page 238

- 235 -
Installing on ASUSTOR NAS via App Central
Before you begin installing NAKIVO Backup & Replication on a NAS make sure your NAS model is supported.
To install NAKIVO Backup & Replication on ASUSTOR NAS via App Central:
1. Open the ASUSTOR Desktop in your browser by entering the IP address of your ASUSTOR NAS. 

2. Go to App Central.
3. Go to Browse > All Apps.
4. Find NAKIVO Backup & Replication in the store. Alternatively, enter Nakivo in the search box.
5. Click Install.

6. In the About This App dialog box that opens, select Enable port forwarding for NAKIVO Backup & Replication
and then click Install.

- 236 -
 7. Wait until the installation is complete.
By default, the NAKIVO Backup & Replication interface is available at the IP address of your ASUSTOR NAS on the port
4443: https://<IP_address_of_ASUSTOR_NAS>:4443.
Note
If you have installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be added
to the application outside of the ARM-based NAS to allow working with VMware vCenters and ESXi hosts. Please refer to
the “Adding VMware vCenters and ESXi hosts” on page 335 topic for details.
Refer to “Getting Started” on page 83 to understand better how to continue working with NAKIVO Backup &
Replication. 

- 237 -
Installing on ASUSTOR NAS Manually
Before you begin installing NAKIVO Backup & Replication on a NAS, make sure your NAS model is supported and you
have downloaded an installer (.apk file) for ASUSTOR NAS.
To manually install NAKIVO Backup & Replication on ASUSTOR NAS:
1. Open the ASUSTOR Desktop in your browser by entering the IP address of your ASUSTOR NAS.
2. Go toApp Central.

3. Click Manual Install.

4. Click Browse. In the dialog box that opens, locate the installer (.apk file) on your computer.
5. Click Upload.
6. In the About This App dialog box that opens, check Enable port forwarding for NAKIVO Backup & Replication.

- 238 -
 7. Click Next.
8. In the warning dialog box that opens, select I understand the risks associated with installing unverified apps.
9. Click Install.
10. Wait until the installation is complete.
By default, the NAKIVO Backup & Replication interface is available at the IP address of your ASUSTOR NAS on the port
4443: https://<IP_address_of_ASUSTOR_NAS>:4443.
Note
If you have installed NAKIVO Backup & Replication on an ARM-based NAS, an additional Transporter needs to be added
to the application outside of the ARM-based NAS to allow working with VMware vCenters and ESXi hosts. Please refer to
the “Adding VMware vCenters and ESXi hosts” on page 335 topic for details.
Refer to “Getting Started” on page 83 to understand better how to continue working with NAKIVO Backup &
Replication. 

- 239 -
Installing on Western Digital NAS
You can install a Western Digital MyCloud package with either all NAKIVO Backup & Replication components (Director,
Transporter, Backup Repository) or a Transporter only. The following  packages are available:
l Western Digital MyCloud DL2100 package
l Western Digital MyCloud DL2100 Transporter package
l Western Digital MyCloud DL4100 package
l Western Digital MyCloud DL4100 Transporter package
l Western Digital MyCloud PR2100 package
l Western Digital MyCloud PR 2100 Transporter package
l Western Digital MyCloud PR 4100 package
l Western Digital MyCloud PR 4100 Transporter package
NAKIVO Backup & Replication can be installed directly on a Western Digital MyCloud NAS to create your own, high-
performance backup appliance. With this appliance, all VM data protection components are unified in a single system
that is quick to deploy and easy to manage, while also not consuming your environment's valuable resources.
Moreover, you are getting an all-in-one backup hardware, backup software, backup storage, and data deduplication in
a single box. This results in a zero VMware footprint, less power and cooling, less required maintenance, time, money,
and – most of all – higher VM backup performance.
NAKIVO Backup & Replication is installed on a NAS hard drive (not on the NAS Flash memory), so if you remove the hard
drive from the NAS you will also remove the product from it.
Prior to installing NAKIVO Backup & Replication onto a Western Digital MyCloud NAS device, make sure the following
requirements have been met:
1. Your Western Digital MyCloud NAS model is supported by NAKIVO Backup & Replication.
2. You have access to the NAS My Cloud Dashboard.
3. You have NAKIVO Backup & Replication installer for Western Digital NAS available on your computer.
Follow the steps below to install NAKIVO Backup & Replication on a Western Digital MyCloud NAS device:
1. On the My Cloud dashboard, click Apps. The list of installed NAS applications opens on the left side of the page.
2. Above the list of NAS installed applications, click Install an app manually. The File Upload dialog opens.

- 240 -
 3. In the File Upload dialog, navigate to your copy of NAKIVO Backup & Replication installer and click Open. The
installation progress bar opens.
4. When the installation finishes successfully, a dialog box opens with a message informing you about it. Click OK to
close the dialog box.
After the installation is complete, NAKIVO Backup & Replication will appear in the list of installed NAS applications. To
access the product, do either of the following:
l Open the https://<NAS_IP>:4443 address in your browser.
l In the list of installed NAS applications, click NAKIVO Backup & Replication and then click Configure.
Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication. 

- 241 -
Installing on NETGEAR ReadyNAS

You can install the NETGEAR package that includes all NAKIVO Backup & Replication components (Director, Transporter,
Backup Repository) or the NETGEAR Transporter package.
NAKIVO Backup & Replication can be installed directly on a supported NETGEAR ReadyNAS to create your own high-
performance backup appliance. With the appliance, all VM data protection components are unified in a single system
that is fast to deploy and easy to manage, while also not consuming your environment's valuable resources. Moreover,
you are getting an all-in-one backup hardware, backup software, backup storage, and data deduplication in a single
box. For installation instructions, refer to the following topics:
l “Installing on NETGEAR ReadyNAS via Available Apps” on page 243
l “Installing on NETGEAR ReadyNAS Manually” on page 244

- 242 -
Installing on NETGEAR ReadyNAS via Available Apps
Before you begin installing NAKIVO Backup & Replication or NAKIVO Transporter on a NETGEAR ReadyNAS device,
please check if your NETGEAR ReadyNAS model is supported.
To install NAKIVO Backup & Replication or NAKIVO Transporter, take the following steps:
1. Open the NETGEAR ReadyNAS Admin Page in your browser by entering the IP address of your NAS.
2. Go to Apps -> Available Apps.
3. Find NAKIVO Backup & Replication or NAKIVO Transporter in the list of available applications. Alternatively,
you can enter NAKIVO to the filtering box in the upper left corner of the Admin Page.
4. Click the Install button below the corresponding item.

Note
Make sure that only one instance of the NAKIVO solution - either Full Product or Transporter-only - is installed on
the device concurrently. Having both products installed at once may lead to incorrect operation.
5. Wait until the installation is completed.
By default, the NAKIVO Backup & Replication interface is available at the IP address of your NETGEAR ReadyNAS on the
port 4443: https://<IP_address_of_ NETGEAR_ReadyNAS>:4443.
Refer to “Getting Started” on page 83 to know how to continue working with NAKIVO Backup & Replication. 

- 243 -
Installing on NETGEAR ReadyNAS Manually
Before you begin installing NAKIVO Backup & Replication or NAKIVO Transporter on a NETGEAR ReadyNAS device, make
sure your NAS model is supported and you have downloaded a relevant installer (.deb file) for NETGEAR ReadyNAS.
To install NAKIVO Backup & Replication or NAKIVO Transporter, take the following actions:
1. Open the NETGEAR ReadyNAS Admin Page in your browser by entering the IP address of your NAS.
2. Go to Apps and click Upload.

3. The Install Application dialog box opens. Click Browse.

4. In the dialog box that opens, locate the downloaded installer (.deb file) and then click Upload. 
5. Wait until the installation has been completed.
Note
Make sure that only one instance of the NAKIVO solution - either Full Product or Transporter-only - is installed on
the device concurrently. Having both products installed may lead to incorrect operations.
By default, NAKIVO Backup & Replication interface is available at the IP address of your NETGEAR ReadyNAS on the port
4443: https://<IP_address_of_ NETGEAR_ReadyNAS>:4443.
Refer to “Getting Started” on page 83 to understand better how to continue working with NAKIVO Backup &
Replication. 

- 244 -
Installing on Generic ARM-based Device
NAKIVO Backup & Replication can be deployed on ARMv7/ARMv8 computers by downloading and running an
appropriate script within a Linux-based OS supported by NAKIVO Backup & Replication.
1. Download a package suitable for your setup from the downloads page.
2. Upload the installer file to the machine on which you wish to install NAKIVO Backup & Replication in the binary
transfer mode. For example:
1. Upload the installer from a Windows-based machine
2. Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO Backup_&_Replication v8.5.0.30224 Installer-NAS-ARM-TRIAL.sh'
3. Log in to the Linux machine and allow for the execution of the installer file.
Example
chmod +x ./NAKIVO Backup_&_Replication v8.5.0.30224 Installer-NAS-ARM-TRIAL.sh
4. Execute the installer file with root privileges. 
Example
sudo ./NAKIVO Backup_&_Replication v8.5.0.30224 Installer-NAS-ARM-TRIAL.sh
5. Accept the License Agreement by typing [Y] and hit Enter. You can review the license agreement by typing [R].
Rejecting [N] the license agreement will terminate the installation process and the product will not be installed.
6. The system will notify you when the installation is successfully completed.

Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication. 

- 245 -
Installing on FreeNAS
Make sure the following prerequisites are met:
1. You have access to the FreeNAS system.
2. Your FreeNAS system meets system requirements for installing NAKIVO Backup & Replication.
3. The iocage jail/container manager is installed on your FreeNAS system. Refer to the iocage README page for
a description.
4. A storage pool is created on your FreeNAS system. Make sure the pool has enough storage for all NAKIVO Backup
& Replication functionality. Refer to FreeNAS User Guide for more details on creating storage pools.
Follow the steps below to install NAKIVO Backup & Replication on a FreeNAS system:
1. Log in to the FreeNAS system via SSH.
2. Go to the tmp folder:  cd /tmp
3. Download the necessary json file:
l for the full NAKIVO Backup & Replication installation on a FreeNAS v11.3:
wget https://github.com/NAKIVO/iocage-plugin-nbr/raw/master/nbr.json
l for the NAKIVO Backup & Replication Transporter installation on a FreeNAS v11.3:
wget https://github.com/NAKIVO/iocage-plugin-nbr-transporter/raw/master/nbr-transporter.json
Note
If a utility for downloading files like wget or curl is missing on your FreeNAS system, you can first
download the necessary file to your local machine and then upload it to FreeNAS with a third-party tool
like WinSCP or FileZilla.
4. Install NAKIVO Backup & Replication with the iocage jail/container manager:
Note
Make sure that the jail IP address is not the IP address of your FreeNAS system.
l For the full NAKIVO Backup & Replication installation on a FreeNAS v11.3:
iocage fetch -P nbr.json vnet="off" ip4="inherit" ip4_
addr="em0|x.x.x.x/24"
l For the NAKIVO Backup & Replication Transporter installation on a FreeNAS v11.3:
iocage fetch -P nbr-transporter.json vnet="off" ip4="inherit" ip4_
addr="em0|x.x.x.x/24"
5. For the NAKIVO Backup & Replication Transporter installation, add the Transporter to the Director. Refer to “Adding
Installed Transporters” on page 347 for details.

- 246 -
Installing on Raspberry Pi
NAKIVO Backup & Replication can be installed on a Raspberry Pi computer.
l For system requirements, refer to “Generic ARM-based NAS devices” on page 141 .
l For the installation procedure, refer to “Installing on Generic ARM-based Device” on page 245 .
Refer to “Getting Started” on page 83 to better understand how to continue working with NAKIVO Backup &
Replication.

- 247 -
Updating NAKIVO Backup and Replication
NAKIVO Backup & Replication automatically checks for updates once each day. If an update is available, a notification is
displayed in the product web interface. Click the notification link to view information about the update.
Starting from v8.5, a full solution of the NAKIVO Backup & Replication installed on Windows or Linux can be updated
automatically. Should you find that product auto updating is not supported or there are some network issues, you can
update the product manually. For more details, refer to the corresponding articles below. 
To manually update any copy of NAKIVO Backup & Replication, go to the download page with updaters.
To update your copy of the product to a newer version, you need to download an appropriate updater and run it on:
l Each machine on which you have additionally installed the Transporter.
l The machine on which the Director is installed.
Refer to the following topics for more information:
l “Auto Updating NAKIVO Backup and Replication” on page 249
l “Updating Virtual Appliance” on page 253
l “Updating on Windows” on page 258
l “Updating on Linux” on page 259
l “Updating on Synology NAS” on page 260
l “Updating on Western Digital NAS” on page 262
l “Updating on Amazon EC2” on page 263
l “Updating on QNAP NAS” on page 268
l “Updating on ASUSTOR NAS” on page 271
l “Updating on NETGEAR ReadyNAS” on page 273
l “Updating on FreeNAS” on page 275
l “Updating on Generic ARM-based Device” on page 276

- 248 -
Auto Updating NAKIVO Backup and Replication
l Download & Update Option
l Download Option
l Forgetting Update
If the full solution of NAKIVO Backup & Replication is installed on a Windows or Linux machine, you can download
product updates and install them using NAKIVO Backup & Replication interface. Once the update becomes available,
the Update available notification appears in the main menu of the product. You can choose to either download and
update the product immediately or download the update and run it at a later time.

Note
If you are using a multi-tenant solution, only master-tenant users who have appropriate permissions will be able to see
and manage this button.
Product Auto-Updating Prerequisites
l At least 1GB of free space must be available on the machine on which the full solution is installed.
l Make sure your Maintenance & Support period is active. You can verify this on the product Licensing page.

Download & Update Option

To download and install the update in a single click, do the following:
1. Click the Update Available button.
2. Optionally, click Release Notes to see features and improvements implemented in the new product version.
3. In the Update Available dialog box, click Download & update. 

- 249 -
4. In the Update Available dialog box, click Proceed to confirm stopping all current activities and start downloading
the update. When the download is complete, the product updating process will begin.

The product will download the update to the Director first. When the Director is updated, the update will be
downloaded to the Transporters that in turn will be updated simultaneously. If some Transporters are not
updated, you can update them outside the product. Refer to the corresponding articles for details.
Updating the product will conduct self-backup and stop all current activities including running jobs, recovery
jobs, repository maintenance, etc.
Notes
l Only the following NAKIVO Backup & Replication Transporters can be auto-updated:
l Windows including Hyper-V Transporters
l Linux including Hyper-V Transporters
l Amazon EC2 Transporters
l VMware Transportes

- 250 -
 l Only 20 Transporters can be updated simultaneously. All other Transporters will be sent to a queue and
updated when their turn comes.
5. If the full solution is updated successfully, the Update Complete dialog box opens. Click Close to dismiss the
dialog box.

Download Option
If you wish to postpone updating or schedule it for a certain period of time, take the following steps to download the
update only:
1. Click the Update Available button in the product interface.
2. In the Update Available dialog box, click Download to start downloading the update.

3. When downloading is complete, the Update Ready dialog box appears in Notifications.

4.  Do either of the following:
l  Click Update Now if you want to start the updating process. In the confirmation dialog box that opens,
click Proceed. Updating the product will stop all current activities, including running jobs, recovery jobs,
repository maintenance, etc. 

- 251 -
 l Click Schedule Update to update the solution on a schedule:
1. In the dialog box that opens, pick a day and time for updating. Click Apply.

2. On a working day before the scheduled update, you will see the notification in the product menu
with the Update Reminder dialog box. Do any of the following:
a. Click Reschedule if you want to reschedule the update and pick a different time.
b. Click Cancel update to cancel updating of the full solution.
Note
A notification about the update will also be sent to your email if email settings are
configured.

Forgetting Update
In the Update Available dialog box, you can click Forget to dismiss all notifications. If you select this option, you will not
receive a notification regarding a product update until the next update is available.

- 252 -
Updating Virtual Appliance
Prior to updating your virtual appliance (VA):
1. Make sure that no jobs or repository maintenance tasks are running in the product.
2. Create a snapshot of the VA to revert to the previous version in case any failure occurs. 
Follow the steps below to update your VA:
1.  Using SSH client, log in to the VA that needs to be updated. 

2. Download the latest VA and Linux updater from www.nakivo.com/resources/download/update/.

3. Change the directory to /opt/nakivo/updates and locate the updater.

- 253 -
4. Log out from the SSH client.
5. Log in to your vSphere client, navigate to your VA and click Launch Web Console.

6. Do one of the following depending on the NAKIVO Backup & Replication version you use:

- 254 -
l For the product Version 8.1 and above:
1. In the VA menu, select Manage NAKIVO services and press Enter.

2. In the menu that opens, select Software update and press Enter.

3. Select the updater that you have downloaded and press Enter.

- 255 -
4. Review the End User License Agreement. Press Space to go to the bottom of it. If you agree to the
terms of the agreement, type Y and then press Enter to begin the update process.

- 256 -
 l For earlier product versions:
1. In the VA menu, select Software update and press Enter.
2. Select the updater that you have downloaded and press Enter.
3. Review the End User License Agreement. Press Space to go to the bottom of it. If you agree to the
terms of the agreement, type Y and then press Enter to begin the update process.
7. When the update process is complete, a message will appear to inform you about it. Exit the VA console.
8. Update all machines on which you have deployed an additional Transporter.
Note
Updating your VA with versions prior to the previous major version (for example, updating VA version 6.1 to version 9.0)
is prohibited. Please update your VA to the next major version first.

- 257 -
Updating on Windows
If auto-update within the NAKIVO Backup & Replication interface is not supported, follow the steps below to update the
product manually:
1. Download the latest Windows updater from www.nakivo.com/resources/download/update/.
2. Make sure that no jobs or repository maintenance tasks are running in the product.
If NAKIVO Backup & Replication is installed on a VM, create a snapshot of the VM before updating the product.
3. Run the updater on the machine on which the Director is installed, and also on all machines on which you have
additionally deployed a Transporter.
4. Click Update.
5. When the update is complete, click Finish.

- 258 -
Updating on Linux
If updating on a Linux OS within the NAKIVO Backup & Replication interface is not supported, follow the steps below to
update the product manually:
1. Download the latest Linux/VA updater from  www.nakivo.com/resources/download/update/.
2. Upload the updater to the machine on which the Director is installed. 
Important
Make sure you are using the binary transfer mode when uploading the updater to the machine with a Linux
OS. For example:
l Upload the installer from a Windows-based machine
l Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO_Backup_Replication_vX.X.X_Updater.sh'
3. Log in to the Linux machine and allow the execution of the updater file. For example: chmod +x NAKIVO_
Backup_Replication_vX.X.X_Updater.sh
4. Make sure that no jobs or repository maintenance tasks are running in the product.
If NAKIVO Backup & Replication is installed on a VM, create a snapshot of the VM prior to updating the product.
5. Run the updater file with root privileges. For example: sudo ./NAKIVO_Backup_Replication_
vX.X.X_Updater.sh
6. Review the license agreement (press Space to go to the next page of the agreement). If you agree to the terms of
the license agreement, press “Y” and then press Enter.
7. Enter the “Y” key and then press Enter to confirm that you wish to stop the services and begin the update
process.
8. Update all machines on which you have additionally deployed a “Transporter” on page 130.

- 259 -
Updating on Synology NAS
l Updating via Synology Package Center
l Updating Manually

Updating via Synology Package Center

1. Make sure that no jobs or repository maintenance tasks are running in the product.
2. In the Synology NAS management interface, open the Package Center.

3. Go to the Installed section.
4. If there is a new version of NAKIVO Backup & Replication available, you will see an Update button.

5. Click Update.

- 260 -
 6. Wait until the update is complete.
7. Repeat these steps on all Synology NAS where you have also installed a Transporter.

Updating Manually
1. Download the latest Synology NAS updater from www.nakivo.com/resources/download/update/.
2. Make sure that no jobs or repository maintenance tasks are running in the product.
3. In the Synology NAS management interface, open the Package Center.

4. Click Manual Install.

5. Click Browse, navigate to the Synology NAS package that you have downloaded, select it, and click Open.
6. Click Next. the package is uploaded to your NAS. 
7. Click Apply. 
8. Run an appropriate updater on all machines on which you have also installed a Transporter. 
Now, NAKIVO Backup & Replication has been updated. 

- 261 -
Updating on Western Digital NAS
Prior to updating NAKIVO Backup & Replication on Western Digital MyCloud NAS, make sure the following requirements
have been met:
l You have access to the Western Digital NAS MyCloud Dashboard.
l NAKIVO Backup & Replication installer is available for your Western Digital NAS.
Please follow the steps below to update NAKIVO Backup & Replication on a Western Digital MyCloud NAS device:
1. In the My Cloud Dashboard, click Apps. The list of installed NAS applications opens on the left side of the page.
2. Above the list of NAS installed applications, click Install an app manually. The File Upload dialog opens.
3. In the File Upload dialog, navigate to your copy of the NAKIVO Backup & Replication installer for Western Digital
NAS and click Open. The update progress bar opens.

4. Once the update has successfully finished, a dialog box opens with a message including said information.
Click OK to close the dialog box.

- 262 -
Updating on Amazon EC2
The main installation of NAKIVO Backup & Replication (Director and Transporter) must be updated the way it is done
on Linux.
Notes
l You have to apply the -e argument for executing the installer, in order to avoid changing the Amazon EC2
Transporter with the regular Linux Transporter. Refer to “Installing on Linux” on page 217 for a description of the
available arguments.
l Only the main installation of NAKIVO Backup & Replication needs to be updated manually. Transporters installed
on Amazon EC2 instances are updated automatically.

- 263 -
Connecting to an Amazon EC2 Instance from Windows
You can use the following free tools to connect to your Amazon EC2 instance:
l WinSCP to upload the installer file.
l PuTTYgen tool to convert the private key.
l PuTTY tool to connect to an Amazon instance securely.
1. Log in to NAKIVO Backup & Replication.
2. Go to Settings > Transporters.
3. Download the keys of your Amazon instance.

4. Click on the Transporter to view its details. Copy or remember the IP-address/hostname of the Amazon instance.
5. Unzip the folder with the key.
6. Convert the key using PuTTYgen:

- 264 -
1. In PuTTYgen menu, go to Conversions > Import.

2. Locate the SSH_key.pem you just downloaded and unzipped. If you don't see it in the Open... dialogue
box, change the file type to All files.

- 265 -
 3. Click on Save private key. If PuTTYgen asks you to save the key without a passphrase, click Yes.
7. Open WinSCP.
8. Create a new session:
1. Add the hostname or IP address of your Amazon instance you received on step 4 into the Host Name box.
2. In the Username box, enter ubuntu.
3. Leave the Password box empty.
4. Add the private key to WinSCP:
1. Click the Advanced... button.
2. The Advanced Site Settings dialog box opens. Go to SSH > Authentication > Private key file: and
select the key file you generated on step 6.

3. Click OK.
5. Click Login. 

- 266 -
 6. Upload the updater file.
7. Open PuTTY.
8. Enter the IP-address or hostname of the Amazon EC2 instance.
9. Go to Connection > SSH > Auth and add the private key in Private key file for authentication: box.

10. Click Open.
11. In the command line prompt that opens: log in to the Amazon EC2 instance:
1. For login, enter ubuntu
2. For password, leave a blank line.
9. Update NAKIVO Backup & Replication following the instructions.

- 267 -
Updating on QNAP NAS
You can update NAKIVO Backup & Replication via QNAP AppCenter or manually. Refer to the following subtopics for
details:
l Updating via QNAP AppCenter
l Updating Manually

Updating via QNAP AppCenter

1. Open the QNAP Desktop in your browser by entering the IP address of your QNAP NAS.

2. Go to App Center.
3. Select the Backup/Sync category and find NAKIVO Backup & Replication. Alternatively, use the search box at the
top of the App Center window: click on the magnifier icon and enter "Nakivo".
4. If the new version of NAKIVO Backup & Replication is available in the QNAP App Center, you will see a green
Update button.

5. Click the Update button and wait till update finishes.

- 268 -
Updating Manually
1. Download the update package from www.nakivo.com/resources/download/update/
2. Open the QNAP Desktop in your browser by entering the IP address of your QNAP NAS.

3. Go to App Center.
4. Click the Install Manually icon.

5. Click Browse. In the window appears, locate the installer (.qpkg file) on your computer. 

- 269 -
6. Click Install.
7. Wait until the update process is finished.

- 270 -
Updating on ASUSTOR NAS
l Updating on ASUSTOR NAS Manually
l Updating on ASUSTOR NAS via App Central

Updating on ASUSTOR NAS Manually

Prior to updating NAKIVO Backup & Replication on ASUSTOR NAS manually, make sure the following requirements are
met:
l You have access to the ASUSTOR NAS.
l NAKIVO Backup & Replication installer is available for your ASUSTOR NAS.
Follow the steps below to update NAKIVO Backup & Replication on ASUSTOR NAS manually:
1. Open the App Central from the ASUSTOR NAS Desktop.
2. Click Management in the bottom left corner and click Manual Install. 
3. The Manual Install pane opens to the right of the App Central. Click Browse. 
4. The Open dialog box opens. Locate your copy of NAKIVO Backup & Replication installer for ASUSTOR NAS and click
the Open button.
5. The Open dialog closes, and the Upload button becomes enabled. Click the Upload button.
6. When the upload finishes, the About This App dialog opens.  If you are sure the requirements are met, click
the Next button.
7. The About This App dialog opens a message asking you to review the summary of the NAKIVO Backup &
Replication update. Select the checkbox I understand the risks associated with installing unverified Apps and
click Install.
8. The About This App dialog closes, and the Installed pane of the App Central opens. 
9. Wait until the update of  NAKIVO Backup & Replication is complete.

- 271 -
Updating on ASUSTOR NAS via App Central
Follow the steps below to update NAKIVO Backup & Replication on ASUSTOR NAS via App Central:
1. Open the App Central from the ASUSTOR NAS Desktop.
2. In the Browse menu to the left, click All Apps. The list of applications available in the App Central opens in the
right pane.
3. In the search box in the upper right corner of the pane, enter "Nakivo". Installations of the NAKIVO Backup &
Replication application that are available at App Central are now displayed. 
4. Click the Update button below the required NAKIVO Backup & Replication application to start uploading the
update.
5. When the update is uploaded successfully, the About This App dialog opens. Click the Update button if you are
sure that all the requirements are met.
6. The About This App dialog closes, and the Installed pane of the App Central opens. Wait until the update of the
NAKIVO Backup & Replication is completed.

- 272 -
Updating on NETGEAR ReadyNAS
l Updating on NETGEAR ReadyNAS Manually
l Updating on NETGEAR ReadyNAS via Available Apps

Updating on NETGEAR ReadyNAS Manually

Prior to updating NAKIVO Backup & Replication on NETGEAR ReadyNAS manually, make sure the following
requirements have been met:
l You have access to the NETGEAR ReadyNAS.
l NAKIVO Backup & Replication update is available for your NETGEAR ReadyNAS.
Follow the steps below to update NAKIVO Backup & Replication on NETGEAR ReadyNAS manually:
1. Open the NETGEAR ReadyNAS Admin Page in your browser by entering the IP address of your NAS.
2. Go to Apps and click Upload.
3. The Install Application dialog box opens. Click Browse.
4. In the dialog box that opens, locate the downloaded installer (.deb file) and then click Upload.
5. Wait until the update is completed.

Updating on NETGEAR ReadyNAS via Available Apps

Prior to updating NAKIVO Backup & Replication on NETGEAR ReadyNAS via Available Apps, make sure that you have
access to NETGEAR ReadyNAS.
Follow the steps below to update NAKIVO Backup & Replication on NETGEAR ReadyNAS via Available Apps:
1. Open the NETGEAR ReadyNAS Admin Page in your browser by entering the IP address of your NAS.
2. Go to Apps > Available Apps.

- 273 -
3. Find NAKIVO Backup & Replication in the list of available applications. Alternatively, enter NAKIVO to the filtering
box in the upper left corner of the Admin Page.
4. If a new version of NAKIVO Backup & Replication is available in the NETGEAR Available Apps, the Update button
will be available below the application item. Click the Update button.
5. Wait until the update is complete.

- 274 -
Updating on FreeNAS
Prerequisites:
l You are logged in to the FreeNAS system with the FreeNAS GUI.
l The Shell button is enabled in the interface.
Follow the steps below to update NAKIVO Backup & Replication on your FreeNAS system:
1. Navigate to the Jails page of the FreeNAS GUI and click the jail of the NAKIVO Backup & Replication plugin to select
it.
2. Click the Shell button to open a web shell.
3. In the web shell prompt, download the latest Linux/VA updater from the NAKIVO Backup & Replication Update
page with the curl command. For example:
curl -O https://d96i82q710b04.cloudfront.net/res/product/NAKIVO_Backup_
Replication_vX.X.X_Updater.sh
4. Change the updater file permission with the chmod command:
chmod +x NAKIVO_Backup_&_Replication_vX.X.X_Updater.sh
5. Run the updater in silent mode:
./NAKIVO_Backup_&_Replication_vX.X.X_Updater.sh -y -u --eula-accept

- 275 -
Updating on Generic ARM-based Device
If auto updating of NAKIVO Backup & Replication is not supported, follow the steps below to update the product on
a Generic ARM-based device manually:
1. Download the latest Generic ARM-based NAS updater from  www.nakivo.com/resources/download/update/.
2. Upload the updater to the machine on which the Director is installed. 
Important
Make sure you are using the binary transfer mode when uploading the updater to the machine with a Linux
OS. For example:
l Upload the installer from a Windows-based machine
l Upload the product from a Linux-based machine: run the following command: wget 'server_
ip/shared/NAKIVO_Backup_Replication_vX.X.X_Updater.sh'
3. Log in to the Generic ARM-based NAS machine and allow the execution of the updater file. For example: chmod
+x NAKIVO_Backup_Replication_vX.X.X_Updater.sh
4. Make sure that no jobs or repository maintenance tasks are running in the product.
If NAKIVO Backup & Replication is installed on a VM, create a snapshot of the VM prior to updating the product.
5. Execute the updater file with root privileges. For example: sudo ./NAKIVO_Backup_Replication_
vX.X.X_Updater.sh
6. Review the license agreement (press Space to go to the next page of the agreement). If you agree to the terms of
the license agreement, press “Y” and then press Enter.
7. Press the “Y” key and then press Enter to confirm that you wish to stop the services and begin the update
process.
8. Update all machines on which you have additionally deployed a Transporter.

- 276 -
Uninstalling NAKIVO Backup and Replication
l Uninstalling on Windows
l Uninstalling on Linux or Generic ARM-based NAS
l Uninstalling Director and Onboard transporter on Linux or Generic ARM-Based NAS

l Uninstalling Transporter on Linux or Generic ARM-Based NAS

l Uninstalling on Synology NAS

l Uninstalling on Western Digital NAS
l Uninstalling on QNAP NAS
l Uninstalling on ASUSTOR NAS
l Uninstalling NETGEAR ReadyNAS
l Terminating on Amazon EC2
l Uninstalling on FreeNAS

Uninstalling on Windows
To uninstall NAKIVO Backup & Replication, run the uninstaller:
1. Go to Start -> Control Panel and run Programs and Features.
2. Select NAKIVO Backup & Replication and click Uninstall.
3. In the NAKIVO Backup & Replication Uninstallation wizard, click Uninstall.
4. Click Close when the uninstallation process is completed.

Uninstalling on Linux or Generic ARM-based NAS

Refer to the sections below to learn how to uninstall NAKIVO Backup & Replication on a Linux OS or a generic ARM-
based NAS.

Uninstalling Director and Onboard Transporter on Linux or Generic ARM-based

NAS
To uninstall the Director and Onboard Transporter, which is installed with the Director by default, follow the steps
below:
1. Run the "uninstall" script which is located in the Ddirector folder inside the product installation folder. If the
product is installed in the default location, run: /opt/nakivo/director/uninstall 
2. Enter "U" and then press Enter to confirm uninstalling the application.

Uninstalling Transporter on Linux or Generic ARM-based NAS

To uninstall the Transporter, follow the steps below:
1. Run the "uninstall" script which is located in the transporter folder inside the product installation folder. If the
product is installed in the default location, run: /opt/nakivo/transporter/uninstall

- 277 -
 2. Enter "U" and then press Enter to confirm uninstalling the application.

Uninstalling on Synology NAS

Follow the steps below to uninstall NAKIVO Backup & Replication on a Synology NAS:
1. In the Synology NAS management interface, open the Package Center. 
2. Click NAKIVO Backup & Replication.
3. Choose Uninstall from the Actions list. 
4. Click OK in the message box that opens to confirm that you wish to uninstall the application. 
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
applications.

Uninstalling on Western Digital NAS

Follow the steps below to uninstall NAKIVO Backup & Replication on a Western Digital NAS:
1. Open the NAS My Cloud Dashboard and click Apps.
2. In the Installed Apps list, select NAKIVO Backup & Replication.
3. The NAKIVO Backup & Replication item opens to the right of the installed applications list. Click the Uninstall
button.
4. The Uninstall NAKIVO Backup and Replication dialog opens. Click OK to confirm that you wish to uninstall the
application and delete all application data and settings.
5. The Updating progress bar opens. Wait until the uninstallation completes.
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
applications.

Uninstalling on QNAP NAS

Follow the steps below to uninstall NAKIVO Backup & Replication on a QNAP NAS:
1. Open the QNAP NAS Desktop and click App Center.
2. The App Center dialog opens. In the My Apps list, locate the NAKIVO Backup & Replication application and open
the list of applicable actions by clicking the drop-down button.
3. In the list of applicable actions, click Remove.
4. In the dialog that opens, click OK to confirm removing the application and application-relevant user data.
5. Wait until the uninstallation is complete.
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
applications.

Uninstalling on ASUSTOR NAS

Follow the steps below to uninstall NAKIVO Backup & Replication on a QNAP NAS:

- 278 -
 1. Open the ASUSTOR NAS Desktop and click App Central.
2. In the list of installed applications, locate NAKIVO Backup & Replication, select it and then click the Remove
button.
3. In the dialog that opens, click OK to confirm that you wish to remove the application.
4. The Removing progress bar opens. Wait until the uninstallation is completed.
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
applications.

Uninstalling on NETGEAR ReadyNAS

Follow the steps below to uninstall NAKIVO Backup & Replication on NETGEAR ReadyNAS:
1. Open the NETGEAR ReadyNAS Admin Page and go to Apps > Installed Apps.
2. Locate NAKIVO Backup & Replication in the list of available applications. Alternatively, enter NAKIVO to the
filtering box in the upper left corner of the Admin Page.
3. Click the Remove button below the application item.
4. The Confirm Deletion dialog box opens. Click Yes to confirm that you wish to uninstall NAKIVO Backup &
Replication on NETGEAR ReadyNAS.
5. Wait until the uninstallation is completed.
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
applications.

Terminating on Amazon EC2

Follow the steps below to terminate NAKIVO Backup & Replication that is launched as an Amazon EC2 instance:
1. Open AWS Management Console and go to EC2 Dashboard.
2. In the Instances menu, click Instances.
3. In the list of instances, locate the necessary NAKIVO Backup & Replication instance and select it.
4. In the Actions menu, go to Instance State and click Terminate.
5. In the Terminate Instances dialog, click Yes, Terminate to confirm that you wish to terminate your instance of
NAKIVO Backup & Replication.
6. Wait until the instance is terminated.
In about 60 minutes, the terminated NAKIVO Backup & Replication instance will be removed from the list of Amazon
EC2 instances.

Uninstalling on FreeNAS
Uninstalling a plugin deletes the associated FreeNAS jail because it is no longer required. Before uninstalling NAKIVO
Backup & Replication, make sure that there is no data or configuration in the jail that needs to be saved.
Follow the steps below to uninstall NAKIVO Backup & Replication on a FreeNAS:

- 279 -
 1. Log in to the FreeNAS system using the FreeNAS GUI.
2. In the left pane of the FreeNAS GUI, click Plugins -> Installed.
3. A list of installed plugins opens. For the desired NAKIVO plugin, click the Options button and then Delete.
4. The Delete dialog opens asking to confirm the operation. Click Delete.
When the uninstallation process is completed, NAKIVO Backup & Replication will be removed from the list of installed
plugins.

- 280 -
Settings
This section covers the following topics:
l “General” on page 282
l “Inventory” on page 329
l “Transporters” on page 339
l “Backup Repositories” on page 364
l “Virtual Appliance Configuration” on page 444
l “Multi-Tenant Mode Configuration” on page 448
l “Support Bundles” on page 457
l “Built-in Support Chat” on page 459
l “Replacing License” on page 466

- 281 -
General
This section contains the following topics: 
l “Bandwidth Throttling” on page 283
l “Branding Configuration” on page 286
l “Email Notifications” on page 289
l “Configuring Events” on page 288
l “Self-Backup Configuration” on page 292
l “System Migration” on page 296
l “System Settings” on page 298
l “Users and Roles” on page 327

- 282 -
Bandwidth Throttling
With bandwidth throttling settings, you can configure how LAN/WAN bandwidth is consumed by NAKIVO Backup &
Replication jobs. Bandwidth consumption is managed with bandwidth rules. When a bandwidth rule is applied to your
job, the speed of data transfer from source to target will not exceed the specified limit. Refer to “Advanced Bandwidth
Throttling” on page 45 for a description of bandwidth rules.
This topic contains the following instructions:
l Accessing Bandwidth Throttling Settings
l Creating Bandwidth Rules
l Managing Bandwidth Rules

Accessing Bandwidth Throttling Settings

To access bandwidth throttling settings, follow the steps below:
1. Click Settings in the left pane of the application to open the Settings dashboard.
2. In the General tab of the Settings dashboard, click Bandwidth throttling.

The Bandwidth throttling section opens.

Creating Bandwidth Rules

Please follow the steps below to create a bandwidth rule:
1. In the Bandwidth throttling section of the General tab of Settings, click Create New Rule.
2. The New Bandwidth Rule dialog opens. Proceed as follows:
a. Choose a type for your bandwidth rule:
l Global: The rule will be applied to the whole application.
l Per job: The rule will be applied to the selected jobs.
Note

- 283 -
 When applied to specific jobs, Per job bandwidth rules have higher priority over Global bandwidth
rules.
b. Name: Enter a name for your bandwidth rule.
c. Throttle bandwidth to: Enter the value of the bandwidth limit; and choose the measurement unit: kbit/s,
Mbit/s, or Gbit/s.
Notes
For your convenience, a description is available below the value you've entered, explaining what the
l

value means.
l In some cases, the actual data transfer speed may exceed the limit you set by up to 0.3 MByte/s or

2.4 Mbit/s.
d. Rule schedule: Choose either of the following:
l Always active: The rule will always be active.
l Active on schedule: The rule will be active on schedule. When chosen, the following options are
available:
a. Starting at and ending at: Enter the time, in hours and minutes, when the rule will be active.
b. Days: Select weekdays for which the rule will be active.
c. Time zone: Choose a time zone of your rule.
l Disabled: The rule will be disabled.
e. Show/Hide jobs: This option is available for the Per job rule type only. Select jobs for which the rule will be
active.
3. Click Save.

Managing Bandwidth Rules

You can manage bandwidth rules with the following commands:
l Edit: The Edit Bandwidth Rule dialog opens where you can modify your rule.
l Disable/Enable: When applied, the command will disable/enable the rule.

- 284 -
 l Remove: When applied, a dialog will open asking you to confirm the operation. Click Delete to confirm that you
wish to delete your rule.

Note
Per job bandwidth rules can also be created/managed on the Options page of the wizard during creating/editing the
corresponding jobs. Please refer to the topics:
l “Creating VMware Backup Jobs” on page 468
l “Creating Backup Copy Jobs” on page 497
l “Creating VMware Replication Jobs” on page 695
l “VMware VM Recovery” on page 593

- 285 -
Branding Configuration
You can change the product branding settings such as product name, logo, background, and so on. To configure these
product settings, follow the steps below:
1. Click Settings in the left pane of the product.
2. Go to the General tab and click Branding. 

3. Change the following, as appropriate:

l Product title
l Company name
l Website URL
l Contact email
l Support email
l Contact phone
l Bookmark icon
l Global logo
l Page background

4. Click Apply.

- 286 -
During upload, the logo and bookmark icon images are internally resized while preserving the aspect ratio. The
background image is used as it is. To get the best image quality, follow the recommendations below.

Image Best format Best resolution

Global logo .png 40x40

Page background .jpeg 1920x1440

Bookmark icon .png 16x16

- 287 -
Configuring Events
NAKIVO Backup & Replication can store and display system events. By default, events are stored for 60 days; you can
change the time period in Settings.
To view events, follow the steps below:
1. Click Settings in the left pane of the product.
2. Open the General tab and click Events. The Events page opens, displaying the NAKIVO Backup & Replication
system events.
3. Optionally, you can enter a search string to the Search box. This allows you to see events related only to NAKIVO
Backup & Replication items – Transporters, repositories, jobs, backups, and replicas,– contained in your search
string.
4. Optionally,  you can select Show only warnings and alarms. If selected, the events list displays only warnings and
alarms.
5. Optionally, you can select Filter by date and enter the beginning and ending dates for events filtering. This allows
you to limit the events list within a specific time period.
6. If required, navigate between pages by using the Page control.

- 288 -
Email Notifications
l “Email Settings” below
l “Email Notifications” on the next page
l “Automatic Reports” on the next page
NAKIVO Backup & Replication can send notifications and reports over email. To receive automatic notifications,
configure email settings by following the steps below:
1. Log in to NAKIVO Backup & Replication.
2. Click Settings in the left pane of the product.
3. Go to the General tab.
4. Click Email notifications to configure email settings, email notifications, and automatic reports section on the
page that opens.

Email Settings
1. To set email settings, fill out the fields in the Email settings section:
l SMTP server: The address of the server responsible for sending emails.
l SMTP username: The username on the server (usually the same as the email username).
l SMTP password: Usually the same as the password to your email.
l SMTP port: Depends on encryption type.
l Encrypted connection: Select the type of encryption:
l Never: Always use a plaintext connection. Not recommended.
l TLS, if possible: Start with plaintext, then use STARTTLS to switch to secure connection if supported
by the server.
l TLS, required: Start with plaintext, then use STARTTLS to switch to secure connection; drop the
connection if not supported by the server.
l SSL, required: Use the SSL-encrypted connection.
2. Click Send Test Email to verify that the settings are correct.

- 289 -
 Note
If you want to use a Gmail account to receive email notifications, turn on the Less secure apps access setting by
navigating to Manage your Google Account>Security in your Google account. 

Email Notifications
To set Email notifications, fill out the fields in the Email notifications section: 
l Send alarm (error) notifications: If this option is selected, NAKIVO Backup & Replication will send email
notifications to the specified recipients in case an error (for example, a job failure) occurs in the product.
l Send warning notifications: If this option is selected, NAKIVO Backup & Replication will send email notifications
to the specified recipients in case the product generates a warning message (for example, lost connection to a
host or Backup Repository).  
l Limit email notification frequency: This option provides you with the ability to set up a notification email
frequency and hourly limit. If notification emails exceed the hourly limit, all new notifications will be delivered the
next hour. If deselected, notification emails will be sent every 5 minutes with no hourly limit.
l Email notification recipients: Specify the recipients who will be receiving alarm and warning notifications (if
enabled).

Automatic Reports
To set automatic reports, fill out the fields in the Automatic Reports section: 
l Attach PDF copy to all automatic reports: If selected, a PDF copy of the report will be attached to each
automatic job report and to the Overview report. Note that this increases the size of email messages.
l Send job reports on each job completion: If this option is selected, NAKIVO Backup & Replication will send an

- 290 -
 HTML report after the completion of every job (regardless of the job success or failure) to email addresses
specified in the text field. Use a semi-colon to separate multiple email addresses.
l Send Overview report on schedule to: If this option is selected, NAKIVO Backup & Replication will generate the
Overview report (which includes information about all jobs and groups in the product) on the date and time
specified in the scheduler and will send the report to the recipients specified in the text field. Use a semi-colon to
separate multiple email addresses.
l Send Protection Coverage report on schedule to: If this option is selected, NAKIVO Backup & Replication will
generate the Protection Coverage report. This includes information about all VMs & instances protected by
backup and/or replication jobs as well as the information about all unprotected VMs & instances. The report will
be sent to the recipients specified in the text field on the date and time specified in the scheduler. Use a semi-
colon to separate multiple email addresses.

Click Apply when all settings are configured.

- 291 -
Self-Backup Configuration
The self-backup feature allows you to automatically protect configuration settings of your NAKIVO Backup & Replication
instance. For more information, refer to “Self-Backup Feature” on page 42.
Note
Self-backup is not supported for the multi-tenant configuration.
To configure self-backup options, proceed as described in the following sections:
l “Accessing Self-Backup Options” below
l “Setting Up Self-Backup Destination” below
l “Self-Backup Schedule” on page 294
l “Self-Backup Retention” on page 295
l “Recovering from Self-Backup” on page 295

Accessing Self-Backup Options

To access self-backup options, follow the steps below:
1. Click Settings in the left pane of NAKIVO Backup & Replication.
2. Go to the General tab and click Self-backup.

Setting Up Self-Backup Destination

To configure a self-backup destination, follow the steps below:
1. Select Back up system configuration to all repositories to enable all repositories in the list of repositories where
system configuration will be backed up. If deselected, you can remove specific repositories from the list.
Important

- 292 -
 Backing up your NAKIVO Backup & Replication system configuration to a DD Boost storage unit Backup
Repository causes the DD Boost storage unit to be unmounted. Therefore, to avoid re-adding the DD Boost
storage as an existing Backup Repository manually, exclude DD Boost storage unit repositories from the list of
repositories for self-backup.

2. If necessary, remove a Backup Repository from the list of repositories for self-backup:
1. Hover the pointer over the header of the Backup Repository and then click Remove.
2. In the dialog that opens, choose either of the following:
l Remove repository and keep self- backups: Removes the selected Backup Repository from the list
and keeps the self-backups.
l Remove repository and self-backups: Removes both the selected Backup Repository and self-
backups.
3. Click Remove to confirm your operation.

3. If necessary, add a Backup Repository to the list:

1. Click Add backup repository to add repositories to the list of repositories for system backing up.
2. In the Backup Repositories dialog that opens, select the necessary repositories and close the dialog.

- 293 -
 4. When ready with configuring the self-backup destination, click Apply.

Self-Backup Schedule
To configure the self-backup schedule, follow the steps below:
1. In the Start at group of boxes, enter time to trigger starting the self-backup. You can choose a specific time zone
from the list, enter the hours and minutes of the day, and select the necessary days of the week.
2. If you need to start the self-backup immediately, click Run Self-backup Now.
3. When ready with configuring the self-backup schedule, click Apply.

- 294 -
Self-Backup Retention
In the Retention section of the self-backup settings, you can enter a number of recovery points to be kept for the self-
backup. To apply your settings, click the Apply button.

Recovering from Self-Backup

To recover the configuration of NAKIVO Backup & Replication from a self-backup stored in a Backup Repository, do the
following:
1. Go to Settings > Repositories.
2. Select one of the repositories that contain a self-backup.
3. Select the self-backup from the Backups list and click Recover.
4. Select a recovery point and click Restore.
5. Wait while the system configuration is restored. When the self-backup recovery process is completed, a message
announcing success appears.
Note
If a selected recovery point was created from an encrypted self-backup, you will have to enter the password to it.

- 295 -
System Migration
NAKIVO Backup & Replication provides you with the ability to migrate all your settings (including inventory, jobs,
credentials, transporter settings, and so on) to a new instance (copy) of the product.
Important
System configuration export and import are designed for migration purposes only, and not to serve as a system
configuration backup. After you have exported system configuration from an old instance of the product, do not run
jobs in that old instance. Doing so will result in failed jobs in the new instance after the migration. All jobs will have to be
recreated, and full initial job run will be required.
See the topics below for more information:
l Exporting System Configuration
l Importing System Configuration

Exporting System Configuration

To export system configuration from the old deployment, follow the steps below:
1. Click Settings in the left pane of the product.
2. Click System Migration in the General tab.
3. Click Export system configuration.
4. In the dialog window that appears, click Export.

5. Click Proceed to confirm the operation.

Note
All activities in the old instance (such as jobs and recovery sessions) will be automatically stopped and all jobs will
be disabled.
6. Wait until the export is completed and download the export bundle.
7. Do not run jobs in the old instance.

- 296 -
Importing System Configuration
To import system configuration into a new instance of the product, follow the steps below:
1. Click Settings in the left pane of the product.
2. Click System Migration in the General tab.
3. Click Import system configuration.
4. In the dialog window that appears, locate the system configuration bundle using the Browse button.

5. Click Import.
6. Click Proceed to confirm the operation.
Important
l If there is any existing data in the new instance, it will be overwritten with the import operation.
l If a physical configuration of your source deployment differs from a target deployment, a Backup
Repository may become inaccessible after the bundle import is completed.
7. Wait until the import is completed, and close the dialog window.
Notes
l Backup Repositories are not migrated by the system configuration export and import. If you have a local Backup
Repository on the old instance of the product, you may want to move it to the new location. After moving the
Backup Repository, you may need to edit Backup Repository settings in the new instance, s that the new settings
refer to the actual Backup Repository location.
l In case a custom TLS/SSL certificate of the Web server was used in the old instance, a manual service restart will
be required in the new deployment.

- 297 -
System Settings
To configure the system settings, follow the steps below:
1. Click Settings in the main menu on the left.
2. Go to the General tab and click System settings.

3. Set the following options:

1. In the System section:
l Store system events for the last x days: Events older than the specified number of days (can be
from 10 to 365) will be deleted.
l Store job history for the last x days: The history of the jobs older than the specified number of
days will be deleted.
l Auto log out after x minutes of inactivity: When this option is selected, the current user will be
automatically logged out of NAKIVO Backup & Replication after the specified period of inactivity.
l Auto retry failed jobs x times with y minutes interval: When this option is selected, failed jobs will

- 298 -
 be automatically retried the specified number of times (from 2 to 10) and with the specified time
interval (from 1 to 60). Jobs with failed backup, replication, and recovery remain in the “running”
state until all retries have either succeeded or failed.
l Retry critical errors: When this option is selected, NAKIVO Backup & Replication tries to
automatically rerun jobs with critical and non-critical errors a specified number of times.
l Auto upload support bundles to support team server: When this option is selected, NAKIVO
Backup & Replication automatically creates, encrypts, and uploads support bundles once a day to a
NAKIVO support server. The NAKIVO Support team may use this information to improve the
product experience and to identify and resolve product issues faster.
l Enable built-in support chat: When this option is selected, you can contact a NAKIVO
representative via chat in the NAKIVO Backup & Replication interface. When selected in the multi-
tenant mode, the built-in support chat is available to all tenants of the NAKIVO Backup & Replication
instance.
l Display special offers: When this option is enabled, the NAKIVO special offers toolbar appears in
the NAKIVO Backup & Replication interface. 
l Continue to update even if self-back fails: When this option is selected, updates proceed even if
self-backup cannot be performed.
l You can click  Restart Director service to stop all current activities and restart the Director. After
clicking the link, a confirmation window appears. Click Reboot to confirm the restart.
2. In the Tape Options section:
l Auto erase expired tapes: When this option is selected, expired tapes are erased automatically. 
Important
If this option is selected, the following prerequisites must be met for a cartridge to be erased:
l All recovery points within the tape cartridge are expired.
l There are no dependent recovery points on other tape cartridges.
l The product keeps at least one full chain of recovery points.
l Wait for next tape for: Specify how long the system should wait for the next tape if there is no
appropriate amount. Select the Send email notification checkbox to receive email notifications.
l Auto refresh tapes every: Select how often the contents of the tapes are refreshed in minutes or
hours. Deselect if refreshing is not required.
3. In the Processing Options section:
l Auto remove deleted VMs and instances from jobs: This option applies to a protected container
(such as a VMware cluster or EC2 region). When this option is selected, if NAKIVO Backup &
Replication discovers (during the inventory refresh) that a VM(s) and/or EC2 instance(s) is no longer
available in the protected container, NAKIVO Backup & Replication automatically removes these
VMs and EC2 instances from all jobs.
l Process every source machine by one job at a time: When this option is selected, all machines in

- 299 -
 backup and replication jobs are processed by one job at a time only. Running jobs and respective
source objects will not be affected after changing this setting. For physical servers, this option is
always enabled.
l Skip swap files and partitions during processing: When this option is selected, swap files and
partitions are skipped during backup and replication to reduce backup size.
l Check for sufficient RAM on the target host for replication/recovery jobs: When this option is
deselected, NAKIVO Backup & Replication does not check whether the amount of RAM on the
target host is sufficient for replication and recovery jobs.
l LVM Snapshot allocation size: This option allows you to set an LVM allocation snapshot size for a
Linux physical server backup. The default size is 1 GB. The maximum size is 1000 GB. 
4. In the Auto Refresh section: 
l Auto refresh inventories every X minutes: Specify how often you want your inventories to be
refreshed. 
l Auto refresh Transporters every X minutes: Specify how often you want your Transporters to be
refreshed. 
l Auto refresh repositories every X minutes: Specify how often you want your inventories to be
refreshed. 
5. In the Regional options section, set:
l Clock format
l Short date format
l Long date format
l First day of week
l Decimal symbol
l Default time zone
6. In the Web Interface TLS/SSL Certificate section, you can either:
l View current certificate: A dialog containing the current certificate information opens.
l Install new certificate: A dialog opens allowing you to install a new TLS/SSL certificate for the NAKIVO
Backup & Replication web interface. Certificates are generated either internally or through certification
authorities. Proceed as follows to install a new certificate:
l Click Browse and navigate to the location of either of the following certificate file types:

l Private key: A file in the *.key format.

l Private key password (optional): A password for your private key.

l Certificate file: A file in the *.pem, *.crt, *.cer, *.p7b, or *.p7s format.

- 300 -
 l Intermediate certificate (optional): A file in the *.pem, *.crt, *.cer, *.p7b, *.p7s format.

l Click Install.
Notes
l NAKIVO Backup & Replication supports Certificates with the RSA algorithm only.  
l In the Web Interface TLS/SSL Certificate section, you can see a notification about imminent TLS/SSL Certificate
expiration in 30 days and onwards. If your certificate has expired, you will be asked to install a valid certificate.

- 301 -
Users and Roles
Accessing NAKIVO Backup & Replication is possible either with a user account created in the product or with an account
added to the product from Active Directory. Each user in the product is assigned a role, which is a set of specific
permissions.
l Managing Users and Roles

l Navigating Users View

l Navigating AD Groups View

Managing Users and Roles

Managing users and roles can be done by following these steps:
1. Log in to NAKIVO Backup & Replication.
2. Click Settings (cog icon) in the left pane of the product.
3. Go to the General tab and click Users and Roles.

Navigating Users View

To see the list of all local users, select the Users view from the drop-down list in the upper-left pane. On this page of the
solution you can do the following:
l See the list of all local users added to NAKIVO Backup & Replication.
l Sort the list by Name, Role, or Group by clicking on the respective name of the column.
l Filter the list of users by entering the name of the user fully or partially into the Search bar or by selecting the
Filter option.
l Clicking Filter opens a new window that allows you to filter the list of local users according to Name, User
name, Email, Group, Role, and Status.
l Add a new local user by clicking Add User.
l Integrate Active Directory account by clicking AD Integration.

- 302 -
 l Edit, delete, disable, and assign a new role to the local user individually. This can also be done in bulk by checking
the box in the upper left pane to select all users and clicking Bulk Action.
Note
When selecting all local users to apply a bulk action, NAKIVO Backup & Replication selects only those users that
are displayed on the screen.
l Edit the role assigned to the local use by clicking on the name of the role in the respective column.

Navigating AD Groups View

To see the list of all Active Directory groups, select the AD Groups view from the drop-down list in the upper-left pane.
On this page of the solution you can do the following:
l See the list of all AD groups added to NAKIVO Backup & Replication.
l Sort the list by Name, Users, or Role by clicking on the respective name of the column.
l Filter the list of users by entering the name of the user fully or partially into the Search bar or by selecting the
Filter option.
l Clicking Filter opens a new window that allows you to filter the list of local users according to Name, Role,
and Status.
l Add a new AD group by clicking Add AD group.
l Integrate Active Directory account by clicking AD Integration.
l Edit, delete, disable, and assign a new role to the AD group individually. This can also be done in bulk by checking
the box in the upper left pane to select all groups and clicking Bulk Action.
Note
When selecting all AD groups to apply a bulk action, NAKIVO Backup & Replication selects only those groups that
are displayed on the screen.
l Edit the role assigned to the local use by clicking on the name of the role in the respective column.
For details, refer to the following sections:
l “Managing Active Directory Users” on page 304
l “Managing Local Users” on page 311
l “Managing User Roles” on page 319

- 303 -
Managing Active Directory Users
With NAKIVO Backup & Replication, you can configure Active Directory integration at any time. You can also freely add,
edit, disable, delete AD users, or assign a role to them. For details, refer to the topics below:
l “Adding Active Directory User” on page 305
l “Assigning Role to Active Directory User” on page 306
l “Configuring Active Directory Integration” on page 307
l “Deleting Active Directory User” on page 308
l “Disabling Active Directory User” on page 309
l “Editing Active Directory User” on page 310

- 304 -
Adding Active Directory User

After configuring AD integration in the Active Directory Configuration wizard, you can proceed with adding AD user
(s). Proceed as follows:
1. Optionally, you can filter the tree of Active Directory users by entering a string to the Search box. You can enter a
section or the whole name of the item.
2. Select Active Directory users and groups by placing a checkmark to their left.
3. The selected items appear in the right pane of the page. If necessary, reorder the selected items by dragging them
to a new position. By doing so, you can specify to add the most important users and groups first.
4. Review the list of selected items. If necessary, remove a selected user or group from the list in either of the
following ways:
1. Deselect the item in the left pane. This will remove the item from the right pane.
2. In the right pane, hover the pointer over the item you wish to remove and click the Remove button. This
will deselect the item in the left pane.
5. In the Role list, choose a user role to be assigned to the users.

6. To unhide permissions granted to the users based on the role assigned, click the Show button beside the
Permissions label. To hide the user permissions again, click Hide.
7. In the lower right corner of the page, click Add. Active Directory users appear in the NAKIVO Backup & Replication
list of users.

- 305 -
Assigning Role to Active Directory User

Follow the steps below to assign a role to an Active Directory user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the Active Directory user, and then click Manage
in the rightmost column of the row.
3. In the menu that opens, click Assign role.
4. In the dialog box that opens, select a new user role from the Role list and then click Save.

The Active Directory user appears in the list of users with the assigned role.

- 306 -
Configuring Active Directory Integration

To configure Active Directory integration, follow these steps:

1. Go to Settings > General > Users & Roles.
2. The Users & Roles page opens in the Users view. Click the Configure AD Integration button.
3. The Active Directory Configuration Wizard opens on the Settings page. Proceed as follows:
1. In the Domain name box, enter the domain name.
2. In the Preferred DC hostname/IP box, enter the name of the preferred domain controller or its IP address.
3. Optionally, you can enter the name of the preferred Active Directory groups in the Preferred prioritized
groups box.
Note
If a user is a member of two or more Active Directory groups, enter the prioritized group’s name in this
field.
4. In the Domain user login box, enter the username that will be applied when integrating Active Directory.
5. In the Domain user password box, enter the user password that will be applied when integrating Active
Directory.
6. Refresh AD information every: Specify a periodicity of refreshing Active Directory information.
7. Click the Test Integration button to verify the successful integration with Active Directory.

8. If Active Directory integration is tested successfully, a checkmark appears beside the Test Integration
button. Then click Next to go to the next page of the wizard. If you fail to connect to the AD domain, refer
to the Knowledge Base article for possible causes.
9. On the Users page of the wizard, proceed with adding an Active Directory user.
When the wizard closes, the Users & Roles page opens, displaying the newly-added Active Directory users in the list of
users.

- 307 -
Deleting Active Directory User

Follow the steps below to delete an Active Directory user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the Active Directory user you want to delete, and
then click Manage in the rightmost cell of the row.
3. In the menu that opens, click Delete.
4. In the dialog box that opens, click Delete to confirm that you wish to delete the AD user.

The Active Directory user disappears from the list of users.

- 308 -
Disabling Active Directory User

Follow the steps below to disable an Active Directory user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the Active Directory user you want to disable, and
then click Manage in the rightmost column of the row.
3. In the menu that opens, click Disable.
4. In the dialog box that opens, click Disable to confirm that you want to disable the Active Directory user.

The Active Directory user appears dimmed in the list of users.

- 309 -
Editing Active Directory User

Follow the steps below to edit an Active Directory user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. In the list of users, do either of the following:
a. Locate the Active Directory user and click its name.
b. Hover over the Active Directory user, click Manage in the rightmost column of the row.
c. Click Edit.

3. The Edit Active Directory User page opens. Edit the Active Directory user properties if necessary:
a. In the Description box, edit the user description.
b. In the Role list, edit the user role.
c. To unhide permissions granted to the user based on the role assigned, click the Show button beside the
Permissions label. To hide the user permissions again, click Hide.
d. Click Save to save your modifications to the Active Directory user.

- 310 -
Managing Local Users
With NAKIVO Backup & Replication, you can freely add, edit, disable, delete local users, or assign a role to them. For
details, refer to the topics below:
l “Adding Local Users” on page 312
l “Assigning Role to Local User” on page 314
l “Deleting Local User” on page 315
l “Disabling Local User” on page 316
l “Editing Local User” on page 317
The application has the following built-in local users:
l admin: This user has the Administrator role assigned. You cannot delete it, disable it, or assign another role.
l guest: This user has the View only role assigned, with configurable file and object recovery permissions. By
default, the account is disabled.

- 311 -
Adding Local Users

Follow the steps below to add a local user:

1. Go to Settings > General > Users and Roles
2. The Users and Roles page opens in the Users view. Click Add User.
3. In the menu that opens, click Local User.

4. The Add Local User page opens. Proceed as follows:

a. In the Username box, enter the user name.
b. In the Name box, enter the user’s real name.
c. In the Password box, enter the user password. To generate a password automatically and send it to the
user, select Generate password and send by.
d. In the Repeat password box, re-enter the user password.
e. In the Email box, enter the user’s email address.
f. In the Description box, optionally enter a user description.
g. In the Access level dropdown list, select an access level for the new user (for multi-tenant solutions only).
h. In the Role dropdown list, select a user role. Refer to “Managing User Roles” on page 319 for more details
about user roles.
i. To unhide permissions granted to the user based on the role assigned, click the Show button beside the
Permissions label. To hide the user permissions again, click Hide.
j. To proceed with creating another user after creating the current one, select Create another user.

- 312 -
 k. In the lower right corner of the page, click Add.

The local user appears in the list of users.

- 313 -
Assigning Role to Local User

Follow the steps below to assign a role to a local user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the local user, and then click Manage in the
rightmost column of the row.
3. In the menu that opens, click Assign role.
4. In the dialog box that opens, select a new user role from the Role drop-down list and then click Save.

The local user appears in the list of users with the assigned role.

- 314 -
Deleting Local User

Follow the steps below to delete a local user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the local user you wish to be deleted, and then
click Manage in the rightmost cell of the row.
3. In the menu that opens, click Delete.
4. In the dialog box that opens, click Delete to delete the local user.

The deleted user disappears from the list of users.

- 315 -
Disabling Local User

Follow the steps below to disable a local user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. Hover over the local user you wish to be disabled, and then
click Manage in the rightmost column of the row.
3. In the menu that opens, click Disable.
4. In the dialog box that opens, click Disable to disable the local user.

The disabled user appears dimmed in the list of local users.

- 316 -
Editing Local User

Please follow the steps below to edit a local user:

1. Go to Settings > General > Users & Roles.
2. The Users and Roles page opens in the Users view. In the list of users, do either of the following:
a. Locate the local user that you want to edit.
b. Hover over the local user, click Manage in the rightmost column of the row and then click Edit.

3. The Edit User page opens. Edit the local user properties if needed:
a. In the Name box, edit the user name.
b. In the Password box, edit the user password.
c. If you edited the user password, re-enter the user password in the Repeat password box.
d. In the Email box, edit the user’s email address.
e. In the Description box, edit the user description.
f. In the Role list, edit the user role.
g. To unhide permissions granted to the user based on the role assigned, click the Show button beside the
Permissions label. To hide the user permissions again, click Hide.

- 317 -
h. Click Save to save your modifications to the local user.

- 318 -
Managing User Roles
A user role with full access to the User management permission is assigned to your user profile to manage user
roles. You cannot edit or delete the user role that is assigned to your user profile. The following topics describe how to
manage roles of NAKIVO Backup &Replication users in detail:
l “Overview of User Roles” on page 325
l “Adding User Role” on page 320
l “Editing User Role” on page 323
l “Cloning User Role” on page 321
l “Deleting User Role” on page 322

- 319 -
Adding User Role

Follow the steps below to add a user role:

1. Go to Settings > General > Users & Roles.
2. On the Users & Roles page, switch to the Roles view. 
3. Click Add Role.
4. The Add Role page opens. Proceed as follows:
a. In the Role name box, enter the role name.
b. If you are working with a multi-tenant environment, choose either a tenant, master tenant, or all tenants,
from the Access level list.
c. In the Description box, optionally enter a user description.
d. To unhide permissions to be granted to the role, click the Show button beside the Permissions label. 
e. A list of permissions opens. Specify necessary permissions for the user role.
f. Click Add in the lower right corner of the page.
The user role appears in the list of roles.

- 320 -
Cloning User Role

Follow the steps below to clone a user role:

1. Go to Settings > General > Users & Roles.
2. On the Users & Roles page, switch to the Roles view. 
3. Hover over the user role, click Manage in the rightmost column of the row and then click Clone.
4. A dialog opens asking you to enter the name of the new user role. Enter the name of the new user role and click
Save.

The new user role appears in the list of roles.

- 321 -
Deleting User Role

Follow the steps below to delete a user role:

1. Go to Settings > General > Users & Roles.
2. On the Users & Roles page, switch to the Roles view. 
3. Hover over the user role, click Manage in the rightmost column of the row and then click Delete.
4. In the dialog box that opens, click Delete to confirm deleting the local user.

The user role disappears from the list of roles.

- 322 -
Editing User Role

Follow the steps below to edit a user role:

1. Go to Settings > General > Users & Roles.
2. On the Users & Roles page, switch to the Roles view. 
3. In the list of roles, do either of the following:
a. Locate the user role and click on it.
b. Hover over the user role, click Manage in the rightmost column of the row.
c. Click Edit.

4. The Edit User Role page opens. Edit the user role properties if needed:
a. In the Role name box, edit the user role name.
b. If you are working with a multi-tenant environment, you can change the access level for this role by
choosing another tenant, master tenant, or all tenants in the Access level list.
c. In the Description box, edit the user description.
d. You can view the Number of users assigned with this role and click view allto see their full list on a new
page.
e. To unhide permissions to be granted to the role, click the Show button beside the Permissions label. 
f. A list of permissions opens. Edit necessary permissions for the user role.

- 323 -
g. When ready to save the user role, click Save in the lower right corner of the page.

- 324 -
Overview of User Roles

NAKIVO Backup & Replication allows you to assign roles and grant specific permissions to users of the product.
l User Roles
l Access Levels
l Built-in User Roles

User Roles

A user role consists of a set of permissions that can be granted to a NAKIVO Backup & Replication user. Available
permissions are grouped by the following product objects:
l Calendar: Contains permissions for accessing the Calendar dashboard.
l Activities: Contains permissions for accessing the Activities dashboard.
l Global Search: Contains permissions for accessing Global Search.
l Configuration: Contains a series of permissions for accessing configuration of NAKIVO Backup & Replication.
l Jobs: Contains a series of permissions for managing jobs.
l User profile: Сontains a series of permissions for managing user profile.
l Help and Support: Сontains a series of permissions for accessing email support, online help center, chat support,
and system information.
l Aptare Report Generation: Contains permissions for managing Aptare report generation.

Access Levels

There are the following access levels that can be set up for particular permission:

- 325 -
 l No access:The user cannot view, edit, and run the commands, neither from the graphical interface nor from the
command line.
l View only: The user can view the commands in the graphical interface but cannot edit or run them; using the
command line, the user can only run the commands that do not change NAKIVO Backup & Replication objects.
l Run only: The user can only view and run commands, both from the graphical interface and the command line.
l Full access: The user can view, edit, and run the commands, both from the graphical interface and the command
line.
l Custom: A custom set of permissions is configured for a product object.

Built-In User Roles

The product offers you a number of built-in user roles:

l Backup operator
l Recovery operator
l Self-service administrator
l Self-service user
l View only
Built-in user roles can be used for performing typical user management tasks. If you need an extra level of security, you
can add a new user role or take a built-in user role as a starting point by cloning it.
The user profile can only have a single role assigned.

- 326 -
Users and Roles
Accessing NAKIVO Backup & Replication is possible either with a user account created in the product or with an account
added to the product from Active Directory. Each user in the product is assigned a role, which is a set of specific
permissions.
l Managing Users and Roles

l Navigating Users View

l Navigating AD Groups View

Managing Users and Roles

Managing users and roles can be done by following these steps:

1. Log in to NAKIVO Backup & Replication.
2. Click Settings (cog icon) in the left pane of the product.
3. Go to the General tab and click Users and Roles.

Navigating Users View

To see the list of all local users, select the Users view from the drop-down list in the upper-left pane. On this page of the
solution you can do the following:
l See the list of all local users added to NAKIVO Backup & Replication.
l Sort the list by Name, Role, or Group by clicking on the respective name of the column.
l Filter the list of users by entering the name of the user fully or partially into the Search bar or by selecting the
Filter option.
l Clicking Filter opens a new window that allows you to filter the list of local users according to Name, User
name, Email, Group, Role, and Status.
l Add a new local user by clicking Add User.
l Integrate Active Directory account by clicking AD Integration.

- 327 -
 l Edit, delete, disable, and assign a new role to the local user individually. This can also be done in bulk by checking
the box in the upper left pane to select all users and clicking Bulk Action.
Note
When selecting all local users to apply a bulk action, NAKIVO Backup & Replication selects only those users that
are displayed on the screen.
l Edit the role assigned to the local use by clicking on the name of the role in the respective column.

Navigating AD Groups View

To see the list of all Active Directory groups, select the AD Groups view from the drop-down list in the upper-left pane.
On this page of the solution you can do the following:
l See the list of all AD groups added to NAKIVO Backup & Replication.
l Sort the list by Name, Users, or Role by clicking on the respective name of the column.
l Filter the list of users by entering the name of the user fully or partially into the Search bar or by selecting the
Filter option.
l Clicking Filter opens a new window that allows you to filter the list of local users according to Name, Role,
and Status.
l Add a new AD group by clicking Add AD group.
l Integrate Active Directory account by clicking AD Integration.
l Edit, delete, disable, and assign a new role to the AD group individually. This can also be done in bulk by checking
the box in the upper left pane to select all groups and clicking Bulk Action.
Note
When selecting all AD groups to apply a bulk action, NAKIVO Backup & Replication selects only those groups that
are displayed on the screen.
l Edit the role assigned to the local use by clicking on the name of the role in the respective column.
For details, refer to the following sections:
l “Managing Active Directory Users” on page 304
l “Managing Local Users” on page 311
l “Managing User Roles” on page 319

- 328 -
Inventory
Prior to creating backup, replication, or recovery jobs, you need to add your virtual/cloud infrastructure to the
product’s Inventory. The discovered infrastructure is added to the internal product database, which is refreshed every 1
hour by default. Refer to the following sections to learn more: 
l “Adding VMware vCenters and ESXi hosts” on page 335
l “Managing Credentials” on page 336
l “Managing Inventory” on page 330

- 329 -
Managing Inventory
Refer to the following topics:
l “Refreshing Inventory” on page 332
l “Editing Inventory Items” on page 331
l “Removing Items from Inventory” on page 334

- 330 -
Editing Inventory Items
If the credentials of an inventory item are no longer correct, the connection to the inventory item will be lost. To re-
establish a connection, update the required fields in the product by following the steps below:
1. Click Settings in the left pane of the product.
2. Go to the Inventory tab.
3. Click the item you want to edit.
4. In the title of the item, click Manage and then click Edit.

5. Update the appropriate fields and click Apply.

- 331 -
Refreshing Inventory
NAKIVO Backup & Replication keeps the information about the discovered infrastructure in its internal database, which
is refreshed every 1 hour by default. During the inventory refresh, the product collects all required information about
your virtual infrastructure, such as a list of hosts and VMs, their power state, and so on.
Only one item can be refreshed at a time. If you have added multiple items to the inventory, they will remain in the
queue until they are able to be refreshed.Refer to the sections below to learn how to refresh the discovered
infrastructure.
l Changing Inventory Refresh Frequency
l Manually Refreshing All Inventory
l Manually Refreshing a Discovered Item

Changing Inventory Refresh Frequency

1. Click Settings in the left pane of the product.

2. Go to the Inventory tab.
3. Do either of the following:
l To prevent the product from automatically refreshing the inventory, deselect the Refresh inventory

every  X [time period] checkbox.

l To change the inventory refresh frequency, enter a new value in the Refresh inventory every X [time

period] field (from 1 to 60 minutes or from 1 to 24 hours).

Note
New setting are applied instantly and do not need to be saved.

Manually Refreshing All Inventory

To update all inventory items, follow the steps below:

1. Click Settings in the left pane of the product and go to the Inventory tab.
2. Click Refresh All.

Manually Refreshing a Discovered Item

To update a single discovered item, follow the steps below:

1. Click Settings in the left pane of the product and go to the Inventory tab.
2. Click the item that you would like to update.
3. In the title of the item, click Refresh.

- 332 -
- 333 -
Removing Items from Inventory
You cannot remove an inventory item if there is at least one backup or replication job that uses the item or its children.
In order to remove such items from the inventory, you first need to delete (or edit) the corresponding jobs so no
VMs/Instances are backed up or replicated on the host/server/account being removed.
To remove an item from the inventory, follow the steps below:
1. Click Settings in the left pane of the product and go to the Inventory tab.
2. Click the item that you wish to remove from inventory.
3. In the item title, click Manage, and then click Remove.
4. In the dialog that opens, click Remove.

- 334 -
Adding VMware vCenters and ESXi hosts
To add VMware vCenter servers and standalone ESXi hosts to the product, follow the steps below:
1. Navigate to Settings. 
2. Go to the Inventory tab and click Add New.
3. In the dialog that opens, click VMware vCenter or ESXi host.
4. The Add New VMware vCenter or ESXi Host page opens. Proceed as follows:
1. In the Hostname or IP field, specify the hostname or IP address of the vCenter server or standalone ESXi
host that you wish to add to the inventory.
vCenter-managed ESXi hosts should not be discovered directly by their IP addresses or hostnames.
Instead, you should add the vCenter that manages such ESXi hosts.
2. In the Username and Password fields, specify credentials of the vCenter server or standalone ESXi host
that you want to add to the inventory.
The credentials you specify should have full administrative privileges to the vCenter server or standalone
ESXi host.
3. Specify the Web services port in the appropriate field and click Add. After the process has completed
successfully, you can exit Settings and create jobs with the newly discovered VMs.

4. A dialog box may open informing you that the current Transporter does not support VMware vSphere and
asking you to deploy an additional Transporter. This is the case for NAKIVO Backup & Replication when it is
deployed on an ARM-based NAS. Click Got It to close the dialog.
Refer to “Deploying Transporter as VMware Appliance” on page 355 for more details about deploying
additional Transporters that support VMware vSphere.

- 335 -
Managing Credentials
NAKIVO Backup & Replication provides you with the ability to store your OS login and password, Amazon EC2
instance private keys or shh keys to your Linux machines. Refer to the following topics:
l Adding Credentials
l Editing Credentials
l Deleting Credentials

Adding Credentials
To add new credentials, do the following:
1. Click Settings in the left pane of the product.
2. Go to the Inventory tab.
3. Click Manage.
4. In the dialog that opens, click Manage Credentials.
5. In the Manage Credentials dialog that opens, click Add Credentials.

6. Then do the following:

l Type: Select the type of credentials:

l To add a username and password, fill out the Username, Password, and Description fields and click
Save.
l To add a private key to an Amazon EC2 instance or a Linux physical machine, do the following:
a. Private key:Select a private key from the Type menu.
b. Username: Enter a username for the private key.
c. Password: Create a password for the private key.
d. Repeat password: Repeat password.
Note
- 336 -
 If you generated your key with a passphrase, you have to enter this passphrase into the pass-
word and repeat password boxes.
e. Locate and select the private key.
Information
Supported key formats: RSA, DSA
Supported file extensions: no extension, .pem, .key, .cer, .der, .txt
f. Fill out the Description box.
g. Click Save.

You can now assign the credentials while creating jobs.

Editing Credentials
To edit credentials, do the following:
1. Click Settings in the left pane of the product.
2. Go to the Inventory tab.
3. Click Manage credentials.
4. Hover the mouse pointer over the record that you would like to edit, and click Edit.

- 337 -
 5. Make any required changes, and then click Save. 

Deleting Credentials
Do the following:
1. Click Settings in the left pane of the product.
2. Go to the Inventory tab.
3. Click Manage credentials.
4. Hover the mouse pointer over the record that you would like to delete, and click Delete.

5. Click Delete in the confirmation dialog that opens.

- 338 -
Transporters
The Transporter is one of NAKIVO Backup & Replication component that does all of the heavy-lifting: it performs
backup, replication, and recovery, as well as data compression, deduplication, and encryption. To learn how to add an
additional Transporter and how to manage it, refer to the topics below:
l “Adding Installed Transporters” on page 347
l “Deploying Transporter as VMware Appliance” on page 355
l “Managing Transporters” on page 340

- 339 -
Managing Transporters
Refer to the following topics:
l “Editing Transporters” on page 342
l “Refreshing Transporter Details” on page 344
l “Downloading Transporter's Credentials” on page 341
l “Removing (Deleting) Transporters” on page 346

- 340 -
Downloading Transporter's Credentials
If you want to re-import an Amazon EC2 or VMware Transporter into another installation of the NAKIVO Backup &
Replication, you need to have the Transporter's credentials. To obtain the credentials, click the Download key link next
to the corresponding Transporter.

Clicking the link downloads the ZIP file containing the Transporter's credentials.

- 341 -
Editing Transporters
To modify the settings of an existing Transporter, follow the steps below:
1. Click Settings in the left pane of the product.
2. Go to the Transporters tab and click on the Transporter you would like to edit.
3. In the Transporter title, click Manage and then click Edit.

4. A dialog opens for editing the Transporter settings. Edit the settings as required:
l Hostname or IP: Here you can edit the IP address or hostname of the machine on which the Transporter is
installed.
l In the Networking section:
l Transporter port: Enter a communication port for your Transporter.
l Data transfer ports: Enter a port range that will be used by your Transporter for actual data
transfer.
l In the Settings section:
l Transporter name: Edit the name of your Transporter.
l Maximum load: Edit the number of tasks concurrently processed by the Transporter.
l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to
the set maximum Transporter load to be used for recovery jobs exclusively. This allows for
running the specified amount of concurrent recovery jobs along with other types of jobs
without the need to wait for their completion. 

- 342 -
 l Enable debug logging for this transporter: Enable/disable debug level logging for the
Transporter. Having this option enabled on a permanent basis is not recommended.
5. Click Appy to save your changes.

The changes you have made are applied to the Transporter.

- 343 -
Refreshing Transporter Details
By default, NAKIVO Backup & Replication refreshes the information about Transporters every hour. During the
refreshing process, the product collects all the required information about all Transporters. Only one Transporter can
be refreshed at a time. If you have more than one Transporter, all others will remain in the queue until they are able to
be refreshed.
l Manually Refreshing All Transporters
l Manually Refreshing a Single Transporter

Manually Refreshing All Transporters

To update all Transporters, follow the steps below:

1. Click Settings in the left pane of the product and go to the Transporters tab.
2. Click Refresh All.

The update of all Transporters starts.

Manually Refreshing a Single Transporter

To update a single Transporter, follow the steps below:

1. Click Settings in the left pane of the product.
2. Go to the Transporters tab.
3. Select the Transporter you would like to update.
4. In the title of the Transporter, click Refresh.

- 344 -
The Transporter refresh starts.

- 345 -
Removing (Deleting) Transporters
To remove a Transporter from NAKIVO Backup & Replication, follow the steps below:
1. Click Settings in the left pane of the product.
2. Go to the Transporters tab.
3. Select the Transporter you would like to remove.
4. In the Transporter title, click Manage and then click Remove.

5. Click Remove in the message that appears. 

Important
The following Transporters cannot be removed:
l The Onboard Transporter (which is installed with the “Director” on page 128 by default)
l Transporters manually assigned to a job
l Transporters assigned to the backup repositories in Amazon Cloud.

- 346 -
Adding Installed Transporters
After you have installed a Transporter, you need to add it to NAKIVO Backup & Replication so that the Transporter can
be used for backup, replication, and recovery tasks. Refer to the following topics:
l Installed Service
l VMware Appliance
l Amazon EC2 Instance
l Nutanix AHV Appliance

Installed Service
Please follow the steps below to add a Transporter that is installed as a service:
1. Click Settings in the left pane of the product dashboard and go to the Transporters tab.
2. Click Add Existing Transporter and then click Installed service in the dialog that opens.

3. The Add Existing Transporter - Installed Service dialog opens. In the Hostname or IP box, enter the IP address
or a hostname of the machine on which the Transporter is installed.
Note
If you are adding the Transporter by a DNS name, make sure this DNS name can be resolved on the machines on
which the Director and any other Transporters (which you plan to use in conjunction with the current one) are
installed.
4. Click More options and fill out the following fields: 

- 347 -
 l In the Networking section:
l Transporter port: Specify the port number that will be used to connect to the Transporter.
l Data transfer ports: Specify a range of port numbers (from 1 to 65535) that will be used to transfer
data. The range you specify should contain at least 100 ports. Make sure that the ports you specify
are open in your firewall.
l In the Settings section:
l Transporter name: Specify a display name for the Transporter.
l Maximum load: Specify the maximum number of tasks that the Transporter should process
simultaneously. A task, for example, is a backup or replication of a single VM disk, or one granular
recovery session.
l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to set
maximum transporter load to be used for recovery jobs exclusively. This allows running the
specified amount of concurrent recovery jobs along with other types of jobs without the need to
wait for their completion. 
l Enable debug logging for this transporter: If needed, enable debug level logging for the current
transporter. It is not recommended to use this option on a permanent basis.
5. Click Add.

The Transporter is added to the product and is ready to be used for backup, replication, and recovery.

VMware Appliance
Please follow the steps below to add a Transporter that is deployed as a VMware appliance:
1. Click Settings in the left pane of the product dashboard and go to the Transporters tab.
2. Click Add Existing Transporter and then click VMware appliance in the dialog that opens.

- 348 -
3. The VMware Appliance dialog opens. Fill out the fields as described below:
l In the Host or cluster box, enter the IP address or name of the host or the cluster where the corresponding
virtual machine is deployed.
l In the Virtual machine box, specify the virtual machine on which the Transporter is installed.
l In the OS Username and OS Password fields, specify credentials for accessing the virtual machine.
l Click More options and fill out the following fields:
l In the Networking section:
l Transporter port: Specify the port number that will be used to connect to the Transporter.
l Data transfer ports: Specify a range of port numbers (from 1 to 65535) that will be used to
transfer data. The range you specify should contain at least 100 ports. Make sure that the
ports you specify are open in your firewall.
l In the Settings section:
l Transporter name: Specify a display name for the Transporter.
l Maximum load: Specify the maximum number of tasks that the Transporter should process
simultaneously. A task, for example, is a backup or replication of a single VM disk, or one
granular recovery session.
l Additional load for recovery jobs: Selecting this option reserves the Transporter's resources
exclusively for recovery jobs. This allows you to run recovery jobs concurrently with other
types of jobs without the need to wait for their completion. The Transporter resources will be
reserved according to the specified number.

- 349 -
 l Enable debug logging for this transporter: If needed, enable debug level logging for the
current transporter. It is not recommended to use this option on a permanent basis.
4. Click Add.

The Transporter is added to the product and is ready to be used for backup, replication, and recovery.

Amazon EC2 Instance

If you have already deployed a Transporter in Amazon EC2 and now wish to re-import the Transporter in a new instance
of NAKIVO Backup & Replication, do the following:
1. Click Settings in the left pane of the product dashboard and go to the Transporters tab.
2. Click Add Existing Transporter and then click Amazon EC2 instance in the popup that opens.

- 350 -
3. The Amazon EC2 Instance dialog opens. Fill out the fields as described below:
l AWS account: Choose an appropriate Amazon AWS Account from the list of Amazon AWS Accounts added
to the Inventory.
l Region: Choose a region in which an AWS EC2 instance with the Transporter is deployed.
l EC2 Instance: Select the Amazon EC2 Instance with the Transporter that you wish to add to the product.
l Private key: Click the Browse button to locate and upload the Private key for the Transporter Instance that
was created when you deployed the Transporter in the cloud.
l Click More options and fill out the following fields:
l In the Networking section:
l Transporter port: Specify the port number that will be used to connect to the Transporter.
l Data transfer ports: Specify a range of port numbers (from 1 to 65535) that will be used to
transfer data. The range you specify should contain at least 100 ports. Make sure that the
ports you specify are open in your firewall.
l In the Settings section:
l Operation mode: Choose either of the following Transporter operation modes:
l Always running
l Running while required
l Transporter name: Specify a display name for the Transporter.
l Maximum load: Specify the maximum number of tasks that the Transporter should process
simultaneously. A task, for example, is a backup or replication of a single VM disk, or one
granular recovery session. 

- 351 -
 l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to
set maximum transporter load to be used for recovery jobs exclusively.
l Enable debug logging for this Transporter: If needed, enable debug level logging for the
current transporter. It is not recommended that you use this option on a permanent basis.
4. Click Add.

The Transporter is added to the product and is ready to be used for backup, replication, and recovery tasks.

Nutanix AHV Appliance

Please follow the steps below to add a Transporter that is deployed as a Nutanix AHV appliance:
1. Click Settings in the left pane of the product dashboard and go to the Transporters tab.
2. Click Add Existing Transporter and then select Nutanix AHV Appliance.

- 352 -
3. In the Add Existing Transporter - Nutanix AHV Appliance dialog, enter the following options:
l Cluster: Select a cluster where the corresponding virtual machine is deployed.
l Virtual machine: Select the virtual machine on which the Transporter is installed.
l Username/Password: Enter credentials for accessing the virtual machine where the Transporter is
installed.
l Transporter port: Enter the port number that will be used to connect to the Transporter.
l Data transfer ports: Enter a range of port numbers (from 1 to 65535) that will be used to transfer data. The
range you specify should contain at least 100 ports. Make sure that the ports you specify are open in your
firewall.
l Transporter name: Enter a display name for the Transporter.
l Maximum load: Select the maximum number of tasks that the Transporter should process
simultaneously. A task, for example, is a backup or replication of a single VM disk, or one granular recovery
session.
l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to set maximum
transporter load to be used for recovery jobs exclusively.
l Enable debug logging for this transporter: If needed, enable debug level logging for the current

- 353 -
 transporter. It is not recommended that you use this option on a permanent basis.

4. Click Add. The Transporter is added to the product and can be used for backup, replication, and recovery.

- 354 -
Deploying Transporter as VMware Appliance

Note
If your instance of NAKIVO Backup & Replication is installed on ARM-based NAS, an external Transporter needs to be
deployed to work with VMware vCenters and ESXi hosts. This is because certain features are not supported by ARM-
based NASes.
Please follow the steps below to deploy a Transporter that supports VMware vCenter:
1. Go to Settings > Transporters and then click Deploy New Transporter.
2. In the dialog that opens, click VMware appliance.

3. In the Deploy New Transporter - VMware Appliance dialog that opens, proceed as follows:
l Transporter name: Enter a name for your Transporter.
l Host or cluster: Select a target host or cluster.
l Datastore: Select a target datastore.
l Virtual network: Select a target virtual network.
Note
An internet connection is required to deploy a new Transporter as a VMware appliance on the target host
or cluster.
l If necessary, access the advanced options for your Transporter by clicking More options and then entering
data for the following parameters:

- 355 -
 l In the Networking section:
l IP configuration: It can be either Automatic setup (DHCP), or Manual setup.
l IP address: If you have chosen Manual setup for the IP configuration, enter a Transporter IP
address.
l Subnet mask: If you have chosen Manual setup for the IP configuration, enter a subnet
mask.
l Default gateway: If you have chosen Manual setup for the IP configuration, enter a default
gateway.
l DNS configuration: It can be either Automatic setup (DHCP), or Manual setup.
l Primary DNS: If you have chosen Manual setup for the DNS configuration, enter a primary
DNS server IP address.
l Secondary DNS: If you have chosen Manual setup for the DNS configuration, enter a
secondary DNS server IP address.
l Transporter port: Enter a communication port for your transporter.
l Data transfer ports: Enter a port range that will be used by your transporter for actual data
transfer.
l In the Settings section:
l Maximum load: A number of tasks concurrently processed by the Transporter.
l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to
set maximum transporter load to be used for recovery jobs exclusively. This allows for
running the specified amount of concurrent recovery jobs along with other types of jobs
without the need to wait for their completion. 
l Enable debug logging for this transporter: When selected, it enables debug level logging for
the Transporter. It is not recommended to have this option selected on a permanent basis.
4. Click Deploy to confirm deploying the Transporter.

- 356 -
When deployment of the new Transporter finishes successfully, a message appears informing you about it.

- 357 -
Deploying Transporters in Amazon EC2
You need to deploy a Transporter in Amazon EC2 to enable the following features:
l Backing up VMware VMs and/or Amazon EC2 Instances to a backup repository located in Amazon EC2.
l Backing up Amazon EC2 Instances in a particular Amazon EC2 Region. 
NAKIVO Backup & Replication automates deploying a Transporter in Amazon EC2. To deploy a Transporter in Amazon
EC2 within the product interface, follow the steps below:
1. Click Settings in the left pane of the product dashboard and then go to the Transporters tab.
2. Click Deploy New Transporter and then click Amazon EC2 instance.

3. The Amazon EC2 instance dialog opens. Fill out the fields as described below:
l Transporter name: Enter a name for the Transporter.
l Region: Select an Amazon EC2 region where you wish to deploy the Transporter. This will enable you to
create a backup repository in the region as well as back up Amazon EC2 Instances available in the region. 
l Instance type: Choose a type of Amazon EC2 Instance (for example, "t2.medium") that will be used to
deploy the Transporter. Note that more powerful Instances may be able to process data faster, but will
cost more to run on Amazon EC2. 
l Click More options and do the following: 
l In the Networking section:
l Automatically configure VPC for this transporter: If selected, a new VPC with a single public
subnet will be created and used to deploy this transporter. If you want to deploy the
Transporter into a different VPC and subnet, deselect this option.

- 358 -
 l Network: Select a network to which the Amazon EC2 instance with the Transporter will
be connected. 
l Subnet: Select a subnet for the Amazon EC2 Instance with the Transporter. 
l Allowed traffic from: Enter the IP addresses of the machines that can connect to
the Amazon EC2 instance with the Transporter. Access from other IP addresses will be
restricted. 
Important
By default, the Amazon EC2 security group is not restricted, that is, the Transporter can be
accessed by and receive tasks from any machine. For security purposes, restrict traffic only
to trusted IP addresses.
l Transporter Port: Specify the port number that will be used to connect to the Transporter.
l Data transfer ports: Specify a range of port numbers (from 1 to 65535) that will be used to
transfer data. The range you specify should contain at least 100 ports. Make sure that the
ports you specify are open in your firewall.
l In the Settings section:
l Operation mode: If you select the Running while required option, the Amazon EC2 Instance
with the Transporter will be powered on only when the Transporter is required to run a
backup, replication, and recovery tasks. 
l Platform: Choose an OS for the instance where the Transporter will be deployed. 
l Maximum load: Specify the maximum number of tasks that the Transporter should process
simultaneously. An example of a task is processing a single VM disk or a single file recovery
session.
l Additional load for recovery jobs: If selected, the specified amount of tasks will be added to
set the maximum Transporter load to be used for recovery jobs exclusively. This allows for
running the specified quantity of concurrent recovery jobs along with other types of jobs
without the need to wait for their completion. 
l Enable debug logging for this Transporter: Enables debug level logging for the current
Transporter. Since this feature slows down Transporter performance, it is recommended that
you enable debug logging only for the investigation of support issues.
4. Click Deploy.

- 359 -
Important
l After you have deployed a Transporter in Amazon EC2, you need to download the Transporter Keys. The Trans-
porter Keys are used by NAKIVO Backup & Replication to access and manage the Transporter in Amazon EC2. If
you lose the current instance of NAKIVO Backup & Replication and install a new copy of the product, you will need
to provide the Transporter Keys to access the Transporter. 
l You may be additionally charged for using a 3rd-party resource. Please refer to the 3rd-party resource provider
documentation for details.

- 360 -
Deploying Transporter as Nutanix AHV Appliance
To enable NAKIVO Backup & Replication to create and run jobs within a Nutanix AHV cluster, a dedicated Transporter
must be deployed as a Nutanix appliance in that cluster.
Please follow the steps below to add a transporter as a Nutanix appliance:
1. Go to Settings > Transporters tab.
2. On the Transporters tab, click Deploy New Transporter and select Nutanix AHV Appliance from the drop-down
list.

3. In the Deploy New Transporter - Nutanix AHV Appliance dialog, specify the following options:
l Transporter name: Enter a name for the new Transporter.
l Cluster: Select a cluster where the transporter VM will run.
l Storage container: Select a storage container where the transporter VM will be located.
l Virtual network: Select a virtual network where the transporter VM will be connected.

- 361 -
4. Click Deploy if you want to go with the automatically selected networking options and default Transporter load
configuration. 
5. Alternatively, click More options if you wish to manually set the following options:
l IP configuration: Can be either Automatic setup (DHCP) or Manual setup. With manual setup selected,
specify an IP address, Subnet mask and Default gateway.
l DNS configuration: Can be either Automatic setup (DHCP) or Manual setup. With manual setup selected,
specify Primary and Secondary DNS.
l Transporter port: Enter a communication port for your Transporter.
l Data transfer ports: Enter a port range that will be used by your Transporter for actual data transfer.
l Maximum load: Specify the maximum number of tasks that the Transporter should process
simultaneously. A task, for example, is a backup or replication of a single VM disk, or one granular recovery
session.
l Additional load for recovery jobs: If selected, the specified quantity of tasks will be added to set the
maximum Transporter load to be used for recovery jobs exclusively. This allows for running the
specified amount of concurrent recovery jobs along with other types of jobs without the need to wait for
their completion. 
l Enable debug logging for this transporter: If needed, enable debug level logging for the current

- 362 -
 transporter. Using this option on a permanent basis is not recommended.

6. Click Deploy. The deployment process starts. Successfully deployed Transporter is displayed in the
Transporters tab.

- 363 -
Backup Repositories
A Backup Repository is one of the key components of NAKIVO Backup & Replication and is a regular folder where the
product stores backups and backup metadata. For more detailed information, refer to “Backup Repository” on
page 134.
This section covers repository-related topics such as creation, management, etc. of Backup Repositories and contains
the following articles:
l “Creating Backup Repositories” on page 365
l “Managing Backup Repositories” on page 397
l “Viewing Backup Repository Details” on page 416

- 364 -
Creating Backup Repositories
NAKIVO Backup & Replication allows you to create additional Backup Repositories for storing and restoring your
backup. You can use a local share, NFS share, CIFS share, EBS/Wasabi storage, or a deduplication appliance as a Backup
Repository location. To create a new Backup Repository, follow the steps below:
Important
Do not create Backup Repositories inside NAKIVO Backup & Replication installation folders. The data inside Director and
Transporter folders can be lost after the solution update.
1. In the NAKIVO Backup & Replication, navigate to Settings.
2. Go to the Repositoriestab and click Add Backup Repository.
3. Click Create new backup repository.

Choose one of the locations for storing your backups by completing the Create Backup Repository wizard as it’s
described in the sections below:
l “Local Backup Repository” on page 366
l “Backup Repository on CIFS Share” on page 370
l “Backup Repository on NFS Share” on page 375
l “Backup Repository on Deduplication Appliance” on page 391

- 365 -
Local Backup Repository
To create a Backup Repository locally on the machine on which the assigned Transporter is installed, choose a local
folder. Proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Local Folder and click Next to move to the next page
of the wizard. 

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following:

1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Enter the path to the local Backup Repository folder on the machine on which the assigned Transporter is
installed.
Example
/opt/nakivo/repository

- 366 -
 4. Click Next to go to the next page of the wizard.
Important
Before choosing this location, make sure that you have read and write permissions for the folder that will be used
as a repository.

Create Backup Repository: Options

On the Options page, do the following:

1. Select one of the following data storage types from the Data Storage drop-down list:
l Forever incremental: After the initial full backup, all subsequent backups transfer only changed data
(increments) to the Backup Repository.  
l Incremental with full backups:  After the initial full backup, backup jobs will store changed data
(increments) in separate files and will periodically create full backups as specified in the job settings. Backup
deduplication is not available when this option is selected.
2. Set up Storage Savings & Encryption options:
l Compression: Select a compression level that will be used to reduce the data size in the Backup
Repository. Note that higher compression levels consume considerably more CPU and may slow down VM
backup speed. The following options are available:
l Disabled: The data in the Backup Repository will not be compressed.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.
Note
This option cannot be configured after creating the Backup Repository.
l Deduplication: Leave the Enabled option to store only unique blocks of data in the Backup Repository in
order to save storage space.
Note
This option cannot be configured after creating the Backup Repository.
l Encryption: This option is available only if the Backup Repository is created locally on the machine on
which the Assigned Transporter is installed, and the machine is running a Linux OS. Select  Enabled from
the drop-down list and specify an encryption password. (The password will be required for importing the

- 367 -
 Backup Repository into a new instance of the product.) The product will encrypt the repository
destination (using ecryptfs for folders and cryptsetup (crypt-md) in LUKS mode for
devices/partitions) prior to creating the Backup Repository.
Notes
l To avoid ecryptfs errors, make sure that there are no other folders and files except the
NakivoBackup folder in the repository location.
l  Backup Repository encryption can significantly influence backup speed.
3. Set up Reliability & Maintenance options: 
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing in case the product detects symptoms of problems in the backup infrastructure such as
incorrect timestamps on metadata and data files. You can deselect this option and run self-healing
manually.
l Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing on
schedule. You can configure the schedule by clicking the schedule link when the option is selected. The
default schedule is set to run every day at 11 AM.
If Stop backup and recovery to run self-healing is selected, any jobs or recoveries which use this
repository will be stopped to run scheduled self-healing. Otherwise, scheduled self-healing will be skipped
in case there are running jobs or recoveries on this repository.
l Run full data verification on schedule: If selected, NAKIVO Backup & Replication will run full verification
of all data available in the Backup Repository on the specified schedule. The product will read each block of
data and ensure that it is identical to the data block that was read on the source VM during the backup.
This way, the product will verify each recovery points in the Backup Repository.
If Stop backup and recovery to run backup verification is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled data verification. Otherwise, scheduled data
verification will be skipped in case there are running jobs on this Backup Repository.
Note
Backup verification is a time-consuming process and consumes CPU of the Transporter assigned to the
Backup Repository. It is recommended that you schedule backup verification during non-working hours.
l Reclaim unused space on schedule: If required, select this option to run the Backup Repository space
reclaim process on schedule. Space reclaim will compact the data. Unused space will be reclaimed. Keep in
mind, that this process can be time-consuming. You have the following options:
l Space reclaim can be set to run on a daily/weekly or monthly/yearly basis.
l You can set specific time frames in the  Starting at and Ending fields to create a dedicated
maintenance window for Backup Repositories.
If Stop backup and recovery to run space reclaim is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled space reclaiming. Otherwise, scheduled space
reclaiming will be skipped in case there are running jobs on this Backup Repository.

- 368 -
 Important
Do not reboot/disconnect the assigned Transporter and underlying storage device while space
reclaim is in progress to avoid Backup Repository corruption.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled.
4. Schedule detaching of the Backup Repository: 
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and metadata
in a consistent state and then stops the product's interaction with the Backup Repository (so that the
Backup Repository can be copied or moved). You can use this feature, for example, for the disk-to-disk-to-
tape (D2D2T) data protection approach, in which backups are stored on a disk for fast operational
recovery, and copied to a tape (while the repository is detached) for archiving and long-term storage. 
l Delete and re-create the repository on attach: If this option is selected, all data in the Backup
Repository will be erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository will create full VM backups. You can use this option, for example, to create full
daily, weekly, or monthly VM backups and write them to tape or removable media.
5. Click Finish to finish creating the local Backup Repository. 

- 369 -
Backup Repository on CIFS Share
Choose this option if you want to create a Backup Repository on a Windows CIFS share. Before creating a Backup
Repository on a CIFS share, make sure that all the necessary prerequisites are met:
l The folder where you would like to create the Backup Repository exists on the share.
l The share can be accessed from the machine on which the Assigned Transporter is installed.
l You are using credentials with read and write permissions to the share.
l The share is compatible with Version 2 or later of the SMB protocol.
To create a Backup Repository on a Windows CIFS share, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select CIFS Share and click Next to move to the next page of
the wizard.

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following

- 370 -
 1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Enter the path to the CIFS share.
Example
Synology share path: \\10.30.30.61\ayunt_cifs1
4. Provide username and password in the appropriate boxes.
Note
If you're using domain credentials to access the share, enter your domain username via the following format:
domain\username.
5. Select Advanced mount options if needed. Refer to the mount man pages for a detailed description of CIFS share
mount options.
6. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

1. Select one of the following data storage types from the Data Storage drop-down list:
l Forever incremental: After the initial full backup, all subsequent backups will transfer and store only
changed data (increments) to the Backup Repository.  
l Incremental with full backups:  After the initial full backup, backup jobs will store changed data
(increments) in separate files and will periodically create full backups as specified in the job settings. Backup
deduplication is not available when this option is selected.
2. Set up Storage Savings & Encryption options:
l Compression: Select a compression level that will be used to reduce the data size in the Backup
Repository. Note that higher compression levels consume considerably more CPU and may slow down VM
backup speed. The following options are available:
l Disabled: The data in the Backup Repository will not be compressed.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.

- 371 -
 Note
This option cannot be configured after the Backup Repository is created.
l Deduplication: Leave the Enabled option to store only unique blocks of data in the Backup
Repository in order to save storage space.
Note
This option cannot be changed after the Backup Repository is created.
l Encryption: This option is available only if the Backup Repository is created locally on the machine
on which the Assigned Transporter is installed, and the machine is running a Linux OS.
Select Enabled from the drop-down list and specify an encryption password. (The password will be
required for importing the Backup Repository into a new instance of the product.) The product will
encrypt the repository destination (using ecryptfs for folders and cryptsetup (crypt-
md) in LUKS mode for devices/partitions) prior to creating the Backup Repository.
Notes
l To avoid ecryptfs errors, make sure that there are no other folders and files except the
NakivoBackup folder in the repository location.
l Backup Repository encryption can significantly influence backup speed.
3. Set up Reliability & Maintenance options: 
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing in case the product detects symptoms of problems in the backup infrastructure such as
incorrect timestamps on metadata and data files. You can deselect this option and run self-healing
manually.
l Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing on
schedule. You can configure the schedule by clicking the schedule link when the option is selected. The
default schedule is set to run every day at 11 AM.
If Stop backup and recovery to run self-healing is selected, any jobs or recoveries which use this
repository will be stopped to run scheduled self-healing. Otherwise, scheduled self-healing will be skipped
in case there are running jobs or recoveries on this repository.
l Run full data verification on schedule: If selected, the product will run full verification of all data available
in the Backup Repository on the specified schedule. The product will read each block of data and ensure
that it is identical to the data block that was read on the source VM during the backup. This way, the
product will verify each recovery points in the Backup Repository.
If Stop backup and recovery to run backup verification is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled data verification. Otherwise, scheduled data
verification will be skipped in case there are running jobs on this Backup Repository.

- 372 -
 Note
Backup verification is a time-consuming process and utilizes the CPU resources of the Transporter
assigned to the Backup Repository. It is recommended that you schedule backup verification during non-
working hours.
l Reclaim unused space on schedule: If required, select this option to run the Backup Repository space
reclaim process on schedule. Space reclaim will compact the data. Unused space will be reclaimed. Keep in
mind, that this process can be time-consuming. You have the following options:
l Space reclaim can be set to run on a daily/weekly or monthly/yearly basis.
l You can set specific time frames in the  Starting at and Ending fields to create a dedicated
maintenance window for Backup Repositories.
If Stop backup and recovery to run space reclaim is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled space reclaiming. Otherwise, scheduled space
reclaiming will be skipped in case there are running jobs on this Backup Repository.
Important
Do not reboot/disconnect the assigned Transporter and underlying storage device while space
reclaim is in progress to avoid Backup Repository corruption.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
4. Schedule detaching of the Backup Repository: 
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and metadata
in a consistent state and then stops the product's interaction with the Backup Repository (so that the
Backup Repository can be copied or moved). You can use this feature, for example, for the disk-to-disk-to-
tape (D2D2T) data protection approach, in which backups are stored on a disk for fast operational
recovery, and copied to a tape (while the repository is detached) for archiving and long-term storage.
l Delete and re-create the repository on attach: If this option is selected, all data in the Backup
Repository will be erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository will create full VM backups. You can use this option, for example, to create full
daily, weekly, or monthly VM backups and write them to tape or removable media.

- 373 -
5. Click Finish to finish creating the Backup Repository. 

- 374 -
Backup Repository on NFS Share
Choose this option if you wish to create a Backup Repository on an NFS share. Before creating a Backup Repository on
an NFS share, make sure that all the necessary prerequisites are met:
l The folder where you would like to create the Backup Repository exists on the share.
l The share can be accessed from the machine on which the Assigned Transporter is installed.
l You are using credentials with read and write permissions to the share.
To create a repository on an NFS share, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select NFS Share and click Next to move to the next page of
the wizard.

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following

- 375 -
 1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Enter the path to the NFS share.
Examples
QNAP share path: 10.30.30.109:/ayunt_nfs
FreeNAS share path: 192.168.3.2:/mnt/NFS_dataset/nfs01
Note
If the Assigned Transporter is installed on a Windows OS, you need to enable the "Client for NFS" feature on the
machine on which the Transporter is installed.
4. Select Advanced mount options if needed. Refer to the mount man pages for a detailed description of mount
options.
Note
To create a Backup Repository on a NEC HydraStor deduplication appliance, refer to Integrating with NEC
HydraStor.
5. Click Next to go to the next page of the wizard. 

Create Backup Repository: Options

On the Options page, do the following:

1. Select one of the following data storage types from the Data Storage drop-down list:
l Forever incremental: After the initial full backup, all subsequent backups will transfer and store only
changed data (increments) to the Backup Repository.  
l Incremental with full backups: After the initial full backup, backup jobs will store changed data
(increments) in separate files and will periodically create full backups as specified in the job settings. Backup
deduplication is not available when this option is selected. Select this option if you use a deduplication
appliance as a location for your Backup Repository.
2. Set up Storage Savings & Encryption options (disabled for deduplication appliances): 
l Compression: Select a compression level that will be used to reduce the data size in the Backup
Repository. Note that higher compression levels consume considerably more CPU and may slow down VM
backup speed. The following options are available:

- 376 -
 l Disabled: The data in the Backup Repository will not be compressed.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.
Note
This option cannot be configured after the Backup Repository is created.
l Deduplication: Leave the Enabled option to store only unique blocks of data in the Backup Repository in
order to save storage space.
Note
This option cannot be changed after the Backup Repository is created.
l Encryption: This option is available only if the Backup Repository is created locally on the machine on
which the Assigned Transporter is installed, and the machine is running a Linux OS. Select  Enabled from
the drop-down list and specify an encryption password. (The password will be required for importing the
Backup Repository into a new instance of the product.) The product will encrypt the repository
destination (using ecryptfs for folders and cryptsetup (crypt-md) in LUKS mode for
devices/partitions) prior to creating the Backup Repository. 
Notes
l To avoid ecryptfs errors, make sure that there are no other folders and files except the
NakivoBackup folder in the repository location.
l Backup Repository encryption can significantly influence backup speed.
3. Set up Reliability & Maintenance options: 
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing in case the product detects symptoms of problems in the backup infrastructure such as
incorrect timestamps on metadata and data files. You can deselect this option and run self-healing
manually.
l Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing on
schedule. You can configure the schedule by clicking the schedule link when the option is selected. The
default schedule is set to run every day at 11 AM.
If Stop backup and recovery to run self-healing is selected, any jobs or recoveries which use this
repository will be stopped to run scheduled self-healing. Otherwise, scheduled self-healing will be skipped
in case there are running jobs or recoveries on this repository.
l Run full data verification on schedule: If selected, the product will run full verification of all data available
in the Backup Repository on the specified schedule. The product will read each block of data and ensure
that it is identical to the data block that was read on the source VM during the backup. This way, the
product will verify each recovery points in the Backup Repository. 
If Stop backup and recovery to run backup verification is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled data verification. Otherwise, scheduled data

- 377 -
 verification will be skipped in case there are running jobs on this Backup Repository.
Note
Backup verification is a time-consuming process and utilizes the CPU resources of the Transporter
assigned to the Backup Repository. It is recommended that you schedule backup verification during non-
working hours.
l Reclaim unused space on schedule: If required, select this option to run the Backup
Repository space reclaim process on schedule. Space reclaim will compact the data. Unused space will be
reclaimed. Keep in mind, that this process can be time-consuming. You have the following options:
l Space reclaim can be set to run on a daily/weekly or monthly/yearly basis.
l You can set specific time frames in the  Starting at and Ending fields to create a dedicated
maintenance window for Backup Repositories.
If Stop backup and recovery to run space reclaim is selected, any running jobs which use this
Backup Repository will be stopped to run scheduled space reclaiming. Otherwise, scheduled space
reclaiming will be skipped in case there are running jobs on this Backup Repository.
Important
Do not reboot/disconnect the assigned Transporter and underlying storage device while space
reclaim is in progress to avoid Backup Repository corruption.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
4. Schedule detaching of the Backup Repository: 
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and
metadata in a consistent state and then stops the product's interaction with the Backup Repository (so
that the Backup Repository can be copied or moved). You can use this feature, for example, for the disk-
to-disk-to-tape (D2D2T) data protection approach, in which backups are stored on a disk for fast
operational recovery, and copied to a tape (while the repository is detached) for archiving and long-term
storage.
l Delete and re-create the repository on attach: If this option is selected, all data in the Backup
Repository will be erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository will create full VM backups. You can use this option, for example, to create full
daily, weekly, or monthly VM backups and write them to tape or removable media.

- 378 -
5. Click Finish to finish creating the Backup Repository. 

- 379 -
Backup Repository in Amazon EC2
Choose this option if you want to create a Backup Repository in Amazon EC2. The Backup Repository will be created in
the same region where the assigned Transported is located. 
Important
l To avoid disrupting NAKIVO Backup & Replication processes and data corruption, add NAKIVO Backup &
Replication to the white/exclusions list of the antivirus software running on the machine on which the NAKIVO
Backup Repository is set up.
l You may be additionally charged for using a 3rd-party resource. Please refer to the 3rd-party resource provider
documentation for details.
To create a repository on an Amazon EC2, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Amazon EC2 and click Next to move to the next page
of the wizard.

- 380 -
Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following

1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

1. In the Data Storage Type section, set up the following options:
l Data storage: Select one of the following data storage types:
l Forever incremental: After the initial full backup, all subsequent backups will transfer and store only
changed data (increments) to the Backup Repository.  
l Incremental with full backups:  After the initial full backup, backup jobs will store changed data
(increments) in separate files and will periodically create full backups as specified in the job settings.
Backup deduplication is not available when this option is selected.
l Volume type: Choose one of the following EBS volumes that will be used for creating the Backup
Repository:
l Cold HDD (sc1)
l Throughput Optimized HDD (st1)
l General Purpose SDD (gp2)
l Magnetic Standard
l Storage: Specify the size for the Backup Repository that will be allocated in Amazon EC2 using EBS Volumes.
The volumes will be attached to the selected Amazon EC2 Transporter.
l Storage Chunk: A Backup Repository in Amazon EC2 is created by using multiple EBS Volumes (chunks).
The maximum size of the Backup Repository is limited by 50 EBS Volumes (chunks) or 16 TB (whatever
comes first). The size of a storage chunk defines the size of each individual EBS volume. Also, the storage
will be resized (either manually or automatically) with the minimal step of the storage chunk specified here.
To scale up to 16000 GB, it is recommended that you have 400 GB storage chunk or bigger. Storage chunk
cannot be changed later.

- 381 -
 l Automatically resize storage: If this option is selected, the cloud storage will be automatically increased
and reduced as required.
2. Set up Storage Savings & Encryption options:
l Compression: Select a compression level that will be used to reduce the data size in the Backup
Repository. Note that higher compression levels consume considerably more CPU and may slow down VM
backup speed. The following options are available:
l Disabled: The data in the Backup Repository will not be compressed.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.
Note
This option cannot be configured after the Backup Repository is created.
l Deduplication: Leave the Enabled option to store only unique blocks of data in the Backup Repository in
order to save storage space.
Note
This option cannot be changed after the Backup Repository is created.
l Encryption: This option is available only if the Backup Repository is created locally on the machine on
which the Assigned Transporter is installed, and the machine is running a Linux OS. Select Enabled from
the drop-down list and specify an encryption password. (The password will be required for importing the
Backup Repository into a new instance of the product.) The product will encrypt the repository
destination (using ecryptfs for folders and cryptsetup (crypt-md) in LUKS mode for
devices/partitions) prior to creating the Backup Repository. 
Notes
l To avoid ecryptfs errors, make sure that there are no other folders and files except the
NakivoBackup folder in the repository location.
l Backup Repository encryption can significantly influence backup speed.
3. Set up Reliability & Maintenance options: 
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing in case the product detects symptoms of problems in the backup infrastructure such as
incorrect timestamps on metadata and data files. You can deselect this option and run self-healing
manually.
l Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing on
schedule. You can configure the schedule by clicking the schedule link when the option is selected. The
default schedule is set to run every day at 11 AM.
If Stop backup and recovery to run self-healing is selected, any jobs or recoveries which use this
repository will be stopped to run scheduled self-healing. Otherwise, scheduled self-healing will be skipped
in case there are running jobs or recoveries on this repository.

- 382 -
 l Run full data verification on schedule: If selected, the product will run full verification of all data available
in the Backup Repository on the specified schedule. The product will read each block of data and ensure
that it is identical to the data block that was read on the source VM during the backup. This way, the
product will verify each recovery points in the Backup Repository.
Stop backup and recovery to run backup verification:If selected, any running jobs which use this Backup
Repository will be stopped to run scheduled data verification. Otherwise, scheduled data verification will
be skipped in case there are running jobs on this Backup Repository.
Note
Backup verification is a time-consuming process. It also consumes the CPU of the Transporter assigned to
the Backup Repository. It is recommended that you schedule backup verification during non-working
hours.
l Reclaim unused space on schedule: If required, select this option to run the Backup Repository space
reclaim process on schedule. Space reclaim will compact the data. Unused space will be reclaimed. Keep in
mind that this process can be time-consuming.
If Stop backup and recovery to run space reclaim is selected, any running jobs which use this Backup
Repository will be stopped to run scheduled space reclaiming. Otherwise, scheduled space reclaiming will
be skipped in case there are running jobs on this Backup Repository.
Important
Do not reboot/disconnect the assigned Transporter and underlying storage device while space reclaim is
in progress to avoid Backup Repository corruption.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
4.  Schedule detaching of the Backup Repository:
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and metadata
in a consistent state and then stops the product's interaction with the Backup Repository (so that the
Backup Repository can be copied or moved). You can use this feature, for example, for the disk-to-disk-to-
tape (D2D2T) data protection approach, in which backups are stored on a disk for fast operational
recovery, and copied to a tape (while the repository is detached) for archiving and long-term storage.
l Delete and re-create the repository on attach: If this option is selected, all data in the Backup
Repository will be erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository will create full VM backups. You can use this option, for example, to create full
daily, weekly, or monthly VM backups and write them to tape or removable media .
Note
Resizing of Amazon EBS repository will not take place immediately, but after the following actions:

- 383 -
 l Next job run
l Repository refreshing
5. Click Finish to finish creating the Backup Repository. 

- 384 -
Backup Repository in Amazon S3
Select the Amazon S3 option if you want to create a Backup Repository in Amazon S3. Before creating a repository,
grant the required S3 access permissions to NAKIVO Backup & Replication. For details, refer to Required AWS IAM
Permissions for Amazon S3 and Wasabi and Permissions for the Amazon S3 Bucket.
Important
l You will be charged for Amazon S3 storage/traffic according to AWS tariffs.
l Forever incremental backups are not supported by this location.
To create a Backup Repository in an Amazon S3 bucket, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Amazon S3 and click Next to go to the next page of
the wizard.

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following:

- 385 -
 1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Select an AWS account from the Account drop-down list.
4. Select the AWS region connected to the bucket where you want to store your backups. 
5. Select the bucket where you want to store your backups from the Bucket drop-down list.
6. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

1. In the Storage Savings section, select a compression level for reducing the data size in the Backup Repository.
Note that higher compression levels consume considerably more CPU and may slow down the backup speed. The
following options are available:
l Disabled: No compression.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.
Note
This option cannot be configured after you create the Backup Repository.
2. Set up Reliability & Maintenance options: 
l Run full data verification on schedule: When selected, the product runs full verification of all data
available in the Backup Repository according to the specified schedule. The product reads each block of
data and ensures that it is identical to the data block that was read on the source machine during the
backup. This way, the product verifies each recovery point in the Backup Repository. 
When Stop backup and recovery to run full data verification is selected, any running jobs that use this
Backup Repository are stopped to run scheduled data verification. When this option is not selected,
scheduled data verification is skipped if there are running jobs on this Backup Repository.

- 386 -
 Note
Backup verification is a time-consuming process and utilizes the CPU resources of the Transporter
assigned to the Backup Repository. It is recommended that you schedule backup verification during non-
working hours.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
3. Schedule detaching of the Backup Repository: 
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository based on a schedule. Detaching a Backup Repository saves the Backup Repository data and
metadata in a consistent state and then stops the interaction of the product with the Backup Repository
(so that the Backup Repository can be copied or moved). You can use this feature, for example, for the
disk-to-disk-to-tape (D2D2T) data protection approach, in which backups are stored on a disk for fast
operational recovery and copied to a tape (while the repository is detached) for archiving and long-term
storage.
l Delete and re-create the repository on attach: When this option is selected, all the data in the
Backup Repository is erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository create full backups. You can use this option, for example, to create full daily,
weekly, or monthly VM backups and write them to tape or removable media.
4. Click Finish to complete Backup Repository creation.

- 387 -
Backup Repository in Wasabi Hot Cloud Storage
Select the Wasabi option if you want to create a Backup Repository in Wasabi. Before creating a repository, grant the
required Wasabi access permissions to NAKIVO Backup & Replication. For details, refer to Required AWS IAM
Permissions for Amazon S3 and Wasabi.
Important
l You may be charged for Wasabi storage/traffic. Refer to Cloud Storage Pricing for details.
l Forever incremental backups are not supported by this location.
To create a Backup Repository in a Wasabi bucket, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Wasabi and click Next to go to the next page of the
wizard.

Create Backup Repository: Name and Location

On the Name & Location page of the wizard, do the following:

- 388 -
 1. Enter the name of the Backup Repository in the Name box. 
2. Select the Transporter from the Assigned transporter drop-down list. 
3. Select a Wasabi account from the Account drop-down list.
4. Select the Wasabi region connected to the bucket where you want to store your backups. 
5. Select the bucket where you want to store your backups from the Bucket drop-down list.
6. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

1. In the Storage Savings section, select a compression level for reducing the data size in the Backup Repository.
Note that higher compression levels consume considerably more CPU and may slow down the backup speed. The
following options are available:
l Disabled: No compression.
l Fast: Lowest compression level.
l Medium: Medium compression level.
l Best: Maximum compression level.
Note
This option cannot be configured after you create the Backup Repository.
2. Set up Reliability & Maintenance options: 
l Run full data verification on schedule: When selected, the product runs full verification of all data
available in the Backup Repository according to the specified schedule. The product reads each block of
data and ensures that it is identical to the data block that was read on the source machine during the
backup. This way, the product verifies each recovery point in the Backup Repository. 
When Stop backup and recovery to run full data verification is selected, any running jobs that use this
Backup Repository are stopped to run scheduled data verification. When this option is not selected,
scheduled data verification is skipped if there are running jobs on this Backup Repository.

- 389 -
 Note
Backup verification is a time-consuming process and utilizes the CPU resources of the Transporter
assigned to the Backup Repository. It is recommended that you schedule backup verification during non-
working hours.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
3. Schedule detaching of the Backup Repository:
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository based on a schedule. Detaching a Backup Repository saves the Backup Repository data and
metadata in a consistent state and then stops the interaction of the product with the Backup Repository
(so that the Backup Repository can be copied or moved). 
l Delete and re-create the repository on attach: When this option is selected, all the data in the
Backup Repository is erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository create full backups. You can use this option, for example, to create full daily,
weekly, or monthly VM backups and write them to tape or removable media.
4. Click Finish to complete Backup Repository creation.

- 390 -
Backup Repository on Deduplication Appliance
NAKIVO Backup & Replication allows you to use advanced deduplication appliances for data protection.
Notes
l Before creating a Backup Repository on a Dell EMC DD, you need to install BoostFS Plugin and create a storage
unit on the data domain backup appliance. Refer to Integrating with EMC DD Boost for details.
l Before creating a Backup Repository on an NEC HYDRAstor, you need to configure the NEC HYDRAstor and the
machine on which NAKIVO Transporter is installed. Refer to Integrating with NEC HYDRAstor for details.
l To create a Backup Repository on other deduplication appliances, refer to “Backup Repository on NFS Share” on
page 375. 
 To create a repository on a deduplication appliance, proceed as described in the following sections: 
l Create Backup Repository: Type
l Create Backup Repository: Device
l Create Backup Repository: Name and Location
l Create Backup Repository: Options

Create Backup Repository: Type

On the Type page of the Create Backup Repository wizard, select Deduplication Appliance and click Next to go to the
next page of the wizard.
Note
Refer to “Storage Integration Requirements” on page 138 to see the list of supported advanced deduplication
appliances.

- 391 -
Create Backup Repository: Device

1. On the Device page, select one of the devices:

l Dell EMC Data Domain Boost
l HP StoreOnce Catalyst
l NEC HYDRAstor
2. Click Next to go to the next page of the wizard.

Create Backup Repository: Name and Location

On the Name & Location page, specify the following:

- 392 -
1. Name: Enter a name for the Backup Repository.
2. Assigned transporter: Choose a Transporter that will manage (that is, write data to and read data from) this
Backup Repository.
3. Depending on the deduplication appliance, provide the following information:
l Dell EMC Data Domain Boost
1. Name: Enter the name of your Backup Repository.
2. Assigned transporter: Select the assigned Transporter.
3. Path to the share: Enter the path to the share folder in the following format: <backup_
appliance>:/<storage_unit>. Refer to Creating a NAKIVO Backup & Replication Backup
Repository on EMC Data Domain Backup Appliance for details. 

l HPE StoreOnce Catalyst

1. Name: Enter the name of your Backup Repository.
2. Assigned transporter: Select the assigned Transporter.
3. Connection type: Select one of the connection types to be used to access the Backup Repository:
l IP address
l Fibre Channel
4. Depending on the connection type, do the following:
l Server name (if IP address connection type is selected): Enter the server name or IP address
of the HPE StoreOnce Catalyst.
l COFC identifier (if Fibre Channel connection type is selected): Enter the COFC identifier. You
can find your COFC identifier by going to Catalyst Settings>Fibre Channel in the StoreOnce
Management Console.
5. Catalyst store name: Enter the Catalyst store name.
6. Username: Provide the username to the Catalyst store.

- 393 -
 7. Password: Provide the password to the Catalyst store.

l NEC HYDRAstor
1. Name: Enter the name of your Backup Repository.
2. Assigned transporter: Select the assigned Transporter.
3. Path to the mount point: Enter the path to the mount point in the following
format: /opt/nakivo/repository/hsva. 

4. Click Next to go to the next page of the wizard.

Create Backup Repository: Options

On the Options page, do the following:

1. Set up Reliability & Maintenance options: 
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing if the product detects symptoms of problems in the backup infrastructure, such as incorrect
timestamps on metadata and data files. Optionally, you can deselect this option and run self-healing

- 394 -
 manually.
l Run repository self-healing on schedule: If required, select this checkbox to run repository self-healing
according to a schedule. You can configure the schedule by clicking the schedule link when the option is
selected. The default schedule is set to run every day at 11 AM.
When Stop backup and recovery to run self-healing is selected, any jobs or recoveries that use this
Backup Repository are stopped before running scheduled self-healing. When the option is not selected,
scheduled self-healing is skipped if there are running jobs or recoveries on this repository.
l Run full data verification on schedule: When selected, full verification of all data available in the Backup
Repository are performed as scheduled. The product reads each block of data and ensures that it is
identical to the data block that was read on the source VM during the backup. This way, the product
verifies each recovery point in the Backup Repository.
When Stop backup and recovery to run backup verification is selected, any running jobs that use this
Backup Repository are stopped before running scheduled data verification. If the option is not selected,
scheduled data verification is skipped if there are running jobs on this Backup Repository.
l Enforce explicit file system sync: When selected, explicit sync with the file system is enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on certain storage devices. By default, the option is disabled. 
2. Schedule detaching of the Backup Repository: 
l Detach this repository on schedule: Select this option if you want to detach and then attach the Backup
Repository according to a schedule. Detaching a Backup Repository saves the Backup Repository data and
metadata in a consistent state and then stops the product's interaction with the Backup Repository (so
that the Backup Repository can be copied or moved). You can use this feature, for example, for the disk-to-
disk-to-tape (D2D2T) data protection approach, in which backups are stored on a disk for fast operational
recovery and copied to a tape (while the repository is detached) for archiving and long-term storage.
l Delete and re-create the repository on attach: When this option is selected, all data in the Backup
Repository is erased prior to attaching it to the product. As a result, jobs that write to this Backup
Repository create full VM backups. You can use this option, for example, to create full daily, weekly,
or monthly backups, and write them to tape or removable media.
3. Click Finish to finish creating the local Backup Repository.

- 395 -
- 396 -
Managing Backup Repositories
Refer to the following topics:
l “Reclaiming Backup Repository Space” on page 402
l “Detaching Backup Repositories” on page 399
l “Attaching Backup Repositories” on page 398
l “Running Backup Repository Self-Healing” on page 408
l “Running Block-Level Backup Verification” on page 410
l “Editing Backup Repositories” on page 400
l “Removing and Deleting Backup Repositories” on page 406
l “Refreshing Backup Repositories” on page 404

- 397 -
Attaching Backup Repositories
If you have detached a Backup Repository, you can reattach it to the product by following the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and click a Backup Repository.
3. In the Backup Repository title, click Manage and then click Attach.

The Backup Repository is reattached to NAKIVO Backup & Replication. You can now back up to the attached
Backup Repository.

- 398 -
Detaching Backup Repositories
Detaching a Backup Repository saves the Backup Repository data and metadata in a consistent state and then stops
the product's interaction with the Backup Repository (such as read and write of data and metadata, and so on). You
may want to detach a Backup Repository in order to move it to a different location or to put the storage with the
Backup Repository on maintenance.
Important
Since the product stops working with detached backup repositories, jobs that back up VMs to a detached Backup
Repository will fail.
To detach a Backup Repository, follow the steps below:
1. Go to the main menu and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the Backup Repository title, click Manage and then click Detach.

Note
A Backup Repository cannot be detached if a job that backs up to this Backup Repository is running.
The Backup Repository is detached from the product. You can reattach the Backup Repository to NAKIVO Backup
& Replication when needed.

- 399 -
Editing Backup Repositories
To modify the settings of an existing Backup Repository, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the Backup Repository title, click Manage and then click Edit.

Note
A Backup Repository cannot be edited if there is a job that backs up to this Backup Repository is concurrently
running.
4. Update the fields as necessary.
5. Click Apply. Changes you have made are applied and the Backup Repository update starts.

- 400 -
How to Copy Backup Repository to Tape
With NAKIVO Backup & Replication, you are able to use a disk-to-disk-to-tape (D2D2T) data protection approach. This
approach allows to store backups on a disk for fast operational recovery and copy them to a tape for archival and long-
term storage. To achieve this, you need to take these steps:
1. Create a Backup Repository on a disk or use the Onboard Backup Repository created with the product
installation.
Note
The Onboard Backup Repository is forever incremental by default. If you want to store backups that include
incremental and full backup files, you should create a new backup repository and configure it as incremental with
full backups. This can be done on the Options page of the Create Backup Repository wizard.
2. Create and run VM backup jobs to the Backup Repository.
3. After all backup jobs are complete, do either of the following:
l Manually detach the Backup Repository to ensure its data is consistent.
l Enable scheduled repository detach/attach in repository settings.
4. Copy the entire folder with the Backup Repository to a tape.
Note
To automate the folder copy process, you can use post-job scripts or 3rd-party utilities.

- 401 -
Reclaiming Backup Repository Space
When a backup or recovery point is deleted in a Backup Repository, the space occupied by that backup or recovery
point is marked as “free” and can be reused by new data blocks on the next job runs. However, the actual size of the
Backup Repository may not change. The size of a Backup Repository can be reduced by rearranging the data blocks so
there are no “free” ones occupying storage space. The amount of space that can be freed up is displayed in parentheses
after the amount of used space. This is applicable if the repository type is Forever-incremental. Otherwise, if the
repository type is Incremental with full backups, space reclaiming is not required. It is enough to delete the backups or
recovery points to free up space and continue backing up to the repository.
For the incremental with full backup Backup Repository type, it is technically impossible to remove recovery points if
there is no full backup after them. Make a full backup before deleting older recovery points.
Reclaiming free space can take the same amount of time as copying the entire Backup Repository to the storage where
it is located (that is, if your repository size is 500 GB, reclaiming free space can take the same amount of time as copying
500GB of data to the storage where the Backup Repository is located).
Refer to the following topic to learn how to start and stop the reclaiming process:
l “Starting the Space Reclaiming Process” below
l “Stopping the Space Reclaiming Process” on the next page

Starting the Space Reclaiming Process

Important
Space reclaim requires at least 500 MB of free space on the repository storage in order to start.
To reclaim free space, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Reclaim unused space.

The space reclaiming process cannot be started if a job that backs up to this Backup Repository is concurrently
running.
4. In the dialog box that opens, leave the Interrupt space reclaim task if backup or recovery is started option

- 402 -
 selected to pause the space reclaiming process when a backup or recovery is started. The space reclaiming
process will be resumed once the backup or recovery job is completed. If you deselect the option, backup jobs
will fail and recovery jobs will not start until the space reclaim process is completed.
5. Click Start. The process of rearranging data blocks is started, and progress is displayed in the title of the Backup
Repository.

Stopping the Space Reclaiming Process

You can stop the space reclaim process at any time (for example to run a recovery job, move your Backup Repository to
a new location, or put your backup storage on maintenance).
Before the space reclaiming process begins, the Backup Repository is detached from the product to keep data in a
consistent state. Jobs that back up VMs to such a Backup Repository will fail while the space reclaiming process is in
progress.
To stop the space reclaim process, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Stop space reclaim.

- 403 -
Refreshing Backup Repositories
By default, NAKIVO Backup & Replication refreshes information about Backup Repositories every hour. During the
refreshing process, the product collects all required information about Backup Repositories (such as the amount of free
space, number of backups and recovery points, and so on).
Only one Backup Repository is refreshed at a time. Therefore, if you have more than one Backup Repository, all others
will remain in a queue.
l Refreshing All Backup Repositories
l Refreshing a Single Backup Repository

Refreshing All Backup Repositories

To refresh all backup repositories, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab.
3. Click Refresh All.

The Backup Repositories refresh starts.

Refreshing a Single Backup Repository

To update a single Backup Repository, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab.

- 404 -
 3. Click the Backup Repository that you wish to update.
4. In the title of the Backup Repository, click Refresh.

The Backup Repository refresh starts.

- 405 -
Removing and Deleting Backup Repositories
In NAKIVO Backup & Replication, you can either permanently delete a Backup Repository and all of its data or remove
only the Backup Repository from the product while maintaining all of its data. After removing a Backup Repository you
will be able to import it into the same or a new instance of the product.
Important
You will not be able to remove a Backup Repository if there is a job that backs up to this Backup Repository. To remove
such a Backup Repository, you first need to delete (or edit) the corresponding jobs so no items are backed up to the
Backup Repository that is being removed.
To permanently delete or remove a Backup Repository from the product, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab.
3. Click a Backup Repository.
4. In the Backup Repository title, click Manage and then click Remove.

5. Do the following when the confirmation message appears:

l To remove the Backup Repository from NAKIVO Backup & Replication and keep the Backup Repository on
a disk, click the Remove Repository and Keep Backups button.
Note
You can import the removed Backup Repository back to the same or to new product installation.
l To permanently delete the Backup Repository and all its data, click the Remove Repository and Delete
Backups button.

- 406 -
Important
This operation will permanently delete the Backup Repository and all VM backups.

- 407 -
Running Backup Repository Self-Healing
The self-healing process verifies Backup Repository integrity and automatically repairs errors wherever possible.
Namely, the process performs the following tasks:
l Verifies that the data blocks of each recovery point are present in the Backup Repository.
l Cleans up “in progress” blocks of data from failed/crashed backup job runs that did not have a proper cleanup.
l Verifies and repairs Backup Repository metadata so that it correctly describes available data.
l Restores the consistent state of the Backup Repository to enable subsequent backup jobs.
Before the self-healing process begins, the Backup Repository is detached from the product to keep data in a consistent
state. Jobs that back up VMs to such Backup Repository will fail while the self-healing process is in progress.
Refer to the following topics to learn more:
l “Starting the Self-Healing Process” below
l “Stopping the Self-Healing Process” on the next page

Starting the Self-Healing Process

To run the Backup Repository self-healing, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Run repository self-healing.

- 408 -
 4. In the dialog box that appears, click Start.
The self-healing process is started.

Stopping the Self-Healing Process

You can stop the self-healing process at any time (for example, to run a recovery job, move your Backup Repository to a
new location, or put your backup storage on maintenance).
To stop the self-healing process, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Stop repository self-healing.

The self-healing process is stopped.

- 409 -
Running Block-Level Backup Verification
Block-level backup verification reads each block of data in a Backup Repository, makes a hash of each data block, and
then compares the newly created hashes to the originals that were created during the backup process. If the hashes
match, this means that the data blocks in the Backup Repository are identical to the data blocks that were read on the
source machines. This way NAKIVO Backup & Replication verifies that backups are good and recoverable.
Refer to the following topics to learn more:
l “Verifying Backups” below
l “Verifying all VM Backups” below
l “Verifying a Single Backup” on the next page
l “Stopping the Backup Verification Process” on page 412
l “Stopping Backup Verification for a Backup Repository” on page 412
l “Stopping Backup Verification for a Single Backup” on page 412

Verifying Backups

Important
Before backup verification begins, the Backup Repository is detached from the product to keep data in a consistent
state. Backup jobs that write data to such a Backup Repository will fail while the backup verification process is in
progress.

Verifying all VM Backups

To verify all VM backups in a repository, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Verify all backups.
The backup verification process cannot be started if a job that backs up to this Backup Repository is running.
4. In the dialog box that opens, click Start. The backup verification process is started.

- 410 -
Verifying a Single Backup

To verify a single VM backup in a repository, follow the steps below:

1. In the main menu of NAKIVO Backup & Replication, click Settings.
2. Go to the Repositories tab and click a Backup Repository to expand it. 
3. In the title of a VM backup, click Verify.

- 411 -
Stopping the Backup Verification Process

You can stop the backup verification process at any time (for example, to run a recovery job, move your Backup
Repository to a new location, or put your backup storage on maintenance).

Stopping Backup Verification for a Backup Repository

To stop the backup verification process, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and choose a Backup Repository.
3. In the title of the Backup Repository, click Manage and then click Stop backup verification.

The backup verification process is stopped.

Stopping Backup Verification for a Single Backup

To stop the backup verification process, follow the steps below:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and click a Backup Repository to expand it. 

- 412 -
 3. In the title of a VM backup, click Stop verifying.

For near-instant backup verification, refer to the “VM Verification” on page 43 feature.

- 413 -
Adding Existing Backup Repositories
NAKIVO Backup & Replication provides you with the ability to add an existing backup repository to a new copy of the
product. 
Important
During the import process, NAKIVO Backup & Replication searches for the "NakivoBackup" folder in the specified
location, so if your Backup Repository is located in E:\backup\NakivoBackup, you need to specify the following
path: E:\backup
To import an existing Backup Repository, do the following:
1. Go to the main menu and click Settings.
2. Go to the Repositories tab and click Add Backup Repository.
3. Click Add existing backup repository in the dialog that opens.

4. The Add Existing Backup Repository wizard opens. On the Type page of the wizard, select one of the following
Backup Repository types: 
l Local Folder
l CIFS Share
l NFS Share
l Amazon EC2
l Amazon S3

- 414 -
 l Wasabi
l Deduplication Appliance
5. On the Name & Location page of the wizard, fill out all the necessary fields the way it's described in the article for
the corresponding Backup Repository type.
6. On the Options page of the wizard, depending on the repository type, the following options can be available for
configuration:
l Encryption password: If the Backup Repository is encrypted, type in the encryption password.
l Enable automatic repository self-healing: Leave this option selected to automatically trigger repository
self-healing in case the product detects symptoms of problems in the backup infrastructure (such as
incorrect timestamps on metadata and data files). You can deselect this option and run self-healing
manually.
l Run repository self-healing on schedule: If required, select this checkbox to additionally run
repository self-healing on schedule. You can configure the schedule by clicking the schedule link when the
option is selected. The default schedule is set to run every day at 11 AM.
l Run full data verification on schedule: If selected, the product will run full verification of all data available
in the Backup Repository on the specified schedule. The product will read each block of data and ensure
that it is identical to the data block that was read on the source VM during the backup process. This way
the product will verify each recovery points in the Backup Repository.
Backup verification is a time-consuming process and consumes CPU of the Transporter assigned to the
Backup Repository. It is recommended to schedule backup verification during non-working hours.
l Reclaim unused space on schedule: If required, select this option to run the Backup Repository space
reclaim process on schedule. You can configure the schedule by clicking the schedule link when the option
is selected. The default schedule is set to run every Saturday at 12 PM.
l Enforce explicit file system sync: If selected, explicit sync with the file system will be enforced during all
backup operations to this repository. This setting is considered more reliable but may lead to lower
performance on some storage devices.  
l Detach this repository on schedule: Select this option if you want to detach and then reattach the Backup
Repository on a schedule. Detaching a Backup Repository saves the Backup Repository data and metadata
in a consistent state and stops the product interaction with the Backup Repository (so that the Backup
Repository can be copied or moved). You can use this feature, for example, for the disk-to-disk-to-tape
(D2D2T) data protection approach, in which backups are stored on a disk for fast operational recovery, and
copied to a tape (while the repository is detached) for archiving and long-term storage.
l Delete and re-create the repository on attach: If this option is selected, all data in the Backup
Repository will be erased prior to attaching it to the product. As a result, jobs that write to this
Backup Repository will create full VM backups. You can use this option, for example, to create full
daily, weekly, or monthly VM backups and write them to tape or removable media.
7. Click Finish. The Backup Repository is imported.

- 415 -
Viewing Backup Repository Details
To view Backup Repository details, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab.
3. Click a Backup Repository.
4. The following data is displayed:

l Free: The amount of free space currently available for the Backup Repository.
l Used: The amount of space that the Backup Repository occupies on a disk. The amount of space that can be
reclaimed is displayed in parentheses.
l Deduplication: The status of deduplication in the current Backup Repository.
l Compression: The compression level specified for the current Backup Repository.
l Encryption: The status of encryption in the current Backup Repository.
l Space savings: The estimated percentage and amount of space saved by compression and deduplication. For
example, if 200 GB of data were backed up and the size of the backup was reduced to 50 GB, the ratio is calculated
as 75%.
l Automatic self-healing: The current state of the automatic self-healing option for the Backup Repository.
l Scheduled self-healing: The current state of the scheduled self-healing option for the Backup Repository.
l Enforce explicit file system sync: The current state of the enforce explicit file system sync option for the Backup
Repository.
l Scheduled data verification: The current state of the scheduled data verification option for the Backup Repos-
itory.
l Scheduled space reclaiming: The current state of the scheduled space reclaiming option for the Backup Repos-
itory.
l Scheduled detach: The current state of the scheduled detach option for the Backup Repository.

- 416 -
l Data storage type: The type of Backup Repository, which can be one of the following:
l Forever incremental: After the initial full backup, all subsequent backups will transfer and store only

changed data (increments) to the backup repository.

l Incremental with full backups: After the initial full backup, backup jobs will store changed data (incre-

ments) in separate files and will periodically create full backups as specified in the job settings. Backup dedu-
plication is not available when this option is selected.
l Type: The location of the Backup Repository, which can be one of the following:
l Local folder on the assigned Transporter

l Remote CIFS Share

l Remote NFS Share

l Amazon EC2

l SaaS

l Amazon S3

l Wasabi

l Deduplication Appliance

l Path to the folder: The path to the Backup Repository folder.

l Assigned transporter: The Transporter that manages the Backup Repository (i.e. reads data from and writes data
to the Backup Repository).
l Backups: List of available backups in the Backup Repository.

- 417 -
Tape
To start working with tape devices in NAKIVO Backup & Replication, you first need to add and configure them on
the Tape page of the Settings dashboard. 

The default view of the Tape page is set to Devices, and once you add your tape devices, you will be able to view and
manage them here. Also, by selecting different views from the View drop-down list you will be able to work with tapes
and backups.
On the Tape page, you can perform the following operations:
l “Adding Robotic Tape Libraries or VTLs” on page 419
l “Adding Standalone Tape Drives” on page 424
l “Managing Tape Devices” on page 427
l “Managing Tape Cartridges” on page 428
l “Managing Backups” on page 437
l “Managing Locations” on page 440
l “Managing Media Pools” on page 442

- 418 -
Adding Robotic Tape Libraries or VTLs
Important
Please observe the following prerequisites before adding Robotic Tape Libraries or VTLs to Inventory:
l Vendor drivers should be installed on tape devices prior to adding them to NAKIVO Backup & Replication
inventory.
l To be able to work with AWS VTL, you need to deploy a Transporter and manually mount VTL targets.
The process of adding a Robotic tape library or VTL to NAKIVO Backup & Replication includes the following steps:
l Launching Wizard
l Selecting Transporter
l Selecting Changers
l Selecting Drives
l Selecting Options
l Managing Added Tape Library

Launching Wizard
To add a Robotic tape library or VTL to the system:
Note
Before adding a Robotic tape library or VTL, make sure that the on-premises VM or Amazon EC2 instance meets the
necessary feature requirements.
1. Go to Settings and click the Tape tab.
2.  Select Devices from the View drop-down list.
3. Click Add New Device and select Robotic tape library or VTL.

The Add New Robotic Tape Library or Virtual Tape Library wizard opens. Follow the steps below to add a new
device.

- 419 -
Selecting Transporter
Important
Before adding a new tape device to NAKIVO Backup & Replication, you need to deploy or add an existing “Transporter”
on page 130 on a machine that is physically connected to the tape device.
For virtual tape libraries, the transporter should run in a separate VM on the same host or in a separate cloud instance
in the same network.
Refer to “Deploying Transporter as VMware Appliance” on page 355 and “Adding Installed Transporters” on page 347
for more information on Transporter deployment.
On the Select Transporter step, you need to specify a Transporter assigned to the device or VTL you want to add. This
Transporter acts as a network appliance that manages traffic between the tape device and NAKIVO Backup &
Replication. 
1. From the Assigned Transporter drop-down list, select the relevant installed Transporter.

2. Click Next.

Selecting Changers
The Select Changers page displays the list of media changers on the selected Transporter. 
Note
If no media changers were found on the specified transporter, make sure the devices are connected, powered on, and
the appropriate drivers are installed.
Select one media charger from the list. Media changers already being used in another discovered tape library are
disabled.

- 420 -
The following information is displayed for each media changer to facilitate the selection:
l Device name: Indicates device's vendor and model, separated by space
l Address: Indicates the hardware address including the bus and node numbers
l Path: Indicates location in the operating system
l Serial number: Indicates the serial number of the device

Selecting Drives
On the Select Drives page, you can select tape drives from the tape library and specify the actual drive number for each
drive. Drives already used in another discovered tape device are disabled and cannot be selected. The table provides
the following information:
l Device name: Indicates the device's vendor and model.
l Address: Displays the hardware address including the bus and node numbers.
l Path: Shows the location in the operating system.
l Serial number: Shows the serial number of the drive.
l Drive Number: Indicates the drive number and allows changing it.  Changing the drive number may be required
to address situations, where iSCSI targets are assigned incorrectly to the mounted drives.
Note
If more than one drive is selected, such drives should use the same host\buses.

Click Next to proceed to the next page.

- 421 -
Selecting Options
The last step of adding a tape library is selecting its options.

1. Specify the following parameters:

l Name: Enter the name for the tape library
l Compression: Select a compression level of the tape device:
l Hardware-based (default)
l Software-based (fast)
l Software-based (medium)
l Software-based (best)
Note, that combining hardware compression with software compression is not recommended. 
l Block size: Select the block size of the tape device:
l 32 KB
l 64 KB
l 128 KB
l 256 KB (default)
l 512 KB
l 1 MB
The system does not automatically detect the block size; make sure to use the correct block size when
importing backups.
l Device location: Select the location of the device and all tapes inserted into this device. The automatically created
My office location is selected by default. To create another location, click Add Location. For more information on
locations management, refer to “Managing Locations” on page 440
l Default media pool: Select a default media pool for all new tapes inserted into this device. To create another
media pool, click Add Media Pool. For more information on media pools management, refer to “Managing Media
Pools” on page 442
l Default offline location: Select a default location for all tapes ejected from this device.
2. Click Save to start adding the tape library to NAKIVO Backup & Replication. After successful addition, the tape library
will become available in the Devices view of the Tape tab.

- 422 -
Managing Added Tape Library
Clicking the name of the tape library opens its Parameters page. In addition to giving the details on the selected tape
library, the Parameters page provides the following options:
l Refresh: Allows for refreshing the device by initiating the process of updating information regarding the content
of the tape device. Refreshing involves checking the tapes' barcodes and may include moving tape cartridges
within the device
l Manage: Allows for performing the following actions with the tape library:
l Edit: Selecting this option opens the same wizard as described in previous sections, but with all fields
already predefined. All fields, apart from Compression and Block size, can be changed
l Detach/Attach: Allows performing manual tape library attach/detach. Tape cartridges contained in a
detached tape device become offline
l Remove: Removes the device from NAKIVO Backup & Replication. This option is unavailable if the device is
currently in use by a job or other process
l View all: Clicking the view all link opens the Tapes screen where you can view and manage tape cartridges in the
device.

- 423 -
Adding Standalone Tape Drives
Important
Vendor drivers should be installed on tape devices prior to adding them to NAKIVO Backup & Replication inventory.
The process of adding a standalone tape drive to NAKIVO Backup & Replication includes the following steps:
l Launching Wizard
l Selecting Transporter
l Selecting Options
l Managing Added Tape Drives

Launching Wizard
To add a standalone tape drive to the system:
1. Go to Settings and click the Tape tab.
2. Select Devices from the View drop-down list
3. Click Add New Device and select Standalone tape drive.

The Add New Standalone Tape Drive wizard opens. Follow the steps below to add a new tape drive.

Selecting Transporter
Important
Before adding a new tape drive to NAKIVO Backup & Replication, you need to deploy or add an existing Transporter on
a machine that is physically connected to the tape drive.
Refer to “Deploying Transporter as VMware Appliance” on page 355 and “Adding Installed Transporters” on page 347
for more information on Transporter deployment.
During the Select Transporter step, you need to specify a Transporter assigned to the drive that you would like to add.
This Transporter acts as a network appliance that manages traffic between the tape drive and NAKIVO Backup &
Replication. 

- 424 -
 1. From the Assigned Transporter drop-down list, select the relevant installed Transporter.

2. Click Next.

Selecting Options
The last step of adding a tape drive is selecting its options.

1. Specify the following parameters:

l Name: Enter the name of the tape library
l Drive: Select one of the standalone tape drives on the assigned transporter
l Compression: Select a compression level of the tape device:
l Hardware-based (default)
l Software-based (fast)
l Software-based (medium)
l Software-based (best)
Note, that combining hardware compression with software compression is not recommended
l Block size: Select the block size of the tape device:
l 32 KB
l 64 KB
l 128 KB

- 425 -
 l 256 KB (default)
l 512 KB
l 1 MB
The system does not automatically detect the block size; make sure to use the correct block size when
importing backups.
l Device location: Select the location of the device and all tapes inserted into this device. The automatically created
My office location is selected by default. To create another location, click Add Location. For more information on
locations management, refer to “Managing Locations” on page 440
l Default media pool: Select a default media pool for all new tapes inserted into this device. Optionally, you can
select No default media pool if you want to skip this step. To create another media pool, click Add Media Pool.
For more information on media pools management, refer to “Managing Media Pools” on page 442
l Default offline location: Select a default location for all tapes ejected from this device. Optionally, you can select
No default offline location if you want to skip this step.
2. Click Save to start adding the tape drive to NAKIVO Backup & Replication. After successful addition, the tape drive will
become available in the Devices view of the Tape tab.

Managing Added Tape Drives

Clicking the name of the tape drive opens its Parameters page. Apart from giving details on the selected tape drive, the
Parameters tab provides the following functionality:
l Refresh: Allows for refreshing the device by initiating the process of updating information regarding the content
of the tape device.
l Manage: Allows for performing the following actions with the tape drive:
l Edit: Selecting this option opens the same wizard as described in previous sections, but with all fields
already predefined. All fields, apart from Compression and Block size, can be changed.
l Detach/Attach: Allows for performing manual tape library attach/detach. Tape cartridges contained in a
detached tape device become offline.
l Remove: Removes the device from NAKIVO Backup & Replication. This option is unavailable in case the
device is currently in use by a job or other process.
l View tapes: Clicking the view all link opens the Tapes screen where you can view and manage tape cartridges in
the device.

- 426 -
Managing Tape Devices
Once the tape devices are added to the system, you can view and manage them on the Devices view of the Tape page.
Hovering the mouse cursor over the device name opens the management controls:
l Manage: opens the following options:
l Edit: Opens the Add New Robotic Tape Library or Virtual Tape Library or Add New Standalone Tape Drive
wizard, depending on the type of the device, where you can change the device's properties. Detached
devices are greyed out in the interface and cannot be interacted with
l Detach: Detaching a tape device saves the device's data and metadata in a consistent state and then stops
the product's interaction with the device (such as read and write of data and metadata, and so on). You
may want to detach a tape device to move it to a different location or to put it on maintenance.
l Remove: Removes the tape device from the inventory. The device may be then added again, for example, if
you need to change the block size or compression type of the device.
l Refresh: Refresh action shall initiate the process of updating information regarding content of the tape device.

Clicking the name of the tape device opens the device's details window where you can manage it and view the
device's detailed information.

- 427 -
Managing Tape Cartridges
The Tapes view allows you to view and manage all tape cartridges registered in the system. This section covers the
following topics:
l Viewing Tapes
l Searching for Tape Cartridges
l Filtering Tape Cartridges
l Tape Cartridge Management Page
l Action Buttons

l Details Pane

l Options Pane

l Tape Cartridge Contents Table

l Recovery Page

l Bulk Tape Cartridge Management

Viewing Tapes
To navigate to the Tapes view, go to Settings > Tapes and select Tapes from the View drop-down list.
The Tapes view provides you with the following information about the tape cartridges in the table:
l Name: Displays the tape cartridge name. Clicking the name opens the tape cartridge management page. For more
information, see Tape Cartridge Management Page.
l Label: Displays the label assigned to the tape cartridge ("none" for tape cartridges without labels)
l Status: Displays the current status of the tape cartridge - Scanning / Online / Reading / Writing / Erasing /
Warning / Error / Offline.
l Device: Displays the name of the tape device that contains the tape cartridge.
l Slot#/Drive#: Displays the slot/drive number in which the tape cartridge currently is.
l Last Written: Displays the date of the last recording on the tape cartridge.
l Overwritable: Displays the date when all recovery points on this tape cartridge will expire.
l Media Pool: Displays the name of the media pool that the tape cartridge belongs to.
l Location: Displays the name of the device location that the tape cartridge belongs to.
l Contents: Indicates the contents of the tape cartridge: number of backups present on the tape cartridge, the tape
cartridge is empty, unidentified or contains the 3rd party data.
l Type: Displays the type of the tape cartridge:
l Read/Write Tape
l Write Protected Tape
l Cleaning Tape
The columns availability within the table can be managed by clicking the small arrow in any column header and
selecting/clearing the checkboxes next to the column name.

- 428 -
Searching for Tape Cartridges
You can search for particular tape cartridge(s) by entering its name (or part of it) into the Search box. The table will
dynamically change to display the search results matching your query.

Clicking the Clear button in the search field will clear the query and the table will display all tape cartridges.

Filtering Tape Cartridges

The Tapes view also provides sophisticated filtering options that can be applied to search for particular tape cartridges.
To access filtering options, click the Filter link in the Search box. In the dialog that opens you can select one or several
filtering criteria that will be applied with the AND statement.

- 429 -
You can apply the following filtering criteria:
l Backup name: Tape cartridges containing the backups with the provided name will be displayed.
l Status: Tape cartridges in one of the following statuses will be displayed:
l Offline
l Online
l Scanning
l Erasing
l Reading
l Writing
l Warning
l Moving
l Error
l Device: Only the tape cartridges from the specified type device will be displayed.
l Media Pool: Only the tape cartridges from the specified media pool will be displayed.
l Location: Only the tape cartridges from the specified device location will be displayed.
l Last Written: Displays the tape cartridges that have the data written to it on/before/after a specified date.
l Overwritable: Displays the date when the tape cartridge can be overwritten (calculated using the age and
retention of all recovery points on this tape cartridge) .
l In Slot: Displays the tape cartridges in a specified slot or range of slots.
l In Drive: Displays the tape cartridges in a specified tape drive or range of tape drives.
l Type: Displays the tape cartridges according to their type:
l Read/Write Tape
l Write Protected Tape
l Cleaning Tape
Note
The Search and Filter features can only be applied separately; that is, you cannot simultaneously enter a character's
string and select filtering options.

- 430 -
Tape Cartridge Management Page
Clicking on the tape cartridge name opens the tape cartridge management page where you can apply certain actions to
the tape cartridge or get extensive information about it.
The tape cartridge management page consists of the following functional blocks:
l Action Buttons
l Details Pane
l Options Pane
l Tape Cartridge Contents Table

Action Buttons

The action buttons allow you to perform particular actions with the tape cartridge. Depending on the state of the tape
cartridge, its type, status, etc., the button’s availability may vary; the button can be disabled in case a certain action
cannot be applied to the tape cartridge. Hovering over the disabled button opens a tooltip describing the reason for
action unavailability.
Some of the actions can be applied to several tapes at once. For more information, refer to “Bulk Tape Cartridge
Management” on page 435.
The following actions can be applied to the tape cartridge:
l Scanning: Scanning of the tape cartridge implies checking its contents. The system recognizes the contents to be:
l Known NAKIVO Backup & Replication backups: Such content requires no scanning. The backups contained
on this tape cartridge are displayed in the Tape Cartridge Contents Table and can be used for VM restoring.
l Unknown NAKIVO Backup & Replication backups: The system recognizes the contents as created by
NAKIVO Backup & Replication (i.e. on another product instance) but cannot be used for VM restoring until
scanned.

- 431 -
 l Empty: The tape cartridge contains no data and is ready to be used for backing up.
l Third Party Data: The tape cartridge contains some third-party data that cannot be recognized by NAKIVO
Backup & Replication. Such tape cartridges cannot be used unless their contents are erased.
l Incomplete Backups: The tape cartridge contains incomplete backup(s), the result of an inappropriately
finished backup job (e.g. a backup copy job was stopped by the user and the backup copy was not
completed). Incomplete backups cannot be used for recovery.
l Unidentified: The contents of a newly introduced tape cartridge is unknown to the system and must be
scanned first.
When you insert new tape cartridges into the tape device, and these tape cartridges contain backups created using
another instance of NAKIVO Backup & Replication, the application opens the Scan new tape cartridges? message box,
asking you to scan all tape cartridges. Clicking the Scan all link will initiate the scanning action for all newly discovered
tape cartridges.
l Editing: Clicking the Edit button opens the Edit Tape dialog where you can:
l Create or change a label for the tape for easier tape identifying.
l Assign the tape to a pre-created media pool.
l Allocate the tape to a pre-created location.
The newly added details are displayed in the Options pane.
l Moving: This action allows you to move the tape cartridge to an available drive slot or tape drive. Occupied drive
slots or tape drives are disabled in the menu.
l Protecting: Applying this action to the tape cartridge makes it protected from data overwriting. This action is only
available on tape cartridges that contain recovery points. Recovery from protected tape cartridges is available.
Protected tape cartridges can be reverted by clicking the Unprotect button. Clicking the Protect or
Unprotect button requires confirmation.
l Marking as free: Marking the tape cartridge as free makes it eligible for writing backups to it. Marking the tape
cartridge as free does not erase the data right away: the next time, the product needs a tape cartridge for writing
data, it can take this tape cartridge and do a quick-erase before writing new data to it. The button is not available
in case the tape cartridge is protected or empty. Marking the tape cartridge as free requires confirmation. The
confirmation box displays detailed information about the data that is about to be deleted. This action cannot be
undone.
l Marking as cleaning: Specialized tape cartridges designed for tape drive cleaning need to be marked as cleaning
tapes. For the tape cartridges that have been marked as cleaning tapes, though still need to be reverted to
normal tapes, the Mark as cleaning button is substituted with the Mark as data button.
Important
Currently, the cleaning tapes inserted into the device are not automatically recognized by the system as cleaning.
Instead, the system identifies the tapes to contain a 3rd party data. It is a user's responsibility to mark the tape
as cleaning once the tape is inserted into the device and discovered. Otherwise, the cartridge will be performing
the drive's cleaning automatically every time the library is refreshed

- 432 -
 l Retiring: The tape cartridges marked as retired will not be used for new backups. Recovery from retired tape
cartridges is still available. The action is not available for tape cartridges marked as free or do not contain recovery
points. This action requires your confirmation.
l Erasing: The contents of the tape can be erased using:
l Quick erase: The data is marked as deleted without actual data deletion. Such data can still be recovered if
necessary.
l Full erase: Deletes the data from the tape forever.
Keep in mind that both methods can be very time-consuming.
Clicking the Erase button opens the Erase selected tape? dialog providing detailed information about the
data that is about to be deleted and allows choosing the erase method 
l Removing: Clicking this button will physically remove the tape cartridge from the tape device. The button is only
available for the offline tape cartridges. The action requires your confirmation.

Details Pane

The Details pane provides full information about the tape:

l Status: Displays the status of the tape cartridge and the current tape device name and drive slot #/tape drive #.
The tape cartridge can be in one of the following
statuses: Scanning / Online / Reading / Writing / Erasing / Warning/ Moving / Error / Offline
l Name: Displays the name of the tape cartridge. Can be modified by clicking the Edit button.
l Barcode: Displays the tape cartridge barcode if available.
l Last written: Displays the date of the last write operation.
l Overwritable: Displays the date when all recovery points on this tape cartridge will be expired.
l Type: Displays the type of the tape cartridge: Read/Write Tape / WORM Tape / Write Protected Tape / Cleaning
Tape.

Options Pane

In the Options pane, you can view the tape cartridge label, media pool and device location where the tape cartridge
belongs. Changing this information is available via the Edit button.

Tape Cartridge Contents Table

The Tape Contents table provides information about the backups residing on the tape cartridge and allows for
recovering VMs from backups right from the table. In case the tape cartridge contains no backups, the table displays
generic information about the tape cartridge contents:
l "This tape contains third party data."
l "This tape cannot be identified due to a lack of barcode. Please scan the tape in order to discover its content."
l "This tape is empty."
l "This tape contains backups.": The tape contains backups created by NAKIVO Backup & Replication but has not

- 433 -
 been scanned yet.
l  A grid of tape backups in case the tape contains backups.
If the tape cartridge contains backups and has been scanned already, the Tape Contents table displays the backups in
the grid and provides the following information:
l Name: Displays the name of the backup. Clicking on the name of the backup opens the Recovery page.
l Type: Displays the type of a backup: VMware VM, Hyper-V VM or EC2 instance.
l Tapes: Shows the number of tape cartridges this backup is stored on.
l Points: Displays the number of recovery points in the backup.
l Last point: Displays the date of the most recent recovery point in the backup.
l Location: Displays the location the tape cartridge is assigned to.
The Tape Contents table can be modified to display the column you need by clicking on the arrow icon in the table
header, and selecting the required columns.
Clicking the column's header sorts the contents of the column.

Recovery Page

Clicking on a backup name in the Tape Cartridge Contents table opens the Recovery page where you can view the
backup information as well as see all recovery points available for this backup. From here, you can also initiate the
recovery process.

The Backup Details section provides the following information about the backup:
l Name: Shows the name of the backup.
l Type: Shows the type of backup: VMware, Hyper-V VM, EC2 instance or physical machine.
l Tapes: Shows the number of tape cartridges this backup is stored on.
l Recovery points: Shows the number of recovery points within the backup.
l First recovery point: Shows the date of the latest recovery point of the backup.

- 434 -
 l Last recovery point: Shows the date of the most recent recovery point of the backup.
l Location: Shows the location the backup is assigned to.
The Recovery points table lists all the recovery points available for the current backup and provides the following
information:
l Date: Indicates the date the recovery point was created. Clicking on the recovery point, you can start the
Recovery Wizard with the current backup and recovery point selected.
l Type: Indicates the type of backup: Full or Incremental.
l Tape: Indicates the name of the tape cartridge the backup is stored on.
l Expiration date: Indicates the date when the recovery point expires.
Clicking either the Recover button or the name of the recovery point opens the Recovery Job Wizard. For more
information about recovering from tape cartridge, refer to “Recovery From Tape” on page 630 .

Bulk Tape Cartridge Management

Certain actions can be applied to several tape cartridges simultaneously. While being on the Tapes view, select the
checkbox next to the tape cartridges you need to apply an action to, and click Apply action. In the dialog that opens,
select an action to apply. Note that the availability of actions depends on various factors, thus not all actions may be
available. For actions description, refer to Action Buttons.

- 435 -
The Create report action is unique to the bulk tape cartridge management and is used to generate reports about
selected tape cartridges. The report is created as a PDF file and is stored locally on your computer.

- 436 -
Managing Backups
From the Tape tab, you can also manage all backups stored on tape cartridges by selecting the Backups option from
the View drop-down list.

From the Backups view, you can search for backups, recover from backups, and view backups' details.
l Searching for Backups
l Filtering Backups
l Backups Table
l Recovering from Backups

Searching for Backups

You can search for particular backup(s) by entering its name (or part of it) into the Search box. The table will dynamically
change to display the search results matching your query.
Clicking the Clear button in the search box will clear the query and the table will display all backups.

Filtering Backups
The Backups view also provides sophisticated filtering options that can be applied to search for particular backups. To
access filtering options, click the Filter link in the Search box. In the dialog that opens, you can select one or several
filtering criteria that will be applied with the AND statement.

- 437 -
You can apply the following filtering criteria:
l Backup name: The backups with the name provided will be displayed. Part of the name can be entered.
l Status: Specify the type of backups to be displayed:
l VMware VM
l Hyper-V VM
l Amazon EC2 instance
l Any
l Location: Only the backups from the tape cartridges of the specified device location will be displayed.
l Recovery points: Only the backups with less or more recovery points will be displayed.
l Last recovery point: Only the backups with the last recovery point created on/newer/later than the date specified
will be displayed.
Note
The Search and Filter features can only be applied separately; that is, you cannot simultaneously enter a search string
and select filtering options.

Backups Table
The Backups table provides the detailed information about each backup:
l Name: Displays the name of the backup. Clicking on the name opens the Recovery screen.
l Type: Displays the type of backup.
l Tapes: Displays how many tape cartridges the backup occupies.
l Points: Displays how many recovery points the backup has.
l Last point: Displays the date of the last recovery point on the backup.
l Location: Displays the location the tape(s) with the backup belongs to.

Recovering from Backups

You can initiate the recovery process from the Backups view by selecting the checkboxes next to the backups' names
and clicking the Recover button.

- 438 -
The New Recovery Job Wizard opens with the specified backups and their latest recovery points selected.

- 439 -
Managing Locations
Device location is a logical container representing a geographical place where the tape devices are located. Larger
companies can have their tape devices in different locations, e.g. the UK, USA, Australia, etc. By default, the system
automatically creates the My Office device location, but you can create more device locations if necessary. Refer to
these sections for details:
l Adding Device Locations
l Managing Device Locations

Adding Device Locations

To add a Location:
1. Go to Settings > Tape.
2. With Devices view selected, click Manage and select Locations. The Location Management dialog opens.

3. Click Add New Location.

4. In the Add New Location dialog box, specify a name for the device location and provide its description
(optionally).

5. Click Save. The new device location is added to the list.

- 440 -
Managing Device Locations
From the Location Management screen page,  you can also edit or delete Locations by using the corresponding buttons
or search for the location by entering a location name (or a part of its name) into the Search box.

- 441 -
Managing Media Pools
Media pools are logical containers created in NAKIVO Backup & Replication to organize and manage tape cartridges. No
Media Pools are created by default, but you can create new ones if necessary. for details, refer to the following sections:
l Adding Media Pools
l Managing Media Pools

Adding Media Pools

To create a Media Pool:
1. Go to Settings > Tape.
2. With the Devices view selected, click Manage and select Media Pools. The Media Pool Management dialog box
opens.

3. Click Create Media Pool.

4. In the Create Media Pool dialog box, specify the name for the Media Pool and provide its description (optionally).
5. From the Move Offline Tapes To drop-down list, select a device location to determine which location is
automatically set for all offline tapes from this media pool. If the tape cartridge goes online again, it will return to
the initial device location.
6. Select the Automatically add free tapes to this pool when required checkbox to automatically add one of the
empty available tape cartridges to this media pool if the media pool does not have available tape cartridges.

- 442 -
 7. Click Save.The new Media Pool is created.

Managing Media Pools

From the Media Pool Management page,  you can also edit or delete Media Pools by using the corresponding buttons
or search for the media pool by entering its name or a part of it into the Search box.

- 443 -
Virtual Appliance Configuration
This section covers the following topics:
l “Configuring Network Settings of Virtual Appliance” on page 445
l “Increasing Backup Repository Size on Virtual Appliance” on page 446
l “Removing the Disk with Backup Repository from Virtual Appliance” on page 447

- 444 -
Configuring Network Settings of Virtual Appliance
To configure networking on the Virtual Appliance (VA), follow the steps below:
1. Open the VA console.
2. On the main menu, select the Network Settings option and press Enter.
3. Do either of the following:
l To change the Virtual Appliance hostname, select the Hostname option, press Enter, enter a new
hostname, and press Enter again.
l To configure a network card, select it and press Enter. Press Enter to switch between DHCP and manual
network settings. If you set the DHCP option to disabled, you can manually set up network settings by
selecting an option, pressing Enter, entering a new value, and pressing Enter again. Press F10 to save your
changes and exit. 

- 445 -
Increasing Backup Repository Size on Virtual Appliance
A Backup Repository on a Virtual Appliance (VA) is located in a logical volume (that can spread across multiple physical
volumes). To extend the Backup Repository size on the VA, you need to add a new disk to the VA and then use the VA
console to extend the Backup Repository to the new disk. 
The Backup Repository size on the VA cannot be increased by extending existing VA disks.
The backup repository size on the VA cannot be increased by extending existing VA disks. To increase the size of the
backup repository on the Virtual Appliance, follow the steps below:
1. Attach a new disk to the VA.
2. Open the VA console in your hypervisor's client.
3. Run the following commands in the VA console depending on the NAKIVO Backup & Replication version you use:
l For the product Version 8.1 and higher:
i. Select Manage NAKIVO services in the main menu and press Enter.
II. Select Onboard repository storage and press Enter.
l For earlier product versions, select Backup storage in the main menu and press Enter.
4. Refresh the list of disks by pressing F5.
5. Select the disk that you have created and press Enter.
6. Press Enter again to confirm the procedure. The disk is formatted and added to the Backup Repository on the VA.

- 446 -
Removing the Disk with Backup Repository from Virtual Appli-
ance
The Virtual Appliance (VA) comes with a 500 GB disk on which a Backup Repository is created. If you have deployed the
Virtual Appliance disks using the Thin Provision option, then the disk does not consume 500 GB of space on your
datastore – only the space occupied by VM backups is consumed.
If you still would like to delete the 500GB disk after you have deployed the Virtual Appliance, follow the steps below:
1. Log in to NAKIVO Backup & Replication.
2. Go to the Configuration > Repositories tab.
3. Click Onboard repository
4.  Click Manage and choose Remove from the menu.
5. In the message that opens, click the Remove Repository and Delete Backups button.
6. Click Remove to confirm that you wish to remove the Backup Repository.
7. Open the vSphere client and launch the console of the VA.
8. In the Virtual Appliance interface, select the Exit to system console option and press Enter.
9. Enter a login and password (default are root/root).
10. Run the following command to unmount the volume on which the Backup Repository is located: umount
/opt/nakivo/repository
11. Open the configuration file with the nano editor by running the following command: nano/etc/fstab
12. In the editor, delete the line: dev/mapper/Volume_Group_Backup_Repository_500GB/Logical_
Volume_Backup_Repository_500GB /opt/nakivo ext4 defaults 0 2
13. Save changes by pressing Ctrl+O, and then pressing Enter.
14. Exit the editor by pressing Ctrl+X.
15. Power off the VA and delete the 500 GB disk. 

- 447 -
Multi-Tenant Mode Configuration
This section covers the following topics:
l “Changing Login and Password in Multi-Tenant Mode” on page 449
l “Configuring Email Settings in Multi-Tenant Mode” on page 453
l “Configuring Email Notifications in Multi-Tenant Mode” on page 452
l “Configuring Branding Settings in Multi-Tenant Mode” on page 450
l “Configuring System Settings in Multi-Tenant Mode” on page 454
l “Exporting and Importing Configuration in Multi-Tenant Mode” on page 456

- 448 -
Changing Login and Password in Multi-Tenant Mode
To change the login and password of the Master Admin, follow the steps below:
1. Log in to NAKIVO Backup & Replication as a Master Admin.
2. Click Configuration in the upper right corner of the product.
3. Go to the General tab and click Users and Roles. 
4. In the list of users that opens, click the Master Admin user.
5. For the Master Admin, enter data in the Login, Password, Confirm Password, and Admin email boxes and click
Apply.

- 449 -
Configuring Branding Settings in Multi-Tenant Mode
In the multi-tenant mode, you can change the product branding settings such as product name, logo, background, and
so on. To configure the system settings, follow the steps below:
1. Log in to NAKIVO Backup & Replication as a Master Admin.
2. Click Configuration in the upper right corner of the product.
3. Go to the General tab and click Branding.

4. Do the following:
l To change the product title, company name, website URL, contact email, support email, and contact
phone, type a new value in the appropriate field
l To change the product logo, background, and default tenant logo, click Change under the appropriate
box, select a new image, and click Open.

5. Click Apply. 
NOTE: During upload, the logo and bookmark icon images are resized internally while preserving the aspect ratio. The
background image is used as it is. To get the best image quality, follow the recommendations below:

- 450 -
 Image Best format Best resolution

Global logo .png 40x40

Page
.jpeg 1920x1440
background

Bookmark icon .png 16x16

Default tent logo .png 120x95

- 451 -
Configuring Email Notifications in Multi-Tenant Mode
NAKIVO Backup & Replication can send notifications and reports over email. To configure the email notifications, follow
the steps below:
1. Make sure you have configured your email settings.
2. Log in to NAKIVO Backup & Replication as a Master Admin.
3. Click Configuration in the upper right corner of the product and go to the General tab.
4. Click Email settings.
5. In the Email Notifications section, select the options as appropriate:
a. Send alarm (error) notifications: If selected, this will send notifications about a job, repository,
infrastructure, connection, and other failures to email addresses specified in the text field. Use a semicolon
to separate multiple email addresses.
b. Send warning notifications: If selected, this will send warning notifications on non-critical events, such as
infrastructure change, to email addresses specified in the text field. Use a semicolon to separate multiple
email addresses.
c. Limit email notification frequency to: Set a limit to how often email notifications are sent.
6. In the Automatic Reports section, select or deselect the following automatic reports options:
l Attach PDF copy to automatic reports: Specify whether you wish to include a copy of the PDF report with
notifications. 
l Send tenant Overview reports on schedule to: If this option is selected, NAKIVO Backup & Replication will
generate an Overview report (which includes information about all jobs and groups in the product) on the
date and time specified in the scheduler and will send the report to the recipients specified in the text field.
Use a semicolon to separate multiple email addresses.
l Send tenant Protection Coverage reports on schedule to: If this option is selected, NAKIVO Backup &
Replication will generate the Protection Coverage report (which includes information about all VMs &
instances protected by backup and/or replication jobs as well as the information about all unprotected
VMs & instances) on the date and time specified in the scheduler and will send the report to the recipients
specified in the text field. Use a semicolon to separate multiple email addresses.
l Click Apply.

- 452 -
Configuring Email Settings in Multi-Tenant Mode
Configure email settings so that NAKIVO Backup & Replication can send email notifications as well as reports over email.
If email settings are not configured, tenants will not be able to configure email notifications for their jobs. To configure
email settings, follow the steps below:
1. Log in to NAKIVO Backup & Replication as a Master Admin.
2. Click Configuration in the upper right corner of the product.
3. Go to the General tab and click Email notifications. 
4. In the Email Settings section, enter data in the boxes, and click Send Test Email to verify the settings are correct.
After the email settings are configured, you can configure the product email notifications.

- 453 -
Configuring System Settings in Multi-Tenant Mode
To configure the system settings, follow the steps below:
1. Log in to NAKIVO Backup & Replication as a Master Admin.
2. Click Configuration in the upper right corner of the product.
3. Go to the General tab and click System settings. 
4. Select or deselect the following options:
l Store system events for the last X days: This option specifies the time period (from 10 to 365 days) during
which the application events will be kept. Older events are automatically deleted.
l Auto log out after X minutes of inactivity: If this option is selected, the current user will be automatically
logged out of the product after the specified period of inactivity.
l Auto upload support bundles to support team server: If this option is enabled, NAKIVO Backup &
Replication will automatically create, encrypt, and upload support bundles once a day to a NAKIVO support
server during the evaluation period. The NAKIVO Support team may use this information to improve the
product experience and will be able to identify and resolve product issues faster.
l Enable built-in support chat: If selected, this will allow you to chat with the NAKIVO support team. 
l Display special offers: If selected, this will show a toolbar with special offers in the GUI.
l Continue product update if self-backup fails: If selected, product update will proceed even if automatic
self-backup cannot be performed.
l Tape options: These present  you with setting options for tape devices:
l Auto erase expired tapes: If selected, expired tape cartridges will be erased automatically.
l Wait for next tape for: Specify for how long the system needs to wait for the next tape cartridge if
there is no appropriate one. Select the Send email notification checkbox to allow you to receive
email notifications.
l Auto refresh tapes every: Select how often the contents of tape cartridges are to be refreshed in
minutes or hours. Deselect if no refreshing is required.
l Regional options: Set the clock format, short date format, long date format, first day of the week, decimal
symbol, and default time zone in the corresponding fields. 
l  In the Web Interface TLS/SSL Certificate section, you can either:
l View current certificate: A dialog containing the current certificate information opens.
l Install new certificate: A dialog opens, allowing you to install a new TLS/SSL certificate for the NAKIVO
Backup & Replication web interface. Certificates are generated either internally or through certification
authorities. Proceed as follows to install a new certificate:
l Click Browse and navigate to the location of either of the following certificate file types:
l Private key: A file in the *.key format.
l Private key password (optional): A password for your private key.
l Certificate file: A file in the *.pem, *.crt, *.cer, *.p7b, or *.p7s format.

- 454 -
 l Intermediate certificate (optional): A file in the *.pem, *.crt, *.cer, *.p7b, *.p7s format.
l Click Install. 
Note
In the Web Interface TLS/SSL Certificate section, you can see a notification about imminent TLS/SSL certificate expiration
in 30 days and onwards. If your certificate has expired, you will be asked to install a valid certificate.

- 455 -
Exporting and Importing Configuration in Multi-Tenant Mode
System configuration export and import are recommended for easy migration to new product deployment. System
configuration, such as jobs, user credentials, inventory items, Transporter and Backup Repository settings, is all
exported into a single export bundle.
The export bundle can be applied to a new deployment.
To export system configuration from the old deployment, follow the steps below:
1. Open Configuration of the old deployment.
2. Go to the General tab and click System migration.
3. Click Export system configuration.
4. In the dialog box that opens, click Export.
5. Click Proceed to confirm the operation.
Note
All activities in the old deployment (such as jobs and recovery sessions) will be automatically stopped and
disabled.
6. Wait until the export is completed, and download the export bundle.
To import system configuration into the new deployment, follow the steps below:
1. Open Configuration of the new deployment.
2. Go to the General tab and click System migration.
3. Click Import system configuration.
4. In the dialog window that appears, locate the export bundle using the Browse button.
5. Click Import.
6. Click Proceed to confirm the operation.
Note
 If there is any existing data in the new deployment, it will be overwritten with the import operation.
7. Wait until the import is completed, and close the dialog box.
Notes
l Data contained in backup repositories is not migrated to the new location automatically. If you are using a
locally attached Backup Repository, the physical data must be copied or moved to the new location manually. 
After moving the files you may need to edit the Backup Repository settings in the new deployment so that the
new settings refer to the actual Backup Repository location.
l If a custom TLS/SSL certificate of the Web server was used in the old deployment, a manual service restart will be
required in the new deployment.

- 456 -
Support Bundles
NAKIVO Backup & Replication provides you with the ability to create support bundles – a zipped collection of the
product logs and system information. Sending a support bundle to the NAKIVO Support Team allows them to quickly
identify the root cause of issues and suggest a proper solution.
l Creating Support Bundles
l Sending Support Bundles

Creating Support Bundles

To create a support bundle, follow the steps below: 
Important
Before creating a support bundle, make sure Email settings are configured.
1. Click the "?" (help) icon in the lower-left corner of the web UI.
2. Select and click Request support . The dialog box will appear.
3. Enter a description of your problem in the Please describe the problem you're experiencing box.
4. Enter your email address in the Contact email box.
5. If necessary, upload an attachment by clicking Browse.
6. Select Include logs of all tenants if you wish to include log files of all tenants to the support bundle.
7. Select Include main database if you want to include your main database. 
8. Select Include tenant databases if you wish to include tenant databases containing most of the tenant
configuration, including inventory, transporters, repositories, and jobs.
9. Click Create & Send Support Bundle to send the support bundle to NAKIVO Support Team. You will receive an
answer from the NAKIVO Support Team within one business day.
10. Optionally, click Download to save the support bundle on your machine.

- 457 -
Sending Support Bundles Manually
Some support bundles may become overly large in size. This can occur due to large log files or file dumps. In such cases,
it is recommended to upload these files manually. 
To do this, follow these steps:
1. Open the Upload Files to NAKIVO Support page.
2. In the Files section, click Browse and select up to three files. You can select more than three files by clicking Add
Another File.
Note
You can upload any files relevant to your issue: logs, file dumps, or the support bundles that you have manually
downloaded from the product's UI.
3. Enter your email address in the Contact email field.
4. You can also enter the ID of your support ticket in the Ticket ID field if you have one opened.
5. Optionally, enter a description in the Description field.
6. Click Upload when you’re done uploading the file(s).
Note
Wait for a successful upload notification before closing the page. 

- 458 -
Built-in Support Chat
You have the possibility to contact a NAKIVO representative via chat in the NAKIVO Backup & Replication interface.
l Opening Built-in Support Chat
l Sending Files in Built-in Support Chat
l Sending Feedback to Built-in Support Chat
l Sending Email Transcript of Built-in Support Chat
l Disabling/Enabling Sound Notifications
l Disabling Built-in Support Chat

Opening Built-in Support Chat

To open Built-in Support Chat, follow the steps below:
1. In the lower right corner of the NAKIVO Backup & Replication interface, click the chat button.

2. The NAKIVO Support dialog box opens. Introduce yourself by providing the following information:
a. In the upper box of the dialog box, enter your name.
b. In the box below, enter your email address.
3. Choose a department from the list of available departments.
4. Enter your message text and click Start Chatting.

- 459 -
5. Your message is sent to a NAKIVO representative and will be processed as soon as possible. If needed, click the Send
Another button to proceed with sending another chat message.

Sending Files in Built-in Support Chat

Please use either of the following ways to send your files in Built-in Support Chat:
l Drag and drop: open Windows File Explorer, select necessary files, and then drag them and drop to the chat
dialog.
l Built-in Support Chat interface:
1. In the upper left corner of the Built-in Support Chat dialog, click Options.
2. In the dialog that opens, click Send a file.
3. The Open dialog opens. Navigate to the location of your files, select them and then click Open.

- 460 -
Note
The following file formats are allowed: .pdf, .png, .jpeg, .gif, .txt. The maximum file size is 20 MB.

Sending Feedback to Built-in Support Chat

You have the possibility of sending feedback to Built-in Support Chat: in the upper right corner of the dialog, click Good
or Bad, as you deem appropriate.
If appropriate, leave a comment for NAKIVO Support Team: click Leave a comment and in the
text box that opens, enter your comment about the chat service. Then click Send.

- 461 -
Sending Email Transcript of Built-in Support Chat
Follow the steps below to send the transcript of your Built-in Support Chat session:
1. In the upper left corner of the Built-in Support Chat dialog, click Options.
2. In the dialog that opens, click Email transcript.
3. In the dialog that opens, make sure the email address of the recipient is correct, and then click Send.
Your Built-in Support Chat transcript will be sent to the specified email recipient.

- 462 -
Disabling/Enabling Sound Notifications
By default, sound notifications are enabled for Built-in Support Chat.
Do the following to disable sound notifications in Built-in Support Chat:
1. In the upper left corner of the Built-in Support Chat dialog, click Options.
2. In the dialog that opens, click Sound.
3. Close the options dialog.
Sound notifications will be disabled for Built-in Support Chat.

- 463 -
Disabling Built-in Support Chat
By default, the built-in support chat is enabled in your instance of NAKIVO Backup & Replication.
Do the following to disable built-in support chat:
1. Go to Settings > General > System settings.
2. Click Edit to make system settings editable and then deselect the Enable built-in support chat checkbox.
3. Click the Apply button.

- 464 -
Note
When disabled, the Built-in Support Chat will not be available in all tenants of the NAKIVO Backup & Replication instance
in multi-tenant mode.

- 465 -
Replacing License
To change your current license, follow the steps below:
1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Licensing tab and click Change License.

3. Locate and open the license file in the window that appears.

Upgrading from Free License

If your current license type is Free and the Trial license has not yet been applied to the current deployment of NAKIVO
Backup & Replication, you can try the full functionality of the solution for 15 days. To do that:
1. Open the Help Menu
2. Select the Try full functionality option. A new popup window appears.
3. Click Start Free Trial.
Note
Once the Trial license expires, the product automatically goes back to using your Free license.

- 466 -
Backup
This section contains the following topics:
l “Creating VMware Backup Jobs” on page 468
l “Creating Backup Copy Jobs” on page 497
l “Backing Up to Tape” on page 519
l “Staging (Seeding) Initial Backup” on page 536
l “Deleting Backups” on page 537

- 467 -
Creating VMware Backup Jobs
With NAKIVO Backup & Replication, you can back up VMware VMs by creating a backup job that specifies which VMs
should be backed up, where the backups should be located, how often the backup should be run, and what backup
options should be used. To create a backup job, click Create on the Dashboard and then click VMware vSphere backup
job.

The New Backup Job Wizard for VMware vSphere opens. Complete the wizard as described in the sections below: 
l “Backup Job Wizard for VMware: Source” on page 469
l “Backup Job Wizard for VMware: Destination” on page 474
l “Backup Job Wizard for VMware: Schedule” on page 478
l “Backup Job Wizard for VMware: Retention” on page 482
l “Backup Job Wizard for VMware: Options” on page 484

- 468 -
Backup Job Wizard for VMware: Source
On the Source page in the wizard, you can add VMware VMs to your backup job by using one of the inventory views.
Proceed as described in the sections below:
l Hosts and Clusters
l VMs and Templates
l Policy

Hosts and Clusters

When Hosts & Clusters view is selected, the inventory tree opens in the left pane and displays all VMware items:
clusters, hosts, folders, resource pools, and VMs. Proceed as follows:
1. Optionally, you can filter the inventory tree by entering a string into the Search box. You can enter a part of the
entire name of the item.

2. Select VMware items by placing a checkmark to the left of each item.

3. The selected items appear in the right pane of the page. You can drag a VM or a container with the pointer to a
new position to reorder the selected items. By doing that, you can specify to back up the most important VMs
first.

- 469 -
4. Review the list of selected VMware items. You can remove a selected VM or a container from the backup job in
one of the following ways:
l Deselect the object in the left pane. This will remove the object from the right pane; OR
l In the right pane, hover the pointer over the item you want to remove and. This will deselect the object in

- 470 -
 the left pane.

VMs and Templates

When the VMs & Templates view is selected, the inventory tree displays VMware hosts, VMs, and VM templates.
Proceed as it was described for the Hosts & Clusters view above.

- 471 -
Policy
When the Policy view is selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details.
Follow the steps below:
1. If the items are selected in alternate views, a dialog box opens warning you that switching to the Policy view will
reset your current selection. Click Switch View to confirm switching to the Policy view.

- 472 -
 2. Add at least one rule to the job policy. Refer to “Managing Policy Rules” on page 110 for details.

3. Click Next to confirm adding selected VMs to the backup job. The wizard will display the next page.
Notes
1. If you cannot find a VM or a container, try the following:
l Make sure that the corresponding vCenter or ESXi host has been added to the inventory.
l “Refreshing Inventory” on page 332.
2. By adding a VMware container to the job, you ensure that important VMs are always protected. If you add a
VMware container to the job:
l All VMs currently available in the selected container will be backed up.
l All new VMs that are created in (or moved to) the container in the future will be automatically added to the
job and backed up.
3. The order in which VMs are backed up is important if the Transporter performing the backup cannot process all
VMs of the job simultaneously – either because the Transporter is processing other jobs at the same time or
because the number of VM disks in the job exceeds the Transporter’s maximum Load specified during the
Transporter creation. 

- 473 -
Backup Job Wizard for VMware: Destination
On the Destination page of the wizard, you can select one or different Backup Repositories to back up your VMs.
Proceed as described in the sections below:
l Setting a Single Backup Repository for All VMs
l Setting Different Backup Repositories for VMs
l Mapping Source VMs to Existing Backups
l Excluding VM Disks from the Backup Job

Setting a Single Backup Repository for All VMs

To back up the VMs selected on the previous page to a single Backup Repository, choose a Backup Repository from the
Backup repository drop-down list.

Setting Different Backup Repositories for VMs

To back up the selected VMs to different Backup Repositories, follow the steps below:
1. Click Advanced options.
2. In the VM boxes, choose a Backup Repository for each VM individually from the Target destination drop-down

- 474 -
 list.

Mapping Source VMs to Existing Backups

If you have previously backed up a VM and then lost the backup job due to accidental job deletion or a need to recreate
jobs in a new copy of the product, you can map source VMs to existing backups in order to avoid running full VM
backups again.
To map source VMs to existing backups, follow the steps below:
1. Click Advanced options.
2. From the Backup repository drop-down list, choose a Backup Repository that contains an existing VM backup.

- 475 -
 3. Select the Use existing backup as a target option and choose an existing backup from the drop-down list.

When you run the job, the product will analyze the target VM you have selected, determine how it is different from the
source VM, and transfer only the differential data.
VM backup mapping can be a time-consuming process that can be equal to the time required to create a full VM
backup.
After the job is completed, a new recovery point will be created and existing recovery points will not be changed or
overwritten.

Excluding VM Disks from the Backup Job

If you do not want to back up certain VM disks, you can exclude those disks from the backup job by following the steps
below:
1. Click Advanced options.
2. Cancel the selection of the VM disks that you do not want to back up.

- 476 -
- 477 -
Backup Job Wizard for VMware: Schedule
On the Schedule page of the wizard, select to run the backup job manually or schedule the job to run on a regular basis.
Proceed as described in the sections below:
l Disabling Scheduled Job Execution
l Daily or Weekly Backup
l Monthly or Yearly Backup
l Periodic Backup
l Chained Job
l Additional Schedule

Disabling Scheduled Job Execution

If you want to start the job manually (without any schedule), select the Do not schedule, run on demand checkbox.

Daily or Weekly Backup

To run the job once a day, choose Run daily/weekly from the schedule drop-down list and do the following:
l Choose a time zone that should be used for the job start and end times from the time zone drop-down list.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.

- 478 -
 l If necessary, select the Effective from checkbox and pick the date when the schedule should come into effect. 

Monthly or Yearly Backup

To run the job monthly or yearly, choose Run monthly/yearly from the schedule drop-down list and do the following:
l Specify the job start schedule in the appropriate boxes.
l Specify the day and month when the job should be started in the Run every boxes.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Periodic Backup
To run the job multiple times per day, choose Run periodically from the schedule drop-down list and then choose a
time period from the appropriate boxes:

- 479 -
 l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Chained Job
To run the job after a previous one has completed, choose Run after another job from the schedule drop-down list and
set the options as follows:
l After the job: Select a job after which the current job will be started.
l Run this job: Choose whether to run the current job immediately after the previous one has completed or within
a delay.
l After successful runs: If selected, the job will run if the previous one has completed successfully.
l After failed runs: If selected, the job will run if the previous one has failed.
l After stopped runs: If selected, the job will run if the previous one has been stopped.

- 480 -
 l Effective from: If selected, the schedule will come into effect on the date picked.

Additional Schedule
If you want to have more than one schedule for your job, click Add another schedule and set it up as has been
described above.

- 481 -
Backup Job Wizard for VMware: Retention
After each job run, NAKIVO Backup & Replication creates a recovery point for each VM in the Backup Repository. A
recovery point represents the backed up VM as of a particular moment in time and allows you to recover individual
files, application objects, or the entire VM from the Backup Repository. You can specify how many recovery points you
want to be retained in the Backup Repository using the Grandfather-Father-Son (GFS) backup rotation scheme. 
When the Amazon S3 Backup Repository is selected as the only backup destination, you can apply S3 Object Lock to
recovery points in this repository. With S3 Object Lock applied, the recovery points are immutable and stored using the
write-once-read-many (WORM) model. Immutable recovery points cannot be overwritten, deleted, or changed until a
specified period has expired.

Retention Settings
Here you can set the retention settings for the backup job. Set the following options:
l Keep x last recovery points: Retains the specified number of last recovery points for each VM in the job.
l Keep one recovery point per day for x days: Retains one last recovery point per day for the specified number of
days.
l Keep one recovery point per week for x weeks: Retains the last available backup of every week for the specified
number of weeks.
l Keep one recovery point per month for x months: Retains the last available backup of every month for the
specified number of months.
l Keep one recovery point per year for x years: Retains the last available backup of every year for the specified
number of years.

Immutability
In this section, you can configure the Make recovery points immutable for x days option. The recovery points remain
immutable for the specified number of days.
Note
For the Immutability section to be available, the following conditions must be met:
l Only Amazon S3 Backup Repositories must be selected at the Destination page of the wizard.
l Object Lock must be enabled for the Amazon S3 bucket where your Backup Repository is located.

- 482 -
For more details and an example of job retention settings, refer to the Keeping Recovery Points article in the Knowledge
Base.

- 483 -
Backup Job Wizard for VMware: Options
On the Options page of the wizard, you can set up job options. Proceed as described in the sections below:
l Job Options
l Job Name

l App-Aware Mode

l Change Tracking

l Network Acceleration

l Encryption

l VM Verification

l Skip Swap Files and Partitions

l Skip Unused Blocks

l Full Backup
l Pre and Post Job Actions
l Email Notifications

l Truncation of Microsoft Exchange Server Transactions Logs

l Truncation of Microsoft SQL Server Transaction Logs

l Pre Job Script

l Post Job Script

l Data Transfer
l Transport Mode

l Transporters

l Transporter Load

l Bandwidth Throttling

l Completing the New Backup Job Wizard for VMware

Job Options
In this section, you can specify a name for the backup job and enable/disable app-aware mode, change tracking,
network acceleration, encryption, VM Verification, and other options. Proceed as described below. 

- 484 -
Job Name

Enter a name for the backup job in the appropriate box.

App-Aware Mode

When the app-aware mode option is enabled, VM backup is performed using VMware Guest OS quiescing, which relies
on Microsoft VSS to ensure that application data is consistent. 

Change Tracking

Select one of the options from the Change tracking drop-down list:
l Use VMware CBT: When selected, NAKIVO Backup & Replication enables the VMware Changed Block Tracking
feature for source VMs. This feature enables the product to quickly identify the data blocks that have changed
since the last job run, which significantly increases the job speed. Click the error handling link to specify the
following options:
l On error: Choose one of the following job behaviors in relation to CBT error:
l switch to proprietary method: If VMware CBT fails to provide data on changed blocks for a VM and this
option is selected, NAKIVO Backup & Replication performs an incremental backup of the VM using the
NAKIVO proprietary change tracking technology.
l reset CBT: If VMware CBT fails to provide data on changed blocks for a VM and this option is selected,

- 485 -
 NAKIVO Backup & Replication resets VMware CBT for the VM. 
l fail VM processing: If VMware CBT fails to provide data on changed blocks for a VM and this option is
selected, NAKIVO Backup & Replication does not process the VM and states job failure (other VMs in the
job will be processed).
l Double-check changed blocks provided by CBT: When selected, NAKIVO Backup & Replication runs a check on
data blocks provided by VMware CBT to ensure that VMware CBT does not overstate the amount of changed
data.
l Use proprietary method: When selected, NAKIVO Backup & Replication performs incremental backups using the
NAKIVO proprietary change tracking technology. This feature requires reading the contents of all VM disks to
determine which data blocks have changed since the last job run.
l No change tracking (always full): When selected, NAKIVO Backup & Replication always performs a full VM
backup of all source VMs. 

Network Acceleration

When enabled, NAKIVO Backup & Replication uses compression and traffic reduction techniques to speed up data
transfer. Select this option if you plan to back up over WAN or slow LAN links. 

Encryption

When enabled, VM data is protected with AES 256 encryption while traveling over the network. 
l Data encryption increases the backup time and CPU load on machines running Transporters. Select this option if
you back up over WAN without a VPN connection.
l You need at least one Transporter at source and target sites to enable encryption.

VM Verification

When VM verification is enabled, the NAKIVO Backup & Replication checks the integrity of the backup by starting it and
interacting with it. You can choose one of the following VM verification options: 
l Disabled: VM Verification is disabled.
l Screenshot verification: When enabled, all VM backups created by the job are verified: After a backup of a VM is
completed, the VM is recovered from the backup using Flash VM Boot (and is disconnected from networks) and a
screenshot of the recovered VM is taken once the VM OS has booted, after which the VM is discarded. VM
screenshots are included in email notifications (if they have been configured) and displayed on the Dashboard.
l Boot verification: When enabled, all VM backups created by the job are verified as follows. After a VM backup is
completed, NAKIVO Backup & Replication recovers the VM using Flash VM Boot, disables networking to prevent
network connections, and verifies that system start is successful.
Important
VM verification requires VMware Tools to be installed on all VMs. 

- 486 -
After choosing Screenshot verification, do the following in the dialog box that opens:
1. Provide a location of the VMs to be booted:
a. Target Container: Choose a target container (cluster, host, or resource pool) where VMs will be run using
Flash VM Boot.
b. Target Datastore: Choose a datastore that will host changes to the recovered VMs.
c. Proxy transporter: Choose a proxy Transporter from the list of available Transporters.
Note
NAKIVO Backup & Replication will use a proxy Transporter in the following cases:
l The Transporter assigned to the Backup Repository cannot use iSCSI port 3260 because it is
occupied by other services.
l iSCSI packages are missing on the Transporter assigned to the Backup Repository.
2. Set verification options:
a. Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started
on the target container simultaneously. 
b. Recovery time objective: Specify the amount of time allocated for verification of each VM backup. If a VM
OS does not start within the specified amount of time, verification will be considered failed.
c. Screenshot delay: The amount of time that the product should wait after the guest OS start before
making a screenshot.
The specified time must be sufficient to fully start the VM OS. Try increasing this amount if the default

- 487 -
 amount is insufficient.

After choosing Boot verification, do the following in the dialog box that opens: 
1. Provide a location of the VMs to be booted as described for the Screenshot verification option.
2. Set verification options:
a. Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started
on the target container simultaneously. 
b. Recovery time objective: Specify the amount of time allocated for the verification of each VM backup. If a

- 488 -
 VM OS does not start within the specified amount of time, verification is considered failed.

Skip Swap Files and Partitions

With this option enabled, NAKIVO Backup & Replication automatically skips swap files and partitions during the backup
process.

Skip Unused Blocks

With this option enabled, NAKIVO Backup & Replication automatically skips unused disk blocks and blocks occupied by
deleted files during processing of source objects running Windows OS. This feature allows for reducing backup storage
space and object processing time.

Full Backup
If the type of the Backup Repository that you've selected on the Destination page of the wizard is set to Incremental
with full backups, you can specify the following options:
l Create full backup: Specify how often full backups should be created. 
l Full backup mode: Specify how the full backup should be created. You can choose one of the following options:
l Synthetic Full: When this option is selected, NAKIVO Backup & Replication first performs an incremental
backup (that is, transfers only the data that has changed since the last backup) and then transforms the
available data into a full backup file. The benefits of this approach are:

- 489 -
 l The Synthetic Full backup is usually faster than the Active Full backup.
l The load on the network is lower as less data is transferred.
l The load on the source datastores running your production VMs is lower.
l Active Full: When this option is selected, NAKIVO Backup & Replication reads all VM data from the source
datastore and transfers it to the Backup Repository. 

Pre and Post Job Actions

NAKIVO Backup & Replication allows you to enable certain actions before a backup job begins and after it has
completed. You can choose to send job run reports, truncate Microsoft Exchange and Microsoft SQL Server logs on
specified VMs, and run local pre- and post- job scripts.

- 490 -
Email Notifications

NAKIVO Backup & Replication can send email notifications about job completion status to specified recipients. This
feature complements global notifications and allows you to configure notifications on a per-job level.
To enable this option, configure your Email settings.
To send email notifications, select Send job run reports to and specify one or more email addresses in the text box. Use
semicolons to separate multiple email addresses.

Truncation of Microsoft Exchange Server Transaction Logs

Microsoft Exchange Server database transaction logs record all changes to an Exchange Server database. Over time,
these log files accumulate and can consume all of the available disk space if not periodically removed. NAKIVO Backup &
Replication provides an option to delete (aka truncate) Microsoft Exchange Server logs on the source VMs after job
completion.
The transaction logs are deleted after the job is completed so that the log files are available in the VM backup. Note that
the product deletes only those transaction logs which are already committed to (available in) the Microsoft Exchange
database.
To set up Microsoft Exchange log truncation, do the following:
1. Select the Truncate Exchange logs option.
2. In the dialog box that opens, select the checkboxes next to the VMs running Microsoft Exchange and then select

- 491 -
 the credentials next to each VM. These credentials will be used to log in to the VMs that you have selected. 

Truncation of Microsoft SQL Server Transaction Logs

Microsoft SQL Server database transaction logs record all changes to an SQL Server database. Over time, these logs
accumulate and can consume all of the available disk space if not periodically removed. NAKIVO Backup & Replication
provides the option to delete (or truncate) Microsoft SQL Server logs on the source VMs after job completion.
The transaction logs are deleted after the job is completed so that the original log records are available in the VM
backup. Note that the product deletes only those transaction logs that are already committed to (available in) the
Microsoft SQL Server database.
To set up Microsoft SQL Server log truncation, do the following:
1. Select the Truncate SQL Server logs option.
2. In the dialog box that opens, select the checkboxes next to the VMs running Microsoft SQL Server and then
select credentials next to each VM. These credentials will be used to log in to the VMs that you have selected.

Pre Job Script

To run a script before the product begins backing up VMs, do the following:
1. Place a script file on the machine on which the Director is installed.
2. Select the Run local pre job script option.
3. Specify the following options in the dialog box that opens:
l Script path: Specify a local path to the script on the machine on which the Director is installed. A script
interpreter should be specified.
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: When this option is selected, VM backup is only started after the
script is completed.
l Do not wait for the script to finish: When this option is selected, the product runs the script and
starts backing up VMs at the same time.
l Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: When this option is selected, the job performs VM backup even
if the script has failed.
l Fail the job on script failure: When this option is selected and the script fails, the job is failed and
VM backup is not performed.

Post Job Script

To run a script after the product has finished backing up all VMs, do the following:

- 492 -
 l Place a script file on the machine on which the Director is installed.
l Select the Run local post job script option.
l Specify the following options in the dialog box that opens:
l Script path: Specify a local path to the script on the machine on which the Director is installed. A script
interpreter should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: When this option is selected, the job is in the “running” state until the
script is completed.
l Do not wait for the script to finish: When this option is selected, the job is completed even if the
script execution is still in progress.
l Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: When this option is selected, script failure does not influence
the status of the job.
l Fail the job on script failure: When this option is selected and the script fails, the job status is set
to “failed” even if VM backup is successful.
Important
Pre- and post-job scripts can be executed only on the machine on which the Director is installed. 

Data Transfer
In the Data Transfer section of the Options page, you can choose a transport mode, select a Transporter to be used for
reading data from source VMs, specify a Transporter load, and configure bandwidth throttling.

- 493 -
Transport Mode

To select a transport mode, do the following:

1. In the Data Transfer section, choose a transport mode for retrieving VM data:
l Automatic selection: When this option is selected, NAKIVO Backup & Replication automatically selects the
best transport mode available:
l When the source Transporter is installed on a VM, NAKIVO Backup & Replication tries to use
transport modes in the following order: Hot Add > SAN > LAN.
l When the source Transporter is installed on a physical machine, NAKIVO Backup & Replication tries
to use transport modes in the following order: SAN > LAN. Hot Add is not supported for physical
machines.
l SAN only: When this option is selected, NAKIVO Backup & Replication only uses direct SAN access to
retrieve VM data. If direct SAN access to VM data is not available, the job fails.
l Hot-add only: When this option is selected, NAKIVO Backup & Replication only uses Hot-add to retrieve
VM data. If direct Hot-add is not available, the job fails.
Note
When hot-add cannot be enabled for at least one disk of a source VM (even if the disk is deselected in the
job), Hot-add is unavailable for all disks of the VM
l LAN only: When this option is selected, NAKIVO Backup & Replication only retrieves VM data over LAN.

- 494 -
Transporters

In NAKIVO Backup & Replication, Transporters perform all of the heavy lifting: reading data from the source VM,
compressing the data, transferring the data over the network, performing data deduplication, and so on. In large and
geographically distributed environments, multiple Transporters can be deployed to distribute the data protection
workload, optimize network traffic, and improve data transfer speeds. Thus, if more than one Transporter is deployed
for NAKIVO Backup & Replication, it is important to determine which should be used to read data from a particular
source VM (the target Transporter is always the one that is assigned to the Backup Repository).
By default, the product automatically determines which Transporter should be used to read data from the source VM.
However, you can manually specify which Transporters should be used for the job. To manually specify Transporters,
proceed as follows:
In the Data Transfer section, choose one of the following options:
l Automatic selection: The product automatically determines which Transporters are the closest to source hosts

(the hosts that run selected VMs) and uses those Transporters to retrieve data from source VMs.
l Manual - configured for all VMs: Select this option to manually specify a single Transporter to be used to

retrieve data from source VMs.

l Manual - configured per host: Select this option to manually specify which Transporter should be used to

retrieve data from each source host.

Transporter Load

You can limit the maximum number of Transporter tasks used by the job. By default, this number is set to 3 concurrent
tasks.
To change the default number of tasks, do the following:
1. In the Data Transfer section, select the Limit transporter load to checkbox.
2. Specify the number of concurrent tasks in the corresponding box.

Bandwidth Throttling

Follow the steps below to regulate the speed of data transfer over the network for your backup job:
1. For the Bandwidth throttling option, choose Enabled.
Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer
to “Bandwidth Throttling” on page 283 for details.
2. Click the settings link that becomes available.
3. The Job Bandwidth Rules dialog box opens, displaying the list of available rules. You have the following options:
l Create a new bandwidth rule for your backup job:
a. Click the Create New Rule button.
b. The New Bandwidth Rule dialog box opens. Refer to the “Bandwidth Throttling” on page 283 topic

- 495 -
 for details on creating a bandwidth rule.
c. Click Save.
l Activate an existing bandwidth rule for your job. Select the checkbox to the left of the required bandwidth
rule. To deactivate a bandwidth rule for your job, deselect the corresponding checkbox.
l Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth
Rule dialog box that opens.
l Disable a bandwidth rule. Click the Disable link. The bandwidth rule is disabled for all jobs.
l Remove a bandwidth rule. Click the Remove link and then click Delete to confirm your operation.

Completing the New Backup Job Wizard for VMware

Click Finish or Finish & Run to complete job creation.
Note
If you click Finish & Run, you will have to define the scope of your job. Refer to “Running Jobs on Demand” on page 97
for details.

- 496 -
Creating Backup Copy Jobs
To create a backup copy job, click Create on the Dashboard, and then click Backup copy job.

The New Backup Copy Job Wizard opens. Complete the wizard as described in the sections below: 
l “Backup Copy Job Wizard: Backups” on page 498
l “Backup Copy Job Wizard: Destination” on page 501
l “Backup Copy Job Wizard: Schedule” on page 504
l “Backup Copy Job Wizard: Retention” on page 508
l “Backup Copy Job Wizard: Options” on page 510

- 497 -
Backup Copy Job Wizard: Backups
On the Backups page of the wizard, you can add items to your backup copy job using one of the inventory
views. Proceed as described in the sections below:
l Creating Backup Copies Using Jobs and Groups

l Creating Backup Copies Using Backup Repositories

l Creating Backup Copies Using Policies

Creating Backup Copies Using Jobs and Groups

In the left pane of the page, select the Jobs & Groups view to use existing backup jobs and groups. The inventory tree
opens in the left pane and displays the backup groups along with backups. Proceed as follows:
1. Optionally, filter the inventory tree by entering a string into the Search box. You can enter a part of the entire
name of the item.
2. Select backup items by selecting the checkbox next to the item.
3. The selected items appear in the right pane of the page. If necessary, reorder the selected items by dragging
them to a new position. By doing so, you can specify what items you wish to back up first.
4. Review the list of the selected items. If needed, remove a selected backup from the backup copy job in either of
the following ways:
l Cancel the selection of the item(s) in the left pane. This will remove the item(s) from the right pane.
l In the right pane, hover over the item you wish to remove and click the red “X” to the right. This will cancel
the selection of the item(s) in the left pane.

Creating Backup Copies Using Backup Repositories

If the Backup Repositories view is selected, the inventory tree displays the Backup Repositories along with backups.
Proceed as described for the Jobs & Groups view above.

- 498 -
Creating Backup Copies Using Policies
If the Policy view is selected, it allows you to use job policies; refer to “Managing Job Policies” on page 108 for details.
Please follow the steps below:
1. If the items were selected in alternate views, a dialog box opens, warning you that switching to the Policy view
will reset your current selection. Click Switch View to confirm that you wish to switch to the Policy view.
2. Make sure that at least one item matches the available set of policy rules. Refer to “Managing Policy Rules” on
page 110 for details.

Click Next to confirm that you wish to add selected items to the backup copy job. The wizard will display the next page.
Notes
1. If you add a container – a group, job, or a backup repository,– to the backup copy job, the following will happen:
l All backups currently available in the selected container will be backed up.
l All new backups that will be created in (or moved to) the container in the future will be automatically
added to the job and backed up.
2. The order in which backups are copied is important if the Transporter running the job cannot process all items
simultaneously: either because the Transporter is processing other tasks at the same time or because the

- 499 -
number of backups in the job exceeds the Transporter’s Maximum Load specified during the Transporter
creation.

- 500 -
Backup Copy Job Wizard: Destination
On the Destination page of the wizard, select a target location for backup copies.
l Selecting a Tape Storage
l Selecting A Target Backup Repository
l Mapping Source Backups to Existing Backups

Selecting a Tape Storage

The Backup Copy Job Wizard allows you to copy backups to tape devices or to media pools. Detailed information about
copying backups to tapes is available in “Backing Up to Tape” on page 519 .

Selecting a Target Backup Repository

Backup Copy jobs can copy backups from one Backup Repository to another. Select a target Backup Repository as
described below:
l To copy all backups you have selected on the Backups page to a single Backup Repository, select Disk from
the Destination type drop-down list and then select a Backup Repository from the Destination drop-down list.

l To copy backups to different Backup Repositories, follow the steps below:

a. Click Advanced options.

- 501 -
 b. For each backup, select a target Backup Repository.

Mapping Source Backups to Existing Backups

If you have previously copied backups to a different Backup Repository and then lost the Backup Copy job (due to
accidental job deletion or because you need to recreate jobs in a new copy of the product) you can map source backups
to existing backups in the target Backup Repository to avoid transferring all backup data again.
To map source backups to existing backups in a target Backup Repository, follow the steps below:
1. Click Advanced options.
2. From the Backup repository drop-down list, choose a Backup Repository that contains a copy of the source
backup.

- 502 -
 3. Select the Use existing backup as a target option and select the existing backup copy from the drop-down list.

When running the job, the product analyzes the existing backup copy you have selected, determines how it is different
from the source backup, and transfers only the differential data.

- 503 -
Backup Copy Job Wizard: Schedule
On the Schedule page of the wizard, select to run the backup job manually or schedule the job to run on a regular basis.
l Disabling Scheduled Job Execution
l Daily or Weekly Backup
l Monthly or Yearly Backup
l Periodic Backup
l Chained Job
l Adding Additional Schedule

Disabling Scheduled Job Execution

If you wish to start the job manually (without any schedule), select the Do not schedule, run on demand checkbox.

Daily or Weekly Backup

To run the job once a day, choose Run daily/weekly from the schedule drop-down list and do the following:
l Choose a time zone that should be used for the job start and end times from the time zone drop-down list.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.

- 504 -
 l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Monthly or Yearly Backup

To run the job monthly or yearly, choose Run monthly/yearly from the schedule drop-down list and do the following:
l Specify the job start schedule in the appropriate boxes.
l Specify the day and month when the job should be started in the Run every boxes.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

- 505 -
Periodic Backup
To run the job multiple times per day, choose Run periodically from the schedule drop-down list and then choose a
time period from the appropriate boxes:
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Chained Job
To run the job after a previous one has completed, choose Run after another job from the schedule drop-down list and
set the options as follows:
l After the job: Select a job after which the current job will be started.
l Run this job: Choose whether to run the current job immediately after the previous one has completed or within
a delay.
l After successful runs: If selected, the job will run if the previous one has completed successfully.
l After failed runs: If selected, the job will run if the previous one has failed.
l After stopped runs: If selected, the job will run if the previous one has been stopped.

- 506 -
 l Effective from: If selected, the schedule will come into effect on the date picked.  

Adding Additional Schedule

If you want to have more than one schedule for your job, click Add another schedule and set it up as has been
described above.

- 507 -
Backup Copy Job Wizard: Retention
Specify the number of recovery points that the job must copy. When the Amazon S3 Backup Repository is selected as
the only backup destination, you can apply S3 Object Lock to recovery points in this repository. With S3 Object Lock
applied, the recovery points are immutable and stored using the write-once-read-many (WORM) model. Immutable
recovery points cannot be overwritten, deleted, or changed until a specified period has expired.

Retention Settings
Here you can set the retention settings for the backup job. Set the following options:
l Maintain exact copy of the source backup: All available recovery points are copied by the job. To set a different
retention policy, deselect this option and choose one of the options below. 
l Keep x last recovery points: Keeps the specified number of last recovery points for each VM in the job.
l Keep one recovery point per day for x days: Retains one last recovery point per day for the specified number of
days.
l Keep one recovery point per week for x weeks: Retains the last available backup of every week for the specified
number of weeks.
l Keep one recovery point per month for x months: Retains the last available backup of every month for the
specified number of months.
l Keep one recovery point per year for x years: Retains the last available backup of every year for the specified
number of years.

Immutability
In this section, you can configure the Make recovery points immutable for X days option. The recovery points remain
immutable for the specified number of days.
Note
For the Immutability section to be available, the following conditions must be met:
l Only Amazon S3 Backup Repositories must be selected at the Destination page of the wizard.
l Object Lock must be enabled for the Amazon S3 bucket where your Backup Repository is located.

- 508 -
For more details and an example of job retention settings, refer to the Keeping Recovery Points article in the Knowledge
Base.

- 509 -
Backup Copy Job Wizard: Options
On the Options page of the wizard, you can set up job options. Proceed as described in these sections: 
l Job Options
l Job Name

l Network Acceleration

l Encryption

l VM Verification

l Full Backup
l Pre and Post Actions
l Email Notifications

l Pre Job Script

l Post Job Script

l Data Transfer
l Transporter Load

l Bandwidth Throttling

l Completing the New Backup Copy Job Wizard

Job Options
In this section, you can give a name to the backup copy job and enable/disable network acceleration, change tracking,
encryption, and VM Verification. Proceed as described below.

Job Name

Specify a name for the backup copy job in the Job Name box.

- 510 -
Network Acceleration

If network acceleration is enabled, NAKIVO Backup & Replication uses compression and traffic reduction techniques to
speed up data transfer. Select this option if you plan to back up over WAN or slow LAN links. 

Encryption

If the Encryption option is selected, backup data will be protected with AES 256 encryption while traveling over the
network. Data encryption increases the backup time and CPU load on machines running Transporters. Select this
option if you are backing up over WAN without a VPN connection. 
Note
You need at least one Transporter at the source and target sites to enable encryption.

VM Verification

VM Verification allows you to check the integrity of the backup by starting it and interacting with it. For more details,
refer to “VM Verification” on page 43 . 
You can choose one of the following VM verification options: 
l Disabled: VM verification is disabled.
l Screenshot verification: When enabled, all VM backups created by the job are verified: After a backup of a VM is
completed, the VM will be recovered from the backup using Flash VM Boot (and will be disconnected from
networks) and a screenshot of the recovered VM will be taken once the VM OS has booted, after which the VM
will be discarded. VM screenshots will be included in email notifications (if they’re configured) and displayed on
the Dashboard.
l Boot verification: When enabled, all VM backups created by the job are verified as follows. After a VM backup is
completed, NAKIVO Backup & Replication recovers the VM using Flash VM Boot, disables networking to prevent
network connections, and verifies that system start is successful. 
After choosing Screenshot verification, provide the following information in the dialog box that opens: 
1. Provide a location of the VMs that need to be booted:
a. Target Container: Choose a target container (cluster, host, or resource pool) where VMs will be run using
Flash VM Boot.
b. Target Datastore: Choose a datastore that will host changes to the recovered VMs.
c. Proxy transporter: Choose a proxy transporter from the list of available Transporters.
Note
NAKIVO Backup & Replication will use a proxy Transporter in the following cases:
The Transporter assigned to the Backup Repository cannot use iSCSI port 3260 because it is occupied by other
services.
iSCSI packages are missing on the Transporter assigned to the Backup Repository.

- 511 -
 2. Set verification options:
l Verify not more than X VMs simultaneously: Specify the maximum number of VMs that can be started
on the Target Container simultaneously. 
l Recovery time objective: Specify the amount of time allocated for the verification of each VM backup. If a
VM OS does not start within the specified amount of time, verification will be considered failed.
l Screenshot delay: The amount of time that the product should wait after the guest OS starts before taking
a screenshot.
The specified time must be sufficient to fully start the VM OS. Try increasing this amount if the default
amount is not sufficient.

After selecting Boot verification, do the following in the dialog box that opens: 
1. Provide the location of the VMs to be booted as described for the Screenshot verification option.
2. Set verification options:
l Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started
on the Target Container simultaneously. 
l Recovery time objective: Specify the amount of time allocated for verification of each VM backup. If a VM

- 512 -
 OS does not start within the specified amount of time, verification will be considered failed.

Full Backup
If the type of the Backup Repository that you selected on the Destination page is set to Incremental with full backups,
you can specify the following options:
l Create full backup: Specify how often full backups should be created. 
l Full backup mode: Specify how the full backup should be created. You can choose between the following
options:
l Synthetic Full: If this option is selected, NAKIVO Backup & Replication will first perform an incremental
backup (that is, will transfer only the data that has changed since the last backup) and will then transform
the available data into a full backup file. The benefits of this approach are as follows:
l The synthetic full backup is usually faster than the active full backup.
l The load on the network is lower, as less data is transferred.
l The load on the source datastores running your production VMs is lower.
l Active Full: If this option is selected, NAKIVO Backup & Replication will read all VM data from the source

- 513 -
 datastore and transfer it to the Backup Repository. 

Pre and Post Actions

NAKIVO Backup & Replication allows you to set up certain actions before a backup copy job begins and after it has
completed. You can choose to send job run reports to the email provided and run local pre and post job scripts.

Email Notifications 

NAKIVO Backup & Replication can send email notifications on job completion status to specified recipients. This feature
complements global notifications and provides you with the ability to configure notifications on a per-job level.
To enable this option, configure your Email settings.
To send email notifications, do the following:

- 514 -
 1. In the Pre and Post Actions section, select the Send job run reports to option.
2. Specify one or more email addresses in the text box. Separate multiple email addresses with a semicolon.

Pre Job Script

To run a script before the product begins copying backups, do the following:
1. Place a script file on the machine where the Director is installed.
2. In the Pre and Post Actions section, select the Run local pre job script option and click the settings link. Specify
the following parameters in the dialog box that opens:
l Script path: Specify a local path to the script on the machine where the Director is installed. Script interpreter
should be specified.
Example (Windows): cmd.exe /c D:\script.bat

Example (Linux): bash /root/script.sh

l Job behavior: Choose either of the following job behaviors in relation to script completion:
l Wait for the script to finish: If this option is selected, the backup copy will not be started until the script
is completed.
l Do not wait for the script to finish: If this option is selected, the product will run the script and will start
copying backups at the same time.
l Error handling: Choose either of the following job behaviors in relation to script failure:
l Continue the job on script failure: If this option is selected, the job will perform backup copy even if the
script has failed.
l Fail the job on script failure: If this option is selected and the script fails, the job will be failed and the
backup copy will not be performed.

Post Job Script

To run a script after the product has finished copying all backups, do the following:
1. Place a script file on the machine on which the Director is installed.
2. In the Pre and Post Actions section, select the Run local post job script option and click the settings link. Specify
the following parameters in the dialog box that opens:

- 515 -
 l Script path: Specify a local path to the script on the machine on which the Director is installed. Script interpreter
should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose either of the following job behaviors in relation to script completion:
l Wait for the script to finish: If this option is selected, the job will be in the “running” state until the script

is completed.
l Do not wait for the script to finish: If this option is selected, the job will be completed even if the script

execution is still in progress.

l Error handling: Choose either of the following job behaviors in relation to script failure.
l Continue the job on script failure: If this option is selected, script failure will not influence the status of
the job.
l Fail the job on script failure: If this option is selected and the script has failed, the job status will be set
to “failed” even if VM backup has been successful.
Notes
l Pre- and post-job scripts can be executed only on the machine on which the Director is installed.
l When Integration Services are used on Hyper-V 2016 and above, custom pre/post scripts are unavailable for
Windows VMs.

Data Transfer
In the Data Transfer section of the Options page, you can specify a Transporter load and configure bandwidth
throttling.

- 516 -
Transporter Load

You can limit the maximum number of Transporter tasks used by the job. By default, it is set to 3 concurrent tasks.
To change the default number of tasks, do the following:
1. In the Data Transfer section, select the Limit transporter load to checkbox.
2. Specify the number of concurrent tasks in the corresponding box.

Bandwidth Throttling

Follow the steps below to regulate the speed of data transfer over the network for your backup copy job:
1. For the Bandwidth throttling option, choose Enabled.
Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. 
2. Click the settings link that becomes available.
3. The Job Bandwidth Rules dialog box opens displaying you the list of available rules. You have the following
options:
l Create a new bandwidth rule for your backup copy job:
a. Click the Create New Rule button.
b. The New Bandwidth Rule dialog box opens. Refer to “Bandwidth Throttling” on page 283 for details
on creating a bandwidth rule.
c. Click Save.
l Activate an existing bandwidth rule for your job. Select the checkbox to the left of the necessary
bandwidth rule. To deactivate a bandwidth rule for your job, clear the corresponding checkbox.
l Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth Rule
dialog box that opens.
l Disable a bandwidth rule. Click the Disable link. The bandwidth rule will be disabled for all jobs.

- 517 -
 l Remove a bandwidth rule. Click the Remove link and then click Delete to confirm your operation.

Completing the New Backup Copy Job Wizard

Click Finish or Finish & Run to complete the job creation.
Note
If you click Finish & Run, you will have to define the scope of your job. Please refer to “Running Jobs on Demand” on
page 97 for details.

- 518 -
Backing Up to Tape
Backing up to tape is, in essence, performing a backup copy job with the destination set to a tape device or media pool.
Currently, the direct backing up to tape is not supported, instead, it is done in stages: the backup is first put into a
Backup Repository and then moved to tape via a Backup copy job.
To create a backup copy job, click Create on the Dashboard and then click Backup copy job.

The  New Backup Copy Job Wizard opens. Complete the wizard as described in the sections below: 
l “Tape Backup Wizard: Backups” on page 520
l “Tape Backup Wizard: Destination” on page 523
l “Tape Backup Wizard: Schedule” on page 524
l “Tape Backup Wizard: Retention” on page 528
l “Tape Backup Wizard: Options” on page 529

- 519 -
Tape Backup Wizard: Backups
On the Backups page of the wizard, you can add items to your backup copy job. Proceed as follows:
1. In the left pane of the page, choose either of the following inventory views:
l Jobs & Groups: If chosen, the inventory tree opens in the left pane and shows the backup groups along
with backups. Proceed as follows:
a. Optionally, filter the inventory tree by entering a string to the Search box. You can enter a part or
the entire item name.
b. Select backup items by selecting the checkbox next to the them.
c. The selected items appear in the right pane of the page. If necessary, reorder the selected items by
dragging them to a new position. By doing so, you can specify the order in which the items should
be backed up.
d. Review the list of the selected items. If needed, remove a selected backup in the backup copy job in
either of the following ways:
l Cancel the selection of the item(s) in the left pane. This will remove the item(s) from the right
pane.
l In the right pane, hover over the item you want to remove and click the red “X” to the right.
This will cancel the selection of the item(s) in the left pane.

l Backup Repositories: If chosen, the inventory tree shows available Backup Repositories along with the

- 520 -
 backups in them. Proceed as it is described for the Jobs & Groups view above.

l Policy: If selected, this allows you to use job policies; refer to “Managing Job Policies” on page 108 for
details. Please follow the steps below:
a. If items were selected in alternate views, a dialog box opens warning you that switching to the Policy
view will reset your current selection. Click Switch View to confirm switching to the Policy view.
b. Make sure that at least one item matches the available set of policy rules. Refer to “Managing Policy
Rules” on page 110 for details.

- 521 -
 2. Click Next to confirm adding selected items to the backup copy job.
The wizard will display the next page.
Notes
1. If you add a container – a group, job, or a backup repository – to the backup copy job, the following actions will
occur:
l All backups currently available in the selected container will be backed up.
l All new backups that are created in (or moved to) the container in the future will be automatically added to
the job and backed up.
2. The order in which backups are copied is important if the Transporter that is running the job cannot process all
items simultaneously: either because the Transporter is processing other tasks at the same time or because the
number of backups in the job exceeds the Transporter’s Maximum Load specified during the Transporter
creation.

- 522 -
Tape Backup Wizard: Destination
On the Destination page, you can specify where the backup will be stored. You can select a device or a media pool. The
job allows for copying a backup from a Backup Repository to tape cartridges or a virtual tape library.
To specify a destination for the selected backups:
1. From the Destination type drop-down list, select Tape.
2. From the Destination drop-down list, select one of the configured devices or media pools.
3. To see the space and disks the individual backups take, click the name of the job and expand the backups in the
list.

4. Click Next to proceed to the next page.

- 523 -
Tape Backup Wizard: Schedule
On the Schedule page of the wizard, select to run the backup job manually or schedule the job to run on a regular basis.
l Disabling Scheduled Job Execution
l Daily or Weekly Backup
l Monthly or Yearly Backup
l Periodic Backup
l Chained Job
l Adding Another Schedule

Disabling Scheduled Job Execution

If you wish to start the job manually (without any schedule), select the Do not schedule, run on demand checkbox.

Daily or Weekly Backup

To run the job once a day, choose Run daily/weekly from the schedule drop-down list and do the following:
l Specify the time when the job should be started in the Starting box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Choose a time zone that should be used for the job start and end times from the time zone drop-down list.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

- 524 -
Monthly or Yearly Backup
To run the job monthly or yearly, choose Monthly/yearly from the schedule drop-down list and do the following:
l Specify the job start schedule in the appropriate boxes.
l Specify the day and month when the job should be started in the Run every boxes.
l Specify the time when the job should be started in the Starting box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

- 525 -
Periodic Backup
To run the job multiple times per day, choose Run periodically from the schedule drop-down list and then choose a
time period from the appropriate boxes:
l Specify the time when the job should be started in the Starting box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Chained Job
To run the job after a previous one has completed, choose Run after another job from the schedule drop-down list and
set the options as follows:
l After the job: Select a job after which the current job will be started.
l Run this job: Choose whether to run the current job immediately after the previous one has completed or within
a delay.
l After successful runs: If selected, the job will run if the previous one has completed successfully.
l After failed runs: If selected, the job will run if the previous one has failed.
l After stopped runs: If selected, the job will run if the previous one has been stopped.
l Effective from: If selected, the schedule will come into effect on the date picked.  

- 526 -
Adding Another Schedule
If you want to have more than one schedule for your job, click Add another schedule and set it up as has been
described above.

- 527 -
Tape Backup Wizard: Retention
Specify how many recovery points you need to be copied by the job. Use the following options:
l Keep all recovery points forever: All available recovery points will be copied by the job. To set a different
retention policy, deselect this option and choose one of the options below. 
l Keep X last recovery points: Keeps the specified number of last recovery points for each machine in the job.
l Keep one recovery point per day for X days: Keeps one last recovery point per day for the specified number of
days.
l Keep one recovery point per week for X weeks: Keeps the last available backup of every week for the specified
number of weeks.
l Keep one recovery point per month for X months: Keeps the last available backup of every month for the
specified number of months.
l Keep one recovery point per year for X years: Keeps the last available backup of every year for the specified
number of years.

For an example of job retention settings and further explanation, refer to the Keeping Recovery Points Knowledge Base
article.

- 528 -
Tape Backup Wizard: Options
Options page of the wizard, you can name the job and enable/disable network acceleration and encryption. What’s
more, you can set up pre and post actions and enable bandwidth throttling. 
l Job Options
l Job Name

l Network Acceleration

l Data Encryption

l Full Backup Settings

l Create Full Backup

l Tape Appending

l Pre and Post Job Actions

l Email Notifications

l Pre Job Script

l Post Job Script

l Data Transfer
l Bandwidth Throttling

l Completing Tape Backup Wizard

Job Options
In this section, you can give a name to the tape backup job and enable/disable app-aware mode, change tracking,
network acceleration, and encryption.

Job Name

Specify a name for the tape backup job in the Job name box.

- 529 -
Network Acceleration

Once Network Acceleration is enabled, NAKIVO Backup & Replication will use compression and traffic reduction
techniques to speed up data transfer. Select this option if you are backing up over WAN without a VPN connection. For
more information, refer to Network Acceleration. 

Data Encryption

If the Encryption option is selected, backup data will be protected with AES 256 encryption while traveling over the
network. Data encryption increases the backup time and CPU load on machines running Transporters. Select this
option if you back up over WAN without a VPN connection. For more information, refer to “Encryption in Flight and at
Rest” on page 38.
Note
You need at least one Transporter at the source and target sites to enable encryption.

Full Backup Settings

In this section, select when you want the system to create full backups and set up the rules for data appending.

Creating Full Backup

With the Create full backup list, you can specify how often the system should perform a full (not incremental) backup
to tape. The following options are available:
l Always: Every backup will be full
l Every: Select a day of the week. The full backup will be performed once a week on a specified day
l Every 2nd: Select a day of the week. The full backup will be performed once in 2 weeks on a specified day
l First: Select a day of the week. The full backup will be performed once per month starting with the first specified

- 530 -
 day of the month
l Second: Select a day of the week. The full backup will be performed once per month starting with the second
specified day of the month
l Third: Select a day of the week. The full backup will be performed once per month starting with the third specified
day of the month
l Fourth: Select a day of the week. The full backup will be performed once per month starting with the fourth
specified day of the month
l Last: Select a day of the week. The full backup will be performed once per month starting with the last specified
day of the month
l Day #: Select the day number. The full backup will be performed once per month on the specified day number
l Job runs #: Specify the number of backup jobs to pass before running a full backup
Note
Only Always and Job runs # options are always available for selection. The rest of the options' availability depends on
the scheduling settings specified on the Schedule page.

Tape Appending

The Tape appending feature allows you to set up the rules for data appending. The following options are available:
l Append previous tape if possible: 
l The job run appends data to the last tape cartridge.
l If the tape cartridge that was last written during the last job run is not available in the device or is full, the
job starts with an empty cartridge:
l All job objects within the job run are written to the selected tape cartridge one by one.
l If the selected tape cartridge runs out of space, the next empty tape cartridge is selected and the
process repeats until all job objects are written.
l Start full backup with an empty tape: 
l In case the backup modes of all job objects within the job run are defined as full:
l The job run starts with an empty tape cartridge.
l All job objects within the job run are written to the selected tape cartridge one by one.
l If the selected tape cartridge runs out of space, the next empty tape cartridge is selected and the
process repeats until all job objects are written.
l In case the backup modes of all job objects within the job run are defined as incremental:
l The job run appends data to the last tape cartridge.
l All job objects within the job run are written to the selected tape cartridge one by one.
l If the selected tape cartridge runs out of space, the next empty tape cartridge is selected and the
process repeats until all job objects are written.
l In case the backup modes of all job objects within the job run are defined as a mix of full and incremental
modes:

- 531 -
 l The job run appends data to the last tape cartridge.
l All job objects within the job run are written to the selected tape cartridge one by one.
l If the selected tape cartridge runs out of space, the next empty tape cartridge is selected and the
process repeats until all job objects are written.
l Always start with an empty tape: 
l The job starts with an empty tape cartridge.
l All job objects within the job run are written to the selected tape cartridge one by one.
l In case the selected tape cartridge runs out of space, the next empty tape cartridge is selected and the
process repeats until all job objects are written.

Pre and Post Job Actions

NAKIVO Backup & Replication provides you with the ability to enable certain actions before a tape backup job begins
and after it has completed. You can choose to send job run reports to the email provided and run local pre and post job
scripts.

Email Notifications 

NAKIVO Backup & Replication can send email notifications on job completion status to specified recipients. This feature
complements global notifications and provides you with the ability to configure notifications on a per-job level.
To enable this option, configure your Email settings.
To send email notifications, do the following:
l In the Pre- and Post- Actions section, select the Send job run reports to option and specify one or more email
addresses in the text box. Separate multiple email addresses with a semicolon.

- 532 -
Pre Job Script

To run a script before the product begins copying backups, do the following:
1. Place a script file on the machine on which the Director is installed.
2. In the Pre and Post Actions section, select the Run local pre job script option and click the settings link. Specify
the following parameters in the dialog that opens:
l Script path: Specify a local path to the script on the machine on which the Director is installed. Script interpreter
should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose either of the following job behaviors in relation to script completion:
l Wait for the script to finish: If this option is selected, tape backup will not be started until the script is
completed.
l Do not wait for the script to finish: If this option is selected, the product will run the script and will start
copying backups at the same time.
l Error handling: Choose either of the following job behaviors in relation to script failure:
l Continue the job on script failure: If this option is selected, the job will perform tape backup even if the
script has failed.
l Fail the job on script failure: If this option is selected and the script fails, the job will be failed and tape
backup will not be performed.

Post Job Script

To run a script after the product has finished copying all backups, do the following:
1. Place a script file on the machine on which the Director is installed.
2. In the Pre and Post Actions section, select the Run local post job script option and click the settings link. Specify
the following parameters in the dialog box that opens:

- 533 -
 l Script path: Specify a local path to the script on the machine on which the Director is installed. Script interpreter
should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose either of the following job behaviors in relation to script completion:
l Wait for the script to finish: If this option is selected, the job will be in the “running” state until the script
is completed.
l Do not wait for the script to finish: f this option is selected, the job will be completed even if the script
execution is still in progress.
l Error handling: Choose either of the following job behaviors in relation to script failure:
l Continue the job on script failure: If this option is selected, script failure will not influence the status of
the job.
l Fail the job on script failure: If this option is selected and the script has failed, the job status will be set to
“failed” even if VM backup has been successful.
Important
Pre and post job scripts can be executed only on the machine where the Director is installed.

Data Transfer
In the Data Transfer section of the Options page, you can configure bandwidth throttling.

Bandwidth Throttling

Follow the steps below to regulate the speed of data transfer over the network for your tape backup job:

- 534 -
 1. For the Bandwidth throttling option, choose Enabled.
Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer to
“Bandwidth Throttling” on page 283 for details.
2. Click the Settings link that becomes available.
3. The Job Bandwidth Rules dialog box opens displaying you the list of available rules. You have the following
options:
l Create a new bandwidth rule for your tape backup job:
1. Click the Create New Rule button.
2. The New Bandwidth Rule dialog box opens. Refer to “Bandwidth Throttling” on page 283 for details
on creating a bandwidth rule.
3. Click Save.
l Activate an existing bandwidth rule for your job. Select the checkbox to the left of the necessary bandwidth
rule. To deactivate a bandwidth rule for your job, clear the corresponding checkbox.
l Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth Rule
dialog box that opens.
l Disable a bandwidth rule. Click the Disable link. The bandwidth rule will be disabled for all jobs.
l Remove a bandwidth rule. Click the Remove link and then click Delete to confirm your operation.

Completing Tape Backup Wizard

Click Finish or Finish & Run to complete the job creation.
Note
If you click Finish & Run, you will have to define the scope of your job. Refer to “Running Jobs on Demand” on page 97
for details.

- 535 -
Staging (Seeding) Initial Backup
Since initial backups are often large, the first backup job run can be slow and time-consuming when done over WAN,
and it can also put an undesirable load on the network when done over LAN. To speed up the initial backup and save
network bandwidth, you can perform a staged backup (seed backups): run the initial backup on a removable media
device (such as an external USB hard drive), transfer the media to a new location, and then run an incremental backup
to the new location.
To perform a staged backup, follow the steps below:
1. Create a new Backup Repository.
2. Create and run a new backup job.
3. After the job has completed, move the Backup Repository to a new location.
4. If required, edit the backup job and specify a schedule for the backup job. 

- 536 -
Deleting Backups
With NAKIVO Backup & Replication, you can permanently delete a backup (including all of its recovery points) if it is
available in a Backup Repository. Also, you can delete specific recovery points of a backup without affecting any of the
others.
Note
You can only delete a backup if you have deleted the corresponding backup job or edited the backup job so that it does
not include the backup’s source VM or a physical machine.
Refer to one of the following sections:
l Deleting a Single Backup
l Deleting Backups in Bulk
l Deleting Recovery Points
l Deleting a Single Recovery Point

l Bulk Recovery Points Deletion

Deleting a Single Backup

To delete a backup permanently, follow the steps below:
1. Click Settings in the main menu of the product.
2. Go to the Repositories tab and click a Backup Repository.
3. Click the backup you want to delete.
4. In the backup page, click Delete.
5. Click Delete in the dialog box that opens.
Note
For a forever-incremental Backup Repository, the space occupied by the backup will be marked as “free” and reused by
new data blocks on the next job runs, though the actual size of the Backup Repository may not change. To free up the
space occupied by the backup, you can reclaim free space.

- 537 -
Deleting Backups in Bulk
To permanently delete a number of backups that match particular criteria, follow the steps below:
1. Click Settings in the main menu.
2. Go to the Repositories tab and hover over a Backup Repository.
3. Click Manage and then click Delete backups in bulk.

The Bulk Delete Backups dialog box opens.

- 538 -
 4. Select one of the available options:
l All backups not belonging to any job
l All backups not belonging to any job and older than X <time_units>, where X is an integer and <time_
units> is either Days, Weeks, or Months
The dialog shows the number of backups to be deleted.
5. Click Next.
6. A list of backups/recovery points to be deleted opens. Click Delete.
Note
For a forever-incremental Backup Repository, the space occupied by the backup will be marked as “free” and reused by
new data blocks on the next job runs, though the actual size of the Backup Repository may not change. To free up
space occupied by the backup, you can reclaim free space.

Deleting Recovery Points

You can delete either a single recovery point, all corrupted recovery points, or all recovery points older than the
specified number of days.
Notes
1. If a backup is used by a VM/Amazon EC2/physical machine backup job, you cannot delete its last recovery point.
2. A recovery point cannot be deleted while the source VM/physical machine backup job is running.

Deleting a Single Recovery Point

1. Click Settings in the main menu.
2. Go to the Repositories tab.
3. Click a Backup Repository.
4. Click the backup where you want to delete a recovery point.
5. Hover over the recovery point you want to delete.
6. Click Delete.

- 539 -
 7. Click Delete Recovery Point in the message box that opens.
Note
For forever-incremental Backup Repository, the space occupied by the recovery point will be marked as “free” and
reused by new data blocks on the next job runs, though the actual size of the Backup Repository may not change. To
free up space occupied by the recovery point, you can reclaim free space.

Bulk Recovery Points Deletion

1. Click Settings in the main menu of the product.
2. Go to the Repositories tab.
3. Click a Backup Repository.
4. Click Manage.
5. Click Delete backups in bulk.
6. The Bulk Delete Backups dialog box opens. Select criteria for recovery points to be deleted:
l All recovery points older than X <time_units>, where X is an integer and <time_units> is either Days,
Weeks, or Months: When selected, the recovery points that are older than the specified time interval will
be deleted.
Note
The following deletion exclusions are applicable:
l For forever-incremental repositories: if all recovery points of a backup match the deletion criteria,
the latest recovery point – no matter whether it is corrupted or not – will not be deleted.
l For incremental-with-full backups repositories:
l Recovery points that are older than the end of the time interval, but have dependent
recovery points that are newer than the beginning of the time interval, will not be deleted.
l If all recovery points of a backup match the deletion criteria, the latest full recovery point – no
matter whether it is corrupted or not – will not be deleted.
l All corrupted recovery points: If selected, all recovery points that are corrupted will be deleted. For
incremental-with-full Backup Repositories, this will delete all recovery points that are dependent on
corrupted recovery points. The following deletion exclusions are applicable:

- 540 -
 l For forever-incremental repositories: if a backup is used by a backup job and all its recovery points
are corrupted, the latest recovery point will not be deleted.
l For incremental-with-full-backups repositories: if all recovery points of a backup are corrupted or
depend on a corrupted recovery point, and match the deletion criteria, the latest full recovery point
will not be deleted.
Note
This option is unavailable for Microsoft 365 backups.
7. The Bulk Delete Recovery Points dialog box opens displaying the list of recovery points to be deleted. Click
Delete to confirm the deletion of recovery points.

- 541 -
Recovery
During outage events that threaten business continuity, NAKIVO Backup & Replications offers multiple recovery options
allowing you to resume normal business operations swiftly. 
This section covers the following recovery topics:
l “Granular Recovery” on page 543
l “Full Recovery” on page 592
l “Planning Disaster Recovery” on page 639

- 542 -
Granular Recovery
The granular recovery technology allows you to instantly recover specific files and objects from image-based backups.
With this technology, you can easily recover corrupted or accidentally deleted files or objects without fully restoring a
VM first. With NAKIVO Backup & Replication you can recover files for VMware, Microsoft Hyper-V, and AWS virtual
environments. You can also recover Microsoft Exchange emails, and Microsoft Active Directory and Microsoft SQL
Server objects directly from compressed and deduplicated backups.
Before you start the recovery process, verify that:
l The target VM/instance/physical machine is powered on.
l The target VM/instance/physical machine has enough space. The required minimum of free space is equal to the
size of the recovered object + 1 GB.
l The target VM/instance/physical machine is accessible over the network.
For more details, refer to the corresponding articles below:
l “File Recovery” on page 544
l “Object Recovery for Microsoft Exchange” on page 557
l “Object Recovery for Microsoft Active Directory” on page 566
l “Importing Recovered Objects to Active Directory” on page 577
l “Object Recovery for Microsoft SQL Server” on page 578
l “Performing Universal Object Recovery” on page 586

- 543 -
File Recovery
With NAKIVO Backup & Replication, you can recover files or folders directly from compressed and deduplicated
backups. Refer to “Instant File Recovery to Source” on page 19 for mode information.
Note
File recovery is restricted to supported disk types and file systems.
Refer to the following topics to learn more:
l “Opening File Recovery Wizard” on page 545
l “File Recovery Wizard: Backup” on page 547
l “File Recovery Wizard: Recovery Server” on page 548
l “File Recovery Wizard: Files” on page 550
l “File Recovery Wizard: Options” on page 553

- 544 -
Opening File Recovery Wizard
You can start the recovery process either from the Dashboard, or from the Repositories tab in Settings  (for example, if
you no longer have a backup job, but still have the backup). Refer to the following sections for more details:
l Starting File Recovery from Dashboard
l Starting File Recovery from Backup Repository

Starting File Recovery from Dashboard

To start file recovery from the Dashboard, click Recover and then click Individual Files.

Starting File Recovery from Backup Repository

To start file recovery from a Backup Repository, do the following:

1. Go to the main menu of NAKIVO Backup & Replication and click Settings.
2. Go to the Repositories tab and hover over the Backup Repository containing the required backup.
3. Click the Recover button and then click Individual Files. The File Recovery Wizard opens.

- 545 -
- 546 -
File Recovery Wizard: Backup
On the Backup page of the wizard, select a backup using either a Backup Repository or Jobs & Groups view in the left
pane, and then select a recovery point in the right pane.

Click Next to go to the next page of the wizard.

- 547 -
File Recovery Wizard: Recovery Server
In this page of the wizard, choose one of the following recovery methods:
l Recovering Files to Server
l Downloading Files to Browser or Sending Files via Email

Recovering Files to Server

Please do the following to recover files to a server:

1. In the Recovery Method section, choose Recover to the following server.
2. The Recovery Server Settings section opens. Set the following options:
1. Recovery server: Choose the target server from the drop-down list.
Note
NAKIVO Backup & Replication will try to auto-detect the IP address automatically.
2. Server IP address: Enter the IP address of the recovery server if it is not detected by the application based
on the recovery server name.
3. Use custom SSH port: If necessary, enter an SSH port to be used for connecting to the recovery server.
The default value is 22.
4. Username: Enter a username with administrative privileges for the recovery server entered above. Refer to
“Feature Requirements” on page 162 for a full list of requirements for recovering files to server.
5. Password: Enter a user password.
3. Click the Test Connection button to test your credentials for the specified recovery server. If your credentials are
correct, a checkmark appears to the right of the button.
4. Click Next.

After NAKIVO Backup & Replication prepares a recovery point, the next page of the wizard opens.

Downloading Files to Browser or Sending Files via Email

To download files to your browser or send them via email, follow the steps below:

- 548 -
 1. In the Recovery Method section, choose Download to browser or send via email.
2. The Data Routing section opens. In the Proxy transporter list, the Do not use proxy transporter option is
chosen by default. You can also choose a proxy transporter from the list of available transporters.
3. Click Next.

Note
NAKIVO Backup & Replication will use a proxy transporter in the following cases:
l The transporter assigned to the backup repository is missing support for some file systems.
l The transporter assigned to the backup repository is missing iSCSI packages.
NAKIVO Backup & Replication starts preparing a recovery point for the recovery. After the recovery point is prepared
successfully, the next page of the wizard opens.

- 549 -
File Recovery Wizard: Files
On this page of the wizard, select files for recovery.
l Searching for Files and Folders
l Browsing Files and Folders
l Selecting Files and Folders for Recovery

Searching for Files and Folders

To search for a file or a folder, enter a part of or the entire name of the item into the Search box and press Enter.

Notes
1. NFS-mounted folders appear in the file tree as empty and the wizard does not recover the content of these
folders.
2. The search is performed starting from the point selected in the navigation pane. For example, if you select Hard
drive 1 > Disk 1 > Program Files, the search will be performed only inside the Program Files folder.

Browsing Files and Folders

You can browse the files and folders of a VM backup using the navigation pane:

- 550 -
If a VM backup contains Linux LVM volumes or Windows dynamic disks, the navigation pane will display these logical
groups in addition to all hard drives available in the VM backup. If a hard drive does not contain any partitions and
servers as a part of a Linux LVM volume or a Windows dynamic disk, this hard drive will appear as empty.
You can also quickly move between folders by using the navigation bar above the navigation pane.

Selecting Files and Folders for Recovery

After locating the item you want to recover, select the checkbox next to it.
The number of items selected for recovery is displayed at the bottom of the wizard page. You can also:
l Click show to view the list of all items selected for recovery.
l Click clear selection to clear the list of items selected for recovery.

- 551 -
Click Next to go to the next page of the wizard.

- 552 -
File Recovery Wizard: Options
On this page of the wizard, you can choose one of the following recovery types:
l Recovering Files via Recovery Server
l Recovering Files to the Original Location

l Recovering Files to a Custom Location

l Downloading Files to Browser or Sending Files via Email

l Downloading Files

l Forwarding Files via Email

Recovering Files via Recovery Server

If you have chosen the Recover to the following server recovery method, on the Recovery Server page of the wizard,
proceed as follows.
Warning
File recovery is not possible if a backup contains an incomplete set of disks that are a part of the spanned
volume/dynamic disks/LVM/RAID software or any other disk structures.

Recovering Files to the Original Location

To recover files to original location:

1. In the Recovery type list, choose Recover to original location.
2. The Overwrite behavior list opens. Please choose one of the following:
l Rename recovered item if such item exists: Choose the necessary server from the drop-down list.
l Skip recovered item if such item exists
l Overwrite the original item if such item exists
3. Click Recover to start recovering files to original location.

Recovering Files to a Custom Location

To recover files to a custom location:

1. In the Recovery type list, choose Recover to custom location.
2. A number of boxes open to let you set the options for a custom location. Do the following:

- 553 -
 a. In the Location type box, choose one of the following:
l Local folder on Recovery Server

l CIFS share

l NFS share

b. In the Location path / Path to share box, enter the path to be used for file recovery:
l A local path if you choose the Local folder on Recovery Server option.

l A path to a share on a remote server if you choose CIFS share / NFS share.
c. In the Overwrite behavior box, choose one of the following:
l Rename recovered item if such item exists

l Skip recovered item if such item exists

l Overwrite the original item if such item exists

d. In the Username and Password boxes, enter the credentials required for accessing the CIFS share location you
specified above.
Click Recover.

Downloading Files to Browser or Sending Files via Email

If you have chosen the Download to browser or send via email recovery method, on the Recovery Server page of the
wizard, proceed as follows.

Downloading Files

Please do the following to download files for recovery:

1. In the Recovery Type drop-down list, select Download.
2. Click Recover.

- 554 -
When the download has finished successfully, the archive with the recovered items appears in the browser downloads
folder.

Forwarding Files via Email

Note
To use this recovery type, your Email settings must be properly configured in the NAKIVO Backup & Replication
Configuration. Refer to “Email Notifications” on page 289 for details.
Please do the following to forward recovered files via Email:
1. In the Recovery type list, choose Forward via email.
2. A number of boxes open to set the options required for forwarding recovery files via email. Do the following:
1. In the To box, enter one or more email addresses to be primary recipients of the recovery files. Use
semicolons to separate multiple email addresses. The recipient’s email address is mandatory.
2. Optionally, in the CC box, you can enter one or more email addresses of secondary recipients.
3. Optionally, you can enter a subject in the Subject box.

- 555 -
4. Click Recover.

- 556 -
Object Recovery for Microsoft Exchange
The object recovery feature in NAKIVO Backup & Replication allows you to browse, search, and recover Microsoft
Exchange emails directly from compressed and deduplicated backups. Recovery can also be performed back to the
source or any other location including CIFS share. The Object Recovery for Microsoft Exchange feature is agentless,
works right out of the box, and does not require creating a special lab or running a special backup type. 
Refer to the following topics for more information:
l “Starting Object Recovery for Microsoft Exchange” on page 558
l “Object Recovery Wizard for Microsoft Exchange: Backup” on page 560
l “Object Recovery Wizard for Microsoft Exchange: Recovery Method” on page 561
l “Object Recovery Wizard for Microsoft Exchange: Objects” on page 562
l “Object Recovery Wizard for Microsoft Exchange: Options” on page 564

- 557 -
Starting Object Recovery for Microsoft Exchange
You can start the recovery process either from the Dashboard or from the Repositories tab in Settings (for example, if
you no longer have a backup job but still have the backup). 
Important
 The recovery process may result in additional load and memory usage on the target server. Therefore, make sure that
the server has enough memory.
Refer to the following sections to learn how to start the object recovery process for Microsoft Exchange:
l Starting Object Recovery for Microsoft Exchange from Dashboard
l Starting Object Recovery for Microsoft Exchange from Backup Repository

Starting Object Recovery for Microsoft Exchange from Dashboard 

To start object recovery for Microsoft Exchange from the Dashboard , click Recover and then click Microsoft Exchange
Objects.

Starting Object Recovery for Microsoft Exchange from Backup Repository

To start object recovery for Microsoft Exchange from a Backup Repository, do the following:
1. Click Settings in the main menu of the product.
2. Go to the Repositories tab and hover over the Backup Repository containing the required backup.

- 558 -
 3. Click the Recover button and then click Microsoft Exchange Objects.

The Object Recovery Wizard for Microsoft Exchange opens.

- 559 -
Object Recovery Wizard for Microsoft Exchange: Backup
On the Backups page of the wizard, select a backup using either a Backup Repository or Jobs & Groups view in the left
pane, and then select a recovery point in the right pane.

By default, NAKIVO Backup & Replication automatically searches the selected recovery point for Microsoft Exchange
databases (files with .edb extension) from which application objects can be recovered. This process can take a few
minutes. If you want to manually specify the location of the database file, deselect the Automatically locate
application databases option.
Click Next to go to the next page of the wizard.

- 560 -
Object Recovery Wizard for Microsoft Exchange: Recovery Method
On the Recovery Method page, select the Exchange Server you want to recover to and provide authentication
information:
l Recovery server: From the drop-down list, select the Exchange Server instance to which the objects must be
recovered. The original VM is selected by default. The selection functionality lets you switch views to display the
platform where the required VM resides: VMware vSphere, Microsoft Hyper-V, Amazon EC2, Nutanix AHV, or a
physical machine. You can also search for the VM by its name. You can skip this parameter altogether and enter
the VM’s IP address manually in the next field.
l Server IP address: Displays the automatically detected IP address of the server to which the objects must be
recovered. You'll need to enter the IP address of the recovery server manually if autodetection fails or if you did
not select anything in the previous parameter.
l Use custom SSH port (for Linux objects only): Put a checkmark and enter the port number to be used for SSH
connection. When the Use custom SSH port  checkbox is not checked, the default value is used for SSH
connections.
l Username: Enter the username to log in to the VM.
l Password: Enter the password to log in to the VM.
l Test Connection: Click this button to verify the credentials. You won’t be able to proceed until after the
connection has been successfully established.
l Click Next to proceed to the next step.

- 561 -
Object Recovery Wizard for Microsoft Exchange: Objects
On the Objects page of the wizard, select Microsoft Exchange objects for recovery. Proceed as described in the following
sections:
l Searching for Microsoft Exchange Objects
l Browsing Microsoft Exchange Objects
l Viewing Microsoft Exchange Objects
l Selecting Microsoft Exchange Objects to Recover

Searching for Microsoft Exchange Objects

NAKIVO Backup & Replication allows you to search for emails. The search functionality, however, has the following
limitations:
l The product can search for emails only by email subject or email body
l If text formatting (such as “bold text”) is applied to a keyword that is searched for, the search may not find the
keyword due to formatting conversion issues.
l The product does not create or maintain an index of the Exchange database contents. The search is performed on
the fly and can take a long time to complete.
To speed up the search, perform the search within a particular folder, rather than in a mailbox.
To search for an email by its subject or body, type a word in the Search field and press Enter.

The search is performed starting from the point selected in the left (Navigation) pane. For example, if you have selected
Mailbox Database > John Smith, the search will be performed only inside the John Smith mailbox.

Browsing Microsoft Exchange Objects

NAKIVO Backup & Replication scans the selected recovery point for Microsoft Exchange databases (files with “.edb”
extension) and displays the list of found databases in the left pane.
Not all of the found database files contain Microsoft Exchange objects that can be recovered by the product. To browse
Microsoft Exchange objects, expand the appropriate database in the left pane.

- 562 -
Viewing Microsoft Exchange Objects

To view a Microsoft Exchange object such as an email, click the object. Object contents will be displayed.

Selecting Microsoft Exchange Objects to Recover

In the right pane, select checkboxes next to files and folders you want to recover. The number of items selected for
recovery is displayed at the bottom of the wizard page. You can also:
l Click show to view the list of all items selected for recovery.
l Click clear selection to clear the list of items selected for recovery.
l Click hide to hide the list of items selected for recovery.
After selecting objects for recovery, click Next to go to the next page of the wizard.

- 563 -
Object Recovery Wizard for Microsoft Exchange: Options
On the Options page, specify the location for recovered objects and define overwriting options and naming
conventions.
l Recovering to the Original Location
l Recovering to a Custom Location
l Exporting to a Custom Location
l Overwriting Behavior

Recovering to the Original Location

In the Recovery type drop-down list, select Recover to original location to recover the objects to their original location
on the recovery VM.

Recovering to a Custom Location

In the Recovery type drop-down list, select Recover to custom location to recover the objects to a custom location on
the VM. You can select the recovery location by specifying it in the Local path field or by browsing to it.

Exporting to a Custom Location

In the Recovery type drop-down list, you can choose Export to export Microsoft Exchange objects to a CIFS share. In
this case, you’ll need to provide the path to the share and credentials.

- 564 -
Overwriting Behavior

Specify the naming convention for the recovered folders by choosing one of the following options from the Overwrite
behavior drop-down list:
l Rename recovered item if such an item exists
l Skip recovered item if such an item exists
l Overwrite the original item if such an item exists

Click Recover to proceed with the recovery process. The Finish page is displayed. You cannot return to the previous
pages of the wizard at this point, however, you can check the progress of the job execution by clicking the Activities
link.

- 565 -
Object Recovery for Microsoft Active Directory
The instant object recovery feature allows you to browse, search and recover Microsoft Active Directory objects directly
from compressed and deduplicated backups. This feature is agentless, works right out of the box, and does not require
you to create a special lab or run a special type of backup. Microsoft Active Directory objects can be recovered in .ldif
format and then be imported back to the Active Directory Server. 
Refer to the following topics for more information:
l “Starting Object Recovery for Microsoft Active Directory” on page 567
l “Object Recovery Wizard for Microsoft AD Server: Backup” on page 569
l “Object Recovery Wizard for Microsoft AD Server: Recovery Server” on page 570
l “Object Recovery Wizard for Microsoft AD Server: Objects” on page 571
l “Object Recovery Wizard for Microsoft AD Server: Options” on page 574

- 566 -
Starting Object Recovery for Microsoft Active Directory
You can start the recovery process either from the Dashboard, or from the Repositories tab in the Settings (for
example, if you no longer have a backup job, but still have the backup). Refer to the following sections for more details:
l Starting Active Directory Object Recovery from Dashboard
l Starting Active Directory Object Recovery from a Backup Repository

Starting Active Directory Object Recovery from Dashboard

To start Active Directory Object Recovery from the Dashboard, click Recover and then choose Microsoft
Active Directory objects.

Starting Active Directory Object Recovery from a Backup Repository

To start Active Directory Object Recovery from a Backup Repository, do the following:

1. Go to the main menu of the product and click Settings.
2. Go to the Repositories tab and hover over the Backup Repository containing the required backup.

- 567 -
 3. Click the Recover button and then click Microsoft Active Directory objects.

The Object Recovery Job Wizard for Microsoft AD Server opens.

- 568 -
Object Recovery Wizard for Microsoft AD Server: Backup
On the Backup page of the wizard, select a backup of a VM with the Microsoft Active Directory server in the left pane
and then select a recovery point in the right pane. You can choose a backup from either a Backup Repository or jobs
and groups you've created.

By default, NAKIVO Backup & Replication automatically searches the selected recovery point for the Microsoft Active
Directory database from which application objects can be recovered. This process can take a few minutes. If you want
to manually specify the location of the database file, deselect the Automatically locate application databases
checkbox.
Click Next to go to the next page of the wizard.

- 569 -
Object Recovery Wizard for Microsoft AD Server: Recovery Server
On the Recovery Server page of the wizard, set up a Microsoft Active Directory server to which objects will be
recovered.
Important
l The ISCSI Initiator service must be running on the recovery server.
l The vc_redist.x86.exe (v.2015) file must be installed on the recovery server. Refer to the Microsoft article
for installation details. 
Set up a Microsoft Active Directory server the following way:
l In the Recovery Server drop-down list, select a recovery server name.
l In the Server IP address box, enter the IP address of the recovery server. This is necessary if the application has
not detected the IP address based on the recovery server name.
l In the Username box, enter the name of a user with administrative privileges for the recovery server.
l In the Password box, enter a user password.
l Click the Test Connection button to test your credentials for the specified recovery server. If your credentials are
correct, a checkmark appears to the right of the button.
l Create snapshot before recovery: When selected, a snapshot of the VM will be taken if recovery fails, and the
VM will be reverted to this snapshot. 
l Click Next to go to the next page of the wizard.

- 570 -
Object Recovery Wizard for Microsoft AD Server: Objects
On the Objects page of the wizard, select Active Directory objects you want to recover. 
l Searching for Active Directory Objects
l Browsing Active Directory Objects
l Viewing Active Directory Objects
l Selecting Active Directory Objects to Recover

Searching for Active Directory Objects

NAKIVO Backup & Replication allows you to search Active Directory objects by name. To find an object by its name,
enter a word in the Search box and press Enter

The search is performed starting from the point selected in the left (navigation) pane. For example, if you have selected
the Users group, the search will only be performed inside the Users group.

Browsing Active Directory Objects

NAKIVO Backup & Replication scans the selected recovery point for Active Directory databases (files with “.edb”
extension) and displays the list of identified databases in the left (Navigation) pane. To browse Microsoft Active
Directory objects, simply expand the appropriate database in the left pane. You can also browse the tree by using the
scroll bar.

- 571 -
Viewing Active Directory Objects

To view a Microsoft Active Directory object, click the object. The object contents will be displayed.  Use the close
buttons to close the item.

- 572 -
Selecting Active Directory Objects to Recover

In the Contents pane to the right, select a checkbox next to the items you want to recover. The number of items
selected for recovery is displayed at the bottom of the wizard page. You can also:
l Click show to view the list of all items selected for recovery.
l Click clear selection to clear the list of items selected for recovery.
l Click hide to hide the list of items selected for recovery.

When ready with selecting Microsoft Active Directory objects for recovery, click Next to go to the next page of the
wizard

- 573 -
Object Recovery Wizard for Microsoft AD Server: Options
On the Options page of the wizard, you can set up the following options for your object recovery job:
l Recovering Objects to the Original Location
l Exporting Active Directory Objects

Recovering Objects to the Original Location

Follow the steps below to recover objects of your Microsoft Active Directory server to the original location:
1. In the Recovery typelist, select Recover to original location.
2. If you have selected multiple objects or container(s) that include one or more “user” objects, the Recover of user
object list becomes available. Select either of the following options:
l User will be disabled: If this option is selected, NAKIVO Backup & Replication disables all recovered “user”
objects and the corresponding user accounts are disabled after importing these objects to Active
Directory.
l User must change password at next log on: If this option is selected, NAKIVO Backup & Replication
generates a new password for each recovered “user” object. The passwords.txt file is added to the ZIP
archive with recovered objects, and it contains the new passwords. After importing the “user” objects to
Active Directory, corresponding users are forced to change the password on the next log on.

3. In the Overwrite behavior list, select what you wish to do if the recovered item conflicts with an existing one:
l Rename recovered item if such item exists
l Skip recovered item if such item exists
l Overwrite the original item if such item exists
4. If you have chosen to recover a full database (ntds.dit file) on the Recovery Server pageput a checkmark in
theStop Microsoft Active Directory instance before recovery checkbox to stop the instance before the recovery

- 574 -
 process begins.This option is recommended for the safe recovery of Active Directory objects.

5. Click Recover.
Notes
l Some attributes may be skipped for the selected object(s) depending on the Active Directory system settings.
l In case the recovery process fails, theVM will be reverted to the snapshot taken on the Recovery Server page of
the wizard

Exporting Active Directory Objects

Follow the steps below to export recovered objects of your Microsoft Active Directory server to a custom location:
1. In the Recovery type list, select Export. A number of options become available for setting up a custom location.
2. In the Export location list, select the appropriate location type:
l Local folder on Recovery Server: If this option is selected, you will have to enter the path to a local folder
on the recovery server in the Local path field.

l CIFS share: If this option is selected, enter the following values:

1. Path to the share
2. Username

- 575 -
 3. Password

3. In the Overwrite behavior list, select what needs to be done if the recovered item conflicts with an existing item.
Refer to the section above for an explanation.
4. Click Recover.
The Finish page of the wizard opens informing you that Microsoft Active Directory object recovery has started. To view
the object recovery progress, go to the Activities page.
To close the wizard, click Close.

- 576 -
Importing Recovered Objects to Active Directory
Refer to the sections below for information on how to import recovered objects in Active Directory.
l Importing Non-User Objects
l Importing User Objects

Importing Non-User Objects

If Active Directory objects or containers that you have recovered do not contain “User” objects, follow the steps below
to import the objects in Active Directory:
1. On the Active Directory machine, run command line as an administrator.
2. Run the following command: ldifde -i -k -f filename -j logfolder, where “file-
name.ldif” is the path to the recovered ldif file, and “logfolder” is the path to the folder where import
logs will be saved.

Importing User Objects

If you have recovered one or more “User” objects or if you have recovered containers that include one or more “User”
objects, follow the steps below to import the objects in Active Directory:
1. On the Active Directory machine, run command line as an administrator.
2. Enable a secure LDAP connection on the Active Directory machine:
a. Log on to the server and open the Server Manager tool.
b. Add the Active Directory Certificate Services role. On the Role services page of the Add Roles and Features
wizard, select a Certification Authority.
c. When configuring the Active Directory Certificate service on the destination server, use proper credentials
to configure the service, choose the Enterprise CA setup type, and choose a Root CA for CA Type.
d. Follow the rest of wizard instructions to complete adding the Active Directory Certificate Services role.
3. Run the following command: ldifde -i -t 636 -f filename.ldif -k -j logfolder, where
“filename.ldif” is the path to the recovered ldif file, and “logfolder” is the path to the folder where
import logs will be saved.
4. Edit the group policy by adding imported users. After importing one or more users, you may need to verify pass-
word options via user logon.

- 577 -
Object Recovery for Microsoft SQL Server
The instant object recovery feature in NAKIVO Backup & Replication allows you to browse, search, and recover
Microsoft SQL Server objects directly from compressed and deduplicated backups. This out-of-the-box feature is
agentless, and it does not require creating a special lab or running a special backup type. Microsoft SQL Server objects
can be recovered to a source or another VM.
Refer to the following topics for more information:
l “Starting Object Recovery for Microsoft SQL Server” on page 579
l “Object Recovery Wizard for Microsoft SQL Server: Backup” on page 581
l “Object Recovery Wizard for Microsoft SQL Server: Recovery Server” on page 582
l “Object Recovery Wizard for Microsoft SQL Server: Objects” on page 583
l “ Object Recovery Wizard for Microsoft SQL Server: Options” on page 584

- 578 -
Starting Object Recovery for Microsoft SQL Server
You can start the recovery process either from the Dashboard or from the Repositories tab in the Settings (for example,
if you no longer have a backup job but still have the backup). Refer to the following sections for more details:
l Starting SQL Server Object Recovery from Dashboard
l Starting SQL Server Object Recovery from a Backup Repository

Starting SQL Server Object Recovery from Dashboard

To start Microsoft SQL Server object recovery from the Dashboard, сlick Recover and choose Microsoft SQL Server
objects.

Starting SQL Server Object Recovery from Backup Repository

To start SQL Server object recovery from a Backup Repository:

1. Click Settings in the main menu of the product.
2. Go to the Repositories tab and hover the cursor over the backup repository containing the required backup.

- 579 -
 3. Click the Recover button and then click Microsoft SQL Server objects.

The New Object Recovery Wizard for Microsoft SQL Server opens.

- 580 -
Object Recovery Wizard for Microsoft SQL Server: Backup
On the Backup page of the wizard: 
1. Select a backup of a VM with Microsoft SQL in the left pane using either the Backup Repositories or Jobs &
Groups view.
2. Select a recovery point in the right pane.

3. Click Next.
By default, NAKIVO Backup & Replication automatically searches the selected recovery point for Microsoft SQL database
from which objects can be recovered. This process can take a few minutes. If you want to manually specify the location
of the database file, deselect the Automatically locate application databases option.

- 581 -
Object Recovery Wizard for Microsoft SQL Server: Recovery Server
To set up a recovery server for Microsoft SQL Server objects:
1. The Recovery Server Settings section opens. Please enter the following values:
a. Recovery server: Choose the target server from the drop-down list.
Note
NAKIVO Backup & Replication will try to auto-detect the IP address automatically.
b. Server IP address: Enter the IP address of the recovery server if it is not detected by the application based
on the recovery server name.
c. Use custom SSH port: If necessary, enter an SSH port to be used for connecting to the recovery server. The
default value is 22
d. Username: Enter a user name with administrative privileges for the recovery server entered above. Refer
to “Requirements for Microsoft SQL Server Object Recovery” on page 167 for a full list of requirements for
recovering files to server.
e. Password: Enter a user password.
f. SQL instance: Select a target SQL instance.
2. Click the Test Connection button to test your credentials for the specified recovery server. If your credentials are
correct, a checkmark appears to the right of the button.
3. Click Next.

- 582 -
Object Recovery Wizard for Microsoft SQL Server: Objects
On the Objects page of the wizard, select objects for recovery. You can select either entire databases or individual
objects for recovery.
1. Select the database in the left pane.
2. Select the objects in the right pane. If you want to restore an entire database, select all objects in this pane.
3. Alternatively, you can look for objects using the Search bar.
4. When you are done, click Next.

- 583 -
Object Recovery Wizard for Microsoft SQL Server: Options
On the Options page of the wizard, set the options for the recovery job.
l Recovery Scope
l Recovery Settings
l Overwrite Behavior

Recovery Scope

Set the recovery scope by selecting either Recover schema and data or Recover only schema.

Recovery Settings

Set up the recovery type and overwrite behavior.

Recovery Type

l Recover to original location: Recover objects to the same server and SQL instance where they were originally
located.
l Recover to custom location: Recover objects to a different instance.
l Export : Export objects as files to a specified location.
l SQL instance: Select the target SQL instance.
l Target database: Select the target database of the selected instance.
l Local folder on Recovery Server: Specify a path to save objects.
l CIFS share: Specify a remote CIFS (Windows) file share and your credentials for it (or select them from the

- 584 -
 Manage credentials list).

If you are using a domain name, enter it in the following format: domain\username

Overwrite Behavior

Select what to do if the recovered item conflicts with an existing one:

l Rename recovered item if such item exists
l Skip recovered item if such item exists
l Overwrite the original item if such item exists

Click Recover to start the object recovery process. The Finish page opens.

- 585 -
Performing Universal Object Recovery
With Universal Object Recovery you can choose a disk from a VM recovery point and mount it to a target machine. This
will allow you to recover backup data located on the mounted disk. Before creating a Universal Object Recovery job,
make sure the System Requirements for recovering files to a server are met.
Please refer to the following topics for creating a Universal Object Recovery job:
l “Opening Universal Object Recovery Wizard” on page 587
l “Universal Object Recovery Wizard: Backup” on page 589
l “Universal Object Recovery Wizard: Disks” on page 590
l “Universal Object Recovery Wizard: Options” on page 591

- 586 -
Opening Universal Object Recovery Wizard
You can start the recovery process either from the Dashboard or from the Repositories page in Settings (for example, if
you no longer have a backup job but still have the backup). Refer to the following sections for more details:
l Starting Universal Object Recovery from Dashboard
l Starting Universal Object Recovery from a Backup Repository

Starting Universal Object Recovery from Dashboard

To start Universal object recovery from the Dashboard, click Recover and choose Universal Object Recovery.

Starting Universal Object Recovery from a Backup Repository

To start Universal object recovery from a Backup Repository:

1. Click Settings in the main menu of NAKIVO Backup & Replication.
2. Go to the Repositories tab and hover the cursor over the Backup Repository containing the required backup.

- 587 -
 3. Click the Recover button and then click Universal Object Recovery.

The new Universal Recovery Job Wizard opens.

- 588 -
Universal Object Recovery Wizard: Backup
On the Backup page of the wizard, do the following:
1. Optionally, you can filter the items tree by entering a string into the Search box. You can enter a part of or the
entire name of the item.
2. Choose either of the following item views:
l Backup Repositories: When chosen, the Backup Repositories tree opens in the left pane. Proceed as
follows:
a. Expand a repository by clicking the icon to the left of the repository.
b. Choose a backup in the left pane and then choose a recovery point in the right pane.
l Jobs & Groups: When chosen, the jobs' tree opens in the left pane. Proceed as follows:
a. Expand a job by clicking the icon to the left of the job.
b. Choose a backup in the left pane and then choose a recovery point in the right pane.
3. Click Next to go to the next page of the wizard.

- 589 -
Universal Object Recovery Wizard: Disks
On the Disks page of the wizard, choose one or more disks from the list of disks. Click Next to go to the next page of the
wizard.

- 590 -
Universal Object Recovery Wizard: Options
In the Options page of the wizard:
1. Specify mount location options:
l Mount location: Choose the mount location from the drop-down list.
l Location IP address: Enter the IP address of the server to which the disks will be mounted if it is not
detected by the application based on the Mount location value. Here you can enter an IP address of
any virtual or physical machine.
Use custom SSH port: To recover to a Linux server, select this option to enter a custom SSH port to be
used for connecting to the recovery server. The default value is 22.
l Username: Enter a username with administrative privileges for the recovery server specified above.
l Password: Enter a user password.
2. Click the Test Connection button to test your credentials for the specified recovery server. If your credentials are
correct, a checkmark appears to the right of the button.
3. Click Mount to confirm mounting your disks to the selected recovery server.

The Universal Object Recovery is started and the Finish page of the wizard opens.
4. Click the Activities link to go to the Activities page if you want to view the progress of the Universal Object
Recovery.
5. Click Close to close the Universal Object Recovery Wizard. Upon successful Universal Object Recovery, the disks
are mounted to the recovery server.

- 591 -
Full Recovery
With NAKIVO Backup & Replication, you can recover an entire VM in case of hardware or VM failure. The VM is
recovered in the same state as it was during the backup and it will appear on the host selected for recovery. You can
also perform cross-platform recovery that allows you to export virtual disks from VM backups to different formats for
further manual recovery of the VMs in different virtual environments. 
The Flash VM Boot feature allows you to recover an entire VM from the backup in seconds. This feature makes it
possible to boot a VM directly from a compressed and deduplicated backup without recovering the entire VM. The VM
can be started in a few seconds, and it can run directly from the backup.
For more details, refer to the corresponding articles below:
l “Performing Flash VM Boot Recovery” on page 606
l “VMware VM Recovery” on page 593
l “Recovery From Tape” on page 630
l “Performing Cross-Platform Recovery” on page 623

- 592 -
VMware VM Recovery
With NAKIVO Backup & Replication, you can recover full VMs from backups. Multiple VMs can be recovered within a
single recovery job—the system allows you to select separate resources (containers, datastores, networks, and folders)
for different VMs or to restore all VMs using the same setup. When you run VM recovery, a new VM is created; the
source VM is not reverted to a previous state or replaced with the new VM.
Refer to the following topics for more information:
l “Starting VMware VM Recovery” on page 594
l “Recovery Job Wizard for VMware: Backups” on page 595
l “Recovery Job Wizard for VMware: Destination” on page 596
l “Recovery Job Wizard for VMware: Options” on page 599

- 593 -
Starting VMware VM Recovery
To recover entire VMware VMs from backups, do one of the following:
l Start recovery from the Dashboard by clicking Recover and then clicking VM recovery from backup

l Open the NewRecovery Job Wizard from the Repositories tab by following the steps below:
a. Go to the main menu of NAKIVO Backup & Replication and click Settings.
b. Go to the Repositories tab and hover over a Backup Repository containing the necessary backup.
c. Click Recover and then click VM recovery from backup. 

The New Recovery Job Wizard for VMware vSphere opens.

- 594 -
Recovery Job Wizard for VMware: Backups
On the Backups page of the wizard, proceed as follows:
1. Select one of the views:
l Jobs & Groups: When selected, perform the following:
1. Select one or more VM backups in the left pane.
2. Select a recovery point for each backup in the right pane.
l Backup Repositories: When selected, perform the following:
1. Select one or more Backup Repositories in the left pane.
2. Select a recovery point for each backup in the right pane.

2. Click Next to go to the next page.

- 595 -
Recovery Job Wizard for VMware: Destination
On the Destination page of the wizard, select a location for the recovered VMs. Proceed as described in these sections:
l “Setting the Same Host, Datastore, and Network for All Recovered VMs” below
l “Setting Original Location for All Recovered VMs” below
l “Setting the Default Destination for Recovered VMs” on the next page
l “Setting Different Options for Recovered VMs” on the next page

Setting the Same Host, Datastore, and Network for All Recovered VMs

To recover all VMs to the same container/folder and datastore, and to connect all recovered VMs to the same
networks, follow the steps below:
1. Choose a cluster, host, or resource pool from the Container drop-down list.
2. Choose a datastore from the Datastore drop-down list.
3. Choose a network from the Network drop-down list.
4. Optionally, you can choose a folder if there is one in the container.

Setting Original Location for All Recovered VMs

To recover VMs to their original location, select Original container from the Container drop-down list and click Next.

Important
If the location of the VMs is unknown or unavailable, you will have to configure it manually via Advanced options. 

- 596 -
Setting the Default Destination for Recovered VMs

If you have chosen a host, cluster, folder, or a Backup Repository as a source for your recovery job on the
Backups page, you can set the default container, datastore, and VM folder for the recovered VMs. To do this, follow the
steps below:
1. Click Advanced options and then click on the name of the chosen host, cluster, folder, or a resource pool.
2. Choose a Default container.
3. If you have chosen the backup job on the Source page, you can choose a Default Network.
4. Optionally, you can also choose a Default VM folder.

Setting Different Options for Recovered VMs

To specify different options for recovered VMs, follow the steps below:
1. Click Advanced options.
2. Click on the backup to expand its recovery options.
3. Choose a target location, target datastore, and target network for each VM.
4. To get additional information about the source and target VMs within a backup, click on its name.
5. Click Next to go to the next page of the wizard.

- 597 -
- 598 -
Recovery Job Wizard for VMware: Options
On the Options page of the wizard, set the recovery job options. 
l “Job Options” below
l “Recovery Options” on the next page
l “Pre and Post Actions” on page 601
l “Setting a Pre-Job Script” on page 601
l “Setting a Post-Job Script” on page 602
l “Email Notifications” on page 602
l “Data Transfer” on page 603
l “Transport Mode” on page 603
l “Transporters” on page 603
l “Transporter Load” on page 604
l “Bandwidth Throttling” on page 604
l “Completing the New Recovery Job Wizard for VMware” on page 605

Job Options

Specify the general options as follows:

1. Job name: Specify a name for the recovery job.
2. Network acceleration: With network acceleration enabled, NAKIVO Backup & Replication uses compression and
traffic reduction techniques to speed up data transfer. Enable this option if you plan to recover VMs over WAN or
slow LAN links.
3. Encryption: With encryption enabled, VM data is protected with AES 256 encryption while traveling over the
network. Data encryption increases the backup time and CPU load on machines running Transporters. Select this
option when recovering over WAN without a VPN connection.

- 599 -
Recovery Options

Specify the recovery options as follows:

1. Recovery mode: Choose one of the following:
l Synthetic: With this recovery mode, the VMs are recovered with the environmental dependencies (such as
CPU affinity) removed. Select this option when recovering VMs to a new location.
l Production: With this recovery mode, environment dependencies are preserved on recovered VMs. Make
sure the location to which the VMs are recovered does not contain the original VMs, otherwise, UUID and
MAC address conflicts may occur.
2. Recovered VM names: Choose one of the following:
l Append "-recovered" in the end: Source VM names are used for recovered VM names and “-recoverd” is
added after the name of the recovered VMs.
l Leave recovered VM names as is: Recovered VM names are identical to the source VM names.
l Enter custom recovered VM names: You can enter custom names for recovered VMs.
3. VM disks: Choose one of the following:
l Respect original VM disk type: When specified, disks that respect the original VM disk type are created on
target VMs. Select this option to recover VMs to their original location.
l Create only thin disks on target VMs: When specified, only thin disks are created on target VMs. Use this
option to save space on the target datastore.
4. VM MAC addresses: Choose one of the following:

- 600 -
 l Do not generate new MAC addresses: When this option is selected, the recovered VM has the same MAC
address as the source VM.
l Generate new MAC addresses: When this option is selected, a new MAC address is generated for the
recovered VM.
5. VM power on: When the Power on recovered VMs option is selected, the recovered VMs are powered on.

Pre and Post Actions

NAKIVO Backup & Replication allows you to run a script before VM recovery begins (a pre-job script) and after the
recovery of all VMs in the job has completed (a post-job script). The scripts can only be executed on the machine on
which the Director is installed. 

Setting a Pre-Job Script

To run a script before the product begins recovering VMs, do the following:
1. Place a script file on the machine on which the Director is installed.
2. Select the Run local pre job script option and click the settings link.
3. Specify the following parameters in the dialog box that opens:
l Script path: Specify a local path to the script on the machine on which the Director is installed. A script
interpreter should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh

- 601 -
 l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, VM backup is started only after the script is
completed.
l Do not wait for the script to finish: With this option selected, the product runs the script and
starts backing up VMs at the same time.
l Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: With this option selected, the job performs VM backup even if
the script has failed.
l Fail the job on script failure: With this option selected, if the script fails, the job is failed and VM
backup is not performed.

Setting a Post-Job Script

To run a script after the product has finished backing up all VMs, do the following:
1. Place a script file on the machine on which the Director is installed.
2. Select the Run local post job script option and click the settings link.
3. Specify the following parameters in the dialog box that opens:
l Script path: Specify a local path to the script on the machine on which the Director is installed. A script
interpreter should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, the job is in the “running” state until the
script is completed.
l Do not wait for the script to finish: With this option selected, the job is completed even if the
script execution is still in progress.
l Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: With this option selected, script failure does not influence the
status of the job.
l Fail the job on script failure: With this option selected, if the script fails, the job status is set to
“failed” even if VM backup is successful.

Email Notifications

NAKIVO Backup & Replication can send email notifications about job completion status to specified recipients. This
feature complements global notifications and allows you to configure notifications on a per-job level.
To enable this option, make sure that Email settings are configured.
To send email notifications, do the following:
1. In the Pre and Post Actions section, select the Send job run reports to.
2. Specify one or more email addresses in the text box. Use semicolons to separate multiple email addresses.

- 602 -
Data Transfer

In the Data Transfer section, choose a transport mode for writing VM data, select which Transporter to be used for
reading data from the source VM, and set bandwidth throttling.

Transport Mode

NAKIVO Backup & Replication provides the following transport modes for writing VM data:
l Hot Add only: NAKIVO Backup & Replication can write data directly to the datastore, bypassing the network,
which can significantly improve job performance. This is achieved with the help of VMware's Hot Add technology.
In order for the Hot Add feature to work, the target Transporter (the one that will be writing data ) should run on
a host that has access to the target datastore(s).
l LAN only: Data will be written over LAN.
l Automatic: When this option is chosen, Hot Add mode is used where possible. If the product cannot use Hot
Add, LAN mode is used.

Transporters

By default, the product automatically determines which Transporter should be used to read data from the source VM.
However, you can manually specify which Transporters should be used for the job:
l Automatic selection: The product automatically determines the Transporters that are closest to the source and
target hosts.
l Manual - configured for all VMs: Select this option to manually specify a single source and a single target

- 603 -
 Transporter to be used for data transfer by the job.
l Manual - configured per host: Select this option to manually specify Transporters for all source and target hosts.

Transporter Load

You can limit the maximum number of transporter tasks used by the job. By default, this number is set to 3 concurrent
tasks.
To change the default number of tasks, do the following:
1. In the Data Transfer section, select the Limit transporter load to checkbox.
2. Specify the number of concurrent tasks in the corresponding box.

Bandwidth Throttling

Follow the steps below to set the speed of data transfer over the network for your recovery job:
1. For the Bandwidth throttling option, choose Enabled.
Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer
to Bandwidth Throttling for details.
2. Click the Settings link that becomes available.
3. The Job Bandwidth Rules dialog box opens displaying the list of available rules. You have the following options:
l Create a new bandwidth rule for your recovery job:
1. Click the Create New Rule button.
2. The New Bandwidth Rule dialog box opens. Refer to the “Bandwidth Throttling” on page 283 topic
for details on creating a bandwidth rule.
3. Click Save.
l Activate an existing bandwidth rule for your job: Select the checkbox to the left of the required
bandwidth rule. To deactivate a bandwidth rule for your job, deselect the corresponding checkbox.
l Edit a bandwidth rule: Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth
Rule dialog box that opens.
l Disable a bandwidth rule: Click the Disable link. The bandwidth rule is disabled for all jobs.

- 604 -
 l Remove a bandwidth rule: Click the Remove link and then click Delete to confirm your operation.

Completing the New Recovery Job Wizard for VMware

Click Finish or Finish & Run to complete the job creation.

Note
If you click Finish & Run, you will have to define the scope of your job. Refer to “Running Jobs on Demand” on page 97
for details.

- 605 -
Performing Flash VM Boot Recovery
The Flash VM Boot feature allows you to run (boot) VMware and Hyper-V VMs directly from compressed and
deduplicated VM backups, without recovering entire VMs first. When you boot a VM from a backup, NAKIVO Backup &
Replication creates a new VM on the target server. 

When the VMware VM is created, NAKIVO Backup & Replication takes a snapshot of the VM: this way all changes that
occur to the VM are temporarily stored in the snapshot and discarded when you stop the job. When the Hyper-V VM is
created, the application temporarily stores the changes to the VM in a disk-based write cache in the Backup Repository;
changes are discarded when the job is stopped. For more information, refer to the following topics:
l “Creating VMware Flash VM Boot Jobs” on page 607
l “Migrating Recovered VMs Using Flash Boot” on page 622

- 606 -
Creating VMware Flash VM Boot Jobs
To create a VMware Flash VM Boot job, do one of the following:
l Open the Flash VM Boot wizard from the Dashboard by clicking Recover and then clicking Flash VM Boot.

l Open the Flash VM Boot wizard from the Repositories tab in Settings by following the steps below:
1. Go to the main menu and click Settings.
2. Go to the Repositories tab and select a Backup Repository.
3. In the Backup Repository title, click Recover and then click Flash VM Boot.

The New Flash Boot Job Wizard opens. 

l “VMware Flash VM Boot Job Wizard: Backups” on page 609
l “VMware Flash VM Boot Job Wizard: Destination” on page 610

- 607 -
l “VMware Flash VM Boot Job Wizard: Schedule” on page 612
l “VMware Flash VM Boot Job Wizard: Options” on page 616

- 608 -
VMware Flash VM Boot Job Wizard: Backups

On the Backups page of the wizard, select backups for recovery by taking the following actions:
1. Select one of the views:
l Jobs & Groups: Select one or more VM backups in the left pane and then select a recovery point for each
backup in the right pane.
l Backup Repositories: Select one or more Backup Repositories in the left pane and then select a recovery
point for each backup in the right pane.

2. Click Next to go to the next page of the wizard.

- 609 -
VMware Flash VM Boot Job Wizard: Destination

On the Destination page, select a destination for the recovered VMs.

Important
Due to vSphere storage limitations, only 256 VM disks can be flash-booted per host.
Proceed as described in these sections:
l “Setting the Same Host, Datastore, and Network for all VMs” below
l “Setting Different Options for Recovered VMs” below

Setting the Same Host, Datastore, and Network for all VMs

To run all VMs on the same host (cluster, or resource pool), datastore and VM folder (optional), and to connect all
recovered VMs to the same network, choose a target container, datastore, VM folder and network from the
appropriate drop-down lists:

If you choose the Connect to temporary isolated network option from the Network drop-down list, NAKIVO Backup &
Replication will create a new vSwitch and a new network on all hosts where VMs will be recovered. Recovered VMs will
be connected to the newly created network.

Setting Different Options for Recovered VMs

To specify different options for VMs, follow the steps below:

1. Click Advanced options.
2. Choose a target container, target datastore, and target network for each individual VM. 

- 610 -
 If you choose the Connect to temporary isolated network option for a NIC, NAKIVO Backup & Replication will
create a new vSwitch and a new network on the host where the VM will be recovered. The recovered VM will be
connected to the network. 
3. Click Next.

- 611 -
VMware Flash VM Boot Job Wizard: Schedule

On the Schedule page of the wizard, select to run the recovery job manually or schedule the job to run on a regular
basis. Proceed as described in the sections below:
l “Disabling Scheduled Job Execution” below
l “Daily Job Execution” below
l “Monthly or Yearly Job Execution” on the next page
l “Periodic Job Execution” on page 614
l “Chained Job” on page 614
l “Additional Schedule” on page 615

Disabling Scheduled Job Execution

If you want to start the job manually only (without scheduling), select the Do not schedule, run on demand checkbox:

Daily Job Execution

To run a job once a day, choose Run daily/weekly from the schedule drop-down list:
l Choose a time zone to be used for the job start and end times from the time zone drop-down list.
l Choose Run daily/weekly from the Schedule drop-down list.
l Specify the time when the job should be started in the Starting at field.
l Specify the end time for the job in the Ending field. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week on which the job will be started.

- 612 -
Monthly or Yearly Job Execution

To run a job monthly or yearly, choose Run monthly/yearly from the schedule drop-down list:
l Specify the job start schedule in the appropriate fields.
l Specify the time when the job should be started in the Starting at field.
l Specify the end time for the job in the Ending field. If the job has not completed by the time specified, the job will
be stopped.
l Choose a time zone to be used for the job start and end times from the time zone drop-down list.
l Select the days of the week on which the job will be started.

- 613 -
Periodic Job Execution

To run a job multiple times per day, choose Run periodically from the schedule drop-down list and then choose a time
period from the appropriate fields:
l Specify the time when the job should be started in the Starting at field.
l Specify the end time for the job in the Ending field. If the job has not completed by the time specified, the job will
be stopped.
l Choose a time zone to be used for the job start and end times from the time zone drop-down list.

Chained Job

To run the job after a previous one has completed, choose Run after another job from the schedule drop-down list and
set the options as follows:
1. After the job: Select a job after which the current job will be started.
2. Run this job: Choose whether to run the current job immediately after the previous one has completed or
specify a delay.
3. After successful runs: When selected, the job will run if the previous one has completed successfully.
4. After failed runs: When selected, the job will run if the previous one has failed.
5. After stopped runs: When selected, the job will run if the previous one has been stopped.

- 614 -
Additional Schedule

If you need to add an additional schedule, click Add another schedule and configure it as described above.

- 615 -
VMware Flash VM Boot Job Wizard: Options

On the Options page, set up job options as described in these sections:

l “Job Options” below
l “Job Name” below
l “VM Verification” on the next page
l “Recovery Options” on page 618
l “Specifying VM Names” on page 618
l “Generating VM MAC Addresses” on page 618
l “Powering Recovered VMs” on page 618
l “Pre and Post Actions” on page 619
l “Setting up Email Notifications for the Job” on page 619
l “Setting Up a Pre-Job Script” on page 619
l “Setting Up a Post-Job Script” on page 620
l “Data Routing” on page 621
l “Completing the New Flash VM Boot Job Wizard” on page 621

Job Options

In this section, specify a job name and select a VM verification type.

Job Name
Enter a name for your job in the Job name box.

- 616 -
VM Verification
VM Verification allows you to check the integrity of the backup by starting it and interacting with it. For more details,
refer to the VM Verification article. 
You can choose one of the following VM verification options: 
l Screenshot verification: When enabled, all VM backups created by the job will be verified as follows: After a
backup of a VM is completed, the VM is recovered from the backup using Flash VM Boot (and is disconnected
from networks), a screenshot of the recovered VM is taken once the VM OS has booted, after which the VM is
discarded. VM screenshots will be included in email notifications (if they are configured) and displayed on the
main Dashboard.
l Boot verification: When enabled, all VM backups created by the job will be verified as follows: After a VM backup
is completed, NAKIVO Backup & Replication recovers the VM using Flash VM Boot, disables networking to
prevent network connections, and verifies successful system start. 
If you select the Screenshot verification option, provide verification options in the VM Boot Location dialog box that
opens:
l Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started on the
target container simultaneously.
l Recovery time objective: Specify an amount of time allocated for verification of each VM backup. If the VM OS
does not start within the specified amount of time, verification will be considered failed.
l Screenshot delay: Specify an amount of time that the product should wait after a Guest OS start before taking a
screenshot.
Note
The specified time must be sufficient to fully start the VM OS. Try increasing this amount if the default amount is not
sufficient.
When Boot verification is selected, specify verification options in the dialog box that opens: 
l Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started on the
target container simultaneously. 
l Recovery time objective: Specify the amount of time allocated for verification of each VM backup. If a VM OS
does not start within the specified amount of time, verification will be considered failed.

- 617 -
Recovery Options

In this section, specify VM names, generate VM MAC addresses, and choose whether you want to power on recovered
VMs or not.

Specifying VM Names
NAKIVO Backup & Replication allows you to change the names of recovered VMs so you can distinguish between
recovered VMs and source VMs. By default, the text “- recovered” is appended to the end of the recovered VM name.
To change VM replica names, choose one of the following Recovered VM names options in the Recovered VM Options
section:
l Append “-recovered” in the end: Source VM names are used for recovered VM names and “-recovered” is added
after the recovered VM name.
l Leave recovered VM names as is: Recovered VM names are identical to the source VM names.
l Enter custom recovered VM names: You can enter custom names for recovered VMs.

Generating VM MAC Addresses

In the Recovered VM Options section, you can choose one of the following options in relation to recovered VM MAC
addresses:
l Do not generate new MAC addresses: The recovered VMs will have the same MAC address as the source VMs
l Generate new MAC addresses: A new MAC address will be generated for each recovered VM.

Powering Recovered VMs

To power on the recovered VMs, choose the VM power on option.

- 618 -
Pre and Post Actions

NAKIVO Backup & Replication allows you to run a script before Flash VM boot begins (a pre-job script) and after the
boot of all VMs in the job has completed (a post-job script). The scripts can only be executed on the machine where the
Director is installed. You can also set up email notifications for the job.

Setting up Email Notifications for the Job

NAKIVO Backup & Replication can send email notifications about job completion status to specified recipients. This
feature complements global notifications and allows you to configure notifications on a per-job level.
To enable this option, make sure Email settings are configured.

To send email notifications, do the following:

1. In the Pre and Post Actions section, select the Send job run reports to option.
2. In the text box that becomes enabled, specify one or more email addresses. Use semicolons to separate multiple
email addresses.

Setting Up a Pre-Job Script

To run a script before the product begins recovering VMs, do the following:
1. Place a script file on the machine where the Director is installed.
2. In the Pre and Post Actions section, select the Run local pre job script option and click settings.
3. Specify the following parameters in the dialog that opens:
1. Script path: Specify a local path to the script on the machine where the Director is installed. A script
interpreter should be specified.
Example (Windows): cmd.exe /c D:\script.bat

- 619 -
 Example (Linux): bash /root/script.sh
2. Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish:With this option selected, the job will be in the “running” state until
the script is completed.
l Do not wait for the script to finish: With this option selected, the job will be completed even if the
script execution is still in progress.
3. Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: With this option selected, script failure will not influence the
status of the job.
l Fail the job on script failure: With this option selected, if the script fails, the job status will be set
to “failed” even if VM backup has been successful.

Setting Up a Post-Job Script

To run a script after the product has finished recovering all VMs, do the following:
1. Place a script file on the machine where the Director is installed.
2. In the Pre and Post Actions section, select the Run local post job script option and click settings.
3. Specify the following parameters in the dialog that opens:
1. Script path: Specify a local path to the script on the machine where the Director is installed. A script
interpreter should be specified. 
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
2. Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, the job will be in the “running” state until
the script is completed.
l Do not wait for the script to finish: With this option selected, the job will be completed even if the
script execution is still in progress.
3. Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: With this option selected, script failure will not influence the
status of the job.
l Fail the job on script failure: With this option selected, if the script fails, the job status will be set
to “failed” even if VM backup has been successful.

- 620 -
Data Routing

If the Transporter assigned to the Backup Repository cannot use iSCSI port 3260 because it is occupied by other
services, you can set data routing: a proxy transporter can be used to forward iSCSI target exposed from the Backup
Repository to the target host. To set data routing, go to the Data routing section and choose a proxy transporter from
the list of available Transporters.

Completing the New Flash VM Boot Job Wizard

Click Finish or Finish & Run to complete the job creation.

Note
If you click Finish & Run, you will have to define the scope of your job. Please refer to “Running Jobs on Demand” on
page 97 for details.

- 621 -
Migrating Recovered VMs Using Flash Boot
Using Flash VM Boot, you can migrate the recovered VMs to another location. To do this, follow the instructions below:

Migrating Recovered VMware VMs Using Flash VM Boot

To migrate a booted VM from one datastore to another, do the following while the virtual machine is running:
1. Open vSphere Client.
2. In the vSphere Client inventory, select the virtual machine recovered with Flash VM Boot that you want to
migrate.
3. Right-click on the VM and select Migrate.
4. Select Change datastore and click Next.
5. Select the format of your virtual hard disk.
6. Select the datastore where you want to store the VM.
7. Review the page and click Finish.
Note
After migrating the booted VMs, you can click the Discard VMs button in the Flash VM Boot job. The job detects that
the VMs were migrated and does not discard them.
Replicate booted VMs as described below:
1. Refresh the Inventory in Settings (so that the VMs created by Flash VM Boot are added to the product). 
2. Create a new replication job for the VMs that you want to permanently recover. 
3. Run the replication job. 
4. After replication is finished, run the job once again. This is required because the recovered VMs were running (and
obtaining some changes) while the initial replication was in progress. 
5. To ensure zero data loss, power off the VMs created by Flash VM Boot in the VMware vSphere client and run the
VM replication job one last time. 
6. Discard the VMs created by Flash VM Boot.
7. Power on the VMs created by the replication job.

- 622 -
Performing Cross-Platform Recovery
With the Cross-Platform Recovery feature of NAKIVO Backup & Replication, you can export backups to standard
formats that are compatible with various platforms. The following formats are supported:
l VMDK for disk(s) of VMware virtual machine(s)
l VHD for disk(s) of Hyper-V virtual machine(s)
l VHDX for disk(s) of Hyper-V virtual machine(s)
To export your backup for subsequent recovery on the same platform or a different one, use the Backup Export Wizard
in NAKIVO Backup & Replication. Refer to “Feature Requirements” on page 162 for the supported scenarios for cross-
platform recovery.
NAKIVO Backup & Replication does not run VM preparation when exporting the backups into a specific format. If you
plan to import the VM into a different platform and VM preparation is required, prepare your VM in advance.
This section includes the following topics:
l “Opening Backup Export Wizard” on page 624
l “Backup Export Wizard: Backups” on page 626
l “Backup Export Wizard: Disks” on page 627
l “Backup Export Wizard: Options” on page 628
l “Backup Export Wizard: Finish” on page 629

- 623 -
Opening Backup Export Wizard
Open Backup Export Wizard using one of the following ways:
l Navigate to the Dashboard, click Recover and then click Export Backups.

l On the Settings page:

1. Click the Repositories tab.
2. In the list of repositories, click a repository to expand it.
3. In the list of backups, hover over a backup and then click Recover.
4. In the menu that opens, click Export Backups.

- 624 -
The Backup Export Wizard opens.

- 625 -
Backup Export Wizard: Backups
On the Backups page of the wizard:
1. In the left pane, select one or more backups using one of these views:
o Jobs & Groups
o Backup Repositories
2. Select a recovery point for each backup in the right pane.
3. Click Next to go to the next page of the wizard.

- 626 -
Backup Export Wizard: Disks
On the Disks page of the wizard:
1. Select one or more disks under each backup.
2. Click Next to go to the next page of the wizard.

- 627 -
Backup Export Wizard: Options
On the Options page of the wizard, specify options for exporting your backups:
1. Export format: Choose one of the following:
o VMDK
o VHD
o VHDX
Note
VMDK disks are always pre-allocated with the thick provisioning type of storage.
2. Export location: Choose one of the following:
o Local folder on assigned Transporter: With this option selected, you have to specify a path to the local
folder to which the backups will be exported.
o CIFS share: With this option selected, proceed as follows:
a. Enter the following:
l Path to the share
l Username and Password
b. Click Test Connection to check your credentials for the specified share.
o NFS share: With this option selected, proceed as follows:
a. Enter Path to the share.
b. Click Test Connection to check the connection to the specified share.
3. Click Export to go to the next page of the wizard.

- 628 -
Backup Export Wizard: Finish
The Finish page of the wizard informs you that your backup export has started. To view the status of your backup
export, go to Activities.
To view the backup export progress, go to Settings > General > Events.
To close the Backup Export Wizard, click Close.

- 629 -
Recovery From Tape
To recover backups from tape, move the backed up data from a tape cartridge to a backup repository. Once the data is
in the repository, you can restore the contents using the standard NAKIVO Backup & Replication tools.

Refer to the following topics for more information:

l “Starting Recovery from Tape Wizard” on page 631
l “Recovery from Tape Wizard: Backups” on page 632
l “Recovery from Tape Wizard: Destination” on page 633
l “Recovery from Tape Wizard: Options” on page 634

- 630 -
Starting Recovery from Tape Wizard
To launch the recovery from the Tape wizard, do the following:
1. Go to Inventory, click the Tape tab and select Backups from the View drop-down list.

2.  In the Backups table, do one of the following:

l Select the checkbox next to one or several backups that you want to recover and click the Recover button.
This opens the Recovery wizard with specified backups and their latest recovery point selected.
Note
Only backups of the same type can be selected. That is, you cannot select VMware and Hyper-V type
backups and launch the Recovery wizard.
l Click the name of the backup to go to the Recovery of the Tape Cartridge Management page where you
can launch the Recovery wizard.

The New Tape Recovery Job Wizard opens.

3. Alternatively, go to the “Managing Tape Cartridges” on page 428 page, select a backup in the Tape contents pane
and then click the recovery point you want to restore from.

- 631 -
Recovery from Tape Wizard: Backups
The first page of the Recovery Wizard is Backups. The number of backups and recovery points present in the table
depends on the backups and recovery points you selected when launching the wizard. However, during this step, you
can add or delete the backups and select different recovery points of the same type (hypervisor). You can also search
for backups by entering a name (or part of it) into the Search box and group the backups by media pools, device
locations, or tape devices.
Note
l If a selected recovery point of the job object is a full recovery point, NAKIVO Backup & Replication will recover the
selected recovery point.
l If a selected recovery point of the job is incremental, NAKIVO Backup & Replication will recover the chain of
recovery points starting with the full recovery point that is the ancestor to the selected recovery point and
finishing with the selected incremental recovery point. 

After you are done, click Next.

- 632 -
Recovery from Tape Wizard: Destination
On the Destination page, you define the Backup Repository where the backup will be placed by selecting an option
from the Container drop-down list. You can also select which VM disks to recover by clicking Advanced options.

Click Next to proceed to the next page.

- 633 -
Recovery from Tape Wizard: Options
l “General Options” below
l “Pre and Post Actions” on the next page
l “Setting Up a Pre-Job Script” on the next page
l “Setting Up a Post Job Script” on page 636
l “Email Notifications” on page 636
l “Data Transfer” on page 637
l “Bandwidth Throttling” on page 637

General Options
Specify the general options as follows:
1. Job name: Specify a name for the recovery job.
2. Network acceleration: When network acceleration is enabled, NAKIVO Backup & Replication uses compression
and traffic reduction techniques to speed up data transfer. Enable this option if you plan to recover VMs over
WAN or slow LAN links. For more information, refer to “Network Acceleration” on page 61.
3. Encryption: When encryption is enabled, VM data is protected with AES 256 encryption while traveling over the
network. Data encryption increases the backup time and CPU load on machines running Transporters. Select this
option if recovering over WAN without a VPN connection. For details, refer to “Encryption in Flight and at Rest”
on page 38.

- 634 -
Pre and Post Actions
NAKIVO Backup & Replication allows you to run a script before VM recovery begins (a pre-job script) and after the
recovery of all VMs in the job has completed (a post-job script). The scripts can only be executed on the machine where
the Director is installed. Refer to “Pre and Post Job Scripts” on page 69 for details.

Setting Up a Pre-Job Script

To run a script before the product begins recovering VMs, do the following:
1. Place a script file on the machine where the Director is installed.
2. Select the Run local pre job script option and click the settings link.
3. Specify the following parameters in the dialog that appears:
l Script path: Specify a local path to the script on the machine where the Director is installed. A script
interpreter should be specified. 
l Example (Windows): cmd.exe /c D:\script.bat
l Example (Linux): bash /root/script.sh
l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, VM recovery is only started after the script
is completed.
l Do not wait for the script to finish: With this option selected, the product runs the script and
starts recovering VMs at the same time.
l Error handling: Choose one of the following job behaviors in relation to scrip failure:
l Continue the job on script failure: With this option selected, the job will perform VM recovery
even if the script has failed.
l Fail the job on script failure: With this option selected, if the script fails, the job will be failed and
VM recovery will not be performed.

- 635 -
Setting Up a Post Job Script

To run a script after the product has finished backing up all VMs, do the following:
1. Place a script file on the machine where the Director is installed.
2. Select the Run local post job script option and click the settings link.
3. Specify the following parameters in the dialog that appears:
l Script path: Specify a local path to the script on the machine where the Director is installed. A script interpreter
should be specified. 
l Example (Windows): cmd.exe /c D:\script.bat
l Example (Linux): bash /root/script.sh
l Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, VM recovery is only started after the script is
completed.
l Do not wait for the script to finish: With this option selected, the product runs the script and starts
recovering VMs at the same time.
l Error handling: Choose one of the following job behaviors in relation to scrip failure:
l Continue the job on script failure: With this option selected, the job will perform VM recovery even if
the script has failed.
l Fail the job on script failure: With this option selected, if the script fails, the job will be failed and VM
recovery will not be performed.

Email Notifications

NAKIVO Backup & Replication can send email notifications about job completion status to specified recipients. This
feature complements the global notifications feature and allows you to configure notifications on a per-job level.
To send email notifications, select the Send job run reports to option in the Pre and Post Actions section and specify
one or more email addresses in the text field. The semicolon character should be used to separate multiple email
addresses. To enable this option, make sure that your email setting are configured. Refer to “Email Notifications” on
page 289 for details.

- 636 -
Data Transfer
In the Data Transfer section of the Options page, you can set or configure bandwidth throttling rules.

Bandwidth Throttling

Follow the steps below to regulate the speed of data transfer over the network for your backup job:
1. For the Bandwidth throttling option, choose Enabled.

Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer
to “Bandwidth Throttling” on page 283 for details.
2. Click the Settings link that becomes available.
3. The Job Bandwidth Rules dialog opens displaying you the list of available rules. You have the following options:
l Create a new bandwidth rule for your backup job:
1. Click the Create New Rule button.
2. The New Bandwidth Rule dialog opens. Refer to the “Bandwidth Throttling” on page 283 topic for

- 637 -
 details on creating a bandwidth rule.
3. Click Save.
l Activate an existing bandwidth rule for your job. Select the checkbox to the left of the necessary
bandwidth rule. To deactivate a bandwidth rule for your job, deselect the corresponding checkbox.
l Edit a bandwidth rule. Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth
Rule dialog box that opens.
l Disable a bandwidth rule. Click the Disable link. The bandwidth rule will be disabled for all jobs.
l Remove a bandwidth rule. Click the Remove link and then click Delete to confirm your operation.

- 638 -
Planning Disaster Recovery
NAKIVO Backup & Replication allows you to address all major disaster recovery (DR) planning points by creating
automated DR workflows for VMware, Microsoft Hyper-V, and AWS EC2 environments. The application allows you to
protect VMs running within a cluster, replicate VMs, failover to replicas, and replica failback. 
When using Site Recovery, you can include up to 200 actions in a single job, including failover, failback, start/stop VMs
and instances, run/stop jobs, run script, attach or detach repository, send an email, wait, and check condition. By
arranging actions and conditions into one automated algorithm, you can create disaster recovery jobs of any
complexity.
For more details, refer to the corresponding articles below:
l “Failover to Replica for VMware” on page 640
l “Replica Failback for VMware vSphere” on page 649
l “Site Recovery Job” on page 661

- 639 -
Failover to Replica for VMware
With NAKIVO Backup & Replication, you can switch your VMware VM to the VM’s latest replica in case of failure.
Refer to the following topics for more information:
l “Starting VMware Failover to Replica” on page 641
l “Failover Job Wizard for VMware: Source” on page 642
l “Failover Job Wizard for VMware: Networks” on page 643
l “Failover Job Wizard for VMware: Re-IP” on page 645
l “Failover Job Wizard for VMware: Options” on page 647

- 640 -
Starting VMware Failover to Replica
To start the procedure of switching a VMware system workload to a backup VM, click Recover in the NAKIVO Backup &
Replication Dashboard and then click VM replica failover.

The New Failover Job Wizard for VMware vSphere opens.

- 641 -
Failover Job Wizard for VMware: Source
On the Source page of the wizard, do the following:
1. In the left pane of the page, choose either of the following inventory views:
o Jobs & Groups: When selected, the inventory tree displays groups, jobs, and backups of the
appropriate hypervisor. You can select the required replica from the list of replication jobs.
o Policy:  When selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for
details. If the items were selected in alternate views, a dialog box opens warning you that switching to
the Policy view will reset your current selection. Click Switch View to confirm switching to
the Policy view. Make sure that at least one item matches the available set of policy rules. Refer
to “Managing Policy Rules” on page 110 for details.
2. Select one or more source VMware VMs in the left pane and then select a recovery point for each source VM in
the right pane.

3. Click Next to go to the next page of the wizard.

- 642 -
Failover Job Wizard for VMware: Networks
When the replica network – or target VMware virtual network, – differs from the network address where the source
VMs are deployed – or source VMware virtual network, – your failover job needs a relation between these networks to
be performed successfully. Such relation is called a network mapping.
To map source VMware virtual networks to appropriate target virtual networks, please do the following on the
Networks page of the wizard:
1. Select Enable network mapping.
2. The Network Mappings dialog box opens. You have the following options:
l Create a new network mapping:
a. Click Create new mapping.
b. The New Network Mapping dialog opens. Choose a source network and a target network and
click Save.

l Add an existing network mapping:

a. Click Add existing mapping.
b. The Network Mappings dialog opens. Choose one or more appropriate network mappings and

- 643 -
 close the dialog box.

l Edit an existing network mapping:

a. Hover over the necessary item in the Network Mappings list and then click the Edit button to
the right of the item.
b. The Edit Network Mapping dialog box opens. Choose an appropriate item from the Target
network drop-down list and then click Save.
l Delete an existing mapping: hover over the necessary item in the Network Mappings list and then click
the X icon to the right of the item.

l To leave the list of existing network mappings intact, go to the next page of the wizard.
3. Click Next to go to the next page of the wizard.

- 644 -
Failover Job Wizard for VMware: Re-IP
When the IP addressing scheme for the target replica differs from the IP addressing scheme for the VMware source
VMs, your failover job needs relations between source VMs addresses and the target replica VMs addresses to be
performed successfully. These relations are called re-IP rules.
Warning
VMware Tools must be running on source VMs to successfully enable re-IP for your failover job.
To map a source VM IP address to a specific target IP address, do the following on the Re-IP page of the wizard:
1. Select Enable Re-IP.
2. The Re-IP Rules section opens. Click the Select VMs link.
3. The Re-IP dialog box opens. In the list of your source VMs, select at least one VM and close the dialog box.
4. You have the following options:
l Create a new rule:
a. Click Create new rule.
b. The New Re-IP Rule dialog opens. Enter source and target settings for the Re-IP rule and click
Save.

Note that you can use wildcards for IP addresses. For example, if you enter 192.168.1.* -
> 10.30.30.* for the re-IP rule, a source VM IP address such as 192.168.1.50 will be
changed to the 10.30.30.50 IP address for your failover job.

l Add an existing rule:

- 645 -
 a. Click Add existing rule.
b. The Re-IP Rules dialog opens. Select one or more appropriate Re-IP rules and close the dialog.

l Edit an existing Re-IP rule:

a. Hover over the required item in the Re-IP Rules list and click the Edit button to the right of the
item.
b. The Edit Re-IP Rule dialog box opens. Edit the required properties of the Re-IP rule and click
Save.
l Delete an existing mapping: Hover over the required item in the Re-IP Rules list and click the X icon to
the right of the item.

l To leave the list of existing Re-IP rules intact, go to the next page of the wizard.
5. Click Next to go to the next page of the wizard.

- 646 -
Failover Job Wizard for VMware: Options
On this page of the wizard, set the options for the VMware failover job:
l “Job Options” below
l “Pre and Post Actions” below
l “Completing the New Failover Job Wizard for VMware” on the next page

Job Options

The following failover job options are available for editing:

1. Job name: A string of 50 or fewer characters specifying the name of the failover job.
2. Power off source VMs: Select this checkbox to power off source VMs when the failover job has completed.

Pre and Post Actions

The following pre- and post-job actions can be set up:

1. Send job run reports to: When selected, a job report is sent to specified recipients each time the failover job
has completed. This overrides the default setting in the NAKIVO Backup & Replication “Settings” on page 281.
2. Run local pre job script: When selected, a dialog box opens in which you can specify the following options of
the pre-job script to be executed:
1. Script path: A local path to the script on the machine where the Director is installed. A script interpreter
should be specified as well.
2. Job behavior: The following options are available:
n Wait for the script to finish: This is the default option.
n Do not wait for the script to finish.
3. Error handling: The following options are available:
n Continue the job on script failure: This is the default option.
n Fail the job on script failure.
3. Run local post job script: When selected, a dialog box opens in which you can specify options of the post-job
script to be executed on the machine where the product is installed. The options are similar to the ones of

- 647 -
 the pre-job script. 

Completing the New Failover Job Wizard for VMware

Click Finish or Finish & Run to complete the job creation.

Note
If you click Finish & Run, you will have to define the scope of your job. Refer to “Running Jobs on Demand” on page 97
for details.

- 648 -
Replica Failback for VMware vSphere
With NAKIVO Backup & Replication, you can switch your VMware VM replicas back to the source or to a new location.
Refer to the following topics for more information:
l “Starting Replica Failback for VMware vSphere” on page 650
l “Failback Job Wizard for VMware vSphere: Source” on page 651
l “Failback Job Wizard for VMware vSphere: Destination” on page 653
l “Failback Job Wizard for VMware vSphere: Networks” on page 655
l “Failback Job Wizard for VMware vSphere: Re-IP” on page 656
l “Failback Job Wizard for VMware vSphere: Options” on page 658

- 649 -
Starting Replica Failback for VMware vSphere
Before starting replica failback for VMware vSphere, make sure that you have switched the replicas to the “Failover”
state with a VMware Failover Job. Refer to “Failover to Replica for VMware” on page 640 for details.
To start the failback procedure, click Recover in the Dashboard of NAKIVO Backup & Replication and then click VM
replica failback.

- 650 -
Failback Job Wizard for VMware vSphere: Source
On the Source page of the wizard, do the following:
1. In the left pane of the page, choose either of the following inventory views:
l Jobs & Groups: When selected, the inventory tree displays groups, jobs, and backups of the appropriate
hypervisor. You can select the required replica from the list of replication jobs.
l Policy: When selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details. If
the items were selected in alternate views, a dialog box opens warning you that switching to
the Policy view will reset your current selection. Click Switch View to confirm switching to the Policy view.
Make sure that at least one item matches the available set of policy rules. Refer to “Managing Policy Rules”
on page 110 for details.
2. Select one or more replica VMware VMs in the left pane of the page.

Click Next to confirm adding selected replicas to the failback job. The wizard will display the next page.
Notes
1. If you cannot find a replica or a container.
l Make sure the corresponding vCenter or ESX(i) host has been added to the inventory.
l Refresh inventory.
2. Adding a VMware container to the job ensures that important replicas are always protected. If you add a VMware
container to the job:

- 651 -
 l All replicas in the "Failover" state that are available in the selected container will be processed.
l All new replicas that will be created in (or moved to) the container in the future will be automatically added
to the job and processed.
3. The order in which replicas are processed is important if the Transporter performing failback cannot process all
replicas of the job simultaneously — either because the Transporter is processing other jobs at the same time or
because the job contains more VM disks than the Transporter’s maximum load specified during the Transporter
creation.

- 652 -
Failback Job Wizard for VMware vSphere: Destination
On this page of the wizard, you can specify a failback destination for your VMware replicas. Failback to the original
location will update/replace the existing source VM in the original location. Failback to the new location will create a new
VM.
Refer to the following subsections on providing a destination for your VMware vSphere Replica Failback job:
l “Using Original VMware Failback Location” below
l “Creating New VMware Failback Location” below
l “Creating a Different VMware Failback Location for All Replicas” on the next page

Using Original VMware Failback Location

To use the original location for your VMware failback job, follow the steps below:
1. In the Failback location list, choose Original Location.
2. Click Next to go to the Networks page of the wizard.

Creating New VMware Failback Location

To create a new location for your VMware failback job, follow the steps below:
1. In the Failback location list, choose New Location.
2. In the Container list, choose a container for your failback location.
3. In the Datastore list, choose a datastore for your failback location.
4. Optionally, you can choose a target VM folder from the VM folder drop-down list.
5. Click Next to go to the Networks page of the wizard.

- 653 -
Creating a Different VMware Failback Location for All Replicas

To create a new failover location for every replica you've added to the job, click Advanced options and set up the
options as described for New Location.  

- 654 -
Failback Job Wizard for VMware vSphere: Networks
To map source VM virtual networks to appropriate target virtual networks, take the following actions on
the Networks page of the wizard:
1. Select Enable network mapping.
2. The Network Mappings section opens. You have the following options:
l Create a new mapping:
a. Click Create new mapping.
b. The New Network Mapping dialog opens. Choose a source network and a target network and
click Save.
l Add an existing mapping:
a. Click Add existing mapping.
b. The Network Mappings dialog opens. Choose one or more appropriate network mappings and
close the dialog box.
l Edit an existing mapping:
a. Hover the pointer over the necessary item in the Network Mappings list.
b. A toolbar with icons opens to the right of the item. Click the Edit button.
c. The Edit Network Mapping dialog opens. Choose an appropriate item from the Target
network drop-down list and then click Save.
l Delete an existing mapping:
a. Hover the pointer over the necessary item in the Network Mappings list.
b. A toolbar with icons opens to the right of the item. Click the Delete icon.
l To leave the list of existing network mappings intact, go to the next page of the wizard.
3. Click Next to go to the next page of the wizard.

- 655 -
Failback Job Wizard for VMware vSphere: Re-IP
On the Re-IP page of the wizard, you can map a source VM IP address to a specific target IP address.
Please proceed as follows:
1. Select Enable Re-IP.
2. The Re-IP Rules section opens. Click the Select VMs link.
3. The Re-IP dialog box opens. In the list of your source VMs, select at least one VM. Select the credentials to be
used for each VM and close the dialog box.
Note
Re-IP rules will be applied only to VMs that have a static IPv4 address configured.
4. You have the following options:
l Create a new rule:
1. Click Create new rule.
2. The New Re-IP Rule dialog opens. Enter source and target settings for the Re-IP rule and click Save. 
Note
You can use wildcards for IP addresses.
Example
When you enter 192.168.1.* -> 10.30.30.* Re-IP rule, the source VM IP address such as192.168.1.50
will be changed to the 10.30.30.50 IP address for your replica failback job. When there are several
Re-IP rules applicable to your source VM, the application will define the most suitable one and
apply it to the source VM IP address.
l Add an existing rule:
1. Click Add existing rule.
2. The Re-IP Rules dialog opens. Choose an appropriate Re-IP rule and close the dialog.
l Edit an existing Re-IP rule:
1. Hover the pointer over the required item in the Re-IP Rules list.
2. A toolbar with icons opens to the right of the item. Click the Edit button.
3. The Edit Re-IP Rule dialog opens. Edit the required properties of the Re-IP rule and click Save.
l Delete an existing mapping:
1. Hover the pointer over the required item in the Re-IP Rules list.
2. A toolbar with icons opens to the right of the item. Click the Delete icon.
l To leave the list of existing Re-IP rules intact, go to the next page of the wizard.

- 656 -
5. Click Next to go to the next page of the wizard.

- 657 -
Failback Job Wizard for VMware vSphere: Options
On the Options page of the wizard, specify options for the VMware Failback job as described in the following sections:
l “Job Options” below
l “Pre and Post Actions” below
l “Data Transfer” on the next page
l “Transport Mode” on the next page
l “Transporters” on the next page

Job Options

1. In the Job name box, enter a string of 50 or fewer characters specifying the name of your failback job.
2. Select Power off replica VMs to power off the replica workloads during the failback.

Pre and Post Actions

If needed, enable pre and post actions:

1. Send job run reports to: When selected, a job report is sent to specified recipients each time the failback job has
completed. This overrides the default setting in the NAKIVO Backup & Replication “Settings” on page 281
dashboard.
2. Run local pre job script: When selected, a dialog box open in which you can specify the following options of the
pre-job script to be run:
l Script path: A local path to the script on the machine where the Director is installed. A script interpreter
should be specified as well.
l Job behavior: The following options are available:
l Wait for the script to finish: This is the default option.
l Do not wait for the script to finish.
l Error handling: The following options are available:

- 658 -
 l Continue the job on script failure: This is the default option.
l Fail the job on script failure.
3. Run local post job script: When selected, a dialog box opens in which you can specify options of the post-job
script to be executed on the machine where the product is installed. Proceed with setting the options as
described for Run local pre job script.

Data Transfer

In the Data Transfer section of the Options page, you can select a transport mode and select a Transporter to be used
for reading data. Proceed as described in the sections below.

Transport Mode

Transport mode defines the method of VM data retrieval by a source Transporter. Do one of the following:
l Select Automatic selection to allow the product to choose the best transport mode available. If the product
cannot use SAN or Hot Add, LAN mode will be used.
l Manually select one of the available transport mode options:
l SAN
l Hot Add
l LAN

Transporters

By default, the product automatically determines which Transporter should be used to read data from the source VM.
However, you can manually specify which Transporters should be used for the job. Here’s how:
1. In the Data Transfer section, choose one of the following options:
l Automatic selection: The product will automatically determine which Transporters are the closest to
source hosts (the hosts that run selected VMs) and will use those Transporters to retrieve data from source
VMs.
l Manual - configured for all VMs: Select this option to manually specify a single Transporter that will be

- 659 -
 used to retrieve data from source VMs.
l Manual - configured per host: Select this option to manually specify which Transporter should be used to
retrieve data from each source host.  When selected, the Replacement Transporter drop-down list
becomes available. In case a primary Transporter is unavailable, a replacement Transporter will be used.
Note that the product selects what Transporter to use (primary or replacement) at the beginning of the job
run, not while the job is running. 
2. Click Finish or Finish & Run to complete the job creation.

Note
If you click Finish & Run, you will have to define the scope of your job. Refer to “Running Jobs on Demand” on page 97
for details.

- 660 -
Site Recovery Job
Site Recovery Job is a special job that automates execution of one or multiple Site Recovery actions. 
You can execute your Site Recovery Job on demand or on schedule.
Creating a Site Recovery Job is done with a wizard and includes the following steps:
l “Creating Site Recovery Job” on page 662
l “Running Site Recovery Job” on page 691

- 661 -
Creating Site Recovery Job
Creating a Site Recovery Job is done with a wizard and includes the following steps:
l “Starting Site Recovery Job Wizard” on page 663
l “Site Recovery Job Wizard: Actions” on page 664
l “Site Recovery Job Wizard: Networks” on page 681
l “Site Recovery Job Wizard: Re-IP” on page 683
l “Site Recovery Job Wizard: Test Schedule” on page 686
l “Site Recovery Job Wizard: Options” on page 690

- 662 -
Starting Site Recovery Job Wizard

Follow the steps below to start creating a Site Recovery Job:

1. Go to the Dashboard and open the Create menu.
2. In the Create menu, click Site recovery job.

The New Site Recovery Job Wizard opens.

- 663 -
Site Recovery Job Wizard: Actions

On the Actions page of the Site Recovery Job wizard, you can add one or more actions to a Site Recovery job. Refer to
the subsections below for details:
l Actions Available for Site Recovery Job
l Managing Actions of Site Recovery Job
l Options Common to Most Actions
When finished with adding actions to a Site Recovery job, click Next to go to the Networks page of the Site Recovery
Job Wizard.

Actions Available for Site Recovery Job

The list of actions available for a Site Recovery job is available in the left pane. It includes the following:
l “Failover VMware VMs: VMs” on page 667
l “Failback VMware VMs: VMs” on page 669
l “Start VMs / Instances Action” on page 672
l “Stop VMs / Instances Action” on page 673
l “Run / Stop Jobs Action” on page 674
l “Run Script Action” on page 675
l “Attach / Detach Repository Action” on page 676
l “Send Email Action” on page 677
l “Wait Action” on page 678
l “Check Condition Action” on page 679
To add an action to a Site Recovery job, click the corresponding item in the actions list and follow the instructions of
the wizard that opens.

Managing Actions of Site Recovery Job

The actions list of a Site Recovery job is located in the right pane and contains the actions you add.
For a selected action, a toolbar with buttons is available allowing you to perform the following commands:
l Move up / Move down: Moves your action up/down in the list of Site Recovery job actions.
l Edit: A page opens allowing you to make changes to your Site Recovery job action. When finished with editing the
Site Recovery job action, click Save.
l Remove: A dialog box opens asking you to confirm removing the Site Recovery job action. Click

- 664 -
 the Remove button to confirm your operation.=

Options Common to Most Actions

Most of the actions you add to your Site Recovery job will have the following common options:
l Run this action in: This option allows you to choose how to run the action:
l Run this action in both testing and production mode.
l Run this action in production mode only.
l Run this action in testing mode only.
l Waiting behavior: This option allows you to choose one of the following:
l Wait for this action to complete: The Site Recovery job will wait for the action to be completed before
continuing to run the job.
l Start next action immediately: The Site Recovery job will continue running while the action is in progress.
l Error handling: This option allows you to choose one of the following:
l Stop and fail the site recovery job if this action fails: The Site Recovery job will stop and fail if the action
fails.
l Continue the site recovery job if the action fails: The Site Recovery job will continue if the action fails.
l Transport mode: This option defines the method of VM data retrieval by a source Transporter. Do one of the
following:
l Select Automatic selection to allow the product to choose the best transport mode available. If the
product cannot use SAN or Hot Add, LAN mode will be used.
l Manually select one of the available transport mode options:
l SAN
l Hot Add
l LAN
l Transporters: This option allows you to specify which Transporters should be used for the job. Choose one of the

- 665 -
following options:
l Automatic selection: The product will automatically determine which Transporters are the closest to
source hosts (the hosts that run selected VMs) and will use those Transporters to retrieve data from source
VMs.
l Manual - configured for all VMs: Select this option to manually specify a single Transporter that will be
used to retrieve data from source VMs.
l Manual - configured per host: Select this option to manually specify which Transporter should be used to
retrieve data from each source host.  When selected, the Replacement Transporter drop-down list
becomes available. In case a primary Transporter is unavailable, a replacement Transporter will be used.
Note that the product selects what Transporter to use (primary or replacement) at the beginning of the
job run, not while the job is running. 
Note
The Transport mode and Transporters options are available for VMware failback options action only.

- 666 -
Failover VMware VMs Action

Please refer to the following sections on adding a Failover VMware VMs action to your Site Recovery job:
Failover VMware VMs: VMs
Failover VMware VMs: Options

Failover VMware VMs: VMs

On this step of the wizard, do the following:
1. In the left pane of the page, choose either of the following inventory views:
l Jobs & Groups: When selected, the inventory tree displays groups, jobs, and backups of the appropriate
hypervisor. You can select the required replica from the list of replication jobs.
l Policy: When selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details. If
the items were selected in alternate views, a dialog box opens warning you that switching to
the Policy view will reset your current selection. Click Switch View to confirm switching to the Policy view.
Make sure that at least one item matches the available set of policy rules. Refer to “Managing Policy Rules”
on page 110 for details.
2. Select one or more source VMware VMs in the left pane and then select a recovery point for each source VM in
the right pane.
3. Click Next to go to the Options page.

- 667 -
Failover VMware VMs: Options
On this page of the wizard, do the following:
1. Select Power off source VMs to power off the production workloads during the failover. Note that this will take
place only in production mode; no workloads will be powered on in test mode.
2. In the Action options section, set the options for your action. Refer to “Site Recovery Job Wizard: Actions” on
page 664 for details.
3. Click Save.

The Options page closes and your Failover VMware VMs action is added to the Site Recovery Job.

- 668 -
Failback VMware VMs Action

Please refer to the following sections on adding a Failback VMware VMs action to your Site Recovery job:
l Failback VMware VMs: VMs
l Failback VMware VMs: Location
l Failback VMware VMs: Options

Failback VMware VMs: VMs

On this page of the wizard, do the following:
1. In the left pane of the page, choose either of the following inventory views:
l Jobs & Groups: When selected, the inventory tree displays groups, jobs, and backups of the appropriate
hypervisor. You can select the required replica from the list of replication jobs.
l Policy: When selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details. If
the items were selected in alternate views, a dialog box opens warning you that switching to
the Policy view will reset your current selection. Click Switch View to confirm switching to the Policy view.
Make sure that at least one item matches the available set of policy rules. Refer to “Managing Policy Rules”
on page 110 for details.
2. Select one or more replica VMware VMs in the left pane of the page.
3. Click Next to go to the Location page of the wizard.

Failback VMware VMs: Location

Please refer to the following subsections on providing a location for your Failback VMware VMs action:

- 669 -
 l “Using Original VMware Failback Location” below
l “Creating New VMware Failback Location” below
l “Reusing Existing VMware Failback Location” on the next page

Using Original VMware Failback Location

To use the original location for your Failback VMware VMs action, follow the steps below:
1. In the Failback location list, choose Original Location.
2. Click Next to go to the Options page.

Creating New VMware Failback Location

To create a new location for your Failback VMware VMs action, follow the steps below:
1. In the Failback location list, choose New Location.
2. In the Container list, choose a container for your failback location.
3. In the Datastore list, choose a datastore for your failback location.
4. Click Next to go to the Options page.

- 670 -
Reusing Existing VMware Failback Location
To reuse existing locations for your Failback VMware VMs action, follow the steps below:
1. In the Failback location list, choose New Location.
2. Click Advanced Options.
3. Click on the necessary source VMs to expand them.
4. For the required VM, click Use existing target VM to select it.
5. The Virtual Machine list updates to include VMs. Select the VM that should be used as a target.
6. After setting the location advanced options, click Next to go to the Options page.

Failback VMware VMs: Options

On this page of the wizard, do the following:
1. Select Power off replica VMs to power off the production workloads during the failover. Please note that this will
take place only in production mode; no workloads will be powered on in test mode.
2. In the Action options section, set the options for your action. Refer to “Site Recovery Job Wizard: Actions” on
page 664 for details.
3. Click Save.

The Options page closes and your Failback VMware VMs action is added to the Site Recovery job.

- 671 -
Start VMs / Instances Action

The topic covers the following actions of a Site Recovery Job:

l Start VMware VMs
l Start Hyper-V VMs
l Start EC2 Instances 
On the wizard’s page that opens, do the following:
1. In the left pane of the page, choose either of the following inventory views:
l Hosts & Clusters: Not available for AWS EC2. When chosen, the inventory tree displays all containers and
VMs.
l VMs & Templates. Available for VMware only. When chosen, the inventory tree displays VMware hosts,
VMs, and VM templates.
l AWS Accounts: Available for AWS EC2 only. When chosen, the inventory tree displays all AWS EC2
accounts along with their regions and available instances.
l Policy: When selected, job policies can be used. Refer to Managing Job Policies for details.
Note
Switching to an alternative view resets your selection in the current view.

2. Optionally, you can filter the inventory tree by entering a string into the Search box. You can enter a part of or
the entire name of the item.
3. Select at least one VMware/Hyper-V VM or EC2 instance in the inventory tree.
4. Set the action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
5. Click Save.
The page of the wizard closes and your Start VMs / Instances action is added to the Site Recovery Job.

- 672 -
Stop VMs / Instances Action

The topic covers the following actions of your site recovery job:
l Stop VMware VMs
l Stop Hyper-V VMs
l Stop EC2 Instances
On the Stop VMs / Instances page that opens from the Actions page of the Site Recovery Job Wizard, do the following:
1. In the left pane of the page, choose one of the following inventory views:
l Hosts & Clusters: Not available for AWS EC2. When chosen, the inventory tree displays all containers and
VMs.
l VMs & Templates view: Available for VMware only. When chosen, the inventory tree displays VMware
hosts, VMs, and VM templates.
l AWS Accounts: Available for AWS EC2 only. When chosen, the inventory tree displays all AWS EC2
accounts along with their regions and available instances.
l Policy: When selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details.
Note
Switching to an alternative view resets your selection in the current view.

2.  Optionally, you can filter the inventory tree by entering a string into the Search box. You can enter a part of the
entire name of the item.
3. Select at least one VMware/Hyper-V VM or EC2 instance in the inventory tree.
4. Set action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
5. Click Save.
 The page of the wizard closes, and your Stop VMs / Instances action is added to the site recovery job.

- 673 -
Run / Stop Jobs Action

The topic covers the following actions of a Site Recovery Job:

l Run Jobs
l Stop Jobs 
On the Run / Stop Jobs page that opens from the Actions page of the Site Recovery Job Wizard, do the following:
1. Select at least one item in the list of jobs.
2. Configure action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
3. Click Save.

The page of the wizard closes and your Run / Stop Jobs action is added to the Site Recovery Job.

- 674 -
Run Script Action

To add the action to a Site Recovery Job, on the Run Script page of the wizard, do the following:
1. Target type: Choose one of the following target types for your script:
l This server (Director): The script will run on the machine where the Director is deployed. Provide the
following options:
1. Script path: A path to the script.
2. Username / Password: Credentials for running your script on the machine.
l Remote Windows / Linux server: The script will run on a remote Windows / Linux server. Provide the
following options:
1. Target server: The hostname or the IP address of the remote server.
2. Script path: A path to the script on the remote server.
3. Username / Password: Credentials for running your script on the remote server.
l VMware / Hyper-V VM / EC2 instance: The script will run on a VMware or Hyper-V VM or an EC2 instance.
Provide the following options:
1. Target VM / Instance: Choose the required item from the inventory tree.
2. Script path: A path to the script on the VMware or Hyper-V VM or EC2 instance.
3. Username / Password: Credentials for running your script on the VMware or Hyper-V VM or EC2
instance.
2. Set the Action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
3. Click Save.

The page of the wizard closes and your Run Script action is added to the Site Recovery Job.

- 675 -
Attach / Detach Repository Action

The topic covers the following actions of a Site Recovery Job:

l Attach Repository
l Detach Repository  
On the Attach / Detach Repository page that opens from the Actions page of the Site Recovery Job Wizard, do the
following:
1. Select a repository in the list of repositories.
2. Specify action options. Refer to Options Common to Most Actions for details.
3. Click Save.

The page of the wizard closes and your Attach / Detach Repository action is added to the site recovery job.

- 676 -
Send Email Action

On the Send Email page of the wizard, do the following to add the action to your site recovery job:
1. In the To box, enter a valid email address for the recipient.
2. In the Cc box, optionally you can enter an email address of the carbon copy recipient.
3. In the Subject box, optionally you can enter a subject of the mail.
4. Optionally, you can add attachments to your mail with the Browse button.
5. Enter your message text in the email body box.
6. Set up action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
7. Click Save.

The page of the wizard closes, and your Send Email action will be added to the site recovery job.

- 677 -
Wait Action

To add a wait action to your Site Recovery job, on the Wait page of the wizard, do the following:
1. Enter the time to wait in minutes or hours.
2. Set the action options. Refer to “Site Recovery Job Wizard: Actions” on page 664 for details.
3. Click Save.

The page of the wizard closes and your Wait action is added to the Site Recovery job.

- 678 -
Check Condition Action

On the Check Condition page of the wizard, do the following to add the action to your site recovery job:
1. Choose a condition type from the list:
l Resource exists: This condition checks whether the specified resource exists. With this option, you have to
set the following:
1. Choose a resource type from the list:
l VMware VM
l Hyper-V VM
l EC2 Instance
2. Define your identification method by using two lists:
a. In the first list, choose either Name or ID.
b. In the second list, choose one of the following:
l Equals
l Contains
l Starts with
l Ends with
3. Enter your condition criterion in the Search string box. 
l Resource is running: This condition checks whether the specified resource is running. With this option,
you have to set the options as described for the Resource exists option above.
l IP/hostname is reachable: This condition checks whether the specified IP/hostname is reachable. With
this option, you have to enter the following:
1. Choose the source endpoint among the following:
l This server (Director): With this option, the condition checks whether the Director can reach
the IP/hostname specified in the box below.
l Remote transporter: With this option, the condition checks whether one of your remote
Transporters can reach the IP/hostname specified in the box below.
2. In the IP/hostname box, enter an IP address or a host name of the resource to be checked for
reachability.
2. In the Action if True section of the page, choose an action to be taken if the condition criterion is satisfied:
l Continue site recovery job: Your Site Recovery job will be continued.
l Stop and fail site recovery job: Your Site Recovery job will be stopped as failed.
l End site recovery job successfully: Your Site Recovery job will be ended as successful.
l Go to another site recovery Job action: Another action of your Site Recovery job will be initiated. If you
choose this action type, a new box will open to allow you to choose the necessary action.
3. In the Action if False section of the page, choose an action to be taken if the condition criterion is not satisfied.
Available options are similar to those described in the Action if True section above.

- 679 -
 4. Click Save.

The page of the wizard closes and your Check Condition action is added to the Site Recovery job.

- 680 -
Site Recovery Job Wizard: Networks

On the Networks page of the Site Recovery Job Wizard you can map source VM virtual networks to appropriate target
virtual networks and test networks.
Please proceed as follows:
1. Select Enable network mapping.
Note
A failover or a failback action needs to be on the actions list to allow enabling network mapping for your site
recovery job.
2. The Network Mapping section opens. You have the following options:
l Create a new network mapping:
a. Click Create new mapping.
b. The New Network Mapping dialog opens. Choose a source network, a target network and a test
network, and click Save.

l Add an existing network mapping:

a. Click Add existing mapping.
b. The Network Mappings dialog opens. Choose an appropriate network mapping and close the

- 681 -
 dialog box.

l Edit an existing network mapping:

a. Hover the pointer over the necessary item in the Network Mappings list and then click
the Edit button to the right of the item.
b. The Edit Network Mapping dialog box opens. Choose appropriate items from the Target
network and the Test network lists and then click Save.

l Delete an existing mapping: hover the pointer over the necessary item in the Network Mappings list and
then click the Delete icon to the right of the item.
l To leave the list of existing network mappings intact, go to the next page of the wizard.
3. Click Next to go to the next page of the wizard.

- 682 -
Site Recovery Job Wizard: Re-IP

In the Re-IP page of the Site Recovery Job Wizard you can map a source VM IP address to a specific target IP address.
Please proceed as follows:
1. Select Enable Re-IP.
Note
A failover or a failback action needs to be in the actions list to allow enabling Re-IP for your site recovery job.
2. The Re-IP Rules section opens. Click the Select VMs link.
3. The Re-IP dialog opens. In the list of your source VMs, select at least one, select the credentials to be used for
each VM, and close the dialog.
Note
Re-IP rules will be applied only to VMs that have a static IPv4 address configured.
4. You have the following options:
l Create a new rule:
a. Click Create new rule.
b. The New Re-IP Rule dialog opens. Enter source and target settings for the Re-IP rule and click Save.

Note
You can use wildcards for IP addresses. For example, when the 192.168.1.* -> 10.30.30.* Re-IP rule is
available, it will change the source VM IP address like 192.168.1.50 to the 10.30.30.50 IP address, for
your site recovery job.
When there are several Re-IP rules applicable to your source VM, the application will define the
most suitable one and apply it to the source VM IP address.
l Add an existing rule:
a. Click Add existing rule.
b. The Re-IP Rules dialog box opens. Choose an appropriate Re-IP rule and close the dialog.

- 683 -
l Edit an existing Re-IP rule:
a. Hover the pointer over the necessary item in the Re-IP Rules list and then click the Edit button to
the right of the item.
b. The Edit Re-IP Rule dialog opens. Edit the necessary properties of the Re-IP rule and then
click Save.

l Delete an existing mapping: hover the pointer over the necessary item in the Re-IP Rules list and then click
the Delete icon to the right of the item.

- 684 -
 l To leave the list of existing Re-IP rules intact, go to the next page of the wizard.
5. Click Next to go to the next page of the wizard.

- 685 -
Site Recovery Job Wizard: Test Schedule

On the Test Schedule page of the Site Recovery Job Wizard you can schedule testing your site recovery job.
Please refer to the following sections for details:
l “Disabling Site Recovery Job Test Schedule” below
l “Daily Site Recovery Job Testing” below
l “Monthly or Yearly Site Recovery Job Testing” on the next page
l “Periodic Site Recovery Job Testing” on page 688
l “Chained Site Recovery Job” on page 688
l “Additional Schedule” on page 689

Disabling Site Recovery Job Test Schedule

If you only want to start the site recovery job manually (without any test schedule), select the Do not schedule, test on
demand check box.

Then click Next to go to the Options page of the Site Recovery Job Wizard.

Daily Site Recovery Job Testing

To test your site recovery job once a day, do the following:

1. Choose a time zone that should be used for the site recovery job start and end times from the time zone list.
2. Choose Run daily/weekly from the Schedule #1 list.
3. Specify the time when the site recovery job should be started in the Starting at box.
4. Specify the end time for the site recovery job in the Ending box. If the site recovery job has not completed by the
time specified, the site recovery job will be stopped.
5. Select the days of the week during which the site recovery job will be started.
6. To specify a date when the job test schedule comes into effect, click Effective from, click date and then pick a
date in the calendar that opens.

- 686 -
 7. Click Next to go to the Options page of the Site Recovery Job Wizard.

Monthly or Yearly Site Recovery Job Testing

To test your site recovery job monthly or yearly, do the following:

1. Choose Monthly/yearly from the schedule list.
2. Choose a time zone that should be used for the job start and end times, in the list of available time zones.
3. Specify a site recovery job start schedule in the appropriate boxes.
4. Specify the time when the site recovery job should be started, in the Starting at box.
5. Specify the end time for the site recovery job, in the Ending box. If the site recovery job has not completed by the
time specified, the site recovery job will be stopped.
6. Select the days of the week during which the job will be started.
7. To specify a date when the job test schedule comes into effect, click Effective from, click Date and then pick a
date in the calendar that opens.
8. Click Next to go to the Options page of the Site Recovery Job Wizard.

- 687 -
Periodic Site Recovery Job Testing

To test your site recovery job multiple times per day, do the following:
1. Choose a time zone that should be used for the site recovery job start and end times from the list of time zones.
2. Choose Run periodically from the Schedule #1 list and then choose a time period from the appropriate boxes.
3. Specify the time when the site recovery job should be started in the Starting at box.
4. Specify the end time for the job in the Ending box. If the site recovery job has not completed by the time
specified, the site recovery job will be stopped.
5. To specify a date when the job test schedule comes into effect, click Effective from, click Date and then pick a
date in the calendar that opens.
6. Click Next to go to the Options page of the Site Recovery Job Wizard.

Chained Site Recovery Job

To run the site recovery job after a previous job has completed, do the following:
1. Choose Run after another job from the Schedule #1 list.
2. Set the options as follows:
1. After the job: select a job after which the current site recovery job will be started.
2. Run this job: Choose whether to run the current site recovery job immediately after the previous job has
completed, or specify a delay.
3. After successful runs: If selected, the site recovery job will run if the previous job has completed
successfully.
4. After failed runs: If selected, the site recovery job will run if the previous job has failed.
5. After stopped runs: If selected, the site recovery job will run if the previous job has been stopped.
3. To specify a date when the job test schedule comes into effect, click Effective from, click date and then pick a
date in the calendar that opens.

- 688 -
 4. Click Next to go to the Options page of the Site Recovery Job Wizard.

Additional Schedule

To add more than one schedule to your site recovery job, do the following:
1. Click Add another schedule.
2. The Schedule #2 section opens. Proceed with instructions provided in the sections above.
3. When ready with adding an additional schedule to your site recovery job, click Next.

- 689 -
Site Recovery Job Wizard: Options

On the Options page of the Site Recovery Job Wizard you can specify options of your Site Recovery Job.
Proceed as follows:
1. In the Site Recovery Job section, specify a name for your Site Recovery Job.
2. In the Testing Options section:
l Recovery time objective: Enter the amount of time allowed for the Site Recovery Job test to complete. The
report will inform you of whether this objective has been met.
l Send test/run report to: When selected, it enables sending Email notifications to the specified recipients.
The semi-colon character should be used to separate multiple email addresses.
3. Click Finish to complete creating your Site Recovery Job.

The Site Recovery Job Wizard will close and your Site Recovery Job will appear in the list of NAKIVO Backup &
Replication jobs.

- 690 -
Running Site Recovery Job
The section includes the following topics:
l Running Site Recovery Job in Test Mode
l Running Site Recovery Job in Production Mode

Running Site Recovery Job in Test Mode

Running your Site Recovery Job in the test mode allows you to verify the site recovery workflow and results.
Please follow the steps below to run your Site Recovery Job in the test mode:
1. In the Jobs dashboard, select your Site Recovery Job and then click the Run Job button.
2. In the dialog that opens, click Test site recovery job.

3. The Recovery time objective dialog opens. Here you can:

l Disable/enable the Recovery time objective option.
l If the Recovery time objective is enabled, modify the amount of time allowed for the job to be completed.

- 691 -
 4. Click Test when ready.
The Site Recovery Job starts running in the test mode.
Note
In addition to testing the site recovery job on demand, testing can also be scheduled. Refer to Site Recovery Job
Wizard: Test Schedule for details.

Running Site Recovery Job in Production Mode

Running your Site Recovery Job in the production mode allows you to recover your environment from disaster.
Please follow the steps below to run your Site Recovery Job in the production mode:
1. In the Jobs dashboard, select your Site Recovery Job and then click the Run Job button.
2. In the dialog that opens, click Run site recovery job.

- 692 -
 3. The Failover type dialog opens. Choose either of the following failover types:
l Planned failover: The application will sync replica data with the source VM before switching workloads to
the replica.
l Emergency failover: The application will switch workloads from the source VM to the replica immediately.
Note
The Failover type option is only available for Site Recovery Jobs containing a Failover action.

4. Click Run.
The Site Recovery Job starts running in the production mode.

- 693 -
Replication
With NAKIVO Backup & Replication, you can perform replication of virtual machines. Replication creates and maintains
an identical copy of the source VM at the target location.
Refer to the following topics for more information:
l “Staging (Seeding) VM Replication” on page 729

- 694 -
Creating VMware Replication Jobs
With NAKIVO Backup & Replication, you can replicate VMware VMs using the workflow with a wide array of available
options. To create a replication job, click Create and then click VMware VSphere replication job on the Dashboard.

The New Replication Job Wizard for VMware vSphere opens. Complete the wizard to create a replication job.
l “Replication Job Wizard for VMware: Source” on page 696
l “Replication Job Wizard for VMware: Destination” on page 701
l “Replication Job Wizard for VMware: Networks” on page 705
l “Replication Job Wizard for VMware: Re-IP” on page 708
l “Replication Job Wizard for VMware: Schedule” on page 711
l “Replication Job Wizard for VMware: Retention” on page 715
l “Replication Job Wizard for VMware: Options” on page 716

- 695 -
Replication Job Wizard for VMware: Source
 On the Source page of the wizard, select one of the views to add VMware items to your replication job.
l “Host and Clusters” below
l “VMs and Templates” on the next page
l “Jobs and Groups” on page 698
l “Backup Repositories” on page 698
l “Policy ” on page 699

Host and Clusters

When the Host & Clusters view is chosen, the inventory tree opens in the left pane and displays all VMware items:
clusters, hosts, folders, resource pools, and VMs. Proceed as follows:
1. Optionally, you can filter the inventory tree by entering a string into the Search box. You can enter a part of or the
entire name of the item.
2. Select VMware items by placing a checkmark to the left of each item.
3. The selected items appear in the right pane of the page. You can reorder the selected items by dragging a VM or a
container with the pointer to a new position. By doing that, you can specify to replicate the most important VMs
first.
4. Review the list of selected VMware items. You can remove a selected VM or a container from the replication job in
one of the following ways:
l Deselect the item in the left pane. This will remove the item from the right pane; OR
l In the right pane, hover the pointer over the item you want to remove and click the red “x” on the right.
This will deselect the item in the left pane.

- 696 -
VMs and Templates
When the VMs & Templates view is selected, the inventory tree displays VMware hosts, VMs, and VM templates.
Proceed as described for the Hosts & Clusters view above.

- 697 -
Jobs and Groups
When the Jobs & Groups view is selected, the inventory tree displays groups, jobs, and backups of the appropriate
hypervisor. Selecting a backup from the list allows you to replicate VMs directly from the backup (Refer to “Replication
From Backup” on page 26). Proceed as described for the Hosts & Clusters view above.

Backup Repositories
When the Backup Repositories view is selected, the inventory tree displays backup repositories that contain backups of
the appropriate hypervisor. Proceed as described for the Hosts & Clusters view above.

- 698 -
Policy 
When the Policy view selected, job policies can be used. Refer to “Managing Job Policies” on page 108 for details. If the
items were selected in alternate views, a dialog box opens warning you that switching to the Policy view will reset your
current selection. Click Switch View to confirm switching to the Policy view. Make sure that at least one item matches
the available set of policy rules. Refer to “Managing Policy Rules” on page 110 for details.

Click Next to confirm adding selected VMs to the replication job. The wizard will display the next page.
Notes
1. If you cannot find a VM or a container:
l Make sure the corresponding vCenter or ESX(i) host has been added to the inventory.
l Refresh the Inventory.
2. By adding a VMware container to the job, you ensure that important VMs are always protected. If you add a
VMware container to the job:
l All VMs currently available in the selected container will be replicated.
l All new VMs that will be created in (or moved to) the container in the future will be automatically added to
the job and replicated.
3. The order in which VMs are replicated is important if the Transporter performing replication cannot process all

- 699 -
 VMs of the job simultaneously — either because the Transporter is processing other jobs at the same time or
because the job contains more VM disks than a Transporter’s maximum load specified during the Transporter
creation.
4. If all disks of a VM are unsupported (such as RDM disks in physical compatibility mode), this VM will be disabled in
the inventory tree and it will not be possible to select it. Refer to “Supported Platforms” on page 137 for details.
5. VMs marked as primary are protected by VMware Fault Tolerance. Disabled VMs are Fault Tolerance shadow
VMs.

- 700 -
Replication Job Wizard for VMware: Destination
On the Destination page, select a location for your replica(s).
l “Setting the Same Host, Datastore, and Network for All Replicas” below
l “Setting the Default Destination for Replicas” below
l “Setting Different Options for Replicas” on the next page
l “Mapping Source VMs to Existing Replicas” on page 703
l “Excluding a VM Disk from the Replication Job” on page 703

Setting the Same Host, Datastore, and Network for All Replicas
To replicate all VMs to the same container and datastore, and to connect all replicas to the same network, follow the
steps below:
1. Choose a cluster, host, or resource pool from the Container drop-down list.
2. Choose a datastore from the Datastore drop-down list.
3. If you create a Replication job from a backup job (Jobs & Groups or Backup repository view), select a target
network from the Network drop-down list.
4. Optionally, you can choose a target VM folder from the VM folder drop-down list.

Setting the Default Destination for Replicas

If you have chosen a host, cluster, folder, or a resource pool as a source for your replication job on the Source wizard
page, you can set the default container, datastore, and VM folder for replicas. To do this, follow the steps below:
1. Click Advanced options and then click on the name of the chosen host, cluster, folder, or a resource pool.
2. Choose a Default container.
3. If you have chosen the backup job on the Source page, you can choose a Default Network.
4. Optionally, you can also choose a Default VM folder.

- 701 -
Setting Different Options for Replicas
To specify different replication options for VMs, follow the steps below:
1. Click Advanced options.
2. Choose a target container, target VM, and target datastore for each VM.

- 702 -
Mapping Source VMs to Existing Replicas
If you want to perform staged replication or if you lose the replication job (due to accidental job deletion or because
you need to recreate jobs in a new copy of the product), you can map source VMs to existing replicas to avoid running
full VM replication again.
To map source VMs to existing VMs, follow the steps below:
1. Click Advanced options.
2. Open the target VM drop-down list and select the Use existing target VM option.
3. Select the VM that should be used as a target for replication in the Virtual Machine drop-down list.

When you run the job, the product analyzes the target VM you have selected, determines how it is different from the
source VM, and transfers only the differential data.
VM replication mapping can be a time-consuming process that can be equal to the time required to create a full VM
replication.
After the job completion, a new recovery point will be created and existing recovery points will not be changed or
overwritten.

Excluding a VM Disk from the Replication Job

If you do not want to replicate some disks of a VM, you can exclude those disks from the replication job. Follow the
steps below:
1. Click Advanced options.
2. Open the target VM drop-down list.

- 703 -
3. Click the drop-down list next to the disk that you want to skip and select the Skip this disk option.
4. After you have specified replica location options, click Next to go to the next page.

- 704 -
Replication Job Wizard for VMware: Networks
Note
The Networks page is skipped if you have chosen an existing backup as the target for your replication job on the Source
wizard page.
To map source VM virtual networks to appropriate target virtual networks, do the following on the Networks page in
the wizard:
1. Select Enable network mapping.
2. The Network Mappings section opens. You have the following options:
l Create a new mapping:
a. Click Create new mapping.
b. The New Network Mapping dialog box opens. Choose a source network and a target network and
click Save.

l Add an existing mapping:

a. Click Add existing mapping.
b. The Network Mappings dialog box opens. Choose one or more appropriate network mappings and
close the dialog box.

- 705 -
l Edit an existing mapping:
1. Hover the pointer over the required item in the Network Mappings list and click the Edit button to
the right of the item.
2. The Edit Network Mapping dialog box opens. Choose the required item from the Target network
drop-down list and click Save.

l Delete an existing mapping: Hover the pointer over the required item in the Network Mappings list and
click the Delete icon (x) to the right of the item.

- 706 -
3. Click Next to go to the next page of the wizard.

- 707 -
Replication Job Wizard for VMware: Re-IP
Note
The Re-IP page is skipped if you have chosen an existing backup as the target for your replication job on the Source
wizard page.
To enable Re-IP rules for your replication job, do the following on the Re-IP page of the wizard:
1. Select Enable Re-IP.
2. Click the Select VMs link.
3. The Re-IP dialog box opens. In the list of your source VMs, select at least one, and close the dialog box.
4. You have the following options:
l Create a new rule:
a. Click Create new rule.
b. The New Re-IP Rule dialog box opens. Enter source and target settings for the Re-IP rule and click
Save.

Note
You can use wildcards for IP addresses. Refer to the “Failover Job Wizard for VMware: Re-IP” on
page 645 topic for details.
l Add an existing rule:
a. Click Add existing rule.
b. The Re-IP Rules dialog box opens. Select one or more appropriate Re-IP rules and close the
dialog box.

- 708 -
l Edit an existing Re-IP rule:
a. Hover the pointer over the required item in the Re-IP Rules list and click the Edit button to the right
of the item.
b. The Edit Re-IP Rule dialog box opens. Edit the required properties of the Re-IP rule and click Save.

l Delete an existing mapping: Hover the pointer over the required item in the Re-IP Rules list and click the
Delete icon to the right of the item.

- 709 -
 l To leave the list of existing Re-IP rules intact, go to the next page of the wizard.
5. Click Next to go to the next page of the wizard.

Notes
l Re-IP Rules enabled for replication jobs are only stubs for failover jobs. They do not work at the replication
stage.
l Re-IP rules that are enabled for your replication job can be used for creating the corresponding failover
jobs. Refer to “Failover Job Wizard for VMware: Re-IP” on page 645 for details.

- 710 -
Replication Job Wizard for VMware: Schedule
On the Schedule page of the wizard, select to run the backup job manually or schedule the job to run on a regular basis.
l “Disabling Scheduled Job Execution” below
l “Daily or Weekly Replication” below
l “Monthly or Yearly Replication” on the next page
l “Periodic Replication” on page 713
l “Chained Job” on page 713
l “Add Another Schedule” on page 714

Disabling Scheduled Job Execution

If you wish to start the job manually (without any schedule), select the Do not schedule, run on demand checkbox.

Daily or Weekly Replication

To run the job once a day, choose Run daily/weekly from the schedule drop-down list and do the following:
l Choose a time zone that should be used for the job start and end times from the time zone drop-down list.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

- 711 -
Monthly or Yearly Replication
To run the job monthly or yearly, choose Run monthly/yearly from the schedule drop-down list and do the following:
l Specify the job start schedule in the appropriate boxes.
l Specify the day and month when the job should be started in the Run every boxes.
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

- 712 -
Periodic Replication
To run the job multiple times per day, choose Run periodically from the schedule drop-down list and then choose a
time period from the appropriate boxes:
l Specify the time when the job should be started in the Starting at box.
l Specify the end time for the job in the Ending box. If the job has not completed by the time specified, the job will
be stopped.
l Select the days of the week during which the job will be started.
l If necessary, select the Effective from checkbox and pick the date when the schedule comes into effect. 

Chained Job
To run the job after a previous one has completed, choose Run after another job from the schedule drop-down list and
set the options as follows:
l After the job: Select a job after which the current job will be started.
l Run this job: Choose whether to run the current job immediately after the previous one has completed or within
a delay.
l After successful runs: If selected, the job will run if the previous one has completed successfully.
l After failed runs: If selected, the job will run if the previous one has failed.
l After stopped runs: If selected, the job will run if the previous one has been stopped.
l Effective from: If selected, the schedule will come into effect on the date picked.  

- 713 -
Add Another Schedule
If you want to have more than one schedule for your job, click Add another schedule and set it up as has been
described above.

- 714 -
Replication Job Wizard for VMware: Retention
NAKIVO Backup & Replication can create a recovery point (snapshot) on the replica VM after each job run. You can
specify the number of recovery points to be retained using the Grandfather-Father-Son (GFS) backup rotation scheme.
Up to 30 recovery points in total can be created on a replica VM.
Use the following options to specify a retention policy:
l Keep x last recovery points: Retains the specified number of last recovery points for each VM in the job.
l Keep one recovery point per day for x days: Retains one last recovery point per day for the specified number of
days.
l Keep one recovery point per week for x weeks: Retains the last available backup of every week for the specified
number of weeks.
l Keep one recovery point per month for x months: Retains the last available backup of every month for the
specified number of months.
l Keep one recovery point per year for x years: Retains the last available backup of every year for the specified
number of years. 

- 715 -
Replication Job Wizard for VMware: Options
On the Options page, set up replication job options as described in the sections below:
l “Job Options” on the next page
l “Job Name” on the next page
l “App-aware Mode” on the next page
l “Change Tracking” on page 718
l “Network Acceleration” on page 718
l “Encryption” on page 718
l “VM Verification” on page 719
l “Skip Swap Files and Partitions” on page 721
l “Skip Unused Blocks” on page 721
l “Replica Options” on page 722
l “Replica VM Disks” on page 722
l “Replica VM Names” on page 722
l “Pre and Post Actions” on page 723
l “Email Notifications” on page 723
l “Microsoft Exchange Server Logs Truncation” on page 724
l “Microsoft SQL Server Logs Truncation” on page 724
l “Pre Job Script” on page 724
l “Post Job Script” on page 725
l “Data Transfer” on page 726
l “Transport Mode” on page 726
l “Transporters” on page 727
l “Transporter Load” on page 727
l “Bandwidth Throttling” on page 727
l “Completing the New Replication Job Wizard for VMware” on page 728

- 716 -
Job Options
In this section, you can specify a name for your replication job, and enable/disable app-aware mode, change tracking,
network acceleration, encryption, “VM Verification” on page 43, and skipping swap files, partitions and unused blocks.

Job Name

Specify a name for the replication job.

App-aware Mode

With the App-aware mode selected, VM replication is performed using VMware Guest OS quiescing (which in turn relies
on Microsoft VSS) to ensure the consistency of application data. Select one of the options from the Change tracking
drop-down list:
l Enabled (proceed on error): With this option selected, NAKIVO Backup & Replication proceeds even if an
application quiescing error is encountered.
l Enabled (fail on error): With this option selected, NAKIVO Backup & Replication automatically fails the job if an
application quiescing error is encountered.
l Disabled: Selecting this option disables the app-aware mode.
Note
This option is not available for existing backups chosen as the target of replication on the Source wizard page.

- 717 -
Change Tracking

Select one of the options from the Change tracking drop-down list:

l Utilize VMware CBT: With this option selected, NAKIVO Backup & Replication enables the Change tracking
feature for source VMs. This feature quickly identifies which data blocks have changed since the last job run,
significantly increasing job speed. Click settings to specify the following options:
l On error:
l switch to proprietary method immediately/on the next retry/on the last retry: If VMware CBT
fails to provide data on changed blocks for a VM with this option selected, NAKIVO Backup &
Replication performs an incremental backup of the VM using the proprietary change tracking
technology.
l reset CBT on the next retry/on the last retry: If VMware CBT fails to provide data on changed
blocks for a VM with this option selected, NAKIVO Backup & Replication resets VMware CBT for the
VM.
l fail VM processing immediately/on the next retry/on the last retry: If VMware CBT fails to
provide data on changed blocks for a VM with this option selected, NAKIVO Backup & Replication
does not process the VM and states job failure (other VMs in the job are processed).
l Double-check changed blocks provided by CBT: With this option selected, NAKIVO Backup &
Replication runs a check on data blocks provided by VMware CBT to ensure that VMware CBT does
not overstate the amount of changed data.
l Use proprietary method: With this option selected, NAKIVO Backup & Replication performs incremental backups
using the proprietary change tracking technology. This feature requires reading the contents of all VM disks to
determine the data blocks that have changed since the last job run.
l No change tracking (always full): With this option selected, NAKIVO Backup & Replication always performs a full
VM backup of all source VMs. 
Note
This option is not available for existing backups chosen as the target of replication on the Source wizard page.

Network Acceleration

With Network acceleration enabled, NAKIVO Backup & Replication uses compression and traffic reduction techniques to
speed up data transfer. Select this option if you plan to replicate over WAN or slow LAN links.

Encryption

If Encryption is enabled VM data is protected with AES 256 encryption while traveling over the network. Data encryption
increases the replication time and CPU load on machines running Transporters. Select this option when replicating over
WAN without a VPN connection.
Note

- 718 -
You need at least one Transporter at source and target sites to enable encryption.

VM Verification

VM Verification allows you to check the integrity of the backup by starting it and interacting with it. For more details,
refer to the “VM Verification” on page 43 article.
You can choose one of the following VM Verification options: 
l Disabled: VM Verification is disabled.
l Screenshot verification: When enabled, the VM replica created by the job is verified: NAKIVO Backup &
Replication powers on this replica with networking turned off, takes a screenshot of the OS, then powers off the
VM replica. The VM screenshot will be included in email notifications (if they’re configured. See “Email
Notifications” on page 289.) and displayed on the Dashboard.  
l Boot verification: When enabled, the VM replica created by the job is verified: After VM replication is completed,
NAKIVO Backup & Replication recovers the VM using Flash VM Boot, disables networking to prevent network
connections, and verifies that system start is successful.
Important
VM verification requires VMware Tools to be installed on all VMs. 
After selecting the Screenshot verification option, do the following in the dialog box that opens:
l Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started on the
target container simultaneously. 
l Recovery time objective x minutes: Specify the amount of time allocated for verification of each VM backup. If a
VM OS does not start within the specified amount of time, verification will be considered failed.
l Screenshot delay x seconds: The amount of time that the product should wait after the Guest OS starts before
taking a screenshot.
Note
 The specified time must be sufficient to fully start the VM OS. Try increasing this amount if the default amount is not
sufficient.

- 719 -
After choosing Boot verification, do the following in the dialog box that opens: 
1. Provide a location of the VMs to be booted as described for the Screenshot verification option.
2. Set verification options:
l Verify not more than x VMs simultaneously: Specify the maximum number of VMs that can be started
on the Target Container simultaneously. 
l Recovery time objective: Specify the amount of time allocated for verification of each VM backup. If a VM

- 720 -
 OS does not start within the specified amount of time, verification will be considered failed.

Skip Swap Files and Partitions

When this option is enabled, NAKIVO Backup & Replication automatically skips swap files and partitions during the
backup process.
Note
This feature is not available for replication from backup jobs.

Skip Unused Blocks

When this option is enabled, NAKIVO Backup & Replication automatically skips unused disk blocks and blocks occupied
by deleted files during processing of source objects running Windows OS. This feature allows for reducing backup
storage space and object processing time.
Note
This feature is not available for replication from backup jobs.

- 721 -
Replica Options
In this section, you can choose a VM disk type and VM name. Proceed as described below.

Replica VM Disks

Choose one of the following options:

l Respect original VM disk type: With this option enabled, the created disk will be of the same type as that of the
source VM.
l Create only thin disks on target VMs: With this option enabled, only thin disks are created on replicas,
regardless of the disk types of the original source VM.

Replica VM Names

NAKIVO Backup & Replication allows you to change VM Replica names to easily distinguish between the VM Replicas
and the source VMs. By default, the text “-replica” is appended to the end of the VM Replica name.
To change VM Replica names:
In the Replica Options section, choose one of the following Replica VM names options:
l Append “-replica” in the end: Source VM names are used for replica names and “-replica” are added to the rep-
lica name.

- 722 -
 l Leave replica names as is: Replica names will be identical to the source VM names.
l Enter custom replica names: Enter custom names for replicas.

Pre and Post Actions

In the Pre and Post Actions section, you can set up email notifications, Exchange and SQL Server logs truncation, pre
and post job scripts.

Email Notifications

NAKIVO Backup & Replication can send email notifications about the job completion status to specified recipients. This
feature complements global notifications and allows you to configure notifications on a per-job level.
Note
To enable this option, make sure your Email settings are configured. 
To send email notifications, do the following: 
In the Pre and Post Actions section:
1. Select Send job run reports to.
2. Specify one or more email addresses in the text field. Use semicolons to separate multiple email addresses.

- 723 -
Microsoft Exchange Server Logs Truncation

NAKIVO Backup & Replication allows you to delete (aka truncate) Microsoft Exchange Server logs on the source VMs
after job completion.
To set up Microsoft Exchange log truncation, do the following:
1. In the Pre and Post Actions section, select the Truncate Exchange logs option.
2. In the Exchange Log Truncation dialog box that opens, select the checkboxes next to the VMs running Microsoft
Exchange and then select the credentials next to each VM. These credentials are used to log into the VMs that
you have selected.
Note
This option is not available for existing backups chosen as the target of replication on the Source wizard page.

Microsoft SQL Server Logs Truncation

NAKIVO Backup & Replication allows you to delete (aka truncate) Microsoft SQL Server logs on the source VMs after job
completion.
To set up Microsoft SQL log truncation, do the following:
1. In the Pre and Post Actions section, select the Truncate SQL Server logs option.
2. In the SQL Server Log Truncation dialog box that opens, select the checkboxes next to the VMs running
Microsoft SQL Server and then select the credentials next to each VM. These credentials are used to log into the
VMs that you have selected.
Note
This option is not available for existing backups chosen as the target of replication on the Source wizard page.

Pre Job Script

To run a script before the product begins replicating VMs:

1. Place a script file on the machine where the Director is installed.
2. In the Pre and Post Actions section, select the Run local pre job script option.
3. Specify the following parameters in the dialog box that opens:
1. Script path: Specify a local path to the script on the machine where the Director is installed. Script
interpreter should be specified.
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
2. Job behavior: Choose one of the following job behaviors in relation to script completion:
l Do not wait for the script to finish: With this option selected, the product runs the script and
starts replicating VMs at the same time.
l Wait for the script to finish: With this option selected, VM replication is started only after the script
is completed.

- 724 -
 3. Error handling: Choose one of the following job behaviors in relation to script failure:
l Fail the job on script failure: With this option selected, the job is failed and VM replication is not
performed if the script has failed.
l Continue the job on script failure: With this option selected, the job performs VM replication even
if the script has failed.

Post Job Script

To run a script after the product has finished backing up all VMs:
1. Place a script file on the machine where the Director is installed.
2. In the Pre and Post Actions section, select the Run local post job script option.
3. Specify the following parameters in the dialog box that opens:
1. Script path: Specify a local path to the script on the machine where the Director is installed. Script
interpreter should be specified.
Example (Windows): cmd.exe /c D:\script.bat
Example (Linux): bash /root/script.sh
2. Job behavior: Choose one of the following job behaviors in relation to script completion:
l Wait for the script to finish: With this option selected, the job is in the “running” state until the
script is completed.
l Do not wait for the script to finish: With this option selected, the job is completed even if the
script execution is still in progress.
3. Error handling: Choose one of the following job behaviors in relation to script failure:
l Continue the job on script failure: With this option selected, script failure does not influence the
status of the job.
l Fail the job on script failure: With this option selected and the script has failed, the job status will
be set to “failed” even if VM replication has been successful.

- 725 -
Data Transfer
In the Data Transfer section, you can choose a transport mode and a Transporter to be used for reading data from
source VMs, and configure bandwidth throttling. Proceed as described below.

Transport Mode

To select a transport mode, in the Data Transfer section, choose a transport mode for retrieving VM data:
l Automatic selection: With this option selected, NAKIVO Backup & Replication automatically selects the best
transport mode available:
l If the source Transporter is installed on a VM, NAKIVO Backup & Replication tries to use transport modes in
the following order: Hot Add > SAN > LAN.
l If the source Transporter is installed on a physical machine, NAKIVO Backup & Replication tries to use
transport modes in the following order: SAN > Hot Add > LAN.
l SAN only: With this option selected, NAKIVO Backup & Replication only uses direct SAN access to retrieve VM
data. If direct SAN access to VM data is not available, the job will fail.
l Hot-add only: With this option selected, NAKIVO Backup & Replication only uses Hot-add to retrieve VM data. If
direct Hot-add is not available, the job will fail.
l LAN only: With this option selected, NAKIVO Backup & Replication only retrieves VM data via LAN.
Note

- 726 -
This option is not available for existing backups chosen as the target of replication on the Source wizard page.

Transporters

By default, the product automatically determines the Transporter to be used to read data from the source VM.
However, you can manually specify the Transporters to be used for the job by choosing one of the following
Transporters options in the Data Transfer section:
l Automatic selection: The product automatically determines the Transporters that are the closest to source and
target hosts.
l Manual - configured for all VMs: Select this option to manually specify a single source and a single target
Transporter to be used for data transfer by the job.
l Manual - configured per host: Select this option to manually specify Transporters for all source and target hosts.

Transporter Load

You can limit the maximum number of transporter tasks used by the job. By default, it is set to 3 concurrent tasks.
To change the default number of tasks, do the following:
1. In the Data Transfer section, select the checkbox next to Limit transporter load to.
2. Specify the number of concurrent tasks in the corresponding field.

Bandwidth Throttling

To regulate the speed of data transfer over the network for your replication job:
1. For the Bandwidth throttling option, choose Enabled.
Note
If bandwidth throttling is disabled for the current job, global bandwidth rules may still apply to your job. Refer to
“Bandwidth Throttling” on page 283 for details.
2. Click the settings link that becomes available.
3. The Job Bandwidth Rules dialog box opens displaying the list of available rules. You have the following options:
l Create a new bandwidth rule for your replication job:
a. Click the Create New Rule button.
b. The New Bandwidth Rule dialog box opens. Refer to the “Bandwidth Throttling” on page 283 topic
for details on creating a bandwidth rule.
c. Click Save.
l Activate an existing bandwidth rule for your job: Select the checkbox to the left of the required bandwidth
rule. To deactivate a bandwidth rule for your job, deselect the corresponding checkbox.
l Edit a bandwidth rule: Click the Edit link for a bandwidth rule and modify it in the Edit Bandwidth Rule
dialog box that opens.
l Disable a bandwidth rule: Click the Disable link. The bandwidth rule will be disabled for all jobs.

- 727 -
 l Remove a bandwidth rule: Click the Remove link and then click Delete to confirm your operation.

Completing the New Replication Job Wizard for VMware

Click Finish or Finish & Run to complete job creation.
Note
If you click Finish & Run, you will have to define the scope of your job. Please refer to “Running Jobs on Demand” on
page 97 for details.

- 728 -
Staging (Seeding) VM Replication
With VMs usually being large, the initial (full) VM replication can be slow and time-consuming, and can put an
undesirable load on the network. Perform staged replication to speed up the initial VM replication and save network
bandwidth. Staging requires the transfer of VMs to the target site using a removable medium (such as an external USB
hard drive). You can then create a new replication job that will use the transferred VMs as a target and perform only
incremental replication.
To stage VM replication, follow the steps below:
1. Put VMs that you want to replicate on a removable medium (such as an external USB hard drive) using backup,
replication, or any other method.
2. Transfer the medium to the target location.
3. Add (recover) the VMs to the desired server and datastore.
4. Create a new replication job and map the source VMs to the transferred VMs.

- 729 -
Multi-Tenant Mode
This section covers the following topics:
l “Tenant Creation” on page 731
l “Tenant Configuration” on page 738
l “Tenant Management” on page 739
l Granting Self-Service Access

- 730 -
Tenant Creation
This section covers the topics describing the tenant creation process in NAKIVO Backup & Replication.
To create a new tenant, follow the steps below:
1. Log in to NAKIVO Backup & Replication as a Master Admin.
2. Click Create New Tenant.

3. Complete the wizard as described in the topics below to finish the tenant creation process:
l “Tenant Creation Wizard: Tenant” on page 732
l “Tenant Creation Wizard: Inventory” on page 734
l “Tenant Creation Wizard: Transporters” on page 735
l “Tenant Creation Wizard: Repositories” on page 736
l “Tenant Creation Wizard: Users” on page 737

- 731 -
Tenant Creation Wizard: Tenant
On this page of the wizard, you can provide a name for the tenant, assign licenses to the tenant, and enter contact
information for the tenant.
Proceed as follows:
1. To add a tenant logo, click Change tenant logo, navigate to a new image, select it, and click Open. The uploaded
image is resized and displayed on the right side of the page.
2. In the Tenant name field, enter a name for the tenant. By default, the tenant name is displayed under the tenant
logo. If you do not want the tenant name to be displayed, deselect the Display tenant name checkbox.
3. Optionally, in the Labels field, select the tags you want to assign to the tenant. Additionally, you can enter the
name of the new label in the field and click Create new label to create and add it to the Labels field automatically.
4. In case the Trial or Subscription license is installed, do the following:
a. In the Workloads allocated field, enter the number of workloads you want to assign to the tenant.
b. In the Microsoft 365 users allocated field, enter the number of Microsoft 365 users you want to assign to
the tenant.
5. In case the Perpetual license is installed, do the following:
a. In the Sockets allocated field, enter the number of sockets you want to assign to the tenant.
b. In the Physical servers allocated field, enter the number of physical server licenses you want to assign to
the tenant.
c. In the Physical workstations allocated field, enter the number of physical workstation licenses you want
to assign to the tenant.
d. In the Microsoft 365 users allocated field, enter the number of Microsoft 365 users you want to assign to
the tenant.
e. In the Oracle databases allocated field, enter the number of Oracle Database licenses you want to assign to
the tenant.
6. Optionally, in the Contact email field, enter the email address of the tenant.
7. Optionally, in the Contact phone field, enter the phone number of the tenant.
8. Optionally, in the Website field, enter the website URL of the tenant.
9. Optionally, in the Address field, enter the address of the tenant.
10. Click Next to proceed to the Inventory page.

- 732 -
- 733 -
Tenant Creation Wizard: Inventory
On this page, you can assign inventory items to the tenant. Proceed as follows:
1. Choose the platform to display the items added to the inventory. All is selected by default.
Note
Items that are assigned to other tenants are visible, but cannot be selected.
2. Optionally, you can filter the inventory tree by entering a string into the Search box. You can enter either a part or
the entire name of the item.
3. Select the items you want to be assigned to the tenant. The selected items appear in the right pane.

4. Click Next to proceed to the Transporters page.

- 734 -
Tenant Creation Wizard: Transporters
On this page of the wizard, you can assign the Transporters that the tenant will be able to use for backup, recovery, and
replication jobs. Proceed as follows:
1. In the Search field, you can enter either a part or the entire name of the Transporter to find the specific ones you
need.
Note
If you assigned an inventory item with the dependant Transporter to the tenant on the Inventory page of the
wizard, that Transporter would not be selected automatically, and it cannot be deselected. If an inventory item
with the dependant Transporter was not assigned to a tenant, that Transporter cannot be selected on this page.
2. On the left pane of the screen, you can select the Transporters to be assigned to the tenant. The following
information is available
1. Name: Name of the Transporter.
2. Assigned tenants: The number of tenants assigned to the Transporter. Multiple tenants can use the same
Transporter without accessing each other's data.
3. Maximum load per tenant: The maximum number of tasks that the Transporter is able to perform at the
same time per each assigned tenant.
3. The selected Transporters appear in the right pane. Click Next to proceed.

- 735 -
Tenant Creation Wizard: Repositories
On this page of the wizard, you can assign Backup Repositories that the tenant will be able to use for backup, recovery,
and replication jobs. Note that a single repository cannot be used by multiple tenants Proceed as follows:
1. In the Search field, you can enter either a part or the entire name of the Backup Repository to find the specific
ones you need.
Note
If the dependent Transporter was not chosen on the Transporters page of the wizard, the Backup Repositories
assigned to this Transporter would not be available for selection.
2. On the left pane of the screen, you can select the Backup Repositories to be assigned to the tenant. The following
information is available
1. Name: Name of the Backup Repository.
2. Free Space: The amount of free space available on the Backup Repository.
The selected Backup Repositories appear in the right pane.

3. Click Next to proceed to the next page of the wizard.

- 736 -
Tenant Creation Wizard: Users
On this page of the wizard, you can create local users or import Active Directory users for the tenant. The added users
can use the product and have access to the allocated resources. Do the following:
1. In the lower-left pane of the screen, click Create local user to create a new local user for the tenant. 
2. If you have successfully configured AD integration, you can click Add AD user to import AD user for the tenant.
3. Once you’re done, click Finish to complete Tenant Creation Wizard.

- 737 -
Tenant Configuration
After creating a new tenant, click the tenant to open the initial Tenant Configuration Wizard which will guide you
through the tenant setup process. Refer to “First Steps with NAKIVO Backup & Replication” on page 88 for a description
of the initial configuration wizard.

- 738 -
Tenant Management
This section covers the following topics:
l “Using Filters” on page 740
l “Using Labels” on page 742
l “Viewing Tenant Information” on page 745
l “Opening Tenant Dashboard” on page 746
l “Disabling Tenants” on page 747
l “Editing Tenants” on page 748
l “Deleting Tenants” on page 749

- 739 -
Using Filters
l About Filters
l Applying Filters
l Dismissing Filters

About Filters
NAKIVO Backup & Replication comes with four built-in filters that allow you to quickly display tenants according to their
state. The following filters are available:
l OK: Displays tenants that have no errors and notifications.
l Warning: Displays only tenants that have notifications.
l Error: Displays only tenants that have errors.
l Enabled: Displays only enabled tenants.
l Disabled: Displays only disabled tenants.

Applying Filters
To apply a filter, click on the filter name.

The filters that are currently applied are displayed under the Active Filters.

Dismissing Filters
To dismiss a filter, click the filter name under Active filters.

- 740 -
- 741 -
Using Labels
l About Labels
l Creating Labels
l Assigning Labels to Tenants
l Editing Label Names
l Deleting Label

About Labels
With NAKIVO Backup & Replication, you can create custom labels and assign them to tenants. Assigning a label to a
tenant allows you to quickly sort existing tenants into different categories, such as location, SLA level, etc.

Creating Labels
To create a new label, click the Plus icon next to Labels and enter a name for the new label, and press the Enter key.

You can also create a new label whencreating a new tenant.

- 742 -
Assigning Labels to Tenants
You can assign a label to a tenant either during the tenant creation or by editing the tenant.

Editing Label Names

To change a label name, do the following:
1. Hover over the label.
2. Click the Edit icon.

3. Enter the new label name and press the Enter key.

Deleting Labels
To permanently delete a label, do the following:
1. Hover the mouse pointer over a label.
2. Click the Delete icon.

- 743 -
3. In the dialog box that opens, click Delete to confirm that you wish to permanently delete the label

- 744 -
Viewing Tenant Information
To view tenant information, hover over the tenant and click on the Info button.

The tenant information is displayed.

- 745 -
Opening Tenant Dashboard
In the multi-tenant mode, you need to open the tenant dashboard to perform tenant configuration, create jobs and
groups for the tenant, and recover files and emails. To open a tenant dashboard, simply click the tenant.

Returning Master Admin Dashboard

To return to the Master Admin dashboard, click Tenants in the navigation bar.

- 746 -
Disabling Tenants
In multi-tenant mode, you can disable a tenant to temporarily stop delivering backup, replication, and recovery services
for that tenant. After disabling a tenant:
l Tenant admin and tenant guest will not be able to log in to the self-service interface. A message saying that the
service has been disabled will be displayed after login attempts.
l Existing jobs will not be run on schedule.
l All currently running jobs will be allowed to complete.
To disable a tenant, hover over the tenant and click the Disable button.

- 747 -
Editing Tenants
To edit a tenant, do the following:
1. Hover over a tenant box and click the Edit icon.

2. In the Edit dialog that opens, make the required changes and click Save.

- 748 -
Deleting Tenants
To permanently delete a tenant from the product, hover over a tenant and click the Delete icon.

The tenant will be permanently deleted from NAKIVO Backup & Replication.
Tenant Transporters are not uninstalled and the Tenant Backup Repositories are not removed.

- 749 -
Granting Self-Service Access
In the multi-tenant mode, you can provide tenants with access to their dashboards. By default, a tenant admin account
is automatically created when you create a new tenant. The tenant admin has full control over the product features
inside the tenant dashboard (such as edit and update tenant inventory, Transporters, and Backup Repositories, and
create and manage jobs and groups). For each tenant, one guest account can also be created. The tenant guest has
limited permissions inside the tenant and can only generate job and group reports by default. To provide a tenant with
access to the self-service interface, send the following information to the tenant:
l Link to NAKIVO Backup & Replication Director
l Tenant login
l Tenant password

- 750 -
Integration and Automation
This section contains the following topics:
l “Command Line Interface” on page 752
l “Automation with HTTP API” on page 764
l “Aptare IT Analytics Integration” on page 765

- 751 -
Command Line Interface
This section covers the following topics:
l “Using Command Line Interface” on page 753
l “Available Commands” on page 755
l “Exit Codes” on page 763

- 752 -
Using Command Line Interface
l “Operation Modes of Command Line Interface” below
l “Using Command Line Interface Locally” below
l “Using Command Line Interface Remotely” below
l “Using Command Line Interface in Multi-Tenant Mode” on the next page

NAKIVO Backup & Replication allows you running actions from the product’s command line interface (CLI).
In case credentials are configured for the product, running an action via CLI requires providing administrator credentials
as arguments, namely, --username [login] --password [password], where [login] is the
administrator user name and [password] is the administrator password.

Operation Modes of Command Line Interface

You can run CLI in either of the following modes:
l Interactive mode. This allows you to use a single login for a session. When opened in the interactive mode, CLI
allows you executing commands without dashes.
To open CLI in the interactive mode, enter cli.bat --interactive --username [login] --
password [password] and press Enter. To exit the CLI interactive mode, enter Ctrl-C.
l Non-interactive mode. This requires entering your credentials for each command. You will have to enter dashes
before commands. For example: cli.bat --username [login] --password [password] --
inventory-list

Using Command Line Interface Locally

To use CLI on the machine where NAKIVO Backup & Replication Director is installed, follow the steps below:
1. Run the CLI executable:
l If NAKIVO Backup & Replication is installed on a Windows OS, run the cli.bat file located in
the bin folder inside the product installation folder ("C:\Program Files\NAKIVO Backup &
Replication" by default).
l If NAKIVO Backup & Replication is installed on a Linux OS, run the cli.sh file located in
the director/bin folder inside the product installation folder (/opt/nakivo/ by default).
2. Run available commands.

Using Command Line Interface Remotely

To use CLI from a remote machine, follow the steps below:
1. Copy the CLI executable and .jar files to the machine from where you plan to use the CLI:
l If NAKIVO Backup & Replication is installed on a Windows OS, copy the cli.bat and cli.jar files
located in the bin folder inside the product installation folder ("C:\Program Files\NAKIVO

- 753 -
 Backup & Replication" by default).
l If NAKIVO Backup & Replication is installed on a Linux OS, copy the cli.sh and cli.jar files located in
the director/bin folder inside the product installation folder (/opt/nakivo/ by default).
2. On the machine from where you plan to use the CLI, configure the PATH system variable as described
at http://java.com/en/download/help/path.xml
3. Run commands using the following format: <command> <host> <port> <username> <password>
Example
To get a list of jobs of the product which is installed on the machine with the 192.168.10.10 IP address, uses the
4443 port number for the Director Web HTTPS port, and has “admin” as login and password for the product’s web
UI, run the following command: --job-list --host 192.168.10.10 --port 4443 --username
admin --password admin

Using Command Line Interface in Multi-Tenant Mode

Triggering an action inside a tenant in the multi-tenant mode via command line interface requires providing a tenant ID
as an argument:
cli.bat --repository-detach [repo_id] --username [login] --password 
[password] --tenant [tenant-id]

- 754 -
Available Commands
l “Help” on the next page
l “General help” on the next page
l “Job Management” on the next page
l “List all jobs” on the next page
l “Start a job” on the next page
l “Stop a job” on the next page
l “Disable a job” on the next page
l “Disable multiple jobs” on the next page
l “Enable a job” on the next page
l “Enable multiple jobs” on the next page
l “Generate a report for a job” on the next page
l “Return information about a job” on page 757
l “Inventory” on page 757
l “List all inventory items” on page 757
l “Update all inventory items” on page 757
l “Update an inventory item” on page 758
l “Return information about an inventory item” on page 758
l “Transporters” on page 758
l “List all transporters” on page 758
l “Update all transporters” on page 758
l “Update a transporter” on page 758
l “Return information about a transporter” on page 758
l “Repositories” on page 759
l “List all repositories” on page 759
l “Update all repositories” on page 759
l “Update a repository” on page 759
l “Detach a repository” on page 759
l “Attach a repository” on page 759
l “Start repository maintenance” on page 759
l “Stop repository maintenance” on page 759
l “Return information about a repository” on page 759
l “Support” on page 760
l “Generate a support bundle” on page 760
l “Licensing” on page 760
l “Get the current license information” on page 760
l “Replace the current license with a new license file” on page 761

- 755 -
 l “Multi Tenancy” on page 761
l “List all tenants” on page 761
l “Disable a tenant” on page 761
l “Enable a tenant” on page 761
l “Return information about a tenant” on page 761
l “Create a support bundle for master admin level” on page 761
l “Miscellaneous” on page 761
l “Get the CLI version” on page 761
l “Run a command in the debug mode” on page 762
You can run CLI commands either in interactive or non-interactive mode. Refer to the Operation Modes of Command
Line Interface subsection of the “Using Command Line Interface” on page 753 topic. 
Use either long or short form of the commands*.

Command Long form Short form  Output

Help
l Command name
General help cli.bat --help cli.bat -h
l Description

Job Management
l Job ID
l Job name
List all jobs cli.bat --job-list cli.bat -jl
l Current job status
l Job last run result

Start a job cli.bat --job-start [job_id] cli.bat -jr [job_id]

Stop a job cli.bat --job-stop [job_id] cli.bat -js [job_id]

Disable a job cli.bat --job-disable [job_id] cli.bat -jd [job_id]

Disable multiple cli.bat --job-disable [job_id1]  cli.bat -jd [job_id1] [job_

jobs [job_id2] [job_id3] ... [job_idX] id2] [job_id3] ... [job_idX]

Enable a job cli.bat --job-enable [job_id] cli.bat -je [job_id]

Enable multiple cli.bat --job-enable [job_id1]  cli.bat -je [job_id1] [job_

jobs [job_id2] [job_id3] ... [job_idX] id2] [job_id3] ... [job_idX]

Generate a
cli.bat --job-report [job_id] cli.bat -jp [job_id]
report for a job

- 756 -
 Command Long form Short form  Output

l The command with

l The command with no no arguments
arguments creates the job creates the job
report and saves it to the report and saves it
current directory. to the current
l To save the report to other directory.
directory: cli.bat --job- l To save the report
report [job_id] --save-to to other directory:
[dir_path] cli.bat -jp [job_id] -f
l To send the report to [dir_path]
default email(s): cli.bat. -- l To send the report
job-report [job_id] --send- to default email(s):
by-email cli.bat. -jp [job_id] -
l To send the report to eml
other email: cli.bat. --job- l To send the report
report [job_id] --send-by- to other email:
email [email_address] cli.bat. -jp [job_id] -
eml [email_address]

l Job ID
Return inform- l Job name
ation about a cli.bat --job-info [job_id] cli.bat -ji [job_id]
job
l Current job status
l Job last run result

Inventory
l Item ID
l Item IP/host name
l Item type (host/vCenter)
List all inventory
cli.bat --inventory-list cli.bat -il l Item children count (X
items
hosts, E VMs)
l Item current state
l Item current status

Update all
cli.bat --inventory-update cli.bat -iu
inventory items

- 757 -
 Command Long form Short form  Output

Update an cli.bat --inventory-update [item_

cli.bat -iu [item_id]
inventory item id]

l Item ID
l Item IP/host name
Return inform- l Item type (host/vCenter)
ation about an cli.bat --inventory-info [item_id] cli.bat -ii [item_id] l Item children count (X
inventory item hosts, E VMs)
l Item current state
l Item current status

Transporters
l Transporter ID
l Transporter IP/host
name
l Transporter current load
List all trans-
cli.bat --transporter-list cli.bat -trl l Transporter maximum
porters
load
l Transporter current state
l Transporter current
status

Update all trans-

cli.bat --transporter-update cli.bat -tru
porters

Update a trans- cli.bat --transporter-update cli.bat -tru [transporter_

porter [transporter_id] id]

l Transporter ID
l Transporter IP/host
name
Return inform- l Transporter current load
cli.bat --transporter-info
ation about a cli.bat -tri [transporter_id] l Transporter maximum
transporter [transporter_id]
load
l Transporter current state
l Transporter current
status

- 758 -
 Command Long form Short form  Output

Repositories
l Repository ID
l Repository name
l Assigned transporter
l Backup count
l Free space
List all repos-
cli.bat --repository-list cli.bat -rl  l Attached or detached
itories
l Consistent or
inconsistent
l Repository current state
l Repository current
status

Update all repos-

cli.bat --repository-update cli.bat -ru
itories

Update a repos- cli.bat --repository-update [repo_

cli.bat -ru [repo_id]
itory id]

Detach a repos- cli.bat --repository-detach [repo_

cli.bat -rd [repo_id]
itory id]

Attach a repos- cli.bat --repository-attach [repo_

cli.bat -ra [repo_id]
itory id]

cli.bat --repository-maintenance cli.bat -rm [repo_id]

[repo_id] [parameter] [parameter]
Start repository Parameters: Parameters:
maintenance l --selfheal l --selfheal
l --verify l --verify
l --spacereclaim l --spacereclaim

Stop repository cli.bat --repository-maintenance-

cli.bat -rms [repo_id]
maintenance stop [repo_id]

Return inform- l Repository ID

ation about a cli.bat --repository-info [repo_id] cli.bat -ri [repo_id] l Repository name
repository l Assigned transporter

- 759 -
Command Long form Short form  Output

l Backup count and free

space
l Attached or detached
l Consistent or
inconsistent
l Repository current state
l Repository current
status

Support
cli.bat -bc
cli.bat --bundle-create l The command with
l The command with no no parameters will
parameters will create a create a support
support bundle and save it bundle and save it
in the current directory. in the current
l To save the bundle to directory.
other directory: cli.bat -- l To save the bundle
bundle-create --save-to to other
Generate a sup-
[dir_path] directory: cli.bat -bc
port bundle
l To send the bundle to -f [dir_path]
support over email: cli.bat l To send the bundle
--bundle-create --send-to- to support over
support email: cli.bat -bc -
l To send the bundle to sup
other email: cli.bat -- l To send the bundle
bundle-create --send-by- to other
email [email_address] email: cli.bat -bc -
eml [email_address]

Licensing
Get the current
license inform- cli.bat --license-info cli.bat -li
ation

- 760 -
 Command Long form Short form  Output

Replace the cur-

rent license with
cli.bat --license-replace [file_path] cli.bat -lin [file_path]
a new license
file

Multi Tenancy
l Tenant ID
l Tenant name
l Allocated items type and
List all tenants cli.bat --tenant-list cli.bat -tl 
count
l Tenant status
l Enabled or disabled

cli.bat --tenant-disable [tenant_

Disable a tenant cli.bat -td [tenant_id]
id]

cli.bat --tenant-enable [tenant_

Enable a tenant cli.bat -te [tenant_id]
id]

l Tenant ID
l Tenant Account ID
Return inform- l Tenant name
ation about a cli.bat --tenant-info [tenant_id] cli.bat -ti [tenant_id] l Allocated items type and
tenant count
l Tenant status
l Enabled or disabled

l Generate the support l Generate the

bundle for master level support bundle for
only: cli.bat --bundle- master level only:
Create a sup-
port bundle for create cli.bat -bc
master admin l Generate the support l Generate the
level
bundle with all tenants support bundle
logs: cli.bat --bundle-create with all tenants
--include-tenants logs: cli.bat -bc -ite

Miscellaneous
Get the CLI ver-
cli.bat --version -
sion

- 761 -
 Command Long form Short form  Output

The command returns the CLI

version which is equal to the full
version of NAKIVO Backup &
Replication.

cli.bat --repository-info [repo_id]

--debug
This is an option that can be
Run a com- added to any other CLI
mand in the cli.bat -ri [repo_id] --debug
debug mode command.
With the debug mode turned on,
the commands will return the full
error text.

*Examples are given for Windows OS.

- 762 -
Exit Codes
NAKIVO Backup & Replication CLI provides the following exit codes:
l 0: Normal
l 1: Unknown command
l 2: Cannot login
l 3: Command failed
l 4: Local failure
l 5: No arguments

- 763 -
Automation with HTTP API
HTTP API allows you to run common NAKIVO Backup & Replication commands outside of the product web interface.
The API is JSON-RPC based. For detailed request and response syntax, refer to API Reference. 

- 764 -
Aptare IT Analytics Integration
APTARE IT Analytics is a storage resource management platform for integrating storage and backup solutions. The
integration with NAKIVO Backup & Replication is based on an APTARE data collector that sends storage component
information to the system’s platform. The steps for integrating NAKIVO Backup & Replication with APTARE IT Analytics
are as follows:
1. On the machine where NAKIVO Backup & Replication is deployed, do the following:
1. Install APTARE StorageConsole Data Collector with NAKIVO connector. 
2. When the installation has been successfully completed, make sure that the APTARE Agent service is
running.
2. Open your NAKIVO Backup & Replication instance and run your backup jobs.
3. Log in to the APTARE portal. 
4. Go to the ADMIN tab and take the following steps: 

a. Add a Collector. For details, refer to the Managing and Monitoring Data Collection subsection of the
APTARE IT Analytics User Guide.

b. Add a NAKIVO Backup & Replication data protection policy with a connection to your NAKIVO Backup &
Replication instance. For details, refer to the Pre-Installation Setup for Generic Backup subsection of the
APTARE IT Analytics User Guide.

- 765 -
c. Run your policy.

- 766 -
5. Go to the REPORTS tab in the APTARE portal and take the following actions:

a. Create and configure the report for your backup job the following way:
i. Right-click on your report folder and select New SQL Template.

ii. Select the template designer that will be used to gather user input for the report.

iii.  Build an SQL query for your machine backup report or daily backup report, use either:

- 767 -
 Daily Backup Report
select * from SDK_V_NKVO_NBR_DAILYBACKUP where (creation_date
between ${startDate} and ${endDate}) and (server_instance_id in
(select server_instance_id from apt_v_server_instance where
server_id in (${hosts}))) order by report_id desc

Machine Backup Report

select * from SDK_V_NKVO_NBR_MACHINEBACKUP where (creation_date
between ${startDate} and ${endDate}) and (server_instance_id in
(select server_instance_id from apt_v_server_instance where
server_id in (${hosts}))) order by report_id desc

iv. Change formatting options if necessary.

- 768 -
 v. Provide a name and description of the report and select users to share it with. Click Finish.

b. Double-click on the report. In the dialog box that opens, enter the necessary time and report scope. Click
Generate to generate your report. For details, refer to the Generating and Maintaining Reports subsection
of the APTARE IT Analytics User Guide.

- 769 -
To know more about APTARE IT Analytics, refer to the APTARE IT Analytics User Guide.

- 770 -