Re: TSM and TDP
2003-05-06 22:30:49
You don't necessarily need 2 scheduler services. Your TDP backups are
ACTION=COMMAND schedules. What that script file does and how it connects
back to TSM is independant of the name used to schedule it. The only thing
you lose is seeing an association for the TDP nodename on TSM. This way also
you won't be running 2 schedules on that box at the same time. With 2
schedulers you could actually have the B/A client backup running at the same
time as the TDP backup. On some of my servers I schedule the TDP agent
backups using the same scheduler service. I have one DB2 box that has 4
instances running on it. I have a NODENAME for each instance, but I schedule
only 1 backup script. The script changes between instances and ends up
connecting back to the server as 4 different nodenames that the one I used
to kick off the schedule/script.
Your call. Either way works.
Bill Boyer
DSS, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Neilson Lui
Sent: Tuesday, May 06, 2003 9:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM and TDP
Del,
if we are going to use separate NODENAMEs, then we would need to put
up two schedulers. Do i need to assign two separate TCPCLIENTPORT for the
schedulers, that is, 1501 and 1502. ( assuming i'm using schedmode =
prompted )
Thanks
Del Hoobler
<[email protected] To: ADSM-L AT VM.MARIST DOT EDU
BM.COM> cc:
Sent by: Subject: Re: TSM and TDP
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
05/06/2003
07:41 PM
Please
respond to
"ADSM: Dist
Stor Manager"
Neilson,
You do not have to use separate NODENAMEs, but I
recommend it. It makes it easier for a number of
things like scheduling and data management.
Del
----------------------------------------------------
> Do i have to define two client nodes on the TSM server, for a server
using
> TSM backup client and TDP for SQL client ? Or i can just merge the
dsm.opt
> for both TSM backup and TDP for SQL ?
|
|
|