Geoff

I believe that the purpose of the incremental schedule for Domino
backups is to 'catch' any new db's (.nsf files) that have been created
since the last Full backup or to backup any db's whose DBIID has
changed. Certain Domino functions cause the DBIID to change and the
outcome of these functions warrant a backup of that particular db.
Compaction or compression is such a function.

Therefore I would say that a node doing an incremental to a new server
with no previous backups, would treat all the db's as new and a Full
backup would occur.

Would it be possible to export the node from the current server to the
new server on the day of the migration.  Obviously if the occupancy is
considerably large, it may not be achievable in a day.

It might be possible to export only the active data. Thus giving the new
server a copy of all the db's and negating the need for a full, but also
minimising the amount of data on the new server.

I must admit to never having tried the export node allactive with a
domino filespace before, but I have no reason to believe that it would
not operate any differently.

Leigh

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gill, Geoffrey L.
Sent: 02 May 2006 05:16
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Domino Backups

I was wondering if someone could answer this that has knowledge having
done
something similar. The scenario is a Domino server does a full backup of
all
DB's on Sunday. Sometime during the week the node will be migrated to
now
back up to a new TSM server. The next schedule is actually an
Incremental.
Will it really be doing a FULL since it has never backed up to this
server
or will it really do a small incremental?



I'm trying to avoid a manual full if it doesn't need it. We do want a
full
for all DB's so we don't have a full on one system and incrementals on
another.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:  <mailto:geoffrey.l.gill AT saic DOT com> geoffrey.l.gill AT saic DOT com