Jim,

Ben's note was incorrect.  I think he was confusing Q AUDITOCC with Q
FILESPACE.  In any case, Q OCC and Q AUDITOCC should return virtually the
same numbers.  The differences are that Q AUDITOCC requires an AUDIT
LICENSE to be run, and the numbers are current as of the time that the
AUDIT was run.  Q OCC, on the other hand, does not require an AUDIT LICENSE
to be run.  Furthermore, Q OCC breaks down the occupancy by storage pool,
whereas Q AUDITOCC does not.  Both Q AUDITOCC and Q OCC reflect the same
thing: the amount of ADSM storage used.

If you want to get some idea of compression, you can do the following:

Issue QUERY FILESPACE ...  to determine the size of a user's disk, the
percent utilization, and therefore the amount of data on the disk.  You can
compare that to the numbers returned by Q OCC (or Q AUDITOCC).  This will
give only a very rough estimate, and can be misleading in some cases.  This
is because of the following caveats:
Not all user data may be backed up (due to excludes),
Some data may have multiple backup copies (due to versioning of files),
Deleted files are kept in ADSM for some time.
For a filesystem that is fairly static and has most of its data backed up,
the numbers can be a fair indicator of compression.  On the other hand, for
a filesystem that changes frequently or has lots of excludes, the numbers
will be misleading.

..Paul
--
At 11:29 AM 12/2/98 -0600, you wrote:
At 11:29 AM 12/2/98 -0600, you wrote:
>I saw Ben's reply and it occurred to me that I was using Q OCC when I
>should have been using Q AUDITOCC when I tell management what  a great
>job we're doing and how much client storage we are protecting.  So, I
>ran an AUDIT LICENSE, Q AUDITOCC and Q OCC and, despite the fact that we
>typically install clients with compression turned on, the numbers are
>practically identical.  I have 391.57983 GBytes for Q OCC and 391.576
>for AUDITOCC.
>
>We are running the VM V2 server.  I know that when I installed
>originally, compression worked because I couldn't even backup my own PC
>disk on the small test storage pool I initially installed with.  I
>turned on compression and it fit with room to spare.
>
>Any ideas?
>
>Jim Bohnsack
>Raytheon Systems Co.
>
>> ----------
>> From:         Ben Kokenge[SMTP:ben AT EDMS DOT NET]
>> Sent:         Wednesday, December 02, 1998 8:37 AM
>> To:   ADSM-L AT VM.MARIST DOT EDU
>> Subject:      Re: query occupancy for clients?
>>
>> NOTE:
>>
>> q auditocc -->  Gives amount of data originally stored on node.
>>
>> Q OCC --> Gives amount of data stored on server (so if the node
>> compresses
>>           50% of 10GB, q occ will show 5GB)
>>
>> It is a good method to see what kind of compression a node is doing
>> overall.
>>
>> -Ben
>>
>>
>>
>