🚀 go-pugleaf

lemson@fnbc.com (David Lemson) writes:
> rich@pencil.cs.missouri.edu (Rich Winkel) writes:
>> Eh?  I've been dumping next's to sun exabyte for a couple months.
>> Is there something I need to know???  It seemed to run without errors.
> 
> From my tests, it does seem to work.  The only hitch is that you cannot  
> restore those files on a Sun using SunOS restore command.  You must use  
> rrestore from a NeXT.  restore on the Sun core dumps when it tries to 
> read that dump block!
> 
Well, After all this talk of how easy things are, I decided to
give it another shot. Here is a (long) summary...

1) Set up an "Exabyte server" which is a Sun 4/330 named "pacific".

2) Have about 6 NeXTs I want backed up, and I also want pacific backed
up.

3) I was able to get rdump working from NeXTs to pacific just fine.

4) I was *not* able to get rrestore working. (Hints??)

5) I changed my script to use rdump.old instead.

6) I can now rdump.old to pacific (the Sun), and restore locally on the
Sun (if all I need is a file or two.)

7) If I have a *real* crash, I can always move the Exabyte drive to the
dead NeXT, and restore.old from there.

Unfortunately, I noticed that restore on the Sun gives a few warning
messages when doing a "restore tf" on the NeXT rdump.old format
files. The warnings look like: "Warning: .. not found".

I am curious if anyone has successfully used rrestore from a NeXT with
an Exabyte (we have an EXB-8200) connected to a Sun. Although you
could always move the Exabyte drive to the NeXT with a problem, this is
really a pain if all you need are a few files. My restore needs are
commonly to retrieve an old file or subdirectory, not to restore an
entire disk drive. 

Whenever I get this all figured out, I will post a few scripts.
(Special thanks to Rich Winkel for help so far...)

Regards,

John
-- 
John Robison - Oceania Health Care Systems 
john@oceania.com - NeXTMail Gladly Accepted