Hi David, Hi Fred, 1) David - We aren't using the DRM .... 2) Fred - Your approach would work, I'm sure..... Because, when the OFFSITE Reclamation (or Move Data) ends after hundreds of mounts, then the now empty Volumes Status is EMPTY and afterwards they are used for new copies again. (And suddenly TSM doesn't think that this Volume is still OFFSITE .... how strange......he will use it again......) But our intention is to free up (reclaim) the Copy-Volumes, when they reach a Reclamation-Threshold of 60% ..... and so i don't understand the suggestion of Fred - because how can I tell TSM that he should create new copies instead of the old Ones, which are on the OFFSITE Volume xxxxxx ?? And: I don't want to Delete the Volume with Discard=yes.... (in this case, he would create a new copy - but what happens, when a Primary Tape is corrupted ? Data is lost....) That's of course a new question ..... What happens, when TSM is making an OFFSITE Reclamation, using the primary tapes, and one of the primary Tapes is corrupt ? Will the Reclamation Process fail ? Will he then use the Copy-Volume with the Access=ReadWrite and will he change his own opinion, that this volume is OFFSITE ?? One more hint in this point of view: I tried the following: Setting the Access Status of the Primary Pool to UNAVAILABLE and Move-Data of a Volume, which has Status Read/Write and where TSM is thinking that it's OFFSITE. So I "forced" him to use a Volume from the Primary Pool, which is unavailable........and It's unbelievable, but even though the Status is UNAVAILABE he is mounting and using a Tape of the unavailable Primary Pool....... -- Gerhard -- [EMAIL PROTECTED] (Fred Johanson) am 08.01.2001 16:39:28 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema: Re: *SMs Thinking of OFFSITE Volumes ?
It works the same without DRM. Lower the Reclamation value on the offsite pool. As a fresh version of the copypool is being created, the old one is going to empty. When you're thru, send off the new version and bring back the empties. At 10:16 AM 1/8/2001 -0500, you wrote: >Are you using DRM? If so then you need to let reclamation empty the >volumes, then request from vault tapes that are in a DRM state of >vaultretrieve - which will be empty tapes. Then when there are back >then one way to handle is MOVE DRMEDIA xxxxxx wherestate=vaultr >tostate=onsiter for each tape, xxxxxx = volume name. These tapes are then >available to be checked back into your library as scratch tapes. > >David B. Longo >Systems Administrator >Health First, Inc. I/T >3300 Fiske Blvd. >Rockledge, FL 32955-4305 >PH 321.434.5536 >Pager 321.634.8230 >Fax: 321.434.5525 >[EMAIL PROTECTED] > > > > >>> [EMAIL PROTECTED] 01/08/01 05:25AM >>> >Hi *SMer, >We are reclaiming OFFSITE-Volumes, when they reach a Reclamation Threshold >of 60 >Percent. >Therefor following steps are being done: >1) All pertaining OFFSITE Volumes come in from the offsite Location. >2) Following SQL Stmt will be performed for each Volume: (Setting the >Access of >the volume and the Location-Comment) >UPD VOL xxxxxx Access=ReadWrite Location="" >3) Set the Reclamation Threshold from 100% to 60% to start the Reclamation. > >Now following Problem occurs: >TSM still thinks, that the volume is OFFSITE (However....) and is making an >OFFSITE-Reclamation. >And the big Problem is: The original (primary) Tapepool is collocated and the >Copy-Pool isn't. >This means, that for OFFSITE-Reclamation for one Copy-Volume in the worst case >hundreds of mounts of the primary Volumes will be needed. >The same happens, when I am making a "manual" Move-Data... (See below the >example of a Move-Data) > >So why is TSM still thinking, that the Volume is OFFSITE although the >Access-State is READ/WRITE ?? >Even strange (look below) that it takes about 17 Minutes to determine, >where the >original Data is located and why is the Completion State of the canceled >process >SUCCESS ?? > >Our Server-Configuration is: >.) OS/390 V2 R9.0 >.) Tivoli Storage Manager for MVS, Version 3, Release 7, Level 4.0 > >Is it a bug or a User Failure ? >Can someone help me ? > >Thanks for all hints >Gerhard Wolkerstorfer > > > >Example of the Move Data => >(Comments are in BIG LETTERS, the rest is the Original Joblog) > >1) A QU VOL OF THE COPY-VOLUME IS BRINGING: >(REMARK THAT THE ACCESS OF THE VOLUME IS READ/WRITE !) > > 11.50.01 STC15273 ANR5965I Console command: QU VOL PC0204 F=D > 11.50.01 STC15273 ANR2017I Administrator SERVER_CONSOLE issued command: > QUERY >VOLUME PC0204 F=D > 11.50.01 STC15273 > 11.50.01 STC15273 Volume Name: PC0204 > 11.50.01 STC15273 Storage Pool Name: BACKUP_COPY_AUF_3590E > 11.50.01 STC15273 Device Class Name: 3590E > 11.50.02 STC15273 Estimated Capacity (MB): 22,856.4 > 11.50.02 STC15273 Pct Util: 70.2 > 11.50.02 STC15273 Volume Status: Full > 11.50.02 STC15273 Access: Read/Write > 11.50.02 STC15273 Pct. Reclaimable Space: 39.4 > 11.50.02 STC15273 Scratch Volume?: No > 11.50.02 STC15273 In Error State?: No > 11.50.02 STC15273 Number of Writable Sides: 1 > 11.50.02 STC15273 Number of Times Mounted: 10 > 11.50.02 STC15273 Write Pass Number: 1 > 11.50.02 STC15273 Approx. Date Last Written: 2000-07-25 13:42:35 > 11.50.02 STC15273 Approx. Date Last Read: 2000-07-13 17:05:36 > 11.50.03 STC15273 Date Became Pending: > 11.50.03 STC15273 Number of Write Errors: 0 > 11.50.03 STC15273 Number of Read Errors: 0 > 11.50.03 STC15273 Volume Location: > 11.50.03 STC15273 Last Update by (administrator): WOLKE > 11.50.03 STC15273 Last Update Date/Time: 2000-10-16 11:47:52 > >2) STARTING THE MOVE DATA PROCESS... >REMARK THAT TSM IS MAKING AN OFFSITE MOVE DATA AND THEREFORE IS SEARCHING >EXACTLY 17 MINUTES (I GUESS THIS IS A LITTLE BIT TOO LONG, ISN'T IT ?) FOR THE >LOCATION OF THE ORIGINAL DATA AND AFTER THIS TIME THE FIRST (!!!!) ORIGINAL >VOLUME IS BEING MOUNTED. > > 11.50.03 STC15273 > 11.50.03 STC15273 > 11.50.03 STC15273 TSM:ATEDV003> > 11.50.33 STC15273 ANR2017I Administrator WOLKE issued command: MOVE DATA >PC0204 Stgpool=BACKUP_C- > 11.50.33 STC15273 ANR2017I OPY_AUF_3590E > 11.50.33 STC15273 ANR0984I Process 5 for MOVE DATA started in the > BACKGROUND >at 11:50:33. > 11.50.33 STC15273 ANR1140I Move data process started for volume PC0204 >(process ID 5). > 11.50.33 STC15273 ANR2017I Administrator WOLKE issued command: QUERY > PROCESS > 11.50.33 STC15273 ANR2017I Administrator WOLKE issued command: Show Time > 11.50.51 STC15273 ANR5965I Console command: QU PR > 11.50.51 STC15273 ANR2017I Administrator SERVER_CONSOLE issued command: > QUERY >PROCESS > 11.50.51 STC15273 > 11.50.51 STC15273 Process Process Description Status > 11.50.51 STC15273 Number > 11.50.51 STC15273 -------- -------------------- >------------------------------------------------- > 11.50.51 STC15273 5 Move Data Offsite Volume PC0204 > (storage >pool BACKUP_COPY_- > 11.50.51 STC15273 AUF_3590E), Target Pool >BACKUP_COPY_AUF_3590E, > 11.50.51 STC15273 Moved Files: 0, Moved > Bytes: >0, Unreadable > 11.50.51 STC15273 Files: 0, Unreadable > Bytes: >0. Current Physical > 11.50.51 STC15273 File (bytes): None > 11.50.51 STC15273 > 11.50.51 STC15273 TSM:ATEDV003> > 12.07.51 STC15273 ANR1157I Removable volume PC0058 is required for Move > Data >process. > 12.07.51 STC15273 ANR5216I 3590 PC0058 is expected to be mounted (R/O). > 12.08.08 STC15273 ANR2017I Administrator WOLKE issued command: QUERY > PROCESS > 12.08.09 STC15273 ANR2017I Administrator WOLKE issued command: Show Time > 12.10.24 STC15273 IEC501A M 07B0,PC0058,SL,COMP,ADSMT,ADSMT,ADSM.BFS > 12.10.24 STC15273 IEC501A M 07B2,PC0220,SL,COMP,ADSMT,ADSMT,ADSM.BFS > 12.11.02 STC15273 IEC271I MESSAGE DISPLAY 'PC0058' ON 07B0 ISSUED BY > JOB ADSMT > 12.11.06 STC15273 IEC271I MESSAGE DISPLAY 'PC0220' ON 07B2 ISSUED BY > JOB ADSMT > >3) QU VOL OF THE 2 MOUNTED VOLUMES - THE FIRST (PC0058) IS THE ORIGINAL TAPE, >THE SECOND (PC0220) IS THE OUTPUT(!) COPY-TAPE >(BACKUP_3590E IS THE PRIMARY TAPEPOOL AND BACKUP_COPY_AUF_3590E IS THE >COPYPOOL) > > 12.11.20 STC15273 ANR5965I Console command: QU VOL PC0058 F=D > 12.11.20 STC15273 ANR2017I Administrator SERVER_CONSOLE issued command: > QUERY >VOLUME PC0058 F=D > 12.11.20 STC15273 > 12.11.20 STC15273 Volume Name: PC0058 > 12.11.20 STC15273 Storage Pool Name: BACKUP_3590E > 12.11.20 STC15273 Device Class Name: 3590E > 12.11.20 STC15273 Estimated Capacity (MB): 21,145.0 > 12.11.20 STC15273 Pct Util: 80.2 > 12.11.20 STC15273 Volume Status: Full > 12.11.20 STC15273 Access: Read/Write > 12.11.20 STC15273 Pct. Reclaimable Space: 32.1 > 12.11.21 STC15273 Scratch Volume?: No > 12.11.21 STC15273 In Error State?: No > 12.11.21 STC15273 Number of Writable Sides: 1 > 12.11.21 STC15273 Number of Times Mounted: 23 > 12.11.21 STC15273 Write Pass Number: 2 > 12.11.21 STC15273 Approx. Date Last Written: 2000-09-19 08:58:42 > 12.11.21 STC15273 Approx. Date Last Read: 2000-10-16 12:11:03 > 12.11.21 STC15273 Date Became Pending: > 12.11.21 STC15273 Number of Write Errors: 0 > 12.11.21 STC15273 Number of Read Errors: 0 > 12.11.21 STC15273 Volume Location: > 12.11.21 STC15273 Last Update by (administrator): DEIN > 12.11.21 STC15273 Last Update Date/Time: 2000-05-16 10:36:44 > 12.11.21 STC15273 > 12.11.21 STC15273 > 12.11.21 STC15273 TSM:ATEDV003> > 12.11.25 STC15273 ANR5965I Console command: QU VOL PC0220 F=D > 12.11.25 STC15273 ANR2017I Administrator SERVER_CONSOLE issued command: > QUERY >VOLUME PC0220 F=D > 12.11.26 STC15273 > 12.11.26 STC15273 Volume Name: PC0220 > 12.11.26 STC15273 Storage Pool Name: BACKUP_COPY_AUF_3590E > 12.11.26 STC15273 Device Class Name: 3590E > 12.11.26 STC15273 Estimated Capacity (MB): 21,000.0 > 12.11.26 STC15273 Pct Util: 39.2 > 12.11.26 STC15273 Volume Status: Filling > 12.11.26 STC15273 Access: Read/Write > 12.11.26 STC15273 Pct. Reclaimable Space: 3.6 > 12.11.26 STC15273 Scratch Volume?: No > 12.11.26 STC15273 In Error State?: No > 12.11.26 STC15273 Number of Writable Sides: 1 > 12.11.26 STC15273 Number of Times Mounted: 36 > 12.11.26 STC15273 Write Pass Number: 3 > 12.11.26 STC15273 Approx. Date Last Written: 2000-10-14 17:07:57 > 12.11.26 STC15273 Approx. Date Last Read: 2000-09-18 10:04:49 > 12.11.26 STC15273 Date Became Pending: > 12.11.26 STC15273 Number of Write Errors: 0 > 12.11.26 STC15273 Number of Read Errors: 0 > 12.11.26 STC15273 Volume Location: > 12.11.26 STC15273 Last Update by (administrator): WOLKE > 12.11.26 STC15273 Last Update Date/Time: 2000-06-13 14:37:28 > 12.11.26 STC15273 > 12.11.26 STC15273 > 12.11.26 STC15273 TSM:ATEDV003> > 12.11.47 STC15273 ANR5965I Console command: QU PR > 12.11.47 STC15273 ANR2017I Administrator SERVER_CONSOLE issued command: > QUERY >PROCESS > 12.11.47 STC15273 > 12.11.47 STC15273 Process Process Description Status > 12.11.47 STC15273 Number > 12.11.47 STC15273 -------- -------------------- >------------------------------------------------- > 12.11.47 STC15273 5 Move Data Offsite Volume PC0204 > (storage >pool BACKUP_COPY_- > 12.11.47 STC15273 AUF_3590E), Target Pool >BACKUP_COPY_AUF_3590E, > 12.11.47 STC15273 Moved Files: 0, Moved > Bytes: >0, Unreadable > 12.11.47 STC15273 Files: 0, Unreadable > Bytes: >0. Current Physical > 12.11.47 STC15273 File (bytes): > 4,502ÚCurrent >input volume: > 12.11.47 STC15273 PC0058.ÚCurrent output >volume: PC0220.Ú > 12.11.47 STC15273 > 12.11.47 STC15273 TSM:ATEDV003> > >4) BECAUSE TSM WOULD NOW MOUNT ABOUT 100 TAPES FROM THE TAPEPOOL, I AM >CANCELING >THE PROCESS >REMARK: THE COMPLETION STATE OF THE MOVE DATA PROCESS IS "SUCCESS" ALTHOUGH IT >WAS CANCELED.....EVEN STRANGE ! > > 12.12.13 STC15273 ANR2017I Administrator WOLKE issued command: CANCEL > PROCESS >5 > 12.12.19 STC15273 ANR1143W Move data process terminated for volume PC0204 - >process canceled. > 12.12.19 STC15273 ANR0985I Process 5 for MOVE DATA running in the > BACKGROUND >completed with > 12.12.19 STC15273 ANR0985I completion state SUCCESS at 12:12:19. > 12.13.19 STC15273 ANR5217I Dismounting volume PC0220 - 1 minute mount >retention expired. > 12.13.19 STC15273 ANR5217I Dismounting volume PC0058 - 1 minute mount >retention expired. > 12.13.19 STC15273 ANR5208I Dismounting volume PC0220 (updated). > 12.13.19 STC15273 ANR5209I Dismounting volume PC0058 (read-only access). > 12.13.24 STC15273 IEF234E K 07B2,PC0220,PVT,ADSMT,ADSMT > 12.14.10 STC15273 IEF234E K 07B0,PC0058,PVT,ADSMT,ADSMT
