Practical guide

Backups, Sync and Version History: What Each Can Recover

“The files are in the cloud” does not tell you what can be recovered. Start with what might happen, how far back you would need to go and who could restore useful work.

Sync, version history and backup can all help in some situations. The useful question is which recovery route still works for the loss you are trying to cover.

Use the worksheet ↓

Different mechanisms, overlapping recovery

Synchronization keeps selected locations aligned as changes happen. Depending on the service, an edit or deletion can spread to the other copies. A synced copy may help if a device fails, while offering no earlier clean copy after a bad change.

Version history keeps earlier states of a file. Recycle bins and deletion recovery may retain removed items. Both can be useful, within the service’s limits and while the necessary account, permissions and retained content remain available.

An independent backup keeps recoverable copies with a separate recovery arrangement. Independence is a question to verify: could the same account loss, administrator action or incident affect both the working files and the backup?

Which route would you check first?

These are starting points for verification, not promises that a feature exists or a restore will succeed. Follow the current service documentation and your administrator’s arrangements.

A file is overwritten: Look for a retained earlier version or backup from before the edit. A synchronized current copy may already contain the same change.
A file is deleted: Check deletion recovery, its deadline and who can use it. Then check a retained backup if the item is outside that window.
Many files are corrupted: Ask whether a bulk rollback or backup contains a clean point, how affected files are identified and how restoration avoids spreading the problem.
An account is lost: Check account recovery and administrative authority, plus whether a separately accessible backup can restore the needed data. Data recovery and restoring the account are different tasks.
The provider is unavailable: Check whether copies, credentials and a recovery destination can be used without that service. Another copy at the same provider may share the outage.
An older version is needed: Check how far back versions or backups go for this file type. Confirm the required date is actually retained, rather than assuming “history” means indefinitely.
The administrator is unavailable: Check the authorized backup person, support escalation and access to the procedure. A retained copy is of limited use if nobody can obtain it.

Read the limits before you need recovery

Retention means how long a copy or version is kept. The usable recovery window may depend on settings, file type, subscription and whether someone has permanently deleted the retained content. Do not assume that every file has the same history.

Microsoft documents a whole-OneDrive restore feature for Microsoft 365 subscribers, with a limited recovery window. It also documents limits involving permanently deleted content. See the linked Microsoft source for the current conditions.
Google distinguishes Docs, Sheets and Slides history from versions of other files in Drive. Its documentation describes deletion limits and an option to retain selected versions. See the linked Google source for the current rules.

Technical detail: time and dependencies

Ask how much recent work could be lost between recoverable points, and how long restoring usable service would take. These are often called recovery point and recovery time objectives. Include software, configuration, encryption keys and connected records where the business process needs them; a file copy alone may not rebuild the application.

A successful backup is not a completed recovery

A completed backup job reports that a backup operation finished. Recovery also requires the right retained copy, authorized access, a workable destination and information that opens and supports the work.

Ask for evidence from an authorized recovery test: what was restored, from which point, where it was checked, what worked and what remained unresolved. CISA recommends protecting backups from the incident affecting the working environment and regularly testing their availability and integrity.

Review existing evidence with the responsible administrator first.
If a new test is needed, agree a safe isolated destination, permissions and a plan with the operator.
Do not delete files, disconnect accounts or restore over live data to try this checklist.

Make recovery possible when the usual person is away

Name who can authorize recovery, who performs it and an authorized backup person. They need a usable support route and secure access arrangements that do not depend solely on the account being recovered.

Keep the recovery procedure and contacts in an approved place that remains available during the incident. Store passwords, recovery codes and keys in secure systems, with appropriate access controls, rather than in an ordinary worksheet.

Resolve one uncertainty first

Choose a scenario below that would interrupt important work. Ask the operator to explain the route and show existing evidence. Record what is known, what is still unknown and who will check it next.

IT Mushroom recommends reviewing this arrangement after a provider, account, system or business requirement changes. A checklist organizes questions; it does not inspect your systems or certify that you can recover.

What happens if…? A recovery checklist

Copy or print this checklist for your provider or administrator. Choose one important process and ask about each scenario. Record answers privately in your own approved document; do not include credentials or sensitive configuration.

This is a blank working template. No answers are collected or attached to Contact. You can select the text or use your browser’s print command without JavaScript.

A file is accidentally overwritten

Which earlier copy could we use, and could we recover it without replacing other good work?
Route / evidence / next check: ____________________

A file is deleted

What recovery deadline applies? What happens after the recycle bin or deletion window is exhausted?
Route / deadline / next check: ____________________

Many files are corrupted

How would we identify a clean point and restore enough files to resume work? Who checks the result?
Clean point / operator / evidence: ____________________

An account is lost

Who can recover access? Can retained data be reached if this account remains unavailable?
Authority / separate access route / next check: ____________________

The provider or service is unavailable

Can we obtain and use copies elsewhere? What software, permissions or other dependencies would we still need?
Available copy / destination / dependencies: ____________________

We need an older version

Is the required date retained for this file type and plan? What evidence confirms it?
Required date / available point / evidence: ____________________

The administrator is away

Who is authorized to take over? Can they reach the procedure and support contact during an outage?
Backup person / procedure location / next check: ____________________

For each scenario, record: recovery route; oldest usable point or retention limit; who authorizes and performs it; where it can be restored; date and scope of existing test evidence; unanswered question and next owner. Use “unknown” where evidence is missing. Do not carry out an unplanned live restore.

Continue where it helps

For a conversation, use Contact in the company navigation or workspace controls. Sharing the public topic is optional; the worksheet is not attached.

Sources and review

The workflow recommendations and worksheets are IT Mushroom’s guidance. Product examples are supported by the sources below and should be checked against your current service and plan.

Microsoft: Restore your OneDrive
Product example: whole-OneDrive restoration, eligibility, recovery window and permanent-deletion limits. This is not independent backup coverage for every Microsoft 365 service.
Google Drive: Check activity and file versions
Product example: retained versions and the distinction between Google document history and other file versions.
CISA and MS-ISAC: StopRansomware Guide
Backup protection and recovery testing guidance. The checklist here requests evidence, not a destructive test.