Page tree
Skip to end of metadata
Go to start of metadata

Release Date: 2019-09-04

New Features

Nutanix AHV Support

Install NAKIVO Backup & Replication v8.5 as a virtual appliance on a Nutanix AHV. Back up and recover AHV VMs, use Object and File Level Recovery, Log Truncation and other existing product features with Acropolis Hypervisor

VM Replication from Backup

Schedule replication jobs from available VM backups through usual replication wizard by selecting backups from existing Jobs & Groups or Backup Repositories. The feature is available for VMware vSphere and Microsoft Hyper-V VMs. 

Product Auto Update

Update the entire product automatically when an update becomes available. It is possible to download and install the update right away, download the update and automatically install it later, or schedule the update for some other time.

The product supports Product Auto Update of full-solutions installed on Windows and Linux as well as auto-injected Transporters.

FreeNAS Support

Install both NAKIVO Backup & Replication Full Solution and Transporter-Only packages on FreeNAS using Plugins Jail in FreeNAS user interface.

Support of NAS Devices with ARMv8 CPU 

Starting from v8.5, NAKIVO Backup & Replication can be installed on NAS devices with ARMv8 CPU from such vendors as ASUSTOR, Synology, and QNAP.

Improvements

  • Installation on Windows Server 2019 has become available
  • File recovery to source has become available for Windows Servers 2019
  • Maximum load per job has been introduced
  • Installation on Raspberry Pi 
  • AWS GovCloud (US) and all regions are now supported
  • Active Directory integration: domain controller hostname / IP can be explicitly specified
  • Ability to remove last recovery point was added for backups
  • AWS EC2 transporters were switched to Ubuntu 18.04 LTS
  • ASUSTOR ADM 3.1 and 3.2 are now supported for installation
  • AWS EC2 backup repository can be resized beyond 16 TB
  • VM folder selection was made available for VMware VM Failback action of Site Recovery Job
  • t3.micro instance type is used by default for AWS EC2 transporter deployment
  • Application-aware mode setting is propagated to new VMs in a job
  • Database attachment was made available for a tenant support bundle
  • Last job run ending date and time was added to job dashboard
  • Installer scalability was improved to utilize more resources on high end servers
  • Policy view was added to site recovery job actions
  • Email Settings and Email Notifications were merged in Configuration area

Fixed Issues

  • Older versions of ESXi (4.1, 5.0, 5.1) no longer require an installation of the special Transporter
  • List of supported NAS devices was revised and updated
  • Several issues fixed for file recovery to server use case
  • Several issues fixed for AWS EC2 replication
  • Several issues fixed for VMware transporter appliance deployment
  • Fixed error handling of Hot Add mode on ESXi 5.5 and older
  • Fixed issue with deletion of an entire chain of recovery points
  • Fixed issue with application-aware snapshot in case VMware Tools are out of date
  • Using target objects of a job as source objects in the same job was disabled

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
  • 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:
    • ASUSTOR NAS
    • 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 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 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
  • New VMware Transporter Appliance can't be deployed to ESXi versions older than 5.0 
  • Replication across different AWS account types is not supported
  • Backup of encrypted EBS volumes may be unavailable for some AWS EC2 transporter instance types
  • SAN transport mode doesn't work on QNAP NAS

 

  • No labels