So, a quick note for those with the above software – I’d recommend you trying to access an EDB (Exchange Database) file from one of your backups with Veeam Explorer for Exchange at your soonest convenience – it appears that there is an incompatibility with Exchange 2016 Cumulative Update 5 (that Veeam Support were aware of) which results in an inability to view the individual files.
If you’re being hit with this issue, you’re likely to see this delightful error…
![Veeam Exchange 2016 Blob](http://zap-robo.net/wp-content/uploads/2017/04/veeam-exchange2016-blob.png)
Invalid property BLOB.
Moreover, your logs (over in %ProgramData%\Veeam\Backup\ExchangeExplorer\Logs) will show this delightful extract…
4/13/2017 9:36:35 AM 1 (8784) Error: Invalid property BLOB.
4/13/2017 9:36:35 AM 1 (8784) Stack:
4/13/2017 9:36:35 AM 1 (8784) at Veeam.Exchange.Storage.V15.Parsers.PropertyBlobParser.ParseHeader()
at Veeam.Exchange.Storage.V15.Props.PropMaker.Make(IDictionary`2 props, Byte[] data)
at Veeam.Exchange.Storage.V15.Mailboxes.IsTeamMailbox(IMailboxProps mailbox)
at Veeam.Exchange.Storage.V15.Mailboxes.<GetEnumerator>d__0.MoveNext()
at Veeam.Exchange.Explorer.ViewModel.Tree.StoreViewModel.LoadChildren()
at Veeam.Exchange.Explorer.Tree.TreeNodeViewModel.set_IsExpanded(Boolean value)
Word is that the problem will be fixed in “Update 2” from Veeam, but they’re estimating this could be a few months out. Best practice right now? Either avoid upgrading to CU5 or if you have deployed it, you’ll need a third-party tool to extract the data (the backup itself is fully functional and unaffected).