Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

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

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

Legal Notice

Theme

© 2026 Red Hatトップに戻る