LifeWays Operating Procedure

Transcription

1 SUBJECT: Computer Systems Backup GOVERNING AGENCY POLICY: Disaster Recovery and Data Backup CATASTROPHIC EVENTS: The LifeWays computer systems are backed up nightly. The systems backed up are the IBM AS400 and the Windows NT server. The Novell 3.12 server is not currently being backed up and backup will be started again soon. The most important back up is the AS400. This backup MUST occur. AS400 BACKUP Description: Currently the AS400 Backup routines have been set to run automatically. User intervention, unless errors occur, is to change the tape on a daily basis. Backups are called for the day being saved although the actual time of backup is the following early morning. For example Tuesday back up runs Wednesday early AM, Monday backup runs Tuesday early AM. Prepare for Backup Routine Day Time NOTFBCKUP SCD *ALL 04:40:00 *WEEKLY INITAPE SCD *ALL 04:45:00 *WEEKLY PREBACKUP SCD *ALL 04:55:00 *WEEKLY The above three routines prepare the AS400 for Backup. NOTFBCKUP sends a message to all screens still logged onto the AS400 warning of backup and to finish their job and log off the system. INITAPE initializes the backup tape (must be 8mm, 160m). The PREBACKUP ends the QINTER subsystem. Weekly Reboot STOPTCP SCD *TUE 04:56:00 *WEEKLY CLRVWS SCD *TUE 04:59:00 *WEEKLY MONBACKUP SCD *TUE 05:00:00 *WEEKLY WKLYREBOOT SCD *TUE 06:20:00 *WEEKLY STARTSVRS SCD *TUE 07:48:00 *WEEKLY STARTTCPIP SCD *TUE 07:45:00 *WEEKLY Computer Systems Backup Page 1 of 5

