SQL 2012 Failover Cluster and replication, or P2P replication for DR
Posted on 2012-04-11
My clients provides mobile transactional sites for retail clients. They are looking to refresh their infrastructure. Currently, their infrastructure is hosted at a single datacenter (managed hosting). I want to include some DR in their new design, and will have some of their infrastructure hosted at a second site. They currently have a MS SQL Failover Cluster (consisting of 2 servers). I will recommend another non-clustered SQL server at the secondary site. Would it be best to keep the failover cluster at the primary site, and perform replication to the secondary site, maintaining a warm standby, or simply get rid of the failover cluster, and have one SQL server at each site using P2P replication? I know very little about P2P, but having two separate active servers in different locations seems to meet the requirements for resiliency, as well as ensuring the DR site is as up to date as possible.
They will probably buy completely new kit for their planned infrastructure, and obviously P2P doesn't have the expense of shared storage. Connectivity between the sites will be very good.