Choose backup retention for virtual machines
Keep enough restore points to recover yesterday’s mistake and last quarter’s compliance question, then delete the rest on purpose.
Read guideField guides for backing up virtual machines, testing restores, and keeping copies that survive the production site.

Keep enough restore points to recover yesterday’s mistake and last quarter’s compliance question, then delete the rest on purpose.
Read guideA second copy in the same rack still shares power, cooling, and a fire. Send one copy to another site or a separate account.
Read guideA backup counts only after you boot a copy on storage and a network that cannot reach production.
Read guideAsk the guest to flush databases before the hypervisor copies disks, or the restored machine may boot with a torn write.
Read guideUse vzdump or the backup server so each Proxmox guest has a copy outside the disk that holds its virtual disk.
Read guideProtect Hyper-V guests with a job that uses the Hyper-V VSS writer, stores the copy off the CSV, and can import the virtual machine on another host.
Read guideNo. Each hypervisor has its own article, and the practice articles apply across VMware, Hyper-V, and Proxmox.
Yes. Search from the header only returns pages in the language you are reading.
The index lists six guides per page. A second page appears when more than six guides exist.