v10.11.3 Release Notes

Release Date: 17 September 2024

End of Fix: 17 September 2025

End of Support: 17 September 2027 (Updating this release version is not supported. More details are here.)

New Features

VMware vSphere 8.0U3 Full Support

Added full support for VMware vSphere 8.0U3.

Known Issues

Product Usability

  • You may be unable to update from NAKIVO Backup & Replication v7.2 and older due to missing information in old licenses. Please contact support@nakivo.com to obtain an updated license.

  • It is possible to downgrade the Western Digital NAS package to an older version, but this may lead to product configuration loss.

  • When selecting all NAKIVO Backup & Replication users to apply a bulk action, only the users displayed on the screen are selected.

  • When updating NAKIVO Backup & Replication to v10.0, all logos will be updated with the NAKIVO default logo, including customized logos.

  • NAKIVO Backup & Replication may not display the up-to-date size of a SaaS Backup Repository immediately.

  • Backup Repository in NAKIVO Backup & Replication that is deployed as a VA has a size limit of 128TB due to ext4 inode_ratio limitation. The maximum file size is limited to 16TB.

Platform Limitations

Windows

  • If a Transporter is installed on Windows Server 2008R2 or later, it is recommended that you set SAN Policy to OfflineShared or OfflineAll.

  • File recovery may fail if the HDD’s virtual device node is SATA and the Transporter processing the job is installed on Windows.

  • Connection with the Transporter on a Windows 10 physical machine will be lost when it goes into sleep mode or restarts after installing system updates.

  • Microsoft Windows 10 Pro does not support VSS quiescing on Microsoft Hyper-V 2012 R2.

  • If an NFS share Backup Repository is created on Windows OS and has Transporter installed on a Windows OS assigned to it, this repository may become inaccessible after some time. This occurs due to the Windows-specific share permission configuration issue.

NAS

  • Onboard Transporters installed on NAS devices with ARM CPU do not support VMware infrastructures.

  • SAN transport mode doesn’t work when NAKIVO Backup & Replication is running on a QNAP NAS.

VMware

  • VMware VM independent disks are not supported.

  • For successful replication and recovery to an NFS datastore, thin-provisioned disks should be created.

  • Free ESXi host v7.0.2 with SSH connection enabled may not be discoverable due to unsupported SSH server algorithms. For details, refer to Free ESXi Host Cannot Be Discovered.

  • SAN mode is not supported for RDM disks using NPIV.

Hyper-V

  • CBT Driver for Microsoft Hyper-V 2012(R2) is not available.

  • Hyper-V on Windows Nano Server cannot be added to NAKIVO Backup & Replication Inventory.

  • If the same Microsoft Hyper-V VM is processed by multiple jobs simultaneously, some of the jobs may fail to create a VM checkpoint.

  • Issues with Integration Services for Ubuntu 12.04 Server (x64) and SLES 11 SP3/SP4 (x64) prevent connection to source VMs running on Hyper-V. Learn more.

  • Recovery jobs for Microsoft Hyper-V do not allow creating VMs with identical names.

Nutanix

  • Nutanix volume groups are not supported.

  • Application-aware mode is not supported for Windows Server 2022 running on Nutanix.

AWS

  • Application-aware processing for Amazon EC2 may freeze when using domain credentials.

  • The Failback EC2 Instances action with the Original Location option selected turns off the source instance instead of terminating it.

  • Backup of encrypted EBS volumes may be unavailable for certain Amazon EC2 Transporter instance types.

  • Replica AMIs and recovered Amazon EC2 instances have the Platform attribute set to Other Linux due to AWS API limitations.

  • Bandwidth Throttling cannot be applied to instance backups to local Amazon EC2 Regions with a single Transporter.

  • AWS accounts in China (Beijing and Ningxia regions), US ISO West, US ISO East, and US ISOB East (Ohio) are not supported.

Microsoft Azure

  • Premium Page Blobs storage accounts are not supported.

