Backup & disaster recovery

Begin with the work that must continue

Backup and disaster-recovery services remain available. The useful starting point is the business requirement: which systems and information matter, what an interruption would affect and what the organisation needs to recover.

A review considers the existing arrangement alongside those requirements. The resulting scope may involve changes to backup tasks, the recovery environment or the process people follow during an interruption.

Check the operating workflow

A recovery plan needs to account for people as well as equipment. Establish who starts the process, what access they need and how a recovery exercise will show whether the agreed work can be performed.

The anonymised financial-services case study describes an off-site backup redesign followed by a practical drill. Staff worked remotely through the recovery environment when the normal office was assumed unavailable. It is evidence of that project's outcome; the requirements for another organisation need their own assessment.

Agree the scope and evidence

Discuss the current systems, backup arrangements and continuity requirements before choosing an approach. Recovery objectives, testing, ongoing responsibilities and service terms are agreed for the engagement. Sensitive configuration details should be shared through an appropriate channel after the initial discussion.

Problems we can help with

• Backups exist, but the recovery workflow has not been clearly established.
• The current backup or recovery arrangement needs review as requirements or costs change.

How we can help

• Review of backup and disaster-recovery requirements.
• Planning of backup and recovery workflows.
• Practical recovery exercises within an agreed scope.

How we work

• Review the current arrangement and the business requirement.
• Agree the scope, access, responsibilities and service terms.
• Carry out the agreed work and check the result.