Last modified by Billie D on 2021/02/15 17:38
From version 20.1
edited by Billie D
on 2021/02/15 20:32
To version 21.1
edited by Billie D
on 2021/02/15 17:38
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Content
... ... @@ -157,14 +157,18 @@
157 157  
158 158  == Clustering and AlwaysOn Availability Groups Combined ==
159 159  
160 +The diagram in Figure 2-9 shows that the **primary replica** of the database is hosted on a **two-node active/passive cluster**. If the active node fails, the rules of clustering apply, and the **shared storage**, network name, and IP address are reattached to the passive node, which then becomes the active node. If both nodes are inaccessible, however, the availability group listener points the traffic to the **third node of the cluster**, which is situated in the** DR site** and is synchronized using **log stream replication**. Of course, when **asynchronous mode** is used, the database must be **failed over manually by a DBA**.
160 160  
161 161  [[image:SQLAG0010.JPG||height="695" width="992"]]
162 162  
163 -SDAF
164 164  
165 165  == Clustering Combined with Log Shipping ==
166 166  
167 +Another common scenario is the combination of a cluster and log shipping **to achieve high availability and disaster recovery,** respectively. This combination works in much the same way as clustering combined with AlwaysOn Availability Groups and is illustrated in Figure 2-10.
168 +
167 167  [[image:SQLAG0011.JPG||height="750" width="1026"]]
168 168  
169 169  
170 -DSF
172 +The diagram shows that a __two-node active/passive cluster__ has been configured in the primary data center. The __transaction log(s)__ of the database(s) hosted on this instance are then __shipped to a stand-alone server in the DR data center__. Because the cluster uses shared storage, you should also use shared storage for the backup volume and add the backup volume as a resource in the role. This means that when the instance fails over to the other node, the backup share also fails over, and log shipping continues to synchronize, uninterrupted.
173 +
174 +If failover occurs while the log shipping backup or copy jobs are in progress, then log shipping may become unsynchronized and require manual intervention. This means that after a failover, you should check the health of your log shipping jobs.
Icon SQL Server.Code.SQL ServerClass[0]
databaseList1
... ... @@ -1,0 +1,1 @@
1 +Blog.BlogIntroduction