Backing Up and Restoring your SAP System on IBM i

Backing Up the Entire System

• All users have logged off and all SAP systems have been stopped.

  This is important because the IBM i shuts down all subsystems before starting this type of backup.

• You are working at the console, and you are logged on as QSECOFR or as a user with *SAVSYS rights and authorization to start and end subsystems.

• You have enough storage media (that is tapes) available and initialized to contain the complete backup of your system.

Restoring the Entire System

• 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 is available.

• A CD-ROM with the licensed internal code (LIC) is available. It is required if you are restoring the licensed internal code from a device that is not connected to the system bus (bus 1).

• You are aware of your disk configuration, that is you know which auxiliary storage pools (ASPs) were configured before the start of the recovery.

Backing Up the Entire System

1. Enter command GO SAVE.

   The Save menu appears.

2. Select option 21 ( Entire system).

   Note

   This ends all active subsystems, saves all system and user data, and starts the controlling subsystem. When starting the controlling subsystem, the automatic startup program that is specified in system value QSTRUPPGM is executed automatically and all other subsystems are started again.

3. To verify that the backup is complete, enter command DSPJOBLOG to look for error messages that might have occurred during the backup.

   Note

   If errors occurred, your backup might not be complete. Therefore, it might be unusable for recovery.

4. If your SAP systems are not started automatically by the system startup program, start your SAP systems now.

Restoring the Entire System

1. If your system is partitioned, shut down the partition using the command PWRDWNSYS, the Dedicated Service Toole (DST), or the Hardware Management Console (HMC). If the system is not partitioned, shut down the system.

2. Place the system or partition in manual mode and choose IPL source D (IPL from tape or optical media). It depends on your system configuration whether you perform these steps through the control panel, the option Work with system partitions in the System Service Tools (SST), the Dedicated Service Tools (DST), or the Hardware Management Console (HMC).

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

4. Start the system or partition.

5. After a while, the Install Licensed Internal Code (LIC) screen appears 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

   Choose option 3 Install Licensed Internal Code and Recover Configuration.

6. Enter F10 on the Install LIC and Initialize System - Confirmation screen.

7. If you are installing the licensed internal code on the primary partition of a partitioned system, you receive the following error report after the LIC has been loaded:

   Unit has incorrect logical partition configuration

8. To recover your LPAR configuration, start the Dedicated Service Tools (DST) and choose option 11 Work with system partitions, and then option 4 Recover partition data and option 1 Recover primary partition configuration data.

   Note

   You also receive the following error report after the LIC has been loaded:

   Missing disk configuration

9. To recover your disk configuration and the journal receivers in your user ASP, start the Dedicated Service Tools (DST).

10. Choose option 4 Work with disk units, and then option 2 Work with disk unit recovery and option 5 Recover disk configuration.

    Note

    The system displays a Problem Report with two problems:

    Load source has been re-built and ASPs will be cleared.

    You can ignore these reports.

11. To continue, enter F10.

    Note

    You must verify your disk configuration at the end of the procedure.

12. Return to the menu IPL or Install the System and choose option 2 Install the operating system.

13. Confirm the installation of the operating system when requested to do so.

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

15. Choose 1 Take defaults for the install option.

16. When the installation is completed, the system automatically performs an IPL and displays an IPL Sign On screen.

17. Sign on with user profile QSECOFR.

    Note

    The system requires no password at this time. The system displays the Change Password display. The system sets the QSECOFR user profile to *EXPIRED, and the password to QSECOFR. When the IPL completes, the QSECOFR password is the password associated with the SAVSYS media you used.

18. Enter command GO RESTORE.

    The Restore menu appears.

19. Select option 21 ( System and user data).

    Note

    This ends all active subsystems, restores user profiles, configuration data, libraries, documents, folders, objects in directories and authorities, and starts the controlling subsystem. When starting the controlling subsystem, the automatic startup program that is specified in system value QSTRUPPGM is executed automatically and all other subsystems are started again.

20. To verify that the restore is complete, enter command DSPJOBLOG to look for error messages that might have occurred during the restore. If errors occurred during the restore, your system might not be complete. Therefore, the system might be unusable.

21. If the restore was started as a result of an unplanned system outage, or if your backup contains partial transactions, you must perform data recovery. Recover all changes since the last backup until the time shortly before the error as described in section Recovering Changes to the SAP System Since the Last Backup in SAP Database Guide: IBM DB2 for i.

22. If your SAP systems are not started automatically by the system startup program, start your SAP systems now.