HP3000-L Archives

February 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lee Gunter <[log in to unmask]>
Reply To:
Lee Gunter <[log in to unmask]>
Date:
Fri, 13 Feb 1998 07:25:37 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
From: [log in to unmask] on 02/12/98 06:46 PM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: FW: Opinions solicited on database repair "gotchas"




> Ditto ... I'm frequently asked why we bother with Image transaction
logging
> ... this is the reason.
>
> Lee Gunter

So, how do you insure that log files will be turned over at just before
each backup?  (I'm not familiar with the details true online operation.)

>> We do a :CHANGELOG on each logging identifier prior to :LOG ..., STOP.
Log files are backed up every night.  We don't use online backup.  All
logging cycles are restarted weekly.

Do you keep separate log files for each database?

>> In some cases ... one identifier logs four databases ... the rest are
set up as one per log ID.

Do you prohibit Operators from using store/restore directly (ie. only
usable from a command file)?  Do you keep Operators in a menu?

>> No, and no.  See my first post to this thread.  ;-)

Humans have a knack for finding some way to break anything.:-)

>> Sure ... but we can try to protect us (and our data) from ourselves!

ATOM RSS1 RSS2