Backup substrate

SQL backups and restore

Manual backups, restore, interval automation, storage health, multi-server fanout, and inspectable backup manifests live in one isolated page.

Restore is destructive. This page blocks blind restores. Pick a backup, inspect its manifest, review databases/tables/checksum, then type the exact filename. Before MySQL is touched, the current live state is captured as a verified restore point and uploaded to storage. Rollback uses that restore point.

Live state

Polls the admin process and storage servers every few seconds.

Idle

Operation: —
Phase: —
Message: —
Last started: —
Last finished: —
Next automatic backup: —

Capabilities

The admin machine must have MySQL client binaries.

mysqldump: —
mysql restore client: —
Backup scope: —
Filesystem uploads/images: —
Restore guard: —
Rollback: —

Automation and storage servers

Each storage server can have fallback endpoints: local IP, alternate IP, then domain. Backup fanout uploads to every enabled storage server.

Storage health

A server is healthy if at least one endpoint answers with the shared token.

Server	Status	Endpoints

Available backups

Choose a row, then inspect it. Size shows compressed SQL; inspect shows the uncompressed SQL size and table inventory.

	File	Source	Compressed	Uncompressed	DBs / tables	Created	SHA256	Inspect

Backup inspector

This is the proof layer: checksum, gzip validity, compressed/uncompressed size, database/table inventory, and SQL sample header.

No backup inspected

Select a backup and press Inspect. Restore remains disabled until this panel has a valid manifest.

Filename: —
Source: —
SHA256: —
Gzip readable: —

Compressed: —
Uncompressed SQL: —
Compression ratio: —
Databases / tables: —

Database/table browser

Estimated rows come from INSERT tuples in the SQL dump.

Database	Table	Create table	INSERT statements	Estimated rows	SQL bytes

Show SQL sample header

Restore preflight contract

Restore is allowed only after inspection, exact filename confirmation, checksum carry-through, and automatic restore-point creation. That restore point is uploaded to storage before MySQL is touched.

Type the exact filename I understand this will overwrite MySQL database state from the selected SQL dump.

Restore points and rollback

Every restore first snapshots the current live MySQL state. These restore points are intentionally excluded from normal local retention pruning.

Created	Status	Restore target	Rollback source	Storage proof	Rollback contract

Event log

The last backup and restore events from this admin process.