Skip to Content

SUP: Backup and Restore process


This following document highlights the necessary processes for backup in the Sybase Unwired Platform area.

For further information please refer to the “System Administration Section” of Sybase UnwiredPlatform documentation

Backup and recovery
Strategies follow 2 different avenues:

1. Error correction

2. Disaster recovery

This document focuses on error correction. For disaster recovery, you may need to engage with other vendors that provide solutions
geared to maintaining the viability of your entire enterprise.


Initial Backup

An initial complete file system backup of the operating system and Sybase Unwired Platform installations needs to be performed

Package Backup

The packages should be exported and backed up on a regular basis

A package to bundle one or more MBOs and package options in the selected package to create a new instance of a deployment archive. Typically, export is used to move the package contents onto another Unwired Server, however you can only import packages to the same domain as it was exported from.

Note: It is a requirement to create domains in the same order in both the export and import server environment to ensure that an internal ID assigned to the domain in both environment matches. You can verify the internal ID assigned to a domain by looking at the prefix used in the package folder in the exported zip.

1. In the left navigation pane, expand the Packages folder.

Left hand.png

2. In the right administration pane, check the box adjacent to the name of the package and click Export.

The Export Package dialog appears.

3. Check the appropriate export package options from the list: Include synchronization tracing, Include package logging,,Include role  mappings, and Include device notification templates (for RBS packages only).

These selections determine which package settings are retained for the new instance of the package. The current security configuration for the package is automatically applied to the exported package.

4. Click Next

5. Select the file system target for the exported contents and click OK.

Note: Ensure that you
do not hide file type extension when you name the export package; otherwise, when the *.zip extension becomes invisible, which adversely affects the outcome of the export process.

A status message on the General tab indicates the success or failure of the export transaction. If successful a ZIP file is created in the location you specified. You can then use this file to import the package.

Folders and registry backup

The following folders to be backed up regularly together with Windows registry

<UnwiredPlatform_InstallDir>\Servers\UnwiredServer\Repository <UnwiredPlatform_InstallDir>\Servers\Advantage910

<Install Drive>:\Sybase\SCC-3_0\conf

<Install Drive>:\Sybase\SCC-3_0\log

<Install Drive>:\SCC-3_x\services\repository\repository.db

The Windows Registry needs to be backed together with the file system.

Database Backup and Validation

The databases need to be backed up on a regular basis.

SQL-Anywhere databases:

To backup the databases, run the following commands at the command prompt or in a batch file

For consolidated databases, run:

dbbackup -c “ENG=<clusterName>_primary;DBN=default;UID=dba;PWD=SQL” \<backup dir>

For cluster databases, run:

dbbackup -c “ENG=<clusterName>_primary;DBN=clusterdb;UID=dba;PWD=SQL” \<backup dir>

For monitor database, run:

dbbackup -c “ENG=<clusterName>_primary;DBN=monitor;UID=dba;PWD=SQL” \<backup dir>

Note: If you
use the parameter –x in the backup command, it reduces the log file size to 320 KB. This procedure can also be used to shrink the log files.


Example: dbbackup -c “ENG=<clusterName>_primary;DBN=monitor;UID=dba;PWD=SQL”
–x \<backup dir>


After the backup, copy the database files to temporary location and validate as follows:

For consolidated databases, run:

dbvalid.exe -c “DBF=<temp_location>\default.db;UID=dba;PWD=sql

For cluster databases, run:

dbvalid.exe -c “DBF=<temp_location>\clusterdb.db;UID=dba;PWD=sql

For monitor database, run:

dbvalid.exe -c “DBF=<temp_location>\monitorindb.db;UID=dba;PWD=sql

When the verification is successful the backups should be moved to a different server or to tape.

Messaging database

Use the adsbackup utility to back up messaging data. You can then use MORecover to recover the data to an existing database.

The backup target can be any folder. A collection of files constituting the backed-up data is created in a folder you specify.

Note: Backup
files only include raw data in the original tables, without the index data.
Therefore, they cannot be used directly as a database and must be recovered with MORecover before they can be used

You can schedule this command to run regularly when your system is lightly loaded, since the backup operation runs simultaneously with the messaging server’s normal processing.

  1. Change to <UnwiredPlatform_InstallDir>\Servers\AdvantageXXX\Server.
  2. Run the adsbackup utility to create a MORecover snapshot; for example:
  3. adsbackup.exe


Restoration of the Installation File System

The file system needs to be restored, first with the initial backup and then the current backup of regularly backed up files and the windows registry.

Restoration of the Database

To restore the databases, delete the existing db and log files from the following location and copy the latest backup files to these location.





Restoration of the Messaging Data

Restore the Sybase Unwired Platform messaging data tables from a backup by running the MORecover utility.

You can find this utility in the <UnwiredPlatform_InstallDir>\Servers\Messaging\Server\Bin folder.

Before running MORecover to restore your database, convert the data files created by adsbackup back to a standard database format, by running adsbackup with the -r option. You can then use MORecover to restore the backed-up data.

For example, if you sent your backed-up data output to c:\bak, but restored the data to c:\bak\restore, the command line syntax for
adsbackup is:

  1. adsbackup.exe -r “c:\bak\obr.add”

When you run the MORecover utility, use the restore location. For example:

MORecover “c:\bak\restore\obr.add”


Stephen M Dick

Customer Support leader, team builder, process designer.

Other content written by the author here.

View Stephen M Dick's profile on LinkedIn

You must be Logged on to comment or reply to a post.