Skip to main content

Restore (Rollback)

The process of reverting the agent to a previous local backup when the current version misbehaves or configuration drift must be undone.

When it happens​

  • CLI (from terminal): nimbus system agent-revert <backup-name>
  • UI (from overview page): coming soon.
  • Prerequisite: A backup must already exist on the device (see nimbus system agent-backup list).

Before you restore​

  • Run nimbus system agent-backup list to confirm the target backup name and timestamp, and read the Backup page for retention advice.

What is restored​

  • nimbusd daemon binary with the exact build from the backup
  • nimbus CLI binary that matches the daemon

Important behavior​

  • Full replacement (no merging or partial overwrites).
  • Restore requires a backup stored on the device; it cannot fetch remote or cloud copies.
  • Backup and restore must match architectures (ARM vs x86) because binaries are reinstalled directly from the snapshot.
  • After restore, the agent may temporarily appear offline while it reports to the backend with the restored identity.
  • If you need to reapply a newer version afterwards, follow the Upgrade instructions.
  • Understand how snapshots are captured and stored by reading the Backup guide.

Key Characteristics​

  • Backups are local only
  • Upgrade always creates a backup
  • Restore is all-or-nothing
  • Agent is the source of truth for backups