Confirm access, tools, backups, and release compatibility before you restore Red Hat Edge Manager on a Red Hat Enterprise Linux host running systemd-managed Podman quadlets. Mandatory requirements apply to both the primary restore procedure and the database-only alternative.

• Host access: Root privileges or sudo on the host where the quadlets run. You must be able to stop and start systemd units, run systemctl daemon-reload, create unit drop-in files, and run Podman commands.
• Core tools:systemctl and podman installed and usable by your restore account.
• Flight Control CLI tools:flightctl and flightctl-restore available on the host (or on a jump host if your runbook runs commands remotely). Before you restore, confirm that flightctl-restore matches the Red Hat Edge Manager server version.
• Backup artifacts: A tested backup of the flightctl PostgreSQL database, in a form your team can replay (logical dump, physical backup, or other agreed method). Include matching configuration backups from /etc/flightctl/ when your recovery plan requires them.
• Compatible versions: The Red Hat Edge Manager / flightctl-services release on the host must be compatible with the backup data. Use the same major release as when the backup was created.

Optional tools for verification steps (install only what you use):

• jq: parse output from podman secret inspect when retrieving passwords.
• pg_isready: check PostgreSQL readiness on localhost after temporary port publishing.
• redis-cli (Red Hat Enterprise Linux 9) or valkey-cli (Red Hat Enterprise Linux 10): check KV store connectivity on localhost. Use the client that matches your host’s major Red Hat Enterprise Linux version.
• ss or netstat: confirm that ports 5432 and 6379 listen during the restore window.