Veeam Restore Error - Unsupported Storage Version -19908488818

[WinstonWolf]

Hello ,
We create an succesfully Backup of old VMs which was no more used in the VM Environment to an Windows Server Share which was the backup Repository .
Now we need one of this VMs from this Backup to restore Guest Files .
But when we start the Restore we Receive the following Error :

All what we do is that we move the Backup Files on the Repository Server from on Partition with was REFS to another Partition which was NTFS .
The other difference is that the one Partition was 16K Blocksize the other Partition was 32K Blocksize .
When we make an Rescan of this repository this Warning appears :


Hope someone can help to solve this Problem .

Michael

[Gostev]

Hello, please include Veeam support case ID for this issue, as requested when you click New Topic. Thanks!

[PetrM]

Hello!

Regarding the second error during rescan:
I think .vbm contains a character which is not defined by xml specification and import procedure can not read it, please try to import by .vbk while the support case is under investigation.

Thanks!

[WinstonWolf]

Hello ,
The Support ID is #04008220 .
I try to import the vbk , but unfortunately the same behavior .

The Case is eskalated now .
For me its not comprehensible what happens with this Files . The only thing what we do is that we moved the Backup Files from one Partition to another .
It should not be an Problem . We dont change the Files himself ?!?

[PetrM]

In that case, let's wait for results of root cause analysis performed by our support team.

Thanks!

[Gostev]

We dont change the Files himself ?!?

While you certainly didn't, keep in mind that the storage itself may have "changed" them due to so-called "bit rot" issue (Google for more info).
In addition, we saw data corruptions happening in the network stack during data transfer from one storage to another.
Finally, those files could have been purposely corrupted by malware?

[WinstonWolf]

No i dont think so .
When i now use this Partition / Volume as backup Repository i can restore the Files from this .
Yesterday we create an test backup Job to this Partition with the corrupted Veeam Files . After this Backup we are able to import this Backuped Files in Veeam .
I dont know what happens with our Files . This Server is an HP XL420 . In this Server we have 12 x 8TB Harddisks in an Raid 6 ADG.
The only thing what happens last week was that one of this Disks was corrupt and was changed to an new one . After this the RAID was build in the new Disk .

Here the Steps what we do on this Server :

In the Begining we have on our Repository Server 2 Partitions on an 70 TB Volume .
The one Partition was an REfs Partition with 20 TB on which this now corrupted Backup Files resist .
The other Partition was an NTFS Partition with 50 TB .

Now we decide to make the 20 TB Partition smaller because there should later resist only Windows Archiv Files .
But when we try to reduce the Place we see that you cant shrink an Volume which is Formated with REFS .
Therefore we have to Format this Drive with NTFS .
For this we move the Veeam Backup Files from the 20TB Partition tot he 50TB Partition .
Then we Format the 20TB Partition with NTFS . Now it was possible th shrink this Partition to 5 TB .
That is now ok .

But now we have the Problem that we cant extend this 50 TB Partition to 70 TB because we find out that this Partition is Formated with an Blocksize of 16K , that means the highest value for this Partition can be 64TB .

Now we create with the unused Space on the Volume an new 20 TB Partition with an Block Size of 32K . That means we can extend this Volume to 70TB now.
Then we copy all the Files inluded the Veeam Backup Files from the 50TB 16K Blocksize Partition tot he 20TB 32K Blocksize Partition .

After this we delete the 50 TB 16k Blocksize Partition . Now we use the free place to extend the 20 TB 32K Blocksize Partition tot h 70TB .

After this all the Files are corrupt .

I hope this helps you to understand what we do .

But can this destroy all the Files ?!? The only thing what we do ist o move the Files over Partitions with differnet Block Sizes .

Michael

[PetrM]

Hello,

But can this destroy all the Files ?!? The only thing what we do ist o move the Files over Partitions with differnet Block Sizes .

I would say that this is most likely a reason of data corruption in your particular case, may be we are not aware of some additional factors which played key role for your scenario.

By the way, we always recommend to follow 3-2-1 rule in order to ensure successful restore even when primary storage is corrupted or lost.

Thanks!