Configuring AlwaysOn Availability across DataCenters (multi subnet)

Hi,
We are working on configuring AlwaysOn SQL availability in azure across multi subnets. Following are list of steps which we are comepleted,
Creating primary domain controller in VNet1
Established VNet to Vnet connectivity across virtual networks (http://msdn.microsoft.com/en-us/library/azure/dn690122.aspx)
Created Replica DC in other Data center
Created a VM in each Data Center and connected it to domain. Verified that these VMs are reachable via ping
Completed with required configuration relating to Failover cluster installation, DNS update as given in tutorial (http://msdn.microsoft.com/en-us/library/dn249504.aspx)
After this we are currently struck in a stage how to proceed with cluster configuration when its across Datacenters (or multi subnets). Documentation relates to creating cluster for single Data center and we would like to know what changes we need to do
for multi subnet.
Refered below links relating to configuring it across data centers using powershell but couldn't get exactly sequence of steps to be followed for section, "Create the WSFC Cluster"
http://blogs.msdn.com/b/igorpag/archive/2014/07/03/deep-dive-sql-server-alwayson-availability-groups-and-cross-region-virtual-networks-in-azure.aspx
http://blogs.msdn.com/b/clustering/archive/2011/08/31/10204142.aspx
We proceed with steps creating cluster and added both VMs as nodes and got stuck.
Can someone provide with some documentation on how we can proceed for further from here.
Sorry for big post just wanted to be elaborate. Let us know if any more information is required from us.

For multi-subnet cluster configuration, you need to configure multiple virtual IP addresses - one for each network subnet. The real challenge here is Active Directory configuration and replication between subnets. The Windows cluster will create a virtual
computer object in Active Directory and that needs to be replicated on all of the domain controllers. In the Azure environment, it means having a domain controller on all of the Azure data centers where you want to create your multi-subnet cluster. Plus, proper
Active Directory sites have to be created and partitioned so that the cluster node on one data center does not cross over to the other data center just to authenticate. All of these have to be configured even before you can create a Windows Server Failover
Cluster and even before you can create the Availability Group.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Similar Messages

SQL Server 2012 AlwaysOn for Multi-subnet geographical HA solution steps -- NON-Shared storage,standalone servers

1.Can any one provide the detailed steps for multi-subnet HA for Always ON Groups.
--SQL Server 2012 AlwaysOn for Multi-subnet geographical HA solution steps
2.Do we need VLAN or not for SQL Server 2012 on win 2012 ? provide details for this VLAN required or not.
--I read MS links, sql server 2012 and above VLAN not required.
Env:
SQL Server 2012
Windows 2012 R2(2 servers different location)
Non-Shared storage (stand-alone servers)
Always ON Availability Group
I have seen white papers,but did not have detail step by steps.
Thanks

Hi SQLDBA321,
As your post, SQL Server 2012 or higher version has removed that requirement of virtual local area network (VLAN). For more details, please review this similar blog:
What you need for a Multi Subnet Configuration for AlwaysOn FCI in SQL Server 2012.
And you can perform the steps in the following similar blog to set up an AlwaysOn Availability Group with multiple subnets.
http://www.patrickkeisler.com/2013/07/setup-availability-group-with-multiple.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Not able to connect to AlwaysOn Availability listener

Hi,
I have configured alwaysOn Availability SQL in Azure environment with multiple data centers. Upon configuring listener and accessing from SSMS through port I am ending up with below error,
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)
Also, I can see that IP Address of different subnet is able to come online. Can this be reason for this failure?

The Availability Group listener on Azure is exposed on a public IP address that you get when you configure your Azure virtual network. Because you've created a load balanced set name (I assumed this because you've mentioned probe port,) the public IP address
will be routed to different virtual machines via the probe port. The public IP with the public port needs to be mapped to the Availability Group listener public IP and private port, respectively. If your public port is the same as your private port on the
Azure VM endpoint, then, the probe port on the Azure VM endpoint has to be the probe port on the Availability Group listener IP resource name. It's a bit confusing to understand the probe port in the context of Availability Groups because the concept is used
for load balancing workload across virtual machines whereas Availability Groups do not necessarily perform load balancing.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
has been moved.
INFO [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
INFO [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
a affinity option for cluster groups besides the anti-affinity within the current version)
I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
one in Asynchronous commit mode.
Thanks in advance,
Dennis van den Akker

Hi Dennis van den Akker,
Do not use the Failover Cluster Manager to manipulate availability groups, for example:
Do not add or remove resources in the clustered service (resource group) for the availability group.
Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
downtime. You must use Transact-SQL or SQL Server Management Studio.
The related KB:
Failover Clustering and AlwaysOn Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff929171.aspx
The similar thread:
SQL Server Clustering 2008 (Multi Node)
https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Hi I am getting the following error in WFC Manager and in my system event log:
Event ID1564:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\SQL2012ClusterWitnessPath'. Please ensure that file share '\\SQL2012ClusterWitnessPath' exists and is accessible by the cluster.
Event ID 1069:
Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID 1205:
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
These errors showed up every hour on the hour and then suddenly stopped. I tried looking at the cluster.log file but there wasn't anything recorded there. The file share witness shows to be online and my AG did not fail over to another node.
The cluster has read and write permissions to the share. I did not find any error messages about the witness share on the remote server.
I am wondering what caused these series of events to occur?
Thanks.

Hi Kevin Ni,
Thanks for your reply. I have ran the validation test and I have 2 warnings. My environment has 2 nodes and 2 AG's with each node a failover for each AG. So that each node hosts and primary and a secondary of an AG. Both nodes are
on the same subnet. Here are the errors.
- Validate Multiple Subnet Properties
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener1' is set to 1. For the current cluster configuration this value should be set to 0.
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener2' is set to 1. For the current cluster configuration this value should be set to 0.
- Validate Network Communication
Node ONE.domain.com is reachable from Node TWO.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
Node TWO.domain.com is reachable from Node ONE.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
I have node TWO setup with NIC Teaming. Node ONE is also setup with NIC teaming but it also has a second IP address but the second IP address cannot communicate with node TWO.

SQL Server 2012 - DB Mirroring + Log Shipping + Multi-Subnet

Hi again,
So AG would be nice to have, but considering the costs of getting it, well, it is a no go for me at the moment (This is like a 1:20 ratio considering Std comes with server licencing and enterprise is only per 2 cores).
So, having 2 sites, with different subnet. Is it possible to configure automatic failover for DBM ? We are running Windows 2012 R2 which supports multi subnet failover. But what about DBM in this case ?
Can the witness be configured on a third site ? (I was thinking of having the following weights: Site 1:2, Site 2:1, Quorum:2 just to have no reconfig to do in case of Datacenter failure)
Also, in order to offload some of the backup load as the DB are somewhat big (1TB), I was thinking of having one additional node per site to which the logs are shipped and that are used to run the backups. The question being, is it possible to log ship from
each "primary" on each site rather than have the primary on site 1 do it for all the servers across the subnets ?
It would be a setup like this:
Site 1 Primary <---DBM---> Site 2 Primary (Hot failover)
Site 1 Primary <---LogShips---> Site 1 Secondary
Site 2 Primary <---LogShips---> Site 2 Secondary
And thus reduces the load on the link between the 2 sites.
I do hope to see AG in the future for Std as they are removing DBM in the next version.
Thanks,

The idea behind the cluster is to have a single IP on which the applications can reach the DB in case of a failover to the secondary site.
This requires a failover cluster instance - mirroring does not work this way.
Because as far as I understand it, either the application has to be aware and able to switch to the new DB primary, or we can use a multisubnet cluster or we can manually reconfigure the applications (so painful)
Mirroring has the failover partner attribute in the connection string that can be utilized. A multi-subnet cluster would require, again, a FCI.
AFAIK, DBM is not recommended for more than 10 DB on an instance due to the worker threads.
"It depends". There can be worker thread issues, but this will entirely depend on your hardware and architecture of processor/SQL Server. In 32-bit world it'll eat up all of your worker threads. In 64-bit world on a decent server it shouldn't be
a problem to have 10-20 out of the box.
I don't mind having to failover multiple database residing on the same instance and having to setup them per DB.
If any of your databases have a dependency on one another, this isn't going to work well as one database could be failed over and another might not be. Just food for thought.
What it sound like you really want is a failover cluster instance and use log shipping to have a "readable copy" somewhere even if it is behind on time. The problem comes in is that a cluster all has to be in the same domain and part of the same
cluster. Your thoughts involve a separate cluster - so I'm not sure why two different ones unless you have multiple environments you're trying to add some HA to.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Moving the Reporting Services and Report Server DB into AlwaysON Availability Group

I have configured the new set of SQL 2012 AlwaysOn Availability Group and need to move the SSRS and it's Report Server DB into that Availability Group.
Can anyone give tell me the steps to do this move?
Can I just backup the ReportServer DB into the AG server then import that DB into the SSRS running on the new AlwasyOn AG SQL?

Hello,
Based on your description, it seems that you want to move the Report Server database to a different server. If so, both the reportserver and reportservertempdb databases must be moved or copied together. You can move the databases by using Detaching
and Attaching or Backup and Restore.
What's more, you should also backup the encryption keys for the report server database you want to move and then restore to the new server.
You can configure report server databases in Always On Availability Group to be part of a replica; however Reporting Services will not automatically use a different replica for the report server databases when a failover occurs
Reference:
Moving the Report Server Databases to Another Computer
Reporting Services with AlwaysOn Availability Groups (SQL Server)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Alwayson Availability groups for a WSFC hosting mutliple SQL FCI's

Hello,
I have a question regarding SQL server FCI's and alwayson availability groups.
Today I have a customer running a 2 node WSFC hosting 9 different SQL FCI's.
Plan is to introduce on this setup SQL alwayson availability groups one per SQL FCI.
Per SQL FCI, running on the 2 node WSFC, we are planning to introduce a dedicated
alwayson availability group with 2 replicas. On replica as primary linked with the
FCI and one replica as secondary on 1 extra node added to the WSFC.
Question i have is, is this a supported configuration?
Thanks in advance
Regards
Raf

This is a supported scenario. However, make sure that no FCI node will run a SQL Server instance acting as a replica. This means you cannot install a standalone instance on one of the FCI nodes and make it an AG replica. You also cannot configure another
FCI in the same WSFC to be a secondary replica in an AG. If you intend to configure AG per SQL Server FCI, you need to add another node in the WSFC and install a SQL Server instance on that node. This can be a SQL Server FCI (which means you need to add two
more nodes instead of just one) or a standalone instance. Also, having an FCI in an AG configuration means that you lose the ability to do automatic failover on the AG-level. This is because the FCI takes care of automatic failover on the instance-level.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Hi,
It is listed here:
http://technet.microsoft.com/en-us/library/dn281933.aspx
Configuration Manager 2012 r2 and DPM 2012 r2 does not support AlwaysOn.
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.
The backup job within SQL Maintenance plan is failing with the following error:
Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"
Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Thanks.
Tracy Cai
TechNet Community Support

Hi, All. Iam using Adobe Document Cloud. After saving a pdf document to this cloud, I am able to see my PC folders . How to disable this? Does my PC folders are also available across other PC's to access them with my Adobe ID? Please help me. Thanks

Hi, All. Iam using Adobe Document Cloud. After saving a pdf document to this cloud, I am able to see my PC folders as well with a browsing option . How to disable this? Does my PC folders will also available across other PC's to access them with my Adobe ID? Please help me. Thanks in advance.

Hi indi68632954,
I can understand your concern & you need to worry about this, as your PC folders won't be available on other PC's as this option is just to browse through the files of the specific system on which you are working as shown in the screenshot below.
Only the files uploaded on the Document cloud will be available over Internet using Adobe Document Cloud service upon the authentication of your Adobe ID & password.
I hope this will answer your query.
In case if you have any further query please let us know, we will be happy to assist you.
Regards,
Aadesh

Preventing Item On Hand reservation in a configure to order environment for multi org same OU environment

I have a scenario in a configure to order environment where I want to automatically creating flow schedules based on sales order demand. I have two orgs in same OU.
1. How to setup sales order line to generate flow schedules in the manufacturing org and then ship the finished goods from the shipping org. I believe this can be done from sourcing rules to populate Warehouse field in sales order line with the shipping org and create Flow schedule in another manufacturing org. Please advise ?
2. Once flow schedule is completed I want to prevent the reservation of Finished good on hand against Sales order so that the On hand could be transferred to shipping org and shipped. Please advise ?
Thanks for your inputs.
Best,
Rajesh

Pl do not post duplicates - Preventing Item On Hand reservation in a configure to order environment for multi org same OU environment

Maintenance plan for SQL Server 2012 Database in AlwaysOn Availability Group

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Thank you very much for your help!
Jake

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Regular maintenance plan would work. Only thing to remember is that when you create log backup plan, there is a checkbox which says whether it should honor backup preference or not.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Is there Ready Made Configuration Packs available for Lync Client ( Client on end user computer ) and Server

Hi,
is there Ready Made Configuration Packs available for Lync Client ( Client on end user computer ) and Server ... to check the configuration, services,compliance, functionality of all the features etc at end user level
and server configuration packs
Regards
Tanoj
OSLM ENGINEER - SCCM 2007 & 2012

No, there is not something available for Lync. What's available can be found here (and it's all not recent):
https://www.microsoft.com/en-us/search/DownloadsDrillInResults.aspx?q=SCCM+%22configuration+pack%22&cateorder=2_5_1&site=
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Configuring AlwaysOn Availability across DataCenters (multi subnet)

Similar Messages

Maybe you are looking for