I was also told that the INCREMENTAL processing expires deleted databases.
The SELECTIVE only backs up what's there and if you never run the
INCREMENTAL any deleted databases will still be there as active and won't
expire.

I have a client that I'm still trying to convince that hourly archivelog
backups and weekly selective full backups just aren't enough.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Del Hoobler
Sent: Tuesday, August 26, 2003 2:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for Domino 6. ver 5.1.5.1


Lisa,

It should be detecting those new databases.
Each time a "DOMDSMC INCREMENTAL" backup is run
it should be picking up "new" databases (as well as
logged databases that the DBIID has changed or
non-logged databases that the internal time stamp
has changed on.)

Something else must be wrong in your scheduled
scripts or in the location of the new databases
...or something like that.

I would call IBM support so that some traces
can be gathered to find out if those databases
are being "registered" by Domino.

You should not have to run a SELECTIVE backup
to pick those up... the INCREMENTAL backup
should be picking them up.

Thanks,

Del

----------------------------------------------------

I have just discovered something interesting, which in this case is not
something good.


We have transaction logging on, and TDP incrementals run nightly against
the logged databases.  It was my understanding that the incremental would
"turn into" a selective if the DBIID changed or it encountered a new
database.

It's not doing that.  The admins are putting new user databases onto the
server, and they are not being caught by the incremental.  I guess they
don't get 'caught' until we do a compact/selective.

Did I misunderstand the documentation, or is this not working as designed.
Do I tell my notes admins to run a selective backup every time they create
a new database?

tia

lisa