I do believe that the accounting data gives both the "Amount of data, in kilobytes, communicated between the client node and the server during the session" and the "Amount of backup files, in kilobytes, sent by the client to the server". Mr. Lindsay Morris has a free script on his ServerGraph page that will format out the accounting data. The ANE4961I gives the Total number of bytes transferred during the session, and that includes changing retries.
For the amount of data migrated, you can query the SUMMARY table for ACTIVITY=MIGRATION and total up the BYTES column. I would not rely on the summary table to the client backup sessions. There have been so many APARS and supposed fixes for this, that trying to figure out which server and client version actually fix the problem is confusing and a moving target. Plus I belive this is again the total bytes transferred, including retries, and not actually how much data was backed up. Bill Boyer DSS, Inc. "A life?...COOL!! Where can I download one?" -- ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Stapleton Sent: Friday, December 27, 2002 11:10 AM To: [EMAIL PROTECTED] Subject: Re: How much data is being backed up per client? On Fri, 2002-12-27 at 09:21, Cook, Dwight E wrote: > Best source of info on client traffic is the dsmaccnt.log file in the tsm > server install directory. This is not actually true. The accounting log counts the number of bytes passed from client to server, including all retries. If you have a 3GB file that retries 4 times for a backup, and then fails, the accounting log will note 12GB of data when 0 bytes actually backed up. Looking through the server activity log for ANE4961I messages give a more accurate picture. -- Mark Stapleton ([EMAIL PROTECTED])