v10.2 Release Notes

Release Date: 25 January 2021

New Features

Backup & Recovery of SharePoint Online 

Having your Microsoft 365 account added to NAKIVO Backup & Replication with SharePoint credentials, you can now back up SharePoint Online sites and recover SharePoint document libraries and lists. 

Lock Backup Objects in Amazon S3

The feature allows you to make backup objects stored in Amazon S3 immutable. It will provide protection from ransomware and deletion. The feature can be enabled on the Retention step of backup and backup copy job wizards.  


Using the tenant creation wizard in a multi-tenant mode, you can assign infrastructure (host, clusters, VMs, etc.), Transporters, and Backup Repositories to tenants. Supported platforms: VMware, Microsoft Hyper-V, and physical machines.


  • Per backup object verification is now also available for forever-incremental Backup Repositories

  • Support of Dell-EMC Data Domain DD OS v7.x 

  • Support of additionally installed/auto-updated Transporters for Microsoft 365

  • NAS support for Microsoft 365 

  • Integration of Release Notes into NAKIVO Backup & Replication 

  • Use of SSH keys for a physical machine agent in addition to username and password

  • Maintenance scheduling

  • Restart of Director service from the NAKIVO Backup & Replication UI

  • UI improvements

  • Security improvements

  • Support of Nutanix AHV v5.15

  • Granular notifications for Microsoft 365 jobs

  • Product configuration in expert mode

Known Issues

Product Usability

  • You can see an 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 due to missing information in the old license. Please contact support@nakivo.com to obtain an updated license

  • It is possible to downgrade the Western Digital NAS package to an older version, which can lead to lost product configuration

  • When selecting all NAKIVO Backup & Replication users to apply a bulk action, the product selects only the users displayed on the screen

  • When updating NAKIVO Backup & Replication to v10.0, all logos will be updated with the NAKIVO default logo including the customized ones

  • NAKIVO Backup & Replication displays only 1000 emails on the Objects page of the Object Recovery for Microsoft Exchange wizard

Platform Limitations


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

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

  • Connection with Transporter on Windows 10 physical machine will be lost when it goes into sleep mode or restarts after installing system updates

  • Microsoft Windows 10 Pro does not support VSS quiescing on Microsoft Hyper-V 2012 R2


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


  • Onboard Transporters installed on NAS devices with ARM CPU do not support VMware infrastructures

  • SAN transport mode doesn't work when the product is running on a QNAP NAS

  • Transporters running on FreeNAS devices are not supported for backup and recovery of VMware vSphere VMs


  • VMware vSphere Transporter Appliance cannot be deployed to ESXi older than 5.0

  • VMware VM Independent disks are not supported

  • For successful replication and recovery to an NFS datastore, thin-provisioned disks should be created


  • CBT Driver for Hyper-V 2012(R2) is not available 

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

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

  • 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 

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


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

  • Failback Amazon EC2 instances action with Original Location option selected turns off the source instance instead of terminating it

  • Backup of encrypted EBS volumes may be unavailable for certain Amazon EC2 transporter instance types

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

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

  • AWS accounts in China (Beijing and Ningxia regions) and Asia-Pacific (Osaka-local) are not supported

Microsoft 365

  • Backup and recovery of Exchange Online public folder mailboxes, guest mailboxes, online archive folders, distribution groups, contacts, and calendars are not supported

  • Backup and recovery of such OneDrive for Business items as "Shared" folder, "Recent" folder, "Recycle bin", Internal OneDrives or folders are not supported

  • Backup and recovery of such SharePoint Online items as internal folders, document libraries, lists, and list items are not supported

  • Backup and recovery of such SharePoint Online items as MicroFeed lists, picture library, site assets library, and site pages library are not supported

  • Backup and recovery of Microsoft groups and Microsoft teams are not supported

  • Recovery of full SharePoint Online sites is not supported

  • Synology NAS devices with ARMv8 CPU architecture are not supported for backup and recovery of Microsoft 365 accounts

  • FreeNAS devices are not supported for backup and recovery of Microsoft 365 accounts

  • Backup copy jobs are not supported for Microsoft 365

