Veeam Backup & Replication 7.0 patch 4 released
Yesterday Veeam released patch 4 for their Veeam Backup & Replication 7.0 product.
Normally a patch release is not that appealing to write about, but besides a full list of bug fixes this patch of Veeam Backup & Replication also introduces some new features to an already feature rich product.
Veeam Backup & Replication 7.0 patch 4 includes:
VMware Virtual SAN (VSAN) support In addition to adding basic support (as provided by other vendors), the intelligent load-balancing engine was enhanced to account for VSAN specifics. As the result, for each VM the job will pick backup proxy running on VSAN cluster node with most of the virtual disks’ data available locally. This significantly reduces backup traffic on VSAN cluster network, resulting in minimum possible impact on production environment from backup activities.
Microsoft SQL Server 2014 Added support for Microsoft SQL Server 2014 both as the protected guest workload (including application-aware processing functionality), and the back-end database for backup and Enterprise Manager servers.
License key auto update Added automated license key update option to the License Information dialog. With auto-update enabled, the product will check Veeam licensing server periodically for an updated license key, and download and install the key automatically as soon as it becomes available. This feature is particularly useful to the Service Providers and subscription-based customers, and it removes the need to download and install the license key manually each time when the license extension is purchased.
Backup Copy The maximum allowed amount of restore points in the Backup Copy job has been increased to 999. Backup Copy will now resume the transfer after network connection drop to a Linux-based backup repository. Backup Copy jobs should no longer report errors during the days when source backup jobs are not scheduled to run – for example, during the weekend.
Hyper-V Added support for certain Hardware VSS Providers that previously could not be detected by the storage rescan process, and as such could not be used by the jobs. Jobs will now retry failed snapshot creation when another shadow copy of the same volume is already in progress, instead of immediately failing to process a VM.
Prior to installing this patch please reboot the Veeam server to clear any locks on the Veeam services and when the reboot is done, please stop all the Veeam services and apply the patch. When the patch is installed manually, start the Veeam services and open Veeam, and allow it to update all the components.