Database / Relational / Controls / v2026.11
Prevent Data Loss During Failover
CCC.RDMS.CN12 · Data Resilience
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.
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 Threats
| ID | Title | Description |
|---|
| CCC.RDMS.TH12 | Failover Causes Data Loss or Divergent Writes | 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. |
Assessment Requirements
| ID | Text | Applicability |
|---|
| CCC.RDMS.CN12.AR01 | When a standby is configured for automatic failover, replication to that standby MUST be synchronous. | tlp-amber, tlp-red |
| CCC.RDMS.CN12.AR02 | When a standby is promoted, the former primary MUST stop accepting write transactions. | tlp-amber, tlp-red |