DR Recovery Script - Technical Document - BRMS-V12

Prepare AS/400 system for Client

Disaster Recovery Plan iSeries-AS/400

TABLE OF CONTENTS

3Overview

3Amendment History

3Before you Start:

3Step 1: Restore Licensed Internal Code

3Step 2: Restore Operating System

3STEP 3: Recover the BRMS/400 product and associated libraries

3STEP 4: Recover BRMS/400 related media information

3Step 5: Initialize BRMS/400

3Initialize BRMS Functional Authority

3Update BRMS System Name

3Initialize BRMS Devices and Media Library

3Step 6: Restore User Profiles

3Step 7: Restore BRMS Required System Libraries

3Step 8: Restore Configuration Data

3Step 9: Reset the BRMS/400 device and media library information

3STEP 10: Recover IBM product libraries

3Step 11: Restore User Libraries

3Step 12: Restore Document Library objects, Shared Folders and Mail

3STEP 13: Recover objects in directories

3STEP 14: Recover spooled files for all ASPs

3STEP 15: Apply journal changes

3Step 16: Restore Authorization information

3STEP 17: Verify system information

3Reset QSECOFR User profile

3Prevent FTP from running on Startup

3Remove the BRMS network entries

3Stop MPLUS from running

3Prevent ROBOT from running on Startup

3Hold all Scheduled jobs

3Review Job queues

3Hold All Job Queues

3Hold All Output Queues

3Hold All Distribution Queues

3Hold Automatic Clean-up

3Verify Relational Database Entries

3Verify Network Attributes

3Change Domain Information

3Verify IP configuration

3Verify System Information

3Verify System Values

3Add your temporary License Keys

3Initialize the System

3Verify IPL Attributes

3STEP 18: Print your logs

3STEP 19: Perform IPL

3STEP 20: BSafe Security Product Configuration

3STEP 21: Apply PTFs (if applicable)

3Step 22: Configure ROBOT Products - If applicable

3Change Robot System Name

3STEP 23: Perform FINAL IPL

3STEP 24: Configure Netserver Domain

3STEP 25 Clear the DR Box prior to leaving for the HomeSite

3PREFERRED METHOD: IBM recommended Zero disk

3ALTERNATE METHOD

3Checklists and Timings

3Problems Encountered:

Overview

This document contains the procedures required for recovering all iSeries systems within the GIS data center or Third Party provider utilizing IBM BRMS Backup and Recovery Media Services.

Copies of this DR Document are held at:

GE DR Box #1 held offsite at Iron Mountain contains a Hard Copy

Via the Web on the GE Folders site at http://folders.ge.com

Click on the Folders I have rights to Tab

Choose GIS Canada Disaster Recovery folder

Choose iSeriesAS400 folder

Online - http://supportcentral.ge.com/products/sup_products.asp?prod_id=72655Additionally, key members of the specified Disaster Recovery Team should keep a copy at home.

Global Infrastructure services owns this document and will keep it up to date after every DR test as well as every new operating system release level.

Reviewed By: Bill Dong

Date: December 15, 2010

Approved By:

Date:

Next Review Date:December 2011

Amendment History

VersionReview DateNotesPerformed By:

1.0February 2003New DocumentMyra Lush

2.0June 2003Updated instructionsMyra Lush

3.0March 2004Updated for MimixJeff King

4.0May 15 2004Updated instructions for LAN Console, zeroing disk and Special ConsiderationsMyra Lush

5.0May 30 2005Yearly ReviewMyra Lush

6.0August 18, 2005Update with V5R3 additionsMyra Lush

7.0January 25, 2006Update for LPAR considerations on initial buildMyra Lush

8.0May 24, 2006Update CPA4262 for the DR test to handle dupped tapes

9.0Aug 3, 2007Update i5 information and new processesYing Wang

10.0Oct 16, 2008Major reviewYing Wang

11.0Dec.15, 2010Major reviewBill Dong

12.00March 2, 2011Added Bsafe Configuration & Audit ReportMichelle DeMerchant

Before you Start:

If this is for a DR test ensure the DR partition has no hardware errors i.e.: disks and cache batteries are operational 3 to 7 days before.

***************************** A T T E N T I O N *****************************************

These restore procedures will take several hours to complete.

DO NOT cancel any step unless directed to do so by youre a GIS Technical Representative or an IBM Technical Service Representative.

*********************************************************************************************

You will require the following information before proceeding with the restore:

BRMS Recovering your Entire System Report (Latest Copy!) located at the following link (only accessible by GIS Technical Support): \\3.58.164.230\brmsreports$ Use the BRMS Recovery Volume Summary Report to determine where the media volumes for the following reside. If they are Offsite, recall them immediately stating you are in a Disaster situation: See Business Recovery document for information on the Offsite storage vendor for your business.

Most recent set of SAVSYS tapes,

Most recent set of SAVLIB *IBM tapes, (If any)

Most recent set of SAVLIB *NONSYS tapes,

Most recent set of SAVDLO tapes,

Most recent set of IFS tapes,

Most recent SAVSECDTA tape, (If any)

Most recent SAVCFG tape, (If any)

Most recent set of daily save tapes

Disaster Recovery box GEDR#1 located offsite at Iron Mountain which contains:

