We had the same problem. After during manuel backup I found that it was
because we have som Notes Databases (*.nsf) where there was a lot off
delete in.

One off the bases was 32 Mb, but after we replicateted the base, it was
only 2 Mb and the backup went fine.

I still have 2 bases I havent fixed yet, one is the log.nsf.

So all me problem was/is because of Notes not ADSM, so check your
databases. A fix on the bases did not help.

regards

Bent Lerager

> -----Oprindelig meddelelse-----
> Fra:  jteekens AT CIMAD DOT NL@POLITIKEN
> Sendt:        22. oktober 1998 15:22
> Til:  ADSM-L AT VM.MARIST DOT EDU
> Emne: Lotus Notes Connect backup takes more than 7 hours for 5 Gb of
> databases
>
>  <<...>>
> Our notes connect agent is very and very slow, al our other dommino
> server
> are preforming fine, but the BIG DOMINO(S01)
> server is not. I realy don't know what the problem could be. I
> included the
>  dsm.opt for out S01 node(Notes).
>
> There are 5 Gb of databases on our Notes server.
>
> At first I thought that it would be the tcpbuffer or windows size,
> increasing them had no effect.
>
> We got a 100Mbit backbone, a this moment, only for ADSM, so I can't be
> the
> network traffic.
>
> The domino(Notes) server is a IBM Netfinity 5500, PII 400Mhz with
> 256Mb
> mem, that should be enough for a Notes server.
>
> The preformance of notes is very good, so the server has a lot of
> extra
> processor time, why does he use it for ADSM backups?
>
> Our ADSM server, IBM RS6000 H10 with a 3575 library, sets the session
> in
> wait every now and them, for about one or two seconds.
>
> this is my dsm.opt:
> _______________________________
> nodename S01
>
> commmethod       TCPIP
> tcpport          1500
> tcpserveraddress 192.168.1.17
> tcpbuffsize      512
> tcpwindowsize    256
>
> COMPRESSION no
> PASSWORDACCESS Generate
> schedlogretention 5
>
>
> What can I do?