HP3000-L Archives

November 1999, 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:
Re: Image log files
From:
Lee Gunter <[log in to unmask]>
Reply To:
Lee Gunter <[log in to unmask]>
Date:
Mon, 8 Nov 1999 08:42:18 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines) 
As long as the database being logged is not enabled for rollback recovery, you
may even place the log files on a different volume set from the database;
otherwise, I agree with Mark in that log files should reside on a different
device from the database if at all possible.  Also, the entire log file set
should be backed up at least nightly.
----
Lee Gunter                    The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
----
Opinions expressed are solely mine.




From: [log in to unmask] on 11/08/99 07:44 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: [HP3000-L] Image log files




Gary Nolan sez:

>Logging to disc is great as long as you don't lose ldev 1 (as we
>found out the hard way).

Why limit your log file to LDEV 1? If you limit the log file to
a spindle that does not contain your databases, you should be
protected in the event a disk fails - either you lose the
database, or you lose the log file, but not both.

ATOM RSS1 RSS2