IBM Software Installation manual (Doc#: SC41-5120-05)

Backup & Recovery guide (SC41-5304), Appendix A will describe the System Reference (SRC) codes that may be encountered during the restoration process;

"Practical Approach to Managing Backup Recovery and Media Services" Redbook, SG24-4840

"Automated Tape Library Planning and Management" book, SC41-5309.

Details of the Third Party Application software license keys for the DR system

(See Appendix F, entitled THIRD PARTY SOFTWARE INFORMATION)

The IBM Licensed Internal code CD (I-BASE_01) for your system.

NOTE: If tape drive is Fiber attached you need the CD

If tape drive is SCSI attached you can IPL from Tape and do not need the CD.

The Device manual for the tape device that is your alternate IPL device. It describes other SRC codes you might see.

In addition, the Business Recovery document (Appendix) will contain a copy of the following documents:

DR Preparation Checklist

Offsite Storage Information

Subsystems, Output queues Active when in Production Mode & Any Special Instructions on the Business Application

Third Party software Information and contacts

IP Configuration settings

Prior Test results

IMPORTANT: Before starting the restore procedure, ensure (if possible) the tape drive heads have been cleaned

NOTE: If you are recovering at a DR Site, Please consult with the Vendor Representative regarding how your disk has been pre-configured on the SAN. This can affect the method and amount of time required to Zero-out the disks.

******************************** A T T E N T I O N *********************************

GE Standard is to COMPLETELY wipe out the Disks before leaving the Hotsite!!!

********************************************************************************************************************** A T T E N T I O N *********************************

WRITE PROTECT YOUR PRODUCTION SAVE TAPES**************************************************************************************

NOTE: 1. Ensure your I_BASE-01 cd is loaded at this point.

If tape drive is Fiber attached you need the CD.

If tape drive is SCSI attached you can IPL from Tape and do not need the CD.

2. Ensure you know the bus # of the tape drive. 3. Check if the disks are RAID or Mirroring.

4. All the backups are encrypted. Please check the DR infrastructure doc for the DR site to verify that the ATL is configured properly to an EKLM server.Step 1: Restore Licensed Internal Code

START TIME: _______ ___________

Note: Service Tools user ids and authorities are not carried forward when migrating to a new machine. You must go in and reset Service Tools user ids to known GE passwords and authorities. For more details on this section, refer to the procedure for "Recovering the Licensed Internal Code" in the "Backup and Recovery" book.

1. Ensure that the power switch for the Alternate IPL (Tape) device is powered on and the device is READY.

2. If its a standalone drive, insert a cleaning tape into the Alternate IPL (Tape) device before proceeding.

3. Ensure that the Console display is powered on.

4. If this is an LPARed system on a i5 hardware: Find the HMC IP address in file

\\cansvr01corpge\gsdcanada_docs$\7x24 l3\Partition DR info.xls

Access the HMC through web browser using the above IP Change the IPL setting of the partition to D M

Make sure the CD/DVD drive from the file Partition DR info is on and assigned to the partition

5. Load the correct version of IBM Licensed Internal code CD (I-BASE_01) in the optical device (OPT01) if the tape drive you will be restoring from is on a Bus other than Bus 1.

NOTE: If tape drive is Fiber attached you need the CD

If tape drive is SCSI attached you can IPL from Tape and do not need the CD.6. Load the most current weekly backup (SAVSYS) tapes. The Volume Ids will be identified on the BRMS Recovering your entire system report.

*VERY IMPORTANT: If you scratched the system using I_BASE_01, the First Console logon will be QSECOFR from the save tape. The second GUI logon will be the QSECOFR from the CD (password QSECOFR). Be careful as if entered incorrectly it can disable QSECOFR. If LAN console is used, it may attempt to logon once already using the PC configuration therefore you might only have 2 times to try before disabled.

Note: Refer to the IBM Software Installation manual or the Backup and Recovery Guide Appendix A for System reference codes that may be encountered during the restoration process.

7. The Select a Language Group screen will be displayed. Press Enter to select the Language feature.

8. Confirm the primary language is the same as production (mostly 2924) and press enter.

9. The Install Licensed Internal Code menu will appear on the console. Select option 3: Define Alternate Installation device to verify the address and validity of the alternate IPL device.

10. Select the bus number of the Alternate IPL device with option 1 and press Enter. Use the information from the Partition DR info spreadsheet.

11. Select the tape device by placing a 1 beside it. Press Enter. You will receive a message stating, Alternate Installation device selected. Note: the list might be blank for the first several minutes. Please wait 5 minutes and F5 to refresh

12. Press F3 to exit and return to the Install Licensed Internal code screen. Take option 1: Install Licensed Internal code.

13. At the Confirm Alternate Installation device screen, Press Enter to confirm and continue.

14. If you receive the following error, press enter to accept the default IPL device.

15. At the Install Licensed Internal Code (LIC) menu, Select option 2: Install Licensed Internal Code & Initialize System. Use "Option 2" if you are recovering to a different system or if you are recovering to a system with user ASP(s) or if you are recovering to the same system with a different release.

Select option 1: Restore Licensed Internal Code when the system has been pre-initialized. And continue with step 20.

16. You will receive a confirmation screen requesting you press the F10 function key to continue the install.

17. The load source disk will be initialized. The screen will update automatically. This is a long running process.

TIME CHECK: _ _

18. The following screen will be displayed. No action is required. Wait for next screen.

19. When the LIC installation is completed, a Disk Configuration Attention Report will be displayed. You may select option 5 to display the report or press F10 to ignore it and continue.

TIME CHECK: _ _

20. On the IPL or Install the System menu, select option 3 to Use Dedicated Service Tools.

21. Type the Service Tools (DST) security level password. The password will be in the AS400 DR box. If the password does not work, it may have been reset to the shipped value. Try QSECOFR. Press F5 to change the Password.

22. Select option 4: Work with disk units. Make sure if the disks are RAID or Mirroring.

23. Select option 1: Work with disk configuration.

24. If the configuration is RAID 5, select option 5 or if the configuration is mirroring go to step 38

25. Select option 1 to display the status, if not already active, select 2 Start device parity protection or Start the mirroring

26. If you receive the following error, it could mean that Device Parity protection is not valid or it has already started. Press Enter.

27. If you did not receive an error in the previous step, all of the disk subsystems for which you can start device parity will be listed. Select the Disk IOPs by placing a 1 beside those you want to include in parity and press Enter.

28. The Work with Device Parity Protection menu will be re-displayed. Press F3 to display the Work with Disk Configuration menu. Select option 3 Work with ASP configuration.

29. Select option 3: Add Units ASP.

NOTE: If you are recovering at a DR Site, Please consult with the Technical Representative regarding adding SAN Disk to this unit. NOTE: If option 1 is used in step 22, all units should be in the ASP already, and there will be no units to add. This is normal. Continue with step 47.

30. Find the ASP information from DR info. And add disk units accordingly (Mostly ASP1 and sometime ASP 2). Press Enter when completed. Note: The serial numbers listed on your screen will not match those shown below.

31. At the warning display, Press F10 to Ignore problems and continue.

32. The Confirm Add Units screen will be displayed. Press F9 to view the resulting capacity or Press Enter to confirm your choices. NOTE: If you are at a DR Site, Disk is in unprotected status.

33. Confirming the configuration will display the Function Status display as the disk units are added. This is a long running process.

34. When complete, the Work with ASP Configuration screen is redisplayed with the following message Selected units have been added successfully.

35. Take option 1 to Display Disk Configuration capacity.

36. Press F11 to ensure that Device Parity is active on all disks.

37. Press F11 again, they should all have a status of configured.

38. Select option 4 to start mirroring (more print screens). Start remote load source.

more print screens39. When done, Press F3 to exit.

40. The Work with Disk Units screen will be re-displayed. Press F3 again.

41. At the Use Dedicated Service Tools (DST) screen , Press F3

42. Take option 1 and press Enter, to Exit Dedicated Service Tools.

You have now completed installing the Licensed Internal Code.

STOP TIME : __ ___ Step 2: Restore Operating System

START TIME : _____ _For more details on this section, refer to the procedure for " Restoring the Operating System using the Complete Restore Method " in the "Backup and Recovery" book.

1. The IPL or Install the System menu appears. Select option 2: Install the operating system and press Enter.

2. The Install Device Type Selection menu appears. Select option 4 (OS 5.4 above) or option 1 (OS 5.3 below): and press Enter.

Note: Check ATL GUI to make sure the SAVSYS tape still in the original tape drive.

3. At the Confirm Install of Operating System display, press Enter.

4. Press Enter to select the Language feature (copy language words here).

5. Confirm the primary language (2924) and press enter. (language wording)

6. An IPL will take place with several IPL steps listed as they occur. Sample below.

7. If there are non-configured disk units on the system, you will be prompted to add disk units to the system, Enter option 1 to keep the current configuration.

8. The next screen will be the Install the Operating System display. Select option 2 to Change Install options. Enter the current Date and Time and press Enter.

9. On the Specify Install Options screen. Specify the following settings:

10. On the Specify Restore Options screen. Specify the following settings:

11. The OS/400 Installation Status screen will reflect the progress of the operating system restoration.

12. When the OS/400 installation is completed, the AS/400 sign on screen will appear. Logon as QSECOFR. There is no password required at this stage.

13. The next screen to appear will be the IPL Options screen. Change the following options and Press Enter:

Start Print Writers = N

Start system to restricted state = Y

Set Major System options = Y

Define or change system at IPL = Y

14. At the Set Major Systems Options screen, ensure Enable automatic configuration is set to Y, press Enter.

15. At the Define or Change System at IPL screen, select option 3 for System values and press the Enter key.

16. On the System Values Commands screen, select option 3 to Work with System Values and press Enter.

17. The following system values will need to be changed. See Appendix I for a listing of the current System values for this system. Use option 2 to change the System values to the specified new value (if applicable) and press Enter:

If changing the system value, note the old value. It will need to be changed back later.

SYSTEM VALUE

OLD VALUE

NEW VALUE

QALWOBJRST

*all__________

*ALL

QALWUSRDMN

*ALL__________

*ALL

QAUTOCFG

1__________

1

QFRCCVNRST

1__________

0

QINACTITV

240__________

*NONE

QIPLTYPE

0__________

2

QJOBMSGQFL

*WRAP __________

*PRTWRAP

QJOBMSGQMX

64 __________

64MB (30 MB minimum)

QJOBMSGQSZ

16__________

16384

QJOBMSGQTL

24__________

16384QLMTDEVSSN

0__________

0

QLMTSECOFR

0__________

0

QMAXACTLVL

*nomax__________

*NOMAX

QMAXSGNACN

1__________

2

QMAXSIGN

5__________

*NOMAX

QPFRADJ

2__________

2

QPWDEXPITV

240__________

*NOMAX

QSECURITY

30__________

30 (if saved system at 40 or 50)

QSTRUPPGM

__________

*NONE

QSTRUP

QGPLQSYSLIBL

__________

QSYS, QSYS2, QUSRSYS

0

10 QSYS

20 QSYS2

30 QHLPSYS

40 QUSRSYSQUSRLIBL

__________

QGPL, QTEMP

0

10 QGPL

20 QTEMPQVFYOBJRST

3__________

118. Press Enter once again to return to the System Value commands screen. Press F3.

19. Select option 4: Network Attributes commands.

20. Select option 1: Display Network Attributes.

21. On the Display the Network Attributes screen, Press Enter to display the Network Attributes.

22. Make a note of what needs to be changed for a DR test. Nothing to be changed in a true DR.

NOTE: Change the System name to the designated DR assigned System name.

System name:___________________

Local control point name:_________________

Default local location name:______________________

23. Press Enter to return to the previous menu. Select option 2: Change the Network Attributes.

24. Make the changes that you noted in the previous step and Press Enter when done.

NOTE: The System name, Local control point name, Default local location name and Network server domain name can be changed to DR system name.

25. Press F3 to return to the Define or Change the System screen.

26. Press F3 again to Exit and Continue and IPL.

27. The QSECOFR password will need to be reset. Press Enter to change the password.

28. Press F3 or Enter to exit the Display Messages screen and press Enter through any informational break messages that may appear to allow the IPL to continue.

29. You will now be presented with an AS400 Command line.

30. Change the Message description for CPX2313 to execute the command WRKJOB instead of a DSPJOB. That way, you can get a command line during the restore. To do this:

WRKMSGD MSGID(CPX2313)

30. If you are using a media library device and automatic configuration was enabled, you can now use the media library device to automate recovery.

For recovery using the device as a media library (TAPMLBxx):

Unload the media volume containing the *SAVSYS saved item from the device.

Load all the volumes needed for the recovery (including the *SAVSYS volume) in the media library.

Set the media library device for library operations. Refer to the device documentation if you are not familiar with enabling the device for library operations.

Verify the status of the media library device is VARIED ON. To do so, type: WRKMLBSTS and press "Enter".

Use Option 4=Allocate resource to set the current allocation of the media library resources to ALLOCATED.

For recovery using the device as a stand alone device (TAPxx):

Retrieve all volumes needed for recovery. If you are using an automatic cartridge loader, insert the volumes in the loader in the required sequence.

Type the command: WRKDEVD DEVD(*TAP) and press "Enter".

Use Option 8=Work with status to verify the status of the device you are using is VARIED ON.

At this point the Licensed Internal Code and the Operating System installation are complete. STOP TIME : ___________________STEP 3: Recover the BRMS/400 product and associated libraries

START TIME : ___________________

1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA(volume-identifier) required to complete this step. DO NOT use the media listed in these print screen samples. You will also find a step-by-step list of instructions similar to the steps included in this section. Sample excerpt below.

2. In the above excerpt from the BRMS report, make a note of the Saved-item, Sequence-number and Volume-identifier. These need to be inserted into the RSTLIB command and run for each of the Saved items. I.e.: You will run the command 5 times.

Please also note the importance of the OBJECTS column. It is strongly advised that you pay close attention to the number of objects actually restored after running each command and compare it to the report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG)

