Skip to content

IT services

Backup and recovery projects

Plan a backup and recovery project around the systems your organisation needs to use again. Subnet can help design, configure and implement a scoped backup change. Agree what will be covered, how the design will be checked and who will take responsibility when the project ends.

WORK WITH SUBNET

Veeam backup and recovery

Recovery priorities should guide the backup design. Subnet can scope Veeam backup and recovery work around the workloads, dependencies and operating responsibilities that matter to your organisation.

Recovery targets, immutability, off-site storage and testing are design choices to agree, not universal inclusions. Make the configuration, verification and ongoing ownership clear before delivery.

Start with what needs to recover

A system replacement, a move between environments or uncertainty about restore steps can prompt a review of your backup arrangements. Begin with the business activity you need to resume and the information, applications and settings it depends on.

Identify the services that need attention first, who uses them and who can confirm they are ready to use. This helps turn a broad request for better backup into a defined design brief.

  • What must be recovered: the selected data, applications and supporting configuration.
  • Recovery order: which services need to be available before others can resume.
  • Business requirements: acceptable interruption, tolerable loss of recent changes and the people who approve those objectives.
  • Starting point: existing backup tools, available recovery environments and any known gaps.

Choose the work your project needs

The engagement can be scoped around a design, a configuration change or an implementation. The proposal should identify the selected work, its deliverables and the decisions your team needs to make.

Design the approach

Define the systems and recovery scenarios in scope. Review the intended restore destination, access requirements, capacity and connections to other services. Agree the required backup settings and how long copies need to be kept before selecting the design.

Configure the agreed change

Specify the configuration and implementation work, including what can be retained from the current environment. Identify licences, storage, network access and third-party involvement. Any move from an existing setup needs an agreed transition plan and authority to make the changes.

Plan acceptance and handover

Decide whether recovery testing, operating instructions and knowledge transfer belong in the engagement. Name the person who accepts the result and the team that will own the environment afterwards. These outputs need to be included in the scope before delivery begins.

Decide what a recovery check must show

Where recovery testing is included, define the scenario, test environment and pass criteria before work starts. A file restore, an application restore and a wider recovery exercise ask different questions. Choose the checks that reflect the change being made.

Plan any agreed exercise around the data, applications and settings needed to resume the selected activity. Identify dependencies and the order of restoration. The business owner should decide what needs to work before the result can be accepted.

  • Inputs: the selected backup, recovery destination, access approvals and available supporting services.
  • Checks: the agreed data is present, the application can be used for the selected activity and any timing observations are recorded.
  • Review: compare the observed result with the agreed criteria, record exceptions and decide whether further work is needed.
  • Ownership: name who accepts the result, who resolves each exception and who keeps the recovery instructions current.
An example of a scoped recovery project

Illustrative example: an organisation is changing the backup configuration for a business application. Its application owner and IT team agree which data and settings matter, the recovery destination and the order in which supporting services would be needed.

The project team prepares the proposed configuration and change plan for approval. The agreed scope includes a recovery check in a separate test environment. Only the approved systems and data are used, with access and handling arrangements confirmed before testing.

The application owner checks whether the restored application supports the agreed business activity. The team records the result, observed timings and any exceptions against the acceptance criteria. The nominated owner then decides whether to accept the work or require further changes.

Handover includes the configuration record, the agreed recovery steps and a named operational owner. Continuing backup checks, future exercises and incident support are addressed in the ongoing service agreement.

Make the project boundary clear

Keep the project deliverables and continuing operational responsibilities visible in the proposal. That makes it easier to understand what the quoted work covers and what needs a separate decision.

  • Systems and data: the environments included, the recovery scenarios addressed and any exclusions.
  • Customer inputs: current documentation, authorised access, business priorities, application owners and people available to review the result.
  • Dependencies and costs: licences, storage, connectivity, recovery infrastructure and work by other providers. Identify separately charged or recurring items.
  • Change and acceptance: approved change windows, transition arrangements, any tests, the required records and the acceptance owner.
  • Handover outputs: agree whether configuration records, recovery instructions, knowledge transfer and post-project assistance are included.
  • Ongoing ownership: assign backup monitoring, failed-job investigation, restore requests, maintenance and future recovery exercises separately from the project.

Questions about backup and recovery projects

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.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What decision or change do you need to make?
  • What is known about the current environment?
  • What needs to be agreed about scope, dependencies and handover?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us