We've worked with a number of customers using the agent.  Wait for John
Stephens' response to this.

Re. number 1) below.  You do not need to actually stop the server to use
the ba client to backup everything once per week.  Set you management
class/backup copygroup to dynamic, and back it up while running.  This
works fine, with the exception that notes that are "saved" while the backup
is occurring might not be in a usable state.  This is fixed the next time
the agent is run.  The .nsf file is corrupt, only the note that underwent
change during the backup.  I recommend you prove this to yourself with your
customer before recommending it as gospel.  We tested it and didn't have
any problems.

800 GB is way too much data, unless you bring multiple streams and multiple
network paths to bear on the problem.  Then, perhaps, you can get the
elapsed backup time down to something reasonable.

Backup of Lotus notes is not the real problem in any event.  Lots of ways
to do that.  The real problem is restoring.  Single mail messages or a
single database shouldn't pose much of a problem either.  However, a large
restore, lots of databases and lots of notes with long intervals between ba
backups, will be problematic.  The good news, with notes replication and
other techniques, you probably don't need to do that very often, if ever.
 It needs to be considered, though, or you're not really doing your job.



Kelly J. Lipp
Storage Solutions Specialists, Inc.
www.storsol.com
lipp AT storsol DOT com
(719)531-5926