Release Notes for NAKIVO Backup and Replication Transporter

This package contains only Transporter component of NAKIVO Backup and Replication and requires a separate full installation of NAKIVO Backup and Replication to work correctly. NAKIVO Backup and Replication is a fast, reliable, and affordable solution for protecting VMware vSphere, Microsoft Hyper-V and AWS EC2 environments, offering great backup performance, reliability, and advanced recovery features.

Version: 7.2.0.19211


(2017-09-21)

New Features
1. Microsoft SQL Object Recovery
2. Microsoft SQL Log Truncation
3. Calendar Jobs View
4. Multiple schedules per job

Improvements
1. Default password for NAKIVO VA was changed
2. Ability to add the same host multiple times to NAKIVO inventory
3. Additional time zones were added to the product
4. Description is shown in the list of available credentials for Log Truncation
5. Exchange Log Truncation is supported for Public Folders databases now.

Fixed Issues
1. Backup and recovery of Encrypted VMware VMs could fail.
2. Incorrect amount of free space was shown for EFS repository.
3. Multiple fixes for Exchange Log Truncation functionality.
4. Product inventory could show duplicates of Hyper-V VMs on Failover Cluster.
5. Repository space reclaim could be not interrupted by recovery job that has higher priority.

Version: 7.2.0.19211


(2017-09-21)

New Features
1. Microsoft SQL Object Recovery
2. Microsoft SQL Log Truncation
3. Calendar Jobs View
4. Multiple schedules per job

Improvements
1. Default password for NAKIVO VA was changed
2. Ability to add the same host multiple times to NAKIVO inventory
3. Additional time zones were added to the product
4. Description is shown in the list of available credentials for Log Truncation
5. Exchange Log Truncation is supported for Public Folders databases now.

Fixed Issues
1. Backup and recovery of Encrypted VMware VMs could fail.
2. Incorrect amount of free space was shown for EFS repository.
3. Multiple fixes for Exchange Log Truncation functionality.
4. Product inventory could show duplicates of Hyper-V VMs on Failover Cluster.
5. Repository space reclaim could be not interrupted by recovery job that has higher priority.