Kiption Cloud Start
Menu

How Backups Work and What We Have Not Tested

by The Kiption Cloud Operator

Every night, each archive on Kiption Cloud is backed up, and a copy is kept off the server it runs on. If a server dies, your stories are not on it alone. You set nothing up.

What Happens Each Night

A scheduled job runs each archive's backup command, which writes one zip holding the archive's data, logs, and cache databases. The job then copies the recent zips off the server. Zips kept on the server itself are deleted after 14 days.

What We Have Not Tested

We wrote the restore procedure, and we keep it in our operations notes. We have not yet run a full restore drill on a fresh machine from the off-server copies. Until we do, treat the restore path as written but unrehearsed. We will say so here the day that changes.

We also have not published how long the off-server copies are kept. We would rather leave the number out than state one we have not settled.

What a Restore Would Involve

In outline, from our notes: build a fresh server, fetch the newest backup zip for your archive, unzip it into the archive's folder, run the software's migrations, and check the archive loads. The records that route traffic to your archive are snapshotted separately, and restored from that snapshot.

Your Own Copy

You do not have to wait for us. Every story page offers downloads as EPUB, standalone HTML, and Word, and chapters are stored as markdown. Under the terms you can also export a complete copy of your archive at any time. The export docs say how to ask.

If You Cancel

The archive is suspended, and we keep your data for 30 days so you can export everything. After 30 days the data is deleted. Server logs are deleted after 30 days regardless.

Questions about backups go to help [at] kiption [dot] com.