In a disaster recovery restore from our SAVLIB *NONSYS the *PRINT report said all the logical files were restored, but the JOBLOG said they weren't. There were a number of object types omitted from the restore completely. These were Data Dictionaries, DTAQs, USRQs and Journals. Can you advice how these should be restored and do how do we get back our logical files?
It is important to restore objects in a certain order. OS/400 will take care of this if dependent objects are in the same library, but if you have for example, physical files in one library and logical files in another, you are responsible for restoring the physical files before you restore the logicals.
When you do a SAVLIB *NONSYS, libraries are saved in alphabetical order and are restored in the same order when you do a RSTLIB *NONSYS. This may be the cause of the problem you are having.
If you have related objects in different libraries, you need to restore them in this order:
1. Journals before journaled objects
2. Journals before journal receivers.
3. Physical files before logical files.
You may also want to check to see if you save access paths, too. <SAVLIB xxx ACCPTH(*YES)>
Note: the default is *NO.
MORE INFORMATION ON THIS TOPIC
Ask the Experts yourself: Our backup & recovery gurus are waiting to answer your questions.
Search400.com's targeted search engine: Get relevant information on backup & recovery.
Check out this Search400.com Featured Topic on backup & recovery.
Dig Deeper on iSeries disaster recovery and business continuity
Related Q&A from Ken Graap
The BRMS Network feature allows a BRMS system to connect to other BRMS systems via a network, and enables a user to consolidate media such as backup ... Continue Reading
The only option to correct damage preventing file journaling is to use the RCLSTG command. Continue Reading
IBM's iSeries Backup and Recovery manual answers many questions related to system backup and disaster recovery. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.