Recovery Brief

Recovery rehearsal · practical guide

How to test a disaster recovery plan

Use one real workload to find gaps before an outage. A vendor demo does not replace a test with your own data and access rules.

Keep key access in the recovery plan

Veeam Software · Encryption keys are part of the restore path

Encrypted EC2/RDS operations need the appliance’s IAM role to reach the required AWS KMS keys.

Permissions depend on the operation and source/target keys; document applies to build 13.1.2.57.

Source

Start with one workload that matters to the business. Record each result; do not treat a planned target as a measured result.

01

Pick a real recovery case

Name the system, data owner, business impact and who can approve a restore. Include the source location and the recovery environment.

02

Write down the recovery targets

Recovery time objective (RTO) is the longest acceptable time to restore service. Recovery point objective (RPO) is the oldest acceptable data you can restore.

Set targets with the people who use the system. The vendor evidence here does not set your targets.

03

Test access and isolation

Use a separate recovery identity. Check who can delete backup copies, change retention, approve access and start a restore.

Ask the vendor to show the exact configuration for your workload and plan.

04

Restore, verify, and time each step

Record when the request starts, data becomes available, the application works, and users can complete a real task. Keep transfer time separate from application checks.

Do not compare your result with another buyer's data size or a vendor claim.

05

Repeat with a failure scenario

Try a lost credential, an unavailable region, or a clean restore after suspected malware. Record what the team had to do and what stayed unavailable.

06

Turn gaps into quote questions

Ask which plan and workload cover the gap, which storage and network costs apply, and what support is included during a real incident.

Take to your demo

Ask for the same proof from each finalist

Use the same workload, data size, recovery point, region, identity roles and success check. Ask for a written quote with storage, retention, support and restore costs named.

Review vendor-specific questions →