Release Notes for Veeam Backup & Replication 9.5 Update 3
Please confirm you are running version 126.96.36.1990, 188.8.131.521, 184.108.40.2062, 220.127.116.113, 18.104.22.1688 or 22.214.171.1245 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build will be version 126.96.36.1996.
To upgrade from 9.0 or earlier, download the full ISO image and consult the user guide's upgrade section.
If you use Veeam ONE to monitor Veeam Backup & Replication or Veeam Cloud Connect, be sure to install Update 3 for Veeam ONE 9.5 first.
If you are a tenant of a cloud provider, please contact your provider before upgrading to ensure the provider has applied Update 3 on their end.
Providers can be on either 188.8.131.525 (RTM) or 184.108.40.2066 (GA).
As a result of on-going R&D effort and in response to customer feedback, Update 3 includes hundreds of enhancements and bug fixes, the most significant of which are listed below.
Built-in agent management. Veeam Agent for Microsoft Windows and Veeam Agent for Linux can now be deployed and managed directly from the Veeam Backup & Replication console, adding support for physical and cloud workloads protection.
- Maintain complete control of data protection for ALL your virtual, physical and cloud workloads by managing both hypervisor-based and agent-based backups natively through the Veeam Backup & Replication console.
- Ensure no Windows or Linux computers are left unprotected by centrally deploying Veeam agents with automated host discovery via dynamic protection groups based on Active Directory containers, or CSV files exported from your existing CMDB system.
- Protect Microsoft Windows Server Failover Clusters, such as SQL Server failover clusters and SQL Server AlwaysOn Availability Groups, with new agent-based failover cluster backup jobs – and transparently restore guest files and application items from cluster backups.
Data location tagging. Ensure data sovereignty compliance required by various regulations, such as the General Data Protection Regulation (GDPR), by tagging production infrastructure and backup infrastructure objects with locations. Location tags are used to prevent accidental errors when configuring backup and replication jobs or performing out-of-place restores, by issuing a warning when an action may result in a data sovereignty violation and producing audit trails whenever such action is confirmed. Additionally, new Veeam ONE reports use location data to help you prove compliance.
IBM Spectrum Virtualize Integration. Reduce the impact on production environments and achieve lower recovery time and point objectives through new storage snapshots integration for IBM Storwize, IBM SAN Volume Controller (SVC) and any other IBM Spectrum Virtualize based storage system, such as Lenovo Storage V series or IBM/Cisco VersaStack.
Universal Storage Integration API. The new storage array integration framework included in Veeam Backup & Replication starting with this update enables select storage partners to build integrations of their primary storage systems with advanced Veeam Backup & Replication functionality that leverages storage snapshots.
- Microsoft Azure. Direct Restore to Microsoft Azure functionality has been updated to support 4TB virtual disks, Azure Germany and Azure China.
- Microsoft SQL Server 2017 support for application-aware processing on Windows-based virtual machines, including transaction log backup and point-in-time restores; and as a backend configuration database for the Veeam Backup & Replication itself.
- Microsoft Windows 10 Fall Creators Update support as guest virtual machines, and for installation of Veeam Backup & Replication and all of its components.
- Microsoft Windows Server 1709 support as guest virtual machines, and for installation of Veeam Backup & Replication remote components.
- Microsoft Windows Server Hyper-V 1709 support as a hypervisor host, including support for virtual hardware version 8.2 virtual machines.
- VMware Cloud on Amazon AWS support allows protecting VMs running in the cloud, and migrate or replicate workloads from on-prem vSphere deployment to VMC (and vice versa).
- VMware vCloud Director 9.0 compatibility.
- Cisco HyperFlex support of deployments with multiple HyperFlex clusters under a single vCenter Server.
- DELL EMC Data Domain integration now supports Data Domain systems running DD OS 6.1
- HPE 3PAR StoreServ integration has been extended to include snapshot-only backup jobs; ability to retain primary storage snapshots created by backup jobs with a different retention policy; and ability to perform backup from storage snapshots from secondary 3PAR array running in Peer Persistence mode.
- Hyperconverged infrastructures (HCI) deployments can now leverage the new option to force the load balancer to use Direct NFS backup proxy located on the same vSphere host with the processed virtual machine, to avoid stressing storage replication network with backup traffic . To enable this functionality, create EnableSameHostDirectNFSMode (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server. The value is used to controls failover behavior when Direct NFS proxies if the proxy on same host is unavailable: 1 allows failover to other Direct NFS proxies, and 2 restricts failover to NBD only.
- LTO-8 support for all tape-related functionality.
- Backup mapping for agent backup files is now supported to enable scenarios such as backup seeding.
- Restore from backup copies. When initiating a restore from local user interface, Veeam Agent for Microsoft Windows and Veeam Agent for Linux will now provide the ability to pick a restore point stored in the secondary repository, should backup files in the primary repository be missing.
- Hyper-V 2016 VMs with non-snapshottable disk such as disks connected via in-guest iSCSI initiator can now be processed by backup and replication jobs, with unsupported disks skipped and their content not included in a backup or replica. If you’d rather prefer the job to fail on such VMs (legacy behavior), create HyperVIgnoreNonSnapshottableDisks (DWORD) value under HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication registry key on the backup server and set it to 0.
- New Oracle 12.2 account types support includes Microsoft Windows Group Managed Service Accounts (gMSA) and Microsoft Windows Virtual Accounts.
- VMDK resize operation will no longer result in resetting CBT data for all virtual machine disks, but rather for the resized disk only.
- Non-encrypted NBD transport is again available for vSphere 6.5, significantly improving backup and replication performance comparing to previously forced NBDSSL.
9.5 Update 3 includes many new features and enhancements for service providers offering Veeam Cloud Connect services. For the full list of these enhancements and bug fixes, please see this topic on the private VCSP forum. Not a member of the VCSP forum? Click here to join.
This update also resolves the following common support issues:
- Backup Copy jobs should no longer copy weekly GFS fulls twice under certain circumstances, and should now correctly extend copy interval when processing active full backups.
- vSphere Web Client plug-in should no longer display "Session expired" errors during its configuration when using vCenter Server Appliance 6.0
- Linux-based backup repository registered under root account should no longer crash when Data Mover crashes for whatever reason.
- Building VM list operation accelerated up to 4 times for Hyper-V jobs configured to use SCVMM tags.
- Reliability enhancements with Hyper-V backups in off-host backups and guest processing logic.
- File-level recovery in the Enterprise Manager should now work more reliably from non-Windows virtual machines, and after source Hyper-V VM was migrated to another host within SCVMM.
- Prefix for temporary storage snapshots created by backup jobs was changed from “Veeam_” to “VeeamAUX_” due to many users using the original prefix in day to day operations, which made Veeam Explorer for Storage Snapshots skip the corresponding snapshots.
- Direct Restore to Microsoft Azure should now tolerate short term Azure connectivity disruptions, uses more firewall friendly port 443 by default, and supports Azure accounts with multiple directories (use AzureDefaultTenantIdGUID registry value to set GUID of the directory to use).
- VeeamZIP retention should now work correctly with all system locales.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.