Re: Strange copypool volume behavior
There are no destroyed or unavailable volumes. Right now this tape is in pending status, so I have some time to enjure that there is another copy of these files. If there is a way to find their names . when even query content didn't work before delete volume. Maria Ilieva - Original Message - From: "Richard Sims" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 16, 2003 2:40 PM Subject: Re: Strange copypool volume behavior > ... > >However, I decided delete this volume with discarddata=y and make another > >backup stg. > > But that may have been the only surviving instance of those files in TSM server > storage. > > Richard Sims, BU >
Re: Strange copypool volume behavior
... >However, I decided delete this volume with discarddata=y and make another >backup stg. But that may have been the only surviving instance of those files in TSM server storage. Richard Sims, BU
Re: Strange copypool volume behavior
I already did an audit volume fix=y Here is the result: 06/16/2003 13:47:47 ANR4132I Audit volume process ended for volume B0010; 5 files inspected, 0 damaged files deleted, 0 damaged files marked as damaged, 0 objects updated. 06/16/2003 13:47:47 ANR0987I Process 92 for AUDIT VOLUME (REPAIR) running in the BACKGROUND processed 5 items with a completion state of SUCCESS at 13:47:47. So it finds nothing suspicious on this volume. However, I decided delete this volume with discarddata=y and make another backup stg. Maria Ilieva - Original Message - From: "Karel Bos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 16, 2003 2:17 PM Subject: Re: Strange copypool volume behavior > Yes, an audit vol fix=yes clears the problem. > > > -Oorspronkelijk bericht- > > Van: Maria Ilieva [mailto:[EMAIL PROTECTED] > > Verzonden: maandag 16 juni 2003 11:09 > > Aan: [EMAIL PROTECTED] > > Onderwerp: Strange copypool volume behavior > > > > > > TSM Server 5.1.6.5 on AIX 4.3 > > > > I did MOVE DATA on an offsite copypool volume. > > Move data finished and issued these messages: > > > > 06/15/2003 14:59:19 ANR1141I Move data process ended for > > volume B0010. > > 06/15/2003 14:59:19 ANR0986I Process 74 for MOVE DATA > > running in the > > BACKGROUND processed 9 items for a > > total of 1,581,444,559 > > bytes with a completion state of > > SUCCESS at 14:59:19. > > 06/15/2003 14:59:19 ANR1163W Offsite volume B0010 still > > contains files which > > could not be moved. > > > > There is no other message in activity log why these files > > cannot be moved. > > Now query volume shows: > > tsm: PHOBOS>q v B0010 > > > > Volume Name Storage Device Estimated > > Pct Volume > > Pool NameClass Name Capacity > > Util Status > > (MB) > > --- -- - > > - > > B0010 TITANCOPYDLT7000 19,183.9 > > 5.8Full > > > > and query content: > > tsm: PHOBOS>q content B0010 > > ANR2034E QUERY CONTENT: No match found using this criteria. > > ANS8001I Return code 11. > > > > I also did an audit volume - it shows nothing wrong with the volume. > > > > Has anybody seen this? > > > > > > Maria Ilieva > > >
Re: Strange copypool volume behavior
>... >06/15/2003 14:59:19 ANR1163W Offsite volume B0010 still contains > files which could not be moved. >... Maria - You can refer to http://people.bu.edu/rbs/ADSM.QuickFacts in supplementing the Messages manual... ANR1163W Offsite volume __ still contains files which could not be moved. Indicates that a reclamation or MOVe Data was attempted on an offsite volume, but it still contained data. When MOVe Data or reclamation is performed for an offsite volume, files are obtained from a primary storage pool or possibly from another copy storage pool. Message ANR1163W is issued when residual files are left on the offsite volume after this move is completed. This typically occurs when the server cannot copy files from another storage pool because they reside on volumes that are unavailable or offline. Another possibility is that files in the source storage pool are marked as damaged and therefore do not get moved. Check your activity log for messages indicating the reason why the files were not moved. >From other notes in that doc... As an administrator, you need to perform the following regularly: 'Query Volume ACCess=UNAVailable' 'Query Volume ACCess=DESTroyed' 'Query Volume ACCess=READOnly STATus=FIlling' 'Query Volume STatus=PENding Format=Detailed' It might also be the case that no onsite copy was made of some of the data that went offsite. Do a Query Content on the subject volume and research from there. Richard Sims, BU
Re: Strange copypool volume behavior
Yes, an audit vol fix=yes clears the problem. > -Oorspronkelijk bericht- > Van: Maria Ilieva [mailto:[EMAIL PROTECTED] > Verzonden: maandag 16 juni 2003 11:09 > Aan: [EMAIL PROTECTED] > Onderwerp: Strange copypool volume behavior > > > TSM Server 5.1.6.5 on AIX 4.3 > > I did MOVE DATA on an offsite copypool volume. > Move data finished and issued these messages: > > 06/15/2003 14:59:19 ANR1141I Move data process ended for > volume B0010. > 06/15/2003 14:59:19 ANR0986I Process 74 for MOVE DATA > running in the > BACKGROUND processed 9 items for a > total of 1,581,444,559 > bytes with a completion state of > SUCCESS at 14:59:19. > 06/15/2003 14:59:19 ANR1163W Offsite volume B0010 still > contains files which > could not be moved. > > There is no other message in activity log why these files > cannot be moved. > Now query volume shows: > tsm: PHOBOS>q v B0010 > > Volume Name Storage Device Estimated > Pct Volume > Pool NameClass Name Capacity > Util Status > (MB) > --- -- - > - > B0010 TITANCOPYDLT7000 19,183.9 > 5.8Full > > and query content: > tsm: PHOBOS>q content B0010 > ANR2034E QUERY CONTENT: No match found using this criteria. > ANS8001I Return code 11. > > I also did an audit volume - it shows nothing wrong with the volume. > > Has anybody seen this? > > > Maria Ilieva >
Re: Strange copypool volume behavior
Yes, we have seen the same behavior. Have you opened a call with IBM? Ken > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Maria Ilieva > Sent: Monday, June 16, 2003 05:09 > To: [EMAIL PROTECTED] > Subject: Strange copypool volume behavior > > > TSM Server 5.1.6.5 on AIX 4.3 > > I did MOVE DATA on an offsite copypool volume. > Move data finished and issued these messages: > > 06/15/2003 14:59:19 ANR1141I Move data process ended for > volume B0010. > 06/15/2003 14:59:19 ANR0986I Process 74 for MOVE DATA > running in the > BACKGROUND processed 9 items for a > total of 1,581,444,559 > bytes with a completion state of > SUCCESS at 14:59:19. > 06/15/2003 14:59:19 ANR1163W Offsite volume B0010 still > contains files which > could not be moved. > > There is no other message in activity log why these files > cannot be moved. Now query volume shows: > tsm: PHOBOS>q v B0010 > > Volume Name Storage Device Estimated > Pct Volume > Pool NameClass Name Capacity > Util Status > (MB) > --- -- - > - > B0010 TITANCOPYDLT7000 19,183.9 > 5.8Full > > and query content: > tsm: PHOBOS>q content B0010 > ANR2034E QUERY CONTENT: No match found using this criteria. > ANS8001I Return code 11. > > I also did an audit volume - it shows nothing wrong with the volume. > > Has anybody seen this? > > > Maria Ilieva >
