RestoreTrust restores database backups in an isolated test environment and checks the data against your criteria. Separate checks are available for files. A worker in your Kubernetes cluster runs the tests and records the results.
From your organisation to the result, these seven steps show how to set up a backup test, run it, and follow up with your team.
Your organisation is where you manage the team and assign access rights. You can also review your plan, its included features, and billing. Before the first test, this makes it clear who is responsible for setup and who can review results.
A project keeps the setup for related backup tests in one place. Add its sources, workers, test schedules, and notifications. If you use the API, you can also create a key for that project.
The worker needs credentials to access your backup source. Store them as a Kubernetes Secret in your cluster and enter only the Secret's name in RestoreTrust. During a test, the worker uses the credentials in the cluster where the restore runs.
Choose the storage location from which the worker retrieves your backups. RestoreTrust supports S3-compatible object storage and servers using FTP, SFTP, or SMB. In the test schedule, you can then select a path and, if needed, a filename pattern for the backup.
In a test schedule, you connect a backup source to a worker and choose a database or a file check. Set your own test criteria and decide how often the test should run. You can also start the first run manually; available intervals depend on your plan.
Keep your team informed when a test finishes without having to check every result yourself. RestoreTrust can send an email or call an HTTPS webhook. Choose whether to receive a notification for every run or only when a test fails.
After a run, the Console shows which backup was tested and how the test progressed. You can review the download, restore, and your own checks separately. If a step fails, the record helps you find the problem and run the test again after a fix.
A RestoreTrust worker runs the tests in your Kubernetes cluster. Assign it to a project; it uses credentials stored in your cluster and restores database backups in a temporary test environment. The test runs where access to your backups is configured.
For each test, you can see which backup was used and how the download, restore, and checks turned out. Errors are tied to the affected step. Each completed test gets a SHA-256 hash; an additional timestamp proof is optional. Depending on your plan, you can also bring results together in a PDF report.
