| Author |
Message |
Darryl
Guest
|
 Posted:
Thu Oct 27, 2005 4:50 pm Post subject:
Scheduled Tasks in W3K Cluster |
|
|
As I understand it, to make scheduled tasks "cluster aware" in W2K
Advanced, you need to edit the registry, use a Generic Resource, and it
still isn't perfect in that:
a) failover copies the tasks to Node B, but failback leaves the tasks
active on Node B, and they simply fail because the shared disk resource
is no longer available, and
b) ALL tasks get copied...you can't specify tasks that you DON'T want
to be shared/copied.
c) no wizard to do all this.
Are any of these 3 problems addressed in W3K?
Is there a command-line method to enable/disable scheduled tasks? |
|
| Back to top |
|
 |
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Fri Oct 28, 2005 12:50 am Post subject:
Re: Scheduled Tasks in W3K Cluster |
|
|
NO need. What I do is use the same scheduled script for all nodes. First
line is IF EXISTS "x:\cluster\path" - where x:\cluster\path is a path that
the controlling node would own. All other nodes will fail and you can EXIT
Works great!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Darryl" <DarrylJ@yahoo.com> wrote in message
news:1130422912.249177.27100@g47g2000cwa.googlegroups.com...
| Quote: | As I understand it, to make scheduled tasks "cluster aware" in W2K
Advanced, you need to edit the registry, use a Generic Resource, and it
still isn't perfect in that:
a) failover copies the tasks to Node B, but failback leaves the tasks
active on Node B, and they simply fail because the shared disk resource
is no longer available, and
b) ALL tasks get copied...you can't specify tasks that you DON'T want
to be shared/copied.
c) no wizard to do all this.
Are any of these 3 problems addressed in W3K?
Is there a command-line method to enable/disable scheduled tasks?
|
|
|
| Back to top |
|
|
Paul Kelly
Guest
|
| Posted:
Sat Oct 29, 2005 8:50 pm Post subject:
Re: Scheduled Tasks in W3K Cluster |
|
|
The only thing worth bearing in mind is the user context te task runs in.
It's easy to get a task following a Virtual Server, simply use the Volume
Shadow Copy Service resource type, but this runs under the Cluster Service
account and so won't have access to the network (if your script requires
it).
Paul
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:O$Bnvb02FHA.268@TK2MSFTNGP10.phx.gbl...
| Quote: | NO need. What I do is use the same scheduled script for all nodes. First
line is IF EXISTS "x:\cluster\path" - where x:\cluster\path is a path that
the controlling node would own. All other nodes will fail and you can EXIT
Works great!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Darryl" <DarrylJ@yahoo.com> wrote in message
news:1130422912.249177.27100@g47g2000cwa.googlegroups.com...
As I understand it, to make scheduled tasks "cluster aware" in W2K
Advanced, you need to edit the registry, use a Generic Resource, and it
still isn't perfect in that:
a) failover copies the tasks to Node B, but failback leaves the tasks
active on Node B, and they simply fail because the shared disk resource
is no longer available, and
b) ALL tasks get copied...you can't specify tasks that you DON'T want
to be shared/copied.
c) no wizard to do all this.
Are any of these 3 problems addressed in W3K?
Is there a command-line method to enable/disable scheduled tasks?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in