Thanks J-P and MBS. I signed up for that list and am going through their archives.
Don K From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, May 22, 2014 6:35 PM To: [email protected] Subject: RE: [NTSysADM] Server 2012 R2 Multi-Site Failover Cluster best practice fro SQL 2012 HA + DR this list has some very experienced sql admins http://databaseadvisors.com/mailman/listinfo/dba-sqlserver ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Server 2012 R2 Multi-Site Failover Cluster best practice fro SQL 2012 HA + DR Date: Thu, 22 May 2014 23:27:49 +0000 Sure. this is all about the SQL dba configuring AAG and how you configure your witness(es). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Don Kuhlman Sent: Tuesday, May 20, 2014 12:45 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Server 2012 R2 Multi-Site Failover Cluster best practice fro SQL 2012 HA + DR Hi folks. I'm working on a new assignment and have been Googling, searching, looking, etc. for a while and not coming up with too much helpful information. I'm working on building out a Server 2012 R2 failover cluster with a total of 3 nodes - 2 at the prod site, 1 at a DR site. They are to support SQL 2012. We want to have High Availability (HA) and DR but only HA at the 2 node main site with a manual failover to the DR for DR testing or an actual DR scenario. What I've read seems to indicate that we should use a multi-site cluster on the OS level and set the DR node to not vote so it can't become active unless we do a manual failover. We want to allow the DBA to build out Availability Groups in SQL for their requirements, but again we don't ever want the DR site to become active unless we tell it and do manual changes to bring it up using current SQL data. Has anyone worked on this who may have some insight ? Thanks, Don K
