Another fix is to have the schedule run d:\runbackup.cmd, which contains one line: start d:\backup.cmd This will let runbackup.cmd finish, showing successful completion of the schedule, while letting the backup run for as long as it needs to. Since you already have to check elsewhere to see if the backup itself was successful, this doesn't allow a problem to slip through on you. Nick Cassimatis [EMAIL PROTECTED] "I'm one cookie away from happy." - Snoopy (Charles Schulz)
- TDP & ADSM Paul Dowie
- Re: TDP & ADSM Del Hoobler
- TDP & ADSM Thomas Denier
- Nicholas Cassimatis