Build a SQL 2008 R2 Failover clustering

Hi,
Am looking for a 2 node active passive SQL server clustering for testing purpose
I believe that for building a cluster we need a AD, DNS and DHCP and shared disk ..
I have searched in Internet and as of now I haven't found a complete solution for a SQL Server 2008 R2 fail over clustering
I have tried my self for building a SQL cluster with the available information in internet . But every time am getting one or other error...
Could some one here help me here to find out a COMPLETE solution for building a 2 node active passive SQL Server 2008 R2 fail over cluster.
Video links or step by step screen shot will be much appreciated.
Oracle VM virtual manager , and Starwind I have used to create a Windows cluster.

Hi Nirmal,
You are right. Cluster
configured Quorum automatically
But when am installing SQL am getting this error - SQL Server network name
I have tried with Windows cluster name and DTC name in SQL Server network name
But throwing the error
"The SQL server failover cluster instance name already exit as cluster resource. Specify a different failover cluster instance name"
When am trying with a different name am getting the below error.
"The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid."
How to resolve the issue.
Am using
win 2008 R2 SP1, SQL 2008 R2
Oracle VM virtual box, and Star wind software

Similar Messages

Alter IP address of SQL Server AlwaysOn Failover clustering Iistener

Hi,
Is there a possibility to change the IP address of SQL Server AlwaysOn Failover clustering Listener IP address without deleting the exiting one and also retaining the same DNS name.
NOTE: Only the IP address needs to be altered rest all (DNS, port) should remain the same.
Regards
Vijay

Hi Karthikkk,
As your description, you want to modify the listener IP address in AlwaysOn availability group without changing other settings including DNS and port. To achieve this, you could modify a listener IP address on primary replica using the following statement:
ALTER AVAILABILITY GROUP group_name
MODIFY LISTENER ‘dns_name’
ADD IP { (‘four_part_ipv4_address’, ‘four_part_ipv4_mask’) | (‘dns_nameipv6_address’) }
For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ff878601.aspx
Regards,
Michelle Li

ColdFusion 9 Fails after SQL 2008 Cluster Failover

All,
I have a ColdFusion 9 app server that seems to be failing when my SQL 2008 cluster fails over to the passive node. By failing, my IIS server does not respond to any .cfm requests about 4-5 minutes after the failover. It serves out static and .asp pages just fine. Restarting ColdFusion server service and rebooting the server itself does not fix the problem. The only fix is to fail the SQL cluster back to the original node.
Specs are as follows:
SQL - SQL 2008 SP1 64-bit active/passive cluster VM
CF - CF9 running on Windows 2008 SP2 64-bit VM
Erick

Problem solved. We had a linked server defined in SQL that pointed to an Oracle instance. We could successfully run the "Test Connection" in SQL Management Studio for the linked server when our SQL 2008 cluster was on node 1. However, we got an "OraOLEDBpus10.dll: The specified module could not be found" error message when trying to test the connection when the cluster was on node 2. The fix was to add the Oracle folder path to the Windows PATH environment variable on node 2. The Oracle installer is supposed to do this automatically, so we don't know why it was missing.
The reason CF would become unresponsive was that we had a template with a query that used the linked server. The purpose of this template was to monitor the status of the linked server. Using CF Server Monitor, we were able to see active requests to that template which would keep running and not terminate even though we set a timeout value in CF Admin.
Erick

SQl 2008 R2 Failover Cluster does not failover after fresh install

I have installed a two node SQL Server 2008 R2 cluster. I used a Named Instance and the SQL Server and SQL Server Agent cluster resources are online on node 1. When I want to move the SQL Server group to node 2, the SQL Server resource fails to start (error
1205 and 1069).
I see in the application log that it is starting up database 'master'. After that I see: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup etc...
It runs fine on node 1, so what goes wrong?

Hello,
Please verify DTC is configured correctly.
http://msdn.microsoft.com/en-us/library/dd897479(BTS.10).aspx
Please see the following resources also:
http://technet.microsoft.com/en-us/library/cc773525(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc773447(WS.10).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrate from Existing SQL 2008 R2 Failover Cluster (Rackspace) to new offsite SQL 2008 R2 Cluster (our own cloud)

