Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

proxmox-storage-backups

Estrelas0

Forks0

Atualizado29 de junho de 2026 às 20:30

Understand and manage Proxmox storage and backups via the REST API — list storage and content, understand storage types (dir/LVM/ZFS/NFS/CIFS/PBS), run vzdump backups, schedule backup jobs, and restore VMs/LXC from archives or Proxmox Backup Server. Load this for storage inspection, backup creation, or restore tasks on Proxmox.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Redth

Redth/homelab-assist

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	proxmox-storage-backups
description	Understand and manage Proxmox storage and backups via the REST API — list storage and content, understand storage types (dir/LVM/ZFS/NFS/CIFS/PBS), run vzdump backups, schedule backup jobs, and restore VMs/LXC from archives or Proxmox Backup Server. Load this for storage inspection, backup creation, or restore tasks on Proxmox.

Proxmox storage & backups

Manage via the REST API (see proxmox-api). Obey the homelab-core:homelab-safety skill — restore is destructive when it overwrites an existing guest.

Understand storage (read-only)

scripts/pve-api.sh GET /storage                                       # cluster-wide storage definitions
scripts/pve-api.sh GET /nodes/{node}/storage                          # status incl. used/avail per store
scripts/pve-api.sh GET /nodes/{node}/storage/{store}/content          # volumes, backups, ISOs, templates

Storage types and what they hold:

Type	Typical content	Notes
`dir`	anything (images, backups, ISO, vztmpl)	simple directory on a filesystem
`lvm` / `lvmthin`	VM/CT disks	block; thin supports snapshots
`zfspool`	VM/CT disks	snapshots, compression, send/recv
`nfs` / `cifs`	backups, ISO, images	network shares; check connectivity if "inactive"
`pbs`	backups (dedup, incremental)	Proxmox Backup Server — preferred for real backups

The content field on a storage def restricts what it can store (e.g. only backup, only images). A backup will fail if the target storage doesn't allow backup content.

Backups (vzdump)

# one-off backup of a guest (confirm first)
scripts/pve-api.sh POST /nodes/{node}/vzdump --data 'vmid=100&storage=pbs&mode=snapshot&compress=zstd'

mode: snapshot (live, preferred), suspend, or stop. snapshot needs snapshot-capable storage.
Backups run async → poll the returned UPID task for success (proxmox-api).
Scheduled jobs live under /cluster/backup (GET to list, POST to create — confirm first).

scripts/pve-api.sh GET /cluster/backup

Restore (DESTRUCTIVE when overwriting)

Restoring into an existing VMID overwrites that guest. Treat as destructive: confirm explicitly, call out that current data is replaced, and prefer restoring to a new VMID when validating a backup.

# restore a backup archive into a (new) VMID
scripts/pve-api.sh POST /nodes/{node}/qemu --data 'vmid=130&archive=pbs:backup/vm/100/<...>&storage=local-lvm'
# LXC restore uses the lxc create endpoint with ostemplate=<archive> + restore=1
scripts/pve-api.sh POST /nodes/{node}/lxc --data 'vmid=230&ostemplate=<archive>&restore=1&storage=local-lvm'

Archive identifiers come from the storage content listing (filter content=backup). Verify the exact parameter names/shape against the API viewer for the running version (homelab-research) — restore params are version-sensitive.

Before you act

Confirm free space on the target storage (GET /nodes/{node}/storage).
For restores: confirm whether you're overwriting; prefer a new VMID to validate first.
Summarize the plan (source archive, target, overwrite?, downtime) and get approval (homelab-safety).

Mais deste repositório

mesmo repositório

dockhand

Redth/homelab-assist

Manage Docker via Dockhand — the preferred control plane in this homelab — and its Hawser remote agents. Covers the Dockhand architecture (central server + Hawser Standard/Edge agents), how to drive it (the mcp-dockhand MCP server or its REST API), compose-stack and container operations, multi-host/environment targeting, and Git-synced stacks. Load this when the user manages Docker with Dockhand.

2026-07-010

docker-compose-stacks

Redth/homelab-assist

Shared foundational knowledge for working with Docker Compose stacks — the compose file format, services/networks/volumes/secrets, environment and .env handling, healthchecks, common operations (up/down/pull/logs/ps), and safe-change practices. Load this for any compose-based work, alongside the control-plane skill (Dockhand/Portainer/Dockge) that actually applies the changes.

