Wanda, you are correct. The copy in the copy pool may be fine, so the
backup version isn't really destroyed (assuming the copy in the copy pool
is still good). If a primary storage pool volume has damaged files,
RESTORE VOLUME can be attempted to restore the volume.
If the volume being audited is a copy storage pool volume and it is
audited with FIX=YES, then damaged files will be deleted from the copy
pool volume, but the backup version itself won't be deleted from TSM's
inventory (because the primary copy still exists). The next time BACKUP
STGPOOL is run, new copy pool versions of the damaged files will be
created.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/08/2004 14:34
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: Files Marked Damaged by Audit Volume
Andy,
If the volume is audited with FIX=YES, BUT the file has a copy in a copy
pool, I don't think it gets deleted, does it?
Is it eligible for backup again in that case?
Thanks
Wanda
-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: Thursday, April 08, 2004 5:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Files Marked Damaged by Audit Volume
Hi Andy,
When a volume is audited with FIX=NO, damaged files are marked as such,
but not deleted. In this case, damaged files are not automatically
eligible for backup again just by virtue of being damaged. Consider the
possibility that the "damage" could be temporary, such as if the drive on
which the audit was performed was dirty; and that once the drive is
cleaned, another audit will show the file as being fine.
When a volume is audited with FIX=YES, then the damaged files will be
deleted. If the damaged file is deleted AND it is the active version, then
it will be eligible for backup the next time the client backup runs. If
the damaged file is an INACTIVE version, then that by itself will not
trigger another backup of the file (but of course the file could be backed
up again if it has changed on the client system since the last time the
file was backed up).
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Andy Carlson <andyc AT ANDYC.CARENET DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/08/2004 08:55
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Files Marked Damaged by Audit Volume
If an active file is marked damaged by audit volume, is the file backed
up at the next opportunity?
We have a situation where at least one tape that had undiscovered
damaged files was copied to a copypool tape. Those files are not
recoverable at this time. We are contemplating a full audit on all the
volumes in the onsite pool, but need to know if the files marked damaged
will be backed up again.
Thanks for any info.
|
