The snapshot button feels like a backup button. It is not — it is a bookmark stored in the same building as the fire risk. This page sets out the backup routine a virtual NAS honestly needs, layer by layer.
Ask what protects a virtual NAS and most people point at the snapshot they took last month. Then ask where that snapshot lives, and the honest answer ends the conversation: on the same host, on the same datastore, behind the same power supply as the NAS itself. Snapshots are wonderful tools with a specific job. Backup is a different job, and this page separates the two cleanly, then builds the routine that covers both.
👆 Four layers, four different jobs — only the copies that leave the host count as backup (panel recreated for illustration)
A VMware snapshot freezes a VM's state so you can roll back to that moment. It is the perfect tool for short, planned risks: the update you are about to install, the setting you are about to change. It was never designed as storage. The snapshot lives beside the VM, grows as the VM changes, and shares every fate the host has — disk failure, corruption, theft, fire, ransomware that reaches the datastore. Rolling back is a rescue from your own changes. It is no rescue at all from the host's bad day.
Backup means a copy that survives the whole host disappearing. For this lab that copy has two halves, and both matter: the data in your shared folders, and the configuration — users, shares and permissions — that would take a weekend to rebuild from memory. A backup of only the files leaves you restoring data into a NAS you first have to reconstruct. A backup of only the settings leaves you with a beautifully configured empty box.
QTS carries its own backup tool, HBS 3 (Hybrid Backup Sync), and it is the natural engine here. Point it at a target that is physically elsewhere: a USB drive you rotate and unplug, another NAS, or a cloud bucket for the folders that matter most. Schedule it, make it report failures loudly, and check the report — a scheduled job that has been failing silently for a month is worse than no job, because it spent your trust. Separately, export the QTS configuration backup after every meaningful change and store that file with your other recovery files, off the host.
An untested backup is a rumour. Once, before you rely on any of this, do the boring ceremony: pick a folder, delete a test file from the NAS, and restore it from the backup target. Time it. Write down the steps while they are fresh. That twenty minutes converts your backup from a belief into a procedure — and it is exactly the procedure you will follow on the worst day, when nobody has time to improvise.
However good the routine gets, one rule from the core guide does not bend: a virtualised QTS is never the only home of important data. It can hold a copy, a staging area, a test bed. The original — the accounts archive, the only scan of the property papers, the project history — belongs on supported storage with its own backup. The lab is a brilliant teacher. Do not promote it to the office vault because it behaved well for a month.
Watch the video for the install, then come back and set the backup routine before you copy a single real file across.
▶️ Watch Full VideoNo. A snapshot is stored with the VM on the same host and datastore, so anything that takes the host — disk failure, corruption, fire, theft — takes the snapshots with it. Snapshots are for rolling back your own changes over hours or days. A backup is a copy that lives somewhere the host's bad day cannot reach.
Something physically separate that you will actually maintain: a USB drive you plug in for the job and unplug after, a second NAS, or cloud storage for the most important folders. HBS 3 inside QTS can target all of these. The best target is the one whose failure reports you will genuinely read.
After every meaningful change — new users, new shares, permission changes — and before every firmware update. The file is tiny and takes two minutes to make. Store it off the NAS with your install files, so a rebuild starts from your real settings instead of from memory.