XO Backup - question on file level restore

damjank

Hello,

I enabled Delta backups for some VMs, mainly, where I predict I would need file-level restore. The backup is working, I can use functionality to the point, I start to select files to restore, where I can select none, there is a triangle next to the "/" - I figured out, I think that this is due to that some of the servers are set up to use LVM. Is the LVM file level restore not supported or must I set something else?
If this functionality is used and it is very interesting to us, should we switch to a simple layout and ditch LVM?

Here is some tech info:

Screenshot 2023-05-09 at 11.27.14.png

backupNg.listFiles
{
  "remote": "70cc277b-7a40-4be1-b3bb-af6694d7fd77",
  "disk": "/xo-vm-backups/d6abcfc8-3337-9e66-c175-f58533d688f1/vdis/d91f37df-35a4-4739-b874-8ddfebabe7ff/42718aed-3400-433e-af30-cf516a6c11f2/20230506T230845Z.vhd",
  "path": "/"
}
{
  "code": -32000,
  "data": {
    "code": 32,
    "killed": false,
    "signal": null,
    "cmd": "mount --options=loop,ro,norecovery --source=/tmp/1uvkqhp2qbq/vhd0 --target=/tmp/6ahkt5lz58w",
    "stack": "Error: Command failed: mount --options=loop,ro,norecovery --source=/tmp/1uvkqhp2qbq/vhd0 --target=/tmp/6ahkt5lz58w
mount: /tmp/6ahkt5lz58w: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.

    at ChildProcess.exithandler (node:child_process:419:12)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202305081615/@xen-orchestra/log/configure.js:52:17)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
  },
  "message": "Command failed: mount --options=loop,ro,norecovery --source=/tmp/1uvkqhp2qbq/vhd0 --target=/tmp/6ahkt5lz58w
mount: /tmp/6ahkt5lz58w: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
"
}

Thank you!
rgD

olivierlambert

Hi,

Are you using XOA or XO from the sources?

damjank

@olivierlambert XO from sources

olivierlambert

You should try with XOA and tell us if you can reproduce the issue Also don't forget that your XO from the sources is using the latest master commit.

damjank

@olivierlambert I think I cannot switch XO just like that. I will try to get some demo XCP-ng to get some testing done and try to reproduce the error.
But for the sake of discussion - is LVM supported (in either version) for a file-level restore?

olivierlambert

Why you can't switch? Just deploy an XOA, register/enable trial (I can extend it if you don't have it anymore), import config from your XO from the sources, try and report. This will be very helpful to check if it's something due to your source install or something else. Deploy an XOA is only few minutes

damjank

@olivierlambert then I will make this happen today and report back. I will check for a trial but I do believe it is over (for my address),

olivierlambert

Contact me in chat over here with your email so I can extend a previous trial

rittmeister

Are you trying a file-level-restore for a Windows VM? If so, make sure you have the "ntfs-3g" package installed on your VM running XO.

ryan0413

@damjank any update on this? I’m running into the same issue with an Ubuntu VM (also running XOA from source files).

Thank you!

damjank

@ryan0413 no, nothing.. I have abandoned this

secureme

I have opened a ticket to support because file level restore doesn't work anymore after latest update.

Best regards

Walter