Applying journaled changes
With this synchronization method, you use system journaling capabilities to synchronize the information in journaled objects on your test and existing systems.
The applying journaled changes method is most commonly used either by installations that already use and understand journaling or by installations that have very large journaled objects.
The advantage of this method is that you save and restore only the changes that occur to a journaled object, not the entire object. The disadvantage of this method is its complexity.
Journaling before saving
You must set up journaling on your existing system before you perform the save operation from which you build your new systems. When you start journaling for an object, the system assigns a journal ID number (JID) to that object. An object must have a JID before you save it from your existing system and restore it to your new system or you will not be able to apply journaled changes to the test version.
Conceptually, when you use journaling to synchronize objects, you perform the following steps to establish a synchronization point:
- On your existing system, follow these steps:
- Save security data to get a current copy of user profiles and private authorities.
- Save new journal receivers (that contain entries that you have not yet applied on your new system).
- Save any new objects (that do not yet exist on your new system).
- On your new system, follow these steps:
- Restore user profiles (to get any new profiles and current authority information).
- Restore any new objects.
- Restore journal receivers.
- Apply journaled changes from the journal receivers.
- Restore authority to any new objects.
Here is an example of the steps for using journaled changes to synchronize systems: