|
| |||||||||
| Tags: asap, cluster, node, shutdown |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| Help needed ASAP; 2 node cluster shutdown
OK, long story short. I don't know what I am doing with cluster, nodes needed rebooting but didn't even know about the necessity to do graceful shutdown of services (I know!!) I couldn't log in remotely so asked someone else to restart, don't know what happened but both servers are shutdown. It is a file store no exchange or sql thankfully but is the main file store area. I am not in the office yet to restart but I am now panicing as I don't know how they will restart and the implication of my royal mess up and basically how on earth do I fix it! |
|
#2
| |||
| |||
| Re: Help needed ASAP; 2 node cluster shutdown
server 2003 cluster by the way |
|
#3
| |||
| |||
| Re: Help needed ASAP; 2 node cluster shutdown
Start the last server shutdown first. Resources on one node will move (actually failover) to any available node when the other server is shutdown. There a difference betwenn MOVE and FAILOVER. When you have a choice, always MOVE or TAKE OFFLINE, don't rely on a failure mode action. Hopefully the person doing the shutdown waited a bit between shutdowns. The process that worked for me every time was...The goal is to know where the Cluster Group was so it can start first. 1) move all groups to one server (example - move all resource groups to SvrA, SvrB is now empty). 2) shutdown the "empty" server SvrB. 3) Once SvrB is shutdown then shutdown SvrA ...........some time between.................. 4) Start up SvrA 5) Wait for SvrA to start (All resources come online) 6) Start up Svr B 7) Move resource groups to desired servers As long as the cluster knows where it left off, it should know where to pick up from. You should always move groups to the last node to be shutdown manually. Never "force" a resource group to move by a shutdown. It's more gracefull that way and you know exactly what node your resources were on at shutdown. "shambles" <shambles.3tal7b@DoNotSpam.com> wrote in message news:shambles.3tal7b@DoNotSpam.com... > > OK, long story short. I don't know what I am doing with cluster, nodes > needed rebooting but didn't even know about the necessity to do graceful > shutdown of services (I know!!) > I couldn't log in remotely so asked someone else to restart, don't know > what happened but both servers are shutdown. > It is a file store no exchange or sql thankfully but is the main file > store area. > I am not in the office yet to restart but I am now panicing as I don't > know how they will restart and the implication of my royal mess up and > basically how on earth do I fix it! > > > -- > shambles > ------------------------------------------------------------------------ > shambles's Profile: http://forums.techarena.in/members/103506.htm > View this thread: http://forums.techarena.in/server-cluster/1192334.htm > > http://forums.techarena.in > |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "Help needed ASAP; 2 node cluster shutdown" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Live Migration of Failover Cluster Node (SQL) causes cluster halt | Mr. Joe | Windows Server Help | 1 | 21-05-2011 01:41 AM |
| New cluster - fail to add node 2 to the cluster, Error 0x800706ba: The RPC server is unavailable | stepws | Windows Server Help | 1 | 23-04-2011 07:14 PM |
| New node in cluster cannot see chared quorum | msnews.microsoft.com | Windows Server Help | 2 | 12-06-2008 05:33 AM |
| Unable to add new node to existing cluster | NG | Windows Server Help | 2 | 26-07-2007 06:51 PM |
| cluster cannot failover at 2 node | AA | Windows Server Help | 1 | 27-07-2005 09:52 PM |