Restore of entire Linux vm

[EBoucq]

Hi,

How can you prevent the change of UUID / SCSI number of disks when you restore an entire Linux VM with Veeam ?
Is that a Veeam issue ?

I recently had to restore an entire VM and after a successful restore, the vm started and I got:
"fsck.ext3: no such file or directory while trying to open /dev/disk/by-id/scsi-xxxxxxxxxxx
the superblock could not be read or does not describe a correct ext2 filesystem.
"

Thanks.
Eric

[foggy]

Eric, could you please make sure the required disk was not excluded in the corresponding backup job?

[EBoucq]

Hi foggy,

No exclusion. All the disks were restored. Nothing is missing. But it seems that something during the restore process changes disks settings inside the OS (UUID, SCSI,..)
It's not the first time that happened. Always with Linux vm...

Thanks.

[Vitaliy S.]

Does this also happen during isntant VM recovery? Can you please clarify "SCSI number of disks" as I'm not sure I fully understand what you're referring to? Thanks!

[EBoucq]

Sorry about the SCSI comment. It's only the UUID of some disks. I haven't tried instant recovery so I can't answer your question.

[Vitaliy S.]

What is the type of these disks? What happens if you try to restore just this virtual disk and then add it to the VM? Veeam does not force UUID change, so I would appreciate if you could share the results for your tests.

[dellock6]

uuid is changed in several scenarios under VMware, and the problem is that linux relies on these identifiers. Did you restored the VM in place or in a different position? Because the uuid usually changes when the storage path changes. It's the same as copying/moving the VM and receiving the popup question "the VM has changed, was it moved or copied?".

[PKaufmann]

Just found this topic because I have the same issue with a linux VM.
Unfortunately I am not good at Linux

I tried instant recovery.
/dev/disk/by-path/pci-0000:00:10.0-scsi-0:0:1:0-part1: The superblock could not be read or does not describe a correct ext2 filesystem....

checked the VM and 1 disk was excluded by the backup job (SCSI 0:1).

I'll try to remove this disk from fstab .. hmm not really sure what I am doing but I have to try

[PKaufmann]

removing disk from fstab did the trick