ADSM-L

Re: damaged files

1999-10-29 22:21:25
Subject: Re: damaged files
From: Nick Cassimatis <nickpc AT US.IBM DOT COM>
Date: Fri, 29 Oct 1999 22:21:25 -0400
Marking a file as damaged does not cause that file be backed up during
the next backup session.  Generally, the server takes a conservative
approach in handling damaged files to reduce the risk of losing good data.
This often requires the administrator (who may be aware of special
circumstances) to take some explicit action such as auditing the volume,
restoring files from a copy pool, or deleting the damaged files.  If ADSM
were
to force another backup whenever an existing file is marked damaged
(possibly
as a result of some correctable hardware or media problem), valuable data
could be versioned off unnecessarily.

Dave Cannon
Tivoli Storage Manager Server Development, IBM
cannon AT us.ibm DOT com

Why?  Why can't the function be, if the file is the Active version, to take
a new backup of it (same file, right?), then expire the Damaged file?  This
would take a lot of the workload you describe off the ADSM Admin,
especially if they are having media problems.

I put in a request for this a long while back, and never heard anything.  I
guess I'm asking again...

Nick Cassimatis
nickpc AT us.ibm DOT com

If you don't have the time to do it right the first time, where will you
find the time to do it again?
<Prev in Thread] Current Thread [Next in Thread>