tapes not being used fully

[jellyfish]

Currently the diskpool is 100 used and no scratch tapes to migrate date onto, however I noticed when I do a q vol

tsm: TSM01>q vol
Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
AHQ101L3 LTO_OFFSITE LTOCLASS 1,274,648 84.6 Filling
.3
AHQ102L3 LTO_ONSITE LTOCLASS 866,073.5 23.0 Filling
AHQ103L3 LTO_ONSITE LTOCLASS 1,095,854 43.2 Full
.7
AHQ104L3 LTO_OFFSITE LTOCLASS 914,161.7 89.6 Filling
AHQ105L3 LTO_OFFSITE LTOCLASS 836,192.4 0.0 Filling
AHQ106L3 LTO_OFFSITE LTOCLASS 762,938.0 1.1 Filling
AHQ107L3 LTO_OFFSITE LTOCLASS 834,075.3 0.0 Full
AHQ108L3 LTO_ONSITE LTOCLASS 762,938.0 3.0 Filling
AHQ109L3 LTO_OFFSITE LTOCLASS 1,687,103 7.6 Full
.4
AHQ110L3 LTO_OFFSITE LTOCLASS 762,938.0 0.0 Filling
AHQ111L3 LTO_ONSITE LTOCLASS 1,238,252 74.9 Full
.4
F:\TSMDATA\TSM_DISK_STG- DISKPOOL DISK 102,400.0 100.0 On-Line
_POOL\DISKVOL01.DSM
TS0001L3 LTO_OFFSITE LTOCLASS 817,127.2 1.1 Full
TS0002L3 LTO_OFFSITE LTOCLASS 1,854,034 0.0 Full

as you can see some tapes that are classed as onsite are hardly used but migration from diskpool to tapes isnt happening at all

any ideas . How do I ensure these tapes are used correctly.

 

[Harry_Redl]

Hi,

your tapes are in filling state so it seems they should be used for migration. If they are not then it is very likely that they are not in "readwrite" access mode. Check this.
Are they in the right stgpool? Is the "nextstgpool" parameter for "diskpool" set correctly?
Any error from actlog when running migration?
Are the tapes visible in the library? (q libvol)
Another thing (not directly related to the problem)
Check collocation setting fot both onsite and offsite pools - do you want it to be set?

Harry

 

[itcsge]

do you run reclamation against the tapes? check what the pct_reclaim figures are to see how many tapes can be reclaimed etc. As inactive files reach retention periods, space on the tapes can be "reclaimed"

i use a variant of this simple script to check:-

select stgpool_name, volume_name, location, pct_utilized, pct_reclaim, status, last_write_date from volumes where stgpool_name like '%ONSITE%' order by stgpool_name, pct_reclaim desc

 

[rmazzon]

Do you use node or filespace collocation?

 

[jellyfish]

thanks for all the replies, I havent been in the office for a while and as a short term fix we purchased more tapes so the migration from disk pool to tapes occured. .. however I will look into all the recommendations given and will report back

thanks again for all your help.

 

[jellyfish]

Check collocation setting fot both onsite and offsite pools - do you want it to be set?

The 3 storage pools we have (DISKPOOL, LTO_ONSITE, LTO_OFFSITE) collocation is set to no on the two LTO storage pools and not set on the diskspool

Are they in the right stgpool? Is the "nextstgpool" parameter for "diskpool" set correctly?

for DISKPOOL the nextstgpool is set to LTO_ONSITE

 

[Harry_Redl]

Hi,

how about the access mode? That is the most probable cause.
Show us "q act" output whet attepmting migration (migr stgpool diskpool low=0)

Harry

 

[jellyfish]

Hi,

how about the access mode? That is the most probable cause.
Show us "q act" output whet attepmting migration (migr stgpool diskpool low=0)

Harry

This is the events for migration

ANR1000I Migration process 415 started for storage pool DISKPOOL automatically,
highMig=0, lowMig=0, duration=No.
ANR8337I LTO volume TS0138L3 mounted in drive DRIVE1 (mt0.0.0.3).
ANR0513I Process 415 opened output volume TS0138L3.
ANR8341I End-of-volume reached for LTO volume TS0138L3.
ANR8341I End-of-volume reached for LTO volume TS0138L3.
ANR0515I Process 415 closed volume TS0138L3.
ANR1405W Scratch volume mount request denied - no scratch volume available.
ANR1405W Scratch volume mount request denied - no scratch volume available.
ANR1405W Scratch volume mount request denied - no scratch volume available.
ANR1025W Migration process 415 terminated for storage pool DISKPOOL -
insufficient space in subordinate storage pool.
ANR0985I Process 415 for MIGRATION running in the BACKGROUND completed with
completion state FAILURE at 09:01:33.

 

