Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for database administrators

Database Backup and Integrity Agent

A verified, restorable backup for every database within policy

Database Backup and Integrity Agent: what goes in, what the agent does and what you get

What it does

A database is only as safe as its last good, restorable backup, yet backups are often assumed to work until a restore is needed. Each day this agent confirms that scheduled backups ran, are the expected size and are kept per policy. On a schedule it restores a backup into a test environment and runs integrity checks to confirm the data is consistent and complete. If a backup is missing, too small or fails to restore, it retries per the runbook. If it still fails, it raises a high-priority ticket that states how long it has been since the last good backup. It drafts a weekly safety summary. You approve changes to backup schedules or storage. Edge case: a backup that completes but fails an integrity check counts as a failed backup.

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, continueYes, continueApprovedNoNo 1 STARTS WHEN Daily backup check 2 USES A TOOL Confirm backups ran, sizes and retention 3 CHECKS THE RESULT Are all backups present and in the normal sizerange? If not: retry per the runbook, then ticket if stillfailing. Back to step 2. 4 USES A TOOL Restore a backup into the test environment 5 USES A TOOL Run integrity and completeness checks 6 CHECKS THE RESULT Did the restore pass integrity checks? If not: raise a high-priority ticket with time sincelast good backup. Back to step 5. 7 YOU APPROVE DBA approves schedule or storage changes 8 RESULT Weekly backup safety summary
Read the steps as a list
  1. Daily backup check
  2. Confirm backups ran, sizes and retention
  3. Are all backups present and in the normal size range?If not: retry per the runbook, then ticket if still failing. Back to step 2.
  4. Restore a backup into the test environment
  5. Run integrity and completeness checks
  6. Did the restore pass integrity checks?If not: raise a high-priority ticket with time since last good backup. Back to step 5.
  7. DBA approves schedule or storage changesThe agent waits here for your OK.
  8. Weekly backup safety summary

How it decides

A backup counts as good only when it exists, is in the normal size range, restores cleanly and passes integrity checks.

  • Treat a failed integrity check as a failed backup
  • Escalate critical databases after one missed good backup
  • Keep retention exactly to policy

Make it yours

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

  • Size ranges per database
  • Test restore frequency
  • Critical databases list
  • Summary recipients

What keeps you in control

It always asks you first

  • Changing backup schedules or retention
  • Adding storage

Hard limits

  • Never deletes backups outside policy
  • Restores only to the test environment

It stops when

  • Done: every database has a verified backup
  • Stop: backup console unreachable

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 Wednesday, November 6, the nightly backup of the orders database at Glenwood Pharmacy completed at the usual 38 GB. The weekly test restore then failed an integrity check on the payments table. The agent treated it as failed and retried. The second backup failed the same check, so it raised a ticket noting the last clean backup was three days old. The DBA approved an emergency repair.

More agents for database administrators