Documentation Operations
OPERATIONS / SUMMARY

Backups & recovery

Protect existing data and know which recovery path to use.

Keep the existing backups

The infrastructure rollout preserves backup files, destinations, and schedules. The portal shows whether backups are recent and whether restore verification has evidence.

Choose the right recovery

For a broken portal release, roll back the application. For a configuration problem, restore the relevant saved configuration. For a failed disk or operating system, use the machine recovery process before GitHub can reconnect.

Keep this page available

The wiki is hosted independently so you can still read recovery instructions when the local server is offline.

Read the outcome and the timestamp

The portal shows image and database backups separately. A running timer does not mean its last backup succeeded. Check the last outcome, the age of the backup, and the age of the status report.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Expert →

Keep exploring

Documentation that follows code

How release checks keep all three reading versions aligned with implementation.

Add another application

Extend the portal without changing the production AI contract.