3. Type the command: CHGMSGQ MSGQ(QSYSOPR) DLVRY(*NOTIFY) SEV(99) to prevent messages not related to the recovery from interrupting the recovery process.

4. Type: WRKCFGSTS CFGTYPE(*DEV) CFGD(*TAP) and press Enter. Note the name assigned to the tape drive (device-name).

5. Ensure that the tape drive (or Media Library) is Varied on. Type the following command:

VRYCFG DEV(TAPxx) STATUS(*ON)

6. Run the RSTLIB command below for each of the items listed on the BRMS Recovering your Entire System report for this step. The SAVLIB (Saved-item), VOLID (Volume-identifier) and SEQNBR (Sequence-number) parameter details are listed on the report. (See screen print above for an example):

If the type of save is *FULL, type the following command at the command line:

RSTLIB SAVLIB(Saved-item) DEV(TAPxx) VOL(Volume-identifier) SEQNBR(Sequence-number) OUTPUT(*PRINT) ENDTAP(*LEAVE) ALWOBJDIF(*ALL) MBROPT(*ALL)

If the type of save is *CUML or *INCR, type the following command at the command line:

RSTOBJ OBJ(*ALL) SAVLIB(Saved-item) DEV(TAPxx) VOL(Volume-identifier) SEQNBR(Sequence-number) OUTPUT(*PRINT) ENDTAP(*LEAVE) ALWOBJDIF(*ALL) MBROPT(*ALL)

IMPORTANT: Check your BRMS report for DETAILS of libraries to be restored.

If access paths were not saved when the QUSRBRM library was saved, the access paths will be rebuilt when the library is restored. Verify rebuild of the access paths for files in the QUSRBRM library is complete before proceeding to the next step. To verify the rebuild, type the following command and Press Enter: EDTRBDAP

You have now completed installing your BRMS Product libraries.

STOP TIME : ___________________

STEP 4: Recover BRMS/400 related media information

START TIME : ___________________1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. You will also find a step-by-step list of instructions similar to the steps included in this section. You must recover the information for the BRMS/400 product to accurately guide you through the remaining recovery steps.

2. Run the following command specifying the sequence number and using the Volume-identifier from the BRMS report:

Type the following command at the command line:

RSTOBJ OBJ(*ALL) SAVLIB(saved-item) VOLID(volume-identifier) DEV(TAPxx) SEQNBR(sequence-number) MBROPT(*ALL) ALWOBJDIF(*ALL) OUTPUT(*PRINT)

You have now completed installing your BRMS related media Information.

STOP TIME : ___________________Step 5: Initialize BRMS/400

START TIME : ______

STOP TIME : ______

Initialize BRMS Functional Authority

Type the following commands to set the Authority for BRMS:

INZBRM OPTION(*SETAUT)

Use the following command to assure that QSECOFR has the required authorities:

SETUSRBRM USER(QSECOFR) USAGE(*ADMIN)

Update BRMS System Name

If you are restoring to a system with a different name than the Production name, perform the following:

INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(prev_name) NEWSYSNAM(*local)

Initialize BRMS Devices and Media Library

1. You need to clear the BRMS/400 device and media library information and initialize the files before proceeding.

INZBRM OPTION(*DEVICE)

2. Review the BRMS device information by typing the following command: WRKDEVBRMUpdate the device information with any required changes before proceeding.

If this is a DR test with duplicated tapes, there will be a CPA4264 for each restore and TAPMLB01 wont work since BRMS always try to load the original tapes.

Add a reply for CPA5303 for systems with lots of objects.

1. WRKRPYLE, F6 to add an entry if CPA4264 is not already there with an I as the reply

Pick an available sequence number, type in the MSG ID and reply, enter.

2. CHGJOB INQMSGRPY(*SYSRPYL), to use the system reply list to answer the massage.3. In step 5 below, use TAP01 instead of TAPMLB01. Mount the tape via the ATL GUI interface and using *MOUNTED for the restore command.

4. If more than one tapes are used, will need ATL GUI access to load the next volume.

Step 6: Restore User Profiles

START TIME : ____ ___

Note: Service Tools user ids and authorities are not carried forward when migrating to a new machine. You must go in and reset Service Tools user ids to known GE passwords and authorities. 1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. DO NOT use the media listed in these print screen samples. You will also find a step-by-step list of instructions similar to the steps included in this section.

2. Enter the following commands to put your message queue in Notify mode and Log your CL Commands:

CHGMSGQ MSGQ(QSYSOPR) SEV(60) DLVRY(*NOTIFY)

CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)

3. Type the following command to begin recovery of your user profiles:

STRRCYBRM OPTION(*SYSTEM) ACTION(*RESTORE)

4. The Select Recovery Items screen will be displayed. Press F9: Recovery defaults.

**** STEP 5 VERY IMPORTANT!!!

5. On the Recovery defaults screen,

