Backup job error: disk skipped due to unsupported storage type: largeblock
AllowAnyStorage already set to true, service restarted - no change.
Is there a workaround, and is largeblock support planned? Also, would QCOW2 disks on a plain EXT SR work instead, or is QCOW2 unsupported too?
-
kurt
- Enthusiast
- Posts: 79
- Liked: 2 times
- Joined: Jul 07, 2010 9:03 pm
- Full Name: Kurt
- Contact:
-
kurt
- Enthusiast
- Posts: 79
- Liked: 2 times
- Joined: Jul 07, 2010 9:03 pm
- Full Name: Kurt
- Contact:
Re: XCP-ng largeblock local storage?
Rebuilt the affected local SR as plain EXT with Preferred image format set to qcow2 (instead of largeblock). Migrated the VM's disk onto the new SR, which converted it to qcow2 automatically. Set AllowAnyStorage back to false, removed and re-added the XCP-ng host in Veeam - it now sees the storage. I will test the backup job again.
-
ronnmartin61
- Product Manager
- Posts: 779
- Liked: 306 times
- Joined: Mar 07, 2016 3:55 pm
- Full Name: Ronn Martin
- Contact:
Re: XCP-ng largeblock local storage?
@kurt it's not explicitly mentioned as supported SR type here - https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13 but will discuss internally.
-
kurt
- Enthusiast
- Posts: 79
- Liked: 2 times
- Joined: Jul 07, 2010 9:03 pm
- Full Name: Kurt
- Contact:
Re: XCP-ng largeblock local storage?
Thanks for the follow-up. I switched my SR from LargeBlock to a standard EXT SR with QCOW2 as the preferred image format.
That resolved the issue on my end. Veeam now recognizes the storage correctly and my backup job ran successfully. This is probably the preferred SR type and format going forward anyway so all set for now. Thanks
That resolved the issue on my end. Veeam now recognizes the storage correctly and my backup job ran successfully. This is probably the preferred SR type and format going forward anyway so all set for now. Thanks
Who is online
Users browsing this forum: No registered users and 12 guests