Migration to Tape Pool Failed

Status
Not open for further replies.

gtp2008

ADSM.ORG Member
Joined
Jun 18, 2008
Messages
38
Reaction score
0
Points
0
PREDATAR Control23

Hi all,

I'm running TSM 6.1.2 on Windows 2003 Server SP2, with an HP MSL4048 tape library. I have a disk pool setup to migrate to the tape pool with a 70%/90% limits. However, my disk pool is now as 94% full, and it does not automatically flow/migrate over to the tape pool even though it is setup as the next stgpool.

Here is the q stgpool f=d results:

ANS8000I Server command: 'q stgpool f=d'
Storage Pool Name: ARCHIVEPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 0.0 M
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes:
Next Storage Pool: DISKPOOL
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?: No
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Volume Reuse:
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?:
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 10/16/2009 10:34:15
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Storage Pool Name: BACKUPPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 13,000 G
Space Trigger Util: 94.3
Pct Util: 94.3
Pct Migr: 94.3
Pct Logical: 99.9
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes:
Next Storage Pool: LTOBACKUP_POOL
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?: No
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Volume Reuse:
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?:
Last Update by (administrator): ADMIN
Last Update Date/Time: 11/02/2009 16:26:44
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Storage Pool Name: DISKPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 4.0 M
Space Trigger Util: 0.1
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?: No
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Volume Reuse:
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?:
Last Update by (administrator): ADMIN
Last Update Date/Time: 10/20/2009 11:32:01
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Storage Pool Name: LTOBACKUP_POOL
Storage Pool Type: Primary
Device Class Name: AUTOLTO_CLASS
Estimated Capacity: 0.0 M
Space Trigger Util:
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 0.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:
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 100
Number of Scratch Volumes Used: 0
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): ADMIN
Last Update Date/Time: 11/02/2009 16:26:13
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:
Storage Pool Name: SPACEMGPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 0.0 M
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?: No
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Volume Reuse:
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?:
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 10/16/2009 10:33:19
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:

And if I check for scratch tapes, using this command: select volume_name from libvolumes where status='Scratch' it shows me plent of scratch tapes.

Any ideas on how to proceed with my troubleshooting? Thank you.
 
PREDATAR Control23

Aroon,

Yes, everything is "online".

ANS8000I Server command: 'q path'
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: HPMSL4048
Destination Type: LIBRARY
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: LTO1
Destination Type: DRIVE
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: LTO2
Destination Type: DRIVE
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: LB4.1.0.2
Destination Type: LIBRARY
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: MT4.0.0.2
Destination Type: DRIVE
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: MT5.0.0.3
Destination Type: DRIVE
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: GENDRV_0.0.22
Destination Type: DRIVE
On-Line: Yes
Source Name: BACKUPSVR01_SERVER1
Source Type: SERVER
Destination Name: GENDRV_0.0.32
Destination Type: DRIVE
On-Line: Yes

ANS8000I Server command: 'q drive'
Library Name: HPMSL4048
Drive Name: LTO1
Device Type: GENERICTAPE
On-Line: Yes
Library Name: HPMSL4048
Drive Name: LTO2
Device Type: GENERICTAPE
On-Line: Yes
Library Name: LB4.1.0.2
Drive Name: MT4.0.0.2
Device Type: GENERICTAPE
On-Line: Yes
Library Name: LB4.1.0.2
Drive Name: MT5.0.0.3
Device Type: GENERICTAPE
On-Line: Yes
Library Name: LTOLIB3
Drive Name: GENDRV_0.0.22
Device Type: GENERICTAPE
On-Line: Yes
Library Name: LTOLIB4
Drive Name: GENDRV_0.0.32
Device Type: GENERICTAPE
On-Line: Yes
 
PREDATAR Control23

Anyone else have any ideas on how to troubleshoot this? Thanks.
 
PREDATAR Control23

Here you go - thank you very much.

