At one point there was an issue with having a TDP which was not unicode and a Windows backup which was unicode connecting under the same node name. As a result it was recommended not to use the same node name for TDP backups if they were on windows systems where the windows backup was unicode.
Do you know if this is still an issue? I know may people who still keep the TDP backups under a seperate node name. I still due this mainly because we had to do that at one time. Bill Boyer <[EMAIL PROTECTED]> wrote: Is there a specific reason you have a separate scheduler service for the TDP backups? You could schedule your TDP backups via the standard nodename for the server and that service. This is a positive in a couple ways: 1. Only 1 scheduler service on the client 2. The backups are single-streamed since TSM will only run 1 schedule at a time. Your filesystem backups won't interfer with the TDP backups. Just schedule both backups through the same nodename. The TDP backups are an ACTION=COMMAND schedule. The script file that gets executed on the client runs the TDPEXCC.EXE. There is a DSM.OPT file specified for the TDP agent. When the TDP backup starts it connects back up to TSM server under that nodename. This TDP backup doesn't have anything to do with the nodename specified in the scheduler service. And since the TDP agents now participate in TSM version and each has their own filespace names, you don't even need to have a separate nodename for TDP backups. With include statements you can specify the management class so you don't need a separate domain/nodename for that. Except for those TDP agents that don't do versioning...like Oracle. Bill Boyer "Some days you are the bug, some days you are the windshield." - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Levi, Ralph Sent: Thursday, September 02, 2004 3:47 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange 5.5 Also note that the TDP has its own scheduler task that reads a dsm.opt file from the tdpexchange subdirectory. This scheduler task is in addition to the regular tsm scheduler. Ralph -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: September 02, 2004 3:31 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange 5.5 Jason, It sounds like you set up the schedule definition incorrectly. It needs to be an COMMAND type schedule that specifies a batch file on the Exchange server machine that launches Data Protection for Exchange. There are sample batch files shipped with Data Protection for Exchange. If you look at the Data Protection for Exchange User's Guide, it walks you through setting up a scheduled Data Protection for Exchange backup. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" wrote on 09/02/2004 02:27:43 PM: > I am trying to configure the TDP for exchange to be able to backup my > Exchange 5.5 Directory and Information store fully and on a daily basis. > Here is what I have in my dsm.opt (for the tdpexchange) but when I try to > schedule a job it doesn't look like it reads my dsm.opt and it does an > incremental on the entire system. > > [data clipped from original append] > > I have the TSM BAclient and the TDP for exchange installed on the system. I > setup my BA dsm.opt correctly and I am able to backup the system files but I > am having problems backing up the exchange through the client. > > Why is this happening? > --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
