Backups
Backup jobs, the day browser, Backup now, restore and retention, with use and create as separate rights.
Overview
Backups are full copies of a VM in a backup repository, independent of the VM's storage. Verlocx shows your Proxmox backup jobs and archives in a browsable, permission-scoped interface, so restoring doesn't require hypervisor access. Job definitions stay on Proxmox.
| Permission | Allows |
|---|---|
| backup.view / backup.view.all | See backups of owned VMs / of all VMs |
| backup.use | Restore from an existing backup |
| backup.create | Backup now, run or enable jobs |
| backup.delete | Delete backup points or jobs |
| backup.repos.view | See the Repositories tab |
On the VM
- The Backups tab groups archives by day, with count, total size, types (full or incremental) and status. A calendar view shows backup density over the year.
- Clicking a day lists its archives with time, type, size, repository, retention and status.
- Restore (backup.use, completed archives only) and Delete (backup.delete) each ask for confirmation and recap the backup's date, size and repository.
- Backup now (backup.create) queues an immediate backup, for example right before maintenance. It is also in the VM's action menu.
The project Backups page
- Jobs: every scheduled job with schedule, mode, selection, storage, retention, next run and whether it is enabled.
- Backup points: every archive with date, VM, format, size, storage and notes. Archives protected from pruning carry a shield icon.
- Repositories: one card per backup storage with archive count, total size and last write.
- A job's own page has Schedule, Targeted VMs, Run history and Settings tabs. Settings holds the enable switch and Run now.
Automatic job assignment
A template can be configured with a backup job prefix in its Defaults. New VMs from that template are then added to the job for the node they land on. When a VM migrates, it moves to the target node's job. This step never fails a deployment; problems are reported in the step's message.
Retention
- Each archive carries the retention from its job.
- Prune protection keeps selected backup points out of retention cleanup, for example a known-good state before a migration.
- Deleting a VM keeps its existing backups.
Features on this page
- Backup browser
- Backup now
- Restore from backup
- Backup jobs and repositories
- Prune protection
- Automatic backup job assignment
More in Data protectionAll topics
SnapshotsPoint-in-time rollback: create, restore and delete, shown as a tree with the current state.TemplatesAllow golden images per project, cap their resources and set per-template provisioning rules.ClustersConnect Proxmox clusters, watch hosts and storage, fail over between API endpoints, and onboard existing guests.