Backing Up and Restoring AS Java 
Backing up the AS Java and the relevant database prevents you from data loss and is essential for the recovery of the server after the system breaks down.
You can use the backup data to restore your system in various scenarios. For example, you can:
Restore the initial state of the system if an installation or upgrade fails
Restore the SAP NetWeaver AS installation in case of operating system or file system problems
Restore the SAP system data if the database crashes, and so on.
You can apply two backup strategies:
Offline backup - this strategy enables you to create a full and reliable backup of your system, so that the system can be restored in case of a hard disk crash or operating system problems. This strategy requires system downtime, and therefore is not very suitable to be performed on a daily basis.
Online backup - using this strategy, you can backup the database and the file system, which enables you to recover only particular components of your system. It does not require full system shutdown, and therefore is convenient for creating regular incremental data backup. Online backup does not guarantee a full and consistent backup of all system components.
Note
Backing up the system is transparent for the AS Java and its users.
Recommendation
We recommend that you perform regular offline and online backups of your system and system components. The frequency recommendations provided further in this text are only advisable. The frequency of the offline and online backups of your system should be determined by you depending on your scenario, the changes that you make in the system, the occurrence of other important system events, and your requirements for system downtime.
The backup tools for your database and the backup solution for your system are installed and available.
The most important administration tasks related to backing up and restoring that you need to perform in the AS Java are listed below:
After installation or before and after upgrade of AS Java, you need to perform a full offline backup of your system. For more information, see the relevant installation guides on SAP Service Marketplace at .
Recommendation
Include the JDK installation directory in the offline backup as well.
After the initial offline backup, you should also perform offline backup once a week.
After you have created a full backup of your system, you should perform regular online backups of the following components:
Database
Recommendation
We recommend that you include the online backup of the database as well as the logs in the daily routine.
In case the deployed applications use an external database as a persistent storage, make sure that you back up that database, too.
Note
The consistency of data when you back up more than one database is the responsibility of the user.
You can create a backup copy of your database so that you can recover the database if errors occur. For more information, see Database Administration.
File system
Create a backup of the SAP system directory /usr/sap/<SID>.
Note
To ensure that no changes are made to the file system during backup, stop the Software Deployment Manager (SDM).
Shut down the system.
Install a new AS Java system using SAPInst, or restore the file system from the offline backups that you created.
Import the database backup using the relevant tools provided by the database vendor.
Overwrite the SAP system directory /usr/sap/<SID>.
Start the system (see Starting and Stopping SAP NetWeaver ABAP and Java.)
The J2EE Engine is restored with the last backup.
For more information, see the relevant system copy guides on SAP Service Marketplace at service.sap.com.