create_backup_job
Create a scheduled backup job so Proxmox runs guest backups automatically on a calendar schedule, with storage, retention (keep) and per-guest or all-guest targets.
Instructions
Schedule backups: a backup job that Proxmox runs by itself at its time. schedule as Proxmox writes it — 03:00 (every day), mon..fri 21:30, sat,sun 02:00, sun 04:00, or any Proxmox calendar event (*/6:00). Guests: vmids, or all (with exclude). storage: one that takes backups. keep (how many backups to keep: last, daily, weekly, monthly) makes Proxmox delete the older backups of these guests on that storage after each run: it needs the Destroy switch; without keep, the storage's own rule applies. The job gets an ID beginning with claude-.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"host": "<host>",
"schedule": "<schedule>",
"storage": "<storage>",
"reason": "<reason>"
},
"name": "create_backup_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| all | No | Every guest of the host (but those in exclude). | |
| host | Yes | The host's id, from list_hosts. | |
| keep | No | How many backups to keep (Destroy switch). | |
| mode | No | ||
| notes | No | Each backup's note: {{guestname}} and {{vmid}} are filled in. | |
| vmids | No | The guests it backs up. | |
| reason | Yes | Why you are doing this, in a sentence. The user sees it in the approval window and in the log. | |
| comment | No | ||
| enabled | No | ||
| exclude | No | ||
| storage | Yes | ||
| compress | No | ||
| schedule | Yes | When: 03:00 · mon..fri 21:30 · sat,sun 02:00 · sun 04:00 · a Proxmox calendar event. |