Code:
ANS8000I Server command: 'q stg LTOBACKUP_POOL f=d'
                   Storage Pool Name: LTOBACKUP_POOL
                   Storage Pool Type: Primary
                   Device Class Name: AUTOLTO_CLASS
                  Estimated Capacity: 0.0 M
                  Space Trigger Util: 
                            Pct Util: 0.0
                            Pct Migr: 0.0
                         Pct Logical: 0.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: 
                   Overflow Location: 
               Cache Migrated Files?: 
                          Collocate?: Group
               Reclamation Threshold: 60
           Offsite Reclamation Limit: 
     Maximum Scratch Volumes Allowed: 100
      Number of Scratch Volumes Used: 0
       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): ADMIN
               Last Update Date/Time: 11/02/2009 16:26:13
            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:
 
PREDATAR Control23

~I suspect your problem is this:

Next Storage Pool: [......]

You appear to have no "Next storage pool" set on the diskpool, so it has nowhere to migrate *to*.

What is the name of your tape storage pool? Is that LTOBACKUP_POOL?

The statement you need to run is:

upd stgpool DISKPOOL NEXT=LTOBACKUP_POOL

...then see what happens.
 
PREDATAR Control23

~I suspect your problem is this:

Next Storage Pool: [......]

You appear to have no "Next storage pool" set on the diskpool, so it has nowhere to migrate *to*.

What is the name of your tape storage pool? Is that LTOBACKUP_POOL?

The statement you need to run is:

upd stgpool DISKPOOL NEXT=LTOBACKUP_POOL

...then see what happens.

I do have the next pool set, per my original post:

Code:
Storage Pool Name: BACKUPPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 13,000 G
Space Trigger Util: 94.3
Pct Util: 94.3
Pct Migr: 94.3
Pct Logical: 99.9
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 
[B]Next Storage Pool: LTOBACKUP_POOL[/B]
Reclaim Storage Pool: 
Maximum Size Threshold: No Limit
Access: Read/Write
Description: 
Overflow Location: 
Cache Migrated Files?: No
Collocate?: 
Reclamation Threshold: 
Offsite Reclamation Limit: 
Maximum Scratch Volumes Allowed: 
Number of Scratch Volumes Used: 
Delay Period for Volume Reuse: 
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: 
Last Update by (administrator): ADMIN
Last Update Date/Time: 11/02/2009 16:26:44
Storage Pool Data Format: Native
Copy Storage Pool(s): 
Active Data Pool(s): 
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type: 
Overwrite Data when Deleted: 
Deduplicate Data?: No
Processes For Identifying Duplicates: 
Duplicate Data Not Stored:
 
PREDATAR Control23

I would imagine that the log on the server should have something useful to say. Can you run the command

Code:
migrate stg backuppool
then post the log

Code:
q act begint=-00:05  search=migrate
you may have to search on the session number that the migrate process started to get more detailed information
make sure there is no sensitive info in that before you post!
 
PREDATAR Control23

How may tape libraries do you have. Looking at the the stg "LTOBACKUP_POOL" the estimated capacity is "0". You said you have lots of empty scratch tapes but does scratch tapes checkin to your target tape library? Please verify and post your q libvol

Thanks
 
PREDATAR Control23

I would imagine that the log on the server should have something useful to say. Can you run the command

Code:
migrate stg backuppool
then post the log

Code:
q act begint=-00:05  search=migrate
you may have to search on the session number that the migrate process started to get more detailed information
make sure there is no sensitive info in that before you post!
Code:
Date/Time: 11/20/2009 10:19:31
  Message: ANR1003I Migration retry delay ended; checking migration status for storage pool BACKUPPOOL. 
Date/Time: 11/20/2009 10:19:31
  Message: ANR0984I Process 714 for MIGRATION started in the BACKGROUND at 10:19:31. (PROCESS: 714)
Date/Time: 11/20/2009 10:19:31
  Message: ANR1000I Migration process 714 started for storage pool BACKUPPOOL automatically, highMig=90, lowMig=70, duration=No. (PROCESS: 714)
Date/Time: 11/20/2009 10:19:31
  Message: ANR1134E Migration is ended for storage pool BACKUPPOOL. There is an insufficient number of mount points available for removable media. (PROCESS: 714)
Date/Time: 11/20/2009 10:19:31
  Message: ANR0985I Process 714 for MIGRATION running in the BACKGROUND completed with completion state FAILURE at 10:19:31. (PROCESS: 714)
Date/Time: 11/20/2009 10:19:31
  Message: ANR1002I Migration for storage pool BACKUPPOOL will be retried in 60 seconds. 
