Item Subject: Bug in AIX DSMC?
     Remember ! If you have compression on bytes transfered will hopefully
     be far less than bytes allocated ;-)   Also... are you looking at
     dsmaccnt.log data ?  If not set accounting on and pull the info from
     there... if you check out the AIX ADSM Administration GUIDE and search
     for dsmaccnt.log you will find 17 (? +-1) fields of information... off
     the top of my head I can't remember but I believe 3 or 4 of the fields
     relate to KB of data blah... so they report various figures... also
     you will notice with the accounting data you can figure out how much
     data transmitted it misc ADSM overhead...
     To double check if you have compression off is create (if space is
     available) a 1/2 GB file and backup... note the reported KB then copy
     that file 3 times to give you a couple of GB's and back all up with
     one cmd and check those figures...
     later
          Dwight



______________________________ Reply Separator _________________________________
Subject: Bug in AIX DSMC?
Author:  ADSM-L at unix,sh/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    5/1/96 8:53 AM


Is there a known bug in the dsmc distributed with ADSM v2.1 (level 2 I
think for AIX 3.2.5) when it comes to reporting the number of bytes
transferred from the client to the server?

When the volume of data is low during an incremental backup, on the
order of 1 Gigabyte or less, the reported volume is reasonably
accurate.  However, when the volume is much higher, on the order of 18
GB, then the report is way off -- it reports 3 GB.

Is this a known bug?

Tom