Eliza,

I'm in a similar situation to yourself, but I've never run across this
problem with the Connect Agent.

Depending upon your network bandwidth and or type of ADSM Server,
compression is usually better set to off.

We have an ATM backbone but it may aswell be token ring when it comes to IP
on MVS. When backing up to MVS I always turn compression on for better
peformance.
When I backup to AIX my throughput is double if not triple with compression
OFF.

The schedule log doesn't show how much compression took place, however in
all cases so far compression has resulted in less data being transferred.
This is more appreciable when doing a full backup.

Nathan


        -----Original Message-----
        From:   Eliza Lau [SMTP:lau AT VTCAT.CC.VT DOT EDU]
        Sent:   Friday, February 19, 1999 2:18 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Connect Agent for Exchange - Compression

        ADSMers,

        We have been testing the ADSMConnect Agent for Microsoft Exchange
1.1.  We are
        planning to put it into production in a couple of weeks.  My
question is does
        anyone know if compression really works.  I turned it on yesterday,
and the
        amount of data transferred is actually larger than that of the day
before when
        compression was off.  (Both backups are full backups.)  This could
be due to
        extra log files.  The schedule log doesn't report any compression
rate either.
        As far as I can tell no compression was done.  We are testing it
against a test
        database with not much activities going on, so the IS and DIR store
should not
        have grown much in a day.

        Thanks in advance,

        Eliza Lau
        lau AT vt DOT edu
        Virginia Tech Computing Center