How do i label a used tape volume in tsm?

gajidele

ADSM.ORG Member
Joined
Nov 1, 2008
Messages
8
Reaction score
0
Points
0
My environment is AIX, TSM 5.3

I have tape volumes that are reported "empty" and "private"

I am short of tapes and I want to reuse the old tapes as I don't need the data on them, they appear empty anyway.

Please how can I remove the used tapes from the TSM and relabel them for use again as new ones? I need to use the command line

Many thanks in advance.


q libvol

Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------- ---------- --------- ------- ------
TLS8433 A00003L3 Private Data 25 LTO
TLS8433 L00001L3 Private Data 27 LTO
TLS8433 L00002L3 Private Data 22 LTO
TLS8433 L00003L3 Private Data 26 LTO
TLS8433 L00004L3 Private Data 23 LTO
TLS8433 L00005L3 Private Data 24 LTO

q vol

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
/tsmstorage/tsmarchive.- ARCHIVE_OB- DISK 10,000.0 0.0 On-Line
vol00 JECTS_DISK
/tsmstorage/tsmbackup.v- BACKUPPOOL DISK 10,240.0 0.0 On-Line
ol00
/tsmstorage/tsmseismic.- SEISMIC_DI- DISK 10,000.0 92.6 On-Line
vol00 SK
/tsmstorage/tsmseismic.- SEISMIC_DI- DISK 10,000.0 100.0 On-Line
vol01 SK
A00003L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE
L00002L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE_BKUP
L00003L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE_BKUP
L00005L3 BACKUPPOOL- LTO3 0.0 0.0 Empty
_DR

q media * stgpool=seismic_tape

Volume State Location Automated
Name LibName
-------- -------------------------- ------------------- ---------------
A00003L3 Mountable in library TLS8433
 
Thanks. How do I then label this volume for use. Do I have to checkin to make it available to seismic_tape storage pool or something?
 
The tapes are already labelled so you should not need to relabel them. If the empty tapes are in the library then the above "delete volume" command will automatically return them to scratch if the "Scratch Volume?" attribute of the volume is set to "Yes" (do a "q vol f=d" to check). If it is set to "No" then you will subsequently need to issue an "udpate libvol <libname> <volname> status=scratch".
 
This tape volume is already in SCRATCH now. Still I cannot see the vol with the "q vol" command, however I can see it with "q libvol" command. When I tried to checkin, it says it is already in the library. Because of this when I try to migrate stgpool, it report insufficient space. How do I make this volume availabel for use?

q vol L00002L3
Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
L00002L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE_BKUP
q vol L00001L3
ANR2034E QUERY VOLUME: No match found using this criteria.
ANS8001I Return code 11.

q libvol

Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------- ---------- --------- ------- ------
TLS8433 A00003L3 Private Data 25 LTO
TLS8433 L00001L3 Scratch 27 LTO
TLS8433 L00002L3 Private Data 22 LTO
TLS8433 L00003L3 Private Data 26 LTO
TLS8433 L00004L3 Private Data 23 LTO
TLS8433 L00005L3 Private Data 24 LTO

Thanks for your time.
 
You won't see a scratch tape with a "q vol" command because that command only gives information about volumes assigned to stotage pools. By definition a scratch tape isn't.
You don't need to do anything else to make that volume available. Volume L00001L3 is scratch and will be picked up by a storage pool when it needs a scratch tape. If the migration process will not start then you need to find more tape capacity.
 
Something strange seems to be happening. When I tried to force a migration ( update stgpool seismic_disk hi=0 lo=0) , the scratch volume goes to private and the migration is not done. It complains there is no sufficient space the Next storage pool. I actually carried out an audit before the migration.

11/03/08 10:44:54 ANR2017I Administrator ROOT issued command: UPDATE STGPOOL
SEISMIC_DISK HI=0 LO=0 (SESSION: 59)
11/03/08 10:44:54 ANR2202I Storage pool SEISMIC_DISK updated. (SESSION: 59)
11/03/08 10:44:54 ANR0984I Process 329 for MIGRATION started in the
BACKGROUND at 10:44:54. (PROCESS: 329)
11/03/08 10:44:54 ANR1000I Migration process 329 started for storage pool
SEISMIC_DISK automatically, highMig=0, lowMig=0,
duration=No. (PROCESS: 329)
11/03/08 10:44:54 ANR8300E I/O error on library TLS8433 (OP=00006C03,
CC=314, KEY=05, ASC=3B, ASCQ=0E,
SENSE=70.00.05.00.00.00.00.0A.00.00.00.00.3B.0E.00.C0.00-
.04., Description=The source slot or drive was empty in
an attempt to move a volume). Refer to Appendix D in the
'Messages' manual for recommended action. (PROCESS: 329)
more... (<ENTER> to continue, 'C' to cancel)
11/03/08 10:44:54 ANR8312E Volume L00001L3 could not be located in library
TLS8433. (PROCESS: 329)
11/03/08 10:44:54 ANR8358E Audit operation is required for library TLS8433.
(PROCESS: 329)
11/03/08 10:44:54 ANR8778W Scratch volume L00001L3 changed to Private Status
to prevent re-access. (PROCESS: 329)
11/03/08 10:44:55 ANR1405W Scratch volume mount request denied - no scratch
volume available. (PROCESS: 329)
11/03/08 10:44:55 ANR1405W Scratch volume mount request denied - no scratch
volume available. (PROCESS: 329)
11/03/08 10:44:55 ANR1405W Scratch volume mount request denied - no scratch
volume available. (PROCESS: 329)
11/03/08 10:44:55 ANR1025W Migration process 329 terminated for storage pool
SEISMIC_DISK - insufficient space in subordinate storage
pool. (PROCESS: 329)
11/03/08 10:44:55 ANR0985I Process 329 for MIGRATION running in the
BACKGROUND completed with completion state FAILURE at
10:44:55. (PROCESS: 329)
 