2 The AS400 is rebooted (Initial Program Load, IPL) once a week. This must be done on a recurring basis. The AS400 releases and reinitializes computer assets during the reboot, checks for file damage and attempts corrections among other things which occur during an IPL. After the prepare for backup jobs have completed the above series of jobs (commands) are submitted to the AS400. STOPTCP stops all TCP communications connections. CLRVWS clears the virtual workstation devices. MONBACKUP begins the backup of selected libraries on the AS400 to include CMIS5FILES and programs and query libraries. When the backup completes WKLYREBOOT shuts the AS400 down and performs a reboot (IPL). The IPL usually takes approximately an hour. STARTSVRS then executes to start all the AS400 servers for connections to the networks. STARTTCPIP starts the AS400 TCPIP services for the workstations to be able to address the AS400. TUEBACKUP SCD *WED 05:00:00 *WEEKLY WEDBACKUP SCD *THU 05:00:00 *WEEKLY THURBACKUP SCD *FRI 05:00:00 *WEEKLY FRIBACKUP SCD *SAT 05:00:00 *WEEKLY POSTBACKUP SCD *ALL 06:10:00 *WEEKLY All other days the above jobs process automatically by the AS400. After the prepare for backup jobs have ran, the daily backup is then executed. The POSTBACKUP is ran once the backup has completed which starts the QINTER subsystem allowing interactive connections to the AS400. (No backup is ran for Saturday or Sunday. Upgrades when required are usually done on the weekend and a full system is ran prior to any upgrade. The flow of the jobs is through the JOBQ for QBATCH. This flow allows for the submitting of jobs in a sequence at a specific time. This allows us to submit the backup and should it take more time the next job waits in the queue until the working job completes, then moves from the queue to active and runs. Should the active job error, all jobs in JOBQ QBATCH wait until corrective action is taken. As soon as the active job is corrected the next job in the queue IMMEDIATELY executes. ALL checks will need to be performed from the system console in the computer room. First thing in the morning the backup needs to be checked. With AS400 command options enter the following command: DSPMSG ROBBC and then enter. You should see the following messages, the exception being the day for the backup job, for a successful backup completion. Messages not needing a reply (similar to the following) Job /ROBBC/POSTBACKUP completed normally on 02/27/98 at 06:10:04. Job /ROBBC/POSTBACKUP submitted for job schedule entry POSTBACKUP number Job /ROBBC/THURBACKUP completed normally on 02/27/98 at 05:52: Computer Systems Backup Page 2 of 5

3 Job /ROBBC/THURBACKUP submitted for job schedule entry THURBACKUP number Job /ROBBC/PREBACKUP completed normally on 02/27/98 at 04:55:01. Job /ROBBC/PREBACKUP submitted for job schedule entry PREBACKUP More... number Job /ROBBC/INITAPE completed normally on 02/27/98 at 04:45:45. Job /ROBBC/INITAPE submitted for job schedule entry INITAPE number Job /ROBBC/NOTFBCKUP completed normally on 02/27/98 at 04:40:03. Job /ROBBC/NOTFBCKUP submitted for job schedule entry NOTFBCKUP number Should there be other messages about abnormal completions they will also be displayed. Abnormal completion should be reviewed. In most cases nothing will need to be done at this time. However if a message shows tape or hardware problems a service call may be required. Should the backup fail for whatever reason the system currently will need to be made available for the users as soon as possible. For all backups EXCEPT the Monday backup which occurs early Tuesday morning, go to WRKACTJOB, under QBATCH you should find the job that has not completed with a message. Review the message, primarily looking for hardware problems which may have to be serviced and the normal action would be to cancel the job. When the job cancels the backup aborts and the next job submitted to the job queue will execute. Once the backup completes, or aborts the next job restarts QINTER so all can get into the AS400. This process takes approximately 5 minutes. Monday backup which is checked Tuesday morning has additional jobs waiting in the JOBQ. At the completion of the Monday backup the AS400 will execute the next job which performs an IPL (reboot). An IPL on the AS400 takes approximately one hour to complete. Should the Monday backup fail and the AS400 needs to be available for use DO NOT cancel the active job, yet. First, enter WRKJOBQ QBATCH enter. You will see a listing of the other jobs waiting to execute. Enter a 4 next to the WKLYREBOOT job to end this process which is waiting. Press the F5 key to refresh the screen view to verify that the WKLYREBOOT job is no longer waiting. Second, enter WRKACTJOB enter, move to the MONBACKUP under the QBATCH and view the message and cancel the job. As soon as this job cancels the other jobs in the JOBQ will execute, restarting TCP and the AS400 Servers. Third, enter the following command: STRSBS and hit the F4 key, this will bring up another screen. Enter QINTER in the subsystem description line and press enter using *LIBL already in the Library option. This will restart QINTER allowing logins. As stated before, these checks and monitors need to be performed from the system console located in the computer room. Should a backup fail this is the ONLY terminal that will allow Computer Systems Backup Page 3 of 5

4 logins until the QINTER subsystem has been restarted or the system IPL has completed which should automatically restart QINTER. To exchange the tape on the AS400 press the blue button on the tape drive. The tape lights should blink and the tape will be ejected from the tape drive. Place the tape in the case with the date of the backup. Insert the next tape into the tape drive, push the tape into the drive gently until the drive pulls the tape inside the door and drops into place. The tape lights will blink and the tape is ready. Windows NT Server BACKUP Description: The LifeWays NT systems are as follows: Lifeways_nt1 Primary Domain Controller HP Lhpro Main control for network. Data bases, backup software, remote access. Lifeways_nt2 Secondary Domain Controller Dell 2200 poweredge Intranet, SQL Lifeways_nt3 Secondary Domain Controller Dell 2200 poweredge Exchange Lifeways_nt4 Secondary Domain Controller Dell 2200 poweredge located Hillsdale Connectivity to Jackson. The HP file server (lifeways_nt1) is backed up daily. This backup process automatically executes at approximately midnight every night. Currently the Lifeways_nt1, and selected directories from secondary servers are saved to tape. Changes to the backup of the NT server are accomplished through the program Segate Backup Exec. This program is also used to monitor the backups. To check the backup on the NT file server do the following: Logon to the server.(lifeways_nt1) Press the START button and select PROGRAMS Highlight SEGATE BACKUP EXEC and select Highlight SEGATE BACKUP EXEC and select, this step will execute the program and should display a screen with tabs across the bottom. Select the JOB MONITOR tab which will show a listing of the latest backups with the most current and next scheduled at the top. The percent (%) complete for last nights backup should be 100%. If not review any messages. Unlike the AS400 the NT server backup does not shutdown the system and does allow for the backup of files with users active on the system without giving file locks as the AS400 does. To change the tape for the NT server, press the little black button located on the lower front of the tape backup unit. The tape will rewind (unload) when the light turns green, raise the lever Computer Systems Backup Page 4 of 5

5 located below the tape, this will eject the tape from the drive. Exchange the tape with the next tape to be used. Insert the tape all the way in, should "almost" click into place, then lower the lever to lock the tape into place. The tape is now ready for to use. AS400 Normal Backup Process 1. Logon to the AS400 console 2. DSPMSG ROBBC enter 3. Look for something similar to the following: (the day, dates, time and job number will change) Job /ROBBC/THURBACKUP completed normally on 02/27/98 at 05:52: Remove last nights backup tape, change the date on the tape box. 5. Insert tape to be used for next backup. MUST be a 160m 8mm tape. Other tapes will not work. 6. Logoff the AS400 console 7. The old tape is stored upstairs and is rotated. 8. Next tape to be used should have the oldest date. Windows NT Server Backup Process 1. Logon to the Server console 2. Execute the Segate Backup Exec program 3. Execute the Segate Backup Exec option 4. Select the Job Monitor Tab. Look for 100% completion of the backup 5. Remove the tape from the tape unit 6. Insert next tape to be used for backup. 7. Logoff the Server console 8. The old tape is stored upstairs and is rotated. 9. Next tape to be used should have the oldest date/day. HISTORY Effective date: October 22, 1997 Revised: Reviewed: Computer Systems Backup Page 5 of 5