Comprehensive data protection for all workloads
lavvaf
Lurker
Posts: 1
Liked: never
Joined: Oct 27, 2018 6:45 pm
Full Name: Alireza Lavvaf
Contact:

Re: All instances of the storage metadata are corrupted.

Post by lavvaf »

Hi,
unfortunately our backup files header corrupted (encrypted by Ransomware). could you please help us to recover damage file (repair header VBK files). we had recovered SQL backup file by repair headers, but we couldn't find any tools to repair Veeam backup header!
Please Help!
Vitaliy S.
VP, Product Management
Posts: 27260
Liked: 2760 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: All instances of the storage metadata are corrupted.

Post by Vitaliy S. »

Hi Alireza,

There is no out-of-the-box way/tools to repair the header of the VBK file. I would suggest contacting our support team, they might be able to assist you with this, though no guarantees.

On a side note, I know that right now this might sound inappropriate, but please consider following a 3-2-1 rule next time to be protected from these cases.

Thanks!
jlcatalula
Lurker
Posts: 1
Liked: never
Joined: Apr 24, 2024 9:31 am
Full Name: José Luis
Contact:

Re: All instances of the storage metadata are corrupted.

Post by jlcatalula »

lavvaf wrote: Oct 27, 2018 7:22 pm Hi,
unfortunately our backup files header corrupted (encrypted by Ransomware). could you please help us to recover damage file (repair header VBK files). we had recovered SQL backup file by repair headers, but we couldn't find any tools to repair Veeam backup header!
Please Help!
Hello, We have had a similar problem to the one you indicate, with copy files with corrupted headers. I would like to know how you were able to recover the SQL files, it would be very important for us to recover at least those files. Thank you very much in advance.

ID - 07236222
squebel
Service Provider
Posts: 144
Liked: 14 times
Joined: Sep 27, 2019 5:06 pm
Contact:

Re: All instances of the storage metadata are corrupted.

Post by squebel »

We have run into this too many times recently after going to 12.x and it always seems to be related to the extent getting close to or running out of space. This was never a problem previous to 12.x. I just found a situation where an extent supposedly ran out of space and now the backup chain is corrupt. Never did our monitoring system show the extent being below 1.6TB free but the filesystem does believe that it is full. There is something going on with ReFS that's not reporting actual consumption correctly. Case 07273613 for reference.
Post Reply

Who is online

Users browsing this forum: No registered users and 152 guests