I would not expect them to be the same.  physical_mb (and I always get this
confused and have to look it up...) is the space occupied, including any
"dead" space inside aggregates.  logical_mb is the space occupied, not
including any "dead space" inside aggregates.

When a file is expired, if it is a small file living inside an aggregate on
a tape, the logical_mb count will drop, but the physical_mb count will not.
The physical_mb count will drop later when the tape is reclaimed; reclaim
squishes out the dead space inside aggregates as it goes.

Since your onsite and offsite pools have tapes that are not exact image
copies of each other, and the tapes reclaim at different rates/different
times, they should be somewhat different.  (Now if they're off by
terrabytes, I would worry...)
See if adding sum(logical_mb) to the query doesn't give you closer numbers.


************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************





-----Original Message-----
From: Ronnie Crowder [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 3:56 PM
To: [EMAIL PROTECTED]
Subject: Primary vs Backup Stg


Hopefully someone out there can help me.  What I was trying to do was check
to
see if my primary stg pool and copy storage pool contained the same
information.  The way I was checking was using a select statement in the
form:

select sum(physical_mb), sum(num_files) from occupancy where stgpool_name =
'ONSITE'

select sum(physical_mb), sum(num_files) from occupancy where stgpool_name =
'OFFSITE'

The number of files that come back are the same for both but the total size
is
not the same.  I can issue the backup stg pri copy preview=yes but it comes
back basically saying that the pools are the same.  Just wondering why the
offsite pool has a larger total than the onsite.  Could it be because of
data
compression??  The reason I ask is that I have another smaller TSM server at
another location and when I run the script on it, both number come back the
same.  Any comments would be appreciated.

Thanks

Reply via email to