SQL Cluster with Mirroring

Hello All...........Consider following:
We need to build a two-2 node failover cluster in following manner:
OS: Windows 2012
SQL: SQL 2012
Node_A                                     Node_B
=====                                    =====
SAN_A_Storage                          SAN_B_Storage (Both servers with their own Storage, FSW to be used for Quorum)
Instance_A                                 Instance_B
Each server would have its own Instance that is Node_A would have Instance_A and Node_B would have Instance_B. Mirroring would be configured vice versa that is Mirror copy of Node_A would be on Node_B and Node_B's mirror copy would be on Node_A.
In other words, both instances would be active at the same time with mirror copy on the other server.
Is this doable?

Thanks for the reply.
Actually, I have to implement the solution based on a design that has been handed over to me. But, since it made me confused, so, I turned here for guidance. So, design-wise, I cannot change anything.
I fully understand that HA can be achieved directly through a two-2 node cluster. I also, get your point that in common mirroring scenarios, either a cluster is mirrored to a DR site cluster or a single server, but in my scenario, the cluster is the
same at HA and DR sites.
Following are some clarifications with regards to environment:
Design is such that it involves two-2 sites A and B where both sites have their own Storage (no storage replication). FSW will be present at a third-3 site for quorum. The cluster would be a stretched cluster (Fiber connectivity between
sites). Each site node would run instances of their site with its mirror copy being placed on the other site's node.
Mirroring was chosen due to supportability limitation otherwise AOAG is in place for such scenarios. But, since I have not encountered this situation before, so, I am just verifying if this workable or not? As I have a few more questions after
this, but just wanted to make sure that it is supported in SQL 2012.
THanks.

Similar Messages

SQL Cluster with FQDN only (no instance names)

Is it possible to setup a SQL failover cluster with multiple instances but basically be named the "default instance".
Right now I have three instances: AAA, BBB, and CCC. With failover clusters you associate each SQL instance with its own Drive, its own cluster name, etc. So right now this is how you connect:
aaa.db.domain.com\AAA
bbb.db.domain.com\BBB
ccc.db.domain.com\CCC
Is there a way that you can make it where people can connect by not providing an instance name? Because there is always only one instance per virtual server / fqdn:
aaa.db.domain.com
bbb.db.domain.com
ccc.db.domain.com
I hope I explained well enough. Thanks in advance!

So Azure is not using a regular SQL server? I figured they were just using SQL 2014 or such because they offer Azure services for on-premisis now in your own datacenter.
SQL Azure is definitely not the same as an on-premises SQL Server.
For features and limitation for Azure SQL Database, please see:
http://msdn.microsoft.com/en-us/library/azure/ff394115.aspx
http://msdn.microsoft.com/library/azure/jj879332.aspx
Thanks.
Tracy Cai
TechNet Community Support

Sql cluster with Always on

Hi
I have 2 sites Ho & DR
I have 2 sql servers in each site
I need to make on each site sql cluster and between the 2 sites we need to make always on
please need the steps for this scenario
MCP MCSA MCSE MCT MCTS CCNA

Hi Yasser,
According to your description, you want to setup a disaster recovery solution combining SQL Server Failover Cluster in Primary Datacenter and Availability Group on a SQL Server Failover Cluster in Secondary Datacenter. Assume that, in the Primary DataCenter,
SQL_PV is the FCI instance and CLP_1 and CLP_2 are the two nodes. In the Secondary DataCenter, SQL_SV is the FCI instance and CLS_1 and CLS_2 are the two nodes as the screenshot below shows.
To achieve the goal, you could follow the steps below:
1.Add two nodes CLS_1 and CLS_2 from secondary datacenter into the existing
Windows Server Failover Cluster(WSFC). Please note that all nodes for an availability group must exist on a single WSFC within the same Active Directory domain, even between datacenters.
2.Configure Shared Storage for both CLS_1 and CLS_2 nodes.
3.Install FCI instance of SQL 2012 Enterprise edition using "New SQL Server Failover Cluster Installation" and join the other secondary node using Add node to a SQL Server failover Cluster.
4.Enable Always on Availability Group on newly installed FCI.
5.Define the possible owner for each SQL Server FCI as the following:
a. Go to "SQL Server" services on the Cluster instance under SQL_PV group and go to SQL Properties. Under Advanced Policies, choose only CLP_1 and CLP_2 as possible owner for SQL_PV.
b. Go to "SQL Server" services on the Cluster instance under SQL_SV group and go to SQL Properties. Under Advanced Policies, choose only CLS_1 and CLS_2 as possible owner for SQL_SV.
For more information about the process, please refer to Scenario 2 in the article:
http://www.mssqltips.com/sqlservertip/3150/adding-sql-server-alwayson-availability-groups-to-existing-failover-clusters/
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

SQL HA with Mirroring for Lync 2013

Hi All,
Does SQL mirroring require Windows clustering in place? or Lync 2013 just manages the mirroring?

