Solved

SQL server 2014 Always On Availability groups requirement/deploy question

Posted on 2014-12-28
2
351 Views
Last Modified: 2014-12-30
Hello Experts team,

I am a little confused here in regards to cluster requirements to deploy SQL 2014 Always On availbility groups for a couple of servers in one site or across sites.

I would like to deploy SQL 2014 Always Availability group following design below. Please, let me know if that is not possible

Design

Two Virtual machines running Windows 2012 R2 standard edition and SQL 2014 enterprise edition in one site,.

One VIrtual machine deployed on a secondary or DR site

Do I have to install traditional MSCS failover cluster for SQL servers and instances on site 1? or I just need to install failover cluster component?

If so, Do I have to setup 2 virtual NICs for each VM? one for intracluster communication and the second one for production communication?.

If not, can you please attach a link step -by-step to deploy SQL server 2014 Always ON availability groups for a couple of servers in one site, and then replicate information to a DR site?

Once the HA question is clarified, how can I replicate the information from main site to DR site? Can i still use SQL Always on AG, or should I pick up another replication method?

Please, be aware that my client is looking for HA and DR for this design, but according to all blogs and documentation I've read so far, SQL server 2014 for VMware is supported only on a Non-shared disk, meaning that the traditional cluster is not an option. Here is my confusion. I understand that your team only supports SQL and HyperV, but according to VMware official KB, SQL server Always On availability groups is supported only on non-shared disk
0
Comment
Question by:Jerry Seinfield
2 Comments
 

Author Comment

by:Jerry Seinfield
ID: 40521912
Can I get an update please?

Why this questions is neglected?
0
 
LVL 14

Accepted Solution

by:
Daniel_PL earned 500 total points
ID: 40522538
Hi,
Since you want to implement Always ON you only need to create Windows cluster. SQL Server won't be clustered in this case.
I suggest creating a cluster on Windows Server hosts at site1, configure AlwaysON Availability Group and then replicate your database(s) to SQL Server Instance at site2 by using transactional repication.

Please find following links as reference:

VMWare - Setup for Failover Clustering and Microsoft Cluster Service
Setting up Replication on a database that is part of an AlwaysOn Availability Group
Configure Replication for AlwaysOn Availability Groups (SQL Server)

Regards,
Daniel
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now