> CommCell Console > Backup and Restore Agents > Databases > Sybase > Sybase Backups

Backing Up Sybase Transaction Logs to a Disk

Run transaction log backups without a CommServe connection to reduce the CommServe load and to decrease the total number of jobs that run simultaneously.

A Sybase full backup will be converted to a transaction log backup when log dumps are found on the disk. The software starts a full backup automatically after the transaction log backup completes.

In a multiple stream scenario, the number of streams that the software uses for a transaction log backup to disk is less than or equal to the number of streams that you configured in the subclient properties in the CommCell Console.

Note: A Sybase step-by-step restore is not supported for transaction log backup to disk.

Before You Begin

Use additional settings to define the staging directory that log dumps are placed in. When you set this additional setting, the log dump and a metadata file that contains the database name, the timestamp and stripe information are placed in this directory.

You can define an additional setting so that all Sybase instances use the same directory.

  1. To the Sybase client, add the additional setting as shown in the following table.

    For instructions on how to add additional settings from the CommCell Console, see Add or Modify an Additional Setting.

    Note: If you have both levels set, the additional setting that is set for the instance takes precedence over the generic setting.

    Property

    Value

    Name

    • To specify the path for all Sybase instances, in the Name box, type sDiskDumpDir.

    • In cases where you have multiple Sybase instances that need to use separate directories, set an additional setting for each Sybase instance, in the Name box, type <sybaseServerName>_sDiskDumpDir.

      For example, to set the path for Sybase serverS155syb4, in the Name box, type S155syb4_sDiskDumpDir

    Category

    SybaseAgent

    Type

    String

    Value

    The directory path.

    Note: The directory_path must be the full path name.

    Example

    /sybase/syb155/dump

  2. Create the disk dump using the following command: 

    dump transaction dbname to 'SybGalaxy:: -disk' with blocksize=blocksize

    Parameter

    Definition

    dbName

    The Sybase database name

    blocksize

    The size of the Sybase data blocks
Single Stream Example: 
dump transaction db1 to 'SybGalaxy:: -disk' with blocksize=8192
Multiple Stream Example: 
isql -Usa -P -SS155syb4
 1> dump transaction db1 to 'SybGalaxy:: -disk' stripe on 'SybGalaxy:: -disk' with blocksize=8192
 2> go
 Backup Server session id is: 13. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
 Backup Server: 4.132.1.1: Attempting to open byte stream device: 'SybGalaxy::
 -disk -vm Instance002::00'
 Backup Server: 4.132.1.1: Attempting to open byte stream device: 'SybGalaxy::
 -disk -vm Instance002::01'
 Backup Server: 6.28.1.1: Dumpfile name 'db1141910BA44 ' section number 1
 mounted on byte stream 'SybGalaxy:: -disk -vm Instance002::00'
 Backup Server: 6.28.1.1: Dumpfile name 'db1141910BA44 ' section number 1
 mounted on byte stream 'SybGalaxy:: -disk -vm Instance002::01'
 Backup Server: 4.58.1.1: Database db1: 10 kilobytes DUMPED.
 Backup Server: 3.43.1.1: Dump phase number 3 completed.
 Backup Server: 4.58.1.1: Database db1: 18 kilobytes DUMPED.
 Backup Server: 3.42.1.1: DUMP is complete (database db1).

The following files are created as a result of the above transaction log backup.

drwxr-x--- 3 sybase sybase 4096 Jul 10 08:53 ..
 -rw-r--r-- 1 sybase sybase 18432 Jul 10 13:14 db1-2.XACT.1405023284.01
 -rw-r--r-- 1 sybase sybase 24576 Jul 10 13:14 db1-2.XACT.1405023284.00
 -rw-r--r-- 1 sybase sybase 231 Jul 10 13:14 1405023284_s1-2_LOG.metadata
 -rw-r--r-- 1 sybase sybase 231 Jul 10 13:14 1405023284_s0-2_LOG.metadata

Procedure

  1. Run a CommCell Console transaction log backup.

Result

After the job completes and the software finds the log dumps on the disk, the software then backs up the transaction log backups that were dumped on the disk in the next CommCell Console transaction log backup (a full backup converts to a transaction log backup. After the CommCell Console transaction log backup completes, the software deletes the dumped logs.

×

Loading...