v7.4.1 Release Notes

Release Date: 3 May 2018

Overview

This is a maintenance release for v7.4.0. Please refer to Improvements, Fixed Issues and Known Issues below.

Improvements

  • Bandwidth Throttling feature is now available in all editions except Basic

  • The amount of simultaneous vSphere refresh requests is decreased to reduce the load on vCenter Server

Fixed Issues

  • QNAP and ASUSTOR users not able to update because of incorrect maintenance tracking information

  • Incorrect network mapping configuration could cause jobs to fail

  • Self-backup could be removed by bulk delete of backups not belonging to any jobs

  • Other minor fixes and improvements

Known Issues

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

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

  • 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 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 (64-bit) prevent to connect 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