{
  "aliases": [],
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Promotion does not itself prevent the former primary from returning as an independent writer.",
      "citationIds": [
        "pg-failover"
      ]
    }
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-18",
  "slug": "failover",
  "term": "Failover",
  "definition": "Failover transfers a service or resource function to an alternate component or site when the previous one cannot or should not continue serving it.",
  "note": "Scope: Failover can be planned or unplanned, and manually or automatically initiated. The mechanism may transfer a primary role or redirect requests to a replacement instance. A changed route does not by itself exclude a previous writer. [azure-failover] [pg-failover]\n\nData boundary: With asynchronous PostgreSQL replication, promotion can omit committed transactions that never reached the selected standby. Restoring access and satisfying a recovery-point objective are separate checks; the failover label promises neither zero loss nor a fixed interruption time. [pg-replication]\n\nAfterward: Rebuilding a standby restores redundancy; returning the service to its original primary is a separate failback decision. Some deployments keep the new primary instead. [pg-failover] [azure-failover]\n\nResearch contrast: Remus delayed network output until backup checkpoint acknowledgement, but its 2008 prototype lacked execution fencing after loss of both replication paths. Output protection within a fail-stop model does not establish partition safety. [remus2008]",
  "related": [
    "failback",
    "io-fencing",
    "asynchronous-replication",
    "storage-availability",
    "recovery-point-objective",
    "recovery-time-objective"
  ],
  "citations": [
    {
      "id": "azure-failover",
      "title": "Microsoft Azure reliability: failover and failback, planned/unplanned failovers and failback",
      "url": "https://learn.microsoft.com/en-us/azure/reliability/concept-failover-failback",
      "accessed": "2026-11-18"
    },
    {
      "id": "pg-failover",
      "title": "PostgreSQL 18, section 26.3: Failover, former-primary exclusion and standby reconstruction",
      "url": "https://www.postgresql.org/docs/18/warm-standby-failover.html",
      "accessed": "2026-11-18"
    },
    {
      "id": "pg-replication",
      "title": "PostgreSQL 18, section 26.2.8: Synchronous Replication, asynchronous loss window",
      "url": "https://www.postgresql.org/docs/18/warm-standby.html#SYNCHRONOUS-REPLICATION",
      "accessed": "2026-11-18"
    },
    {
      "id": "hesela-fencing",
      "title": "Hesela: Storage fencing, failover and failback boundaries",
      "url": "https://hesela.com/analyses/storage-fencing-stale-writes/",
      "accessed": "2026-11-18"
    },
    {
      "id": "remus2008",
      "title": "Cully et al. Remus: High Availability via Asynchronous Virtual Machine Replication. NSDI 2008, sections 2.1, 2.4 and 2.6.",
      "url": "https://static.usenix.org/events/nsdi08/tech/full_papers/cully/cully_html/index.html",
      "accessed": "2026-11-18"
    }
  ],
  "provenance": [
    "Primary documentation reviewed on 2026-11-18; product-specific examples do not establish a universal failover procedure or measured recovery time."
  ]
}
