Host-based backup of VMware vSphere VMs.
Post Reply
bob808
Lurker
Posts: 2
Liked: never
Joined: Oct 30, 2023 8:59 pm
Contact:

Data corruption on restore points - Case # 06355943

Post by bob808 »

Created ticket with Veeam but no leads so far. Wondering if anyone else has seen this before.

Issue:
- Some restore points are randomly getting "corrupted" after being backed up successfully. This happened 5 times in the last 30 days that we know of for one VM.
- There has been at least one other VM in the same job with this issue as far as we know.
- I haven't seen this in any other jobs yet, but the only way to check is to check each restore point individually, so we don't yet know the full extent of the impact.

Symptoms:
- No errors or failures reported in the backup job.
- The Veeam backup validator reported no issues with the "corrupted" VBK files (https://helpcenter.veeam.com/docs/backu ... ml?ver=120)
- This tells me the VBK files are fine, but the contents of the VMDK files are corrupted.
- This does not happen all the time. Only some restore points are impacted.
- I've only seen this on two VMs so far, within the same job and the dates with corrupted restore points don't always coincide.

Restore Methods (This is a Windows 2019 Server with MS SQL)
1. Full VM Backup
- OS Will not load. VM Will boot up in Windows Recovery Mode as the OS volume is not recognized.

2. File Level Restore
- The Volumes letters are not recognized. Rather than c:\, d:\, etc.... ,the FLR appliance shows Volume1, Volume2, Volume3
- 2 Volumes mount fine, the rest are mounted in Veeam Backup Browser but show as empty with 0 objects.

3. SQL Application Restore
- Database fails to load.
- "MY_DATABASE ExplorerManagementService: Failed to get VM mount result (sessionId = 'd73d48af-39f6-4213-9fa0-xxxxxxxxxxx') | SQL metadata for database MY_DATABASE not found in restore point b479a6fd-be66-4ad1-9270-xxxxxxxxxx"

FLR Logs:
VeeamAgent.MountVm.Client.log
- Volume 0 and Volume 1 load fine. The rest of the volumes fail to load and have this error:

Code: Select all

[30.10.2023 13:09:45.956] <  7596> prx      | ERR |Failed to update reparse points for mounted volume 'C:\VeeamFLR\MY_VIRTUAL_MACHINE_47bf558e\Volume2'. Maximum count of points to update: '1000'.
[30.10.2023 13:09:45.956] <  7596> prx      | >>  |The volume does not contain a recognized file system.
[30.10.2023 13:09:45.956] <  7596> prx      | >>  |Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
[30.10.2023 13:09:45.956] <  7596> prx      | >>  |Failed to open mounted volume: 'C:\VeeamFLR\MY_VIRTUAL_MACHINE_47bf558e\Volume2\'.
[30.10.2023 13:09:45.956] <  7596> prx      | >>  |--tr:Error code: 0x000003ed
[30.10.2023 13:09:45.956] <  7596> prx      | >>  |An exception was thrown from thread [7596].
Gostev
Chief Product Officer
Posts: 31561
Liked: 6725 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Data corruption on restore points - Case # 06355943

Post by Gostev »

Do you use application-aware processing? As my only idea here would be VMware Tools quiescence messing things up.
bob808
Lurker
Posts: 2
Liked: never
Joined: Oct 30, 2023 8:59 pm
Contact:

Re: Data corruption on restore points - Case # 06355943

Post by bob808 »

Hi Gostev,

Yes, this is a backup job with application-aware processing that backs up and truncates MS SQL transaction logs.

I've asked the VM owner to upgrade VMWare tools and perform Windows updates. Still waiting to hear back.

Thanks,

Tim
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 54 guests