Things to check first would be the logs from these runs... due to the time
and bytes transferred both going down on the to tape runs I'd guess it just
sent less data.  A,B,C,Duh you say ;-) could be caused by "retries" of
files... Hey, if it sends a 10 MB file 10 times before it gets it unchanged,
that is still only 10 MB  backed up but 100 MB sent and the time required to
send 100 MB.

Were these run during the same time of the day or one after the other which
might have put the "totape" runs say after work hours ? ? ?

just a thought

Dwight

> ----------
> From:         ANGEL BUGARIN[SMTP:ANGEL.BUGARIN AT MAIL.SPRINT DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Friday, March 24, 2000 1:09 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      What's the big difference?
>
> Hello everyone.
>
> I have an NT client of which two management
> class defined.
>
> NT0_DEFAULT
>       - Destination pool: NT0_DISKPOOL
>
> NT0_DIRECT_TO_TAPE
>       - Destination pool: NT0_TAPEPOOL
>
> Both MC are defined with 65-days retain only backup version.
>
> I ran two FULL backups for each MC. The following are the results:
>
> NT0_DEFAULT:
> 1.    17,677 objects inspected
>       14,777 objects backed up
>       1.35 GB bytes transferred
>       00:50:44 elapsed processing time
>
> 2.    17,817 objects inspected
>       14,781 objects backed up
>       1.35 GB  bytes transferred
>       00:57:59 elapsed processing time
>
> NT_DIRECT_TO_TAPE:
> 1.    17,685 objects inspected
>       14,778 objects backed up
>       954 MB bytes transferred
>       00:41:03 elapsed processing time
>
> 2.    17,753 objects inspected
>       14,780 objects backed up
>       954 MB bytes transferred
>       00:40:40 elapsed processing time
>
> What's going here? Why are there more bytes transferred
> using NT0_DEFAULT and less bytes for NT_DIRECT_TO_TAPE?
>
> Can someone please explain this to me?
>
> TIA,
> Angel
>
>
>
>
>
>
>