You can perform concurrent transaction log backups on Sybase databases that are Sybase ASE 15.7 SP100 version or later.
You can run a dump transaction concurrently with a dump database command, thereby reducing the risk of losing database updates for a longer period than that established by the dump policy. A dump transaction can be run concurrently while copying database pages. Any dump transaction that occurs concurrently with dump database cannot be loaded on top of that database. The dump transaction log will always be loaded to the preceding load sequence.
Advantage of running a concurrent transaction log backup is that we reduce the risk of losing database updates for a longer period. Consider a scenario where full database backup operation runs from 9 am to 1 pm, and concurrent log backup operation runs at 10 am, 11 am, and 12:30 pm. In case of a database crash at 12:45 pm when dump database is still running, we can recover database till 12:30 pm as log backup was running at that time. The dump transaction log will be loaded on the previous full cycle.
Note
Dump transaction does not truncate the transaction log while it is running concurrently with dump database.
Before You Begin
-
Enable concurrent dump transaction parameter at Sybase ASE Server using the following query:
sp_configure "enable concurrent dump tran" , 1 -
Create the additional setting JMSybaseConcurrentLogBackupsEnabled, set its value to 1, and then restart the CommServe services.
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:
-
In the Backup Type section, select Transaction Log.
-
In the Job Initiation section, choose to run the backup now or schedule it.
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.