XenOrchestra FileLevelRestore
-
So I think I know what the fix is, and just want to see if anyone here has any simpler ideas.
Problem: XO can't do FLR on one of my backed-up VMs. Complains that partx can't read the partition table. Further investigation shows that the file system is directly on /dev/xvdb and not in a partition.
Context: Luckily this is a 2nd drive that's used for NC data and it works fine as-is.
Possible (Only?) Solution:
- Add another drive to the VM equal or greater in size than the one that's causing problems
- format new volume / drive properly with partition table goodness and appropriate fairy dust
- copy everything at file level (permissions, timestamps etc etc) from buggy volume to new volume
- change /Data mount to point to new volume
- Fin
If anyone out there has a simple one-liner or something nice that I'm not aware of, please share.
Thanks
-
This sound solid. I have had to do that or rather, just restore the Volume and then mount it? It should be simpler than copying.
-
@dbeato But if I restore the volume it'll restore the "bad" version that's missing the partition table so I'm no better off, right?.... Unless there's some other restore mechanism?
-
@notverypunny said in XenOrchestra FileLevelRestore:
@dbeato But if I restore the volume it'll restore the "bad" version that's missing the partition table so I'm no better off, right?.... Unless there's some other restore mechanism?
I should have asked, what type of backup you have setup for the VM on XenOrchestra?
-
@dbeato It's a full VM delta backup. I was able to restore the whole VM to another host and boot it without any problem, but it restores the borked volume as-is (which is what we'd expect, but doesn't help my situation).
It's not a major stress by any means, was just hoping that on top of having been a dummy for messing up the initial setup, I was overlooking or unaware of a simpler / easier way to fix things.
Cheers!
-
@notverypunny You may want to post your issue on the xcp-ng forums as I haven't seen anyone bring up this issue previously.
-
@Danp Hey Dan, I don't think it's on the xcp-ng forum but I had come across something on the XO forum about it. Don't have the post nearby but it's a known issue.