How-to
Configure PBS Remote Sync for offsite copies.
Push backups from your PBS to an offsite PBS and confirm the copy is available. Push direction is outbound-only and entirely self-service — nothing to configure on the far side.
Steps
- Collect the offsite PBS details. Hostname, user/token, datastore name, and TLS fingerprint. On a hosted plan these come from your billing portal.
- Add the offsite server as a Remote. On your PBS: Configuration > Remotes > Add, enter the details, approve the fingerprint.
- Create a push Sync Job. Datastore > Sync Jobs > Add: set Sync Direction: Push, your local datastore as source, the remote datastore as target. Pick namespaces if used, and leave Remove vanished off so local deletions never propagate offsite.
- Run the first sync now. Trigger manually to seed the offsite copy. Watch bandwidth and job logs — the first run moves everything, every later run only the changes.
- Confirm the offsite copy. The sync job log lists the groups and snapshots transferred; counts should match your local datastore.
Prereqs
- PBS 3.3 or later on your side (push direction)
- Outbound TCP 8007 to the offsite PBS — no inbound rules needed
- Token that can write backups on the offsite datastore
- TLS fingerprint for trust
- Bandwidth expectations noted
Quick checks
- Sync job completes without fingerprint or auth errors.
- Remote datastore shows snapshots after first run.
- Snapshot counts align with what you expect to see.
- Bandwidth stays within acceptable limits.
If something fails
- Re-fetch and approve the remote fingerprint.
- Confirm the token can write backups on the target datastore.
- No "Push" option in the direction dropdown? Your PBS predates 3.3 — upgrade first.
- Check namespace selection matches what you expect to sync.
- Inspect bandwidth/latency and adjust the job's rate limit.
Related guides
Official docs
Reference: Proxmox PBS Remote Sync docs.
Hosted PBS at $4.95/TB.
No storage limits—$4.95/TB with compute and RAM included. We run the infrastructure; you keep control.