Skip to content
EyesOnItDocumentation6.1

Back up and recover a server

HOW-TO GUIDELinux CLI and web UI · EyesOnIt 6.1

Keep a recoverable copy of the server and verify it before you need it. A complete recovery plan covers the installation, private configuration, application data, and every recording volume.

Watch the walkthrough

Section titled “Watch the walkthrough”
Server recovery walkthrough: stop the application, export and restore a disposable WSL server, then verify the restored camera in the web UI.

Download video · Read video captions

Plan the recovery copy

Section titled “Plan the recovery copy”

Choose your server or virtualization platform’s backup method and an approved private destination. Record the installed EyesOnIt version and the time of the backup. Include these items in the same recovery plan:

Include Purpose
System disk and installed application The matching application, services, runtime, and deployment state.
Private configuration and credentials License access, HTTPS, accounts, and integration credentials.
Application data Cameras, rules, identities, incidents, indexes, and retained metadata.
Every recording volume Continuous recordings and saved incident media.

Store the recovery copy with access limited to the people responsible for recovery. Use encryption for storage and transfer. For a cluster, coordinate PostgreSQL recovery and versioned object storage with the node backups.

Capture a consistent backup

Section titled “Capture a consistent backup”

On the server, check its version and readiness:

Terminal window
sudo eoi status
Linux terminal showing EyesOnIt installed version and ready services before a recovery backup.
Linux CLI: record the installed version and current readiness. Enlarge image

During the planned maintenance window, stop EyesOnIt:

Terminal window
sudo eoi stop

Take a complete backup or coordinated snapshot of the server’s disks and recording volumes. Keep the application stopped until the snapshot is complete. Record the backup identifier and checksum or the backup platform’s integrity result.

Linux terminal showing the EyesOnIt stop command before a consistent server backup.
Linux CLI: stop the application before capturing the recovery copy. Enlarge image

Start the original server when the backup is complete, then check readiness:

Terminal window
sudo eoi start
sudo eoi status

Rehearse recovery

Section titled “Rehearse recovery”
  1. Restore the backup to an isolated recovery server with the required NVIDIA hardware and runtime. Keep the original and recovery copies from processing the same cameras at the same time.
  2. Restore every required data volume and its mount point.
  3. Start EyesOnIt and check eoi status.
  4. Open the restored HTTPS address and sign in.
  5. Verify the cameras, configuration, permissions, and identities you expect. Play a known retained recording and run a representative archive search.
  6. Record the result and the time needed to recover.
Restored EyesOnIt web UI showing the recovered Campus east entrance camera and its detection configuration.
Web UI: verify a known camera and its saved configuration after restoring the server. Enlarge image

The walkthrough uses a disposable WSL server and WSL export/import for the system backup. Use the corresponding disk-backup and restore workflow for your production platform. Keep the verified recovery copy and its version information according to your backup policy.

For an application update, the managed installer also maintains its transactional recovery state. See Upgrades and rollback.

Image preview