Verify the tape device is correct.

Verify that the Restore to Library field is set to *SAVLIB

Verify that the Auxiliary Storage pool field is set to *SAVASP

If recovering to a different system:

Specify *ALL for Allow object differences (ALWOBJDIF)

Specify *NONE for system resource management (SRM) Press Enter when complete.

6. Back at the Select Recovery Items screen, select *SAVSECDTA with a 1 and press Enter to restore your User Profiles. 7. The Display Recovery items screen will be displayed (Wait for next display)

8. Once completed, press F3 to exit to the command line. 9. Change the QSECOFR password to ensure it was not changed when it was restored from tape. Type the following command: CHGUSRPRF USRPRF(QSECOFR) PASSWORD (new-password)You have now completed restoring your User Profiles.

STOP TIME : _____________________

Step 7: Restore BRMS Required System Libraries

START TIME : _____ __1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. DO NOT use the media listed in these print screen samples. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

2. If the Select Recovery Items display is not shown, run the following command to begin restoring the specific system libraries that are required to continue the recovery.

STRRCYBRM OPTION(*RESUME)

3. At the Select Recovery Items screen, select the items listed for this step with a 1 and press Enter. NOTE: The screen below is an example only and not to be used for your restore. Check your BRMS Recovering your entire system report for Current information.

Pay close attention to the Volume Ids(Volume Serial). Each time they change, they will need to be loaded in the tape drive in a READY status.

Please also note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the console display/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG).

4. The following screen will be displayed:

5. When the Select Recovery Items screen returns, verify the number of objects restored against the BRMS Recovery your entire system report.

NOTE: You may receive a message stating 1 security format change. Investigate the change and proceed.You have now completed restoring your BRMS/400 Required System Libraries.

STOP TIME : ___ ___

Step 8: Restore Configuration Data

START TIME : _____ __

1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. DO NOT use the media listed in these print screen samples. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

2. If the Select Recovery Items display is not shown, run the following command to begin restoring your system configuration data.


3. At the Select Recovery Items screen, select the item *SAVCFG with a 1 and press Enter.

4. Pay close attention to the Volume Ids (Volume Serial). Each time they change, they will need to be loaded in the tape drive in a READY status.

Please also note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the console display/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG).

Note: You may receive a message (CPF379C) stating that certain objects were not restored. Check the job log to verify the object names. If the objects are OPT01, QCONSOLE, TAP01, TAPMLB01 or QCTL, this is okay, since we are currently using these objects for the restore process. You have now completed restoring your Configuration Data.

STOP TIME : _____ __

Step 9: Reset the BRMS/400 device and media library information

START TIME : _____ __1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the step-by-step list of instructions to complete this step.

2. You need to clear the BRMS/400 device and media library information and initialize the files before proceeding. Type the following command at the command line:

INZBRM OPTION(*DEVICE)

3. Review the BRMS device information by typing the following command: WRKDEVBRMUpdate the device information with any required changes before proceeding.

STOP TIME : ____ ___STEP 10: Recover IBM product libraries

START TIME : ___________________1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

2. If the Select Recovery Items display is not shown, run the following command to begin restoring your IBM product libraries.


*****Attention *****

If your system uses journaling or MIMIX, you must restore the libraries containing the journals before restoring the libraries containing the journaled files.NOTE: If Lakeview Mimix High Availability software is being used on this system, restore library MIMIXJRN before the *ALLUSR libraries. (Refer to section entitled, Special considerations to determine if this system uses Mimix. The journal receivers must be restored before the user data libraries. If this step is forgotten you must journal all files over again so that Mimix knows about the files, using STRJRNPF command.If the save is a serial save, at this point you may press F16 to select all of the remaining recovery items. If any items are from a tape not currently onsite for the recovery, de-select them. Once selected, press Enter. After all the saved items are recovered, continue with Step 14.

If the save is a concurrent save, continue with item 3.

3. Pay close attention to the Volume Ids(Volume Serial). Each time they change, they will need to be loaded in the tape drive in a READY status.

Please also note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the screen/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG).

4. At the Select Recovery Items screen, select the items listed from the Recovering your entire system report with a 1 and press Enter to begin restoring your IBM Product libraries.

You have now completed restoring your IBM Product libraries.

STOP TIME : ___________________

Step 11: Restore User Libraries

START TIME : ______ __1. If recovering from a concurrent save, start QBATCH subsystem so that multiple restore jobs can run. QBATCH will start QSYSWRK. Make sure to end TCP.

2. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

3. If the Select Recovery Items display is not shown, run the following command to begin restoring your configuration data.


4. At the Select Recovery Items screen, select the items listed from the BRMS Recovering your entire system report from the same tape with a 1 and press F14 to submit the restore to QBATCH. Repeat step 3 & 4 for each tape in the full save.

OR

If recovering from a serial save, you may Press F16 to select all remaining items for restore. This will include all remaining libraries IFS, DLO and will be a Long running process.

Please note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the console display/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG)

*************************************Attention ****************************************If you have logical files whose based-on physical files are in a different library, you must restore all based-on physical files before you can restore the logical file.

If your system uses journaling, you must restore the libraries containing the journals before restoring the libraries containing the journaled files.

*************************************Attention ****************************************Search the system log for missing objects using the following command

DSPLOG PERIOD((*AVAIL start date of the DR)) MSGID(CPF3773)

Make a note of the omissions and restore them now using the following command:

RSTLIB SAVLIB(saved-library) DEV(TAPXX) SEQNBR(sequence-number) ENDOPT(*LEAVE) OPTION(*NEW) MBROPT(*ALL ) ALWOBJDIF(*ALL) OUTPUT(*PRINT)

Look at the BRMS report to find the sequence number associated with the library/object to be restored.

You have now completed restoring your User libraries. STOP TIME : _____ ____

Step 12: Restore Document Library objects, Shared Folders and Mail

START TIME : ___________________

1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

2. If the Select Recovery Items display is not shown, run the following command to begin restoring your DLO data.


3. At the Select Recovery Items screen, select the items listed from the BRMS Recovering your entire system report with a 1 and press Enter to begin restoring the current version of your user libraries.

4. Please note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the screen/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG)

5. When the restore command is complete, look at the job log (DSPJOBLOG) to see if any folders/Documents did not restore. Make a note of the omissions and restore them now.

**** ATTENTION ****

When Document Library Objects (DLOs) are restored, the system updates the search index database information for these DLOs. If the recovery fails, the error message may instruct you to run reclaim on the DLOs. To do so, RCLDLO DLO(*ALL) and press Enter.

After the reclaim, try the DLO recovery again.

You have now completed restoring your Document Library Objects.

STOP TIME : ___________________

STEP 13: Recover objects in directories

START TIME : ___________________1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for the List of MEDIA (volume-identifier) required to complete this step. You will also find a step-by-step list of instructions in the report, similar to the steps included in this section.

2. If the Select Recovery Items display is not shown, run the following command to begin restoring your configuration data.


3. At the Select Recovery Items screen, select the items listed from the BRMS Recovering your entire system report with a 1 and press Enter to begin restoring your objects in directories and the Integrated File system (IFS).

4. Pay close attention to the Volume Ids (Volume Serial). Each time they change, they will need to be loaded in the tape drive in a READY status.

Please also note the importance of the OBJECTS SAVED column. It is strongly advised that you pay close attention to the number of objects actually restored and compare it to the console display/report. In most cases, they should match. If there are discrepancies, you need to determine what/why by displaying your job log (DSPJOBLOG) and restore them now.

NOTE: You may receive a message stating the object QNetware was not restored (Message ID CPCA08C). Even if you try to restore the object manually it will not restore. To fix the problem, you need to manually recreate the object using the command MD QNetWare, which is case sensitive. After the first IPL the object should show up as type *DDIR. A Message will be received in QSYSOPR stating QNetWare is ready.

You have now completed restoring your Objects in Directories.

STOP TIME : ___________________

STEP 14: Recover spooled files for all ASPs

If spool files have been saved as part of full save, they have been restored as part of reload. If they are saved outside the full save, restore as requested.

