.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
MarieAdela
Imran Ghani
Post New Web Links

Failover Cluster Question about resource startup and shutdown order

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :
 

Is there a way to change the order of how the Server name, Disk drives, and other Resources go offline to be moved to another node?

 

Server Name:

  • Name: TestSQL08PRD

Disk Drives:

  • Data_Drive
  • Logs_Drive
  • Backup_Drive

Other Resources:

  • GxClusPlugIn (TestSQL08PRD)(Instanace001)
  • SQL Server (TestSQL08INS)
  • SQL Server Agent (TestSQL08INS)

They go offline from bottom up.


View Complete Post


More Related Resource Links

The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. S

  
Hello, I have a node of 2 servers of Win 2008 R2 Enterprise and trying to install a 2nd instance in a SQL 2008 R2 Cluster. I had SQL_INSTANCE2 previously installed that I removed from the two nodes. Now when I attempt to install it again from scratch, in setup GUI where I specify the SQL Server Network Name and enter the previously entered name "Server02", I get a failure in the setup with the following error message: "The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. Specify a different failover cluster instance name." How do I fix this problem, I don't want to enter a new name like "Server03" in order to proceed with the setup, because when I do enter "Server03" the setup does continue without an error message. So what am I missing? Do I have to ask the DNS administrator to see if there's an A record for "Server03" and have him delete it so that the setup works? Or the fix is by doing something else? I would appreciate any help. Thank you  

[amateur question] Why can't I use MSCS cluster ip address for SQL 2008 failover cluster?

  
Good day! Recently, I was tasked to set up SQL 2008 failover cluster on both Windows 2003 Server (Enterprise ed). Everything was set up perfectly, failover work on both cluster nodes. Now the question is my boss asked me a very basic question on which I'm unable to give him a detailed explanation on why can't used only a single IP Address for both MSCS cluster and SQL failover cluster? I replied back him (amateurish) its because of the requirement stated on SQL 2008 failover cluster. I can't even be allowed to install when I keyed in the already used IP Address for MSCS. Can any folks enlighten me on these? Best Regards

SQL Server Agent not listed as cluster resource

  
Hello everyone, thanks for any help on this issue.  I have recently installed SQL 2008 R2 on a Server 2008 R2 machine cluster.  We ran the advanced cluster prep and completion.  I have SQL Server up and running properly and failing over between nodes.  In the failover cluster manager, when I select SQL Server, I do not have the SQL Server Agent listed under other resources.  When I try to start the Agent from the SQL Configuration Manager it fails with an event 103 and I've found several notes on this error but I am figuring the root issue is that there isn't a cluster resource for the Agent. Is it possible to create the resource for the Agent? I have run a repair and I have tried to use add a resource, generic service, sql agent but it fails when I attempt to bring it online. Thanks again for any help on this. Mike

SQL server 2008 failover cluster install

  
Hello all, Looking for the definitive answer with supporting documentation (link). Does a SQL server 2008 cluster have to be installed as or run as a domain service account or can local accounts be used?  I looked for a document that stated yes or no and could not find one. If anyone can provide info it would be much appreciated. Have all ready looked at these 2 links of interest. http://msdn.microsoft.com/en-us/library/ms143504.aspx#Service_SID http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx Thanks in advance,  

why would a dba do a manual failover on a cluster

  
Why would a dba do manual failover because of high cpu?  I got no answer from dba, but cpu did improve from 85 to 60, then down to about 40%.  My thought is there was parameter sniffing problem and clear proc cache from failover fixed the problem, recompiling all the procs is why cpu high at first after failover?  Until cpp started spiking to 80 it was under 50% all day.

