Veeam Backup for Office 365: Update 5b released

  • 9 February 2021
  • 4 comments
  • 159 views

Userlevel 7
Badge +2

Update 5b for Veeam Backup for Office 365 was released yesterday, which I’ve discovered from @AnthonySpiteri’s blog:

https://anthonyspiteri.net/patch-backup-microsoft-office-365-v11/

https://www.veeam.com/kb4092

Besides the preparation for the upcoming v11 VBR release I would like to highlight this resolved issue:

Under certain conditions retention policy mistakenly cleans actual Exchange backup data from Jet-based repositories set with snapshot-based retention of less than 2 years. This issue applies to Veeam Backup for Microsoft Office versions 3.0 – 4c. 

I’m not sure at what conditions this could happen but it sounds rather serious.


4 comments

Userlevel 7
Badge +2

The resolved issue regarding the potential data loss is still under investigation. According to Anton's Weekly Digest every VBO release below of 5a is affected. So one should either upgrade to 5b or wait for the hotfix for version 4c.

https://www.veeam.com/kb4103

https://forums.veeam.com/veeam-backup-for-office-365-f47/update-5b-resolved-issuse-with-retention-policy-t72043.html

More detailed information will be published this week and I'll update this post at that time.

Userlevel 4
Badge +1

Hotfix is released:

https://www.veeam.com/kb4099
 

here are some statements from Veeam.

„Anton is right, the first thing to pay attention to is the unplanned full sync of Exchange data.
And we're working on the option (script likely) that will allow detecting it automatically. Stay tuned“
https://forums.veeam.com/post401459.html#p401459

Userlevel 3
Badge

In the meantime I installed the upgrade 5B for all our tenants, so they can’t be comprimised with the potential data loss issue mentioned in this link : KB4103: Veeam Backup for Microsoft Office 365 retention policy miscalculation causing data loss

Userlevel 7
Badge +2

I’m still waiting for the details or the option to find out whether an installation was affected or not. Of course it’s important to fix this issue but I would feel better if we could check that ourselves.

Comment