My environment is AIX, TSM 5.3

I have tape volumes that are reported "empty" and "private"

I am short of tapes and I want to reuse the old tapes as I don't need the data on them, they appear empty anyway.

Please how can I remove the used tapes from the TSM and relabel them for use again as new ones? I need to use the command line

Many thanks in advance.


q libvol

Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------- ---------- --------- ------- ------
TLS8433 A00003L3 Private Data 25 LTO
TLS8433 L00001L3 Private Data 27 LTO
TLS8433 L00002L3 Private Data 22 LTO
TLS8433 L00003L3 Private Data 26 LTO
TLS8433 L00004L3 Private Data 23 LTO
TLS8433 L00005L3 Private Data 24 LTO

q vol

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
/tsmstorage/tsmarchive.- ARCHIVE_OB- DISK 10,000.0 0.0 On-Line
vol00 JECTS_DISK
/tsmstorage/tsmbackup.v- BACKUPPOOL DISK 10,240.0 0.0 On-Line
ol00
/tsmstorage/tsmseismic.- SEISMIC_DI- DISK 10,000.0 92.6 On-Line
vol00 SK
/tsmstorage/tsmseismic.- SEISMIC_DI- DISK 10,000.0 100.0 On-Line
vol01 SK
A00003L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE
L00002L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE_BKUP
L00003L3 SEISMIC_TA- LTO3 0.0 0.0 Empty
PE_BKUP
L00005L3 BACKUPPOOL- LTO3 0.0 0.0 Empty
_DR

q media * stgpool=seismic_tape

Volume State Location Automated
Name LibName
-------- -------------------------- ------------------- ---------------
A00003L3 Mountable in library TLS8433


I have a similar question, my situation is that I have a primary pool of archives, and i have a volume that i have moved that to another volume, and now I need to delete this volum (now tehere isn't data, I have moved to another volume) but I need to relabel this volume with another name to use this volume (tape)

What I have to do to reuse this volume?

Thanks
 
It seems the inventory of the library is a bit messed up. Try the following: 1. audit library checklabel=barcode 2. label libv search=yes labels=barcode checkin=scratch 3. retry the migration Regards. Wim.
 
Thanks very much everyone for your support and kindness.

I created another stgpool and set this to be the next stgpool for seismic_disk. The I forced the migration and it worked. Seems to me the problem is with the creation of the former stgpool (set as next stgpool for seismic_disk). I might have to recreate the other tape stgpools.

I have started loading data now to see if data will be migrated to the next stgpool automatically with the hi and lomig values set.

When I query the stgpool, is the estimated capacity for the stgpool or for each tape volume in the tape stgpool?

q stgpool

Storage Device Estimated Pct Pct High Low Next Stora-
Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
Pct Pct
----------- ---------- ---------- ----- ----- ---- --- -----------
ARCHIVEPOOL DISK 0.0 M 0.0 0.0 90 70
ARCHIVE_OB- DISK 10 G 0.0 0.0 90 70
JECTS_DISK
BACKUPPOOL DISK 10 G 0.0 0.0 90 70 BACKUP_TAPE
BACKUPPOOL- LTO3 0.0 M 0.0
_DR
BACKUP_TAPE LTO3 0.0 M 0.0 0.0 90 70
SEISMIC_DI- DISK 20 G 86.0 86.0 0 0 SEISMIC_TA-
SK PE2
SEISMIC_TA- LTO3 0.0 M 0.0 0.0 90 70
PE
SEISMIC_TA- LTO3 409,600,0- 0.0 0.0 90 70
PE2 00 G
SEISMIC_TA- LTO3 0.0 M 0.0
PE_BKUP
 
The estimated capacity of the storage pool in megabytes (M) or
gigabytes (G).
 
I have 5 x LTO3 tapes (that is 5 tape volumes) in my stgpool seismic_tape2 and estimated capacity is 400GB.

Does that mean the total size my stgpool seismic_tape2 can take is 400GB instead of 5 x 400GB?

What happens if the data being loaded ecxeeds 400GB, is this going to be lost?

Thanks.
 
Does that mean the total size my stgpool seismic_tape2 can take is 400GB instead of 5 x 400GB?
If you do
Code:
q stg [FONT=Arial]seismic_tape2[/FONT]
and the Estimated Capacity is 400 G, then yes, your storage pool is 400GB not 5x400GB. But estimated capacity is just that, an estimate. If the actual storage capacity is beyond the estimate, backups will continue as normal until the actual capacity is reached.
What happens if the data being loaded ecxeeds 400GB, is this going to be lost?
Once the capacity is reached, backups (or other processes that use that storage pool) will fail. The new data being loaded will not be backed up.
 
Back
Top