# Backup Manager: Backups You Know Can Be Restored

> The Backup Manager is the server backup verification agent in the Ai1 platform by MyZone AI: it runs nightly and hourly backups of your Ai1 server, proves they can be restored with test restores in rotation and never shows a backup as healthy until one has passed.

Canonical page: https://myzone.ai/pages/agents/ai-backup-agent
Part of Ai1, by MyZone AI. Book a Backup Manager walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=Backup%20Manager&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-backup-agent-final
Last updated: 2026-10-05. Reviewed by the MyZone AI team.

Backups proven by test restores, never shown in green on trust.

## At a glance

- **Backups:** A full backup every night, smaller ones hourly and a running log of database changes
- **Proof:** Test restores in rotation, with the evidence kept
- **Integrity:** Backups checked as complete and unchanged, and verified independently
- **Backup Health page:** Each layer's real state, read-only and for admins only
- **When reports stop:** Shown as missing, never as the last good result
- **What it never does:** See or share your storage key

## What the Backup Manager does

- **Runs the backups:** A full backup every night, smaller backups every hour in between, and a continuous log of database changes so data can be brought back to a chosen moment.
- **Proves they restore:** Runs restore tests in rotation and keeps the evidence. A backup only counts as healthy once a recent restore has worked.
- **Checks integrity:** Confirms stored backups are complete and unchanged, and has them verified independently of where they are stored.
- **Shows it all on one page:** Backup monitoring in one place: a read-only Backup Health page shows each layer as fresh, stale, failed, missing, unverified or paused, with when it last ran and how much data could be lost.
- **Raises the alarm honestly:** If a backup stops reporting, the page shows it as missing rather than repeating the last good result, so a real outage never looks like a planned pause.
- **Routes fixes to the right owner:** Code changes go to the Developer, releases to the DevOps Agent and cloud storage to the System Administrator.

## How the Backup Manager differs from a backup that just runs

A backup job that runs every night tells you a file was written, not that your data can come back. The Backup Manager runs nightly and hourly backups with a continuous database log, proves them with test restores in rotation and has them verified independently. Its read-only Backup Health page never shows an untested or stale backup in green, and a backup that stops reporting shows as missing.

## How it works

1. **Back up** (Every night, and hourly in between): Nightly full backups, hourly backups and a continuous database log run on your Ai1 server.
2. **Test restore** (In rotation): Restore tests run in rotation to prove the backups can actually be used.
3. **Verify** (After backups are stored): Integrity checks and independent verification confirm nothing is missing or altered.
4. **Report** (Whenever an admin opens the page): The Backup Health page shows the real state of every layer to your admins.
5. **Fix** (Whenever a problem shows): Problems go to the agent that owns them: code, releases or cloud storage.

## When to use it

- **You want to know whether your data is really protected:** The status of each layer is shown, along with when a restore last worked.
- **You need last week's data back:** It checks the database change log and the latest successful restore test covering that data.
- **A customer or auditor asks about your backups:** You have the restore test evidence and integrity results to hand.
- **The Backup Health page shows a warning:** It explains what the warning means, finds the cause and starts the fix with the agent that owns it.

## What you get

- Nightly full backups with hourly backups in between
- A continuous database change log for point in time restore
- Rotating restore tests, with the evidence kept
- Integrity checks and independent verification results
- A read-only Backup Health page showing each layer's real state

## Example: Backup Health report

Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources.

What it was asked: Tell us whether our backups have really been tested, not just made, and give us evidence we can use in a client's supplier questionnaire.

A sample Backup Health report for a fictional practice in the agent's usual structure: the eight protection layers, test-restore history, an alert explanation and an evidence summary. All figures are invented; no real server, storage or client data was read. Extra storage that adds cost is approved by a person on the Ai1 team, fixes go through Developer and DevOps Agent, and the client decides what evidence to send. Run date: 1 October 2026.

### What it found

- Seven of eight protection layers are fresh, but the practice shows as unverified, not healthy, because the 30 Sep test restore did not finish and the last pass is eight days old.
- The three overwritten fee proposals can be brought back as they were at 17:00 on 23 Sep: the database change log has no gaps, and that morning's database test restore passed.
- On 27 Sep the status report stopped for 5 hours 25 minutes; the page showed 'missing' instead of old green results, while the backups underneath kept running.

### Sources

- [Offline backups in an online world | National Cyber Security Centre](https://www.ncsc.gov.uk/blog-post/offline-backups-in-an-online-world), National Cyber Security Centre (accessed 2026-10-01)

## Guardrails

- A backup that has not passed a recent test restore is shown as unverified, never as healthy.
- The Backup Health page is read-only and visible to admins only. Backups and restore tests run on the server, not from the page.
- It never sees or shares your storage key: the backup scripts read it securely when they run.
- Each rollout step must pass a real backup and a successful restore test before the next one begins.

## Frequently asked questions

### Why run a test restore if a backup finished without errors?

A finished backup only proves a file was written. A test restore proves your data can actually come back. The Backup Manager in Ai1 by MyZone AI runs test restores in rotation and keeps the evidence, and a backup without a recent pass is shown as unverified, not healthy. That is why a brand new backup is marked unverified: it is only trusted once a recent restore test has worked, so you are never given false comfort.

### What is a point in time restore?

Bringing data back as it was at a chosen moment, not only as it was at the last nightly backup. The Backup Manager keeps a continuous log of database changes alongside the nightly and hourly backups, and checks that log and the latest successful test restore before saying the data can come back. This is part of server backup verification: proving a backup can be brought back, not just that it was written. It also checks backups are complete and unchanged, and has them verified independently.

### What should good backup monitoring show a business owner?

The real state of every layer: fresh, stale, failed, missing, unverified or paused, with when each last ran and how much data could be lost. The Backup Manager's read-only Backup Health page shows exactly that, and a backup that stops reporting is shown as missing rather than green. The page is for admins only, and which admin level can see it is a configuration setting. You cannot trigger a restore from it: backups and restore tests are run by the Backup Manager on the server itself.

### When will the Backup Manager run on my server, and does it see our storage password?

As soon as your server is set up. It never shows a backup as healthy until a real restore test has passed. It never sees or shares your backup storage password. The backup scripts read the storage key securely when they run.

## More on this topic

- [Locking Down AI Agents: The 10-Point Security Checklist Every CTO Needs](https://myzone.ai/pages/blog/ai-agent-security): AI agents are powerful,and vulnerable. Learn the 10 critical security steps to lock down your AI agents before they become your biggest liability.

## About Ai1

Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The Backup Manager is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents.

Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.