Take a Tagged Snapshot

Role: Anyone · Screen: Data → timeline → Take Snapshot · Time: a few minutes

The usual place to start a backup is the data item timeline, not the Flows list. Click the Take Snapshot card at the top of Version Timeline. That opens a flow picker, then the Execute page where you set tags. Restore’s default filter is use-case, so a run with only system tags (date, time, flow, db) will not show there until you take a snapshot with the tags you filter on.

Before you start

The agent that owns the datasource is ONLINE. Execute is blocked while the agent is offline.
You already have a data item on Data, or you will create the first one with Quick Backup Wizard (empty Data list).
Decide the tags testers and Restore will use, for example app=quemsi and use-case=checkout.

If Data has no snapshots yet

Open Data (/app/data). The empty card says No Data Snapshots Yet. Click Quick Backup Wizard (/app/quick-backup).

Welcome — click Start.
Agent install — pick an existing agent, or create one if none exist.
Datasource — connect the database to back up.
Local Drive & Storage — create a local drive and storage on that agent.
Create & run flow — click Create & execute. Wait until the status is SUCCESS.
Done — the data item and first version are on Data. Quick Backup does not set Execution Tags.

Open that data item and continue with the steps below so the version Restore cares about has your tags.

Steps

Open the data timeline

In the console, open Data (or /app/data). Click the data item card (title and name). You land on that item’s page: Version Timeline.

Take Snapshot

At the top of the timeline (marked now), click the Take Snapshot card (“Create a new snapshot by executing a flow”).

In the Take Snapshot dialog, pick the backup flow for this data (title, name, agent, status). The first flow is selected for you. Then click Take Snapshot.

If the dialog says No flows are available for this data, click Create New Flow in that dialog. Do not start from the Flows list for a normal snapshot.

Confirm the agent is ready

You land on Execute Flow. You should see Ready to Execute. If you see Agent Offline, start the agent first — Execute stays disabled. If the flow failed to initialize, fix it from agent errors, then save the flow again.

Set Execution Tags and a description

Under Execution Tags, each card is a tag name and value (placeholders: tag name / tag value). Use + for another pair. Default execution tags from the flow, if you saved any, are pre-filled here.

Example: name app, value quemsi. Add name use-case, value checkout.

Under Description, write a short note for the timeline (the field label is “You can describe the snapshot in free format for future reference”).

Execute Flow, then confirm on the timeline

Click Execute Flow. Wait until the execution succeeds. Return to the data item (Back, or open it again from Data). The new version should show your tags and description. System tags such as date and time are added automatically. You set tags on Execute, not by editing the version card later.

Optional: default tags on the flow

On the flow edit page (from Flows, or after you need timers/masking), Default execution tags pre-fill Execute and are applied when a timer runs the flow. Save the flow after you set them. Day-to-day snapshots still start from the timeline’s Take Snapshot card.

If Data has a version but Restore is empty

Restore filters by tag name (default use-case). Take Snapshot again with those tags, or change the Restore filter to a tag you actually set.
The snapshot must have every tag row you selected on Restore (AND).

Not this page

Editing or creating flows from the Flows list — that is for timers, masking, and custom steps. Day-to-day backups start on the data timeline.
Snapshot immediately before a migration, with a distinct park tag — Snapshot before a schema change.
Nightly or weekly runs — Schedule a recurring backup.
Writing to S3 or Azure instead of a local drive — Configure Cloud Storage.
Masking columns in the backup flow — Mask Columns.
Also from the API: Snapshot before deploy.

Create a tagged snapshot

Open the data item, click Take Snapshot, set Execution Tags, then confirm the new version on the timeline.

Open Data