I am trying to cluster two sql node server on hyper-v both virtual and my situation is below :
two hyper-v host connected to vnxe storage
two hyper-v are mapped to 3 LUN ( SQL Data , SQL logs , Quorurm)
connectivity between hyper-v and storage direct fiber
three LUN are mapped to the virtual SQL01 and SQL02 as VHDX and configure it on virtual machine as IDE below is the picture
LUNs are presented to the guest SQL01 and SQL02 and visible through disk management
When create the fail over cluster i am not getting the disk to add them to cluster
Getting the below error when validate the storage :
No Disks suitable for cluster disks were found, For diagnostic information about disks available run the Validate config wizard’..
Also , regarding this LUN how i can make them shared on the host side ?
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical) 2. MSDTC 3. SQL Server 4. windows Cluster
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
I am writing up a general purpose document regarding Disaster Recovery and Backup and Restore, etc. I have a question that I've been unable to find any definitive answer on, and I was hoping that someone might have an answer.
Here is the scenario and what I have so far, and my question:
Scenario - A simple database, with one MDF and one LDF, each on it's own disk, with no mirroring or filegroups etc.
Disaster - the LOG disk fails.
To simulate the disaster, I shut down SQL Server, and delete the LDF manually.
When I restart SQL Server, the database is marked as suspect. As expected :)
So, now the recovery begins..... I've read that in this case there is no data loss, but I find that hard to believe. Can anyone confirm?
Anyway, how to restore the database to usable status? Here is what I've come up with so far:
1) Do a backup of "the tail of the log." This works even though there is no log. I have no idea why really, but I can't proceed otherwise.
2) Detach the database.
3) Reattach the database. This auto-creates a new log file (albeit not in the location I want, which makes for more work after).
At this point the database appears to be fine. I have not seen any lost data or problems, but of course I'm working on a test database, not with live users hitting it constantly. If the database were under heavy use, I expect that there might indeed be data lost?
Is this the recommended way to recover from a disaster of this type? Or, would it be better to just go back to your last good backups and forget about "up to the minute" recovery in this case? Or is there yet another means?
I have a windows 2012 cluster environment that consists of two SQL servers nodes with Quorum disk configured as witness.
Manual failover between nodes is working fine, however the sql instance virtual is not seeing the Quorum disk.
Moreover the Quorum disk has the same number as another cluster storage disk, is that considered a problem?
When I move the SQL instance from a node to anohter, should the Quorum Disk change ownership as well to that destination node ? if it is not changing ownership what would be the problem??
Is there a way for multiple SQL 2005 instances in a cluster to share drives for user databases.
Once we install our instances in the cluster using seperate disk resources. Can we then have multiple instances share the same physical disk for user databases only. This is for a test environment.
I have a 2-node cluster environment & I am planning to replace it with new hardware. Currently I am using MSA1000 Disk arrays. Now I would like to move my storage to SAN.
What are the necessary pre-requisite and actions to do this. Any particular thing, I must take care in planning.
I recently learned of the DiskPart.exe tool that is used to improved the performance of Exchange 2003 cluster implementations. The articles I read alluded to the fact that improperly align disks could ruin the phisical devices themselves due to stress.
So my question is:
How come the MS documentation does not suggest using "Disk Partitions Track-Aligned" methods to improve SQL?
Is there some big difference in the way these two server suites managed I/O reads/writes?
"Site A" SQL 7.0 Cluster with Drives on Shared Storage. "Site B" SQL Server Cluster with Drives on Shared Storage Both Configured as Active/Active (8+ databases <100GB total)
How can I get the DB's (all) from Site A and allow a DIFFERNET cluster to control them.
Basically, I want to move all DB's from "Site A" and bring them into "Site B" with all relevant data ..ie master DB etc . I have a time window of 90 Mins and I cannot lose one single piece of data.........( I need to lie down now) Help would be apprecitated)
We have an HA configuration with an Active-Passive Cluster / Shared Disk SAN which is working great. I have been looking for how to replicate the information to our DR site. We have many databases (some are more static vs. other transactional). I had some questions:Would it make sense to configure a snapshot for the static databases? Is that possible from a clustered environment using it as the publisher?Would it make more sense to configure the clustered environment to use transactional replication? Is it possible from a clustered primary?Is log shipping too archaic?
Cluster services gives the high availability needed - that is great.But I have never seen any discussion about what happens when a nodefails - what do you do to get everything back to the active-passivetandem.I imagine there is not much difference in terms of recovery procedurefor either active or passive node. So I'm just going to make up ascenario that we have encountered. The system hard drive (not theshared disk) on primary node fails. Cluster fails over to the passivenode. Following are the problems I have at hand:-After installing windows, I need to install driver and configure thepermission to access the SAN. There is no way I could do it since thesecondary node has exclusive access to the disks.-Imagine I got that working, is there anyway to install SQL so SQLwould know this server used to be the primary node and attach the DBand translog automatically-Finally, there is no proper way to apply SQL 2000 service pack 3a.Originally when the cluster was fully functional, the service pack wasapplied to active node and that automatically upgrades passive node.Now we have a machine without 3a and a machine with 3a alreadyinstalled. See any problem?Consider all of the above as this one big question: What is a properprocedure to restore a cluster when one of the node goes down? Whetherit's the active or passive node.
I have inherited two separate SQL clusters. One cluster instance is called DESQLSC1INST1 and the other is MKSQLSC1INST1.
On MKSQLSC1INST1 I can connect by using MKSQLSC1INST1, MKSQLSC1 and the IP address that the cluster is running on. On DESQLSC1INST1 I can only connect using DESQLSC1INST1.
I have checked configuration manager but it does not show me how this is set up.
I am learning SQL Server failover cluster installation. My question is regarding the options to install failover cluster instances on the Windows Failover Cluster. I have seen ead there are two options to do so.
From the installation center, installation option-> New SQL Server installation option and afterwards add node to SQL Server failover instance.From Installation Center, Advanced option-> Failover cluster preparation and then Failover cluster completion step.What is the difference between these two options and which option to use in which scenario?
We have 2 clusters, 1 running SQL 2008 on Windows 2008 R2 server and 1 running SQL 2000 on Windows 2003 Server. Because of a disaster with the disks, each of the passive nodes had to be rebuilt and Ive been asked to install SQL on the nodes.
Ive not done this before. Does this mean simply adding a new node to the cluster through the wizard? Or do I need to reinstall the entire cluster?
I think SQL 2000 is too risky as its unsupported, so Im going to resist that. But how should I approach the SQL 2008 Instance?
I am using SQL 2012 SE with clustering on Windows server 2008 R2. Now I want migrate it to windows server 2012 with minimal down time. So I want to evict the passive node and add a new node with windows server 2012 and install sql server 2012 SE on the new passive node and perform a failover(make the node with 2012 OS as active) and then evict the new passive node and add another node with windows 2012 and then do the same thing?
I'm getting the following error when I go to create a cluster in the Failover Cluster Manager in Windows Server 2008.
"The address 10.10.10.111 is not valid for its associated network"
I'm following the instruction in the book for the 70-462 exam. There was a step that had me create a DNS A record for the address sql-cluster.contoso.com. The IP address was mapped to 10.10.10.111. I'm not sure if this is the culprit but its the only time I used that IP address in the setup.
Below are 2 screenshots. The first screenshot is the error. The second screenshot is my DNS console.
I saw following point on Technet article about RBS.The local FILESTREAM provider is supported only when it is used on local hard disk drives or an attached Internet Small Computer System Interface (iSCSI) device. You cannot use the local RBS FILESTREAM provider on remote storage devices such as network attached storage (NAS).It looks like that we cannot use FILESTREAM on Failover Cluster because to setup Failover Cluster we need to have NAS. But then the NAS is made available locally for Failover Cluster so FILESTREAM should work right?Found another article which talks about setting up FILESTREAM on Failover Cluster. URL...
The main objective is to have a third party program operate on a failover cluster. The OS is Windows Server 2012 Datacenter loaded on 2 nodes. A virtual node exists along with supporting disks. This client software uses a SQL Server database. SQL Server 2012 Enterprise is installed and operating in a failover environment. However the client software is not failing over. If the connection to node A is lost, SQL Server fails over to node B. But the client application does not.
What needs to occur in order to associate the client software with the failover cluster? This software has 6 services total installed. Some are referred to as servers - looks like to communicate between remote client computers and the database. What is the process to associate the client software with the failover?
My environment has a 4 node cluster , 2 in primary and 2 in sec dc. Storage is sperate for both.
Need to setup always on for 4 Instances there on the 2 nodes of the primary dc. Is there any restriction in setting up always on for multiple instances for a cluster.
I have had a serious issue with a production AlwaysOn cluster whereby the service did not successfully transition to the secondary node and I cannot find the root cause of the issue.
Some details: It is a 2 node cluster (same datacenter) with a shared disk quorum, Windows Server 2012, both are virtual machines running on VMWare vSphere 5.5. SQL Server version is 2012 Enterprise SP2 CU6
The failover occurred because of a network incident (a spanning tree recalculation caused a connection timeout between both nodes). Initial entries in the SQL Log look normal for this event, for example:
05/08/2015 11:18:06: A connection timeout has occurred on a previously established connection to availability replica 'FIN-IE-PA078' with id [6910F4A9-87E7-4836-BA79-0F41BE90266D]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role. 05/08/2015 11:18:06: AlwaysOn Availability Groups connection with secondary database terminated for primary database 'UserManagement' on the availability replica with Replica ID: {6910f4a9-87e7-4836-ba79-0f41be90266d}. This is an informational message only. No user action is required.
[code]....
My interpretation of this is that the cluster failover attempts failed, because the network condition still persisted. The network interruption lasted approximately 2 minutes, and I would have expected the cluster to come back online at this point, after the restart delay period as suggested in the last entry in the error log. However this did not happen.
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
we have to build high availability SQL 2012 cluster for VDI and we have two options. One option is to build a server cluster with combination of failover and mirroring and other option is to build failover cluster with AlwaysOn.We are not sure which option to chose. We have contacted Microsoft support to provide us some documents and instructions for failovermirroring combination but they have send us instructions for AlwaysOn option.
What would be best way to build high availability cluster for VDI? Also, since first option is very complicated.
I am having Windows 2012R2 Std with SQL2012SP2. Trying to add SQL cluster node2 but unable to locate the instance name when I click on drop down button.Understand that SQL Server Agent is required but it is not listed as cluster resource. Therefore, I perform the followingFrom Windows Power Shell with Administrator rights
1. Import-Module FailoverClusters 2. Add-ClusterResourceType "SQL Server Agent" c:windowssystem32SQAGTRES.DLL
Error: Add-ClusterResourceType : Unable to locate the cluster service executable on node1.The network name cannot be found.No problem to ping all cluster related names as well as fail-over to and from next available node.
I have a 3-nodes AlwaysOn cluster (Windows Server 2008 R2 SP1 + SQL Server 2012 RTM), Node Majority quorum, the quorum vote for each node is 1.
Today the AlwaysOn AG was suddenly down due to the cluster service on node 1 stopped and can't be started.
The error in eventlog is -
The cluster database could not be loaded. The file may be missing or corrupt. Automatic repair might be attempted. The Cluster Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine.
The Cluster Service service terminated with service-specific error The system cannot find the file specified..
The error log in cluster log is -
0000156c.000008f8::2012/09/05-08:09:36.057 INFO [DM] Key RegistryMachineCluster.restored does not appear to be loaded (status STATUS_OBJECT_NAME_NOT_FOUND(c0000034)) 0000156c.000008f8::2012/09/05-08:09:36.057 WARN [DM] Node 1: Failed to unload restored hive from the registry with error STATUS_INVALID_PARAMETER(c000000d) 0000156c.000008f8::2012/09/05-08:09:36.057 INFO [DM] Node 1: loading local hive 0000156c.000008f8::2012/09/05-08:09:36.057 ERR [DM] Node 1: failed to unload cluster hive, error 2.
Now the cluster service can't be started on node 1, error code 2. Looks like the clusdb in C:windowscluster is missing or corrupted. How to restore the clusdb file? And how to prevent this happen again?
All nodes were well patched, AlwaysOn and cluster related hotfixes were all installed. [URL] .... doesn't wok.
In case of hardware unrecoverable issue, I have two msdn articles which states different things.
First one claims you remove the node from mscs.
[URL]
Second one claims you should remove it using sql server installation and links to the first link which says you should do it from mscs:
[URL]
Then this third article invalidates the second article. "To remove a node from an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be removed from the SQL Server failover cluster instance."
[URL]
It is a hardware faillure where the secondary node is inaccessible.
So what is the proper way to evict a node you cannot access due to a hardware failure?
note: I don't plan on adding back the failed nodes after removing it. i.e. I am interested in the removing part.
We are running with a 2 node windows cluster having three SQL instances on it.
OS: Windows server 2008R2 SP1 SQL : SQL server 2008R2 (10.50.6529)
Currently both nodes have 256 GB or memory and we are having multiple auto failover for resources. What will be the best practice for OS memory reservation (OS+tools) so that we can set SQL max memory settings accordingly?
We have two locations in US, I am thinking of having 2 node SQL cluster for Lync 2010, I alardy have One DB server running in one location, now we got new site where we are planning to have one more DB for redundancy.
I want to install service pack 3 to my SQL Server 2012 Enterprise running on windows server 2008 R2 Enterprise fail over cluster, I read about the SP installation in technet, its mentioned that the passive node should be patched first and to do this the passive node should be removed from the cluster, I need to know whether I should completely remove the node from windows cluster or remove the node by using SQL Server installer and install the service pack and then add it back to the cluster, Can I do this by pausing the node in cluster and perform the service pack installation ?
