Sybase backup strategy
One of the major tasks in developing a backup plan is to determine how often to back up your databases. The backup strategy in this section is an example. For guidelines on developing your own backup and recovery plan, refer to your Sybase documentation.
The frequency of your backups determines how much work you can restore in the event of a disaster. Dump each database immediately after you create it to provide a base point, and then dump it on a fixed schedule thereafter.
The following is an example database backup strategy:
- Perform a full database backup by running a database dump every Friday night.
- Back up your Sybase configuration files every Friday night at the same time as the full-database backup.
Sybase recommends that you save all the Sybase scripts. This includes the scripts that contain the disk init, create database, and alter database commands.
Sybase also recommends that you save a hard copy of your sysdatabases, sysusages, and sysdevices tables each time you issue one of these commands. In addition, keep a copy of the syslogins.
- Perform an incremental backup each night by running a transaction log dump.