Backup and Disaster Recovery

SAP recommends that you use your standard complete backup procedures for all host nodes. In case of catastrophic failure, you can completely restore these hosts to their previous state as of the last backup.

The complete backup of a host includes:

File artifacts of installed software components that make up SAP Mobile Platform
Registry entries (so that the installed software and services can all run properly after the restore)

Note: When you back up the SAP Mobile Platform Runtime installation, be aware that the default path to the embedded Web container in the SCC-3_2 folder is too long for Windows to process. Before launching the backup, delete the contents of SCC_HOME\services\EmbeddedWebContainer\container\Jetty-7.6.2.v20120308\work. By default, SCC_HOME is C:\SAP\SCC-3_2). Delete the contents of this folder from the command prompt, not from Windows Explorer.

If you are backing up a single-node cluster, SAP recommends that you reinstall to a new host and add a new node to an existing cluster. This installation option automatically ensures that the same messaging server keys and required artifacts (for example, RSOEs, or installation of third-party software, such as JDBC drivers for non-SAP EIS databases) are shared and configured correctly. Document these backup and configuration requirements in the internal project documentation. For assistance, see Completing Installation Worksheets in Landscape Design and Integration.

Backup and Recovery Life Cycle Stages
Stage	Activity	Frequency
Backup	Plan the backup strategy and understand the artifacts that need to be backed up.	Infrequent. Typically, before installing, or as business requirements, backup strategy, or enterprise policies dictate.
	Back up the artifacts and components that need to be preserved for restoring in case of failure.	Recurring. Typically set up as a scheduled activity based on the planned backup strategy.
Maintenance	Monitor the backup environment.	Routine. Ensure the backup process is working as planned.
	Test the backup process.	Routine. As part of regular company disaster recovery compliance process.
Diagnostics	Diagnose the issue and determine if recovery is required.	As needed. When a failure or disaster happens.
Recovery	Recover from data loss or failure.	As needed. When a failure or disaster happens.

Backing Up
All runtime data is stored in the data tier, which allows you to easily back up the entire system, and recover data as required.
Maintaining Backups
Carefully maintain your backup artifacts, so you can use them to recover your lost data following a hardware failure or other system problem.
Diagnosing Failures
The recovery procedure to use depends on the failure scenario you are addressing. Always diagnose your failure before following a particular course of action.
Recovery Solutions
You can perform recovery procedures for failure scenarios.