The snapshot button is one click and feels like safety. It is not - it is something more specific and more limited. This page separates the two tools Proxmox gives your Windows VM.
Every Windows VM eventually meets a bad update or a worse experiment. Proxmox offers two different protections for that day - snapshots and backups - and confusing them is one of the most expensive misunderstandings in virtualisation. Here is what each one really is, for the Windows VM you just installed.
A Proxmox snapshot freezes the VM's disk at a moment in time and lets the VM keep writing into a new layer on top. Tick Include RAM and it also saves the memory, so a rollback returns you to the very moment - programs open, everything as it was. That makes snapshots perfect short-term safety nets: take one before a big Windows update, a driver install or a software experiment, and roll back in minutes if the change goes wrong.
What a snapshot is not is a copy. It lives in the same storage pool as the VM itself. If that storage fails, or the VM is deleted with its snapshots, the safety net goes with the thing it was protecting. Snapshots also quietly consume space as the VM keeps changing, and a forgotten chain of them can fill a pool.
A backup - made with Proxmox's built-in vzdump, or better, to a Proxmox Backup Server - writes a separate, restorable image of the whole VM: disks, settings, EFI and TPM state included. It can live on a different disk, a NAS, or another machine entirely, and it survives the death of the original VM and its storage. The Backup Server adds deduplication and incremental backups, so nightly copies of a Windows VM stay surprisingly small.
Backup modes matter for a running Windows guest: Snapshot mode copies the VM while it works, with a brief freeze handled by the guest agent; Stop mode shuts the VM down for the cleanest possible copy at the cost of downtime. For most office VMs, snapshot mode with the agent installed is the honest sweet spot.
After installing Windows with the video, set up its snapshot and backup routine the same day - the video's channel covers the rest of the server build.
Watch Full VideoProtected against bad changes, yes - a rollback undoes an update or install gone wrong. Protected against disk failure, theft or deleting the VM itself, no: snapshots live in the same storage as the VM and die with it. You need scheduled vzdump or Proxmox Backup Server backups on separate storage for real protection.
With the QEMU guest agent installed, snapshot-mode backups ask Windows to flush and freeze its file systems for the copy, which produces a consistent image in the same sense as a clean crash recovery - in practice, restores of office VMs this way are routine. For a truly critical guest, stop-mode backups during a quiet window are the strictest option.
As few as possible - one fresh snapshot before a change, deleted once the change proves itself within days. Old snapshots consume growing space on the pool and tempt rollbacks that throw away weeks of newer work. Long-term history belongs in backups, not in a snapshot chain.