MySQL

A MySQL schedule imports a SQL backup into the exact MySQL version you select, then runs your validation gates.

Available versions

Configure the restore

1. 1

   Select MySQL and a version

   Choose the exact version corresponding to the system that produced the backup.

2. 2

   Set the artifact format

   The dump format is SQL. Let RestoreTrust detect the container and compression, or enforce known values. You can use no container, tar, or ZIP and any compression offered in the console.

3. 3

   Configure decryption

   Select ZIP password metadata for a protected ZIP, or the matching age identity/passphrase metadata for age-encrypted input. Ensure the Kubernetes Secret exists in the worker's job namespace.

4. 4

   Set or infer the target database

   Enter an explicit target database when required. If left empty, RestoreTrust uses the first USE statement found in the dump; if none is present, it uses restoretrust_restore.

5. 5

   Add validation gates

   Require successful import and add read-only SQL probes for important data conditions. Compare each probe result as a boolean, integer, or string. Add duration gates for download, restore, or health probes when useful.

Prefer probes that detect incomplete or stale data, such as a minimum count for a critical entity or a known schema marker. Avoid queries that expose secret or personal values in results.

After saving, run the schedule manually and review the selected backup, restore log, probe results, and evidence.