Loading...

Advanced Backup - Sybase Agent

Table of Contents

Full Backups

Full backups provide the most comprehensive protection of data.

Backups for any client start with a full backup. The full backup becomes a baseline to which subsequent backup types are applied. For example, a full backup must be performed before an archive log backup can be initiated.

You can perform a full backup of an online or offline database. The default is online backup.

Use the following steps to run a full backup:

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Full option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Transaction Log Backups

A transaction log backup captures the transaction log which contains a record of all committed or uncommitted transactions. Transaction log backups are consistent with the start time of the backup.

The use of transaction log backups make point-in-time recovery possible. This is useful in the scenario of a database failure where it is unacceptable to lose any data and you want to restore to the point of failure. If you use only full backups, you will be able to restore to the time of the backup, but not to a point-in-time between backups.

A transaction log backup is similar to a traditional incremental backup you might perform on a file system because the transaction log backup contains only the new changes since the full or another transaction log backup.

Each time a transaction log is backed up it is truncated to the exact time of the backup. No checkpoint is issued at this time, therefore dirty pages are not written to disk before or after a transaction log backup. If there are dirty pages, any completed transactions will need to be rolled forward if a transaction log restore is performed. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup.

Use the following steps to run a transaction log backup:

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Transaction Log option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Back Up Transaction Log of Damaged Database (Do Not Truncate Logs)

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.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the subclient and click Backup.
  3. 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.

  4. Click OK to close the Backup Options dialog box.

Skipping Full Backups for Recently Added Databases after a Log Backup

You can use this procedure to skip a full backup for recently added databases after a log backup.

Note: A log backup for a recently added database does not run until you perform a full backup.

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the subclient and click Backup.
  3. 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 Sybase Skip Full for Newly Added database after Log Backup (Sybase).
    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.

Performing Cumulative Incremental Backups

You can perform cumulative incremental backups on Sybase databases that are Sybase ASE 15.7 SP100 version or later.

A Sybase cumulative incremental backup contains the changed data from the last full backup. Cumulative incremental backups use less media and resources than full backups.

The following are advantages of cumulative incremental backups.

  • You can rollforward a full backup of a database without having to back up the entire database.
  • The recovery time is minimized because most of the changes are already applied.
  • The software has tracked the changes that you need to recover the database with a minimal amount of logging.
  • The backup size is smaller, especially for databases that contain large read-only tables.
  • The backup performance is improved for database loads that have updates on a subset of database pages.

A cumulative backup is not supported for the following Sybase database types:

  • The master database
  • Proxy databases
  • Temporary databases.

Before You Begin

You must configure the Sybase database to maintain the list of pages that must be dumped.

You can use the sp_dboption system procedure to enable this feature.

Syntax

sp_dboption dbname, 'allow incremental dumps', true

Parameters

The following table describes the parameters.

Parameter Description
database_name The name of the database that you want to use for the backup.
option The option that you want to set for the database. Use 'allow incremental dumps'.
true Use 'true' to set the feature.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Cumulative Incremental option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Performing On-Demand Backups

You can use an external input file to specify the content when you perform an On-Demand backup.

Note: If you use Sybase ASE version 15.7 ESD #2 (SP100) or later, you can configure the Sybase software to run transaction log dumps even when a full or cumulative dump is running. Set 'enable concurrent dump tran' to 1 to use this feature. When this feature is enabled and you run a restore, there is a possibility that the transaction log load order goes out of sequence. The following error may occur:

Specified file 'dump device' is out of sequence. Current time stamp is Nov 3 2015 1:59:59:423AM while dump was from Nov 3 2015 1:59:59:296AM.

Before You Begin

  1. Create an On-Demand subclient by using the command line interface. For information on how to configure the subclient, see Specifying Sybase Databases for On-Demand Backups Using the SnapProtect Command Line Interface.
  2. Create a text file (called a directive file) that contains the list of databases that you want to back up.

Note: The file must contain one database on each line and must contain all the databases to back up.

Example

An input file with 3 databases

db1
db2
db3

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the On-Demand subclient and click Backup.
  3. On the Backup Options for Subclient dialog box:
    1. In the Directive File box, type or browse to the full path and name to the directive file that you created.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Performing SQL Anywhere Backups

Use dbbackup utility to perform image backups. dbbackup creates a backup copy of all the files for a single database. The image backup created by the dbbackup utility consists of a separate file for each file that is backed up.

Use dbunload utility to obtain the SQL dump of the database, which can later be used to rebuild the database. Use the file system agent to backup the obtained reload file and associated dumped data.

Performing Image Backup

Performing a SQL Anywhere Data backup:

You must perform FULL backups of the subclient created for SQL Anywhere image data backups. You can perform them manually or schedule them at periodic intervals.

Use the following steps to perform a full data backup.

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the SQL Anywhere subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Full option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Performing an SQL Anywhere Log backup:

You must perform frequent Incremental backups of the subclient created for SQL Anywhere image log backups as the system will pick up only the recent transaction log copies generated in the log backup directory. You can perform them manually or schedule them at periodic intervals.

Use the following steps to perform an incremental log backup:

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the SQL Anywhere log subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Full option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

Performing Dump Backup

Perform the backups of the subclient created with obtained reload file and associated dumped data at periodic intervals.

Use the following steps to perform a dump backup:

  1. From the CommCell Browser, expand Client Computers > client > Sybase > instance.
  2. Right-click the SQL Anywhere dump subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select the Full option.
    2. 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.

  4. Click OK to close the Backup Options dialog box.

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 running simultaneously.

Once this is completed, the transaction log backups dumped on the disk are backed up in the next CommCell Console transaction log backup.

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

A Sybase full backup will be converted to a transaction log backup when log dumps are found on the disk. A full backup will be kicked off 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.

Procedure

You can 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 is placed in this directory.

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

Use the following syntax to specify the additional setting for all Sybase instances. Set this additional setting in the etc/CommVaultRegistry/Galaxy/Instance001/SybaseAgent directory.

Note: The directory_path must be the full path name.

sDiskDumpDir <directory_path>

In cases where you have multiple Sybase instances that need to use separate directories, you can set an additional setting for each Sybase instance.

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

Use the following syntax to specify the additional setting for a specific instance, substituting the sybaseServerName and directory_path with your values. Set this additional setting in the etc/CommVaultRegistry/Galaxy/Instance001/SybaseAgent directory.

Note: The directory_path must be the full path name.

<sybaseServerName>_sDiskDumpDir <directory_path>

Example:

S155syb4_sDiskDumpDir /sybase/syb155/dump

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
Expand All

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

Managing Jobs

For information on how to manage the job, see Job Controller Overview.