Excellent video.. never seen this DAG setup in TH-cam.. Awesome.. can we create DAG enable through gui instead of script? Can we enable this DAG only primary to primary?
Thanks for your comments. Coming to your query we can configure DAG only through T SQL for now. May be in newer versions will see Microsoft may add it through GUI. Thanks MS SQL DBA Tech Support
Thanks for the excellent video .. I have one question .. to configure DAG we need to take the backup and restore into all the servers manually or would it automatically sync into DataCenter 2 Servers ?
Thanks for clearing the doubt Can we configure Dag with different domains ?.. let say we have datacenter 1 with abc domain and datacenter 2 with xyz.. can we configure between abc and xyz domains ?.. if yes , what kind of rules we have to check before configuring? 0:26
As of now i haven't tested this scenario ... however i will say yes first we need to configure two way trust from windows then we can configure Dag.again this is very high level test scenario need very lot of time for R&D and windows team help as well.
No. All forwarders are read only. once u fail over the DAG then only the forwarder will get ability to write. after fail over Forwarder will become global primary Global primary will become forwarder. I hope you got the answer. Thanks & Regards MS SQL DBA Tech Support
Hi, i have created the same test env. all is working okay ... but when i shutdown all nodes down from custer1 then all secondarys from cluster2 are not synchronizing... primary node from cluster2 are synchronizing... How can i solve this ? Thanks Andre
You are linking the always on availability groups. when the global primary went down all nodes from second cluster will be synchronizing only. To avoid this u need to bring nodes online from cluster 1 or u need to force fail over to forwarder to take global primary or u can break the DAG. Test the Scenarios and let me know the outcome. Thanks & Regards MS SQL DBA TECH SUPPORT
Hi bro, please reply.. i am working with a client and their whole set up is on DAG, which was done by a very experience previous dba, he is not working for them now, and i am new to that project as only dba and DAG concept is something new to me. i am having one AG ON Data Center for primary and secondary server with two db in a cluster on this with a domain account.. and i am having a DR server on a different network, and DR server is joined to that primary in AG using DAG, but the thing is your node 3 and 4 and synced from ag1 primary, while on my production. my DR shows asynch. why is that , if you can explain me well
Hi Raghav Singh In a distributed availability group, the synchronization status between the two availability groups depends on the availability mode of both replicas. It makes sense that the asynchronous commit mode in the Distributed Availability Group (DAG) is causing the synchronization status to show as asynchronous. The choice of the availability mode in the DAG depends on your specific requirements and network conditions. Asynchronous commit mode can be appropriate for a disaster recovery scenario to minimize the impact on the primary server's performance.There could be another reasons as well however you need to explore since its your environment and let us know if you find anything new that might help us and other fellow DBAs Thanks & Regards MS SQL DBA TECH SUPPORT
@@MSSQLDBATechSupport See , in DC primary and secondry is there in one AG, in second AG only DR is there, So Is it possible to create AG without secondry, because whatever study i have gone through showing two replicas in second AG also. but in my environment only DR in second AG. Thanks
Excellent video, very informative. Thanks a lot Harsha.
Glad it was helpful!
Very we'll explained in simple way.
kudos to your Dedication towards each topic🎉
So nice of you and Keep watching
Thanks for recording video on DAG....❤
Thanks for showing your appreciation
Very useful information. Thanks a lot brother
Always welcome & Keep watching
Thank you 👌😊
Welcome 😊
Nice Bro!!! Keep going.
Thank you, I will
Excellent video.. never seen this DAG setup in TH-cam.. Awesome.. can we create DAG enable through gui instead of script?
Can we enable this DAG only primary to primary?
Thanks for your comments. Coming to your query we can configure
DAG only through T SQL for now. May be in newer versions will see Microsoft may add it through GUI.
Thanks
MS SQL DBA Tech Support
Sir, thank you, For understanding would have show listener details by expanding...
Thanks & Noted
Thanks for the excellent video .. I have one question .. to configure DAG we need to take the backup and restore into all the servers manually or would it automatically sync into DataCenter 2 Servers ?
No need and it automatically sync into DataCenter 2
Thanks for clearing the doubt Can we configure Dag with different domains ?.. let say we have datacenter 1 with abc domain and datacenter 2 with xyz.. can we configure between abc and xyz domains ?.. if yes , what kind of rules we have to check before configuring? 0:26
As of now i haven't tested this scenario ... however i will say yes first we need to configure two way trust from windows then we can configure Dag.again this is very high level test scenario need very lot of time for R&D and windows team help as well.
great explain
Glad you liked it
nice explanation
Thanks and welcome
Short yet so clear! Thank you!
am I then able to write data to node 1 only or this is supported also from the forwarding AG (node3)?
No. All forwarders are read only. once u fail over the DAG then only the forwarder will get ability to write.
after fail over Forwarder will become global primary
Global primary will become forwarder.
I hope you got the answer.
Thanks & Regards
MS SQL DBA Tech Support
Is this suitable for Active-Active HQ DC and Cloud DC where the users can access the application from both DC.
I have not tested this scenario
Thank you bro
Welcome
Hi, i have created the same test env. all is working okay ... but when i shutdown all nodes down from custer1 then all secondarys from cluster2 are not synchronizing... primary node from cluster2 are synchronizing... How can i solve this ?
Thanks Andre
You are linking the always on availability groups. when the global primary went down all nodes from second cluster will be synchronizing only.
To avoid this u need to bring nodes online from cluster 1
or
u need to force fail over to forwarder to take global primary
or
u can break the DAG.
Test the Scenarios and let me know the outcome.
Thanks & Regards
MS SQL DBA TECH SUPPORT
Sir can please make a video for how to configure link server in always on and cluster
Sure
Hi bro, please reply.. i am working with a client and their whole set up is on DAG, which was done by a very experience previous dba, he is not working for them now, and i am new to that project as only dba and DAG concept is something new to me. i am having one AG ON Data Center for primary and secondary server with two db in a cluster on this with a domain account.. and i am having a DR server on a different network, and DR server is joined to that primary in AG using DAG, but the thing is your node 3 and 4 and synced from ag1 primary, while on my production. my DR shows asynch. why is that , if you can explain me well
Hi Raghav Singh
In a distributed availability group, the synchronization status between the two availability groups depends on the availability mode of both replicas.
It makes sense that the asynchronous commit mode in the Distributed Availability Group (DAG) is causing the synchronization status to show as asynchronous.
The choice of the availability mode in the DAG depends on your specific requirements and network conditions. Asynchronous commit mode can be appropriate for a disaster recovery scenario to minimize the impact on the primary server's performance.There could be another reasons as well however you need to explore since its your environment and let us know if you find anything new that might help us and other fellow DBAs
Thanks & Regards
MS SQL DBA TECH SUPPORT
@@MSSQLDBATechSupport See , in DC primary and secondry is there in one AG, in second AG only DR is there, So Is it possible to create AG without secondry, because whatever study i have gone through showing two replicas in second AG also. but in my environment only DR in second AG. Thanks
Yes it is possible. you just type dag sql server in google image search then you will get so many possible setup.
I am getting secondary dag disconnect after dag setup. Can I help
Kindly check error log and permissions
All permission available. Service account has sysadmin permission. The thing is these are azure servers and have LB configured in prod and DR botg
okay