2026-06-290

docker-on-proxmox

Redth/homelab-assist

Understand and troubleshoot a Docker host running inside Proxmox — as a VM or as a privileged/unprivileged LXC — and how VLAN networking, macvlan/ipvlan, VLAN-aware bridges, and passed-through/bind-mounted storage interact across the Proxmox and Docker layers. Load this when a Docker networking or storage problem may originate at the Proxmox layer, or when planning how to host Docker on Proxmox.

2026-06-290

docker-overview

Redth/homelab-assist

Entry point and router for managing Docker in a homelab. Load this first for any Docker request — it identifies which control plane is in use (Dockhand preferred, or Portainer/Dockge/raw Engine), establishes the version check, and routes to the right skill (compose stacks, Dockhand, reverse-proxy label routing, or Docker-on-Proxmox networking).

2026-06-290

dockge

Redth/homelab-assist

Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

2026-06-290

npm-reverse-proxy

Redth/homelab-assist

Set up and manage domain routing for homelab services using nginx-proxy-manager (NPM) driven by Docker container labels via npm-docker-sync. Load this when the user wants to expose a container/stack at a domain, debug why a service isn't routing, or understand the label-based proxy-host automation pattern. Covers the npm.* label scheme, how sync maps containers to NPM proxy hosts, and SSL/forced-host details.

2026-06-290

name	proxmox-storage-backups
description	Understand and manage Proxmox storage and backups via the REST API — list storage and content, understand storage types (dir/LVM/ZFS/NFS/CIFS/PBS), run vzdump backups, schedule backup jobs, and restore VMs/LXC from archives or Proxmox Backup Server. Load this for storage inspection, backup creation, or restore tasks on Proxmox.

Proxmox storage & backups

Manage via the REST API (see proxmox-api). Obey the homelab-core:homelab-safety skill — restore is destructive when it overwrites an existing guest.

Understand storage (read-only)

scripts/pve-api.sh GET /storage                                       # cluster-wide storage definitions
scripts/pve-api.sh GET /nodes/{node}/storage                          # status incl. used/avail per store
scripts/pve-api.sh GET /nodes/{node}/storage/{store}/content          # volumes, backups, ISOs, templates

Storage types and what they hold:

Type	Typical content	Notes
`dir`	anything (images, backups, ISO, vztmpl)	simple directory on a filesystem
`lvm` / `lvmthin`	VM/CT disks	block; thin supports snapshots
`zfspool`	VM/CT disks	snapshots, compression, send/recv
`nfs` / `cifs`	backups, ISO, images	network shares; check connectivity if "inactive"
`pbs`	backups (dedup, incremental)	Proxmox Backup Server — preferred for real backups

The content field on a storage def restricts what it can store (e.g. only backup, only images). A backup will fail if the target storage doesn't allow backup content.

Backups (vzdump)

# one-off backup of a guest (confirm first)
scripts/pve-api.sh POST /nodes/{node}/vzdump --data 'vmid=100&storage=pbs&mode=snapshot&compress=zstd'

mode: snapshot (live, preferred), suspend, or stop. snapshot needs snapshot-capable storage.
Backups run async → poll the returned UPID task for success (proxmox-api).
Scheduled jobs live under /cluster/backup (GET to list, POST to create — confirm first).

scripts/pve-api.sh GET /cluster/backup

Restore (DESTRUCTIVE when overwriting)

# restore a backup archive into a (new) VMID
scripts/pve-api.sh POST /nodes/{node}/qemu --data 'vmid=130&archive=pbs:backup/vm/100/<...>&storage=local-lvm'
# LXC restore uses the lxc create endpoint with ostemplate=<archive> + restore=1
scripts/pve-api.sh POST /nodes/{node}/lxc --data 'vmid=230&ostemplate=<archive>&restore=1&storage=local-lvm'

Before you act

Confirm free space on the target storage (GET /nodes/{node}/storage).
For restores: confirm whether you're overwriting; prefer a new VMID to validate first.
Summarize the plan (source archive, target, overwrite?, downtime) and get approval (homelab-safety).