Won't running INACTIVATELOGS immediately after a full backup potentially
break PIT restores from the prior full backups?  To preserve PIT restore
capability, it seems to me INACTIVATELOGS should be scheduled just before a 
full backup, rather than after, and perhaps less frequently.  Also, for
PIT restores from older backups, don't you need to keep all transaction
logs at least as long as the oldest full backup?

thanks,

Kent Monthei
GlaxoSmithKline





"Del Hoobler" <hoobler AT US.IBM DOT COM>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
24-Jul-2003 09:34
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>




        To:     ADSM-L

        cc:
        Subject:        Re: TDP Domino and transaction logs

Bill,

The logs are uniquely named based on the log name
and logger id. You are correct, they won't be
"inactivated" (forced inactive) until you run the
INACTIVATELOGS command.

When you run the INACTIVATELOGS command, DP for Domino
will determine what logs are necessary for the
current list of *active backups. It will inactivate
the remainder.

If you run a FULL backup, followed by an INACTIVATELOGS
command once per week, all logs prior to that should be inactivated...
That means the older logs will be marked *inactive.

When that happens, the policies for the
VERDELETED/RETONLY will become effective for those inactive logs.

I hope that helps.

Thanks,

Del

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

> But I thought that the logs were uniquely named and wouldn't go away
until
> you did an INACTIVATELOGS command?? And if my oldest backup is 35-days
then
> the INACTIVATELOGS would only remove the logs that are older than that
full
> backup?? Or am I missing something here...(Which wouldn't suprise me!!!)