Potential Backup Data Inconsistency after 9.5 Update 2

[mkretzer]

Hello,

Case 02155759

Saturday we installed Update 2 because our Exchange Team wants to update to CU5.

Today i did some manual restore tests. We first did a FLR of our Exchange and immediately as the restore point was mounted we got a NTFS message that the system drive of the Exchange server has defects.
The live servers shows no NTFS problems after doing chkdsk, also the backups show no error on the points before Update 2.

Instant recovery immediately does chkdsk and fixes some unallocated space which should be allocated.

Anyone else with that kind of issues after Update 2?

Markus

[albertwt]

Markus,

Not that I know of.

So did you install the GA version of the Veeam Backup & Replication 9.5 Update 2 from: https://www.veeam.com/kb2283 ?
I'm using Exchange Server 2013 and also wondering if there is any potential issue after installing it ?

[mkretzer]

Hello,

yes. I am not sure if the issue is connected with Exchange at all, but happening on other VMs as well.

Markus

[foggy]

Hi Markus, we haven't seen this internally, so please continue investigating with support.

[albertwt]

And let us know how it goes and what's the issue after updating to Update 2 Markus.

[mkretzer]

This is all very strange. I tried several more backup runs and now chkdsk does not come up...

I am still having a instant recovery with a "defective" state (= a state which wanted to run chkdsk at boot) open and i am checking exchange database consistency with eseutil (which will take 12 hours or so). Will report back.

[albertwt]

Thanks for sharing this case, Markus.

[mkretzer]

eseutil /g shows no error.

Interestingly i was not the only one with this strange error:
vmware-vsphere-f24/windows-warning-abou ... 41202.html

[mkretzer]

Ok. Veeam is not the problem here. Sorry for causing worries with this thread!

Our live system shows EXACTLY the same FS errors as our instant recovery. But only when chkdsk is run at boot time. In the running OS there are no errors visible with read-only chkdsk.
The only strange thing is that i had to force the chkdsk and the instant recovery did the chkdsk by itself.

[albertwt]

Great to hear that Markus.
So I guess there is no known issue after applying Update 2 on Veeam Backup.