ADSM-L

Re: ANS1512E error

1998-09-01 08:17:11
Subject: Re: ANS1512E error
From: Craig Shreve <CShreve AT UNIONGAS DOT COM>
Date: Tue, 1 Sep 1998 08:17:11 -0400
I have run into this before on an NT client.  Double check the log to
make sure that the backup completed successfully.  Mine had appeared to
as well, but in fact had skipped a filespace.  My situation was that
there were two corrupt files on the root of the c:\.  ADSM successfully
backed up the registry, then tried to process the c:\ but passed it by
(there was a file I\O error at this point in the log - you can check for
this too).  ADSM then continued on and successfully backed up the d:\,
gave the usual final statistics at the end, then gave a message similar
to the one you received.  The corrupt files could not be removed or
renamed.  I had to reboot the NT client so that chkdsk could run and
remove the offending files.
 The only workaround I could come up with while waiting to get the
reboot scheduled was to run backups form the backup\archive client, with
an individual session for each directory that did not contain the
corrupt files (I tried to exclude the files in dsm.opt, but continued to
receive the same error).
Hope this helps.


Craig Shreve
Specialist, Distributed Systems Management
Union Gas Limited
(519) 436-4600 x2045
cshreve AT uniongas DOT com


<Prev in Thread] Current Thread [Next in Thread>