Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 3. Backing up the PostgreSQL database for Red Hat Edge Manager on Red Hat OpenShift Container Platform

This topic describes PostgreSQL backup strategy for Red Hat Edge Manager on Red Hat OpenShift Container Platform: recovery point objectives (RPOs), database backup scope, how to validate restores, and practices that complement database backups in a cluster deployment.

3.1. Overview
复制链接

Red Hat Edge Manager uses PostgreSQL to store mission-critical data, including device configurations, fleet management records, user profiles, and system state. To protect this data and ensure business continuity, implement backup strategies that support disaster recovery.

Define your Recovery Point Objective (RPO) based on your business requirements, compliance obligations, and risk tolerance. Typical baselines include the following:

  • Mission-critical environments: RPO on the order of 15 minutes
  • Non-production or development environments: RPO up to 24 hours
Important

You are responsible for implementing and managing your own backup strategies for the PostgreSQL database. Red Hat Edge Manager documents architectural guidance and best practices; it does not manage backups for your deployment.

3.2. Database backup scope
复制链接

To ensure a full system recovery, back up the flightctl database, including the following:

  • Data: Devices, fleets, organizations, templates, and related records
  • Schema and structure: The database architecture and table definitions that match your installed Red Hat Edge Manager release
  • Security metadata: Database users, roles, and access permissions required for the application

3.3. Testing backups
复制链接

Regularly test backup and restore procedures. Untested backups are a common source of failed recoveries.

  1. Create an isolated test environment that mirrors your production configuration closely enough to exercise a restore (same major Red Hat Edge Manager version and similar configuration).
  2. Restore from your most recent backup into the test environment using your chosen restore procedure.
  3. Verify data integrity by listing Flight Control resources (for example, devices and fleets) and comparing them to production records.
  4. Confirm that the Red Hat Edge Manager API and web console behave as expected against the restored database.
  5. Record any gaps, errors, and corrective actions in your runbooks.

3.4. Recommended practices
复制链接

  • Git-backed configuration: Store declarative configuration in Git. Use the Repository resource to reference configurations with gitRef in device and fleet specifications where appropriate. For a CLI-oriented workflow, see Managing the device configuration from a Git repository on the CLI.
  • Separate failure domain for Git: Host Git repositories on external services (for example, GitHub, GitLab, or Bitbucket) in a different failure domain than the cluster that runs Red Hat Edge Manager.
  • Back up deployment configuration: Regularly back up Helm values files and related configuration manifests so you can redeploy consistently.
  • Version and tag changes: Tag and version configuration changes so you can roll back or redeploy predictably.
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

Legal Notice

Theme

© 2026 Red Hat返回顶部