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 up to 500 versions of every file by default and keeps deleted files in the recycle bin for 93 days. Personal OneDrive retains versions for 30 days on free plans, or longer with a Microsoft 365 subscription.

1. Sign in to OneDrive on the web using your work or personal Microsoft account.
2. Right-click the file or folder you want to manage and choose Version history.
3. Review the list of saved versions. Each entry shows the date, time, and the person who made the change.
4. Click the three dots next to a version and choose Restore to make it the current version, or Download to save a copy locally.
5. 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.

Synology Example

1. Open Synology DSM in your browser and sign in as an administrator.
2. Install and open Snapshot Replication from the Package Center if it is not already installed.
3. Go to Snapshot > Shared Folder and select the folder you want to protect.
4. 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.
5. Set a Retention policy. Keeping 24 hourly, 7 daily, and 4 weekly snapshots gives you a month of recoverable history without filling the volume.
6. Enable Snapshot Lock if your NAS firmware supports it. This prevents ransomware running on a connected device from deleting snapshots.

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

1. Open Google Drive in your browser.
2. Right-click a file and choose File information (or click the 'i' icon), then select Version history or Manage versions.
3. Click Upload new version to add a revised copy, or select an older version and choose Make current or Download.
4. Google Workspace admins can extend Drive's native retention by going to Admin console > Apps > Google Workspace > Drive and Docs > Data management and configuring a Vault retention rule.

Dropbox

1. Sign in to Dropbox on the web.
2. Hover over a file, click the three dots, and choose Version history.
3. Select a version and click Restore or Download.
4. Dropbox Business admins can enable Extended Version History under Admin console > Settings > Version history to keep deleted files and edits for up to 10 years on eligible plans.

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.
• 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.

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, free OneDrive plans only retain versions for 30 days. Upgrade to a Microsoft 365 subscription for extended version history.

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.

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.
• If the corruption is consistent across versions, the source data itself may be the problem. Restore from your offsite backup instead.

Still Having Issues?