Backup and recovery

Know what needs protection

All products are In development. Supported backup commands, archive formats and restore tools will be documented per approved release. This guide provides preparation and recovery principles; it does not certify a particular backup procedure.

Stache personal data and attached files need protection. Alexandria's canonical data and provider provenance have a separate lifecycle. Inventory each service's data, files and private configuration. A database copy alone may not contain every attachment or setting needed to recover.

Make a recoverable backup

1. Follow the installed release's consistency procedure before copying data.
2. Record product versions, backup time and the data and file locations included.
3. Protect credentials and personal contents in the backup; restrict access and store a copy away from the live installation.
4. Restore a copy to a disposable environment with compatible versions.
5. Check that you can sign in, find a sample library record and open a sample attached file before trusting the backup.

Do not overwrite a live installation merely to test a backup. Mobile changes that have not synchronized may be absent from a server backup.

Recovery workflow

Preserve the failed installation and available diagnostics first. Restore using the version-compatible instructions, then verify records and attachments before reconnecting clients. Avoid reintroducing a failed migration or corrupt file blindly. Keep the original backup until recovery is confirmed. See upgrades and troubleshooting.