Show TOC

Restoring All SAP ComponentsLocate this document in the navigation structure

Prerequisites

  • The SAP user profiles ( <SID>OWNER, R3GROUP, and SAP<SID>DB) exist on the system.

  • SAP executables, such as the kernel library and the operating system libraries for Java have been restored or installed from a kernel DVD.

  • If the backup of the database library was obtained with SAVACTWAIT option *NOCMTBDY, sufficient journal receivers to recover all open transactions are available or being restored at the same time.

  • If you restore data to an existing SAP system, you must end all local and remote instances of that system.

  • If you restore data to an existing SAP database library, delete the contents of the old database library first.

    Advantages

    Disadvantages

    You do not run into problems that are caused by duplicate object names due to the asynchronous processing of the system catalogs.

    Deleting the objects from the libraries takes time.

    You do not have to deal with any SAP system objects in the libraries that might be damaged.

    Restoring takes longer if objects from the libraries were deleted, since access paths have to be rebuilt.

Context

This procedure describes how to restore the components of an SAP system. The description includes components of SAP NetWeaver Application Server ABAP and Java installations. If you are using an ABAP only or Java only installation, you cannot find all the libraries mentioned in your backup. ABAP components use the libraries R3<SID>DATA and R3<SID>JRN whereas Java components use the libraries SAP<SID>DB and SAP<SID>JRN. For more information about the commands and a full description of their parameters, see the IBM Information Center.

Caution

The restore sequence is important. Make sure that the journal receiver libraries R3<SID>JRN and SAP<SID>JRN are restored before the database libraries. If the database libraries are restored first, new journal receivers will be located in the database libraries instead of the journal receiver libraries.

Procedure

  1. Load your backup media containing the most recent backup of your SAP system data.
  2. If the journal receivers and their libraries ( R3<SID>JRN or SAP<SID>JRN) do not need to be restored, for example because they were located in a user ASP, continue with step 4.
  3. To restore the journal receiver libraries R3<SID>JRN and SAP<SID>JRN (if applicable), enter the following command:

    RSTLIB SAVLIB(<library>) DEV(<backup device>) OPTION(*NEW) RSTASP(*SAVASP)

  4. To restore the database libraries R3<SID>DATA and SAP<SID>DB (if applicable) enter the following command:

    RSTLIB SAVLIB(<library>) DEV(<backup device>) OPTION(*ALL) RSTASP(*SAVASP)

  5. Verify the completion message of the command RSTLIB. You can use the command DSPJOBLOG to see messages before the completion message. If you find any problems during the restore with the result that objects were not restored, you need to correct these problems before continuing with the next steps.
  6. To restore objects in directories for the SAP system, enter the following command:

    RST DEV(<backup device>) OBJ(('/usr/sap/<SID>/*') ('/sapmnt/<SID>/*'))

    Note

    You must specify the Device parameter as '/QSYS.LIB/<devicename>.DEVD'.

  7. If you need to restore the common transport directory, which is often shared between multiple SAP systems, restore the related directories by entering the following command:

    RST DEV(<backup device>) OBJ(('/usr/sap/trans/*') ('/sapmnt/trans/*'))

    Note

    You must specify the Device parameter as '/QSYS.LIB/<devicename>.DEVD'.

  8. If your SAP data is stored in an independent ASP as described in SAP Note 568820 Information published on SAP site, restore the directories that were stored on the independent ASP by entering the following command:

    RST DEV(<backup device>) OBJ(('/<ASP device>/usr/sap/<SID>/*') ('/<ASP device>/sapmnt/<SID>/*') ('/<ASP device>/sapmnt/trans/*'))

  9. To recover changes to the database based on the entries in the journal receivers, see Recovering SAP Changes Since the Last Backup.
    Note

    This step is mandatory if the backup used SAVACTWAIT option *NOCMTBDY.