I have an existing cluster sitting in Rackspace. We have a new co-location with its own SAN that we want to migrate everything over to. Now, if we were keeping the SAN active in Rackspace, this wouldn't be an issue and I'd just add two new nodes to the cluster
and take down the two old nodes, but I need the data shipped to the new SAN so everything in Rackspace can be turned off. VPN is configured between sites (500mbps pipe), so bandwidth isn't a problem.
Should I be adding new shared storage to the existing cluster, replicate to that, turn off the old shared storage, then add new nodes and eventually disable old nodes? I'm trying to do this with the least downtime.
The picture can best be described as this (very simplified)
RACKSPACE CLUSTER - on its own SAN
Node 1: SQLSERVER1-RACK
Node 2: SQLSERVER2-RACK
SQL Server Name: SQLSERVER
NEW CLUSTER - on its own SAN
Node 1: SQLSERVER1-NEW
Node 2: SQLSERVER2-NEW

while this might be doable using SQL Server replication, log shipping is best on a continual basis, or use a backup restore for a one time copy.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li

Server 2008 R2 failover cluster for DFS servers

A new client currently has a couple Server 2008 R2 failover clusters (one at each of their two primary sites) as their two hub DFS locations. I'm confused, and can't see much of a reason for this implementation, which only seems to introduce added complexity
with no real benefits. Here are my reasons:
- At each site, the servers in the failover clusters are on the same server VM farms, hosted on the same SAN's.
- The data hosted on each node of the clusters are not identical. For example, server1 has 25 DFS replicated folders and server2 has 20 replicated folders. In fact, the ~25 folders on server1 are all named <site>-user, and the ~20 folders on server
2 are <site>-data. There appears to be no crossover.
So if the SAN fails, they're screwed. If the VM host fails, they're screwed. Why not just have two DFS servers at each site for redundancy within each site, and replicating with other site DFS servers as needed? I'm not super strong with failover clustering
at all though, so I may easily be missing something.

Hi Steve,
From the description, as you said it seems create more factors which may cause a failure.
Using DFS on cluster could eliminate the possible of a single failing VM. However if the VM host is down, which will still leads to a failure. So actually the risk is still them same as just creating DFS namespace on these 2 VM hosts or any other file server.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SCCM 2007 Distribution Point Share on a Failover Clustered File Server.

Is SCCM 2007 Distribution Point Share supported on a Windows 2008 R2 Failover Clustered File Server? I can get the packages to copy to the DP Share. But if I create them on a non clustered server it works fine. Are there any special settings that need top
be configured for clustered shares?
Thanks,
Steve
Steve

Hi Steve,
As far as I know this scenario is not supported scenario, In Windows Server® 2008 R2, the Cluster Shared Volumes feature included in failover clustering is only supported for
use with the Hyper-V server role.
The creation, reproduction, and storage of files on Cluster Shared Volumes that were not created for the Hyper-V role, including any user or application data stored under the
ClusterStorage folder of the system drive on every node, are not supported and may result in unpredictable behavior, including data corruption or data loss on these shared volumes. Only files that are created for the Hyper-V role can be stored on Cluster Shared
Volumes. An example of a file type that is created for the Hyper-V role is a Virtual Hard Disk (VHD) file.
More information:
Deploying Cluster Shared Volumes (CSV) in Windows Server 2008 R2 Failover Clustering
http://blogs.msdn.com/b/clustering/archive/2009/02/19/9433146.aspx
Backing Up Cluster Shared Volumes in a Failover Cluster in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff182356(WS.10).aspx
I’m glad to be of help to you!
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]

Hyper-v Failover clustering for SQL Server lab