STEP 15: Apply journal changes

IMPORTANT: Applying Journal changes in a DR is not required. ---Excerpt from DR Script ----

To determine if you need to apply journal changes, refer to the section "Determining Whether You Need to Apply Journaled Changes" under chapter "Restoring Changed Objects and Applying Journaled Changes" as detailed in the "Backup and Recovery" book.

Use one of the following commands to specify journals for applying journal changes.

STRRCYBRM OPTION(*APYJRNCHG) JRN(*JRNLST)

STRRCYBRM OPTION(*APYJRNCHG) JRN((library-name/journal-name) (library-name/journal-name) ... )

Use the End time and date prompt on the PERIOD parameter to specify the time and date of the last journal entry that is to be applied. Type your command choice then press "Enter".

Select Option 1=Apply journal changes on the Work with Journals using BRMS display for those journals you want to apply changes.

Select F16=Apply changes on the Apply Journal Changes using BRMS display to confirm your decision to apply the journal changes.

**** ATTENTION ****

Changes will be applied to the journaled objects of the selected journals for the journal receivers currently on the system.

Step 16: Restore Authorization information

START TIME : ___________________

1. IMPORTANT: Refer to the BRMS Recovering your Entire System report for step-by-step list of instructions similar to the steps included in this section.

2. Restore private authorities (Read, Update, etc.) to user profiles and objects. Enter the following commands to recover your user profile authorizations:

RSTAUT USRPRF(*ALL)

Attention Depending on the number of user profiles on your system, This operation can be a long running process.

Attention ENSURE the system is in restricted state before running this step, otherwise some authorities may not be restored.

3. Restore authority information saved by BRMS for basic user auxiliary pools. Enter the following command:

RSTAUTBRM USRASP(*ALLUSR)

When the command has completed, look at the job log (DSPJOBLOG) to see if any authorities did not restore properly.

You have now completed restoring your User Authorities.

STOP TIME : ___________________STEP 17: Verify system information

START TIME : ___________________Reset QSECOFR User profile

Before signing off or IPLing the system

1. Check that the QSECOFR User Profile password is known and that it is ENABLED. I will have been set by RSTAUT step. It should match what it was at the time of the backup used for the restore .

Prevent FTP from running on Startup

1. Issues can arise in a DR test when FTP processes start running for Inbound and Outbound FTP. As a temporary fix to this problem, rename your FTP commands as follows. This will cause FTP transmissions to abort unsuccessfully.

RNMOBJ OBJ(QSYS/FTP) OBJTYPE(*CMD) NEWOBJ(DRFTP)

RNMOBJ OBJ(QSYS/STRTCPFTP) OBJTYPE(*CMD) NEWOBJ(DRRTCPFTP)

2. Also turn off the FTP server. Type: CFGTCP to access the Configure TCP/IP main menu.

3. Take option 20: Configure TCP/IP applications

4. Take Option 10: Change FTP attributes and change the Autostart Servers entry to *NO and press Enter.

5. Take option 12: Configure SMTP

6. Take Option 3: Change SMTP attributes and change the Autostart Servers entry to *NO.

Remove the BRMS network entries

If this is a DR test, the system will be loaded with a different DR name. To prevent it from sending the BRMS information back to the production systems, please follow the steps to remove the BRMS network entries.

1. WRKPCYBRM *SYS, and OPTION 4

2. Delete all the entries with option 4 (If active, cant be removed)BSAFE Steps ??

Stop MPLUS from running

If this is a DR test, rename the mplus subsystem description so that it wont start after the IPL.

Prevent ROBOT from running on Startup

Refer to the Appendix A for information on the job scheduler that is currently being used for this system.

Rename the RBTSLEEPER subsystem to OLDSLEEPER to prevent Robot products from starting. Check with AS400 support as to the effect of starting RBTSLEEPER once the system comes back online after the Final IPL.

Hold all Scheduled jobs

Refer to the Appendix A, entitled Production Details and special considerations for information on the job scheduler that is currently being used for this system.

Ensure that all regularly scheduled jobs remain on Hold as the system comes up.

Robot Schedule

If you are using Robot SCHEDULE, Subsystem RBTSLEEPER will have been renamed to restrict Robot products from executing commands.

IBM Job Scheduler

If you are using the Basic IBM Job Scheduler for this system, type the following commands:

STRSBS QSYSWRK. This is required in order to access the job scheduler.

WRKJOBSCDE OUTPUT(*PRINT) PRTFMT(*FULL)

WRKJOBSCDE OUTPUT(*PRINT) PRTFMT(*BASIC)

HLDJOBSCDE JOB(*ALL) ENTRYNBR(*ALL)

or

WRKJOBSCDE and place all entries on hold manually.

Please make sure to bring the system back into the restricted status after this, otherwise the system will be accessable.

Review Job queues

Review all job queues and remove or hold old jobs

For QSPL job queue, you may see jobs which will require a 5 to End the job *immed

Hold All Job Queues

1. To ensure that no jobs are submitted from the job queues, ensure all job queues are held.

2. Type, WRKJOBQ JOBQ(*ALL) and press enter.

3. Type option 3 next to each job queue to hold them.

4. Release some system related jobqs, i.e. qsysnomax

Hold All Output Queues

1. Hold all output queues to ensure that no spool files are printed.

2. Type, WRKOUTQ OUTQ(*ALL) and press enter.

3. Type option 3 next to each Output queue to hold them.

Hold All Distribution Queues

1. Ensure that all Distribution queues remain on Hold as the system comes up.

2. Type: WRKDSTQ and use option 3 to place all Distribution queues on hold.

Hold Automatic Clean-up

Ensure that the regularly scheduled Automatic Cleanup is held. Type the command: GO CLEANUP and use option 4 to End cleanup. Then take option 1 and on the cleanup display panel, change allow auto cleanup to N, if required.

Verify Relational Database Entries

1. Verify Relational database entries are correct for the *LOCAL system e.g. DR system name.

(INZSYS issues may occur.verify!!)

2. Refer to Appendix Q, entitled Relational Database Entries for a list of the RDB entries configured on the Production system.

3. Type DSPRDBDIRE on each system.

Verify Network Attributes

Refer to the Appendices, DVD or \\caninf01corpge\brmsreports$\SYSINF for the Original Network Attributes for this system. Use the CHGNETA command to change your Network Attributes

In a DR Test: Change the following to a unique name. i.e.: DRSYSABC:

Current system name Local Control Point Name Default Local Location Network Server Domain Change the LOCAL Network ID if required Change APPN Node Type if required Change Allow Anynet Support to *NO when at DR Site

In a Production recovery, ensure the Network Attributes match those in the Appendices.

Check Ethernet Line

*NOTE: if this is a DR or migration environment, use the Rack configuration located in the Appendices or on DVD to find the Ethernet card resources to assign to the Ethernet lines. After the first IPL vary the Ethernet lines on and test if they are working correctly. They should become active after 5 seconds varied on.

If its a DR test, find out the ioa and ip address from the partition DR info spreadsheet and use the following command to create a new line and change all existing line desc to Online at IPL *NO.

CRTLINETH LIND(ETHLINEGE) RSRCNAME(CMNxx) LINESPEED(1G/100M) DUPLEX(*FULL) LINKSPEED(100M)

1. At the command line, type: WRKHDWRSC *CMN and Press Enter.

Or Go into DST and print the System Rack configuration.

2. Locate the communications resource name. Make a note of the name, it will be something like CMN02 with a description of Ethernet Port.

3. Type: WRKLIND *ELAN and press Enter.

4. Change the Resource name to the Ethernet Port name that you noted in step 1.

5. Page down twice to the Duplex field and type *FULL.

6. Press enter to accept the changes.

Change Domain Information

Refer to the Appendices, DVD or \\caninf01corpge\brmsreports$\SYSINF for the Original TCPIP Domain information for this system. Use the CFGTCP command to change the TCP/IP information.

In a DR Test: 1. Take option 12 from the Configure TCP/IP (CFGTCP) menu

2. Change the Host name to a DR name

