Joshua,

When you say you had the Cluster Admin
"launch the Exchange agent process"...
I assume you mean launch the base client
scheduler? ...since you should not launch
Data Protection for Exchange itself.
The scheduler is a Cluster Resource...dependant on the
Exchange Server Cluster Resource that runs
a scheduled batch file that actually runs DP for Exchange.

Please refer to the User's Guide for
Data Protection for Exchange. There is an
appendix dedicated to explaining this
in detail. It is tricky and if you deviate
from those steps, things may not work correctly.

It is Appendix C in the 2.2 version of the book.
It is Appendix A in the 5.1.5 version of the book.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Never cut what can be untied.
- Commit yourself to constant improvement.

=========================================================

> I installed the TSM Exchange agent in a clustered Windows 2000
> environment.  Everything worked well until I tried to have the Cluster
> Administrator launch the Exchange agent process.  When we started the
> process it caused the Exchange server to bounce back and forth between
> nodes.  This is the command that I used to install the service:
>
> dsmcutil inst /name:"TDP forExchange Scheduler" /node:xxxx
> /password:yyyy /autostart:no  /optfile:"C:\Program
> Files\Tivoli\TSM\TDPExchange\dsm.opt" /startnow:no /clusternode:yes
>
> But after looking at "Using TSM in a Clustered Windows NT Environment
> Redbook" I found that there is a /group option as well.  Should I use
> this flag for an Exchange agent or is it just for the backup-archive
> client?