Eric, you are talking about the actual backupxx.log file created by
NTBACKUP, not the TSM dsmsched.log file.... correct?

The dsmsched.log file would not include the NTBACKUP output, which is
written to backupxx.log created by NTBACKUP. TSM has no control over the
operation of NTBACKUP (beyond launching the batch file that you have
written). Since it is NTBACKUP that is generating an inconsistent backup
log, Microsoft would be able to better answer this question for you. In my
own test cases using your batch file, both manual and scheduled backups
produced a detailed backup log file. I am sorry that I do not have a
better answer than this.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-23
19:21:28:

> That's where the backup log should be going.
> The problem I'm seeing is that when I have it run by the preschedulecmd
> the output is much different.  When manually run the full log was
> displayed, but when I run it with the preschedulecmd it did not show the
> file backup or success/failure of the backup.
>
> Thanks
> Eric
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Andrew Raibeck
> Sent: Wednesday, February 23, 2005 5:02 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: preschedulecmd question
>
> I am not an expert on using NTBACKUP, but it seems at least by default,
> the backup log gets put into a very deep directory structure under
> "Documents and Settings".
>
> When I tested your batch file, I found the log as follows:
>
> - Run batch file manually:
> C:\Documents and Settings\Administrator\Local Settings\Application
> Data\Microsoft\Windows NT\NTBackup\data
>
> - Run batch file through TSM client scheduler:
> C:\Documents and Settings\NetworkService\Local Settings\Application
> Data\Microsoft\Windows NT\NTBackup\data
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
> Raibeck/Tucson/IBM@IBMUS Internet e-mail: storman AT us.ibm DOT com
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-23
> 10:54:45:
>
> > Sorry about that I should have known better..
> > Batch file
> > =============================
> > rem   Remove old backup
> > Del D:\NTBACKUP\systemobjbkup.bkf
> >
> > rem   Backing up NT Systemobject
> > ntbackup backup systemstate /j "SystemState_Daily_Backup" /f
> > "D:\NTBACKUP\systemobjbkup.bkf" /v:yes /l:f /m COPY
> > ============================= The TSM service is running under the
> > Administrators account.
> >
> > Thanks
> > Eric
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
> > Of Andrew Raibeck
> > Sent: Wednesday, February 23, 2005 12:39 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: preschedulecmd question
> >
> >
> > It would help to know:
> >
> > - What your batch file looks like
> > - What the output looks like when the batch file is invoked manually
> > - What the output looks like when the batch file is invoked via
> > PRESCHEDULECMD
> >
> > While I do know know enough at this time to say for sure, I doubt that
>
> > the use of PRESCHEDULECMD itself has anything to do with the output
> > generated by ntbackup; rather, it is probably due to some difference
> > between the environment in which the batch file is run.
> >
> > Regards,
> >
> > Andy
> >
> > Andy Raibeck
> > IBM Software Group
> > Tivoli Storage Manager Client Development Internal Notes e-mail:
> > Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: storman AT us.ibm DOT com
> >
> > The only dumb question is the one that goes unasked.
> > The command line is your friend.
> > "Good enough" is the enemy of excellence.
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-23
> > 10:22:43:
> >
> > > Good Afternoon.
> > > I'm running with Win2K servers with TSM 5.2.2 and AIX 5.2 TSM 5.2.2
> > server.
> > > I have a batch file I'm running that runs NTBACKUP and the
> > > preschedulecmd does a great job.
> > > The question/problem I have is the log file(NTBACKUP log) that is
> > > generated is very different than if the batch is run outside of the
> > > preschedulecmd.
> > > Normally I have a full log that NTBACKUP produces(run from a
> > > scheduled task or on a command line) but when run with the
> > > "preschedulecmd" inside the dsm.opt file I have minimal to no real
> > output.
> > > In the DSM.OPT file I have the following for the preschedulecmd.
> > >
> > ----------------------------------------------------------------------
> > --
> > -------------
> > > preschedulecmd d:\NTBACKUP\SYSTEMSTATE_Backup.bat
> > >
> > ----------------------------------------------------------------------
> > --
> > --------------
> > >
> > > Do I need to add anything different?  I've read the manuals and it
> > > appears you only need to have quotes if there are "blanks" in the
> > command.
> > >
> > > Have a Great Day,
> > > Eric Jones
> > > > *  eric.j.jones AT lmco DOT com
> > > > *:   607-751-4133
> > > Cell : 607-972-7621