Orchid XP v8 wrote:
> The backup scan ran as an AT job.

I'm assuming you mean it ran at the server to pull files, rather than at the 
client to push files. Might be better to switch that around.

> Every now and then, there would be a 
> network glitch or somebody would turn off the PC or something, and the 
> script would hang with the network drive still mapped.

Why are you mapping a drive to a letter at all? Just use UNC names.

And robocopy can be told to stop copying after some number of failures. You 
can even tell it to resume copying halfway thru a large file if the copy 
failed in the middle.

> script bombs out because the drive is still mapped. 

Unmap it before trying to remap it, of course.

> mapped under the system account which runs AT jobs, 

Why? Tell AT to run it as a different user.

> And don't even get me started on how absurdly difficult it is to write 
> DOS scripts that handle failure properly...

That's what robocopy is for.

> Using the BackupExec agent for Exchange, backing up or restoring 
> mailboxes or even individual emails is no harder than backing up a 
> regular file. Try doing that with a DOS script...

Well, sure. If you have a program that understands the file format, backing 
up part of the file works. No surprise there.

-- 
   Darren New, San Diego CA, USA (PST)
   I ordered stamps from Zazzle that read "Place Stamp Here".

Post a reply to this message