Search results

Ahh, that is amazing news. I ended up just implementing a local pbs, then synching with the remote. But would be amazing to simplify in the future :)

Amazing, again, thank you so much for all the support and apologies for not realizing something so basic...

Oh my, that is an absolutely hilarious oversight on my side. Deeply apologise for wasting your time!! Is there some sort of cache before send option?

I updated the original post to keep it all together. Really appreciate your quick responses!

In order to obsfucate the remote IP, I added a port forward so 192.168.1.254 forwards to the remote IP. I tested this beforehand to ensure its working as intended, and I can access it fine, so it isn't interfering :) The same error happens and the VM fails but the CT is fine. pve host...

Apologies for the double post, but this just got even more weird. Oddly containers will back up fine, to the exact same host, in the same backup process. The container is off currently, potentially there is something I am missing with snapshotting running VM's? INFO: starting new backup job...

Oddly I am getting this exact same issue. What is even more weird is I can back up to the exact same remote backup server with the CLI backup client, from the same host that is failing below. Edit: To add RTT for ping is only 30ms. ERROR: Backup of VM 100 failed - VM 100 qmp command 'backup'...