As of last Friday and in particular on the 26th of March 2019 Veeam published a new upgrade for the previous Update 4. This is in fact the Veeam Backup 9.5 U4a. Primarily this is a cumulative hot-fix for the previous big Update 4 version and is promptly addressing the feedback from the Community. Nonetheless it also extends the platform support to include (from the KB article):
- VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. Please note that the testing has been performed on pre-release 6.7 U2 builds, while the official support will still require a comprehensive testing of the GA build.
- Microsoft System Center Virtual Machine Manager 2019 is now supported as a source for Microsoft Hyper-V VMs backup jobs.
- Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols.
- NSS trustee rights on files and folders are now restored during file-level recovery from NSS volumes hosted on Micro Focus Open Enterprise Server (OES).
- Experimental support for keyboard-interactive authentication can be enabled by creating the LinuxKeyboardInteractiveAuth (DWORD) = 1 registry value under the HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server. By default, we will look for the “password” substring in the SSH console prompts. You can override this using the LinuxKeyboardInteractiveAuthPrompt (REG_MULTI_SZ) value, where multiple substrings can be specified one per line.
- New Japanese era compatibility. 新元号の変更検証済み
Update 4a resolves the following common support issues:
- Certificate verification issues cause the backup console taking to long to open, or failing to open with “Object reference not set to an instance to an object” from backup console or “Could not load file or assembly” error in the log.
- Upgrade to Update 4 fails with the “Database version downgrade detected … Reboot and restart the setup” error on machines where system time regional format uses a.m. and p.m. (lowercase with dots).
- SureBackup jobs start failing after upgrading to Update 4 due to virtual lab settings incorrectly updated by the configuration upgrade, in case of lack of free disk space in the vPower NFS cache folder.
- On Hyper-V versions prior to 2016, jobs with application-aware processing disabled fail with “The system cannot find the file specified” error.
- Backup of Windows XP SP1 VMs fails with the “Failed to call RPC function Vss.GetFileFromGADir” error.
- Various primary storage integration issues with HPE Nimble, NetApp, IBM and Dell EMC VNX storage.
- Tape support reliability issues, including a number of UI performance issues with tape management functionality.
- HPE StoreOnce Catalyst library memory leak issue (solved by updating the library to version 18.104.22.168).
- VeeamZIP™ operation incorrectly consumes a license for VMs that were previously licensed by regular backup jobs.
In addition, Update 4a addresses over 300 minor bugs reported by customers and found during the internal testing.
Veeam Cloud & Service Provider Partners
Veeam Backup & Replication 9.5 Update 4a also includes bug fixes for service providers offering Veeam Cloud Connect services, and managing backup servers with Veeam Availability Console.
At the time of writing the Update 4a is already included in the latest ISO available for download from the Veeam website. Existing Veeam Backup 9.5 deployments can be upgraded by running the main executable directly on the Veeam Backup Server. From here it will be possible to push the updates to the additional components like the Backup Proxies.
Veeam Backup 9.5 U4a upgrade process
Before proceeding it is recommended to stop any running job. Once the main executable is extraced from the compressed file the Veeam Backup 9.5 U4a upgrade is a very simple process.
As soon as the wizard verifies the components it will proceed with the actual installation by stopping, protect configuration files, copy the new ones and restart all the services automatically. It is also possible to include the update of the additional components. In such cases the personal preference would be to not include this setting and then choose which components running on additional servers to upgrade. For example some of them might not be running or reachable. Especially in large distributed environments.
The upgrade process itself does not take a long time to complete and of course it also depends on the available resources. The wizard might require for a computer restart to apply for changes.