MariaDB

A MariaDB schedule imports a SQL backup into the exact MariaDB version you select and evaluates your success criteria.

Available versions

Configure the restore

1. 1

   Select MariaDB and a version

   Choose the exact version that produced, or is required to restore, the backup.

2. 2

   Set the artifact format

   MariaDB backups use SQL dump format. Choose automatic detection or enforce the expected container and compression. Containers can be none, tar, or ZIP.

3. 3

   Configure decryption

   Select a ZIP password secret for a protected ZIP container or the matching age secret metadata for age-encrypted input. Create the corresponding Kubernetes Secret in the selected worker's job namespace.

4. 4

   Set or infer the target database

   Enter an explicit target database if needed. If left empty, RestoreTrust uses the first USE statement in the SQL dump, or restoretrust_restore when no such statement is present.

5. 5

   Add validation gates

   Require import completion and add read-only SQL probes for critical restored-data conditions. Compare results as boolean, integer, or string values, and add duration gates when they express an operational requirement.

Good probes can detect missing tables, unexpectedly low record counts, or absent migration state without returning sensitive rows. Keep query output minimal because probe results become part of the check record.

Run the schedule manually after creation. Use Logs to diagnose import failures and Validation gates to improve weak success criteria.