When the standby is promoted while replication lags, transactions committed on the primary may be absent from the new primary, and a former primary that keeps accepting writes produces two divergent copies. This impacts the integrity and availability of the data and can defeat recovery.
Failover Causes Data Loss or Divergent Writes
CCC.RDMS.TH12
Related Capabilities
| ID | Title | Description |
|---|---|---|
| CCC.RDMS.CP16 | Failover | The service may be configured to maintain a standby database that is automatically promoted when the primary cannot be reached. |
| CCC.Core.CP08 | Data Replication | The service automatically replicates data across multiple deployments simultaneously with parity, or may be configured to do so. |
Related Controls
| ID | Title | Description |
|---|---|---|
| CCC.RDMS.CN12 | Prevent Data Loss During Failover | Ensure that automatic failover promotes a standby that holds every committed transaction and that the former primary stops accepting writes, so that failover does not lose or fork data. |