Restoring and Recovering the Entire System Including the SAP System

This procedure describes how to restore the system after losing the system auxiliary storage pool (ASP). The system ASP contains the licensed internal code, operating system, licensed programs, security and configuration information, and SAP system data (unless the SAP system was stored in a user or independent ASP).

If you have lost data because of disk failures that go beyond device parity protection or mirroring, you might need to restore the complete system. This procedure assumes that you have stored the journal receivers in a separate user ASP and want to keep it for data recovery up to the point of failure. For more information about recovery methods, see the IBM backup and recovery documentation.

• All broken disk units have been replaced by the IBM service representative.

• A console screen is available and connected to your IBM i server.

• Backup media with SAVSYS information, IBM libraries and user data from the most recent backup are available.

• A CD-ROM with the licensed internal code (LIC) is available.

• You know which ASPs were configured prior to the data loss.

1. Shut down the system or partition that you want to restore.

2. Place the system or partition in manual mode and choose IPL sourceD (IPL from tape or optical media).

3. Load the SAVSYS media to the alternate IPL device (usually a tape unit) and the Licensed Internal Code CD to your CD drive.

4. Start the system or partition.

   After a while, the Install Licensed Internal Code (LIC) screen appears on the system console with the following options:

   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

5. Choose option 3 ( Install Licensed Internal Code and Recover Configuration).

6. On the Install LIC and Initialize System - Confirmation screen, press F10.

   After the licensed internal code has been loaded, the Disk Configuration Error Report screen appears.

7. In front of the error Missing disk configuration, choose option 5 ( Display Detailed Report).

8. To start the Dedicated Service Tools (DST) and recover your disk configuration with the journal receivers in your user ASP, on the Missing Disk Configuration screen, press F3.

9. Sign on to DST with your service tools user and password then choose option 4 ( Work with disk units), then option 2 ( Work with disk unit recovery), and option 5 ( Recover disk configuration).

   Note

   A report appears with the following problems:

   Load source has been rebuilt

   ASPs will be cleared.

   You can ignore this report.

   To continue, press F10. Verify your disk configuration at the end of the procedure and confirm it once more with F10.

10. Return to the menu IPL or Install the System and choose option 2 ( Install the operating system).

11. When requested, confirm the installation of the operating system.

12. Complete the requested information during the installation as needed, such as the language feature selection or install option.

13. Choose option 1 ( Take defaults).

14. When you have completed the installation, the system will display a Sign On screen.

15. Sign on with user profile QSECOFR.

    Note

    The system requires no password at this time. The system displays the Change Password screen. The system sets the QSECOFR user profile to *EXPIRED, and the password to QSECOFR.

    When the IPL is completed, the QSECOFR password is the password associated with the SAVSYS media you used.

16. When the IPL is completed, put the system into restricted state by ending all subsystems with the following command:

    ENDSBS SBS(*ALL) OPTION(*IMMED)

    Note

    Wait until all subsystems except the controlling subsystem are ended.

17. To restore all user profiles from the SAVSYS media, enter the following command:

    RSTUSRPRF USRPRF(*ALL)

18. To restore device configuration objects from the SAVSYS media, enter the following command:

    RSTCFG OBJ(*ALL) OBJTYPE(*ALL)

19. Load the media that contain the backup of your user libraries and directories, if this is different from the media that contains the SAVSYS media.

20. Restore the IBM and user libraries.

    It is important that the journal receivers in the user ASP are not being replaced by older ones from the save media during this step. The easiest way to ensure this is to specify OPTION(*NEW) on the command RSTLIB. This assumes that the system was initialized, so all data in the system ASP is gone. If all IBM and user libraries are on one set of backup media, you can enter the command RSTLIB SAVLIB(*NONSYS) OPTION(*NEW) to restore all libraries at once. If you have more recent backups of your SAP data on another backup medium, you can first restore all other data and omit the SAP data by adding the parameter OMITLIB(R3<SID>DATA SAP<SID>DB) to the command RSTLIB, and then proceed as described in Restoring All SAP Components.

21. If you have documents and folders that are usually not used in the SAP environment, you need to restore them using the following command:

    RSTDLO DLO(*ALL) SAVFLR(*ANY)

22. To restore all objects in directories, enter the following command:

    RST OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT))

    Note

    If you have stored a more current version of SAP subdirectories on another backup medium, you should first restore all other data by adding ('/usr/sap/<SID>/*' *OMIT) ('/sapmnt/<sid>/*' *OMIT) to the command RST and then proceed as described in Restoring All SAP Components.

23. To restore all private object authorities, enter the following command:

    RSTAUT USRPRF(*ALL)

24. Recover all changes since the last backup until the time shortly before the error as described in Recovering Changes to the SAP System Since the Last Backup.

25. Start the controlling subsystem by entering the command STRSBS.