How is a backup project different from an ongoing backup service?
A project has a defined change and an agreed endpoint, such as a design or configuration implementation. An ongoing service needs its own coverage for monitoring, maintenance and restore requests. Confirm both responsibilities if the project will lead into a continuing service.
Can we keep our current backup tools?
Possibly. Review them against the systems in scope, the proposed recovery approach, support status and licensing. The project brief should identify what can be retained and where a change is needed, rather than assume every tool or environment is compatible.
Does the project include recovery testing?
Only where testing is included in the agreed scope. Define the restore scenario, test environment, data handling, business checks and acceptance owner. Ask which findings and instructions will be handed over, and who will address any exceptions.
How quickly will we be able to recover?
Set recovery objectives for each service during scoping, then consider the design, dependencies and checks needed to assess them. The result of a test describes the conditions tested. Recovery during a different incident may involve additional work or unavailable dependencies.
What will our team need to provide?
Bring the system list, current backup arrangements, known problems and the business priorities for recovery. Identify people who can approve access and changes, explain application dependencies and check the result. Agree any further information needed during scoping.
Who is responsible after the project ends?
Name the operational owner before handover. This may be your internal team or a separately agreed service provider. Confirm who checks backups, responds to failures, authorises restores and maintains the recovery instructions, along with any post-project assistance included in the proposal.
Does Microsoft 365 back up our data for us?
Microsoft’s shared responsibility model keeps responsibility for your information and data with you, even in a cloud service such as Microsoft 365. Built-in features such as retention policies, recycle bins and file versions help recover deleted or changed items, but only within set limits and settings. Scoping should decide which workloads matter (for example email, SharePoint, OneDrive and Teams), how long copies must be kept, whether built-in retention is enough or a separate backup is needed, and who handles restore requests.
Why keep a backup copy separate from our main environment?
A copy that shares accounts, networks or a location with production can be lost in the same incident. The Australian Signals Directorate’s Essential Eight guidance expects backups to be retained securely and protected from modification or deletion by users, with tighter limits on privileged and backup administrator accounts at higher maturity levels. Whether separation is achieved with an off-site, cloud or disconnected copy is a design decision. The scope should name who controls access, what each option costs and how quickly data can be brought back.
What is the difference between a restore test and a disaster recovery exercise?
A restore test checks that selected data or a single application can be recovered and used. A disaster recovery exercise is wider: it follows the agreed order of recovery for several data sets, applications and settings, and shows how the dependencies between them behave. The Australian Signals Directorate’s Essential Eight guidance describes recovery exercises that restore data, applications and settings to a common point in time. Decide which question you need answered, then record the scenario, environment and pass criteria in the scope.
What do RPO and RTO mean, and who sets them?
The recovery point objective (RPO) is how much recent change, measured in time, the business can afford to lose. The recovery time objective (RTO) is how long an activity can be interrupted before the impact becomes unacceptable. Each can differ by service, and tighter targets usually add design, storage and testing effort. Business owners should approve them, informed by how critical each service is. The technical design is then built to meet agreed targets, and testing shows whether it does.