5
Delete old Proxmox VMs without regret (chartmann1590.github.io)
submitted 1 week ago by to c/proxmox@lemmy.world
2 comments fedilink hide all child comments
 

The backup, verify, then destroy-with-purge routine for clearing out stopped guests safely, including the linked-clone check that stops you deleting something a running VM depends on.

Free weekly email with the week's posts, videos and one tip: https://chartmann1590.github.io/homelab-the-right-way/newsletter/

Disclosure: this is my own article (Charles Hartmann, Homelab the Right Way). Written with AI help and edited by me; the setup described is mine.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 week ago (1 child)

Idk, that seems unnecessarily complicated versus just doing it via the UI, which already catches most of the things like orphaned disks etc. Integrity checking a freshly created backup isn't doing much in terms of safety. Protection against pruning is unnecessary when pruning keeps the last copies.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 1 week ago*

    Fair points. The UI does catch orphaned disks, and with sensible prune settings the newest copies stay anyway. The written routine mostly helps when you're clearing out a lot of old guests at once and want a checklist to follow.

  • permalink
  • fedilink
  • source
  • parent