Re: Scheduling task service with failover
- From: mikeros@xxxxxxxxxxxxxxxxxxxx (Mike Rosado [MSFT])
- Date: Thu, 01 Dec 2005 14:22:52 GMT
Phil,
The Task Scheduler resource would actually have to be active on the node
the task is running on. You could try creating like 2 separate groups,
each containing a Physical Disk, Network Name, IP Address and Task
Scheduler resources. Then have one group active on one node and the other
group active on the other node. Hence making it an Active/Active cluster
and see if the task run as you would like them to run.
--------------------
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>
-----Original Message-----
> From: <PhilG@xxxxxxxxxxxxxxxx>
> Subject: Re: Scheduling task service with failover
> Date: Wed, 30 Nov 2005 09:26:10 -0800
>
> Thanks it works ! Now, let's say we want to run tasks on each node
wether or
> not it is the active node. Is it possible ? (And still having jobs
> specifically scheduled for failover like asked earlier).
>
> "Mike Rosado [MSFT]" wrote:
>
> > Hi Phil,
> >
> > Many Generic Services have registry values that are outside the cluster
> > database (registry hive). In these cases, it is necessary to sync the
> > registry keys between the nodes for consistency, and modify the
registry so
> > that common information is available to both nodes.
> >
> > In Windows 2000 Cluster we located the registry keys, modified them so
that
> > the shared job information is stored on the shared disk. Then added
the
> > registry keys to the Registry Replication properties for the Generic
> > Service resource. This should still work the same way on a Windows
2003
> > Cluster.
> >
> > The following steps worked:
> >
> > 1. The scheduled job information is located in c:\%systemroon%\tasks
> > subdirectory.
> >
> > - create a tasks directory on the shared disk
> >
> > 2. Modify the following registry key so that the tasks folder location
is
> > pointed to the tasks subdirectory on the shared disk.
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent
> >
> > This key has the following value:
> > TasksFolder reg_expand_sz %SystemRoot%\Tasks (change this
> > path to task directory on the shared disk)
> >
> > 3. Add "software\microsoft\schedulingagent" (without the quotes) to
the
> > Registry Replication tab for the Generic Service properties.
> >
> > NOTE: The previous customer we helped get this working was performing
the
> > work and test from a terminal server session and the jobs were
initially
> > failing. We had him log off and back on (see KB232276) and then the
jobs
> > worked as expected.
> >
> > http://support.microsoft.com/KB/232276
> >
> > NOTE: The security credentials for each job are contained in the
Protected
> > Storage Database on the local node and not with the job. So in order
for a
> > job to work on both nodes we need to refresh the credentials of the job
on
> > each node. To do that, create the job on first node, set the
credentials.
> > Move the Generic Service resource to the 2nd node and enter the
credentials
> > for the job again. This issue is discussed in the following KB:
> >
> > 317529 - Scheduled Task Does Not Run When You Push It to Another
Computer
> > http://support.microsoft.com/KB/317529
> >
> > --------------------
> > Hope this helps,
> > Mike Rosado
> > Windows 2000 MCSE + MCDBA
> > Microsoft Enterprise Platform Support
> > Windows NT/2000/2003 Cluster Technologies
> >
> > ====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > ====================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > <http://www.microsoft.com/info/cpyright.htm>
> >
> > -----Original Message-----
> > > From: <PhilG@xxxxxxxxxxxxxxxx>
> > > Subject: Re: Scheduling task service with failover
> > > Date: Wed, 30 Nov 2005 04:51:09 -0800
> > >
> > > Ok for the script location, but what about the configuration of the
> > resource
> > > (task scheduler service).
> > >
> > > Thanks for your help.
> > >
> > > "Rodney R. Fournier [MVP]" wrote:
> > >
> > > > Store the script on the shared disk.
> > > >
> > > > Cheers,
> > > >
> > > > Rod
> > > >
> > > > MVP - Windows Server - Clustering
> > > > http://www.nw-america.com - Clustering Website
> > > > http://www.msmvps.com/clustering - Blog
> > > > http://www.clusterhelp.com - Cluster Training
> > > >
> > > >
> > > > "Phil" <PhilG@xxxxxxxxxxxxxxxx> wrote in message
> > > > news:6505704B-AB11-4BBB-B00F-9B4C14611083@xxxxxxxxxxxxxxxx
> > > > > We would like to schedule a task that run only on the active node:
> > > > > Do we have to create a new resource "generic service" containing
> > "task
> > > > > scheduler windows service" and create the same task on both nodes
?
> > > > > Where do we have to store the script launched by the scheduled
task ?
> > > >
> > > >
> > > >
> > >
> >
> >
>
.
- Follow-Ups:
- Re: Scheduling task service with failover
- From: Phil
- Re: Scheduling task service with failover
- References:
- Re: Scheduling task service with failover
- From: Rodney R. Fournier [MVP]
- Re: Scheduling task service with failover
- From: Mike Rosado [MSFT]
- Re: Scheduling task service with failover
- From: Phil
- Re: Scheduling task service with failover
- Prev by Date: RE: Windows Shadow Copies on Cluster-Disks not working
- Next by Date: RE: HCL a must?
- Previous by thread: Re: Scheduling task service with failover
- Next by thread: Re: Scheduling task service with failover
- Index(es):
Relevant Pages
|
