Performing Backup and Recovery of the J2EE Engine 

Use

The backup of the J2EE Engine and the concerning database prevents you from data loss and is essential for a recovery of the J2EE Engine after a breakdown of the system.

This document describes

·        what has to be performed after the first installation and after an upgrade of the J2EE Engine

·        what has to be included in the backup

·        what measures have to be taken to enable a recovery of a J2EE Engine after a disasterous breakdown of the system

·        how the recovery has to be carried out.

Prerequisites

The backup tools for your database and the backup solution for your system must be installed and available.

If you are not yet decided which backup strategy fits to your system needs, refer to the documentation of your database. In case of the SAP DB you find information under www.sapdb.orgor in the online-documentation under The SAP DB Database System  ®Security Concepts ® Backup Strategy  ®  Data Backup and Backup Medium.

In case you run an Oracle database and want to use the SAP BR Tools for your backup procedure, refer to SAP Note 320457.

First Backup after Installation and Upgrade

After the installation and every upgrade of the J2EE Engine you should carry out a first

·        filesystem backup of the J2EE Engine (standard path /usr/sap/<SID>/JC<inst-nr>)

·        filesystem backup of the Software Deployment Manager (SDM). For the description how to backup the SDM refer to the paragraph below.

·        filesystem backup of the database home directory (standard path SAPDB: <drive>:\sapdb, Oracle: <drive>:\orant)

Backup Routine

We recommend to include the online backup of the database as well as the logs in the daily routine. Once a week an offline backup should be carried out.

A filesystem backup of the Software Deployment Manager (SDM) should be performed after software deployment and after the implementation of patches.

If your J2EE Engine is mostly used for development, include the SDM backup in your daily routine!

Procedure

A complete backup including all the modifications of the J2EE Engine from installation on consists of a backup of the databases, the Software Deployment Manager (SDM) and the deployed applications.

Databases

The backup of the database can be executed during online operation.

For information on how to make a backup of your database refer to the specific documentation.

·        In case of SAP DB you find the detailed description in the online documentation under SAP DB Database System ® Security Concepts ® Backup Strategy.

·        If you run an Oracle database, refer to the SAP Database Guide: Oracle ® Backup, Recovery, and Restore.

·        If you have an IBM DB2 Universal Database, refer to the SAP Database Guide: IBM DB2 Universal Database for iSeries ® Backup and Recovery

·        If you have an SQL Server 2000 DBA, refer to the SAP Database Guide: SQL Server 2000 DBA ® Database Backup.

 

 

 

Software Deployment Manager (SDM)

Include the complete SDM directory (standard path /usr/sap/<SID>/JC<inst-nr>/SDM) in the backup.

The SDM contains a list of all deployments that were installed outside of the database, you can see them within Software Deployment Manager GUI in the SDM Repository view under FileSystem and SAP J2EEEngine.

Each development component owner for filesystem software has to specify whether there is specific data to be included in the backup.

SDM should not be running during backup.

Applications

For every SAP application running on your SAP J2EE Engine refer to the corresponding Solution Manager Guide and carry out the described backup procedures.

Restore

To restore your J2EE Engine after breakdown follow the steps described below:

·        Install a new system using the installation wizard SAPinst as described in the installation manual.

The installation guide for SAP Web AS can be found on the SAP Service Marketplace:

http://service.sap.com/instguides

Choose SAP Web Application Server ® Release 6.30 ®Installation Guide - SAP Web Application Server on <Platform>: <Database>

Use exactly the same parameters as in the previous installation you want to restore!

·        Overwrite the mentioned parts of the system by the backup-copies as described below

Java Instances

Overwrite the installed Java Instance (standard path: /usr/sap/<SID>/JC<inst-nr>)

Databases

...

Import the backup using the database specific management tools (e.g. SAPDB: Database Manager, Oracle: brrestore). You find detailes documentation as mentioned above.

After the database has been imported, you also have to import the available log backups.

You find detailed documentation for SAPDB under The SAPDB Database System   ® Security Concepts ® Restartability .

SDM

Overwrite the installed SDM.

Applications

Follow the description in the corresponding Solution Management Guides to recover your SAP applications. You find these guides on the SAP Service Marketplace.

Restart

Restart the J2EE Engine (see Starting and Stopping the SAP System).

Result

The J2EE Engine is restored with the last backup.