> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/redundancy-management-framework/whitepapers/re-evaluating-high-availability-options-for-modern-cybersecurity-threats/application-services-and-sql-high-availability/active-passive/a-la-carte-sql-ha-always-on-availability-groups.md).

# À La Carte SQL HA - Always On Availability Groups

Active-Passive HA for SQL

## Executive Summary

Microsoft's SQL Server Always On Availability Groups \[1] provide high availability by replicating databases across multiple replicas, with automatic failover supported in Enterprise Edition. This active-passive approach ensures continuity during database or service failures, but relies on byte-for-byte replication. While this preserves database state across nodes, it cannot distinguish between valid changes and malicious ones, so corruption or ransomware on the primary is immediately propagated to all replicas. Efficiency remains one-to-one, as each primary requires at least one paired secondary.

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2F0kxH7lg4yiekduTRpkku%2FProduct%20and%20Marketing%20Graphics%20(77).png?alt=media&amp;token=fa20862d-7750-4feb-9716-5ccb7187b299" alt="" width="375"><figcaption><p>Always-On Availablity Group Concept</p></figcaption></figure>

## **Failover**

Always On relies on a Windows Server Failover Cluster, providing resilience against database disk and SQL service failures. Failover is natively handled within the solution.

## **Consistency**

The solution provides rapid SQL database synchronization in a manner transparent to end users.&#x20;

## **Cybersecurity**

<figure><img src="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2F3fNijYjyad8hpAqwJftV%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(9).png?alt=media&amp;token=cc4c5e4d-c4e7-489f-bc0e-91f9b00e95da" alt="" width="242"><figcaption><p>Always On spreads Malware</p></figcaption></figure>

Always On cannot distinguish between legitimate changes and malicious modifications. For example, if a stealthy procedure is injected into the primary replica, it is automatically propagated to all secondary replicas. As AI-driven malware becomes more sophisticated, this byte-for-byte replication model provides no inherent protection against malicious activity. See [Selective Object Synchronization](https://docs.vega365.com/redundancy-management-framework/whitepapers/cybersecure-redundancy-with-vega-systems-solutions/selective-object-synchronization.md) for a non-exhaustive enumeration of intelligent cyber threats that this solution will treat as benign.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Ransomware-Locked Data Pages</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2Fw9TVCoFlRSdkSUhXOqpV%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(4).png?alt=media&amp;token=ddeb0d4e-a025-4526-b551-96ddb8944ccb">RMF_Cyber_Secure_Redundancy_WhitePaper (4).png</a></td></tr><tr><td>Rogue Admin Account Creation</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FRk4s0viEiFGLD7yP2Fui%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(7).png?alt=media&amp;token=d761b8ed-321b-4a6f-b44c-98e526f689f6">RMF_Cyber_Secure_Redundancy_WhitePaper (7).png</a></td></tr><tr><td>Stealth Procedure Injection</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2F3fNijYjyad8hpAqwJftV%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(9).png?alt=media&amp;token=cc4c5e4d-c4e7-489f-bc0e-91f9b00e95da">RMF_Cyber_Secure_Redundancy_WhitePaper (9).png</a></td></tr><tr><td>Privilege Escalation</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2F58ViSe70VeqD9DT61NnI%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(12).png?alt=media&amp;token=c3455020-dc21-4f83-9194-5381cd18d389">RMF_Cyber_Secure_Redundancy_WhitePaper (12).png</a></td></tr><tr><td>Configuration Wipeout</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FeDPF98w8yqrXxblb53nd%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(15).png?alt=media&amp;token=3114209f-ed94-4924-8fa3-40771e7a520e">RMF_Cyber_Secure_Redundancy_WhitePaper (15).png</a></td></tr><tr><td>Standby Disk Overfill</td><td data-object-fit="contain"><a href="https://73860689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK95oxUATgzuZZ2VhRoDw%2Fuploads%2FPot0EEaycCSIvI1rwKNu%2FRMF_Cyber_Secure_Redundancy_WhitePaper%20(21).png?alt=media&amp;token=b50c88f2-c609-4243-950a-810aa44039ec">RMF_Cyber_Secure_Redundancy_WhitePaper (21).png</a></td></tr></tbody></table>

## **Efficiency**

Efficiency is one-to-one, meaning one standby node can support one primary node failure. Two standbys are required to support two simultaneous primary node failures, and so on.

## References

1. Microsoft, *Overview of Always On Availability Groups (SQL Server)*, [link](https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver17).