Hi,
After 20yrs years of IT software experience, now I am realizing that I don't know much about hyperV clustering. :) I am trying to setup a lab. I badly need help on configuring network adapters
to make the machines accessible from each other. Please see details below:
I have a laptop with 8gb ram with windows 8.1 hyper-V. I created 4 VMs with Windows 2008r2 on it and further I intend having SQL Server Failover Clustering. VM details are as below:
DC - Domain Controller
SanStorage - MS iSCSI target
Win1 - Primary node in the cluster that will have SQL Server instance
Win2 - Secondary node in the cluster that will have SQL Server instance.
The laptop has 1 Qualcomm network adapter (generally used for connecting Lan cable) and a Broadcomm (wifi) adapter. I intend setting up three virtual adapters
First for regular communication
Second for Data (SQL Server Data to be stored on SCSI)
Third for HeartBit
Normally, (on my laptop) I connect to internet using Broadcomm (Wi-Fi) and want to ensure that whenever needed:
Run this lab even when Lan or wifi is NOT connected. If one of them is mandatory then even that could be the option.
I should be able to use internet within all VMs as well- though this is good to have requirement.
Internet needs to be available on laptop at least. Even if it is unavailable in VMs that is ok.
Now the actual problem.
I DON'T KNOW how many virtual internal/external/private switches to be
defined and assigned to individual VMs. What should be the IPs, Subnets, DNS, Gateways defined on those?
I was able to setup the stuff up-to certain extend and then it stopped working for unknown reasons. I have VMs ready. Next what should I do? Steps...
setup network adapters in each VM
setup DNS on DC
Add remaining 3 VMs in domain
Define Win1 and Win2 as cluster
Configure Target
Configure initiators and access the target
e. Install SQL Server
Is above correct?
My queries probably demands a separate article. But I have already referred many articles and couldn't figure it out so posting it here. I sincerely request your help!
PS – Even after disabling firewall (with and without having DNS setup) I am unable to ping VMs from each other.
Regards,
ThingToLearn
Thanks, Pravin

Hi,
You need create another guest vm as the NAT device, attach the NAT external to the Wifi adapter or cable adapter, then you can set all your vms in internal network
vswitch.
The related third party article:
Using Wireless with Hyper-V
http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx
Hope this helps.
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Failover Clusters Licesing in MS SQLServer 2008 R2 license delivered by SAP

Dear Experts,
I need to know if the MS SQL Server 2008 R2 Enterprise Edition license delivered by SAP include the rights to use the Failover Clusters Feature of MS Windows Server 2008 R2 Enterprise Edition for the DB Instance. And if so, how many nodes would be covered as such.
Best Regards,
Mohamed Awny
SAP NW Technology Consultant
Smart Consulting Solutions - SCS - Egypt

Hi Mohamed Awny
As per the SAP recommitted to use in the windows 2008 cluster environment you have to use two node clusters, further details you can check the installation guide in the sap Site https://service.sap.com/pam
Regards
Sriram

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Want to Buy SQL 2008/2012 standard edition to achieve Database failover

Hi Team,
We want to know exact part code details to procure 2 nos Sql 2008/2012 standard edition server to installed on "Window 2012 R2 Standard Edition, Factory installed, no media, 2 socket,2 VMs, No client" Server.
I have Access control system application (Main-Standby) on which we need Automatic database failover by using SQL Standard server. Application vendor has suggested us to procure 2 nos of Microsoft Sql 2008/2012 standard edition server.
If possible then please let me know exact part code details of Sql 2008 and 2012 standard edition server which doesn't have any issue to installed on above said server edition.
Thanks,
Vishal

Hi Vishal,
Unfortunately, we do not deal with part codes, I request you to check the below link as this is not the correct forum.
http://www.microsoft.com/en-in/server-cloud/products/sql-server/Support.aspx
Perhaps you could post you question on the SQL forum :
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards,
Mekh.

Windows 2008 failover clustering fails with Event ID 1205 1069 1558

I have a two nodes Windows 2008 and SQL 2008 cluster running in active\passive. I was restarting
my nodes after applying windows update then I received the following error message below within Failover Cluster Manager. I get errors with Event ID 1205 1069 1558 this happens every month .. Could someone help me on to find the root cause for
this issue how to check if it is an issue with network or Quorum drive ?

First, take a look at the 1069 event. This should point out which resource is failing.
Then, open a command prompt and run the command: cluster log /g
This will generate a cluster.log file that you can use to further troubleshoot this issue. The log file will be located in the C:\Windows\Cluster\Reports folder.
The cluster.log will be based on GMT time, so you may need to translate this to the local time zone in order to find the events you are looking for. Look for ERR or WARN messages and these should hopefully give you more insight as to why the resource is
failing.
Hope this helps.
Visit my blog about multi-site clustering

Build a SQL 2008 R2 Failover clustering

Similar Messages

Maybe you are looking for