The network file share is only required while the actual SQL mirroring is initially created as soon as the Lync 2013 topology is published. Clearly, the share should have sufficient space to handle the size of the existing databases with some buffer
to spare.
Please share with us if this helps.
Thanks / rgds,
TechNet/MSDN Forum Moderator - http://www.leedesmond.com

Adding SQL Cluster to MARS

What is the best way to add the physical servers and SQL server instances to MARS?
As a bit of background we have a SQL cluster with 3 physical servers and each one has an ip address. There are also 3 SQL instances with an associated IP address. These are similar in nature to virtual addresses. Both the physical servers and the SQL instances have their own netbios name.
Do we add both the physical servers and the SQL instances to MARS?

Hi Fredrik,
There are alot of events on the IDSSM but these events aren't appeared on MARS although IDSSM is successfully discovered by MARS. That's also happened with Cisco NAC appliance which i added it to MARS but there are no incidents for it on MARS.

SCOM 2012 Reporting Components with a shared SQL cluster

Hi, we are planning to install SCOM 2012 but i am a bit confused around the reporting components.
We have a shared SQL Enterprise cluster with multiple instances which we would like to use for our OperationsMananger and OperationsManagerDW databases. However after trying a test SCOM deployment, installing the SCOM reporting components on a VM requires
a local running copy of SQL reporting services.
Is this true? It seems ludicrous to have to purchase an additional license of SQL just to run the reporting components of SCOM. We have spent a lot of money on our SQL cluster and we would like to use it. We dont want to install the SCOM reporting components
on the shared SQL cluster.
If this is true, can you tell me which license of SQL we require? Just to run SQL reporting services on a VM should just require a standard SQL license, right?
Also if we have to purchase a SQL license for this standalone VM, would you recommend having the OperationsManagerDW database on the shared SQL cluster or on the VM where the standalone instance of SQL reporting services resides.
Surely this is something that other people have an issue with? I would have thought most people would want to use a shared SQL cluster. Any help is much appreciated.

Just to add that SQL Reporting Services isn't cluster aware so the best you could do is to install stand-alone onto a node of the cluster.
To reinforce what Scott is saying, see this screenshot of the install of SCOM reporting:
http://www.systemcentersolutions.co.uk/images/easyblog_images/42/scom/CTP2/Install/SQRS9.png
Technically you can install SCOM reporting on a shared SQL Server Reporting Services instance but as Scott (and the screenshot) state - it will overwrite any existing security settings on existing reports.
Scott is also correct that SQL Server Standard Edition is included as part of the licensing cost of System Center 2012 as long as the SQL instance only runs components of System Center.
cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
I have one SQL 2012 Server with a few instances. 1 for Scom, 1 for SCCM and 1 for Service Manager. The instance shows up as blank for reporting services on the SCOM. Do I have to install SQL on the SCOM box also? Why Can't
it see the instance on my 2012 SQL box? It is in a different instance than SCCM.

SQL Server 2008R2 Active-Active cluster with standard edition?

Hi all,
can I have a 2 node cluster (Windows Server 2008R2 Datacenter Edition: node_1 and node_2) forming a failover cluster with 2 instances of SQL Server 2008R2 Standard Edition (instance_A and instance_B) with:
instance_A running on node_1
instance_B running on node_2

Following thread is on similar topic:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/450dfb42-635b-4c99-ae9f-6b0a23e3430b/sql-server-2008-r2-standard-edition-failover-cluster?forum=sqldatabaseengine
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Cluster 2008 R2 Geocluster configuration with 2 VIP

Hi All,
If anyone has configure 2008 R2 Geo-cluster accross database center in different subnet. I'm interested to know whether is it possible we can cofigure cluster with 2 VIP and both VIP in different subnet e.g primarary DC VIP
is 10.20.x.x and secondary DC VIP 10.144.x.x.
Please help me

Multiple virtual IPs are not supported in SQL Server 2008. The only approach you can go with is implementing a stretched VLAN across the data centers
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

3 Node Cluster with 2 node SQL Always_On

We currently have more than 20 always_on clusters i.e. all following the below configurations
Server 1, Server 2 (High Hardware Configuration i.e. 16 CPU & 30 GB RAM) & File-share Witness on a small box (2 CPU with 4 GB RAM). We have seen some situations where nodes not able to communicate with the file-share and taking the cluster resource
down
Question: Can we create a windows cluster with 2 nodes i.e. (2 big hardware configuration for SQL + 1 small hardware configuration) to make it a 3 node windows cluster and have SQL on only the first 2 nodes with Always_ON ?

Hi,
Could you apply the following updates and see if it will alleviate the symptoms?
System event log errors every 15 minutes on a Windows Server 2008 R2-based Cluster configured with Node Majority and File Share Witness quorum
http://support.microsoft.com/kb/2750820
A cluster resource remains offline after the "Run this resource in a separate Resource Monitor" option is disabled in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;977837
In addition, you may update the NIC drivers and disable TCP chimney offload and check the result.
Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;951037
If still no progress, upload the cluster.log to your OneDrive and share the link here.
Understanding the Cluster Debug Log in 2008
http://blogs.technet.com/b/askcore/archive/2010/04/13/understanding-the-cluster-debug-log-in-2008.aspx
Thanks.
Tracy Cai
TechNet Community Support

Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