Validating cluster resource: SQL Server and SQL Server Agent services

  
SQL Server 2008 R2 installed on a Windows Server 2008 R2 2-node cluster. Cluster validation wizard warns for SQL Server and SQL Server Agent services: This resource is configured to run in a separate monitor. By default, resources are configured to run in a shared monitor. This setting can be changed manually to keep it from affecting or being affected by other resources. It can also be set automatically by the failover cluster. If a resource fails it will be restarted in a separate monitor to try to reduce the impact on other resources if it fails again. This value can be changed by opening the resource properties and selecting the 'Advanced Policies' tab. There is a check-box 'run this resource in a separate Resource Monitor'. "Should" SQL Server and SQL Server Agent services run in shared (default) or separate monitors in this environment?

Validating cluster resource: SQL Server and SQL Server Agent services

  
SQL Server 2008 R2 installed on a Windows Server 2008 R2 2-node cluster. Cluster validation wizard warns for SQL Server and SQL Server Agent services: This resource is configured to run in a separate monitor. By default, resources are configured to run in a shared monitor. This setting can be changed manually to keep it from affecting or being affected by other resources. It can also be set automatically by the failover cluster. If a resource fails it will be restarted in a separate monitor to try to reduce the impact on other resources if it fails again. This value can be changed by opening the resource properties and selecting the 'Advanced Policies' tab. There is a check-box 'run this resource in a separate Resource Monitor'. "Should" SQL Server and SQL Server Agent services run in shared (default) or separate monitors in this environment?

Issues with Kerberos and SQL Server failover-cluster

  
I have a dual-instance SQL 2008 SP1 2-node Failover-cluster running on Server 2008 x64 SP2. SPNs have been manually created in AD for the service account running SQL Server (on both nodes).When the cluster nodes first boot up and the virtual groups come online, everything works flawlessly. I have linked server connections set up between the two instances of SQL server, with one instance running on each node. I can successfully make linked server connections from one instance to another from a third client PC, indicating Kerberos is working successfully, which is great!Problem is, this all stops working as soon as one of the SQL cluster groups fails over (or is taken offline, and moved to the other node). As soon as this happens, all authentications seems to fall back to NTLM. Of course, running both instances on the same physical node will work since Kerberos is not required for this. But as soon as an instance moves to another node - kerberos seems to be permenantly broken for that instance, even if moved back to its original node, until both nodes are rebooted again.One thing to note - the service account running SQL server is not a domain admin. This of course prevents SQL server from auto-registering the SPN upon startup and generates the following in the SQL log: "The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL

SQL server 2008R2 install on a server 2008 R2 failover cluster. Other resources won't failover to o

  
As the subject says, I've built a fresh install w2k8r2 and sql2k8r2 failover cluster. Sql works fine on the primary node, but when I test a failover it breaks. Specifically, if I were to stop the node1 cluster service (causing the cluster to switch to node2), windows changes the cluster DNS appropriatly and moves the shared storage just fine, but sql server doesn't failover.  Server Name, Disk Drives and Other Resources all go offline. I've verified that the advanced policies of the server name, IP, cluster drives all have both nodes checked as possible owners However, Other resources only lists node1 as a possible owner and there appears to be no way to add node2.  Under the Other resources, SQL Server and SQL Server Agent are listed. I'm sorta stumped, I've been combing the forums and have found similar issues, but nothing seems to explain why the two resources won't failover.

SQL Server 2005 Cluster failover issue

  
Hi All, I'm fequently experience Cluster failover issue. The cluster tries to failover and it fails back. Because of this the SQL server is getting restarted and this is a bugging issue during business hours. The following are the System event logs, Cluster resource 'SQL Server' in Resource Group 'Production' failed. The SQL Server Agent (MSSQLSERVER) service was successfully sent a stop control. The SQL Server Agent (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a stop control. The SQL Server (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a start control. The SQL Server (MSSQLSERVER) service entered the running state. The Cluster Service brought the Resource Group "Production" online.    The following are the application event logs, The client was unable to reuse a session with SPID 131, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired [sqsrvres] OnlineThread: QP is not online. The client was unable

Sharepoint 2010 Resource Justification on VMWare cluster

  

Hi eveyrone,

