On Sat, Sep 01, 2001 at 04:39:55PM -0400, Declan Moriarty wrote:
> On Friday 31 August 2001 15:40, you wrote:
> > Some folks on this list use the scripts I developed for bare metal
> > restoration (see Linux Journal #79). There is a new script, make.fdisk
> > which should eliminate a lot of the typing in the recovery
> > process. The script is at
> > http://w3.trib.com/~ccurley/bare.metal.html#TOC63.
> >
> > I'd appreciate it if folks would look at the new script and beat it
> > over the head. Your comments are most welcome.
> >
> > The rest of the scripts and some supplementary material are at the
> > usual place, http://w3.trib.com/~ccurley/bare.metal.html.
>
> What sort of a restore does it cover? I'd have to nobble a system to restore
> it, wouldn't I? I just happen to have a disk loaded with linux which is
> surplus to requirements - What should I do to it before running your script
To get a complete test of the full suite, yes, the system would be
wiped. The restoration process is very invasive: it wipes out and
replaces the MBR, then builds new partitions, and puts file systems on
them.
You will need several of the scripts, not just the new one. there
should be a summary of what each one does toward the top. If not,
that's an error on my part; let me know and I will add one. Some
prepare the system for restoration, others are part of the restoration
process. Unfortunately, the original article where all of this is
explained is not available on line.
The restore process is two-staged. Given a completely wiped computer,
boot to tomsrtbt, mount the ZIP disk (previously prepared with other
scripts), cd to /mnt/root.bin and run make.dev.* as needed. Then run
restore.metadata. Then reboot. Then run the appropriate script, either
on the target or on the backup server, to restore the rest of the
system. Then reboot again.
The preparation is two-staged as well. Run make.fdisk with the device
files of your hard drive(s) to build some of the restore scripts,
make.dev.*. Then run save.metadata to back up a minimal system to a
ZIP drive. That should include data necessary to restore from the
second stage, e.g. the /bru directory if you have bru. Then back up
the whole kazoo as normal. I have scripts in the suite to do that over
the network using ssh.
The new script is non-invasive. To test it only, run it and see if the
two output scripts would work. Of course, they are invasive. Mostly
you would have to check the two files to see if together they build
the replacement partition table correctly and then make the
appropriate file systems in the appropriate partitions.
Hmm, maybe I should add a brief summary of what each script does to my
web page. Well, check back in a few hours.
--
-- C^2
No windows were crashed in the making of this email.
Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley
PGP signature
