ADSM-L

Antwort: Re: [ADSM-L] q filespace / q occ

2005-09-13 02:35:25
Subject: Antwort: Re: [ADSM-L] q filespace / q occ
From: Dierk Harbort <Dierk.Harbort AT BUERGEL DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 13 Sep 2005 08:35:06 +0200
Hi Maurice,

thanks for your statement; the point is, that tsm tells me about db2
filespace always 100% util - backing up with the API always works like
this. So I
think, this must be the amount of data backed up by db2/tsm API. I thought,
it should tell me the real amount of data - but it seems I was wrong ?!
Basicly the MBs shown in a TSM q filesp are ok in my system, I can see this
due to comparing the hdd space and the util % from other nodes/pathes.
So now I'm thinking about Allens statement:
DB2 is showing/calculating its 100% util in a buggy way ?? And for db2 via
API only q occ shows the right amount of util ?

And IBM told me, the api for db2 with fixpack 9 is not realy ok, so there
could be trouble without the newest fixpack 10 - but we won't install that
at
this time, it is 1 week "old" and we are no "beta testers".

So the result for me now is: q filesp for all, but not for db2 via API -
therefor I have to use q occ?

Regards,
Dierk


Allens statement:
Trust the Q occ.  For most conventional filesystems, the q filespace
information is pretty good, but if you're doing anything odd, the numbers
will
be way off.
I don't know how DB2 calculates its' filespace size, but I've got a DB2
database which actually backs up at about 120GB, whose filespace size is
reported at 35TB.  That's close to the total size of 'backup' type files
I've
got in TSM for that DB, but not particularly close.
As another example, I've got a filesystem with 8M files on it, with a
directory structure similar to
/big/big00
    /big01
    /big02
    /big03
    /big04
    /big05
    /big06
    /big07
    /big08
    /big09
Each of those directories is a virtualmountpoint, and each of the
filespaces
associated with the virutalmountpoint reports the size and pct_utilized of
the
enclosing physical filesystem.
The occupancy numbers, on the other hand, are accurate.







|--------+----------------------->
|        |          "ADSM: Dist  |
|        |          Stor Manager"|
|        |          <ADSM-L AT VM DOT MA|
|        |          RIST.EDU>    |
|        |                       |
|        |          12.09.2005   |
|        |          17:20        |
|        |          Bitte        |
|        |          antworten an |
|        |          "ADSM: Dist  |
|        |          Stor Manager"|
|        |                       |
|--------+----------------------->
  
>---------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                        |
  |       An:     ADSM-L AT VM.MARIST DOT EDU                                   
                                               |
  |       Kopie:                                                                
                                        |
  |       Thema:  Re: [ADSM-L] q filespace / q occ                              
                                        |
  
>---------------------------------------------------------------------------------------------------------------------|




Hi Dierk,

You are comparing two very different queries.

q filespaces gives you the filespace info of the node, so you can see i.e.
c:\ with 4GB capacity and 40% util. This means that the c-drive of that
node
is 4GB in size and 40% full. This gives you absolutly no info about the
backup....
q occ gives you the amount of files and MB's of data that is backuped.

So if you backup a filespace with 16TB of data, but you exclude 75%, you
shall have 4TB of data + the extra versions backuped up and that's what you
see if you do a q occ....

Regards,
Maurice

----- Original Message -----
From: "Dierk Harbort" <Dierk.Harbort AT BUERGEL DOT DE>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, September 12, 2005 3:48 PM
Subject: [ADSM-L] q filespace / q occ


> Hello, TSMers !
>
> I'm confused about the space a node uses in tsm: The q filespace for this
> node tells me about 16,123,456,8 (16TB). But, if i use q occ for the same
> node tsm tells
> me only about 6,123,456.9 (6TB).. I can't see many details, it is an db2
> node serving tsm via api interface. So it seems to me like a black box,
> sent from db2 node into tsm.
> Where is my mistake ? Any idea is welcome !
>
>
> Regards,
>
> Dierk
>

<Prev in Thread] Current Thread [Next in Thread>
  • Antwort: Re: [ADSM-L] q filespace / q occ, Dierk Harbort <=