Hello Folks

Here are some of the results we have encountered since migrating one of our
notes servers to the ADSMconnect agent.  The first half of the table
(02/03/98 - 02/14/98) is stats from the Backup/Archive Client, and the
second half (02/15/98 - 02/98) are using the ADSM connect Client.  We have
seen the backups go from about 4 hrs in duration to about 45 minutes.  Also
the data backed up has reduced from 6-9Gig to a much more managable
125-200Meg range. We also have two other servers (at present) which backup
via the Backup Archive agent which backup up 40Gig and 27Gig respectively.
I will be migrating them to the ADSMconnect agent in 1 week and 3 weeks
respectively.   So far we have been very impressed.

We also use the Scheduler service to initiate the backups on a nightly
basis by using a 'Command' format schedule.  The command is to start a
batch file which issues the command:
cd \win32app\ibm\adsm\agentln
dsmnotes incr * -subdir=yes -adsmpw=oursecretpassword
EXIT
This scheduling service has worked error free for the last 3 days.  Not a
lot of history, but good indications so far.

So far we do not have much experience with the restore scenarios with the
ADSMconnect agent, but from the testing, this does not seen to be a big
issue.  Just some more steps involved.  First restore the mail file from
the most recent Backup Archive (full file) backup and then restore the
incremental changes from the ADSMconnect backups.  With the ability to put
in date ranges with the restores using the ADSMconnect agent, this works
fine.  One key point to mention is that I restore via the command line
because if you use the GUI (on the server) is ties up the client until the
restore completes.  This can be an extended time depending on size of data
being restored, as well as the availability of the tapes required.....



(Embedded image moved to file: PIC21139.PCX)

If you have any other questions, let me know.....

Rob Middleton
IBM I/T Specialist