For the second restore library, use the option(*new).  It will skip over
writing what was restored the first pass.  Can be a big time saver.

Christopher K. Bipes
Sr. Programmer/Analyst
CrossCheck, Inc.
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Jim Langston []
Sent: Wednesday, January 03, 2001 3:08 PM
Subject: Re: Oops Restore

I've done this type of restore before, and yes, you can restore the
libraries to other libraries, just do it twice.  Yes, twice.

Then it won't matter what order you do them in.  You will get errors
the first time you run it (logical can't be built over non existent
physical file, etc...) and you should get no errors the second time.

The first time through it will restore all the phsical files, and
some of the logicals, dependent on if the physical was there before
it go to the logical or not.

The second time it will over write the physicals and the logicals it
already did, and then it will restore the rest of the logicals since
the physicals are now there.

I follow this rule whenever I'm restoring any library, just run the 
command twice and forget about it.  Otherwise you're going to spend
a long time trying to figure out where your logicals are.


Jim Langston

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To subscribe to this list send email to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.