- Home
- Skills
- DevOps & Cloud
- Night Watch: Prove Your Proxmox Backups Still Work
More screenshots
Works with the AI Agents you already use
Night Watch: Prove Your Proxmox Backups Still Work
Backups usually break without anyone hearing about it.
$5
Night Watch: Prove Your Proxmox Backups Still Work
Example session with this skill installed
Proxmox cluster, three nodes, backups to PBS. Two nodes have failed nightly for five days with: fingerprint '83:4f:...' not verified, abort! The PBS certificate was regenerated last week. I've got a real Let's Encrypt certificate on PBS now at pbs.example.com. I tried pvesm set pbs-main --server pbs.example.com and it says can't change value of fixed parameter 'server'. How do I fix this so it doesn't happen again?
- Read your context and instructions
- Compiled the night watch
Summary
Your backups stopped because the storage is pinned to the old certificate's fingerprint. A Let's Encrypt certificate changes at every renewal, so a new pin would break again in about 60 days. The lasting fix is to stop pinning. pvesm set refuses because server is a fixed parameter.
What the answer covers
- Prove the certificate verifies from all three nodes before changing anything.
- Make one edit that covers the whole cluster, without breaking your backup jobs.
- Verify on each node and catch up the five missed nights.
- Work out why the third node looks healthy.
- Find out why this ran for five days with nobody told.
The skill gives your agent the edit and the commands.
Connects securely to your tools. The creator never sees your data.
About this skill
Backups usually break without anyone hearing about it.
Your agent checks
- Every node for guests with no recent backup or no job at all
- PBS fingerprint pins that stop every backup when a certificate changes
- Thin pools nearly full while
dflooks healthy - Failure emails stuck on the host because port 25 is blocked
- Backup jobs that didn't follow a guest moved to another node
You also get a vzdump hook that cancels a job before it fills PBS. It never deletes backups to make room.
How it was tested
The checks come from real backup failures on a multi-node estate, reviewed against Proxmox documentation. We tested the hook against simulated PBS responses. In our benchmark a strong agent answered these scenarios correctly without the skill too, so the value here is the checklist and the hook.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
A missing or non-executable hook stops every backup, so follow the install steps.
The hook has only been tested against simulated PBS responses.
If PBS runs in a container, the thin pool check must run on the host.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
- Software
- Proxmox VE with shell access
SSH key access from each node to PBS for the hook.
Permissions
Allowed Hosts
File Scopes
The hook connects only to the PBS host you configure, and only reads disk usage.