[SOLVED] Copy from backup PBS back to PVE without restoring

[isaacntk]

I have an off-site PBS server with a PCT backup that is 1.87 TB I need to restore that backup but the transfer will take 4 days (because internet is slow). I experienced a power loss halfway through and need to restart

Wondering if there's any way to copy PBS backups to PVE storage via rsync --partial, so I can restore locally and still resume in case of any network disruptions

Also, is the task message supposed to be so unverbose that it doesn't even have a progress readout for the transfer? The only message I get while the backup is happening is:

recovering backed-up configuration from 'host:backup/ct/206/2022-07-14T20:41:20Z'
restoring 'host:backup/ct/206/2022-07-14T20:41:20Z' now..

 

[fabian]

I have an off-site PBS server with a PCT backup that is 1.87 TB I need to restore that backup but the transfer will take 4 days (because internet is slow). I experienced a power loss halfway through and need to restart

Wondering if there's any way to copy PBS backups to PVE storage via rsync --partial, so I can restore locally and still resume in case of any network disruptions

well, you can setup PBS + a datastore locally (either on the PVE host itself, or in a VM on the PVE host, or on a baremetal machine in the local network) and then use the built-in sync mechanism to just sync that group from the real PBS to the local one. as long as you don't run a garbage collection locally an interrupted sync should pick up again where it left off when you restart it, once the sync is complete you can give your PVE host access to the local PBS and do the restore from there. the obvious downside is that you need the space to store both the backup and the restored data (but that is true for any solution that transfers the backup data before restoring).

Also, is the task message supposed to be so unverbose that it doesn't even have a progress readout for the transfer? The only message I get while the backup is happening is:

recovering backed-up configuration from 'host:backup/ct/206/2022-07-14T20:41:20Z'
restoring 'host:backup/ct/206/2022-07-14T20:41:20Z' now..

yes. room for improvement there definitely, both for backing up as well as for restoring

 

[isaacntk]

Wow thanks for the quick reply. This seems like a decent workaround for the moment, and I do have enough space for it. Thanks for the suggestion!