Skip to content
NexoVirt

Backups (PBS)

NexoVirt integrates with Proxmox Backup Server (PBS) for the full backup lifecycle: connecting a server, attaching it to your PVE hosts, browsing snapshots, garbage-collecting and verifying datastores, and pruning old backups on a schedule.

Adding a PBS server

Section titled “Adding a PBS server”

Under Settings → PBS, add a server with its address and an API token. NexoVirt authenticates with token auth and pins the server’s certificate fingerprint. The token secret and the datastore encryption key are both encrypted at rest.

  1. Add the PBS server (address, token, fingerprint).
  2. Attach it to one or more PVE hosts as a pbs-* storage, or import an existing PBS storage already configured on a host.
  3. Open the server’s manage page to see datastore status and browse backups.

Managing a server

Section titled “Managing a server”

Each PBS server has its own manage page with:

  • Datastore status and a snapshot browser (a searchable, sortable table of backups).
  • Garbage collection and verify jobs, tracked by their Proxmox task ID (UPID) until they finish.
  • Manual prune with a dry-run preview before you apply it, using the standard PBS keep-* retention parameters (last / daily / weekly / monthly / yearly).

Scheduled prune policies

Section titled “Scheduled prune policies”

Instead of pruning manually, define a prune policy per server: keep-last, keep-daily, keep-weekly, keep-monthly, keep-yearly, an evaluation interval, and an enabled toggle.

Encryption key rotation

Section titled “Encryption key rotation”

A PBS server’s datastore encryption key can be rotated from its manage page:

  • The active key is archived (its fingerprint and encrypted key material are kept).
  • A new key is generated and applied.
  • All PVE storages attached to that server are re-keyed on a best-effort basis.
  • The key-history view exposes only fingerprints and dates, never the key material itself.

Backup alerts

Section titled “Backup alerts”

Two alert types are built into the alerting engine: backup failed and backup stale, so a missed or failing backup job shows up in the same inbox, email and webhook channels as every other alert.

Next steps

Section titled “Next steps”