Running Proxmox Backup Server in the cloud or offsite (S3, Hetzner, hosting)

What are the ways to get backups off site?

The Proxmox Backup Server (PBS) documentation names three ways to keep a copy somewhere else:

  • a second backup server that is synchronised with a sync job
  • an S3-compatible object store as the storage backend of a datastore
  • tape backup as a second storage medium

According to the manual, a “remote” is a separate PBS installation plus a user on it. How the server itself is installed is covered in Install and set up Proxmox Backup Server, and what it costs in Is Proxmox Backup Server free?.

How do I copy to a second backup server?

For a remote, the manual says you need the host name or IP address, a user and password on the remote, and its certificate fingerprint. proxmox-backup-manager cert info on the remote prints the fingerprint. The manual shows these commands for the remote and the sync job:

proxmox-backup-manager remote create pbs2 --host pbs2.mydomain.example --userid sync@pam --password 'SECRET' --fingerprint 64:d3:ff:3a:50:38:53:5a:9b:f7:50:...:ab:fe
proxmox-backup-manager sync-job create pbs2-local --remote pbs2 --remote-store local --store local --schedule 'Wed 02:30'

A sync job can run in pull or push direction, the manual says. The roadmap lists push mode since version 3.3. For push:

  • The remote must support namespaces (minimum version 2.2).
  • The manual strongly advises a dedicated remote configuration with its own user for each push job, because otherwise jobs can remove each other’s snapshots. The user in that remote configuration, meaning on the target, should have limited permissions.
  • Separate from that is Remote.DatastorePrune: the user of the sync job needs this right on the sending server, on the path of the remote. It exists only to remove vanished snapshots and groups on the target.

With remove-vanished, a sync job deletes on the target what has disappeared at the source. The documentation says to leave it off, so that an attacker who has taken over the source cannot cause deletions on the target hosts. That is the pull case, where the target fetches from the source; for push jobs, the rights in the list above apply. verified-only or encrypted-only limits the job to verified or encrypted snapshots.

What does the manual say about the 3-2-1 rule?

The manual describes the rule as three backups on at least two types of storage media, with one copy off site. It names a remote with sync jobs as one way and considers such instances less likely to be infected when ransomware hits the local network.

How do I encrypt backups for a location I do not control?

PBS transfers data over TLS and also supports client-side encryption, but according to the FAQ it is not enabled by default. The manual names AES-256 in GCM mode. For the client it looks like this:

proxmox-backup-client key create my-backup.key
proxmox-backup-client backup etc.pxar:/etc --keyfile /path/to/my-backup.key

Proxmox VE offers the same encryption on the storage; the Proxmox VE manual says it can be set in the web interface or with the option encryption-key. Both manuals warn alike: without the key the backups are inaccessible, and the key must not live on the system being backed up.

Can the sync job encrypt by itself?

Since PBS 4.2 (29 April 2026), a push sync job can encrypt unencrypted snapshots before sending them. The roadmap gives servers at less trusted offsite locations as an example. Snapshots that are already encrypted are pushed unchanged, partially encrypted ones are skipped. An existing key is assigned like this:

proxmox-backup-manager sync-job update pbs2-push --active-encryption-key key0

How do I limit the traffic?

Sync jobs have their own limits: rate-in for pull, rate-out for push, plus burst-in and burst-out for short bursts. The manual shows:

proxmox-backup-manager sync-job update ID --rate-in 20MiB

The server’s general traffic control rules explicitly do not apply to sync jobs.

Can I use S3 object storage as a datastore?

Yes, since PBS 4.2 it is officially supported according to the roadmap. It has been possible since PBS 4.0 (6 August 2025), at first as a “technology preview”. The manual for version 4.2.10-1 names these points:

  • The bucket and the access key must be created at the provider beforehand. PBS acts as a client and needs permission to get, put, list and delete objects.
  • The connection uses HTTPS only. For self-hosted S3 with a self-signed certificate the endpoint needs the fingerprint.
  • The datastore still needs a local persistent cache. 64 to 128 GiB are recommended, best on a dedicated disk, partition or ZFS dataset with a quota.
  • A datastore cannot be shared between several backup servers at the same time. If the server fails, the contents can be reused on a fresh installation.
  • The provider may charge for storage, API requests, egress and bandwidth. The manual therefore recommends monitoring these values and the costs.

The manual gives these commands:

proxmox-backup-manager s3 endpoint create my-s3-ep --access-key 'my-access-key' --secret-key 'my-secret-key' --endpoint '{{bucket}}.s3.{{region}}.amazonaws.com' --region eu-central-1
proxmox-backup-manager datastore create my-s3-store /mnt/datastore/my-s3-store-cache --backend type=s3,client=my-s3-ep,bucket=pbs-s3-bucket

What is documented about Hetzner?

For Hetzner there are only statements from Hetzner itself, and Hetzner’s product and documentation pages for the Storage Box and Object Storage mention neither Proxmox nor PBS.

What does the Storage Box offer?

Hetzner lists FTP, FTPS, SFTP, SCP, SMB/CIFS, BorgBackup, Restic, Rclone, rsync over SSH, HTTPS and WebDAV. S3 is not among them.

According to Hetzner the data sits on several disks in a RAID, but on a single host server. According to the PBS manual, a datastore is a directory in a Unix file system (ext4, xfs or ZFS). Whether a mounted Storage Box is suitable for that, none of the sources says.

What does Object Storage offer?

Hetzner calls it S3-compatible and speaks of “basic compatibility” with the Amazon S3 actions. That PBS works with this service is stated neither there nor in the PBS manual.

What about hosting or a cloud VM?

If the second PBS runs at a hosting provider, it is simply a remote for the first one, see above. Note that on its Get Started page Proxmox recommends dedicated hardware rather than a virtualised instance; that is a recommendation, not a ban. How the VMs themselves are backed up is covered in Backing up and restoring Proxmox VMs.

Is tape a good second medium?

The manual names tape as a second storage medium that can be taken off site or kept in a fireproof vault.

For the copy off site, Nexilon offers a managed offsite PBS in its own data centres.

Sources

Let's talk

Free initial consultation - no sales pitch, just an honest assessment.

Request a consultation →