Disk pool migrating to itself not to tape

[Jarmstrong]

Ok, this one is really obnoxious and I think I should know the answer. Nevertheless...

Running TSM Server 6.2.1. My disk pool is devclass disk and the migration for it is stubbornly migrating the data from 1 volume on the storage pool to another volume on the storage pool. Even though my next storage pool is set to my tape pool, and even though I have available scratch tapes and tape drives, it keeps moving the date from one volume to another on my disk pool. What gives? My stgpool data is below:

Storage Pool Name: ITD_DISK_POOL
Storage Pool Type: Primary
Device Class Name: SEQDISK
Estimated Capacity: 3,243 G
Space Trigger Util: 53.7
Pct Util: 93.1
Pct Migr: 93.1
Pct Logical: 83.1
High Mig Pct: 80
Low Mig Pct: 40
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 3
Reclamation Processes: 4
Next Storage Pool: ITD_HIGH_DENSITY
Reclaim Storage Pool: ITD_HIGH_DENSITY
Maximum Size Threshold: No Limit
Access: Read/Write
Description: Primary Disk Storage Pool
Overflow Location:
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 40
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 100
Number of Scratch Volumes Used: 92
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: Yes
Last Update by (administrator): JARMSTRONG
Last Update Date/Time: 12/09/2010 13:53:25
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type: Threshold
Overwrite Data when Deleted:
Deduplicate Data?: Yes
Processes For Identifying Duplicates: 1
Duplicate Data Not Stored: 7,036 G (65%)
Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No



Storage Pool Name: ITD_HIGH_DENSITY
Storage Pool Type: Primary
Device Class Name: LTOCLASS2
Estimated Capacity: 849,466 G
Space Trigger Util:
Pct Util: 2.0
Pct Migr: 3.4
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description: LTO 4 Tape
Overflow Location:
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 55
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 500
Number of Scratch Volumes Used: 17
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): ADMINISTRATOR
Last Update Date/Time: 12/09/2010 10:05:22
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type: Threshold
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No



Device Class Name: SEQDISK
Device Access Strategy: Sequential
Storage Pool Count: 1
Device Type: FILE
Format: DRIVE
Est/Max Capacity (MB): 102,400.0
Mount Limit: 40
Mount Wait (min):
Mount Retention (min):
Label Prefix:
Drive Letter:
Library:
Directory: G:\TSMDISKPOOL,F:\TSMDISKPOOL
Server Name:
Retry Period:
Retry Interval:
Twosided:
Shared:
High-level Address:
Minimum Capacity:
WORM: No
Drive Encryption:
Scaled Capacity:
Last Update by (administrator): ADMINISTRATOR
Last Update Date/Time: 12/07/2010 10:12:38

 

[MTM]

What makes you believe that a migration is running? Do you see a migration process? Since this is a "File" type devclass, a reclamation could be running, moving files from one disk volume to another.

 

[Harry_Redl]

Hi,

just a question ... why this?
Reclaim Storage Pool: ITD_HIGH_DENSITY
This parameter is used when reclaiming TAPE based pool with single drive device class ... not your case.

Harry