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:
From:
"Newman, Kevin:" <[log in to unmask]>
Reply To:
Newman, Kevin:
Date:
Mon, 8 Nov 1999 10:39:46 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
I thought that this was the exact reason to setup different volumes, just to
protect your data so that a hardware failure wouldn't wipe you out.

If you have a separate volume for your databases and you loose ldev 1, can't
you just re-create/re-build/restore ldev 1 or do you still loose that other
volume when ldev 1 goes away?

Kevin "I thought that I knew how it worked!?!" Newman

> -----Original Message-----
> From: Gary Nolan [SMTP:[log in to unmask]]
> Sent: Monday, November 08, 1999 8:53 AM
> To:   [log in to unmask]
> Subject:      Re: Image log files
>
> This is the kind of mess we already got into. We have our logfiles on ldev
> 1
> and the data bases split among the other 3 drives. We have only a small
> 947
> with 2 1gig and 2 2gig drives and no private volumes. When we lost ldev 1
> the logfiles were clobbered and the data bases are on the other drives
> cannot be recovered when you have no ldev1 (catch 22). Paranoid me having
> been burnt once by this does not intend to burnt again.
> While I have implemented the copying to PC procedure for now, I  am still
> not happy with it and hope somebody will let us spend the $$ on a raid
> solution.
> If anybody has a way to allow me to open the logfile and pull records from
> it as they are  written to it  I would be interested to hear how to do
> this.
>
> Gary Nolan
>

ATOM RSS1 RSS2