Backing Up Runtime Data with a Recovery Server

Sybase recommends that you follow the documented steps to create a backup from which you can recover data.

1. Enabling Transaction Log Mirroring
   (Optional) Enable transaction log mirroring, if your backup strategy requires it. Mirror the transaction log files using the dblog command line utility to store the primary and mirror transaction logs on separate drives from the database file.
2. Creating a Recovery Server
   Use a recovery server to hold all recovery data for all databases on the data tier node. Use this data to recover any database on the data tier in the event of data loss or corruption.
3. Performing a Full Offline Backup After Install or Upgrade
   Back up the entire Unwired Platform runtime and data tier. The recommended time to do this is immediately after installaing or upgrading and before you startup these services, as you cannot perform offline backups while data services are running. .
4. Performing Periodic Incremental Transaction Log Backups Online
   Use periodic incremental live backups to prevent transaction logs from growing too large. Databases can remain online while this type of backup is generated. You can then apply incremental backups against the full backup on the recovery server.
5. Applying Increments to Full Backups on the Recovery Server
   Update the full backup with contents of the transaction log.