occupancy #'s are real time
auditocc #'s only update at "audit license"
Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 925-8045
Ben Bullock
<bbullock@MICRON.
COM> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> Occupancy differences.
09/29/2004 03:30
PM
Please respond to
"ADSM: Dist Stor
Manager"
Here is a strange one:
We all see differences between the "q auditocc" command and the
"Q occ" command, but they are typically rather small.
On this one host, where all it does is archive some data that
resides on a NetApp, there is a significant difference. The occ shows
about 8.8TB and the auditocc shows 51TB:
tsm: TSMHOST3>q occ BOFS8-X
Node Name Type Filespace FSID Storage Number of Physical
Logical
Name Pool Name Files Space
Space
Occupied
Occupied
(MB)
(MB)
---------- ---- ---------- ----- ---------- --------- ---------
---------
BOFS8-X Arch /netapp/b- 1 NOCOPY_TA- 143,633 8,874,745
8,874,745
ofs8/vol- PEPOOL .70
.70
/bofs8vo-
l2/X_-
backup
tsm: TSMHOST3>q auditocc BOFS8-X
License information as of last audit on 09/29/04 at 14:21:04.
Node Name Backup Archive Space-Managed
Total
Storage Storage Storage Used
Storage
Used (MB) Used (MB) (MB)
Used (MB)
----------------------------------- --------- --------- -------------
---------
BOFS8-X 0 51,824,41 0
51,824,41
9
9
Quick math of the number of tapes and their capacity comes up
with about 50TB. So it looks like the auditocc is on the money, but the
occ is way off...
Anybody else seen anything like this?
Thanks,
Ben
|