Hi
I hope to reach out for anyone have done this or have knowledgeable with SharePoint 2013 DR using SQL Availability group, Please advise or comment. I really appreciate all. Please pardon me if my questions below are not making sense as this is my first time doing this task.
I need to build a complete DR for a SharePoint 2013 environment. Forthe past few months, I have build out the DR farm but I have struggle to understand on how to create / setup and configure SQL AlwaysOn Availability Groups at the detail level.
I search through many technical documents and most suggest about the same architecture for SharePoint DR with SQL AOAG but I just can't find the detail information enough on how to create the AG Groups and how configure the AG groups according to the document. I would think the authors must have thought that this information is simple enough to do without much explanation. Well in fact, I went over this with the DBA and they raise many questions that I could not answer or explain.
Our current Primary SharePoint Farm:
One AOAG group Prod-Group1
Database: All databases: config, Service apps, content databases
Member: SQL-N1 and SQL-N2 (Synchronous)
SQL-N1 Primary SQL-N2 secondary
Listener: Prod-Listener
SQL Alias: created SQL_Services for the Prod-listener
Configure SharePoint to connect to SQL_Services.
Working great so far…
I plan to do the following:
This is one of the closest model that I hope to achieve from this design diagram
Primary SharePoint Farm:
Keep the existing AOAG Group Prod-Group1
Same member nodes: SQL-N1 and SQL-N2 (Synchronous commit)
Keep same listener for Prod-Group1: Prod-listener
Keep same SQL Alias: created SQL_Services for the Prod-listener
Change:
For Prod-Group1
Database: only include SharePoint configuration and Service Apps databases on this farm. Content databases here will be moved to Prod-Group2
Create a new AOAG Group: Prod-Group2
Member nodes: SQL-N2 and SQL-N3 (Asynchronous)
SQL-N2 Primary, SQL-N3 secondary
Database: Only Content Databases
No listener (as suggested in technical document for Asynchronous and cross farm node)
Question:
- Will the change above on SQL transparent or will have an affect SharePoint Which still configured to connect to SQL Alias SQL_Services?
- How do Primary SharePoint farm connect to content databases now that in Prod-Group2 and without a listener (no VNN or DNS name). is this transparency ? or how do I configure SharePoint to connect to Prod-Group2?
Answer to these question will help me to build SharePoint DR farm the same way
SharePoint DR Farm:
Create a AOAG Group3 (local to this farm)
Member nodes: SQL-N3 and SQL-N4 (Synchronous commit)
SQL-N3 Primary SQL-N4 secondary
Create a listener for AOAG Group3 (VNN): Group3-listener
SQL Alias: created SQL_DR for the Group3-listener
SharePoint DR Farm configure to connect to SQL Alias SQL_DR
Databases: SharePoint configuration and Service Apps databases on this farm
for content databases, synchronizing from PROD-Group2 to SQL-N3 (secondary and read only ) and possible to SQL-N4
SQL-N3 will change when primary when Failover to SharePoint DR farm take place
I think this is how the detail build out will look like but I know I could be completely missing out steps or just plain out wrong. Please advice and correct me.
Thanks you in advance
Swanl