Backups

croit creates configuration backups of the management node that can be used to restore the croit app. These backups don't contain anything stored in your Ceph cluster, they are only backups of the croit app itself.

Where croit puts backups

Backup	When it runs	Where it lands	Encrypted
Cloud backup	Daily, before croit updates or on demand	Uploaded to croit or your own S3 bucket	Yes, optional for S3
Backup on MON disk	Daily	/var/lib/ceph/mon/.croit-backup.zip on every MON node	No
Backup on Docker host	Before croit updates	/root/.croit/backups on the Docker host	No
Manual download	On demand	Wherever you save it	No

A backup holds your cluster's secrets, so treat every unencrypted copy as sensitive.

Cloud backups

Cloud backups are configured under Croit → Backups. They are uploaded to croit, which requires a registered cluster and internet access to api.croit.io, and they are encrypted before they leave your cluster, so croit cannot decrypt them for you.

Store the encryption key, the croit installation ID and the Ceph cluster ID somewhere outside the cluster. Without them an encrypted backup cannot be restored.

Uploading to your own S3 bucket

Instead of uploading to croit, you can also point cloud backups at an S3 bucket you own. This feature can be used on offline or airgapped clusters. Encryption is optional.

Backup on MON disk

croit also stores an emergency copy on the ceph cluster itself, under /var/lib/ceph/mon/.croit-backup.zip on every node running a MON.

Backup on Docker host

Before every update, croit writes a backup to /root/.croit/backups/ on the Docker host (meaning outside of the croit docker container). See Updating croit for ways to configure this.

Downloading a backup yourself

You can also download an unencrypted backup under Croit → Backups → Download.

Restoring a backup

See Migrating or restoring croit container.