Skip to content
Business Technology / 4 MIN READ

Business backup and Microsoft 365: plan and test recovery

Check Microsoft 365 backup coverage, recovery responsibilities and restore tests. A practical business checklist with Microsoft and CISA sources.

Start reading
CLOUDFUSION / INSIGHTS4 MIN READ

A useful business backup plan explains what you can restore, how much recent work you could lose, how long recovery may take and who will carry it out. A successful backup notification is one piece of evidence. The stronger check is a documented restore that someone has actually completed.

For Microsoft 365, websites and connected business systems, begin with the information the business needs to keep working. Then check the protection already configured, identify gaps and agree a recovery process. Cloudfusion can help review the technology scope through our business technology and support service.

List the data and its owner

Include mail, shared files, website content, databases and important records held in cloud applications. Note where each lives, who administers it and which other services depend on it. A website backup may not include records held by a payment or accounting provider.

Agree a recovery owner and a second person who can act if the owner is unavailable. Record how they obtain the required access safely. Keep credentials out of the planning document itself.

Microsoft 365 backup: what should you check?

Check the workloads and accounts that need protection, the policies actually enabled and the restore options available. Do not assume that buying a Microsoft 365 subscription automatically configures the backup arrangement your business needs.

Microsoft’s Microsoft 365 Backup overview describes protection for Exchange mailboxes, OneDrive accounts and SharePoint sites. Its backup FAQ explains recovery behaviour and limitations. Check the current coverage, retention, billing and restore process against your tenant and requirements before choosing or changing a service.

Distinguish file synchronisation, retention and backup. Synchronisation keeps locations aligned; retention governs how information is kept; backup provides a recovery route under the selected product and policy. They can complement each other. Establish which event each mechanism can recover from rather than treating the words as interchangeable.

Choosing a backup service? Read our Microsoft 365 backup buying guide to compare coverage, retention, restore responsibilities and current plans.

Agree how much interruption the business can tolerate

Two questions make the technical discussion clearer. How much recent work could you afford to recreate? How long could the business operate without the system? These are often called the recovery point objective and recovery time objective.

The answers vary by system. A marketing page and an order database may need different recovery arrangements. State objectives separately from achieved test results; a target does not prove the system can meet it.

Protect the recovery copy as well as the live system

Consider what would happen if an administrator account or live system were compromised. Check who can change backup policies or remove recovery copies, how those actions are protected and how they are reported.

CISA’s StopRansomware guide recommends offline, encrypted backups of critical data and regular checks of their availability and integrity in a recovery scenario. Apply an appropriate design to your systems with your provider; “in the cloud” alone does not describe the protection or prove recoverability.

Run a safe restore test

Choose a representative item or application and a recovery point. Restore into an agreed safe location where possible, avoiding accidental replacement of live work. Check the content, permissions and dependencies needed to use it.

Record the steps, the person who performed them, the restore point used, the time taken and anything missing. A database file that opens is useful evidence; a working application may also need configuration, files, licences and access to connected services.

Write a short recovery runbook

A runbook is a set of recovery instructions that another authorised person can follow. Keep it available through an agreed route that does not depend entirely on the failed system.

  1. Name the system, business owner and recovery contact.
  2. Describe the event that triggers recovery and who can authorise it.
  3. Identify the recovery source and how authorised access is obtained.
  4. Set out the restore steps and dependencies in order.
  5. Explain how to check the restored result before resuming normal work.
  6. Record how recent transactions or changes will be reconciled.
  7. Keep the date, outcome and limitations of the most recent test.

Check connected work after recovery

Restoring one system can put it at a different point in time from another. Decide how to reconcile records before restarting an integration. Replaying every event without checking existing work can create unintended duplicates.

Our public MTE Xpress case study describes a shipping-to-accounting connection with review, retry and catch-up tools. It is an example of delivered integration controls, rather than evidence of a client recovery incident or a disaster recovery guarantee.

Review the plan when the system changes

Revisit coverage when accounts, applications, hosting or responsibilities change. Agree a test schedule that fits the system’s importance and rate of change. Keep failed tests visible and assign the corrective work.

Bring your system list, existing backup arrangements and recovery objectives to a technology support discussion. For a custom application, include backup and recovery responsibilities in the development and handover scope.

All Insights
CLOUDFUSION / GET IN TOUCH
Rather talk first?+27 (0)81 044 5554Call
  1. 01 Choose
  2. 02 Details
  3. 03 Send
What would you like help with?

Describe it in your own words, or choose a service below.

What happens next?

Answer a few questions, then check your details before sending. We’ll review what you need and get in touch to discuss the scope, budget and next step. Sending an enquiry does not commit you to a project.

Already a client?Account help, faults, access or renewals.

Nothing is sent until you submit. How we use your details (opens in a new tab) · Privacy Notice (opens in a new tab) ·

ALREADY WITH CLOUDFUSION

Client
access.

Use the right workspace for what you need to do.

Client login Invoices, renewals, hosting, domains and account details.Get support Sign in to open a support ticket for a service Cloudfusion already manages. Your ticket stays with your account history.

Trouble signing in?

For an active project, use the workspace link supplied by your Cloudfusion contact.