Ah.  Yes, if it gave you the ANR1256W message, it knows that there are files
on the primary tape that are not on a copy pool tape, and therefore can't be
restored.

That's not surprising - could be there was a problem reading the 2 bad files
at the time it was trying to create the copy pool copy.

And you are correct, if you purge the DB entries for the bad files, TSM will
back them up on the next go around, assuming they still exist on the client.


-----Original Message-----
From: Matt Simpson [mailto:msimpson AT UKY DOT EDU]
Sent: Thursday, February 06, 2003 5:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Need advice on dealing with unreadable tape


At 5:11 PM -0500 2/6/03, Prather, Wanda wrote:
>Well, if RESTORE VOLUME says there is nothing to restore, and q content
says
>there is, one of them is lying!

I didn't interpret the messages as meaning there was nothing TO
restore .. I thought it meant there was nothing it COULD restore. It
did say
ANR1256W Volume 000345 contains files that could not be restored.
so it apparently knew there was stuff there it couldn't restore.

>Try AUDIT VOLUME 000345
>If it says the two files can't be read, then run
>
>AUDIT VOLUME 000356 fix=yes
>That should purge the bad DB entries and free up the tape.

OK, thanks.  Am I correct in assuming that purging the DB entries
will force new backups if those are the active versions?



--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.