For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
      • AstroFully-managed data operations, powered by Apache Airflow.
      • Astro Private CloudRun Airflow-as-a-service in your environment.
      • Professional ServicesExpert Airflow services for your enterprise's success.
    • Tools
      • Cosmos
      • Orbiter
      • CLI
      • AI SDK
      • Agents
      • Blueprint
      • UpdatesThe State of Airflow 2026See the insights from over 5,800 data practitioners in the full report. Download Now ➔
  • Customers
  • Docs
    • Insights
      • Blog
      • Webinars
      • Resource Library
      • Events
    • Education
      • Academy
      • What is Airflow?
  • Pricing
Get Started Free
    • Overview
      • Astro Support
      • Astro Office Hours
      • Global environment variables
      • Custom role permissions
      • Allowlist Astro domains
      • Feature previews
      • Deprecations
      • Airflow feature support
      • Azure Native ISV retirement
      • Security
        • Shared responsibility model
        • Resilience
          • Overview
          • Prepare for disaster recovery
          • Set up disaster recovery
          • Trigger failover and failback
        • Data protection
        • GDPR compliance
        • HIPAA compliance
        • Secrets management
      • Glossary
    • Book Office Hours

Product

  • Platform Overview
  • Astro
  • Astro Observe
  • Astro Private Cloud
  • Security & Trust
  • Pricing

Tools & Services

  • Cosmos
  • Docs
  • Professional Services
  • Product Updates

Use Cases

  • AI Ops
  • Data Observability
  • ETL/ELT
  • ML Ops
  • Operational Analytics
  • All Use Cases

Industries

  • Financial Services
  • Gaming
  • Retail
  • Manufacturing
  • Healthcare
  • All Industries

Resources

  • Academy
  • eBooks & Guides
  • Blog
  • Webinars
  • Events
  • The Data Flowcast Podcast
  • All Resources

Airflow

  • What is Airflow
  • Airflow on Astro
  • Airflow 3.0
  • Airflow Upgrades
  • Airflow Use Cases
  • Airflow 2.x End of Life

Company

  • Our Story
  • Customers
  • Newsroom
  • Careers
  • Contact

Support

  • Knowledge Base
  • Status
  • Contact Support
GitHubYouTubeLinkedInx
  • Legal
  • Privacy
  • Terms of Service
  • Consent Preferences

  • Do Not Sell or Share My Personal information
  • Limit the Use Of My Sensitive Personal Information

Apache Airflow®, Airflow, and the Airflow logo are trademarks of the Apache Software Foundation. Copyright © Astronomer 2026. All rights reserved.

LogoLogo
On this page
  • Trigger failover
  • Trigger failback
  • Universal Metrics Export in DR pairs
ReferenceSecurityDisaster recovery

Trigger failover and failback

Edit this page
Built with

Trigger failover

Failover is also supported using the Astro API.

Running, scheduled, and event-triggered tasks may be impacted during the failover window. Tasks may fail and require a retry.

1

Open the DR tab

In the Astro UI, go to Organization Settings > Clusters, select your primary cluster, and open the Disaster Recovery tab. Confirm the Status indicator shows the primary region is active.

2

Initiate failover

On the Disaster Recovery tab, click Failover. Alternatively, open the cluster’s actions menu (⋯) at the top right of the page and select Failover to Secondary…. Follow the prompts to confirm.

The secondary cluster is promoted to active, and all Deployments and data become available in the secondary cluster.

3

Validate Deployments

After failover completes, check the health and status of your Deployments, especially mission-critical ones. Validate that your Dags and tasks are running as expected and retry any failures if necessary.

Trigger failback

After the primary region recovers, you can fail back to the original primary cluster.

Failback is also supported using the Astro API.

Running, scheduled, and event-triggered tasks may be impacted during the failback window. Tasks may fail and require a retry.

1

Open the DR tab

In the Astro UI, go to Organization Settings > Clusters, select your original primary cluster, and open the Disaster Recovery tab. Confirm the Status indicator shows the cluster has failed over to the secondary region.

2

Initiate failback

On the Disaster Recovery tab, click Failback. Alternatively, open the cluster’s actions menu (⋯) at the top right of the page and select Failback to Primary…. Follow the prompts to confirm.

Universal Metrics Export in DR pairs

If you have Universal Metrics Export (UME) configured, the same UME configuration applies to both the primary and secondary clusters. Metrics exported from each cluster include a cloud_region attribute so you can distinguish data from each cluster in your metrics system.

After failover, update your UME settings if needed to reflect the new active cluster.