v8.1 Release Notes

Release Date: 5 November 2018

New Features

Policy-Based Data Protection

NAKIVO Backup & Replication v8.1 revolutionizes the way companies manage their backup operations by introducing Policy-Based Data Protection. Set up policies for your data protection processes and have the corresponding VMs protected automatically. When you add VMs that match your specified criteria, NAKIVO Backup & Replication protects them automatically.

Universal Object Recovery

NAKIVO Backup & Replication v8.1 adds further versatility by introducing Universal Object Recovery. Whenever important application data gets deleted or modified, you can mount VM disks from a backup to your VM and use native application management tools to recover the data to your production database.


  • Installation of a TLS/SSL certificate is provided to allow for a secure HTTPS connection for your instance of NAKIVO Backup & Replication

  • Multiple jobs can be enabled/disabled using CLI and API

  • NAKIVO Backup & Replication system events can be filtered by dates and a search string

  • With drill-down approach implemented, system settings can be accessed and identified easily

  • Apache Tomcat engine is upgraded to Version 9.0 thereby fixing vulnerability issues

  • Alarms for site recovery job are extended

  • Running jobs for failed and stopped VMs propagates this scope to the chained jobs

  • An option added to system settings for checking RAM on target host to be sufficient for replication and recovery jobs

  • Min free space can be configured for the product folder in the expert mode

  • A progress bar is implemented for reflecting backup export in the product activities

  • A possibility added for removing all events in the expert mode

  • The product migrated to VDDK 6.7.1 to improve support of vSphere 6.7 Update 1

Fixed Issues

  • Adding Hyper-V server to a repository fails with Server is not reachable error message

  • Disabled jobs are displayed as scheduled in CLI

  • Startup type of Hyper-V Transporter service is set to Manual

  • AWS minimum permissions that should be granted to NAKIVO Backup & Replication are modified

Known Issues

  • After the update you can see incorrect maintenance end date due to missing information in the old license. Please contact support@nakivo.com to obtain an updated license

  • You may be unable to update from v7.2 and older because of missing information in the old license. Please contact support@nakivo.com to obtain an updated license

  • CBT Driver for Hyper-V 2012 (R2) is not available (this feature will be available in one of the next releases)

  • File recovery may skip empty folders from NTFS file system in certain configurations

  • With backup copy jobs, the value of the job speed on dashboard can vary from the value provided via bandwidth throttling settings

  • Incorrect error is displayed when attempting to run Re-IP on Ubuntu 14.04 while there is no IP address

  • If DNS Server field is empty in the Re-IP rule, this may lead to creation of an empty DNS record in the target VM

  • Encrypted repositories are not supported with RHEL/SLES since required packages are missing

  • NFS datastores cannot be used as target datastores for flash VM boot or screenshot verification

  • Replica/recovered VM disks are always created as Lazy zeroed if source VM had both Lazy and Eager zeroed disks

  • Exchange OLR: Emails that were forwarded to recipient as attachments cannot be recovered from the mailbox

  • Linux transporter should be used for replicating/backing up VMs with SATA disks

  • Exchange Public Folders are not supported for granular recovery

  • Default backup repository of the Virtual Appliance cannot be extended beyond 16 TB

  • Application-aware processing for AWS EC2 may freeze when using domain credentials

  • Replica AMIs and recovered EC2 instances have "Platform" attribute set to "Other Linux" due to AWS API limitations

  • Active Directory printers are skipped during recovered items import

  • First Class Disk (FCD) cannot be backed up if it is not attached to any VM

  • VSS quiescing is not supported for encrypted VMs

  • HotAdd is not supported if the VA with NAKIVO Backup & Replication has the same BIOS UUID as the VM to be backed up or replicated

  • Swap file skipping is not supported for the Dynamic Disks

  • If the same Hyper-V VM is processed by multiple jobs simultaneously, some of the jobs may fail to create VM checkpoint

  • Recovery job on Hyper-V does not allow creating VMs with identical names

  • Backup and replication of Hyper-V VMs with shared drives are not supported

  • Linux swap in files currently is not skipped. Only Linux swap partitions are supported

  • Older versions of ESXi (4.1, 5.0, 5.1) require an installation of the special Transporter

  • File recovery fails if the HDD's Virtual Device Node is SATA and Transporter proceeding the job is installed on Windows

  • File Recovery from Windows dynamic disks is not supported for the following platforms:


    • Red Hat Enterprise Linux 7.x

  • If Transporter is installed on Windows 2008R2 or later, it is recommended to set SAN Policy to OfflineShared or OfflineAll

  • Deployment of source Transporter and source VM from the same Windows VM template may cause backup corruption in HotAdd mode

  • Hyper-V on Windows Nano Server cannot be added to NAKIVO Backup & Replication Inventory

  • It is possible to downgrade Western Digital NAS package to an older version, which leads to lost configuration

  • SQL Server object recovery does not work with databases that have memory-optimized data filegroup containers

  • SQL Server object recovery cannot recover system-versioned table if table with such name already exists in the SQL Server

  • Application log truncation is not available on VMware ESXi 4.1

  • Windows transporter AMI cannot be launched into Amazon EC2 instances with enhanced networking

  • VSS quiescing is not available for Microsoft Windows 7 on some platforms

  • Restarting a file-recovered VM with dynamic disks mounted to Transporter may fail the dynamic disks to be recognized

  • Issues with Integration Services for Ubuntu 12.04 Server (x64), and SLES 11 SP3/SP4 (x64) prevent connecting to source VMs running on Hyper-V

  • VMs that were recovered from encrypted source VMs with NVRAM settings modified may fail to boot

  • Bandwidth throttling is not applicable for backing up Instances to local Amazon EC2 Regions with a single Transporter

  • Authentication error occurs for jobs with Microsoft Exchange 2010 logs truncation enabled in case user credentials miss domain name

  • Failback EC2 Instances action with Original Location option selected turns off the source Instance instead of terminating it

  • Authentication to Active Directory using NTLMv2 fails

  • Recovering files to an NFS share fails if the NFS server on a source VM is configured as NFSv4 only and the NAKIVO Transporter has earlier NFS protocol versions