VTL DD610 - Q VOL doesn't show the volumes.

turdb0

Active Newcomer
Joined
Apr 12, 2011
Messages
9
Reaction score
0
Points
0
Location
San Francisco
PREDATAR Control23

Hi I'm getting pretty close to getting this thing working considering I've only been playing with AIX and TSM for less than a month.:D

I have NFS mounted to run the disk backups to the DD610 temporarily so I'm not going to worry about that for now.

In regards to the VTL, I am able to add the volumes via the Tivoli Integrate Portal (TIP) and I see the 21 volumes I've added. However, I don't see any of those volumes when i run Q VOL. Am I supposed to be able to see the 21 volumes? They're all scratch. When I try to run a backup job, it gives me a "ANS5092S Server out of data storage space." error.

What did I do wrong here?
 
PREDATAR Control23

Q VOL won't show scratch volumes. Q LIBVOL <vtllib) should show volumes defined.

Make sure the backup node has your tape stgpool defined as it's primary pool. That message means that the primary pool for the node has no space.

FYI - after you use a VTL and run out of space, DD will recommend you use NFS storage instead of VTL. They also want "small" volumes. I doubt it really matters, but it sends you down a rat hole so you don't bother them....
 
PREDATAR Control23

Q LIBVOL shows the volumes as scratch.

tsm: TSMSERVER>q libvol

Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------------- ---------- --------- ------- ------
DDAIX610_VTL A99000 Scratch 1,000 LTO
DDAIX610_VTL A99001 Scratch 1,001 LTO
DDAIX610_VTL A99002 Scratch 1,002 LTO
DDAIX610_VTL A99003 Scratch 1,003 LTO
DDAIX610_VTL A99004 Scratch 1,004 LTO
DDAIX610_VTL A99005 Scratch 1,005 LTO

In ACTLOG i see the following:

ANR1405W Scratch volume mount request denied - no scratch volume available.
ANR0522W Transaction failed for session 4424 for node HPSMNIM (AIX) - no space available in storage pool DD_VTL and all successor
pools.
ANR0403I Session 4424 ended for node HPSMNIM (AIX).
 
PREDATAR Control23

Do these & post

q library
q devc
q stg
 
PREDATAR Control23

tsm: TSMSERVER>q libr ddaix610_vtl f=d

Library Name: DDAIX610_VTL
Library Type: SCSI
ACS Id:
Private Category:
Scratch Category:
WORM Scratch Category:
External Manager:
Shared: Yes
LanFree:
ObeyMountRetention:
Primary Library Manager:
WWN:
Serial Number: 3101830000
AutoLabel: Yes
Reset Drives: No
Relabel Scratch:
Last Update by (administrator): KENK
Last Update Date/Time: 04/18/11 12:59:46


tsm: TSMSERVER>q dev vtl f=d

Device Class Name: VTL
Device Access Strategy: Sequential
Storage Pool Count: 1
Device Type: LTO
Format: DRIVE
Est/Max Capacity (MB): 204,800.0
Mount Limit: DRIVES
Mount Wait (min): 1
Mount Retention (min): 1
Label Prefix: ADSM
Library: DDAIX610_VTL
Directory:
Server Name:
Retry Period:
Retry Interval:
Shared:
High-level Address:
Minimum Capacity:
WORM: No
Drive Encryption: Allow
Scaled Capacity:
Last Update by (administrator): KENK
Last Update Date/Time: 04/19/11 12:11:55

tsm: TSMSERVER>q stg dd_vtl f=d

Storage Pool Name: DD_VTL
Storage Pool Type: Primary
Device Class Name: VTL
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: VTL on Data Domain 610
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 15
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): KENK
Last Update Date/Time: 04/15/11 16:07:26
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
 
PREDATAR Control23

Situation resolved...

The problem was that the Virtual tape media was configured as type LTO1, and the drives were emulating LTO3 drives. For some reason, even though I initially specified 400GB tape media, it still configured it at LTO1, where it should have been LTO3. After I reconfigured some LTO3 tape media, the backup jobs worked. Kinda sucks that the logs doesn't specifically point out that the media type is not the right type and instead just gives a generic error.
 
PREDATAR Control23

Situation resolved...

The problem was that the Virtual tape media was configured as type LTO1, and the drives were emulating LTO3 drives. For some reason, even though I initially specified 400GB tape media, it still configured it at LTO1, where it should have been LTO3. After I reconfigured some LTO3 tape media, the backup jobs worked. Kinda sucks that the logs doesn't specifically point out that the media type is not the right type and instead just gives a generic error.


After I reconfigured some LTO3 tape media, the backup jobs worked. ------ would you please elaborate on that? i'm stuck in very similar place i think............
 
Top