Restore the latest backup database file to the data tier whose data
is lost.
- Copy the latest full backup database file and latest incremental
database log to the data tier whose data is lost.
If the backup database and transaction log have been kept in the host that
is the recovery server, skip this step.
- Apply the incremental log to the full backup database to make sure the database
file is recovered to the last correct status.
For example, use the
dbeng16 command to apply the latest
incremental log file to the
defaultdb.
dbeng16 -o
defaultError.log C:\smpbackup\full\default.db -ad C:\smpbackup\incremental\
- Copy the restored database files to the data directory of the data tier.
- Restart SAP Mobile Platform services on the data tier.
- Restart SAP Mobile Server services on the
SAP Mobile Server node.
Next
To make recovery and resynchronization with the server easier,
SAP recommends that you include application code that
checks for, and recovers from SAP Mobile Server failures. In the developer guides, see
Developing the Application Using the Object API >
Recovering From
Server Failures.
If your application does not include code that recovers and
resynchronizes with the server, and if the device is registered at the time of the
backup recovery point and the device registration was lost in the server when restoring
from the old database, you must perform a recovery procedure to make your application
operational again.
Restoring from an older backup can result in data loss
including transactions sent to or retrieve/received from back end systems, client
offline data, and SAP Mobile Platform settings. You need to assess the
data loss and, if applicable, and resubmit or reapply the data.