Guides
Short recipes for a role and a task. Tutorials stay the “why”; these pages are the clicks in the Quemsi UI today.
How to use these guides
Pick the job you are doing, not a product tour. Each recipe names the role, the screen, and what is out of scope. Backup recipes create tagged snapshots; restore recipes use them. For the story behind known test states, see Testing with Known Database States.
Backup
There is no Backup sidebar. Open the data item on Data and click Take Snapshot on the timeline. Start here if Restore is empty.
Take a tagged snapshot
Quick Backup Wizard if Data is empty, then the data item’s Take Snapshot card with Execution Tags so Restore can find the version.
Open guide →Snapshot before a schema change
Tag a work=baseline snapshot before you migrate, so Restore can overwrite back if the change fails.
Schedule a recurring backup
Create a timer under Company Setup, attach it to the backup flow, and keep default execution tags on scheduled runs.
Open guide →Restore
Overwrite a target database from the latest snapshot for a tag combination.
Restore a tagged snapshot
Before a test run, filter Restore by tags, pick the latest matching snapshot, and overwrite a target database.
Open guide →Park work and switch database state
Snapshot and tag in-progress work, restore another tagged state for an urgent task, then switch back.
Open guide →Restore a snapshot across environments
Backup to company cloud storage, then restore onto a database on another agent.
Open guide →More resources
- Tutorials — why teams snapshot and restore
- Integration — company API tokens and
/api/v1for CI - Getting Started — first agent, storage, and backup
- Quick Backup and Restore in the console