file restore test

[godfather007]

Tried 3 different sizes ... all worked well... given I used only some txt files to use during restore testing.

Going to start over with dedup as well while throwing a few gb's of data on it as well...

 

[godfather007]

Arrrgg.. i cannot re-create the problem... on a fresh machine... i'm starting to realize something else must be wrong on a windows/ntfs level.

 

[godfather007]

The test-machine stays working. Files can be restored.

It feels like it has to do with the disks integrity. I'll investigate and report back here.

 

[fabian]

FWIW, I've built proxmox-backup-restore-image packages (for PVE 8.1+) that use the 'ntfs3' driver instead of 'ntfs', if you want you can give them a spin and see if they work better for your snapshot:

http://download.proxmox.com/temp/file-restore-ntfs-3/

$ sha256sum *.deb
23aeab40e58a130901d2b023e11339903dd90dd8ef11cb5caae8d7bafa32596c  proxmox-backup-restore-image_0.6.1~test1_amd64.deb
0f6e4746cc9408bdc3c3d81c0834531eb8fdaaa94ffd2a804a02b7c6581e6a52  proxmox-backup-restore-image-debug_0.6.1~test1_amd64.deb

 

[godfather007]

Yes, this one works!

I tried it on 1 host on my staging environment... the second partition of the drive finally unfolds!

Is there some testing with it that needs to be done before it can be taken in production?

Martijn


Too bad, M$ did not release any recent ReFS info for a linux driver :
https://en.wikipedia.org/wiki/ReFS#Reverse_engineering_and_internals

 

[fabian]

Is there some testing with it that needs to be done before it can be taken in production?

you can easily revert to the stock one if you find problems (but please tell us about them). the only difference between the regular package and this one is that it uses a different NTFS driver in the kernel image used for file-restore. I'd just like to gather some feedback to see if we can unconditionally switch, or if we need to offer both variants in some fashion.

 

[entilza]

Hi, thanks. Just to be clear I am overwriting the standard files with this? Should I backup the old ones.

 

[entilza]

Thank you this worked!!

 

[fabian]

great to hear! you can always revert to the stock package by installing it again ("apt install --reinstall proxmox-backup-restore-image=VERSIONYOUWANTTOINSTALL")

 

[debid]

you can easily revert to the stock one if you find problems (but please tell us about them). the only difference between the regular package and this one is that it uses a different NTFS driver in the kernel image used for file-restore. I'd just like to gather some feedback to see if we can unconditionally switch, or if we need to offer both variants in some fashion.

We just experienced this with one of our nodes and installing the test deb files fixed our issues. Seems like the ntfs-3g is required for some reason, happy to send over logs if helpful to get this into production.

Edit:
We just tested on a 11TB backup thats not been validated, and it looks to have the same error message as reported. Our validated older 11tb backups (2 weeks and longer) are ok with the changed file-restore packages.

 

[fabian]

We just tested on a 11TB backup thats not been validated, and it looks to have the same error message as reported. Our validated older 11tb backups (2 weeks and longer) are ok with the changed file-restore packages.

did those older backups not work with the package from the repositories? or did they also work before?

could you post the full debug log and error message for the new one that is failing with the patched package?

 

[christophe]

FWIW, I've built proxmox-backup-restore-image packages (for PVE 8.1+) that use the 'ntfs3' driver instead of 'ntfs', if you want you can give them a spin and see if they work better for your snapshot:

http://download.proxmox.com/temp/file-restore-ntfs-3/

$ sha256sum *.deb
23aeab40e58a130901d2b023e11339903dd90dd8ef11cb5caae8d7bafa32596c  proxmox-backup-restore-image_0.6.1~test1_amd64.deb
0f6e4746cc9408bdc3c3d81c0834531eb8fdaaa94ffd2a804a02b7c6581e6a52  proxmox-backup-restore-image-debug_0.6.1~test1_amd64.deb

Yes, we worked on that but at the PVE host level, and concluded everything works better with ntfs3 (given by Paragon Software for Linux 5.15?).
Everything works well EXCEPTED deduplicated files, despite some notes about it (https://www.paragon-software.com/ntfs-deduplication-support/#features). ntfs produces an error, ntfs3 no error but restored file is empty or unusable.
Be careful with Windows dedup : dedup jobs start after a few days, the way to effectively see if a file is deduplicated is via properties, if "size" is very different than "size on disk".
Dynamic disks and "software raid" (forgotten exact Windows wording) now works correctly.

ReFS is not (yet?) usable with File Restore.

And file restore for Windows VM il really important for a large number of PBS users...

Christophe.

 

[fmunier]

Hi,
We encounter the same problem !
We are unable to restore files from a NTFS partition !

On the other hand, after installing ntfs-3g package in proxmox CLI, I can manually map and mount this backup without error and see all files in the partition.

 

[fabian]

Hi,
We encounter the same problem !
We are unable to restore files from a NTFS partition !

On the other hand, after installing ntfs-3g package in proxmox CLI, I can manually map and mount this backup without error and see all files in the partition.

did you test the packages linked earlier in the thread as well?

 

[fmunier]

Yes, it's installed, but same problem !

 

[fabian]

what kind of NTFS setup are you using? anything peculiar?

 

[fmunier]

nothing particular, no dedupplication

There if 4 disks on this VM


ProxMox GUI File Restore can access C, E and F partitions but not D
But, as sayed, I can mount D: partition under linux (installed ntfs-3g in Debian)

File restore on D: causes error :

 

[fmunier]

I've also tried to chkdsk on D:, but same problem

 

[fabian]

could you also post the file-restore debug log?

 

[fmunier]

Here is the qemu.log