Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!jetson!john
From: john@jetson.UPMA.MD.US (John Owens)
Newsgroups: comp.unix.xenix
Subject: Re: Xenix Restore Command
Summary: "restore r" of an incremental can only be used after "restore r" of a full
Keywords: Xenix Restore Command
Message-ID: <237@jetson.UPMA.MD.US>
Date: 23 May 89 18:22:40 GMT
References: <131@tdl.UUCP>
Distribution: usa
Organization: SMART HOUSE Limited Partnership
Lines: 27

In article <131@tdl.UUCP>, raulin@tdl.UUCP (Raulin Olivera) writes:
> restored 2 file systems /root and /u from my cpio full system
> backup.  At that point the installation looked fine.  I then
> ran 2 restores from level backups that had been created prior
                           ^ level what?  level > 0?
> to the 2.2.3 install.  	!!!STEPPED ALL OVER MY /U FILESYSTEM!!!

You can only restore incremental backups (with restore r) on top of
restores of the previous full backups and all incrementals with lower
level numbers.  When you do a "restore r", it replaces all the files
into their original inode locations.  When you extract from cpio, the
files will end up with completely different inode numbers.

How did you manage to get an incremental backup from the date of a
cpio anyway?  backup to /dev/null after running cpio?

Summary:  Use backup exclusively for full and incremental backups for
disaster recovery and any other full-filesystem restores.  Use cpio
for special-purpose backups that you're likely to want to restore all
or part of onto a good, existing filesystem.  And only use "restore r"
on a filesystem that's either completely empty (fresh from mkfs) or
has just had another "restore r" done on it from a lower-level backup.

Good luck!
-- 
John Owens		john@jetson.UPMA.MD.US		uunet!jetson!john
+1 301 249 6000		john%jetson.uucp@uunet.uu.net