From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tyree, David
>            On the client I'm getting about 20+ gig of bytes
transferred
>during each backup. Only problem is that the server only has about 8-10
>gig of data on the entire thing.
>
>            The bytes transferred number comes from the dsmsched log
>file on the client side and mostly matches up with the numbers from the
>query node info.
>
>            I looked really closely at the dsmsched log and noticed
that
>I had a lot of 500-800 meg files that are not backing up on the first
>try because they are in use. Once it fails on the first try then I have
>it set to retry 5 times. I'll address the file in use issue separately.
>
>            It eventually gives up and moves on to the next file and
the
>same thing happens again.
>
>            It looks like the system is transferring a big chuck of the
>file then it fails and then restarts the transfer again and again. Just
>like it's supposed to. ach time it's actually transferring some data
>that counts towards the bytes transferred total but the file never
>really gets transferred. The end result is that my bytes transferred
>numbers are being inflated by incomplete transfers.
>
>            Is my reasoning for the inflated numbers correct?

Yes. You can alter your CHANGINGRETRIES parameter within the UPD
COPYGROUP parameters. (The default is 4, I believe.)

--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior TSM consultant