Work Management Standards › Backing-Up › Backing Up Live Application Systems

Backing Up Live Application Systems

One of the goals of the library usage standards discussed is to separate objects into libraries by role. This helps to minimize the amount of backing up that has to be done.

Execution objects and source for live application systems should be kept in separate libraries that need be backed up only when a change is made to them.

The strategy adopted for backing up live application data objects, in particular, the choice of whether journaling, Save Change Objects (SAVCHGOBJ) or Save Objects/Libraries (SAVOBJ) is used, will depend on the following considerations:

• Volume and volatility. Journaling incurs a performance overhead that may become critical on large volumes.
• Transaction complexity. Simple transactions may not need journaling.
• Batch/Interactive job mix. Journaling is less suitable for high volume batch applications.