This guide covers the Proxmox VM policy workflow. A menu option does not establish end-to-end support for every host/cluster, storage, guest or release. Assess Proxmox VM and LXC scope separately; this UI does not imply an alternative restore target.
Screenshots were captured from the actual lab interface on 16 October 2026. The interface is in English; explanations follow your selected language. Resource names, dates and settings are examples; use values for your own environment.
Some lab screenshots are withheld pending privacy review. Follow the documented steps and use your own environment values.
Lab note: a Proxmox connection is registered, but Clients returned no VMs. The cause was not verified; an empty list is not evidence of successful discovery or a working backup. No new policy or backup/restore was executed.
Proxmox release, host/node and master components
Source access, account scope and repository data path
VM identity, boot/firmware and all disks
Capacity, consistency and isolated restore acceptance plan
01
1. Define Proxmox scope and the test VM
Record Proxmox VE release, node/cluster layout, VM identity and disk storage backend. Do not treat QEMU VMs and LXC containers as the same scope; this guide addresses VM selection. Validate snapshot/backup method against backend and release.
Expected result
VM, disk and topology scope are recorded.
02
2. Verify access and repository prerequisites
Check the correct host/node connection, required API/service access and source storage capacity. Use the installation’s approved credential record; keep passwords and token secrets out of policy names and screenshots. Verify repository access and component releases together.
Expected result
The source and data path are ready for testing.
03
3. Select Proxmox in Attribute
Open Home → Policies → VM Policy → Create Policy. Select Proxmox as Policy Type, the correct Server connection, Policy Name and Storage. If Server is empty, complete source registration/access preparation; do not substitute another platform’s connection.
Proxmox Attribute: registered LAB-CONNECTION connection and example policy. The SOURCE identity name belongs to the test connection; no token secret/password is shown. The draft was not saved.
Expected result
An unsaved draft is prepared for the correct platform.
04
4. Select one VM and its disk scope in Clients
If inventory loads, search for one test VM, select it and check the machine count in Summary. Review required boot/data disks, disk order and passthrough/excluded-disk scope. Do not bypass an empty list or No VM state with Select All/Next and call it successful configuration.
PROXMOX Clients: There is no vm on the relevant server and 0 Machines Selected. The cause was not verified; validate connectivity/permissions/actual inventory before saving a job.
Expected result
The selected VM and all required disks are verified.
05
5. Set consistency and retention for the release
Match Advanced Settings to the installed Proxmox data path. Crash-consistent disk copies differ from application/database consistency. A generic VSS, snapshot or incremental label does not guarantee all guest/storage types; define acceptance for the chosen profile and backup chain.
Expected result
Method, consistency and retention scope are explicit.
06
6. Prepare Schedules and an approved Full test
Use Full/incremental options only to the extent validated in the relevant release. Define the first test window, retention and repository capacity; avoid an unplanned Start Now. Once source/disk selection is complete, review the summary, save only the approved test policy and run the appropriate Full action.
Expected result
The initial test job and retention plan are defined.
07
7. Compare the catalog with actual data acceptance
Compare task result, repository output, VM/disk and catalog time. Last Backup or Active alone does not establish usable data. If Proxmox offers only Original Location, do not assume an alternative target; plan separate restore acceptance in an approved isolated lab. Record backup ID, releases, disk scope and result.
Existing Proxmox jobs show Not Yet Backup. A registered policy or Active status is not successful backup or data acceptance. Enlarge ↗
Expected result
Backup output and recovery acceptance are evidenced separately.
COMMON QUESTIONS
Can I continue with an empty VM list?
No. Validate connection, permissions and inventory before treating the draft as successful configuration or backup acceptance.