Complete AI Training

AI agent for director of its

Disaster Recovery Test Evidence Agent

Measured, documented recovery times for every critical system, with gaps turned into tasks

Disaster Recovery Test Evidence Agent: what goes in, what the agent does and what you get

What it does

A disaster recovery plan only matters if restores actually work within the promised time, yet tests are often skipped or not written down. This agent runs the scheduled restore test for each critical system in a sandbox, times each step and compares the result with the recovery time and data loss targets in the plan. After the restore it also tests a real login and a sample transaction, because a restored database is not the same as a working service. If a step fails or runs too long, it records the failing step, retries once with the documented fix and opens a remediation task if it still fails. It then updates the plan with measured times and drafts a summary for management. You approve any plan changes and the summary. Edge case: a database restores fine but the application cannot connect because a secret was rotated.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Quarterly DR test date arrives 2 DOES Pick systems due for testing from the plan 3 USES A TOOL Restore the latest backup into the sandbox and timeeach step 4 USES A TOOL Run a test login and a data freshness query 5 CHECKS THE RESULT Did the system restore within target and pass thelogin test? If not: record the failing step, apply the documentedfix and retry once, then open a remediation task. Backto step 3. 6 DOES Update the plan with measured times and gaps 7 YOU APPROVE IT manager approves plan changes and summary 8 RESULT DR evidence pack filed for audit
Read the steps as a list
  1. Quarterly DR test date arrives
  2. Pick systems due for testing from the plan
  3. Restore the latest backup into the sandbox and time each step
  4. Run a test login and a data freshness query
  5. Did the system restore within target and pass the login test?If not: record the failing step, apply the documented fix and retry once, then open a remediation task. Back to step 3.
  6. Update the plan with measured times and gaps
  7. IT manager approves plan changes and summaryThe agent waits here for your OK.
  8. DR evidence pack filed for audit

How it decides

A system passes only when it restores within its recovery time target, data is no older than its data loss target, and a test login works.

  • Pass only when restore time and data age are within target and login works
  • Retry a failed restore once before raising a task
  • Mark a system as untested if the sandbox lacks capacity, never as passed

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Systems in scope and their test frequency
  • Recovery time and data loss targets per system
  • Sandbox to use
  • Who gets the summary

What keeps you in control

It always asks you first

  • Changes to the official DR plan
  • Sending the summary to management or auditors

Hard limits

  • Restores only into the sandbox, never production
  • Does not delete backups

It stops when

  • Done: all due systems tested and recorded
  • Stop: sandbox unavailable or backup catalog cannot be read

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensOn October 12, the payroll database at Crestview Health had a 4-hour recovery target. The restore finished in 2 hours 10 minutes, but the login test failed. The agent found the service account password had been rotated, applied the runbook fix and retried. The retry passed at 2 hours 25 minutes. It added the password step to the runbook draft, and the IT director approved the updated plan.

More agents for director of its