Deploying Hybrid Manager across multiple data centers

You can configure your HM installation across multiple data centers (multi-DC topology) to meet your high availability requirements. This topology includes a primary HM and one or more data-only HMs (secondaries) across multiple Kubernetes clusters.

• Overview — Reviews multi-DC concepts, explores the available multi-DC topologies, and provides an architecture review of a multi-DC HM installation.

• Configuring a multi-DC deployment — Provides a step-by-step guide of how to configure your HM installation across multiple data centers, and then provision a Postgres cluster across locations.

• Multi-DC for high availability
  • Architecture and roles: Hub and Spoke
    • The primary (The Hub)
    • The secondaries (The Spokes)
    • Data plane & storage
  • Topologies
  • Resilience and failover
  • Network latency in Distributed High Availability (DHA) clusters
  • HM backups and DR for multi-DC environments
  • Current limitations
• Configuring a Hybrid Manager deployment across multiple data centers
  • Before you start
  • Prerequisites
    • Architecture prerequisites
    • Collect the required information
  • Object storage across locations
    • Key requirement
  • Parameter uniqueness
  • Configure the multi-DC topology
  • Reduced set of components (Spoke clusters only)
  • Hybrid Manager installation
    • Validate wiring
    • Create a Postgres database cluster across different data centers
    • Operational notes
  • Validation (end-to-end)
  • Manual failover
    • Manual failover procedure for databases from the primary location to a secondary location
  • Troubleshooting
  • Appendix B — Quick daily checks