Export and back up your data
This page tells you how to keep a copy of your data. Read it together with Recovery.
Export
Lasbolt has no vault export yet. There is no button in the web app and no
lasbolt export command. An export setting for administrators (allowed, owner only, off) is planned. It is not built.What you can do today:
- Read single values with the CLI.
lasbolt ls,lasbolt showandlasbolt readall take--json, so a script can walk through the vault.showhides secret values.readprints one value, and a scope can forbid it. - Keep a local copy. The CLI and the apps keep an encrypted copy of your vault on the device. It is not an export format. Do not copy it by hand.
- Peer sync. Your own devices can hold full copies of your data. See Peer sync.
If you plan to leave Lasbolt, script the export with the CLI before you need it, and test it.
What to keep safe
| Keep | Why |
|---|---|
| Your master password | The only normal way into your account. |
| Your recovery kit | The only way back to your E2E data if you forget the password. Keep it offline. |
| The server backups (the operator) | They bring back the server after a disk failure. |
| A copy of the backup identity key (the operator) | Needed to open sealed backups. |
Server backups
The server makes backups on a schedule. The operator manages them. A backup holds all your data in the same encrypted form as the live database. E2E data stays encrypted with your keys. A restore can look like a rollback to your clients. They then refuse writes to E2E folders until you accept the new state.
The operator guide has the steps: Backups and restore.
An old backup can hold the server-readable copy of an item that you later moved into an E2E folder. The old copy stays until the backup expires.
Last updated on