Restore a Tagged Snapshot

Role: Tester · Screen: Data → Restore · Time: a few minutes after snapshots already exist

This page is the clicks. For why known states matter, read Testing with Known Database States.

Before you start

A backup flow has already created snapshots with the tags you will filter on (for example app=quemsi, or use-case=checkout). If Restore is empty, follow Take a tagged snapshot first. Tags are set when you Take Snapshot (on Execute Flow), not by editing the Data timeline.
The target is a writable MySQL, PostgreSQL, SQL Server, or Oracle datasource. The agent that owns it must be able to read the snapshot’s storage.
MongoDB restore is not available from Restore. Those cards show a warning and stay disabled.
Restore overwrites the target. Existing objects are dropped or cleared, then the snapshot is loaded.

Steps

1

Open Restore

In the console, open Data → Restore, or go to /app/restore.

2

Filter by the tags your tests need

Each row is a tag name and an optional value. Leave Value empty to match every value of that tag. Use + to add another row. All rows must match (AND).

Example: Tag app, Value quemsi. Add Tag use-case, Value checkout if that scenario is tagged separately.

3

Pick the snapshot

You get one card per data item for the selected tag combination: the latest matching version. Cards with newer versions are listed first.

Use the description and tags to tell similar cards apart. Long descriptions and system tags (date, time, flow, db, …) sit behind Show more. A Subset chip means the snapshot is not a full database.

4

Choose the target database

Click Restore. Pick a target from the list (title and database name, with URL and agent underneath). If the target agent is online, Browse on agent opens a live look at that database before you continue.

5

Confirm overwrite

Read the warning: the named database will be overwritten; existing objects are dropped or cleared. Confirm the JDBC URL is the database you intend to wipe. Click Restore and overwrite.

6

Wait on the execution page, then run tests

Quemsi opens the restore execution. When it succeeds, the target is in that tagged state. Run your suite. For the next run, restore again from the same Restore card.

If Restore is empty or a card is disabled

The snapshot must have every tag you selected. Take Snapshot again with those tags (see Take a tagged snapshot), then refresh Restore. You cannot retag a version from the Data timeline.
No writable database of the same type whose agent can see this snapshot’s storage → the card explains why Restore is disabled.
Need an older version with the same tags → open that version on the Data timeline and Restore from there. This page only lists the latest per data item and tag combination.

Not this page

Custom extra steps (Clear Redis, scripts) after restore — build or edit a restore flow under Flows.
Promote lookup tables without wiping the rest of the database — Migrate Config and Reference Data.
MongoDB restore — still out of scope here.
Also from the API: Restore before tests.