File restore and symlinks

[VictorSTS]

Hello,

I have backup of a LXC container. When doing a file restore from PVE7.4 of a directory that contains symlinks, those symlinks are not included in the .zip file that is downloaded from the webUI. The symlinks are shown in the file browser of the webUI. Also, a full restore of that snapshot does restore the symlinks. That is, the symlinks are included in the backup, they just seem to not be included in the .zip file. Maybe PBS isn't using the "--symlinks" parameter when creating the .zip?

Should the symlinks be included in the .zip file?
Also, I tried to download then in .tar.zst format but the option to do so disappears as soon as I browse the backup files. How can I download a file/directory from the file restore browser?

Thanks!

 

[dcsapak]

Should the symlinks be included in the .zip file?

thats currently not implemented (we use our own zip compression code; and symlinks are not really specified in the original zip specification). you can open a feature request here: https://bugzilla.proxmox.com

as for

Also, I tried to download then in .tar.zst format but the option to do so disappears as soon as I browse the backup files. How can I download a file/directory from the file restore browser?

this is currently only implemented for pxar browsing on the pbs directly. i sent a patch for that last year to add it to pve but that seems to have been overlooked, maybe you can also open a feature request for that, so that we don't lose sight of it again

 

[VictorSTS]

thats currently not implemented (we use our own zip compression code; and symlinks are not really specified in the original zip specification). you can open a feature request here: https://bugzilla.proxmox.com

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=4995

this is currently only implemented for pxar browsing on the pbs directly. i sent a patch for that last year to add it to pve but that seems to have been overlooked, maybe you can also open a feature request for that, so that we don't lose sight of it again

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=4996

Thanks!