# Backup and restore project brief

Use this blank worksheet to scope a planned recovery rehearsal with InstaDevOps.
It is a planning aid, not evidence that a restore has passed. Keep credentials,
backup files, customer records and confidential architecture out of the enquiry.

## 1. Workload and owner
- Application and business workflow:
- Workload owner and person accepting the result:
- Hosting provider, region and recovery location:
- Database engine/version, approximate size and other required storage:
- Application configuration, roles, keys and external dependencies:
- What changed recently, or why review recovery now?

## 2. Recovery objectives
- Failure scenario to rehearse:
- Maximum acceptable data loss (RPO):
- Maximum acceptable service interruption (RTO):
- Start and end points used to measure recovery:
- Required data location and handling constraints:
- Target date, permitted test window and budget constraints:

## 3. Existing backup path
- Backup method, cadence, retention and most recent successful job:
- Most recent actually tested restore and evidence available:
- Recovery-point timestamp to test:
- Required software versions, roles, permissions and encryption keys:
- Who can access/recover the backup if the primary system is unavailable?
- Unknowns (record unknown rather than assume):

## 4. Safe test plan
- Isolated target, capacity and permitted data handling:
- How test systems are prevented from contacting real users or production:
- Data checks and representative application workflow:
- Approver, stop conditions and escalation owner:
- Temporary resource, access and cost limits:
- Cleanup owner and evidence to retain:

## 5. Acceptance record, filled after the rehearsal
- Test date and environment:
- Recovery point restored:
- Restore start/end; application validation start/end:
- Observed data freshness versus RPO:
- Observed recovery duration versus RTO (state measurement boundaries):
- Passed checks, failed checks and evidence location:
- Remaining gaps, remediation owner and next test date:
- Runbook location and receiving operator:
- Access removed and temporary resources cleaned up:

A successful backup job or database startup alone is not proof that the
application can recover. Record failures without changing the acceptance criteria
after the test. An isolated rehearsal does not guarantee production recovery time.

Describe your workload and main gap in the project enquiry:
https://instadevops.com/enquire/?service=devops-project

Service scope: https://instadevops.com/services/backup-disaster-recovery/
Project price, access, milestones and support are agreed before work starts.