From owner-freebsd-hackers Wed Mar 4 16:15:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01185 for freebsd-hackers-outgoing; Wed, 4 Mar 1998 16:15:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA00731 for ; Wed, 4 Mar 1998 16:13:49 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 14661 invoked by uid 1000); 5 Mar 1998 00:20:01 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 04 Mar 1998 16:20:01 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: sbabkin@dcn.att.com Subject: RE: SCSI Bus redundancy... Cc: wilko@yedi.iaf.nl, tlambert@primenet.com, jdn@acp.qiv.com, blkirk@float.eli.net, hackers@FreeBSD.ORG, grog@lemis.com, karl@mcs.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Mar-98 sbabkin@dcn.att.com wrote: ... Self - Reminder; This is a FreeBSD, hackers mailing list. Now, Your solutions are workable, but they are user-space, application level solutions. If you are on a black box O/S with a black box DBMS, they are not only valid, but the only workable solution. If you are thinking of way to may FreeBSD, as na O/S better, so that applications can be relieved from this burden, then your solutions are less optimal. > No. If you use Online JFS, what you do: make your database > residing in one filesystem. This is a must. Then take another > 30G volume (the exact size depends on the intensity of changes, > this one estimates that no more than ~1/3 of blocks in your > original filesystem will be changed during backup) and mount it as > a "freeze" to your original filesystem. When some operation is done > on your original filesystem, the contents at the time of "freezing" > will be saved to the second volume. So when your backup reads the > "freezed" filesystem, it will take a proper block from either the > original or second volume. FreeBSD does not have, to date, a journaling file system, available in source under the Berkeley license. Even if it did, it will not solve the original problem of this thread, which was how to guarantee reliability in the face of a SCSI bus failure. > Yet better idea: don't store your database right in the filesystem, > store it in Oracle and you will get possibility of online backups > for free. Oracle for FREE? Where? >> This is a simplistic examples. Life is nastier than that. Can it be >> solved? Of course. With Unix? Yes, what do you think a 5ESS switch >> runs? >> With FreeBSD? Yes. As is today? No.... >> > Unless someone will make Oracle working on it :-) huh! ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message