Release Date: 2018-04-25
Automated VM Failover with Network Mapping and Re-IP
With the new NAKIVO Backup & Replication release, failover jobs can be created to switch VMware and Hyper-V VMs to replicas in case of failure. The functionality includes mapping the VM replica source network to the target one, and reconfiguring network parameters of VM replicas with Re-IP.
Support for Deployment on ARM-based NAS Devices
The application can now be deployed on ARM-based NAS models, and is capable of working with VMware vCenters and ESXi hosts. In this case, an additional Transporter needs to be added to the application in accordance with the instructions.
File Recovery Back to Source
The updated File Recovery Wizard adds possibilities for recovering files to the source VM (Beta) or a custom location, choosing to download files via Web browser or send files via Email. Windows-based and Linux-based VMs are supported.
The user can now limit the data transfer speed for his/her backup / recovery / backup copy / replication job so it consumes less LAN/WAN bandwidth. Bandwidth throttling for replicas is limited to VMware and Hyper-V replication jobs.
Flash VM Boot for Microsoft Hyper-V
Hyper-V VMs can now boot directly from compressed and deduplicated VM backups. The process is fully automated, and allows the user to migrate the booted Hyper-V VMs to the production environment.
Screenshot Verification for Microsoft Hyper-V
Screenshot verification can now be performed for Hyper-V VMs as well. The process test-recovers the VM first, takes a screenshot of the booted OS, and then discards the test-recovered VM.
The entire configuration of NAKIVO Backup & Replication can be backed up to different locations to be later restored.
The Global Search allows the user finding infrastructure objects instantly, seeing object details, and performing object individual and bulk actions.
Built-In Support Chat
In the updated NAKIVO Backup & Replication interface, the user has a possibility to contact a NAKIVO representative via chat.
Object Level Recovery and Log Truncation for Microsoft SQL Server 2017
The Object Recovery Wizard of the application can now work with Microsoft SQL Server 2017, including the Log Truncation option.
- Application deployment on Red Hat Enterprise Linux 7 (64-bit) and SUSE Linux Enterprise Server 12 (64-bit) is supported.
- Transporter mode used in a job run is now shown on a dashboard.
- Full backup schedule has more options.
- Recovery point name now has a year inside to reliably identify different points.
- Events for disabled and removed jobs are not shown in UI to improve performance.
- Hyper-V socket count is done more reliably.
- Additional checks are done to prevent datastore overflow when Hot-Add mode is used.
- Advanced share mount options for CIFS and NFS.
- Jobs can be run for all/selected/failed VMs, and can be stopped for all/selected VMs.
- Retention policies didn't account RPs for the current week.
- Boot order for Hyper-V 2012 VMs recovered on Hyper-V 2016 was incorrect.
- Job editor could be stick if some VMs were excluded from protected LUs.
- Jobs could fail with internal error on slow environments because of missing confirmation block.
- Minor SQL Server Log Truncation and SQL Server Object Recovery fixes.
- CBT Driver for Hyper-V 2012 (R2) is not available (this feature will be available in one of the next releases).
- Encrypted repositories are not supported with RHEL/SLES (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 and those jobs are started at the same time, 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 ASUSTOR NAS.
- 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 Inventory without adding missing PowerShell features.
- 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 Linux Integration Services for Ubuntu 12.04 Server (x64) and SUSE Linux Enterprise Server 11 SP3/SP4 (64-bit) prevent NAKIVO Backup & Replication in establishing connection with source Linux VMs running on Microsoft Hyper-V.
- VMs are not automatically selected when creating jobs for VM folder from the Global Search results page.