Backing Up Sybase Transaction Logs of a Damaged Database

In Sybase server, some databases may not have log devices. By default, when you perform a log backup, the system performs log backups of those databases that possess transaction logs. Hence, it is necessary to perform a full backup after a log backup. A full backup will perform a backup of all databases irrespective of the fact that they may or may not possess transaction logs.

You can see this procedure when your data device fails and the database is inaccessible to get a current copy of the log. The option in this procedure does not truncate the log. In this case, you will want to capture all transaction log events that have occurred since you ran the last backup.

Note

You can only use this procedure when the transaction log is on a separate segment from the database and the master database is accessible.
If a database does not have a log segment on a separate device from the data segments, you cannot run transaction log backup operation.

Procedure

From the CommCell Browser, expand Client Computers > client > Sybase > instance.
Right-click the subclient and click Backup.
On the Backup Options for Subclient dialog box, select the backup type and job initiation:
1. In the Backup Type section, select Transaction Log.
2. In the Backup Type section, select Do Not Truncate Log.
3. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.
  
  Note: If you selected Schedule, set up the schedule.
  
  For information on configuring a backup schedule, see Schedule Backups.
Click OK to close the Backup Options dialog box.