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

Release Date: 2018-01-23

Fixed Issues

  • Issue with deduplication of zero data blocks in the forever incremental backup repository
  • Null pointer exception on attempt to retrieve VMware CBT data in some scenarios
  • Issues with processing VMs located in the root of datastore
  • GUI issue in the Calendar dashboard
  • Minor SQL Server Log Truncation and SQL Server Object Recovery fixes

Known Issues

  • CBT Driver for Hyper-V 2012 (R2) is not available (this feature will be available in one of the next releases)
  • Flash VM Boot and Screenshot Verification for Hyper-V are 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
  • VM boot order in Microsoft Hyper-V 2012 can be incorrect due to API limitations
  • 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

  • No labels