Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!caip!lll-crg!lll-lcc!vecpyr!tflop!mac
From: mac@tflop.UUCP (Mike Mc Namara)
Newsgroups: net.unix-wizards
Subject: Re: 4.2BSD restore(8)
Message-ID: <224@tflop.UUCP>
Date: Mon, 5-May-86 21:06:17 EDT
Article-I.D.: tflop.224
Posted: Mon May  5 21:06:17 1986
Date-Received: Thu, 8-May-86 20:02:37 EDT
References: <2066@hao.UUCP> <801@oliveb.UUCP> <974@tektools.UUCP> <1631@wucs.UUCP> <14840@onfcanim.UUCP>
Reply-To: mac@tflop.UUCP (Mike Mc Namara)
Distribution: net
Organization: ESL, Inc., Sunnyvale, CA.
Lines: 24
Keywords: 4.2BSD restore


	Consider: 

	My disk head has crashed.  I call DEC in. They fix the disk. I get my
	dump tapes.  The most recent full backup tape can not be read (tape errors).
	I get the next previous tape. I do a restore -r.  I then get the various
	incrementals up to that point where the full faulty dump was made.  I 
	restore them.  I have now built the filesystem up to just before that
	dump which cannot be read.  I try to read the first incremental after
	that bad tape, but it can not be read (restore complains about dates...)

	Am I lost? is that info gone? This actually happened, and since the faulty
	full backup only had seen one week of storage time, the users were simply
	told that that week was lost, and no big problems.

	How could I have gotten restore to give me that post-unreadable-full-backup 
	info back on the system?  (short of cracking the tape itself.)

-- 
---------------------------------+--------------------------------------------
| Michael Mc Namara              | Let the words by yours, I'm done with mine.
| UUCP: dual!vecpyr!tflop!mac    | May your life proceed by its own design.
| ARPA: tflop!mac@ames.arpa      |
---------------------------------+--------------------------------------------