Pinned topic Control the reboot sequence across several servers
I would like to hear if anyone has a good approach for, in a maintenance window, to control a restart sequence across several servers after patching.
My customer has a set of servers that are dependent on each other and the startup sequence is important to have the system working. In short terms this can be illustrated like.
Dependent servers are A, B and C
Dependendt services are L, M and N
Sequence could be like:
1) Stop service L on server C
1.1) Service has stopped
2) Restart server A
3) Verify that service M and N on server A is running
4) Restart server B and C
Is it possible to control status across servers? I can only think of one way - implementing each line in a separate task and then control the restarts using delays. All tasks should then be gathered in a single baseline.
All servers are windows servers and a single task (executed on a "parent" server) with several commands like "dos shutdown /m \\<computername> /r" and "dos sc \\<servername> stop <servicename>" is also an option.
Any best practices and good ideas are welcome, thanks in advance.
Re: Control the reboot sequence across several servers2012-04-24T15:01:09ZThis is the accepted answer. This is the accepted answer.There is currently an Action Sequencer aka "Run Book" that is available. It first requires that the API is installed Download API here.
Since this is not an official utility of TEM, send a note to Gerald email@example.com, the tool's creator, to ask for a copy.
There is also some current active discussions at IBM about how to better handle these types of situations. There may be some forth-coming developments on this front.
DanWaksman 270004TABF1 Post
Re: Control the reboot sequence across several servers2012-05-08T20:41:52ZThis is the accepted answer. This is the accepted answer.I was wondering the same thing myself, since certain servers have dependencies and need to be rebooted and available before others.
I have created a "Restart in 5 Minutes" Task and have tested it as part of a Baseline. The ActionScript is just:
You could potentially allow a Task like this within a Baseline to control the reboots rather than restarting as a Post-Action. Either multiple Tasks with different restart times can target machines by relevance, or you could build more logic into your ActionScript.
The one problem is that your Baseline will always be relevant if this Task is relevant. You may need to add this relevance too:
Anyone else have thoughts on this???
Re: Control the reboot sequence across several servers2012-06-06T00:34:41ZThis is the accepted answer. This is the accepted answer.We're going to be discussing the work we're doing to address automation/sequencing in a web-conference this Friday at 9am Pacific time. If you're interested in hearing what we're working on and giving us early feedback, we'd be happy to have you. You'll have to sign off on our Beta agreement, after which you'll be added to a developerworks group in which we discuss our ongoing development work.
Thread with a bit more info about the customer program.
MBARTOSH 2000002HB629 Posts
Re: Control the reboot sequence across several servers2014-07-15T23:01:17ZThis is the accepted answer. This is the accepted answer.
Has there been any more development on this topic?
Tim.Rice 110000PFYE26 Posts
Re: Control the reboot sequence across several servers2014-07-16T01:30:05ZThis is the accepted answer. This is the accepted answer.
gearoid 110000G7X91 Post
Re: Control the reboot sequence across several servers2014-07-16T08:44:08ZThis is the accepted answer. This is the accepted answer.
- MBARTOSH 2000002HB6
@Tim is correct here this is exaclty the type of use case that the Automation Plans in the Server Automation feature deal with.