Thanks to all for the pointers --

Del, the magic was your note about /EXCSERVER (along with getting the
resources for server one back on server one -- sigh).

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: Monday, June 14, 2004 11:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: need help with ms-exchange 2003 cluster backups

Tom,

Can you please get the answers to these questions
from your people?

1. What do you see in the TDPEXC.LOG file?

2. What errors messages are you getting?
   Check the output the TDPEXC.LOG file and the
   output of the TDPEXCC command?

3. Does the userid that owns the Windows Scheduler
   Service have enough authority to back up
   the Exchange server and access the Windows registry?

One thing to keep in mind for a cluster setup is that
you should only be running the scheduled backup on the
machine that currently has the running instance of the
Exchange virtual server. When running with the TSM BA
client scheduler this is accomplished by creating
a cluster resource for the TSM BA scheduler that
is dependant on the Exchange virtual server cluster resource.

Also, when running in a cluster, you need to run
specify the "/EXCSERVER=virt-exch-server-name" option,
where "virt-exch-server-name" is the name of your
Exchange virtual server.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/14/2004
11:15:17 AM:

> I know it's not much to go on -- that's what I'm getting from MY
people
> :-(
>
> At the server side, I see no connect from the cluster, so I'm making
the
> assumption that the Windows 2003 scheduling process (whatever it is)
> isn't actually working (Is there anything besides the 'at' command? I
> haven't looked at this aspect of Windows since NT 3.51 . . .)
>
> Tom Kauffman
> NIBCO, Inc