Backups and restore
If your app has a database or a disk, Kaviris backs it up for you. You don't set anything up.
What is backed up
- Postgres, continuously: every change is archived as it happens, and a full backup is taken every night. That means the database can be brought back to any moment in the kept period, not just to last night.
- Disks, nightly: a copy of the whole disk, encrypted before it leaves the machine. Kaviris takes it while your app is not running, so it never pauses your app. An app that stays awake all night gets no backup that night. See Disks.
- Backups are kept for 7 days, in storage separate from the database. A disk's last backup stays even if it is older.
- Your source: every upload that was deployed is kept, so Kaviris can rebuild the app.
Secret values are not part of backups you can download. Exports contain their names only.
Backups count toward your storage
Your backups count toward your organisation's storage, with your databases. The Usage page in the portal shows them as their own figure.
- Backups can take up to 7 days to shrink after you delete data, because they keep the older copies for 7 days.
- A deleted app's backups do not count. You can't free them, and we keep them for the 30 days we promise.
Restore tests
Restore tests are not yet run on every database. Every night Kaviris restores one test app's database and the platform's own databases into a separate, sealed place, checks that they start and hold data, records the result, and throws the copy away. A running app is not touched.
Your app's database is backed up, but it is probably not among those tested.
list_backups shows the last restore test of your app; empty means it has not
had one. Disks have no restore test yet.
Restore to a point in time
"Restore to yesterday 14:00": any moment in the last 7 days.
- Ask your agent (
restore_app), or use the app's page in the portal, and say the time. - Kaviris shows you what will happen. Nothing changes until you confirm.
- Kaviris creates a new database from the backup at that moment and switches your app to it. The old database is kept, in case you change your mind.
A restore changes your data, so an agent must show you the summary and get your OK first, like a rollback.
Restoring a disk
You and your agent can't restore a disk yet. For now it is a request that our staff handle: write to support with the app and the disk. A disk comes back as it was at its last backup, not at any moment you choose.
Download everything (export)
You can take your app with you at any time, free, also after you archive or delete it (until it is destroyed 30 days later).
- Your agent can export the source, the contract and the names of your
secrets (
export_app, orPOST /v1/apps/{app}/exports). - The database is exported by an owner or admin of your organisation, in the portal, with a confirm. An agent can't download your database: it holds your users' data, so a person decides.
You get a one-time download link, valid for 30 minutes, for one archive:
every source upload Kaviris still holds, a Postgres dump of each database
(pg_dump custom format, for pg_restore), the contract with every
approved version and who approved it, your secret names, and a README.
Secret values are never in it. A large database can take a few minutes; the
link answers "not ready yet" until it is.
When you delete an app
The app stops at once. Its data, backups and source are destroyed 30 days later. Until then support can still restore it. The app's name stays reserved for you: you can create a new app under the same name right away. The new app gets the address; the deleted one keeps its data and export until the 30 days are up, but no longer has the name.