article<\/a>\u00a0of the User Guide.\u00a0 Below is the list of feature limitations.<\/p>\nBackup and Replication<\/strong><\/p>\n\n- VMware VM RDM disks are supported only in virtual compatibility mode<\/li>\n
- Backed up RDM disks in virtual compatibility mode are recovered as thin disks<\/li>\n
- Replicas of VMs with RDM disks in virtual compatibility mode are created with thin disks<\/li>\n
- VMware VM Independent disks are not supported<\/li>\n
- A Transporter installed on Linux should be used to back up and replicate VMs with SATA disks<\/li>\n
- First Class Disk (FCD) cannot be backed up if it is not attached to any VM<\/li>\n
- VSS quiescing is not supported for encrypted VMs<\/li>\n
- VSS quiescing is not available for Microsoft Windows 7 on some platforms<\/li>\n
- Microsoft Windows 10 Pro does not support VSS quiescing on Microsoft Hyper-V 2012 R2<\/li>\n
- LVM logical volumes in a thin pool are not supported for physical backup jobs<\/li>\n
- Replication job fails if a datastore with a replica is renamed<\/li>\n
- An encrypted AWS EC2 instance (default key) can not be replicated between accounts<\/li>\n
- Backups of physical machines with Cluster Shared Volumes (CSV) are not supported.<\/li>\n<\/ul>\n
Skip Swap Files and Partitions<\/strong><\/p>\n\n- Windows dynamic disks are not supported<\/li>\n
- Physical machine backup is not supported<\/li>\n
- Linux swap files are currently not skipped. Only Linux swap partitions are supported<\/li>\n<\/ul>\n
vSphere Hot Add<\/strong><\/p>\n\n- If Hot Add cannot be enabled for at least one disk of a source VM (even if the disk is deselected in the job), Hot Add may be unavailable for all disks of the VM<\/li>\n
- Hot Add is not available for VMs that contain IDE disks<\/li>\n
- vSphere HotAdd is not supported if the VA with NAKIVO Backup & Replication has the same BIOS UUID as the source VM<\/li>\n<\/ul>\n
Encrypted Repository<\/strong><\/p>\n\n- Encrypted repositories are not supported with RHEL\/SLES due to missing required packages<\/li>\n<\/ul>\n
Screenshot Verification<\/strong><\/p>\n\n- NFS datastores cannot be used as target datastores for screenshot verification<\/li>\n<\/ul>\n
Pre and Post Job Actions<\/strong><\/p>\n\n- Application log truncation is not available on ESXi 4.1<\/li>\n
- PowerShell scripts are not supported for standalone jobs.\u00a0All Windows scripts are being run by cmd.exe<\/li>\n<\/ul>\n
Flash VM Boot<\/strong><\/p>\n\n- ESX\/ESXi hosts enable binding the software iSCSI adapter (HBA) to VM Kernel network(s). If such binding is configured for an ESX\/ESXi host that is used as a target for Flash VM Boot, the connectivity between the host and the Transporter might not be available at the iSCSI layer<\/li>\n
- If an iSCSI binding is configured for a host to be used as a target for Flash VM Boot, verify or configure the connectivity at the iSCSI layer (either by selecting a host without binding, removing binding on a host, or adding a dedicated VM Kernel network to the binding that allows the connectivity)<\/li>\n
- NFS datastores cannot be used as target datastores for flash VM boot<\/li>\n<\/ul>\n
Recovery<\/strong><\/p>\n\n- File recovery from Linux LVM volumes is available only in case the Transporter assigned to the Backup Repository is installed on a Linux OS<\/li>\n
- File recovery is not supported for independent, encrypted, and RAID disks<\/li>\n
- File recovery from LVM volumes is not available if the Transporter that is assigned to a backup repository is installed on a NAS such as Synology, QNAP, Western Digital, or ASUSTOR<\/li>\n
- File recovery from systems that use Windows-only features, such as Windows Data Deduplication or DFS, is available only in case the Transporter assigned to a backup repository is installed on Windows machine with such features enabled<\/li>\n
- File recovery is not supported for source VMs on RAID disks<\/li>\n
- File recovery from Windows Dynamic Disks is not supported for the following platforms:\n
\n- ASUSTOR NAS<\/li>\n
- Red Hat Enterprise Linux 7.x<\/li>\n<\/ul>\n<\/li>\n
- Recovering files to an NFS share fails if the NFS server is configured as NFSv4 only and the NAKIVO Transporter has earlier NFS protocol versions<\/li>\n
- File recovery may skip empty folders from the NTFS file system in certain configurations<\/li>\n
- Active Directory printers are skipped during recovered items import<\/li>\n
- Replica\/recovered VM disks are always created as Lazy zeroed if source VM had both Lazy and Eager zeroed disks<\/li>\n
- Exchange emails that were forwarded to recipient as attachments cannot be recovered from the mailbox<\/li>\n
- Exchange Public Folders are not supported for granular recovery<\/li>\n
- File recovery fails if the HDD’s Virtual Device Node is SATA and Transporter proceeding the job is installed on Windows<\/li>\n
- SQL Server object recovery does not work with databases that have memory-optimized data filegroup containers<\/li>\n
- SQL Server object recovery cannot recover system-versioned table if the table with such name already exists<\/li>\n
- File recovery for thinly-provisioned logical volumes is not supported<\/li>\n
- File-level recovery may be unavailable on some Linux configurations with XFS or BTRFS file systems<\/li>\n
- PowerShell scripts are not supported for site recovery actions.\u00a0All Windows scripts are being run by cmd.exe<\/li>\n
- Recovery of mailboxes is not supported for Microsoft Exchange object recovery jobs<\/li>\n
- Cross-platform recovery may not work in case a VM or physical machine includes a special OS kernel<\/li>\n
- Birthday events may not be recovered via an object recovery job for Microsoft Exchange even if the job run was successful<\/li>\n
- NAKIVO Backup & Replication displays only 1000 emails on the Objects page of the Object Recovery for Microsoft Exchange wizard<\/li>\n
- XFS file system is not supported for recovery to source<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
New Features VMware vSphere v7.0 Support NAKIVO Backup & Replication now supports VMware vSphere v7.0 Physical Machine Recovery to VMware VM To protect mixed physical and virtual IT environments, NAKIVO Backup & Replication offers the Physical to Virtual Machine Recovery feature. For details, refer to\u00a0Physical to Virtual Machine Recovery. User Interface Enhancement (Facelift) NAKIVO Backup […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[],"class_list":["post-9518","post","type-post","status-publish","format-standard","hentry","category-product-updates-microdium"],"_links":{"self":[{"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/posts\/9518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/comments?post=9518"}],"version-history":[{"count":0,"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/posts\/9518\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/media?parent=9518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/categories?post=9518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.microdium.com\/public\/wp-json\/wp\/v2\/tags?post=9518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}