{
  "aliases": [],
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Returning traffic without the required data synchronization can expose stale or conflicting state.",
      "citationIds": [
        "azure-failover",
        "element-failback"
      ]
    }
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-18",
  "slug": "failback",
  "term": "Failback",
  "definition": "Failback returns a service or workload from a failover destination to its restored original resource or a designated replacement.",
  "note": "Direction: Failback is a return of service responsibility, not merely restarting the old host. It may be unnecessary when the new primary can remain in service. The return destination can be a different receiving server, rather than the same physical hardware. [azure-failover] [aws-failback]\n\nData boundary: A reverse-resynchronization workflow transfers changes from the active destination back to the original source, followed by a final update and session checks before traffic returns. These steps belong to the cited replicated-volume workflow; they are not permission to overwrite either copy without resolving its history. [element-failback]\n\nRejoining is different: PostgreSQL pg_rewind can prepare a former primary to follow the new one as a standby. Required WAL replay and recovery configuration still matter; adding that standby restores redundancy but does not itself return the primary role. [pg-rewind]",
  "related": [
    "failover",
    "io-fencing",
    "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-rewind",
      "title": "PostgreSQL 18: pg_rewind, Description and Failures While Rewinding",
      "url": "https://www.postgresql.org/docs/18/app-pgrewind.html",
      "accessed": "2026-11-18"
    },
    {
      "id": "element-failback",
      "title": "NetApp Element 12.7: Perform a failback when source volume still exists, reverse resynchronization and final update",
      "url": "https://docs.netapp.com/us-en/element-software-127/storage/task_snapmirror_perform_failback_when_source_volume_exists.html",
      "accessed": "2026-11-18"
    },
    {
      "id": "aws-failback",
      "title": "AWS Elastic Disaster Recovery: Failback to on-premises environment, original or different target server",
      "url": "https://docs.aws.amazon.com/drs/latest/userguide/failback-performing.html",
      "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"
    }
  ],
  "provenance": [
    "Source synthesis only: no production switchover, resynchronization, database recovery or failback timing experiment was performed.",
    "The reverse-resynchronization example is specific to NetApp Element 12.7; the different-server option is documented by AWS Elastic Disaster Recovery. [element-failback] [aws-failback]"
  ]
}
