AXureous Backup

Sign in

AXureous Backup
Email isn't set up yet, so alerts only show here. Set up email
No servers yet. Add your Proxmox hosts and backup server to start watching backups.

Virtual machines and containers

StatusIDNameHost / node Last backupLimitBackup job

Backup jobs (last 30 days)

ResultStartedTookWhereGuests

Backup server

Servers

Add server

Making an API token

AXureous Backup signs in with an API token, not your root password. A token can only read and start backups, so it can't change anything else.

On each Proxmox host (once per cluster is enough)

pveum role add AXBackup -privs "VM.Audit VM.Backup Datastore.Audit Datastore.AllocateSpace Sys.Audit"
pveum user token add root@pam axbackup --privsep 1
pveum acl modify / -token 'root@pam!axbackup' -role AXBackup

The second command prints the secret once. Enter root@pam!axbackup as the token ID and that secret above.

On the Proxmox Backup Server

proxmox-backup-manager user generate-token root@pam axbackup
proxmox-backup-manager acl update /datastore DatastoreAudit --auth-id 'root@pam!axbackup'
proxmox-backup-manager acl update /system Audit --auth-id 'root@pam!axbackup'

The certificate fingerprint is shown on each server's dashboard (Proxmox: node → System → Certificates; PBS: Dashboard → Show Fingerprint).

When is a backup late?

Normally only VMs in an enabled backup job are watched; the rest show as "Not in a job" and never alert. Each VM can have its own limit, be switched on, or be left out: use the ⋯ button on its row on the Dashboard.

Retries

A retry backs up just that VM, to the storage its scheduled backup job uses (or the server's default storage). It waits while another backup is running on the same node.

Email me when

Login password

Email (SMTP)

Server certificate

If your mail server uses a self-signed certificate, check it here and trust it. Only that exact certificate is accepted afterwards, so a different server can't pretend to be yours.

Activity