Yep, working as designed... this is why you might want to alter your
changingretries or start excluding the changing files from backups (since
they probably in the end aren't gettin backed up anyway)
Dwight
-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 25, 2000 10:05 AM
To: [EMAIL PROTECTED]
Subject: Bytes Transferred Statistics from AIX nodes
Once a week (or so), I go through the ADSM (MVS 3.1.2.50) server activity
log file, and strip out the "AN?4961I Bytes Transferred" messages to get an
idea of how much data is being transferred/backed up.
Recently, we noticed that a new node (AIX) was transferring more data than
the total of it's file systems (32GB on a 21GB system).
We turned on VERBOSE logging on the node to see what the !@#$%^&* was going
on.
The only thing we could come up with was the issue of RETRIES on busy
files. The log would show
"....transfering....changed....retrying.......transfering.....changed....ret
rying.....".
When we added up the RETRIES bytes plus the total of the filesystem, it now
adds up.
So, why is the "total bytes transfered" including RETRIES ? Does it
actually send the data, then go back and check to see if the file it just
transfered changed since it sent the data (kinda doubt it <g>) and keep
retry/sending until it runs out of retries and then gives up ?
Or is this a client bug ? This is V3.7.2.0 !
