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

New Features

VMware vSphere 6.7 Support

NAKIVO Backup & Replication v7.5 is compatible with vSphere 6.7, allowing users to seamlessly protect upgraded VMware vSphere environments and benefit from new features that improve backup performance.

EMC Data Domain Boost Support

The new version of NAKIVO Backup & Replication officially integrates with the BoostFS plugin, allowing to combine benefits of the VM backup software and source-side deduplication offered by Dell EMC Data Domain Boost. As a result of this integration, the VM backup size can be reduced by up to 17 times while the VM backup speed can be improved by up to 50%.

Install on NETGEAR ReadyNAS

NAKIVO Backup & Replication v7.5 can be installed directly on NETGEAR ReadyNAS devices, which helps create a cost-effective VM backup appliance. The ReadyNAS-based appliance is a 5-in-1 solution featuring backup hardware, software, storage, built-in global data deduplication, and backup-to-cloud functionality.

Cross-Platform Recovery

NAKIVO Backup & Replication offers a new functionality for cross-platform VM data recovery. With the Cross-Platform Recovery feature, users can export VM data from VMware, Hyper-V, and AWS EC2 backups into VMDK, VHD, or VHDX formats. The exported files can then be used for recovery across different hypervisors, cross-platform VM data migration, long-term archival, or sandboxed testing.

Advanced Bandwidth Throttling

The updated Bandwidth Throttling feature provides for setting speed limits for data protection to avoid network overload during business hours or chosen periods of time. The process can be easily automated by means of setting global rules that maintain bandwidth consumption at certain levels when needed the most.

Improvements

  • NAKIVO Backup & Replication can be installed on Ubuntu 18.04 LTS
  • File recovery to a specific server was made the default option
  • IP address of the target server for File Recovery can be entered manually
  • Custom SSH port of the target server can be used during File Recovery
  • Hyper-V VMs created with Flash VM Boot can be migrated to production storage
  • VMs are seamlessly tracked across different Hyper-V inventory items
  • An ability to specify a certain start date for the job schedule was added
  • Maintenance end notification improved to be shown 60 days before maintenance end
  • Error messages for the File Recovery were extended
  • Performance of Hyper-V Transporter automatic selection was improved
  • VM templates are excluded from jobs automatically
  • Target host RAM requirements are checked more thoroughly
  • Temporary snapshot removal notification behavior was improved
  • Source VM is unlocked right after the temporary snapshot is removed

Fixed Issues

  • Issue with network mapping in Hyper-V failover job
  • Generic error message while adding Hyper-V Server to inventory
  • No information about failed job in case the VM with the product is stopped
  • No information about failed backup repository verification
  • Issues with updating remote Transporters for Hyper-V
  • Issues with updating AWS EC2 installations using Linux installer
  • No alert in case the OS of the target server is not supported by File Recovery
  • Job failing without an error message in case all disks of the VM are RDM
  • vApp selected as a destination causing replication job failure
  • VMs not auto selected when creating jobs for VM folder from the Global Search page
  • Screenshot verification in Flash VM Boot job not respecting the limit of VMs
  • Numerous fixes in the File Recovery feature

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 (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
  • 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 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
  • 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
  • No labels