From owner-freebsd-questions Fri Sep 3 16:43:38 1999 Delivered-To: freebsd-questions@freebsd.org Received: from camelot.bitart.com (camelot.BITart.com [206.103.221.33]) by hub.freebsd.org (Postfix) with SMTP id 84AE415713 for ; Fri, 3 Sep 1999 16:42:38 -0700 (PDT) (envelope-from gerti@bitart.com) Received: (qmail 9664 invoked by uid 101); 3 Sep 1999 23:42:43 -0000 Message-ID: <19990903234243.9663.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Fri, 3 Sep 1999 18:42:42 -0500 To: grog@lemis.com, questions@FreeBSD.ORG Subject: Vinum mirror and strategies for root partition backup Reply-To: gerti@BITart.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, FreeBSD can't be booted from a Vinum drive. I am trying to find a setup that still gives me optimum safety with lowest possible downtime. I will use two disk drives of the same size. Is this strategy sound: - Install 3.2 with the usual slices on the first disk - Put identical slices on the second disk - Make /usr a vimnum drive, mirrored onto the second drive - Make /var a link to /usr/var - Use dump/restore to duplicate the / partition to the second drive (and do so each time something is modified on /) Now: - If the second disk fails, the system should just continue to work. - If the first disk fails, it can be replaced with the second disk and the system will work again. Is this strategy sound? Does vinum store 'absolute' drive info on it's drives, meaning would it get confused in the second case above where the first disk is replaced by the second disk? Thanks Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message