I think this may have been answered already today, but let me clarify just to
be sure.  My e-mail and network were a disaster today - I think the ghosts and
goblins were visiting Hartford big time today.

I also was talking about the server, although it could be run on a client.

On a Notes Server, you would still run the ADSM client as a regular scheduled
process.  It backs up all .NSF Notes DBs, through the API as has been
described already.

The rest of the Server should be backed up as you normally would with ADSM.
Of course you would exclude the NSF files from this.  every so often (perhaps
once a week) - you run a backup of the .NSF files with the regular ADSM
client.  This allows you to have a fallback point - if the whole DB is
destroyed, you can restore from the last regular backup, then restore the
individual documents through the server administrator.

Although it hasn't been stated, the two clients (the regular OS/2 client and
the Notes Agent) do not communicate with each other - they are independent.
That's the main reason why you do the weekly backups with the regular client,
and then do the documents with the Notes client.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: ADSM & Lotus Notes DBs
10-31-96 05:07 PM

-----------------------------------------------------------------------------
Thanks for the reply Jerry, but I should have been clearer, in that I'm
Thanks for the reply Jerry, but I should have been clearer, in that I'm
interested in backing up Notes DBs from servers, not clients.  I'm therefore
keen to find out how ADSM can tell if a DB has actually changed, or not, as
the
nightly server housekeeping tasks update the system tags every night,
regardless of whether changes have occured, or not.

Again, thanks in advance for any replies,
Alan Anderson,
Assistant Lotus Notes Administrator,
British Steel SP&CS, Scunthorpe, UK.