Home > AS/400 Tips > iSeries administrator tips > The ins and outs of journaling -- Part III

	iSeries 400 Tips:	EMAIL THIS

	TIPS & NEWSLETTERS TOPICS

	ISERIES ADMINISTRATOR TIPS The ins and outs of journaling -- Part III Ron Turull 03.30.2005 Rating: -4.25- (out of 5) Digg This!     StumbleUpon     Del.icio.us    How to use a journal for disaster recovery [TABLE] Journals, like mirroring, can be used as protection against loss of data from a disk crash. The trade-off is this: Journaling uses a lot less disk space than mirroring, since it is only protecting files (which is where most of the system activity, i.e. data changes, takes place). However, this is also a disadvantage because, again, only files are protected. In addition, set-up and recovery require a few more manual steps. For maximum protection, use the following steps. Journal set-up and save process Every critical file (which is most files) should be journaled. You can journal multiple files to the same journal, but use caution when doing so because this will introduce another level of complexity (or confusion, as the case may be). The following describes the steps required to set up journaling for a single file: [TABLE]			[IMAGE]

Recovery procedure
After a disk crash or other failure that renders a file unusable, use the following steps to recover that file:

Restore objects in the correct order
Similar to when you use triggers or

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT iSeries administrator tips Translating Linux for IBM i admins: Using GUI to make it easy Translating Linux for IBM i admins: Working with jobs and networking OpenOffice: What to know before making the transition from Microsoft Office OpenOffice: An enterprise open source solution Database performance comparisons on IBM i Translating Linux for IBM i admins: User profile commands Modern System i reports using Client Access Tips for installing Lotus Domino server on a System i partition The iSeries Blog has a new home on IT Knowledge Exchange Virtualization for IBM i: Backups Data backup, storage and retrieval on iSeries Authority restrictions on the AUTL on backup/test systems and AUTL on live system Perform a full system backup without user profile QSECOFR Faster backup method for System i Solve problems concerning the ALLOW OBJECT DIFFERENCES parameter when restoring a library System i backup not advised using network NETBACKUP How to clear expired BRMS created *SAVF files from System i Restore a full system backup from the production partition to the test partition Tivoli Service Manager 6 released with DB2 integration and dedupe Remove a media with a *PERM expiration date from the inventory Booting iSeries from internal or external sources Data backup, storage and retrieval on iSeries Research

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

referential integrity, when you use journaling and perform a restore you must ensure that certain objects are restored in the proper order so that journaling can be re-established automatically. When you need to restore a file that is journaled, along with its associated objects (i.e., logical files, journal and journal receivers), use the following order:

To make things simple, put the journal and receivers in the same library as the files. When configured this way, the system will automatically restore them in the proper order if you restore the entire library (using the RSTLIB command). If they are in different libraries and you do not restore the objects in the above order, you will have to re-establish journaling manually, which may include re-attaching receivers and/or restarting journaling for files.

Note: The restore procedure just discussed is only for when you need to restore a file and its associated journal and receivers. In the recovery procedure discussed earlier, we assumed that the journals and receivers did not have to be restored because they were in another ASP and were not affected by the disk crash.

-----------------------------------
About the author: Ron Turull is editor of Inside Version 5. He has more than 20 years' experience programming for and managing AS/400-iSeries systems.

Rate this Tip To rate tips, you must be a member of Search400.com. Register now to start rating these tips. Log in if you are already a member. Submit a Tip DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.