Know what you can recover.
Decide which applications and files your team needs first after an interruption. Use those priorities to shape cloud access, backup schedules and restore tests.
What’s covered
Cloud workspace care
Review how staff access shared files and email, how licences are assigned and who owns the settings for your cloud tenant.
Backup coverage
Map each important data source to a backup owner, frequency and retention period. Record exclusions so gaps are visible.
Recovery rehearsal
Restore a representative file or workload into a separate location. Record the elapsed time and have its owner confirm that it can be used.
Recovering a shared project folder
Pick a real workflow, identify the recovery point it needs and test opening restored files with the people who depend on them. Put the result in a short recovery runbook.
Frequently asked
Is file sync enough for recovery?
Sync propagates changes between locations. Recovery depends on the available versions, retention settings and your ability to restore the data, so these should be checked separately.
What does a restore test involve?
Choose a sample, restore it in isolation, check its contents with the business owner and record the steps and elapsed time.
Let’s scope your cloud & backup.
Start with the people, locations or systems you want to cover.