NOTE: In a Production recovery, ensure the IP Configuration matches those in the Appendices.Verify IP configuration

Refer to the Appendices, DVD or \\caninf01corpge\brmsreports$\SYSINF for the Original TCP/IP Information for this system. Use the CFGTCP command to change the TCP/IP information.

In a DR Test: 3. Take option 2 from the Configure TCP/IP (CFGTCP) menu

DELETE any Production route destinations.

4. Take option 1 from the Configure TCP/IP (CFGTCP) menu

DELETE any Production IP interfaces. You may leave *LOOPBACK.

ADD new interfaces using the DR IP addresses provided by the GE Telecommunications rep.

Enter a 1 in the Opt column along with the DR IP Address

5. Press enter and key in the following information as applicable for your machine.

6. Take option 2 from the Configure TCP/IP (CFGTCP) menu

ADD a new *DFTROUTE with a Subnet of *NONE and a Next Hop equal to the DR IP Address for the Gateway provided by the GE Telecommunications representative.

7. Add an entry for this DR partition in the host table.

Verify System Information

1. If you ran either of the following commands or the PRTSYSINF command after your save, additional reports were created that enable you to verify your system information.

STRRCYBRM PRTSYSINF(*YES) or STRMNTBRM PRTSYSINF(*YES)

These reports can be found:

In the DR Box on DVD,

A partial listing can be found in the attached Appendices ,

At the following location: \\caninf01corpge\brmsreports$\SYSINF

Or map a drive to 3.58.152.40 folder called systems.

2. If you are using distribution media to restore your system, then you should use these reports to re-create the system information as detailed in the "Backup and Recovery" book.

Verify System Values

1. Return the system values back to their original settings. Type the following command: WRKSYSVAL SYSVAL(xxxxxxxx) 2. Refer to the Appendices, DVD or \\caninf01corpge\brmsreports$\SYSINF for the Original System value settings for this system. Use option 2 to change the System values and press Enter.

You may also refer to the notations made in Step 2: Restore Operating System. Change the system values back to the original values.

Note: Leave the QSTRUPPGM System value at *NONE until the Final IPL.

10 ITADMSYS

20 TECSYSCHG

30 EISSYS

40 QSYS

50 QSYS2

60 QHLPSYS

70 ITADMUSR

80 QUSRSYS

90 MCAUSRSYS

100 DBU90

Add your temporary License Keys

1. Input any 3rd party software upgrades and license keys (See the Special Instructions section of this guide)

2. Refer to the Appendices, or \\caninf01corpge\brmsreports$\SYSINF for a list of Software Resources for this system.

Initialize the System

Before performing an IPL, you need to confirm that Initialize of your system has occurred. To do this, type: GO LICPGM and press Enter. Take option 50.If the Initialize has not occurred you can initiate it with the following command: INZSYS Make sure that no PTFs are being installed during the time the INZSYS is running. If so, it will not complete successfully. If this is encountered, at the end of the PTF install end the system to restricted and repeat the INZSYS.Verify IPL Attributes

1. Ensure the system comes up in a partially restricted state by typing the following command: CHGIPLA and press F4.2. The following screen will be displayed: Note: these attributes are good for ONE IPL only

3. Change the following IPL Attributes:

STRTCP=*YES

Start Print Writers = *NO

Start system to a Restricted state=*YES

Create a new journal receiver for QAUDJRN/QSYS

1. Use command WRKJRNA JRN(QSYS/QAUDJRN), F15 (Work with Receiver Directory).

2. If you see a new journal receiver generated with different naming convention under the partial status receiver, create a new journal receiver with original naming convention (i.e. AUDRCV0200) in the original library (for example QUSRSYS), and attach to original Journal/Lib i.e QAUDJRN/QSYS. Then delete the partial jrnrcv.

STOP TIME : ___________________

STEP 18: Print your logs

START TIME : ___________________

Note: Normal software error found in GO PROBLEM are to be ignored QGLDUAPI and QSRRSPST.

1. You should review the history log for indications of objects not restored. To do so, run the following command: DSPLOG PERIOD((*AVAIL MM/DD/YY) (*AVAIL MM/DD/YY)) MSGID(CPC3700 CPF3700 CPF3800 CPC9000 CPF3848 CPF3773)

2. You should also print and review your job log. To do so, run the following command:

DSPJOBLOG JOB(*) OUTPUT(*PRINT)

3. Print and review your QHST log. To do so, run the following command:

DSPLOG OUTPUT(*PRINT)

4. You should print and review your BRMS Log. To do so , run the following command:

DSPLOGBRM PERIOD((*AVAIL *BEGIN) (*AVAIL *END)) OUTPUT(*PRINT) DETAIL(*FULL)

5. Type WRKSPLF and change the above spool files to SAVE = *YES

6. Review the job logs from your recovery processing to ensure that all recovery steps completed successfully. Ensure all objects were restored.

Common messages are as follows:

CPC3703: XXX objects restored from AAAA to BBBB at 3/31/2003 22:00:00. This is sent to the job log for each library that was successfully restored. It is Important that ALL objects get restored.

CPF3773: XXX objects restored. XX not restored to library AAAA. It is important to identify all objects not restored and determine the reason why. Try recovery again if necessary.

CPF2F17: SQL collection not restored in SYSIBM. This is ok to ignore

NOTE: If message Zero not restored appears, this is typically security related. Do a DSPMSG QSYSOPR to get the error message and then press F9 on the message to get the user id. Then type WRKSPLF QSYS (Where QSYS is the user id).

STOP TIME : ___________________STEP 19: Perform IPL

START TIME : ___________________

1. Remove all tape media from the tape drives.

2. Logon to the LPAR as QSECOFR

3. Type: WRKCTLD CTL*

4. Type: WRKDEVD DSP*

5. Delete Controller CTL01 and Device DSP01

6. Change partition to B N from HMC GUI. At the command line of the console:

PWRDWNSYS *CNTRLD DELAY(300) RESTART(*YES) IPLSRC(B) and press ENTER.7. Refer to the IBM Software Installation manual or the Backup and Recovery Guide Appendix

A for System reference codes that may be encountered during the restoration process.

STOP TIME : ___________________

STEP 20: BSafe Security Product Configuration

This step applies for the Tape Based Recovery of the following LPARs:

STCACBS1 STCTEST4 CVGACBS1 ALACBS02 S1040022 USRACDEV I02D9E00 I0324500 S65E5DED SRVD400 SRVQA400

GECMAS01 GECMAS02 GECMAS03 CFSDIFL1 CFSPIFL1

CFSQIFL1 CFSRIFL1 CFSV6R1Turn over the DR system to the GIS iSeries Security team for the Bsafe Configuration and lockdown requirements for the DR Test.

GIS iSeries Security team will ensure that standard Capital Security lockdown/restrictions are activated. START TIME : ___________________

STEP 21: Apply PTFs (if applicable)

START TIME : ___________________

If applicable, re-apply PTFs that were applied since your last save of system data.

STOP TIME : ___________________

Step 22: Configure ROBOT Products - If applicable

To determine which systems have Robot products installed, refer to Appendix F, entitled Third Party software for this system.

Change Robot System Name

1. Change the system name for ROBOT products to the new DR System name: RSLCHGSYSN (F4) (Run for each applicable product)

STOP TIME : ___________________

STEP 23: Perform FINAL IPL

START TIME : ___________________

1. Release Job Queues: i.e.: QSYSNOMAX and QPWFSERVER (wrong sequence)

2. Have the Network Cables Attached

