Warning: Constant WP_TEMP_DIR already defined in /var/www/html/blogs/joe/wp-config.php on line 93

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/joe/wp-config.php:93) in /var/www/html/blogs/joe/wp-includes/feed-rss2-comments.php on line 8
Comments on: AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using AlwaysOn Availability Groups https://www.sqlskills.com/blogs/joe/alwayson-architecture-guide-building-a-high-availability-and-disaster-recovery-solution-by-using-alwayson-availability-groups/ SQL Server Performance Tuning, High Availability and Disaster Recovery Blog Fri, 09 Aug 2013 20:02:55 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Joseph Sack https://www.sqlskills.com/blogs/joe/alwayson-architecture-guide-building-a-high-availability-and-disaster-recovery-solution-by-using-alwayson-availability-groups/#comment-2787 Fri, 09 Aug 2013 20:02:55 +0000 /blogs/joe/post/AlwaysOn-Architecture-Guide-Building-a-High-Availability-and-Disaster-Recovery-Solution-by-Using-AlwaysOn-Availability-Groups.aspx#comment-2787 In reply to John Tracy.

Hi John,

I think it all depends on stability of connection between the voting members and ensuring you don’t get false loss of quorum and votes.

One quote from Microsoft is “The file share witness can be located at a third site, that is, a different location from the main site and secondary site, so that it is not lost if one of the other two sites has problems.” But if your third site is spotty or connectivity is bad, then local to the primary DC would be another choice I would consider.

]]>
By: John Tracy https://www.sqlskills.com/blogs/joe/alwayson-architecture-guide-building-a-high-availability-and-disaster-recovery-solution-by-using-alwayson-availability-groups/#comment-2786 Fri, 09 Aug 2013 14:44:49 +0000 /blogs/joe/post/AlwaysOn-Architecture-Guide-Building-a-High-Availability-and-Disaster-Recovery-Solution-by-Using-AlwaysOn-Availability-Groups.aspx#comment-2786 In reply to Joseph Sack.

Thanks Joe. To clarify on this setup we are not doing a FCI + AG. That was our first setup. On this one we are doing a standalone sql install in each DC and using automatic failover. So it looks like somewhere outside the both dc’s would be the best?

]]>
By: Joseph Sack https://www.sqlskills.com/blogs/joe/alwayson-architecture-guide-building-a-high-availability-and-disaster-recovery-solution-by-using-alwayson-availability-groups/#comment-2785 Fri, 09 Aug 2013 13:51:19 +0000 /blogs/joe/post/AlwaysOn-Architecture-Guide-Building-a-High-Availability-and-Disaster-Recovery-Solution-by-Using-AlwaysOn-Availability-Groups.aspx#comment-2785 In reply to John Tracy.

Hi John,

For AGs on FCIs – automatic failover is not an option (needs to be manual).

Regarding File Share location – the answer really depends on several factors – but in summary you want to make sure that you don’t have false-loss of quorum if your file share is placed somewhere unstable. I would be biased towards placing it in the same DC, given that automatic failover isn’t an option anyhow. This differs from DBM advice – where having the witness outside of the DC might be beneficial (third data center, for example, or cloud-solution).

Best Regards,

Joe

]]>
By: John Tracy https://www.sqlskills.com/blogs/joe/alwayson-architecture-guide-building-a-high-availability-and-disaster-recovery-solution-by-using-alwayson-availability-groups/#comment-2783 Thu, 08 Aug 2013 22:35:13 +0000 /blogs/joe/post/AlwaysOn-Architecture-Guide-Building-a-High-Availability-and-Disaster-Recovery-Solution-by-Using-AlwaysOn-Availability-Groups.aspx#comment-2783 Joe,

First, thanks for your excellent job on that white paper. We used it and successfully set up and FCI + AG solution for HA and DR. Now for another client we are setting up an asymmetric cluster between two data centers. A standalone sql install in each center with Always On synchronous replica between the two (the latency is very low). I am a bit confused on how to set the quorum for this. The recommendation is Node + File Share. I am not sure where to put the file share? If I put it in the primary data center and the whole DC goes down, will I still fail over to the secondary DC automatically? What about putting it in the secondary data center? Do you have any suggestions or resources you could help me find. My Google skills are failing me on this one.

Thanks

]]>