Microsoft 365

  • Exchange Online:

    • Backup and recovery of guest mailboxes, Group calendars, and Group planners, distribution groups, mail-enabled groups, security groups, resource mailboxes, read-only calendars, calendars added from Directory, event messages (that is, "#microsoft.graph.eventMessageRequest", "#microsoft.graph.eventMessage"), and outbox folders are not supported.

    • When the Back up In-Place Hold items checkbox is selected in the Options step, only items in the DiscoveryHolds folder of the RecoverableItemsRoot folder are backed up. All items in Audit, Calendar Logging, Deletions, Purges, Substate Holds, Versions folders and all subfolders in DiscoveryHolds are skipped.

      • If the DiscoveryHolds folder does not exist, the backup process for these items is skipped and the In-Place Hold folder is not displayed in the recovery wizard.

    • When the Back up Litigation hold items checkbox is selected in the Options step, only items in the Purges folder of the RecoverableItemsRoot folder are backed up. All items in Audit, Calendar Logging, Deletions, DiscoveryHolds, Substate Holds, Versions folders and all subfolders in DiscoveryHolds are skipped.

    • When the Overwrite the original item if such items exists recovery behavior is selected for public folder items, items present in the target location will be skipped, not overwritten.

    • Only public folders located under IPM_subtree can be backed up; other public folders are skipped.

    • Items with the IPM.AbchPerson message type cannot be backed up and are skipped.

    • Contact and calendar items can only be recovered to the original mailbox.

    • If a job contains mailboxes, the size displayed in the Job Contents widget will include the total size of the mailbox folders—other items, such as calendar attachments, will not be included in the mailbox size. “Notes” folder size will also not be included in the total size.

    • If a job contains mailboxes that contain a “Notes” folder, the size of the messages within the folder will be transferred, as opposed to the size of the folder itself.

    • If a Microsoft 365 account is discovered before updating to version 10.6 or later:

      • If Automatically grant required permissions checkbox was selected during initial discovery of the Microsoft 365 account, group mailboxes will be automatically discovered and granted required permissions when updating to version 10.6 or later. If the checkbox was not selected, group mailboxes will not be automatically discovered.

      • To discover group mailboxes, edit the discovered Microsoft 365 account and select Exchange Online Group as a service or discover a new account.

    • The following items are skipped and added to the Skipped Items Report for the backup job run:

      • SharePoint and OneDrive files with 0 byte size

      • Source items that cannot be retrieved from Microsoft after 5 retries

      • Files that are manually deleted during the backup process and cannot be downloaded

      • Public folders with no servers available for a selected mailbox

      • Corrupted items

  • OneDrive for Business:

    • Backup and recovery of "Shared" folder, "Recent" folder, "Recycle bin", Internal OneDrives or folders are not supported.

    • OneDrives without added email addresses or assigned licenses are ignored.

  • SharePoint Online:

    • Backup and recovery of internal folders, internal document libraries, internal lists, and internal list items, MicroFeed lists, picture library, site assets library, site pages library, external users and version history are not supported.

    • Recovery of SharePoint Online lists containing lookup data to a different site is not supported.

    • The lookup data of SharePoint Online lists displayed in the recovery wizard is inaccurate, and it can’t be recovered.

    • Recovery of SharePoint Online lists containing special characters/symbols is not supported.

    • Private SharePoint sites created by Microsoft Teams are not supported.

    • Recovery of SharePoint Online items containing Location column is not supported.

    • Recovery may fail if recovering files or folders that meet at least one of the following criteria:

      • File or folder name exceeds 128 characters

      • Full file path (including path and file name) exceeds 260 characters

  • Teams:

    • If a Microsoft 365 account is discovered before updating to version 10.7 or later:

      • Teams will not be automatically discovered.

      • To discover Teams, edit the discovered Microsoft 365 account and select Teams as a service or discover a new account.

    • Backing up a team will not back up the connected team members' mailboxes, OneDrives, or personal sites.

    • The following are not supported for backup:

      • Private sites

      • Private and shared channels

      • One-on-One and group chats

      • Audio and video calls

      • Video recordings

      • Contacts

      • Calendar: information about meetings and meeting chats

      • Banner notifications in posts

      • Data of applications added as channel tabs that does not reside in the SharePoint document library of the channel

    • The following are not supported for recovery:

      • Reactions to messages using a Post (i.e. pinned, saved, translated, emojis, etc.)

      • Code snippets in posts recovered to a different account

    • Only the following tabs/applications are supported for recovery:

      • Website

      • Word

      • Excel

      • PowerPoint

      • Visio

      • PDF

      • Document Library

      • SharePoint

      • SharePoint Pages

      • SharePoint Lists

    • Due to a Microsoft limitation, it is not possible to recover a source team to a target team if the total number of channels (including deleted channels) exceeds 200. Learn more.

    • If you are only recovering a tab to a different team and the tab contains a link to a document library, the recovery will fail with the error message: "Cannot recover a tab to a different team if the tab links to a document library."

    • If recovering a team or channel to a different team and the team or channel includes a tab that links to a document library, the tab will be skipped for recovery and the recovery will be considered successful.

    • If a channel message that includes an image attachment is selected to be recovered to a different channel, the recovered image may not look the same as the original.

    • If a channel message that includes a sticker attachment is selected to be recovered to a different channel, the sticker will not be recovered.

    • If recovering files/folders that belong to the Team SharePoint document library (and do not belong to a specific channel) to a different channel, the files/folders will be recovered to the root "General" channel folder.

    • If recovering files (regardless of whether they're linked to a tab or message) to a different location, the files will be recovered to the target channel following the selected overwrite behavior (skip/overwrite/rename). No additional folders will be created.

    • When recovering a team, if the Recover members option is selected, users that do not belong to the target account will not be added as a member to that team and member permissions recovery will be skipped for that user.

    • The original sender of Teams posts in a channel may be lost during recovery. The user connected to the Teams credentials upon discovery may be displayed as the sender of the recovered posts.

    • A deleted Team channel remains in Microsoft for 30 days, after which it is permanently deleted. During these 30 days, the deleted channel still exists. Because of this, NAKIVO Backup & Replication cannot restore the deleted channel using normal behavior because this requires creating a new channel using the same name. Instead, NAKIVO Backup & Replication performs the following behavior for restoring channels:

      • If the selected channel exists (by name) in the target team (including both active and deleted channels):

        • If Rename recovered item if such item exists is the selected overwrite behavior, the channel will be recovered with "(recovered yyyy-MM-dd HH:mm:ss)" appended.

        • If Skip recovered item if such item exists is the selected overwrite behavior, the channel will be skipped.

        • If Overwrite the original item if such item exists is the selected overwrite behavior, the channel will be overwritten.

      • Or, you simply can manually restore the deleted channel from the Team’s settings (Manage team > Channels > Deleted) in Microsoft.

    • Alternatively, if you want to use NAKIVO Backup & Replication to restore the deleted channel using the same original name, you first need to manually restore the channel from the Team’s settings, rename it, delete it once more and then restore using NAKIVO Backup & Replication.

    • If Restore Team settings option is selected when recovering a Team, the following settings are restored:

      • Description

      • isMembershipLimitedToOwners

      • funSettings (allowGiphy, giphyContentRating, allowStickersAndMemes, allowCustomMemes)

      • guestSettings (allowCreateUpdateChannels, allowDeleteChannels)

      • memberSettings (allowCreateUpdateChannels, allowCreatePrivateChannels, allowDeleteChannels, allowAddRemoveApps, allowCreateUpdateRemoveTabs, allowCreateUpdateRemoveConnectors)

      • messagingSettings (allowUserEditMessages, allowUserDeleteMessages, allowOwnerDeleteMessages, allowTeamMentions, allowChannelMentions)

      • specialization (none, education_standard, healthcare_standard, etc)

      • visibility (private, public, hidden_membership)

      • discoverySettings (showInTeamsSearchAndSuggestions)

      • team photo (may not always be restored due to an internal error on Microsoft's side, same as for Groups)

    • If Restore members option is selected when recovering a Team, the following will be restored:

      • Team members

      • Team tags related to team members

    • If a channel is selected for recovery, the following channel settings will be recovered with the corresponding overwrite behavior:

      • Rename recovered item if such item exists:

        • Description

        • membershipType: standard, private, shared

        • isFavoriteByDefault

        • channel moderation settings (allowNewMessageFromBots, allowNewMessageFromConnectors, replyRestriction (everyone, authorAndModerators), userNewMessageRestriction (everyone, everyoneExceptGuests, moderators))

      • Overwrite the original item if such item exists:

        • Name

        • Description

        • membershipType: standard, private, shared

        • isFavoriteByDefault

        • channel moderation settings (allowNewMessageFromBots, allowNewMessageFromConnectors, replyRestriction (everyone, authorAndModerators), userNewMessageRestriction (everyone, everyoneExceptGuests, moderators))

    • If a channel is recovered to a different team, the files of the channel will be recovered to a new folder within the target channel whose folder name is the same as the source channel’s.

    • Messages that were backed up but have the "This message has been deleted" tag cannot be recovered

  • Backup copy jobs are not supported.

  • Only back up to SaaS Backup Repositories are supported.

  • ARMv7-based NAS devices and FreeNAS/TrueNAS are not supported for SaaS Backup Repository creation.

  • Recovery is not supported for files and folders that have names exceeding 128 characters and for full file paths exceeding 260 characters. Note that URL encoded characters count as 3 characters for the purpose of reaching these limits.

Cloud Storage

  • iSCSI places strict requirements on data turnaround (any request must be served within 5 second time frame) that cloud storage is not always capable of keeping up with. As the result, features that use iSCSI (that is, Flash Boot, screenshot verification, file-level recovery, recovery to source) may not work with Cloud Storage Repositories or have stability issues.

Integration 

  • Active Directory integration with NAKIVO Backup & Replication is not supported for guest user accounts.

  • HPE StoreOnce Catalyst integration is not supported on devices with ARM7 and ARM64 (AArch64) processors.

Reliability

  • With backup copy jobs, the value of the job speed on the dashboard can differ from the value provided via the Bandwidth Throttling settings.

  • When restarting a recovered VM with dynamic disks mounted to a Transporter, dynamic disks may not be recognized.

  • VMs that were recovered from encrypted source VMs with NVRAM settings modified may fail to boot.

  • Authentication to Active Directory using NTLMv2 cannot be performed.

  • Deployment of source Transporter and source VM from the same Windows VM template may cause backup corruption in HotAdd mode.

Feature Limitations

NAKIVO Backup & Replication features require certain conditions to function properly. For more details about feature requirements, refer to the corresponding articles in the User Guide. Below is a list of feature limitations. 

Backup and Replication

  • VMware VM RDM disks are supported only in virtual compatibility mode.

  • Backed-up RDM disks in virtual compatibility mode are recovered as thin disks.

  • Replicas of VMs with RDM disks in virtual compatibility mode are created with thin disks.

  • First Class Disks (FCDs) cannot be backed up if they are not attached to any VMs.

  • VSS quiescing is not supported for encrypted VMs.

  • LVM logical volumes in a thin pool are not supported for physical backup jobs.

  • An encrypted Amazon EC2 instance (default key) can not be replicated between accounts.

  • Replication across different AWS account types is not supported.

  • Cluster Shared Volumes (CSV) are not supported for backup of physical systems.

  • Windows failover clusters are not supported for backup of physical systems.

  • Backup and replication of Microsoft Hyper-V VMs with shared drives are not supported.

  • Linux Transporter should be used for replicating/backing up VMs with SATA disks.

  • The progress bar may not show accurate data during file share backup due to the lack of pre-indexing and taking snapshots steps in the backup process.

  • When copying a compressed backup between a Backup Repository and tape device, different compression levels may cause very slow transfer speeds. For more information, see this article.

  • SCSI or PCI passthrough devices are not supported for backup or replication.

  • To run backup jobs on NAKIVO Backup & Replication that is installed on FreeNAS\TrueNAS, the Transporter VA must be deployed on ESXi.

  • Replica/recovered VM disks are always created as lazy zeroed if the source VM has both lazy and eager zeroed disks.

  • Windows transporter does not have capabilities for handling Linux physical machines.

  • Linux transporter does not have capabilities for handling Microsoft Hyper-V.

  • The backup of 4k sector hard drives is not supported for physical machines.

Real-Time Replication

  • When creating a storage policy, the I/O filter storage providers must be online for the vCenter to confirm I/O filter installation status.

  • It is not possible to add, change, or remove the I/O filter policy for any VM with a snapshot tree associated with it.

  • If the source VM stores disks on an NFS v3 datastore, the Transporter specified on the Options page of the Real-Time Replication (Beta) Job Wizard for VMware must be located on the same host as the source VM.

  • The Transporter and VM replica must be located in the same vSAN datastore.

  • For one real-time replication job/real-time replication failover job, each target Transporter can support up to 11 source VMs in case there is one disk per source VM or up to 50 disks per source VM. For more information, see this article.

  • Real-time replication does not take into account the priorities of other jobs.

  • If the Transporter is accidentally shut down during the real-time replication stage, the attached disks (journal & replica) are not detached automatically.

  • If the Transporter is migrated during the real-time replication job run, the hot-added disks are deleted and the existing replica cannot be used again during the next job run unless the existing replica disks are manually readded on the user's side.

  • VMs with IDE disks are not supported for real-time replication.

Exclude Swap Files and Partitions

  • Windows dynamic disks are not supported.

  • Physical machine backup is not supported.

  • Linux swap files are currently not excluded. Only Linux swap partitions are supported.

vSphere HotAdd

  • If HotAdd cannot be enabled for at least one disk of a source VM (even if the disk is deselected in the job), HotAdd may be unavailable for all disks of the VM.

  • HotAdd is not available for VMs that contain IDE disks.

  • VMware vSphere HotAdd is not supported if the VA with NAKIVO Backup & Replication has the same BIOS UUID as the source VM.

Encrypted Repository

  • Encrypted repositories are not supported with RHEL/SLES due to missing required packages.

Screenshot Verification

  • NFS datastores cannot be used as target datastores for screenshot verification.

  • Screenshot verification is not supported for ESXi hosts configured to enforce iSCSI Header Digest and/or Data Digest settings.

Pre and Post Job Actions

  • PowerShell scripts are not supported for standalone jobs. All Windows scripts are run by cmd.exe

  • Custom pre/post-job scripts are unavailable for Windows VMs when Integration Services are used on Hyper-V 2016 and above.

Flash VM Boot

  • 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.

  • 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).

  • NFS datastores cannot be used as target datastores for Flash VM Boot.

  • Flash VM Boot may fail for ESXi hosts configured to enforce iSCSI Header Digest and/or Data Digest settings.

  • VM templates are not supported for Flash VM Boot.

  • Flash VM Boot to vSAN datastore is not supported for VMs with disks larger than 2TB.

Bare Metal Recovery

  • The source and target physical machines must have the same or identical hardware.

File-Level Recovery

  • File recovery from Linux LVM volumes is available only when the Transporter assigned to the Backup Repository is installed on a Linux OS.

  • File recovery is not supported for independent, encrypted, and RAID disks.

  • File recovery is not supported for 4K sector size drives and datastores. Refer to How to Check Drive and Datastore Sector Size for more information.

  • File recovery from LVM volumes is not available when the Transporter that is assigned to a Backup Repository is installed on a NAS such as Synology, QNAP, Western Digital, or ASUSTOR.

  • File recovery from systems that use Windows-only features, such as Windows Data Deduplication or DFS, is available only when the Transporter assigned to a Backup Repository is installed on a Windows machine with these features enabled.

  • File recovery is not supported for source VMs on RAID disks. 

    • ASUSTOR NAS

    • Red Hat Enterprise Linux 7.x

  • File recovery from Windows Dynamic Disks is not supported for the following platforms:

  • Recovering files to an NFS share fails if the NFS server is configured as NFSv4 only, and the Transporter has earlier NFS protocol versions.

  • File recovery may skip empty folders from the NTFS file system in certain configurations.

  • File recovery fails if the HDD's virtual device node is SATA, and the Transporter processing the job is installed on Windows

  • File recovery for thin provisioned logical volumes is not supported.

  • File recovery may be unavailable on some Linux configurations with XFS or BTRFS file systems.

  • File recovery is not possible if a backup contains an incomplete set of disks that are a part of the spanned volume/dynamic disks/LVM/RAID software or any other disk structures.

  • File recovery may fail if the Windows machine to which you wish to recover items has over 20 disk volumes (with and without drive letters).

  • File recovery may fail to display the contents of disks containing over 1 million files.

  • Symlinks in Windows and Linux OS, as well as encrypted files, are not supported for file recovery.

  • VM templates are not supported for file and object recovery.

  • Recovery to source for Windows is not possible if the file path, folder path, file name length, or folder name length exceeds 256 characters.

Object-Level Recovery

  • Active Directory printers are skipped during the import of recovered items.

  • Microsoft Exchange Server emails that were forwarded to a recipient as attachments cannot be recovered from the mailbox.

  • Microsoft Exchange Server public folders are not supported for granular recovery.

  • Downloading or forwarding of on-premise Microsoft Exchange Server objects is not guaranteed to work. To achieve the best results, it is recommended to use the recovery to source method.

  • Microsoft SQL Server object recovery does not work with databases that have memory-optimized data filegroup containers.

  • Microsoft SQL Server object recovery cannot recover a system-versioned table if another table with the same name already exists.

  • Recovery of mailboxes is not supported for Microsoft Exchange Server object recovery jobs.

  • Birthday events may not be recovered via an object recovery job for Microsoft Exchange Server even if the job run was successful.

  • Microsoft Exchange Server contact and calendar items are not supported for downloading to a browser or forwarding via email (Expert Mode).

  • Recovery of DNS entries is not supported for Active Directory.

  • For Active Directory object recovery, each recovered object has a new SID generated by the system. Due to Windows limitations, it is not possible to change it back to the original SID.

  • Object-level recovery is not supported for encrypted and signed email messages.

Cross-Platform Recovery

  • Cross-platform recovery may not work if a VM or physical machine includes a special OS kernel.

Site Recovery

  • PowerShell scripts are not supported for Site Recovery actions. All Windows scripts are run by cmd.exe.

Direct Connect

  • Recovery to source, object recovery, universal object recovery, Multi-Channel Recovery, Re-IP, log truncation, and tape support are not supported with Direct Connect.

  • vSphere tags support is not available via Direct Connect.

  • The Transporter with Direct Connect enabled cannot be used as a Replacement Transporter.

Users And Roles

  • If role-based access control (RBAC) is not available for the currently installed NAKIVO Backup & Replication license, creating additional users and roles is not possible.

Backup Immutability

  • When refreshing an Amazon S3 Backup Repository with immutable data, an alarm notifying about corrupted data in the repository may not be displayed in the product.

  • Backup Immutability is not supported for encrypted Backup Repositories.

  • Backup Immutability is not supported for ZFS and Btrfs file systems.

Backup Malware Scan

  • Windows server cannot scan Linux backups. However, Linux server can scan Windows backups for common cases.

  • The scanning process does not go inside the database structures, such as unpacking the individual emails or attachments to scan them separately.

  • The scanning process looks for the virus signatures in the database file itself. For some file formats, such as archives, the antivirus scan unpacks them first and then proceeds with the scan.

  • Each version of Sophos Protection antivirus software for Linux has the list of supported OS.

  • If real-time protection is enabled on the antivirus software, the scan process of NAKIVO Backup & Replication may not find defects.

Miscellaneous

  • The XFS filesystem is not supported for recovery to source.

  • Bandwidth Throttling is not available for recovery from tape jobs.

  • For SaaS Backup Repositories, recovery point statistics are returned only if the recovery point version is higher than v10.3.

  • Reports created by NAKIVO Backup & Replication do not display UTF-8 encoding correctly.