[MAG]

Can you show an updated output for the following commands?

q vol stgp=lto_onsite
q libv

It looks like you'll need to tidy up the number of filling tapes in the onsite tape pool to make sure there's scratch tapes available. When the end of a tape is reached when doing a migration, back stgp, etc, it will very often be halfway through a file. In which case it will need to start on a new scratch tape instead of using a partially used tape.

 

[jellyfish]

Can you show an updated output for the following commands?
q vol stgp=lto_onsite
q libv

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
AHQ102L3 LTO_ONSITE LTOCLASS 866,073.5 23.0 Filling
AHQ103L3 LTO_ONSITE LTOCLASS 1,095,854 43.2 Full
.7
AHQ108L3 LTO_ONSITE LTOCLASS 762,938.0 3.0 Filling
AHQ111L3 LTO_ONSITE LTOCLASS 1,238,252 30.9 Full
.4
TS0004L3 LTO_ONSITE LTOCLASS 1,058,284 1.9 Full
.9
TS0005L3 LTO_ONSITE LTOCLASS 1,192,656 57.6 Full
.3
TS0006L3 LTO_ONSITE LTOCLASS 1,398,873 30.2 Full
.1
TS0007L3 LTO_ONSITE LTOCLASS 720,929.9 3.5 Full
TS0012L3 LTO_ONSITE LTOCLASS 1,308,219 25.5 Full
.6
TS0013L3 LTO_ONSITE LTOCLASS 1,598,716 6.9 Full
.0
TS0015L3 LTO_ONSITE LTOCLASS 663,799.2 64.2 Full
TS0017L3 LTO_ONSITE LTOCLASS 575,879.7 65.1 Full
TS0019L3 LTO_ONSITE LTOCLASS 741,752.7 62.6 Full
TS0023L3 LTO_ONSITE LTOCLASS 1,218,913 59.8 Full
.9
TS0026L3 LTO_ONSITE LTOCLASS 845,866.4 36.3 Full
TS0027L3 LTO_ONSITE LTOCLASS 593,482.3 91.4 Full
TS0030L3 LTO_ONSITE LTOCLASS 1,414,246 25.1 Filling
.5
TS0031L3 LTO_ONSITE LTOCLASS 606,172.5 46.2 Full
TS0034L3 LTO_ONSITE LTOCLASS 1,629,140 2.4 Full
.6
TS0035L3 LTO_ONSITE LTOCLASS 0.0 0.0 Empty
TS0036L3 LTO_ONSITE LTOCLASS 1,199,490 0.4 Full
.4
TS0037L3 LTO_ONSITE LTOCLASS 960,007.5 39.2 Full
TS0039L3 LTO_ONSITE LTOCLASS 843,885.6 0.3 Full
TS0043L3 LTO_ONSITE LTOCLASS 1,304,197 20.9 Filling
.3
TS0046L3 LTO_ONSITE LTOCLASS 1,131,628 59.7 Full
.1
TS0048L3 LTO_ONSITE LTOCLASS 1,503,692 1.6 Full
.1
TS0054L3 LTO_ONSITE LTOCLASS 1,300,617 7.0 Full
.1
TS0056L3 LTO_ONSITE LTOCLASS 1,367,605 9.9 Full
.8
TS0058L3 LTO_ONSITE LTOCLASS 1,483,636 0.5 Full
.4
TS0064L3 LTO_ONSITE LTOCLASS 1,723,151 54.2 Full
.6
TS0065L3 LTO_ONSITE LTOCLASS 1,019,795 0.8 Filling
.7
TS0066L3 LTO_ONSITE LTOCLASS 1,234,565 43.1 Filling
.5
TS0071L3 LTO_ONSITE LTOCLASS 1,420,100 41.3 Full
.2
TS0072L3 LTO_ONSITE LTOCLASS 880,091.6 49.2 Full
TS0074L3 LTO_ONSITE LTOCLASS 623,384.8 18.4 Full
TS0075L3 LTO_ONSITE LTOCLASS 1,235,389 21.1 Full
.0
TS0076L3 LTO_ONSITE LTOCLASS 762,938.0 8.0 Filling
TS0080L3 LTO_ONSITE LTOCLASS 1,769,899 28.4 Full
.8
TS0082L3 LTO_ONSITE LTOCLASS 1,191,080 25.1 Full
.2
TS0083L3 LTO_ONSITE LTOCLASS 740,481.6 46.5 Full
TS0089L3 LTO_ONSITE LTOCLASS 838,982.7 59.5 Full
TS0094L3 LTO_ONSITE LTOCLASS 553,961.6 2.6 Full
TS0095L3 LTO_ONSITE LTOCLASS 1,598,759 53.7 Full
.2
TS0096L3 LTO_ONSITE LTOCLASS 1,041,456 26.3 Full
.9
TS0097L3 LTO_ONSITE LTOCLASS 1,644,987 4.4 Full
.1
TS0102L3 LTO_ONSITE LTOCLASS 1,634,167 30.1 Full
.3
TS0103L3 LTO_ONSITE LTOCLASS 762,938.0 18.0 Filling
TS0104L3 LTO_ONSITE LTOCLASS 1,379,494 5.2 Full
.8
TS0105L3 LTO_ONSITE LTOCLASS 1,079,984 7.0 Full
.7
TS0110L3 LTO_ONSITE LTOCLASS 1,302,045 6.4 Full
.1
TS0111L3 LTO_ONSITE LTOCLASS 1,485,831 58.6 Full
.2
TS0113L3 LTO_ONSITE LTOCLASS 1,614,859 4.3 Full
.3
TS0115L3 LTO_ONSITE LTOCLASS 1,934,572 42.9 Full
.4
TS0129L3 LTO_ONSITE LTOCLASS 1,199,072 32.1 Full
.7
TS0132L3 LTO_ONSITE LTOCLASS 1,051,930 49.0 Full
.4
TS0133L3 LTO_ONSITE LTOCLASS 762,938.0 12.6 Filling
TS0135L3 LTO_ONSITE LTOCLASS 1,001,999 67.4 Full
.9
TS0136L3 LTO_ONSITE LTOCLASS 1,375,523 30.9 Full
.0
TS0138L3 LTO_ONSITE LTOCLASS 1,121,986 95.9 Filling
.1
TS0139L3 LTO_ONSITE LTOCLASS 1,262,370 26.5 Filling
.9
TS0142L3 LTO_ONSITE LTOCLASS 1,252,321 42.3 Full
.6
TS0146L3 LTO_ONSITE LTOCLASS 930,726.9 64.6 Full
TS0148L3 LTO_ONSITE LTOCLASS 1,011,683 25.3 Full
.2


Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------- ---------- --------- ------- ------
TS3310 AHQ102L3 Private Data 4,114 LTO
TS3310 AHQ103L3 Private Data 4,138 LTO
TS3310 AHQ106L3 Private Data 4,104 LTO
TS3310 AHQ108L3 Private Data 4,120 LTO
TS3310 AHQ111L3 Private Data 4,111 LTO
TS3310 TS0004L3 Private Data 4,126 LTO
TS3310 TS0005L3 Private Data 4,122 LTO
TS3310 TS0006L3 Private Data 4,133 LTO
TS3310 TS0007L3 Private Data 4,102 LTO
TS3310 TS0012L3 Private Data 4,139 LTO
TS3310 TS0013L3 Private Data 4,098 LTO
TS3310 TS0015L3 Private Data 4,116 LTO
TS3310 TS0017L3 Private Data 4,153 LTO
TS3310 TS0019L3 Private Data 4,118 LTO
TS3310 TS0023L3 Private Data 4,128 LTO
TS3310 TS0026L3 Private Data 4,117 LTO
TS3310 TS0027L3 Private Data 4,112 LTO
TS3310 TS0031L3 Private Data 4,121 LTO
TS3310 TS0034L3 Private Data 4,135 LTO
TS3310 TS0035L3 Private Data 4,108 LTO
TS3310 TS0037L3 Private Data 4,140 LTO
TS3310 TS0042L3 Private DbBackup 4,123 LTO
TS3310 TS0043L3 Private Data 4,130 LTO
TS3310 TS0046L3 Private Data 4,115 LTO
TS3310 TS0048L3 Private Data 4,144 LTO
TS3310 TS0054L3 Private Data 4,127 LTO
TS3310 TS0056L3 Private Data 4,137 LTO
TS3310 TS0058L3 Private Data 4,132 LTO
TS3310 TS0064L3 Private Data 4,099 LTO
TS3310 TS0065L3 Private Data 4,129 LTO
TS3310 TS0066L3 Private Data 4,110 LTO
TS3310 TS0071L3 Private Data 4,136 LTO
TS3310 TS0074L3 Private Data 4,141 LTO
TS3310 TS0075L3 Private Data 4,151 LTO
TS3310 TS0076L3 Private Data 4,124 LTO
TS3310 TS0080L3 Private Data 4,145 LTO
TS3310 TS0082L3 Private Data 4,109 LTO
TS3310 TS0083L3 Private Data 4,097 LTO
TS3310 TS0089L3 Private Data 4,150 LTO
TS3310 TS0094L3 Private Data 4,106 LTO
TS3310 TS0095L3 Private Data 4,131 LTO
TS3310 TS0096L3 Private Data 4,096 LTO
TS3310 TS0097L3 Private Data 4,119 LTO
TS3310 TS0103L3 Private Data 4,149 LTO
TS3310 TS0104L3 Private Data 4,148 LTO
TS3310 TS0105L3 Private Data 4,142 LTO
TS3310 TS0110L3 Private Data 4,105 LTO
TS3310 TS0111L3 Private Data 4,107 LTO
TS3310 TS0113L3 Private Data 4,103 LTO
TS3310 TS0115L3 Private Data 4,146 LTO
TS3310 TS0129L3 Private Data 4,134 LTO
TS3310 TS0135L3 Private Data 4,154 LTO
TS3310 TS0136L3 Private Data 4,143 LTO
TS3310 TS0138L3 Private Data 4,125 LTO
TS3310 TS0142L3 Private Data 4,113 LTO
TS3310 TS0146L3 Private Data 4,101 LTO
TS3310 TS0148L3 Private Data 4,147 LTO

 

