It's bit Rube-Goldbergish:
You have a Domino client node, with a script that will back it up sitting on
the client.
What happens is:
        -you make sure dsmc sched is running on that (ie the normal file-system
client)
        -you make a TSM server schedule with action=command, object=that client
script
and the TSM server fires up the schedule,
        dsmc sched gets contacted,
        dsmc sched runs the client script for you.

Be aware dsmc is not very good about reporting errors if it gets them.
The error code will probably be in the dsmsched.log file, but "query events"
will probably say things are fine even if it failed.


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Patrick Sheehan
> Sent: Wednesday, June 06, 2001 12:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Schedule clients for backup
>
>
> Hello Everyone
>
>      I am configuring one TSM server to backup three Lotus Domino servers.
> I would like to do so with schedules. I understand I need to have
> domsel.cmd (command files) to run scheduled backups. My question is on the
> other servers (without TSM server but just the TDP for Domino client) I
> have the TSM scheduler running and the nodes are registered on the server,
> do they use the servers command file or does each one require a separate
> cmd file with the /ADSMNODE=othersevername on the server? I guess I'm
> missing how the clients call the cmd file and where they must reside. I do
> have a local client on the server working but the others don't appear to
> be. Any help would be appreciated.
>
> TIA
>
>
> Patrick
>