Last backup per VM¶
With at least one backup server connected (Proxmox Backup Server, Veeam Backup & Replication or HYCU), the Virtualization tab gets a Last backup panel: every VM on vCenter, Proxmox VE and XCP-ng, and when it was last backed up, by whichever backup server holds the newest. It's free in every edition.
The panel lists what needs a look first. Show all lists every VM.
The verdicts¶
| Verdict | Means | Alert |
|---|---|---|
| OK | Backed up in the last 2 days | none |
| Over 2 days | The newest backup is over 2 days old | warning |
| Over a week | The newest backup is over 7 days old | critical |
| No backup | A backup server that answers for this VM's platform holds no backup of it | critical |
| Not checked | No backup server Collimo reads answers for this VM's platform | none |
| Left out | Off for 30 days, tagged, or listed: see below | none |
The alert is VM's last backup old or missing (vm_backup). It clears
when the VM is next backed up.
Not checked is not the same as no backup
Collimo only says No backup when a backup server it reads covers that kind of VM and doesn't hold it. Proxmox Backup Server covers Proxmox VE. Veeam covers vCenter once it holds any vSphere VM. HYCU covers vCenter when it protects vSphere. Anything else may well be backed up by something Collimo doesn't read, so it says Not checked.
Leaving a VM out¶
Some VMs are meant to have no backup: a build box, a test VM. Three ways to leave one out:
- It's been off for 30 days. Off VMs are judged only if they ran in the last 30 days. Templates are never listed.
- Tag it. In Proxmox VE or XCP-ng, give the VM the tag
nobackup. To use another tag, setCOVERAGE_SKIP_TAG. - List it. vCenter tags aren't read, so list the VM by name in
COVERAGE_SKIP, separated by commas.*matches any run of characters:build01, test-*.
Setting the variables
Both go in the stack, like every other setting:
COVERAGE_SKIP_TAG=nobackup
COVERAGE_SKIP=build01, test-*
See Every variable.
How a backup is matched to a VM¶
The matching rules
Each backup server says which machines it holds; Collimo matches each VM to them by what identifies it best:
- vCenter: the VM's ID in vCenter (such as
vm-100), when the backup server gives it and it's from the same vCenter; then by name. - Proxmox VE: the VM's ID (such as
100). If two Proxmox VE clusters you watch both use that ID, the name has to agree too. - XCP-ng: by name.
A backup that carries an ID is only ever that VM's: if a deleted VM's ID was reused, the new VM isn't matched to the old VM's backups by name. Where several backup servers hold a VM, the newest backup counts.
Metrics¶
infra_vm_backup_ok is 1 for a recent backup, 0.5 over 2 days and 0 over a
week or none, for each VM judged. infra_vm_backup_last_timestamp_seconds
is when each VM was last backed up, labeled with the backup server.