File Level Restore results in "Error while scanning disk"

EpicLPer

Heya!

Currently testing XCP-ng a lot to see if I can replace one of my ESXi hosts with it, but I'm currently running into a bit of an issue.

I tried a file level restore on a Windows Server and it simply throws an error "Error while scanning disk". This happens to both backed up disks for some reason.
If it's helpful, I'm using the Xen Orchestra Community edition running on Docker on my Synology, where I used a mounted Docker volume as a Local destination for the backup job. The whole VM restore worked just fine this way, just not the file restore.

Thanks already for your help!

olivierlambert

Are you using NTFS format inside your Windows? If yes, have you installed any ntfs capable driver in your OS?

EpicLPer

You mean the OS running Xen Orchestra or XCP-ng?

olivierlambert

I suppose your Windows guest OS is using NTFS and not ReFS or something exotic?
If you don't understand at all how backup are restored, let me give a quick crash course: everything is going through your XO operating system. File level restore will mount the VHD disk inside XO system so you can browse it. So you need to be able to read a partition content with the proper "driver" (ext, xfs, NTFS...). So now it should be pretty obvious on what you need to file level restore a drive

EpicLPer

@olivierlambert It is NTFS, yes And yeah, kind of thought this is how it's doing it, and since I'm running Xen Orchestra inside Docker the Docker Image might not have NTFS support.
I've opened an issue tho on Github for it, so I'll see what comes from this. Thanks for the crash course tho!

olivierlambert

Note we don't have any official 3rd party installer or Docker, so use it at your own risk and support can only be done by the 3rd party provider

EpicLPer

@olivierlambert Yeah, course! I'm not too familiar with more advanced things yet or "how things work under the hood", coming from ESXi even there I was sometimes overwhelmed by a few things. Still learning, and once I understand how things work together it does make sense

rittmeister

You should probably be able to fix this issue by installing the ntfs-3g package.

As you mentioned you're running it on a Synology, you can do that in DSM by opening Docker -> Container -> Select your container -> Details -> Terminal and enter the below in the console.

apk update

apk add ntfs-3g

Let us know if it helped.