Hi All,
Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
aa

I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
Same edition media has to be used in above two operation.
you can install two separate instances with one enterprise and one standard.
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

Backing up virtualised SQL Cluster on Hyper-V with DPM 2012 R2

I'm sure this must have been answered but I can't find it so far. I have a Server 2012 R2 Hyper-V cluster. On that cluster is a virtual SQL 2012 cluster. What is best practise for protecting the SQL cluster? Do I protect the VM through Hyper-V Host backups,
protect the Hyper-V guests directly, etc.?? Are there any good articles on this?
Thanks
Mark

Hi,
i would install a DPM Agent on all SQL Cluster Nodes an Backup the SQL Databases.
Additionally for Desaster Recovery, i would protect the VM, if your Disk space ist not enought for this, just Backup Systemstate of the CluserNodes
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Can Always On Availability Group co-exist with mirroring on the same machine

So imagine 2 server Server A and Server B hosting database A and Database B.
Database A Principal resides on Server A uses AOAG to create a replica on Server B.
Database B Principal resides on Server A and uses Mirroring to create a replica on Server B.
Is this type of topology possible or sensible?
Given that AOAG requires windows clustering and the listner is used for the DNS.

Hello,
I think this may be a common misconception amongst DBAs that they will co-exist.
Do you have any evidence that they can't co-exist? I certainly don't agree with your very strong statement of it being a "common misconception" when it hasn't been proven as such and can, in fact, work.
When you access AOAG, you only point the DNS to th eAOAG listener and when the failover occurs the AOAG listner automatically moves to the mirror server. So the IP address assosiated with the DNS automatically changes. This is not the concept in
mirroring where the IP remains same and failover is done via "failover partner"
You're making the assumption that you would setup mirroring to use the AG listener when in fact it would not be logical to do so as you'd have the issue you noted above. Instead you'd use the normal instance address which would not have a problem with what
you've just described.
So how will mirroring work when the IP assosiated with the DNS alias of SQL server itself changes
Again, you're assuming incorrectly that you'd use the AG listener for Mirroring. However, to give your question an example, you let DNS do the heavy lifting. For example, if there were a multi-subnet cluster just using WSFC and SQL Clustering the IP address
would change but the DNS lookup should point correctly, thus mirroring would still work just as it did (assuming the failover was successful, etc). That's just a single example.
I wonder if MS has some official documentation.
I highly doubt it since they deprecated mirroring.
The one ISSUE I could see arise would be that there can only ever be a single mirroring endpoint and I believe that could become a bottleneck just as it would with mirroring depending on how much AG and mirroring traffic was attempted to be pushed through
it.
Sean Gallardy | Blog |
Twitter

Shared SQL Cluster or dedicated

Can we use shared SQL cluster instance for Lync 2013 deployment or Lync must have dedicated SQL servers either for mirroring purpose or cluster
User load 2200, with EV
Absar

Hi,
1. SQL clustering topologies are not supported for new Lync Server 2013 deployments. For Back End Server high availability, SQL mirroring is the recommended and supported option.
2. You can collocate each of the following databases on the same database server:
Back-end database
Monitoring database
Archiving database
Persistent Chat database
Persistent Chat compliance database
You can collocate any or any or all of these databases in a single instance of SQL Server or use a separate instance of SQL Server for each, with the following limitations:
Each instance of SQL Server can contain only a single back-end database, a single Monitoring database, a single Archiving database, a single Persistent Chat database, and a single Persistent Chat compliance database.
The database server cannot support more than one Front End pool, one Archiving deployment, and one Monitoring deployment, but it can support one of each, regardless of whether the databases use the same instance of SQL Server or separate instances of SQL
Server.
More details:
https://technet.microsoft.com/en-us/library/gg398102.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Can we install a new mssql cluster on the same windows cluster which already containes a mssql cluster with named instance

We have a MSSQL 2008R2 Enterprise edition with a two node active passive fail-over cluster running on 2008R2 windows cluster with out any issues,
Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup

hi,
>>Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Yes it is possible .You need to add new drives as cluster aware and install SQL server and put data and log files on thse drives.YOu would need to create named instance of SQL server and need to create different resource group.Both old installation and new
onw would work separately.
>>Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Good point indeed.You are about to create Multi instance cluster and should plan for scenario where one node is down and other node is handling load for both instances.Memory and CPU should be enough to handle the load.
>>Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup .
Just for collation if you are installing new instance seems little wierd to me.You can manage collation at column ,database and at server level.
http://technet.microsoft.com/en-us/library/aa174903(v=sql.80).aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Cluster with Mirroring

Similar Messages

Maybe you are looking for