Two ways a guest ends up unprotected
New guests are often never added to a backup job, and guests that are in a job can still go unprotected if the job fails night after night without anyone noticing. A good check covers both. The Proxmox backup and restore documentation explains how backup jobs select guests.
- In any job?
not-backed-uplist - How old is the newest backup?compare with your schedule
- Any failed jobs?failed
vzdumptasks
Step 1: List guests that are in no backup job
pvesh get /cluster/backup-info/not-backed-up
An empty list means every guest is covered by some job. Anything listed needs to be added to a job or deliberately excluded.
Step 2: Check the age of the newest backup
This lists the newest backup age per guest on one backup storage. Replace pve1 and local with your node and storage, and repeat it for each backup storage. Backups on a Proxmox Backup Server storage are listed the same way.
pvesh get /nodes/pve1/storage/local/content --content backup --output-format json | python3 -c '
import sys, json, time
newest = {}
for b in json.load(sys.stdin):
v = b.get("vmid")
newest[v] = max(newest.get(v, 0), b["ctime"])
for vmid, t in sorted(newest.items()):
print(vmid, round((time.time() - t) / 86400, 1), "days old")'
Compare each number with your schedule. For a nightly job, a newest backup older than two days is a warning sign.
Step 3: Look for failed backup jobs
This prints recent backup tasks that did not finish with OK. It only covers recent tasks, so run it regularly:
pvesh get /cluster/tasks --output-format json | python3 -c '
import sys, json
for t in json.load(sys.stdin):
if t.get("type") == "vzdump" and t.get("status") not in ("OK", None):
print(t["node"], t.get("id"), t["status"])'
Check restores, not just backups
Age and job status tell you a backup exists. They do not tell you it works. Follow the guide to test that Proxmox backups actually restore for that last step.
Getting this report automatically
The Proxmox Daily Health Report from Pontavia is free and reports guests with no recent backup or in no backup job, old snapshots and failed backup jobs, along with offline nodes and storage filling up. It only reads. Backup Proof ($79) goes one step further and restores a backup every night to prove it boots.
Frequently asked questions
Why would a Proxmox guest be missing from backups?
Usually a new guest was never added to a job, or a job selects guests by ID or pool and the new guest does not match. It can also be excluded on purpose, which is worth confirming.
How old is too old for a Proxmox backup?
It depends on your schedule. For a nightly job, a newest backup older than about two days suggests a problem. For a weekly job, allow a little over a week.
Does a successful backup job mean the guest is protected?
It means an archive was written. To know the guest can be recovered, restore a backup to a spare ID and check that it boots.
Does this work with Proxmox Backup Server?
Yes. Backups on a Proxmox Backup Server storage appear through the same storage content call, so the age check works the same way.
Related guides
- How to Test That Proxmox Backups Actually Restore
- Stop Forgotten Test VMs: Proxmox Expiry Tags
- Audit Proxmox Access: Users, API Tokens and 2FA
- All guides
Questions about your own setup? Send a message or book a free 15-minute call.