Check with the on-shift Telecommunications Representative regarding setup of TCP/IP (this is the connectivity between the GE Network and the SNN (Sungard National Network). They will need to physically connect the cabling.

3. Change your IPL Attributes back to their original settings. Type the following command: CHGIPLA and press F4. The following screen will be displayed:

4. Change the following IPL Attributes:

STRTCP=*YES

Start Print Writers = *NO (leave this at *NO for DR)

Start system to a Restricted state=*NO

5. Ensure the system is in a Restricted state by entering the following commands:

ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(180)

6. Display the QSYSOPR message queue and review the messages

7. Once you receive the message, System ended to Restricted State, enter the following command and press Enter.PWRDWNSYS *CNTRLD DELAY(300) RESTART(*YES) IPLSRC(B) and press ENTER.8. Refer to the IBM Software Installation manual or the Backup and Recovery Guide Appendix

A for System reference codes that may be encountered during the restoration process.

9. Check with the on-shift Telecommunications Representative regarding setup of TCP/IP connectivity between the GE Network and DR site network.

11. Inform the GE DR Coordinator that the Applications Team may begin testing.

STOP TIME : ___________________

CONGRATULATIONS!!! Your DR Recovery is complete!!

TOTAL RECOVERY TIME: __________________STEP 24: Configure Netserver Domain

Change Netserver Domain

Note: a PTF is required for access to the Netserver via Green screen, if you do not have this PTF, access the netserver through the GUI Operations Navigator interface as described in the next step.

1. Ensure that the Netserver domain is pointing to the DR system at the Hotsite.

2. STRSBS QSYSWRK (or QSERVER) This is required.

3. STRHOSTSVR SERVER(*ALL)

4. STRTCP STRSVR(*NO)

5. ADDLIBLE LIB(NETSRVCMD)

6. Type: GO NETS to access the Netserver main menu

7. Take option 9 to CHANGE the Current Netserver attributes.

8. Change the server name and Domain name to reflect the DR System name. The Server name should have a prefix of Q

9. Ping another system to test connectivity. I.e: PING AS400COR.CORPORATE.GE.COM

STEP 25 Clear the DR Box prior to leaving for the HomeSite

NOTE: If you are recovering at a DR Site, Please consult with the Technical Representative regarding how your disk has been preconfigured on the SAN. This can affect the method and amount of time required to Zero-out the disks.

GE Standard is to COMPLETELY wipe out the Disks before leaving the Hotsite!!!

Prior to cleaning the system, check with the GIS iSeries Security team to ensure that all Audit Reports have been transferred from the system.

START TIME: _________________

PREFERRED METHOD: IBM recommended Zero disk

1. Load the IBM Licensed Internal code CD (I-BASE_01) in the optical device (OPT01) if the tape drive you will be restoring from is on a Bus other than Bus 1.

or

2. Load the most current weekly backup tapes.

3. If the control panel of the AS/400 is locked, insert the Black key stick to unlock.

4. Depending on your system, Press the MODE button to place the AS/400 in manual mode. The green indicator light will illuminate beside the selected mode or a hand symbol will appear. If you do not have a MODE button continue on to the next step.

5. Select the IPL type by pressing the Function Increment button (UP arrow) to display 02 (IPL type) in the Function/Data display of the Control Panel. Press the Enter button.

6. Select the IPL option by pressing the Function Increment button (UP arrow) six times to display D M. NOTE: Depending on your system model, you may only see a D, if so, the manual light or the hand symbol will be illuminated.

7. Press the Enter button on the control panel to accept the selected settings.

8. If your system is already powered off, Power on the AS/400 (white button) or press the Function Increment button (Up arrow) to display 03(start IPL).

If your system is already powered on, after pushing the power button once, you will

receive a 0? on the control panel. Press the Power button a second time to begin the power off sequence. You will notice SRC codes such as D6000484, D6005500, D1848000 indicating that the system is powering down. When the AS400 powers down completely, the power light will go out and 1 DM will be displayed on the control panel. Press the POWER ON button again to begin power up and start the IPL.

or

At the command line of the console: type PWRDWNSYS RESTART(*YES) IPLSRC(D)

9. The Install Licensed Internal Code menu will appear on the console. Select option 1: Install Licensed Internal Code.

10. At the Confirm Alternate Installation device screen, Press Enter to confirm and continue.

11. If you receive the following error, press enter to accept the default IPL device.

12. At the Install Licensed Internal Code (LIC) menu, select option 2: Install Licensed Internal Code & Initialize System.

13. You will receive a confirmation screen requesting you press the F10 function key to continue the install.

14. The load source disk will be initialized. The screen will update automatically. This is a long running process.

TIME CHECK: _ _

15. The following screen will be displayed. No action is required. Wait for next screen.

TIME CHECK: _ _

16. When the LIC installation is completed, a Disk Configuration Attention Report will be displayed. You may select option 5 to display the report or press F10 to ignore it and continue.

17. On the IPL or Install the System menu, Select option 3 to use Dedicated Service Tools.

NOTE: If you are not in DST select option #3 for DST. We should also check option #5 for DST environment, then option #2, then option #6 for console mode. Set it to the device type that you are using.

18. Type the Service Tools (DST) security level password. The password will be in the AS400 DR box. If the password does not work, it may have been reset to the shipped value. Try QSECOFR. Press F5 to change the Password

19. Once you have signed on to Service Tools (DST), the Use Dedicated Service Tools(DST) menu will be displayed. Select option 4: Work with disk units.

20. In version V5R2M0 you will see an option 13 to Work with System Security. Set it to allow SST ID to change

ALTERNATE METHOD

START TIME: _________________

1. At the command line, type: ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(180)

2. When you receive the message, System ended to Restricted condition, log off the system. Continue with next step.

3. Remove all tapes from the Tape drive and remove any CDs from the OPTICAL CD Drive.

4. If the control panel of the AS/400 is locked, insert the Black key stick to unlock.

5. Depending on your system, Press the MODE button to place the AS/400 in manual mode. The green indicator light will illuminate beside the selected mode or a hand symbol will appear. If you do not have a MODE button continue on to the next step.

6. Select the IPL type by pressing the Function Increment button (UP arrow) to display 02 (IPL type) in the Function/Data display of the Control Panel. Press the Enter button.

7. Select the IPL option by pressing the Function Increment button (UP arrow) six times to display D M. NOTE: Depending on your system model, you may only see a D, if so, the manual light or the hand symbol will be illuminated.

8. Press the Enter button on the control panel to accept the selected settings.

9. If your system is already powered off, Power on the AS/400 (white button) or press the Function Increment button (Up arrow) to display 03(start IPL).

10. If your system is already powered on, after pushing the power button once, you will receive a 0? on the control panel. Press the Power button a second time to begin the power off sequence. When the AS400 powers down completely, the power light will go out and 1 DM will be displayed on the control panel. Press the POWER ON button again to begin power up and start the IPL.

or

11. At the command line of the console: type PWRDWNSYS RESTART(*YES) IPLSRC(D)

12. Refer to the IBM Software Installation manual or the Backup and Recovery Guide Appendix A for System reference codes that may be encountered during the restoration process.

13. On the IPL or Install the System menu, Select option 3 to use Dedicated Service Tools.

14. Type the Service Tools (DST) security level password. The password will be in the AS400 DR box. Press Enter.

15. Once you have signed on to Service Tools (DST), the Use Dedicated Service Tools(DST) menu will be displayed. Select option 4: Work with disk units.

16. Select option 1: Work with disk configuration. Press Enter.

17. Select option 3: Work with ASP Configuration.

18. Select option 5: Delete ASP Data.

19. Place a 4 beside each ASP that you want to delete the data from. Press Enter when completed.

20. The system will display the current Disk Configuration. The serial numbers shown here, will not match your system. Press Enter.

21. A Screen will be displayed Confirming your choice for deletion. Review the screen and press F10 key to delete the selected data.

22. A message will be displayed, stating that the data has been marked for deletion.

23. NOTE: If you wish to double check that your data has been successfully deleted.

24. Press F3 twice to exit to the Use Dedicated Service Tools (DST) menu. Select option 1: Perform an IPL.

25. If the data was successfully deleted, you should receive the following message:

Clear of System Completed!!

STOP TIME: _____________________

Checklists and Timings

The following checklist must be used in EVERY test. We can then use this checklist to accurately estimate the time taken to restore the whole system.

DATE: ______________________________________

TaskStart TimeFinish TimePerformed By:

Restore Internal Code

Configure Disk Units

Restore OS/400

Restore User Profiles

Restore Configuration

Restore ALL Data

Restore CORE Data

Restore Authorities

Final IPL

TOTAL RESTORE TIME =

Problems Encountered:

Any problems encountered during a DR TEST should be logged on this sheet.

DATE: ________________________________________

PROBLEM

ENCOUNTEREDRESOLUTIONRESOLVED

BY

Global

Infrastructure

Services

Technical Infrastructure Disaster Recovery Plan

iSeries-AS/400 Recovery for

GE Canada

BRMS Recovery Method

Version 11.0 December 2010

Select a Language Group

Note: The language feature shown is the language feature installed on the system.

Language feature . . . . . . . . . . . . . . 2924

Confirm Language Feature Selection

Language feature . . . . . . . . . . . . . . : 2924

Press Enter to confirm your choice for language feature.

Installing the system will continue.

Press F12 to return to change your choice for language feature.

Install Licensed Internal Code

Select one of the following:

1. Install Licensed Internal Code

2. Work with Dedicated Service Tools (DST)

3. Define alternate installation device

EXAMPLE ONLY

Select Alternate Installation Device Bus

Type Option, press Enter. 1=Select

Option Bus Number Selected

1 01 *

F2=Deselect Device F3=Exit F12=Cancel

Select Alternate Installation Device

Type Option, press Enter. 1=Select 5=Details

BusResource Serial

Option NumberName TypeModel Number Selected

1 0001TAP016380 001 00-110221 *

EXAMPLE ONLY

Install Licensed Internal Code


1. Install Licensed Internal Code

2. Work with Dedicated Service Tools (DST)

3. Define alternate installation device

Confirm Alternate Installation device

You have chosen to install the Licensed internal code from the alternate installation device.

Press Enter to Continue.

Press F12 to Cancel.

Alternate Installation Device Failed.

The Alternate Installation device or media failed.

Press Enter to use the Primary installation device.

Press F5 to Retry.

Press F12 to Cancel.

Unable to allocate resources installation failed.

Install Licensed Internal Code (LIC)

Disk selected to write the Licensed Internal Code to:

Serial Number TypeModel I/O Bus Controller Device

68-0156349 6714 072 0 1 0


1. Restore Licensed Internal Code

2. Install Licensed Internal Code and Initialize system

3. Install Licensed Internal Code and Recover Configuration

4. Install Licensed Internal Code and Restore Disk Unit Data

5. Install Licensed Internal Code and Upgrade Load Source

Selection: 2

Press Enter.

Install LIC and Initialize system - Confirmation

Warning:

All data on this system will be destroyed and the Licensed Internal Code will be written to the selected disk if you choose to continue the initialize and install.

Return to the install selection screen and choose one of the other options if you want to perform some type of recovery after the install of the Licensed Internal Code is complete.

Press F10 to continue the install.

Press F12 (Cancel) to return to the previous screen.

Press F3 (Exit) to return to the install selection screen.

F3=Exit F10=Continue F12=Cancel

EXAMPLE ONLY

Initialize the Disk - Status

The Load source disk is being initialized.

Estimated time to initialize in minutes:170

Elapsed time in minutes:30.5

Please wait.

Wait for next display or press F16 for DST main menu.

EXAMPLE ONLY

Installing Licensed Internal Code - Status

Install of Licensed Internal code in progress.

Percent

Complete

Elapsed time in minutes:3.0

Please wait.

10%

Disk Configuration Attention Report

Type option, press Enter. 5=Display Detailed Report

Press F10 to accept all the following and continue the IPL. The system will attempt to correct them.

OPT Problem

_ New disk configuration

F3=Exit F10=Accept problems and continue

IPL or Install the System

1. Perform an IPL

2. Install the operating system

3. Use Dedicated Service Tools (DST)

4. Perform automatic installation of the operating system

5. Save Licensed Internal Code

Dedicated Service Tools (DST) Sign On

Type choices, press Enter.

Service Tools User . . . . . . QSECOFR

Service Tools password . . . _______

Use Dedicated Service Tools (DST)

1. Perform an IPL

2. Install the operating system

3. Work with Licensed Internal Code

4. Work with disk units

5. Work with DST environment

6. Select DST console mode

7. Start a service tool

8. Perform automatic installation of the operating system

9. Work with save storage and restore storage

10. Work with remote service support

11. Work with system partitions

Selection 4

Work with Disk Units

1. Work with Disk configuration

2. Work with Disk Unit Recovery

Selection: 1

Work with Disk configuration

1. Display Disk configuration

2. Work with ASP Threshold

3. Work with ASP Configuration

4. Work with Mirrored Protection

5. Work with Device Parity Protection

6. Work with Disk Compression

Selection: 5

Work with Device Parity Protection

1. Display Device Parity Status

2. Start Device Parity Protection

3. Stop Device Parity Protection

4. Include unit in Device Parity Protection

5. Exclude unit from Device Parity Protection

Selection: 2

EXAMPLE ONLY

Start Device Parity Protection Failed

There are no disk units eligible for the selected operation due to one or more of the following reasons:

All the Device parity capable disk units are already device parity protected.

Maximum number of arrays exceeded.

An IOP is in a condition that makes the disk units attached to it read/write protected. Examine the product activity log for any reference codes that are logged for the IO subsystem and follow the appropriate procedure for the reference code to correct the problem, if necessary.

Not all disk units attached to an advanced function IOP have reported to the system. Retry the operation.

All the disk units in a parity set must be the same capacity with a minimum number of 4 disk units and a maximum of 10 units in the resulting parity set.

Press enter to continue.

EXAMPLE ONLY

DISPLAY DEVICE PARITY STATUS

ParitySerialResource

Set ASPUnitNumberTypeModelNameStatus

1 10-91600462741001DC01

**68-01666856714072DD004Active

**68-06821756714072DD008Active **68-01677CF6714072DD003Active

1*68-01563496714072DD007Active

**68-01666606714072DD005Active **68-016664C6714072DD006Active

**68-016668E6714072DD001Active

**68-01665C46714072DD002Active








Selection: 3

Work with ASP Configuration

1. Display Disk configuration capacity

2. Delete User ASP

3. Add Units to ASP

4. Delete ASP Data

5. Change ASP Storage Threshold

6. Move Units from one ASP to another

7. Remove Units from Configuration

8. Add Units to ASPs and Balance data

Selection: 3

Specify ASPs to Add Units to

Specify the ASP to add each unit to.

SpecifySerialResource

ASPNumberTypeModelCapacityName

168-0156349671407215355DD002

168-0166660671407215355DD005

168-016668E671407215355DD001

168-0682175671407215355DD008

EXAMPLE ONLY

Problem Report

Note: Some action for the problems listed below may need to be taken. Please select a problem to display more detailed information about the problem and to see what possible action may be taken to correct the problem.

OPT Problem

___ Unit possibly configured for Power PC AS

F3=Exit F10=Ignore problems and continue F12=Cancel

EXAMPLE ONLY

Confirm Add Units

Add will take several minutes for each unit. The system will have the displayed protection after the units are added.

Press Enter to confirm your choice for add units.

Press F9=Capacity information to display the resulting capacity

Press F12=Cancel to return and change your choice.

SerialResource

ASPUnitNumberTypeModelNameProtection

1Unprotected

168-01563496714072DD002Device Parity

268-01666606714072DD005Device Parity

368-016668E6714072DD001 Device Parity

468-06821756714072DD008 Device Parity

EXAMPLE ONLY

Function Status

You selected to add units.

10 % Complete

Wait for the next display or press F16 for DST Main menu

SAMPLE








Selection: 5

Work with ASP Configuration


1. Display Disk configuration capacity

2. Delete User ASP

3. Add Units to ASP

4. Delete ASP Data

5. Change ASP Storage Threshold

6. Move Units from one ASP to another

7. Remove Units from Configuration

8. Add Units to ASPs and Balance data

Selected Units have been added Successfully.

F3=Exit F12=Cancel

Work with Disk Units

1. Work with Disk configuration

2. Work with Disk Unit Recovery

Selection: __

F3=Exit F12=Cancel

Use Dedicated Service Tools (DST)

1. Perform an IPL

2. Insta