Date/Time: 11/20/2009 10:20:31
  Message: ANR1003I Migration retry delay ended; checking migration status for storage pool BACKUPPOOL. 
Date/Time: 11/20/2009 10:20:31
  Message: ANR0984I Process 715 for MIGRATION started in the BACKGROUND at 10:20:31. (PROCESS: 715)
Date/Time: 11/20/2009 10:20:31
  Message: ANR1000I Migration process 715 started for storage pool BACKUPPOOL automatically, highMig=90, lowMig=70, duration=No. (PROCESS: 715)
Date/Time: 11/20/2009 10:20:31
  Message: ANR1134E Migration is ended for storage pool BACKUPPOOL. There is an insufficient number of mount points available for removable media. (PROCESS: 715)
Date/Time: 11/20/2009 10:20:31
  Message: ANR0985I Process 715 for MIGRATION running in the BACKGROUND completed with completion state FAILURE at 10:20:31. (PROCESS: 715)

and for q libv:

Code:
ANS8000I Server command: 'q libv'
Library Name: HPMSL4048
 Volume Name: 000001L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,013
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000002L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,017
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000009L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,004
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000013L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,037
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000016L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,044
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000025L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,020
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000033L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,043
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000077L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,034
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000094L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,024
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000104L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,045
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000105L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,009
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000106L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,001
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000107L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,042
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000108L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,038
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000109L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,030
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000110L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,027
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000111L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,031
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000112L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,022
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000114L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,033
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000117L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,029
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000123L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,006
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000124L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,021
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000125L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,012
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000126L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,016
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000127L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,019
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000133L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,032
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000134L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,007
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000135L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,036
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000136L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,041
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000137L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,039
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000138L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,010
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000139L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,014
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000140L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,018
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000141L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,011
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000142L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,015
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000143L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,028
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000144L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,025
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000145L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,002
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000146L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,005
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000147L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,008
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000148L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,023
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000149L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,040
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000150L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,035
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000151L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,026
 Device Type: 
Library Name: HPMSL4048
 Volume Name: 000152L3
      Status: Scratch
       Owner: 
    Last Use: 
Home Element: 1,003
 Device Type:
 
PREDATAR Control23

Mount limit = Drives. I've got two drives in the library. Thank you again for all of your help!

Code:
ANS8000I Server command: 'q devclass f=d'
             Device Class Name: AUTOLTO_CLASS
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: LTO
                        Format: DRIVE
         Est/Max Capacity (MB): 
                   Mount Limit: DRIVES
              Mount Wait (min): 60
         Mount Retention (min): 60
                  Label Prefix: ADSM
                  Drive Letter: 
                       Library: HPMSL4048
                     Directory: 
                   Server Name: 
                  Retry Period: 
                Retry Interval: 
                      Twosided: 
                        Shared: 
            High-level Address: 
              Minimum Capacity: 
                          WORM: No
              Drive Encryption: Allow
               Scaled Capacity: 
Last Update by (administrator): ADMIN
         Last Update Date/Time: 10/16/2009 13:29:03
             Device Class Name: DISK
        Device Access Strategy: Random
            Storage Pool Count: 4
                   Device Type: 
                        Format: 
         Est/Max Capacity (MB): 
                   Mount Limit: 
              Mount Wait (min): 
         Mount Retention (min): 
                  Label Prefix: 
                  Drive Letter: 
                       Library: 
                     Directory: 
                   Server Name: 
                  Retry Period: 
                Retry Interval: 
                      Twosided: 
                        Shared: 
            High-level Address: 
              Minimum Capacity: 
                          WORM: No
              Drive Encryption: 
               Scaled Capacity: 
Last Update by (administrator): 
         Last Update Date/Time: 10/16/2009 10:22:30
 
PREDATAR Control23

It looks there is mismatch. If you notice on your "q libv" your device type=generic and on "q devclass" your device type=lto. I suggest better call for support to help you with this one.
 
PREDATAR Control23

Ok - finally got this resolved. Had to contact TSM support, but even though the library, drives, and paths were defined properly, we had to delete them, and re-create them, and then everything started working properly again. Very strange.....
 
Status
Not open for further replies.
Top