Make sure that the TSM scheduler service runs under an account that is an
Exchange administrator or so, not just a local system account. Prior to bring
the resource online, run a CLI backup like 'tdpexcc backup full *
/tsmoptfile=.. /tsmpassword=... /excserver=...'. The steps are as usually good
described in the redbook of TSM & Exchange
What are the dependent resources for the TDP scheduler resource that should be
used. In the redbook they say:
-Microsoft Exchange Directory
-Microsoft Exchange Information store
But only the second resource still exists in Exchange2000, so I only took the
Information Store as a dependent resource. Must other resources be added?
regards,
Kurt
------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote:
------------------------
>This has happened to me a couple of times before. Usually it was do to an
>error in the dsmcutil batch files used to create the services, like a typo
>in the cluster name especially. I would uninstall the service on each
>node, double check your syntax, options files, etc. and try going through
>it again. Restart the services on each node a couple of times to verify
>they are working correctly before trying to add the service into the
>cluster again.
>
>You can also change the properties of that service so it doesn't cause an
>entire group failover when it fails, at least until you get things working
>correctly.
>
>______________________________
>John Monahan
>Senior Consultant Enterprise Solutions
>Computech Resources, Inc.
>Office: 952-833-0930 ext 109
>Cell: 952-221-6938
>http://www.compures.com
>
>
>
>
> Henrry Aranda
> To
> Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
> Dist Stor cc
> Manager"
> Continuous cluster failovers
> configuring TDP Exchange Scheduler
>
> 05/21/2003 06:27
> PM
>
>
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
>
>
>
>Hi,
>I have the following environment:
>XSeries machine with Windows 2000 Server running TSM server v.4.2.1.15
>attached to an IBM LTO 3583
>Two Xseries machines with Windows 2000 Advanced Server running MSCS
>Active/Active, Exchange 2000 Server, TSM B/A Client v.5.1.5.7 and TDP for
>Exchange v.5.1.5.0
>
>After I created the TDP for Exchange Scheduler resource in the Cluster
>Administrator, I bring the resource online, but after a couple of minutes
>the resource goes offline. After that the resource tries to go online five
>times, It causes a cluster failover. The same situation occurs in the other
>exchange virtual until the resource causes a fail back. The problem
>continues repeatedly until I delete the resource.
>I got the following error messages in the dsierror.log:
>05/21/2003 03:22:14 sessOpen: Error 137 from signon authentication.
>05/21/2003 03:22:14 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
>05/21/2003 03:22:14 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
>05/21/2003 03:22:34 sessOpen: Error 137 from signon authentication.
>05/21/2003 03:22:34 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
>05/21/2003 03:22:34 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
>
>When I check the registry I see the password for both virtual exc nodes.
>I am following the installation procedure exactly. Please help me! this
>cluster is really important, the customer needs to protect it.
>
>Thanks / Regards.
>Henry Aranda
>
>_________________________________________________________________
>The new MSN 8: advanced junk mail protection and 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
|
