# 07. Backup, Update, Recovery

## 1. Minimum backup before changes

Before major changes, create:
1. configuration export (`Configuration Export`),
2. database export (`Database Export`),
3. backup of the instance data directory.

## 2. Update process (operational model)

Safe minimal flow:
1. stop service,
2. backup,
3. replace binaries,
4. start service,
5. verify endpoints.

Post-update checks:
1. `http://<host>:<web-port>/AircraftList.json`
2. `http://<host>:<admin-port>/admin`
3. hard refresh the radar page to load current static assets,
4. verify at least one desktop and one mobile UI smoke check.

Recommended UI smoke checks:
1. switch theme to `Futuristic` and `OverFuture` and verify map controls have no extra outer frame,
2. on mobile viewport, open aircraft detail sheet and verify expand/collapse gestures,
3. verify aircraft list sorting by `Reg` works and persists after page reload,
4. verify mobile bottom spacing is correct on devices with safe-area insets.

## 3. Recovery after failed deployment

1. Stop service.
2. Restore previous binaries.
3. Restore configuration and/or database from backup.
4. Start service.
5. Verify feeds and admin access.

## 4. What to log after deployment

Track:
1. release version,
2. date and host,
3. changed ports/binding settings,
4. endpoint verification results.