AS/400

AS/400 Full-System Backup

Introduction
Periodic full-system backup tape sets are stored in the fire-proof safe at WPCP and/or the fireproof file
cabinet in the Finance Dept.
A full-system backup should be run quarterly, preferably over a long weekend. Do not run this during a
normal work week. If problems arise, users will not be able to sign on! This provides a set of tapes
containing virtually everything on the machine. Specifically, the full-system option saves the following
items:
Licensed internal code
Operating system
Security data
Device configuration objects
All user libraries including those containing licensed programs
All documents and folders
Distribution and mail objects (Not applicable to our system!)
All directories
The full-system backup must be run from a terminal, not a workstation. Workstation sessions will be
unavailable during the backup, because the process places the AS/400 in restricted mode. Run the backup
from the DP office terminal under QSECOFR signon.
When the process is started, the full-system option will stop all subsystems. After the backup has
finished, the controlling subsystem will be restarted. Once started, the controlling subsystem should start
all other subsystems. Subsystems can be started manually should any one of the required subsystems fail to
start. Reference the listing at the end of this document.
A full-system backup requires more than one tape. As of this writing (09/07/1998) the backup required
three 2.5 Gb tapes. You should initialize at least one more tape than used on the last set before beginning
the backup. This avoids the extra time required for the system to initialize a tape during the backup.
The operator should be familiar with use of the Alt-SysRq key combination to acquire a command line.
During the backup, the operator will have to access QSYSOPR's message queue. Alt-SysRq is the only
way to get to the command line from inside the backup program.
Preparation
The IBM manual suggests the operator print a series of reports prior to running the full-system backup.
These are described in AS/400 Periodic System Reports and can be run prior to the backup day.
You should notify all users the AS/400 will be unavailable during the scheduled backup weekend. This
helps to prevent users from starting lengthy processing (such as a payroll or audit process).
Clean the AS/400 tape drive prior to running the backup, and before inserting each subsequent tape.
Experience has shown if this is not done, the backup system will stop somewhere in the third tape and
request the drive be cleaned. The IBM wet-system cleaning kit is stored on the shelving in the CPU
room above the monitors.
Initialize a set of tapes for use during the backup. Do not use the QIC1000 tapes. Use only the 2.5 Gb
tapes purchased with the model 500 machine.

Running the Backup
Stop Automatic IPL
From the command line, execute GO POWER and verify the machine is not set to IPL during the
backup. If there is an auto-restart set up for the time frame of the system backup, remove it - just to be on
the safe side!
User jobs
Verify all users are signed off. Use WRKACTJOB to check the status of user job queues. If a process
is running, the backup will end it. User jobs are listed with the user's signon under the User column.
System jobs have system names such as QSYS. There will always be system jobs running at the beginning
of the backup.
The SAVE menu
The steps that follow will run the full-system backup as an unattended process. This means the operator
need not be present during the backup. However the operator must check the progress of the backup from
time-to-time to change tapes and reply to the change-tape message.
Initialize and label a set of tapes. Place the first tape in the tape drive and stack the remaining tapes on
the AS/400.
Signon as QSECOFR. From the command line type GO SAVE and press Enter. From the SAVE menu
command line type 21 to select option 21. (This option is not visible on the initial SAVE display, but
appears on a subsequent display if you press PgDn). Read the displayed text. This explains precisely
what the process will and will not do. Press Enter.

Fill in the fields that pertain to our in-house process:

Device = TAP01
Prompt for commands: NO
Check for active files: NO
Message queue deliveries: *NOTIFY
Press Enter to begin processing.
About a minute after Enter is pressed the first system attention tone will sound. This tone is issued as the
SAVSYS command shuts down the various subsystems. Verify this has occurred by executing DSPMSG
QSYSOPR from a command line.
After the first tape has been filled, an attention tone is sounded and the screen displays a message that
reads "Waiting for reply to message on message queue QSYSOPR" Press Alt-SysRq then type
DSPMSG QSYSOPR. If prompted for the message queue name on the next screen, enter *SYSOPR.
Remove the tape from the tape drive and replace it with the next tape in the labeled series. Wait for the
tape drive "busy" lamp to go out, indicating the tape has bee properly tensioned and rewound. This may
take a few minutes. After the busy lamp goes out, return to the console terminal and type G to reply to the
message prompt. Press Enter. Wait a few minutes to ensure the system does not prompt for any additional
messages. Verify the tape drive busy lamp is lit (this may also take a few minutes).
In general, allow several hours for the system to write data to each tape. Until the process is complete
the system will remain in restricted mode, so the operator can start a tape in the evening and return the
following morning to change the tape.
When the process has completed the console will display the following message: Save or restore
option completed successfully. From a command line, type DSPMSG QSYSOPR and verify there are no
unanswered system messages. Then from a command line type WRKSBS and press Enter. The following
subsystems should be
displayed:

QBASE
QSERVER
QSPL
QSYSWRK
Q1PGSCH
If any one of these is not present, you may start it with the STRSBS command.
Alternatively, you can execute the GO POWER command and enter a scheduled automatic shutdown
and IPL to begin as soon as you have removed the last tape. This is preferable, since the automatic IPL will
ensure all subsystems are restarted without operator intervention.
Post-Backup
After verifying the subsystems have restarted, you must restart TCP/IP. restart the NetSoft Router, and
restart the line printer print server. After IPL contains complete instructions for restarting TCP/IP, and
contains a link to the page that describes restarting the NetSoft Router.