pve_node_storage_backend_delete
Remove a storage backend (LVM, LVM-thin, ZFS, or directory) from a Proxmox node. Requires confirmation to execute the irreversible destroy with optional cleanup of underlying disk data.
Instructions
MUTATION: destroy a storage backend on the node.
RISK_HIGH, NO UNDO — backend-specific blast: zfs: destroys the zpool and ALL data on it lvm/lvmthin: removes the VG — any storage built on it breaks directory: removes the directory mapping (data on disk may persist)
To create one instead use pve_node_storage_backend_create; to see what exists first use pve_node_storage_backend_list. Dry-run by default (returns a PLAN); confirm=True executes (DELETE, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the storage backend to destroy. | |
| node | No | PVE node name the backend lives on; defaults to the configured node if omitted. | |
| backend | Yes | Storage backend type to destroy: one of lvm, lvmthin, zfs, directory. | |
| cleanup | No | If True, also removes the underlying disk data/partitions during backend removal. | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the irreversible destroy. | |
| proximo_target | No | Which configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |