In ProxMenux,
encryption is opt-in. The first host backup asks
"Do you want to encrypt this backup?" — pick
No and no keyfile is generated.
If you say Yes, ProxMenux walks you through this:
- Keyfile source— two options:
- Generate a new one — creates
pbs-key.conf locally at /usr/local/share/proxmenux/pbs-key.conf.
- Use an existing one — if you already have a PBS-managed keyfile for the same repo (e.g. the one PVE uses for its own vzdump backups), ProxMenux auto-detects it; otherwise you point to the file.
- Escrow (optional) — "Upload an encrypted copy of the key to PBS?"— Yes/No:
- Yes → you set a passphrase, ProxMenux wraps the key in an openssl envelope (
pbs-key.recovery.enc) and uploads it to PBS as keyrecovery.conf alongside every backup. PBS never sees the plain key — the envelope is passphrase-encrypted client-side. Only take this route if you trust the PBS host with an encrypted blob whose passphrase you keep separately.
- No → the key stays local. ProxMenux shows you the path and reminds you to make your own offsite copy.
- Download from the Monitor — the ProxMenux Monitor dashboard has a Download keyfile button (Host Backup → PBS encryption card). Download it and store the file in a safe place — an external drive, encrypted vault, another host you control. Treat it as a credential file: keep it intact and off the same machine you're backing up.
On a fresh Proxmox reinstall, the flow is:
- Reinstall ProxMenux, then Host Backup → PBS encryption → Import keyfile and upload the
pbs-key.conf you saved.
- The imported key sits back at the standard path. Point ProxMenux at your PBS datastore and the encrypted snapshots restore normally.
- If you took the escrow route in step 2 and lost the local copy, you can still recover: pull the
keyrecovery.conf blob from PBS, feed it to ProxMenux with the passphrase you set, and you're back in.
If you enable encryption and
neither keep a local copy
nor upload the envelope to PBS
nor remember the escrow passphrase, the snapshots are unrecoverable.
Cheers.