Upgrades

Check release support first

All products are In development. Upgrade commands, supported version combinations and migration requirements will accompany approved releases. A milestone tag is not public release approval. Do not upgrade from an unreviewed package merely because its version looks newer.

Before changing a server

1. Read the target release's notes and compatibility information for Alexandria, Stache Server and any mobile clients in use.
2. Confirm the documented upgrade path supports your current versions.
3. Make a complete backup and rehearse its restoration in a disposable environment.
4. Allow clients to synchronize and schedule maintenance with readers.
5. Record current configuration and package versions privately.

Follow the release's deployment order and migration instructions. Never assume a database migration can be undone by installing an older binary. Recovery may require restoring the pre-upgrade backup with the matching versions.

Verify the result

Check service startup, login and an authorization denial. Open a sample library record and attached file, record a small reading update, then confirm it persists after restarting. Check mobile connectivity for the clients actually in use.

If the upgrade fails, stop changing live data, preserve diagnostics and use the documented recovery procedure. Repeatedly rerunning an uncertain migration can worsen the problem. Keep the prior backup until the upgraded installation has been verified. See backup and recovery and troubleshooting.