Complement your backup strategy for Red Hat Edge Manager on Red Hat Enterprise Linux by following recommended practices for archive management, configuration storage, and restore readiness.

• Full server backups: Run flightctl-backup on a schedule that meets your RPO and copy archives off the host. For more information about backing up the full server on Red Hat Enterprise Linux, see Additional resources.
• Git-backed configuration: Store declarative configuration in Git. Use Repository resources and gitRef in device and fleet specifications to sync configuration with the control plane. For more information about managing the device configuration from a Git repository on the CLI, see Additional resources.
• Separate failure domain for Git: Host Git repositories outside the Red Hat Edge Manager host failure domain (for example, a managed Git service or a separate cluster).
• Back up deployment configuration:flightctl-backup includes service configuration (for example, /etc/flightctl/service-config.yaml and drop-in files under /etc/flightctl/conf.d/) and PKI under /etc/flightctl/. Track configuration in Git or a configuration management tool so you can rebuild the host if needed.
• Version and tag changes: Track changes to configuration and automation with version control and tags so you can roll back or redeploy predictably.
• Restoring on Red Hat Enterprise Linux: When you need to recover the database on the host. For more information about restoring the PostgreSQL database for Red Hat Edge Manager on Red Hat Enterprise Linux, see Additional resources.