Skip to main content

Connect PBS to Proxmox VE

This guide adds your HostMyServers managed PBS datastore as a storage in Proxmox VE, then configures backup jobs.

Compatibility

Native PBS integration is available from Proxmox VE 6.3 onwards.

1. Retrieve connection details

From the HostMyServers client portal, Connection (or Authentication) tab:

InformationExample
PBS server URLhttps://pbs1.hostmyservers.fr:8007
Datastore namebackup-hms
Usernameuser@pbs or an API token user@pbs!token-name
Secret / passwordprovided in the client portal
API token recommended

Prefer an API token over a user account for automated connections. A token can be revoked independently without affecting other access.

2. Add the storage in Proxmox VE (web interface)

In the Proxmox VE interface:

DatacenterStorageAddProxmox Backup Server

Fill in the fields:

FieldValue
IDLocal storage name (e.g. pbs-hms)
ServerPBS server URL (without https:// or port)
UsernamePBS username or token
Password / SecretSecret provided in the client portal
DatastoreDatastore name (e.g. backup-hms)
Namespace(optional) target namespace if used
No fingerprint needed

The HostMyServers PBS service uses a certificate signed by a recognized CA. You do not need to enter a fingerprint.

Click Add.

3. Add the storage via CLI (optional)

From a Proxmox VE node:

pvesm add pbs pbs-hms \
--server pbs1.hostmyservers.fr \
--datastore backup-hms \
--username user@pbs!token-name \
--password <secret>

Check status:

pvesm status --storage pbs-hms

4. Configure a backup job

Once the storage is added:

DatacenterBackupAdd

Recommended settings:

ParameterRecommendation
Storagepbs-hms
Schedule02:00 (nightly backup)
SelectionVMs / CTs to include
ModeSnapshot (no VM downtime)
Compressionzstd
RetentionConfigure via PBS prune policy (see Configuration, retention and verification)
NamespaceOptional — useful in multi-cluster setups

Run the first job manually to verify connectivity and confirm snapshot creation on the PBS side.

5. Verify reception in PBS

From the HostMyServers client portal, Content tab:

  • The snapshot should appear under vm/<vmid>/<timestamp>
  • The deduplication ratio updates after the first GC run

Best practices

  • Create one token per Proxmox VE cluster — revocation remains independent
  • Restrict token permissions to the strict minimum on the datastore
  • Schedule backup jobs outside production hours to limit network and I/O impact
  • Test a restore after setup — an untested backup is not a guarantee
Restore testing is mandatory

Run a restore test right after setup, then regularly (monthly is recommended). A snapshot that has never been verified may contain silent corruption.