gansercom

just another private tech blog

Category: Veeam

Veeam released Update 2 for Backup & Replication 9.5

On May 12th Veeam has released the Update 2 for Backup and Replication 9.5

I’ve updated now my home lab and after testing our production site too. The Update runs fine with no errors, all jobs are finishing successful. From my side there is no reason to wait for installing the update.

Veeam had listen to the customers and has included many enhancements (vSAN 6.6; Exchange 2016 CU5; Storage Vendor support) and fixes.

Here are the most significant (for me) of them:

Continue reading

Veeam B&R 9.5 Update 1 released for production

Last weekend the final version of Veeam Backup and Replication Update 1 was released.

VMware vSphere 6.5 is now fully supported.

The vSphere 6.5 support adds the following features:

  • Encrypted VMs support.
  • VMFS6 support.
  • Virtual hardware version 13 support.
  • NBD compression. VDDK 6.5 adds ability to enable native NBD traffic compression.
  • New guest interaction API support.
  • New VM tag API support. vSphere 6.5 introduces new APIs for programmatic access and management of vSphere tags.

To get the full list of changes go to https://www.veeam.com/download_add_packs/vmware-esx-backup/kb2222/

I’ve wrote down the few steps to install the update.

Continue reading

Veeam B&R 9.5 Update 1 – Release Candidate availiable

At the beginning of the new year Veeam has built the Release Candidate for Veeam Backup and Replication 9.5 Update 1.

With this update it is possible to backup VMs running on vSphere 6.5. You have to open a case at Veeam to get the Release Candidate. Remeber: Those updates are only for testing. Productive support will come with the official update!

Continue reading

Veeam B&R 9.5 – Microsoft Exchange logs are not beeing truncated

After upgrade to the new version of Veeam Backup and Replication (9.5) you could get a failure within your Microsoft Exchange Backups.

The Backup runs even normal and ends apparently successful. But the logs are not being truncated and the event logs might shows an event ID 2034.

Continue reading

© 2017 gansercom

Theme by Anders NorenUp ↑