Challenge
After Instant VM Recovery or Full VM Restore, a VMware VM appears to have been restored with its disks out of order. However, the disk files are each associated with the correct SCSI, IDE, or SATA disk IDs, disks are not out of order within the VM guest OS, and the VM otherwise functions correctly.Example:
Before restore:| Disk Label | Disk File | Virtual Device Node |
| Hard disk 1 | testVM.vmdk | SCSI (0:0) |
| Hard disk 2 | testVM_1.vmdk | SCSI (0:1) |
After restore:
| Disk Label | Disk File | Virtual Device Node |
| Hard disk 1 | testVM_1.vmdk | SCSI (0:1) |
| Hard disk 2 | testVM.vmdk | SCSI (0:0) |
Cause
Disk labels are not restored by Veeam Backup & Replication. They are determined by the order in which disks are restored. Typically, disks are restored out of order because of parallel processing of either the backup or the restore.Solution
No intervention is necessary, because the VM is functioning correctly.If a workaround is desired: use the vSphere client or web client to shut down the VM, remove its disks, and then re-add the disks in the original order.