This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 23%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAK%3C/text%3E%3C/svg%3E)
Hi,
I have configured geo-replication and Failover groups for same Azure SQL database, please see following details.
GR
Primary: serverak/testdb
Secondary: serverak3/testdb and serverak4/testdb
Failover groups
Primary: serverak/testdb
Secondary: serverak5/testdb
So my testdb database is getting replicated to three Azure SQL databases (2 for GR and 1 for FG) - question is what happens to GR databases if database is failed over from serverak/testdb ?
One option is GR databases would continue to get the changes from serverak/testdb which would be in readable state after failover. Another option is Azure can see GR and FG are set up on same database and hence GR databases would continue to get the changes from new primary after failover - chances are less still wants to be clear on this.
Appreciate your insightful response. Thank you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 93%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
To understand the question we did testing on our end. We created Primary Server Demo(East US) having Failover group with Secondary Demo1(West US). Also the Demo Server had the geo replication with Demo2(West US2) outside of the Failover Group.
We ran the create and insert queries on Demo and the changes got replicated to both Demo1 and Demo2. We failed over using the Failover group. New roles bein Demo1 as Primary and Demo as Secondary. We even verified by running Insert commands on Demo and it failed with error saying it is read only.
After this we ran insert/create commands on Demo1 and we checked the data on Demo and Demo2 and it had all the new data.
Conclusion - All Geo Replicated secondary move their association to new primary once Failover is done. Please let us know if you are looking for this and get back to us if you have any further question.
Regards
Navtej S
Thank you Navtej for taking time to help !!
"After this we ran insert/create commands on Demo1 and we checked the data on Demo and Demo2 and it had all the new data." - Actually this doesn't tell us if changes in Demo2 are directly coming from Demo1 (new primary) or through Demo1 (new primary) to Demo (old primary, new secondary) and then to Demo2 database.
Continued in next comment....
continued from previous comment....
I also searched in Azure portal but couldn't find which is the current primary server for my geo-replicated databases. I can see geo-replicated databases under the geo-replication blade on both primary server as well as secondary server. I think to avoid this confusion, only listener name should be displayed for geo replication databases which are also configured for failover group.
I have configured FG (Servers: ak & ak5) and GR for Testdb database - attached are snaps before and after failover.
If possible for you @Navtej Singh Saini , could you please respond ?
@anil kumar We are still checking your issues. We will get back to you as soon as possible.
We have answer from the Team regarding the configuration changes during Failover. They have conveyed:
"When failover is activated to one of the secondary databases, all other secondary Db's are automatically linked to the new primary."
Please let us know if you have any further questions.
Regards
Navtej S
Thank you @Navtej Singh Saini for your time and valuable help !!
Stay blessed and happy....