Configuring QNAP snapshots for ransomware protection in Australia
Ransomware has reshaped the way Australian households and small businesses think about data. In 2024 alone, the Australian Signals Directorate logged a cybercrime report roughly every six minutes, and the Office of the Australian Information Commissioner received hundreds of notifications under the Notifiable Data Breaches scheme. High-profile incidents involving Medibank, Latitude Financial and several regional logistics firms have shown that even careful operators can lose access to critical files overnight. Many local IT managers now ask the same question: what stops an attacker from encrypting the very backups we rely on? On a QNAP NAS running QuTS hero or QTS, block-level snapshots form a fast, space-efficient answer. Learn more about Questquest.kz.
Snapshots are point-in-time copies of a volume, LUN or shared folder that take seconds to create and only grow when data changes. Because they live on the same storage pool by default, they are not a substitute for offsite copies, but they do give you a recovery point ransomware typically cannot reach when marked read-only. For Australian users juggling family photos in Perth and project files for a Surry Hills design studio, that quick rollback can mean the difference between a quiet Tuesday and a week of downtime.
How QNAP snapshots actually work
When you trigger a snapshot, QNAP records the metadata of every block currently allocated to the volume. New writes go to fresh blocks while the original ones remain pinned to that snapshot. Read the original data through the snapshot and you see the volume exactly as it was when the snapshot was taken. This copy-on-write behaviour is why dozens of snapshots can coexist on a moderately sized pool without filling the drives.
The platform distinguishes between several snapshot types. Manual snapshots are created on demand for upgrades or risky changes. Scheduled snapshots run hourly, daily or weekly through Snapshot Replica. Smart snapshots use change-rate heuristics so quiet periods generate fewer copies. Snapshots can also be replicated to a remote QNAP, an S3-compatible target, or an Rsync server for offsite safety.
| Method | Granularity | Storage cost | Recovery speed | Ransomware resistance |
|---|---|---|---|---|
| Full backup to USB | Entire volume | High, full copy each time | Slow, depends on USB bus | Strong if rotated offline |
| QNAP block-level snapshot | Volume, LUN or share | Low, only changed blocks | Seconds to minutes | Strong when read-only and replicated |
| QNAP versioned folder (HBS3) | Shared folder | Medium, deduplicated | Minutes | Moderate, depends on policy |
| Cloud sync (OneDrive, Google Drive) | File by file | Per gigabyte | Minutes to hours | Weak, synced files can be overwritten |
| Tape or LTO archive | Full volume | High but cheap per TB | Hours | Very strong when stored offline |
Pairing snapshots with replication gives you an immutable copy that survives a compromise of the primary NAS. Local admins in Adelaide and Brisbane often schedule short snapshots during business hours and longer ones overnight.
Planning a snapshot policy that fits your risk profile
A schedule that works for a four-camera home office in Geelong will not suit a 40-seat accountancy firm in Parramatta. Map the data you cannot afford to lose: accounting files, client records, design projects and family archives usually top the list. Decide how much data loss is acceptable, whether one hour, one day or one week, then set the snapshot interval from that figure.
For most Australian SMBs, a workable baseline is an hourly snapshot during work hours, one at day's end, and a weekly archive kept for three months. Creative agencies add a snapshot before each render job. Healthcare practices bound by the My Health Records Act should consider hourly snapshots for clinical data with twelve months retention.
Storage overhead matters. A busy volume can grow its snapshot footprint by 10 to 30 percent over the pool size, depending on churn. Plan for this in your RAID calculation and leave headroom on the volume rather than filling it to 95 percent, where QTS will start pruning snapshots automatically and erode your rollback window.
Enabling snapshots on a volume or LUN
Open Storage & Snapshots in QTS or QuTS hero, choose the volume you want to protect, and click Snapshot. Decide whether you want a smart, scheduled or manual cadence. For shared folders with small writes, schedule short intervals; for a surveillance volume, fewer longer snapshots make sense. Tick read-only so they cannot be deleted by an attacker who has pivoted through the admin account.
Allocate a snapshot reserve so the system keeps a minimum number of copies even under heavy churn. A reserve of 10 percent of the pool is a sensible starting point for a 4-bay unit such as the TS-464. For larger pools with mixed workloads, 15 to 20 percent gives more breathing room. Apply the schedule, then verify that snapshots appear in the list with the expected timestamp.
If you run virtual machines through Virtualization Station, take snapshots of the VM data LUN as well as the VM configuration folder. Restoring a single VM from a stale snapshot is much faster than rebuilding a whole lab from scratch, which many Brisbane-based managed service providers have learned the hard way after a Crypt