Unsolved
This post is more than 5 years old
8 Posts
0
2055
September 23rd, 2009 22:00
Virtual Pools and TSM Storage groups
HI all,
Me again.
I've got an AIX 6.1 server running TSM which is used by our archiving app to access storage.
We've installed the Centera SDK 3.2 for AIX 5.3 (as there's no release for AIX 6.1 yet).
Working fine!!! Already defined the device classess and storage groups to access the Centera VP's.
Four VP's, each of different quotas. When I query my storage groups in TSM, I obtain the following:
Storage Device Estimated Pct Pct High Low Next Stora-
Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
Pct Pct
----------- ---------- ---------- ----- ----- ---- --- -----------
ARCHIVEPOOL DISK 8.0 M 0.0 0.0 90 70
BACKUPPOOL DISK 8.0 M 0.0 0.0 90 70
CMOD06_STG CMOD06YR 15,262 G 16.2
CMOD12_STG CMOD12YR 15,262 G 16.2
CMOD20_STG CMOD20YR 15,262 G 16.2
CMOD30_STG CMOD30YR 15,262 G 16.2
DB2_STG FILE 8 G 1.7 1.7 90 70
SPACEMGPOOL DISK 8.0 M 0.0 0.0 90 70
Those in bold are my Centera VP's each with the following quota's : 100G, 1500G, 200G and 100G respectively.
My question is why does TSM can see the whole space available on the Centera instead of seing just the allowed quota? Have anyone done this before?
All comments will be helpful...
Thanks,
amarcionek
1 Rookie
•
56 Posts
0
September 24th, 2009 10:00
Quotas are administrative only, in that what you set there is only visible to you the Administrator. As I understand it, it sends you an alert if those pools exceed that quota. They also aren't enforced, i.e. the app will never fail to write a clip because of a quota.
The API call exposed to us app vendors for space reporting reports total size of the Centera, no pool settings are exposed even though we use profiles. So multiple pool connections will all report the same space.
Tandeo
8 Posts
0
September 25th, 2009 00:00
Thanks