Restoring Windows Software RAID 5 partition

[Alfa]

Hello everyone,

We currently have a problem when we try to restore a Windows Software RAID 5 with Veeam. This is a pure data partition and not a boot disc. During the volume level restore process we have selected the 3 affected disks as parity disks and in the progress window it finally hangs with the following error message. Have you ever had something like this and is it even possible to completely restore this RAID 5 array with Veeam?

Code: Select all

30.09.2024 10:45:40 Error Updating disk partition structure Error: The specified data carrier extension exceeds the size of the available storage space.
                              VDS error code: 0x80042515
                             Failed to initialise volume creation.
                             Agent failed to process method {DiskManagement.CreateVolume}.
                             The specified data carrier extension exceeds the amount of available storage space.
                              VDS error code: 0x80042515
                             Failed to initialise volume creation.
                             Agent failed to process method {DiskManagement.CreateVolume}.
30.09.2024 10:45:41 Error Restore failed: The specified data carrier extension exceeds the size of the available storage space.
                              VDS error code: 0x80042515
                             Failed to initialise volume creation.
                             Agent failed to process method {DiskManagement.CreateVolume}.                            

[RogerMialkowski]

Hello Alfa,

Have you tried recreating the RAID 5 volume first and then point Veeam to restore to the single RAID 5 volume? Not sure if Veeam knows what to do with 3 raw disks. Keep us updated.

Thanks,
Roger

[Matts N]

Also... Are you sure you are should select all three disks as parity disks? A RAID-5 normally consists of x number of data disks and a single parity disk, in your case I would assume 2 data disks with the 1 parity disk.

[MPECSInc]

Hello Alfa,

Have you tried recreating the RAID 5 volume first and then point Veeam to restore to the single RAID 5 volume? Not sure if Veeam knows what to do with 3 raw disks. Keep us updated.

Thanks,
Roger

This is the correct way. The underlying OS setup needs to be completed prior to initiating the restore. Veeam has no clue about the storage setup itself at that level. It's the same as needing an F6 driver to allow Windows to see a newer RAID or HBA Controller that has no driver built-in to the operating system.

[Alfa]

Hello Alfa,

Have you tried recreating the RAID 5 volume first and then point Veeam to restore to the single RAID 5 volume? Not sure if Veeam knows what to do with 3 raw disks. Keep us updated.

Thanks,
Roger

Hello Roger,
I have now created a new RAID 5 Volume in Windows, but when I now open the restore Volume function in Veeam, I cannot assign a restored volume, because the disk are now in "Healthy" state.

[Alfa]

Also... Are you sure you are should select all three disks as parity disks? A RAID-5 normally consists of x number of data disks and a single parity disk, in your case I would assume 2 data disks with the 1 parity disk.

Hello Matts,
when I am in the Veem Volume Restoring process, I can select in the dropdown for restoring the volume "Restore as: " and then select the mode with the options "Simple volume", "Span volume", "Stripe volume", "Mirror volume" and "Parity volume". I cannot use only parity or data disks. When I select "parity volume" I must select all avaible disks, which should been used for restoring process and when I select the 3 already mentioned disk, which were a RAID 5 before, it throws the error mentioned before.

[eesa]

Hallo,
I was about to present the same issue, but I found that someone else has already encountered it.
Have you reached a solution, or does anyone have any ideas on how to resolve this problem?