The problem with Win2K is that when you backup the "SYSTEMOBJECT", it backs everything up each time you run a backup. We backup the servers nightly and need to keep all data for a minimum of 90 days(including the system object backup). I had only ever backed up UNIX machines so I never had this problem until recently. With the NTBACKUP you can backup to a single file then have TSM backup that file so 1 file is backed up to TSM instead of 1900+. The amount of data does not change but the number of files does to the database.
Eric -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Steve Schaub Sent: Thursday, February 17, 2005 11:15 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Question on the preschedulecmd All, Maybe I missed the beginning of this thread, but I'm curious as to the advantage of scripting the ntbackup over using the built-in tsm client backup of systemobject/systemstate/systemservice? Does this help DR in some way? -steve -----Original Message----- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005 4:46 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Question on the preschedulecmd From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Eric J >I'm at the point where I've tested backing up the SYSTEM STATE >with NTBACKUP, having TSM backup the drives and exclude the >SYSTEM OBJECT, then rebuild the system, restore with TSM and >use NTBACKUP to restore the SYSTEM STATE. I have a batch >file to kick off NTBACKUP for the SYSTEM STATE backup and want >to use the "preschedulecmd" to run this before TSM scans for >changed files and does the scheduled backup. I need to make >sure the batch file completes before TSM does the backup. >Would there be any situation that TSM might start backing up >before the prescheduledcmd completes? A PRESCHEDCMD batch file must complete successfully (with RC=0) before the backup will happen; if a non-zero return code comes up, or the batch file hangs for any reason, the backup will not happen. What some have had better luck with is running the NTBACKUP batch file as a POSTSCHEDCMD. If the NTBACKUP hangs or fails (which happens once in a while), using POSTSCHEDCMD will not prevent the backup from completing. Yeah, the NTBACKUP results are 24 hours old when they get backed up, but does your system state change that frequently? -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627