Amazon S3 and Wasabi

  • Features that use iSCSI (i.e. FlashBoot, screenshot verification, file-level recovery, recovery to source) may not function correctly with Amazon S3 and Wasabi Backup Repositories due to the networking requirements limitation

  • Tokyo region is not supported for Backup Repositories created in Wasabi storages


  • AD integration with NAKIVO Backup & Replication is not supported for guest user accounts

  • HPE StoreOnce Catalyst integration is not supported on devices with ARM7 and ARM64 (AArch64) processors


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

  • When restarting a recovered VM with dynamic disks mounted to Transporter, dynamic disks may not be recognized

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

  • Authentication to Active Directory using NTLMv2 cannot be performed

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

  • When refreshing an Amazon S3 Backup Repository with immutable data, an alarm notifying of the corrupted data in the repository may not be displayed in the product 

Feature Limitations

NAKIVO Backup & Replication features require certain conditions to function properly. For more details about feature requirements, refer to the corresponding article of the User Guide.  Below is the list of feature limitations. 

Backup and Replication

  • VMware VM RDM disks are supported only in virtual compatibility mode

  • Backed up RDM disks in virtual compatibility mode are recovered as thin disks

  • Replicas of VMs with RDM disks in virtual compatibility mode are created with thin disks

  • A Transporter installed on Linux should be used to back up and replicate VMs with SATA disks

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

  • VSS quiescing is not supported for encrypted VMs

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

  • LVM logical volumes in a thin pool are not supported for physical backup jobs

  • Replication job fails if a datastore with the replica is renamed

  • An encrypted Amazon EC2 instance (default key) can not be replicated between accounts

  • Replication across different AWS account types is not supported

  • Cluster Shared Volumes (CSV) are not supported for backup of physical systems

  • Windows failover clusters are not supported for backup of physical systems

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

Skip Swap Files and Partitions

  • Windows dynamic disks are not supported

  • Physical machine backup is not supported

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

vSphere Hot Add

  • If 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 may be unavailable for all disks of the VM

  • Hot Add is not available for VMs that contain IDE disks

  • vSphere Hot Add is not supported if the VA with NAKIVO Backup & Replication has the same BIOS UUID as the source VM

Encrypted Repository

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

Screenshot Verification

  • NFS datastores cannot be used as target datastores for screenshot verification

Log Truncation

  • Application log truncation is not available on ESXi 4.1

Pre and Post Job Actions

  • PowerShell scripts are not supported for standalone jobs. All Windows scripts are being run by cmd.exe

  • Custom pre/post job scripts are unavailable for Windows VMs when Integration Services are used on Hyper-V 2016 and above

Flash VM Boot

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

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

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

File Level Recovery

  • File recovery from Linux LVM volumes is available only in case the Transporter assigned to the Backup Repository is installed on a Linux OS

  • File recovery is not supported for independent, encrypted, and RAID disks

  • File recovery from LVM volumes is not available if the Transporter that is assigned to a backup repository is installed on a NAS such as Synology, QNAP, Western Digital, or ASUSTOR 

  • File recovery from systems that use Windows-only features, such as Windows Data Deduplication or DFS, is available only in case the Transporter assigned to a backup repository is installed on Windows machine with such features enabled

  • File recovery is not supported for source VMs on RAID disks 

  • File recovery from Windows Dynamic Disks is not supported for the following platforms:


    • Red Hat Enterprise Linux 7.x

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

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

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

  • File recovery for thinly provisioned logical volumes is not supported

  • File recovery may be unavailable on some Linux configurations with XFS or BTRFS file systems

  • 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

  • File recovery may fail if the Windows machine to which you wish to recover items has over 20 disk volumes (with and without drive letters)

Object Level Recovery

  • Active Directory printers are skipped during recovered items import

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

  • Exchange emails that were forwarded to the recipient as attachments cannot be recovered from the mailbox

  • Exchange Public Folders are not supported for granular recovery

  • 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 the table with such name already exists

  • Recovery of mailboxes is not supported for Microsoft Exchange object recovery jobs

  • Birthday events may not be recovered via an object recovery job for Microsoft Exchange even if the job run was successful 

  • Lookup data of SharePoint lists displayed in the recovery wizard is inaccurate, and it can't be recovered

  • Recovery of SharePoint lists containing special characters/symbols is not supported

Cross-Platform Recovery

  • Cross-platform recovery may not function correctly in case a VM or physical machine includes a special OS kernel

Site Recovery

  • PowerShell scripts are not supported for site recovery actions. All Windows scripts are run by cmd.exe


  • XFS file system is not supported for recovery to source

  • Bandwidth Throttling is not available for recovery from tape jobs

  • ARM-based (x32) NAS devices are not supported for SaaS Backup Repository creation

  • Synology NAS devices with ARMv8 architecture are not supported for SaaS Backup Repository creation