How to set up and manage versioned backups to protect against ransomware and accidental file overwrites
Summary
This guide helps you troubleshoot and resolve: How to set up and manage versioned backups to protect against ransomware and accidental file overwrites. Follow the steps below to fix the issue.
Common Causes
Versioned backups keep multiple historical copies of your files rather than overwriting them each time a change is saved. If a ransomware attack encrypts your data, a colleague accidentally overwrites an important spreadsheet, or a file becomes corrupted, you can roll back to a clean version from a specific date and time. This guide walks through enabling versioning in OneDrive, on a typical NAS device, and in third-party cloud storage, plus the day-to-day habits that keep your backups healthy.
Why Versioning Matters
Standard sync tools mirror your current files. If those files are damaged, the damage syncs everywhere. Versioning breaks that chain by preserving older copies on the server side, so even a fully compromised workstation still has clean originals waiting in the cloud or on your NAS.
Set Up Versioning in OneDrive for Business
OneDrive for Business retains file versions according to your Microsoft 365 licence and file type; there is no single default limit that applies to every file. Deleted files are generally kept in the recycle bin for 93 days. Version limits and retention behaviour differ between OneDrive for Business and personal OneDrive accounts, so check your specific Microsoft 365 subscription documentation for exact limits.
- Sign in to OneDrive on the web using your work or personal Microsoft account.
- Right-click the file or folder you want to manage and choose Version history.
- Review the list of saved versions. Each entry shows the date, time, and the person who made the change.
- Click the three dots next to a version and choose Restore to make it the current version, or Download to save a copy locally.
- Versioning is enabled by default in OneDrive. To confirm your sync settings, open the OneDrive desktop client, click the OneDrive icon in the system tray, select Settings > Sync and backup > Advanced settings, and verify your sync folders are configured correctly.
Set Up Versioning on a NAS
Most modern NAS devices from Synology, QNAP, and Asustor include snapshot or versioning features. The exact menu names vary, but the workflow is similar. For Australian businesses, consider data sovereignty when choosing where your NAS backups replicate, and ensure your NBN upload bandwidth can handle the snapshot traffic if you replicate offsite.
Synology Example
- Open Synology DSM in your browser and sign in as an administrator.
- Install and open Snapshot Replication from Package Center if it is not already installed.
- Go to Snapshot Replication > Shared Folder Snapshot and select the folder you want to protect.
- Click Settings > Schedule and choose how often snapshots are taken. For ransomware protection, a snapshot every 4 to 6 hours is a sensible starting point.
- Set a Retention policy. Retention is calculated independently for each frequency (for example, 24 hourly snapshots covers roughly one day, 7 daily snapshots covers one week, and 4 weekly snapshots covers one month). Adjust these numbers based on your recovery point objectives and available disk space.
- Enable Snapshot Lock if your NAS firmware supports it. This prevents ransomware running on a connected device from deleting snapshots, which is an important control for Australian small business threat models where ransomware often targets local backup targets.
QNAP and Asustor
Look for Snapshots in the storage manager, or install the Versioning app from the app centre. The principles are the same: schedule regular snapshots, set a retention policy, and lock them against deletion where possible.
Set Up Versioning in Third-Party Cloud Storage
Google Drive
- Open Google Drive in your browser.
- Right-click a file and choose File information (or click the 'i' icon), then select Version history or Manage versions.
- Click Upload new version to add a revised copy, or select an older version and choose Make current or Download.
- Google Workspace admins should consult current Google Workspace documentation for retention and eDiscovery options, as Vault retention rules apply to held data and are not a simple extension of Drive version history.
Dropbox
- Sign in to Dropbox on the web.
- Hover over a file, click the three dots, and choose Version history.
- Select a version and click Restore or Download.
- Dropbox Business admins can check Admin console > Settings > Version history for available Extended Version History options on eligible plans. Standard version history is typically 30 days; extended options vary by subscription.
Day-to-Day Management Habits
- Test restores quarterly. Pick a random file, restore an older version, and confirm it opens cleanly. A backup you have never tested is a backup you do not have. For ransomware readiness, consider testing more frequently if your recovery time objective is tight.
- Watch your quota. Versioning uses extra storage. Check your OneDrive, Google Drive, or Dropbox usage monthly and archive or delete old versions you no longer need.
- Document your retention policy. Write down how long versions are kept and where they live. Store a printed copy somewhere a ransomware infection cannot reach, such as a password manager or a physical folder.
- Restrict who can delete versions. On a NAS, only give administrator accounts the right to remove snapshots. In OneDrive and SharePoint, use the Microsoft 365 compliance centre to lock retention policies.
- Combine with ransomware protection. Versioning is most effective alongside endpoint protection, multi-factor authentication, and regular security patching. Pair your versioned backups with an offline or immutable copy that ransomware cannot reach.
- Consider NBN upload bandwidth. Cloud versioning uploads changed blocks continuously. If your business operates on a lower-tier NBN plan, schedule large initial backups outside business hours to minimise impact on daily operations.
Troubleshooting
Version history is missing or empty
- Confirm the file actually lives inside the synced folder. Files dragged into the local OneDrive folder before sync was enabled may not have history.
- Check whether your tenant administrator has applied a retention policy that has already purged older versions.
- For personal accounts, review your Microsoft 365 subscription details for version retention limits rather than assuming a fixed period.
OneDrive sync conflicts
- Look for files with names ending in "(computer name)'s conflicted copy" in the OneDrive folder.
- Open both versions, copy the changes you need into a single file, and save it.
- Pause OneDrive sync, resolve the conflict, then resume syncing to prevent duplicate versions from proliferating.
NAS snapshots are failing
- Verify there is enough free space on the volume. Snapshots need roughly 10 to 20 percent headroom to operate reliably.
- Check the Snapshot Replication log for I/O errors. Failing disks often show up here first.
- Confirm the schedule does not overlap with another intensive job such as a virus scan or full backup, which can cause both to time out.
- If snapshot authentication fails, verify the administrator account credentials and ensure two-factor authentication is not blocking the scheduled task.
Google Drive version history issues
- Ensure you are using a Google Workspace account if you need admin-controlled retention; personal Google Drive accounts have different version management limits.
- Check that the file owner has not restricted version history access.
- For large files, wait for the upload to complete before attempting to manage versions.
Dropbox version history issues
- Confirm your Dropbox plan includes version history; Basic accounts may have limited retention.
- Check whether the file has been moved to a shared folder where you do not have ownership rights.
- Verify you are viewing the correct file version in the web interface, as the desktop app may cache older metadata.
Restored file looks corrupted
- Try an earlier version. The most recent saved version may already be damaged.
- Download the version rather than restoring in place, then open it on a different device to rule out a local issue.
Versioned backups are a valuable layer of protection, but they work best when paired with a tested recovery plan and offsite or immutable storage. If you need help configuring versioning, reviewing your retention policy, or restoring files after an incident, our team can assist. Open a Ticket
Still Having Issues?
💻 Open a Ticket