I am a sharepoint architect for a really big client hosting roughly 20 sharepoint boxes (some 2007/2010) in throughout various clusters.  In the near future, all sharepoint boxes will be upgraded to 2010.  There is not more annoying than a list of tasks that need to be attended to on an underspec sharepoint server. 

I have been having some difficulty justifying Microsoft Min specs for numerous sharepoint 2010 small/med farms. 

Has anyone else experienced a similar problem?  If so, how was it dealt with?  If anyone can help me out, I would greatly appreciate it. 

b


SQL server 2008 cluster install error - The resource failed to come online due to the failure of o

  

Hi ,

I ran into the following error when trying to install sql server 2008 cluster (node 1) on windows 2008

The resource failed to come online due to the failure of one or more provider resources. (Exception from HRESULT: 0x80071736)

Any insight on this issue is greatly appreciated

 

Ping

 

 


Intermittent unavailability of an instance in a failover cluster while a standby node is offline.

  

Hi everyone.

I've got a small failover cluster that I run for the websites my company has. During a RAM upgrade of the standby server, our websites started to show errors about not being able to access the database server. I verified that the instance was indeed up and the server accessable via remote desktop.
I also tried a SQL connection to it and it worked, but that might have been after it became available again.

This happened on and off until we were able to roll back the hardware changes that were in progress on the standby server and we were able to bring it back up.

There was nothing of interest in the SQL Server log, but there is a continous log for the whole duration of the problem, so there was no restart of the SQL Server service. The event viewer is of more interest, since it shows events relating to the heartbeat network card, but I don't know how that would affect the availability of the server, since the standby node is offline. I'd appreciate any help you can provide, it's not very redundant if it also depends on the standby server being up. :)

Here are the event logs from the time of the problem:

Level Date and Time Source Event ID Task Category
Information 4/23/2010 10:55:56 AM Microsoft-Wind

DataTable and it's Gridview - A Column Order Question

  

Well, I've been developing with gridviews for quite some time now.  Just recently I came across a situation that has me stumped.  Here's how the gridview has been working for me.

 

1.      A stored procedure from the database is called (three parameters are passed (reporttype, name, location)

2.     The data is retrieved using the SqlDataAdapter to fill a Datatable

3.     The gridview DOES NOT AUTOGENERATE COLUMNS

4.     Columns are created programmatically as it reads the DataTable results (headertext, datafield, and dataformatstring are set at runtime)

5.     The Gridview triggers the databind event - and voila it works.

 

My dilemma is this:  the stored procedure (that I haven't developed) returns a various set of columns and column order.  I have one report type that does the following:

 

ReportType 1:  column orders returned in the following order when running directly in SQL

            col B, col C, col D, col E, col A

 

when I run the report through my gridview, the column order is as follows:

          &nb

SQL Server 2008 A/P Cluster Does not Failover

  

Hi,

I have a SQL Server 2008 Enterprise Edition A/P cluster Server on Windows 2008. Recently One of the Clustered Disks Went OFFLINE. The SQL Resource which has Dependency on the clustered Disk also went offline. Shouldnt a Failover of the resources be happening to the second node, if there is a failure in the first node? Are there any settings which need to altered?

Thanks,


SQL SERVER 2008 sp1 FAILOVER CLUSTER INSTALLATION WITH SLIPSTREAM

  

Hi, I have successfully installed the slip stream SQL SERVER 2008 Enterprise  sp1  on the two node fail over cluster.Now i need to implement the 2 node failover cluster installation again with the standard  edition of SQL SERVER 2008 sp1.

My question is do i  need to go for a slipstream installation with  standard edition also?


one question about sql server cluster

  
Windows 2003 + SQL Server 2000 Cluster. Cluster means when one database server is down,the other node will take over the responsibility.. Suppose that the first node is crash,and we can't startup it. Can I remove the cluster information and add another server into the cluster? How about in SQLServer 2005,and SQLServer 2008?
If you haven't all the things you want,be grateful for the things you don't have that you didn't want.
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend