What is being protected
Mavri keeps everything in a SQLite database inside the data folder of the machine or container where you installed it. Nobody else holds a copy: the maintainers do not host your data and cannot recover it for you. That makes your backup the only safety net.
Two things to back up, not one
1. The backup file. In Mavri, open Settings → Backup and download. You get one gzip file with your records. The API reference is explicit about its limits: accounts, API keys and store connections are not part of a backup.
2. The data folder. The database lives there, and so does the key that protects your store webhook secrets. If you want to rebuild an installation exactly, including store connections, copy the whole folder (or Docker volume) as well. The security notes in the repository say the same thing: the folder holds the database and the keys.
Where to keep the copies
- On a different disk or machine from the one running Mavri.
- Ideally also somewhere off-site. A backup in the same room as the server is lost with the server.
- Treat the backup file as sensitive: it contains your clients and invoices.
Test the restore
- Start a spare Mavri (for example a second container on another port).
- Create its owner account. This is needed because accounts are not stored in a backup.
- Use the restore control in Settings → Backup and choose your file.
- Open a few invoices and check the totals and the numbering.
- Re-create API keys and re-connect any stores, since those are not in the file.
If this works on a spare instance, you have a backup. If you have never done it, you have a hope.
A simple routine
- Download a backup file after any busy billing day.
- Copy the data folder on a schedule you will keep.
- Once a quarter, run the restore test above.
See the guide and API reference for the exact behaviour in your version.