Sno.
|
AlwaysOn FCI for HA and DR
|
AlwaysOn AG for HA and DR
|
1
|
Shared Storage solution
|
Non-Shared Storage solution
|
2
|
Instance level HA
|
Database level HA (can be one or more databases)
|
3
|
Logins, SQL Agent jobs, certificates and other SQL Server instance level objects are in-tact after failover
|
Manual adding logins, SQL Agent jobs, certificates and other SQL Server instance level objects to all secondary's
|
4
|
Instance-level protection without data redundancy
|
Each group of secondary AG database(s) are redundant copy of primary
|
5
|
Have Active\Passive nodes. No concept of a secondary database.
|
DR replica can be Active Secondary for backup, read-only workload.
|
6
|
Application connects via virtual server name
|
Application connects via AG listener name
|
7
|
Does not maintain a redundant copy of the data hence does not protect against an I/O subsystem failure
|
Protection against an I/O subsystem failure i.e Automatic Page Repair
|
8
|
No special requirements with respect to database recovery models
|
Database(s) in AG must be in FULL recovery model
|
Difference between AlwaysOn FCI and AlwaysOn AG
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment