The most common cause is when it prompts for user action and then waits forever
for an answer. Typically it has found destination file was not created by
NTBackup and wants to know if it is OK to overwrite it. This happens when the
previous run fails without closing the file.
On Wed, 25 Nov 2009 07:01:59 -0800 (PST), yaro137 <>
wrote:
>I have a scheduled ntbackup job that's running far too long. Is there
>a way to get the status window while it's running so I can see what's
>it hanging on?
>yaro
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|