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
nickpc AT us.ibm DOT com

"I'm one cookie away from happy." - Snoopy (Charles Schulz)