[MAG]

Yes, you definitely need to get rid of some of the filling tapes. Make sure you never have more than the number of actual tape drives you have, preferably less. For all of the tapes when are virtually empty do a move data to tidy them up and then retry the migration.
Eg,
move data ts0036l3

Also make sure that your migration is not running at the same time as any backup stgp process from disk pool to lto_onsite.

 

[jellyfish]

Yes, you definitely need to get rid of some of the filling tapes. Make sure you never have more than the number of actual tape drives you have, preferably less. For all of the tapes when are virtually empty do a move data to tidy them up and then retry the migration.
Eg,
move data ts0036l3

Also make sure that your migration is not running at the same time as any backup stgp process from disk pool to lto_onsite.

does it matter if for legal reasons we have to keep data for up to 10 years, would that be a reason alot of tapes are being used it and data is never expiring.

 

[MAG]

It won't matter as regards the normal backup operations and all of these almost empty Filling tapes. If you need to keep data for that long you're better off doing monthly archives (or whatever timespan you want) so that the 10 year data stays separate from the normal day to day backups.

 

[jellyfish]

Yes, you definitely need to get rid of some of the filling tapes. Make sure you never have more than the number of actual tape drives you have, preferably less. For all of the tapes when are virtually empty do a move data to tidy them up and then retry the migration.
Eg,
move data ts0036l3

Also make sure that your migration is not running at the same time as any backup stgp process from disk pool to lto_onsite.

thanks will run the move command to free up some tapes, will the tapes automatically go to scratch or will I have to force this by running the update vol command.

 

[MAG]

No, once the move data command has finished the tapes will automatically go to Scratch.
I noticed that you've got a tape that's empty - TS0035L3. You may need to delete the volume manually if the move data command doesn't work with it.

 

[kfiresmith]

does it matter if for legal reasons we have to keep data for up to 10 years, would that be a reason alot of tapes are being used it and data is never expiring.

Moving data between tapes in the same pool is A-OK, you just can't destroy the data haha!

I use move data all the time to shuffle data on "filling" tapes. If you're keeping data for 10 years, you'll be ejecting tapes to make room for scratch. This can get tricky, and add to the amount of manual effort in reclaiming tapes in the event stuff finally starts aging off of them!

 

[ajbarth]

I didn't see anyone ask about maxscratch setting for the pool versus the value in 'number of scratch tapes in use'. you can have all the scratch tapes in the world, but if your pool is set to use only 10, then that's all you get.