Scenario: Journal management

 

This topic provides the steps that a fictitious company, JKL Toy company, takes as it implements journal management on its iSeries™ server.

Sharon Jones, the system administrator for the JKL Toy Company, is responsible for backing up their servers and making sure that their servers can be recovered in the event of a natural disaster or system failure. As security officer, she is also responsible for ensuring the security of the servers.

The JKL Toy Company has a network that consists of a development server, a production server, and an http server. Click on a server on the diagram below for a description of the system and the journaling strategy Sharon uses.

• JKLPROD
  JKLPROD is the system that JKL uses for all of their customer orders and where their business applications are installed (inventory control, customer orders, contracts and pricing, accounts receivable). The information about this server is extremely critical to their business and changes often.

• JKLINT
  JKLINT is the system that JKL uses for their Web site and e-mail. While this data is critical to their business, it is fairly static.

• JKLDEV
  JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often.

 

Parent topic:

Local journal management

Related tasks
Scenario: Backup using BRMS

Related information
Scenarios: Remote journal management and recovery