v10.3 Release Notes

Release Date: 4 May 2021

End of Fix: 4 May 2022

End of Support: 4 May 2024 (More details are here.)

New Features

Direct Connect (No-VPN)

The feature allows NAKIVO Backup & Replication installed at MSP/CSP site to access remote resources of an MSP/CSP client via a single port connection (port should be exposed by a client) without the need to establish a VPN connection. Supported platforms: VMware.

Backup & Recovery of Exchange Online contacts and calendars

Backup and recover Exchange Online contacts and calendars with NAKIVO Backup & Replication. Before using the product for data protection of your Microsoft 365 objects, make sure you meet the necessary requirements and enable the required API permissions. For platform limitations, refer to the corresponding section of the known issues below.

VMware Cloud Director Support

The feature allows you to back up and recover VMware Cloud Director objects including:

vApps which consist of one or more VMs that communicate over a network and use resourcesand services in a VMware Cloud environment;
individual VMs.

Backup from Storage Snapshots

Add HPE 3PAR storage to NAKIVO Backup & Replication to back up VMware VMs from HPE 3PAR storage snapshots. A storage snapshot can be created within seconds, and it consumes a small amount of space which, in its turn, reduces the impact of backup activities on the production environment and improves RPOs.

User Interface Enhancement (Facelift)

Enjoy the enhanced look and functionality of the NAKIVO Backup and Replication installation and update pages.

Harden Transporter

The feature allows you to use certificates and pre-shared keys for Transporters to make NAKIVO Backup & Replication more secure.

Improvements

Support for VMware vSphere v7.0.2
Support for Synology DSM v6.2.3-25426-3
Support for ReadyNAS OS v6.10.3
Support for QNAP QTS v4.5.1
Support for Asustor ADM v3.3.x, 3.4.x, 3.5.x
Support for Wasabi Dallas data center region
App-aware mode using NAKIVO Backup & Replication agent on Hyper-V
Map a new VM found by a policy to existing backups
Download or send to an email Exchange objects by configuring the appropriate setting in Expert Mode
Mark backup objects as corrupted when files of backup objects are removed during repository verification
Keep job history setting is changed to maximum 90 days
Aptare integration is disabled by default
Optimization for long fat networks

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

Windows

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

NAS

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

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
Free ESXi host v7.0.2 with SSH connection enabled may not be discovered due to unsupported SSH server algorithms. For details, refer to Free ESXi Host Cannot Be Discovered

Hyper-V

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

AWS

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 guest mailboxes, public folder mailboxes, online archive folders, calendars added from Directory, read-only calendars, distribution groups, resource mailboxes, event messages (i.e. "#microsoft.graph.eventMessageRequest", "#microsoft.graph.eventMessage"), and outbox folders are not supported
Exchange Online contact and calendar items can only be recovered to the original mailbox.
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, internal document libraries, internal 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
Recovery of SharePoint lists containing lookup data to a different site is not supported
The 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
Backup and recovery of Microsoft groups and Microsoft teams are not supported
Recovery of full SharePoint Online sites is not supported
ARM-based NAS devices and FreeNAS are not supported for SaaS Backup Repository creation
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 work 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

Integration

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

Reliability

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 jobs fail 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
Linux Transporter should be used for replicating/backing up VMs with SATA disks

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:
- ASUSTOR NAS
- 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
Microsoft Exchange contact and calendar items are not supported for downloading to browser or forwarding via email (Expert Mode)

Cross-Platform Recovery

Cross-platform recovery may not work 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

Miscellaneous

XFS file system is not supported for recovery to source
Bandwidth Throttling is not available for recovery from tape jobs
vSphere tags support is not available via Direct Connect