============================================================================================
Veeam Backup Validator Version 11.0.0.0
Copyright (C) 2021 Veeam Software Group GmbH. All rights reserved.
Parameters:
File: F:\Data\0607066\veeamfolder\Btrfs\veeam\Backup_FS1\Backup_FS1D2021-05-07T002513_50A2.vbk
Format: Html
Report:
Silence: no
Skip: no
Validating...
Failed to process storage. Failed to access storage file F:\Data\0607066\veeamfolder\Btrfs\veeam\Backup_FS1\Backup_FS1D2021-05-07T002513_50A2.vbk
Statistic:
Backup files count: 1
Incomplete backup files count: 0
Failed backup files count: 1
Files count: 0
Total size: 0.0 B
Validation failed.
The following files are corrupted:
1. 'F:\Data\0607066\veeamfolder\Btrfs\veeam\Backup_FS1\Backup_FS1D2021-05-07T002513_50A2.vbk': Failed to access storage file F:\Data\0607066\veeamfolder\Btrfs\veeam\Backup_FS1\Backup_FS1D2021-05-07T002513_50A2.vbk
============================================================================================
This file is very important to us, we would like to try to fix this file.
We have heard that Veeam Support Team has a "special tool" able to extract all available data from a corrupt vbk file.
Yes, I have opened a case for the repair service. (Case #04896728)
But, the Veeam customer support seems would not like to give us any help to try to repair or extract that corrupt file.
I am looking for the last chance to recover my system because the file is very important.
What else should I do?
While opportunities are explored regarding the tampered VBK, have you considered plan B? Things I would be looking at would be:
1. Offsite backups, even if you have to download them over a slow WAN link, it might be worth getting the ball rolling now.
2. Stale backups, even if its only got older data on it, a stale backup on an older tape/cloud repo/ USB disk/ SAN snapshot may get some some of the data you're looking for back. Inside VBR if you navigate to "Backups" on the left hand side, do any of the options under here have backup chains for the system you're looking to restore from? If the corrupt .vbk was also configured to be a copy, there may be secondary copy elsewhere.
3. Drastic option but if you can share the reason why the system you need to restore needs restoring then data recovery could be an option e.g fire. flood, RAID array failure, maliciously deleted, ransomware etc.
While the above are being actioned, have you taken steps to get working again? e.g begin to rebuild the lost system, temporary paper based operation?
kadokawa.tw wrote: ↑Jul 12, 2021 4:12 am
Yes, I have opened a case for the repair service. (Case #04896728)
But, the Veeam customer support seems would not like to give us any help to try to repair or extract that corrupt file.
Looking at the support case now and I don't see any such statements made by a support engineer. Nevertheless, you do need to escalate your case to a higher support tier, as T1 engineers are not trained to use those advanced support tools. It normally requires T3 support or even developers, and the results are not guaranteed of course - this depends on how much the backup file was modified.