Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cgunner
Yak Posting Veteran
95 Posts |
Posted - 2005-02-02 : 12:01:08
|
| I was wondering if anyone knows of a way to automate re-boots of both nodes in a cluster gracefully. I would like all the resources on node A to fail over to node B. Node A would than re-boot. Once Node A came up, the all resources would fail to node A and B would re-boot. Once both nodes have re-booted, the resources would fail back to their production state. I know this may be asking allot but as everyone knows Windows needs a re-boot every once in awhile to work properly. |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-02-02 : 13:19:08
|
| Yikes!There may be a way to automate this with Windows Scripting, but I suspect that it's going to be hella complicated. We generally never have to reboot our cluster, but when we do we schedule some time in the wee hours of the morning and do it manually. If something fails with your reboot, you will not know about it until waaaay too late methinks.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-02-02 : 13:50:50
|
quote: I know this may be asking allot but as everyone knows Windows needs a re-boot every once in awhile to work properly.
Rebooting SQL Server is not a good idea for performance reasons. You typically only reboot when absolutely necessary whether it be to fix a problem or maintenance. Automating reboots on SQL Server just isn't needed. Our servers typically are online for months and months at a time. Almost always the reason for a reboot has been for service pack installations and other software type maintenance.Tara |
 |
|
|
cgunner
Yak Posting Veteran
95 Posts |
Posted - 2005-02-02 : 14:13:25
|
| We also manually re-boot during our maintenance window. We have found that doing so cuts our problems dramatically. If there is a failure, our monitoring system would pick up on it if the cluster did not come back online. I know that I can kick over the server with shutdown.exe in a staggered schedule but that is not too graceful. Just wondering if anyone else out there was using a 3rd party utility to move resources. |
 |
|
|
|
|
|