From owner-freebsd-questions Fri Jul 23 0:12: 7 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hermes.axis.de (hermes.axis.de [194.163.241.7]) by hub.freebsd.org (Postfix) with SMTP id 3799A14CB7 for ; Fri, 23 Jul 1999 00:12:01 -0700 (PDT) (envelope-from maret@axis.de) Received: from erlangen01.axis.de by hermes.axis.de via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 23 Jul 1999 07:12:04 UT Received: (private information removed) Message-ID: <91DA20EC3C3DD211833400A0245A4EA9BA1095@erlangen01.axis.de> From: Alexander Maret To: 'Greg Lehey' Cc: "'freebsd-questions@freebsd.org'" Subject: RE: vinum and disaster recovery Date: Fri, 23 Jul 1999 09:11:20 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, well I meant not really on a brandnew drive but on a new drive on which I already created a slice for vinum in the same size the old one was. How can I tell vinum to activate the new drive and copy all the data from the working drive to the new one. Do I have to "reload" the config file like doing "create -f /etc/vinum.config" or does vinum duplicate the configuration from the first drive and I only have to type "vinum start". Another question: Can I reactivate crashed drives without rebooting. I tried the following: I switched off the second drive and vinum went on running with the first one. After a while I switched the second drive back on and tried to reactivate it by typing "vinum start tmp.p1.s0". Unfortunately the only response was "unexpected argument" (or something like that - can't remember, sorry). How can I pull up drives which are marked as "crashed" and "faulty"? Can I tell vinum to resync all data on the drive? After a reboot everything worked fine and both drives were up again. But what happend while reinitializing vinum? Did vinum copy all changed data from the first drive to the second or what happened with the data which had changed during my "crash" of the second drive? Thanks for your help, Alex > On Thursday, 22 July 1999 at 9:38:17 +0200, Alexander Maret wrote: > > Hi, > > > > I have a mirrored vinum drive on a 3.2-R System. Everything works > > fine meanwhile but what happens if a drive fails? I think vinum > > will go on running only using the working drive. But how can I > > get the old data which is on the working drive on a brandnew drive > > to reactivate mirroring? Is "vinum start" enough for vinum to check > > both drives and reactivate mirroring? > > Not on a brand new drive. It would work if you removed the drive and > replaced it. I need to get my act together and document how to do > this, which will also involve some code. Watch this space. > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message