Sync vs. Backup: Make a File Recovery Plan

Seeing a file on several devices does not by itself mean you have a safe backup. Sync keeps file states aligned across connected locations; backup is a system for keeping separate recovery copies that you can return to when something goes wrong. If you delete or overwrite a file in a synced folder, that change may spread to other locations too. For important data, use sync where it helps, and also keep past copies in an independent location for a defined period and confirm that you can restore them.

How are sync and backup different?

A sync service keeps devices or cloud folders showing the current files together. If you edit a document on your laptop, the change is sent to other devices; if you delete it from a folder, that deletion may be reflected there as well. The OneDrive deletion guidance also distinguishes the scope of deletion on devices and in the cloud. Sync therefore makes it convenient to access the latest state and collaborate. Seeing the same document on both your laptop and in the cloud does not mean there are two independent recovery copies.

A backup is a copy stored separately from the original and designed to recover data from a needed point in time after deletion, damage, or device failure. A plan includes when copies are made, how long earlier versions are kept, who can delete the copies, and which accounts or keys are needed to restore them. Some sync products may offer features such as a recycle bin, version history, or full restore, but these vary by product, account type, administrator settings, and retention period. Check the provider's documentation instead of inferring coverage from a feature name.

When does the difference matter?

For example, imagine a team editing project/proposal.docx together in a shared folder. If a colleague saves an older draft with a similar name over the latest document, the wrong content may sync to other devices too. Sync only passed along the change; it did not decide whether the change was correct. If an earlier version has been retained, you may be able to find and restore it, but check the version feature's retention period and conditions.

In another example, imagine accidentally deleting a file while tidying a work folder. It may be possible to bring it back from a sync service's recycle bin, but a recycle bin is not permanent storage. The recovery period may depend on the account, and an item permanently deleted from the bin may not be recoverable. Microsoft Support says the recovery period for deleted items can differ between personal OneDrive and work or school accounts, and an administrator may change the retention period. These are specific OneDrive conditions, not a guarantee for every cloud service. Restore deleted files from OneDrive

Build a recovery plan that fits your needs

First, write down: “Which files would be difficult to lose?” Include not only hard-to-recreate items such as photos and personal documents, but also the data needed to resume work. For a small business, candidates might include customer contacts, billing records, contracts, work documents, and service configuration data. Browser caches or installers you can download again may be lower priority. For team data, name an owner and a person authorized to approve recovery.

Next, set two recovery goals: “How much recent work could I afford to lose?” and “By when would I need the files usable again?” Choose backup frequency and retention to match. For example, if important files change daily but are copied only once a week, several days of changes may not be in the copy after an incident. This is an illustrative planning assumption, not a guarantee for a particular backup product.

Now separate at least three roles:

1. **Working copy:** The computer or shared folder where you normally edit. Sync helps with access and continuity across devices.

2. **Recovery history:** A backup or version-retention feature that keeps earlier versions for a period. Use it to undo recent mistakes or damage. Separately check how isolated the retained versions are from attackers or mistakes.

3. **Separate copy:** A copy kept somewhere else so the original device or account cannot be damaged along with it. If you use an external drive, safely disconnect it after backup and store it separately. If you choose cloud backup, do not assume it is safe merely because it is a different cloud account or backup service; check administrative access, deletion protection, and recovery history.

Practice restoring safely

You can learn enough from a restore test using temporary material without deleting real files. This small check confirms whether a backup is actually saved and can be restored to a new location.

1. Create a new temporary folder in your workspace, such as `restore-practice-date`. Do not copy real customer information or personal documents into it; create a non-sensitive text file such as “Practice document, version 1.”

2. Follow your backup tool's settings or instructions to confirm that this temporary folder is included in the backup. Creating it inside a synced folder does not mean it is included in a separate backup.

3. Check the backup completion status and last successful time. Make a small edit to the file, save it as “version 2,” and check whether the tool kept the earlier version. If you need to change settings, first read the product's official instructions and target only the temporary folder so other real data is not affected.

4. In the backup tool, find version 1 or the file from the test time and restore it to a **separate temporary restore folder, not its original location**. Do not delete or overwrite files in the source folder. If the tool only supports overwriting the original location, stop here and check the official documentation for a safe way to export to a separate location.

5. Open the restored file and check its contents and name. If useful, compare its size or a simple checksum. Record the date, storage location used, restore time, and any problems.

6. After practice, clean up the test files in the temporary restore folder. Check the policy to see whether the backup tool continues to retain the test copy; do not expand the cleanup to real data.

Expected results and what to do if it fails

If successful, you should be able to read the selected point-in-time content in the separate restore folder, while the current file in the working folder remains unchanged. If you restored version 1, you should see content different from version 2. This small test does not guarantee recovery of all data or a particular incident response time.

If the file is missing from the backup list, check the backed-up folders, exclusion rules, and account connection. If the last backup is old, check the schedule, storage space, and device connection, then try again with the temporary file. If no version is available to restore, the version-history retention period or backup policy may be insufficient. If you cannot access encrypted storage, check the safe storage of passwords or recovery keys and the access process for the responsible person. If these problems continue, contact the service provider or your organization's IT contact. If you suspect an actual ransomware infection, do not immediately restore from the infected device or a connected backup; first follow your organization's security or IT response procedure for isolation and safety checks.

Items to check regularly

• Are important files and backup targets reflected in the current list?

• Can you see the last successful backup time, frequency, and retention period?

• Do you know how sync propagates deletions and overwrites?

• What are the recovery periods for version history or recycle bins for each product and account?

• Is at least one copy stored somewhere or under access controls different from the original?

• Are external backups disconnected after use and stored safely against loss, fire, or theft?

• Can the authorized person access the account, password, and encryption key needed for recovery?

• Is there a record of restoring a non-sensitive temporary file to a separate location?

A backup plan is successful when you can find and read the file from the point in time you need, not merely when a “copy complete” indicator appears. Sync makes everyday access and collaboration convenient; separate backups and restore practice provide a return point after mistakes or failures. Document the scope and limits of both, then test them regularly so it is clearer what to do when recovery is needed.

References

• [NCSC: Backing up your data for small organisations](https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security/backing-up-your-data)

• [NCSC: Ransomware-resistant backups](https://www.ncsc.gov.uk/collection/ransomware-resistant-backups)

• [Microsoft: Backup, restore, and recovery in Windows](https://support.microsoft.com/en-us/windows/experience/backup-recovery/backup-restore-and-recovery-in-windows)

• [Microsoft: Restore deleted files from OneDrive](https://support.microsoft.com/en-us/onedrive/restore-your-onedrive-files.)

• [Apple: Restore items from a Time Machine backup](https://support.apple.com/en-au/guide/mac-help/mh11422/mac)