Advanced Backup - Sybase iDataAgent

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, navigate to Client Computers | <Client> | Sybase | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  1. Select Full as the backup type and click Immediate.
  2. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup job has completed, the Job Controller displays Completed.

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, navigate to Client Computers | <Client> | Sybase | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  1. Select Transaction Log as backup type.
  2. Click Immediate.
  3. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup has completed, the Job Controller displays Completed.

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 after a Log Backup

It is necessary to perform a full backup after a log backup. However, you may not always need a full backup after a log backup. Use the following steps to skip a full backup immediately after a log backup:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Sybase | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  1. Select Transaction Log as backup type.
  2. Select Sybase Skip Full after Log Backup (Sybase).
  3. Click Immediate.
  4. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup has completed, the Job Controller displays Completed.

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 bo

Performing On-Demand Backups

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

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

Best Practice: 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. When you want to perform an on-demand backup on the Sybase server, set 'enable concurrent dump tran' to 0. If you have set the value to 1, you may an encounter an error during the restore. For more information, see  A Restore of an on-demand backup fails.

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. Select the Job Initiation as Immediate, or Schedule. Configure the schedule. See Schedule Backups.
  4. Click OK to close the Backup Options dialog box.

Performing SQL Anywhere Backups

Use the dbbackup utility to perform image backups. The dbbackup command 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 the  dbunload utility to obtain the SQL dump of the database, which can later be used to rebuild the database. Use the file system iDataAgent 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, navigate to Client Computers | <Client> | File System iDataAgent | <BackupSet>
  2. Right-click the Subclient created for SQL Anywhere data backups, and click Backup.

  3. Select Full as the backup type and click Immediate.
  4. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup job has completed, the Job Controller displays Completed.

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, navigate to Client Computers | <Client> | File System iDataAgent | <BackupSet>
  2. Right-click the Subclient created for SQL Anywhere log backups, and click Backup.

  3. Select Incremental as the backup type and click Immediate.
  4. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup job has completed, the Job Controller displays Completed.

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, navigate to Client Computers | <Client> | File System iDataAgent | <BackupSet>
  2. Right-click the Subclient created for SQL Anywhere dump backups, and click Backup.

  3. Select the backup type and click Immediate.
  4. Click OK.

    You can track the progress of the job from the Job Controller.  When the backup job has completed, the Job Controller displays Completed.

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 he database name, the timestamp and stripe information is placed in this directory.

You can define this additional setting on a generic level that applies to all Sybase instances, or you can use an additional setting for a specific Sybase instance when you want to have a separate directory for an instance.

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

Set these additional settings in the etc/CommVaultRegistry/Galaxy/Instance001/SybaseAgent directory.

Use the following syntax to specify the additional setting for a specific instance, substituting the sybaseServerName and directory_path with your values.

Note: The directory_path must be the full path name.

<sybaseServerName>_sDiskDumpDir <directory_path>

Example:

S155syb4_sDiskDumpDir /sybase/syb155/dump

Use the following syntax to specify the additional setting for all Sybase instances.

Note: The directory_path must be the full path name.

sDiskDumpDir <directory_path>

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:

sybase$/sybase/syb155/dump/S155syb4/db1>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

Scheduling a Backup

Follow the steps given below to schedule a backup:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Sybase.
  2. Right-click the <Subclient> and click Backup.
  3. Select the Backup type.
  4. Click Schedule to schedule the backup for a specific time.
  5. Click Configure to set the schedule for the backup job. The Schedule Details dialog is displayed.

  6. Select the appropriate scheduling options.  For example:
    • Click Weekly.
    • Check the days you want the run the backup job.
    • Change the Start Time to 9:00 PM.
    • Click OK to close the Schedule Details dialog.
    • Click OK to close the Backup Options dialog.

    The backup job will execute as per the schedule.

Managing Jobs

Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel.

Changes made to this configuration will affect all jobs in the entire CommCell.

To configure the job restartability for a specific job, you can modify the retry settings for that job. This will override the setting in the Control Panel. It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.

Backup jobs for this Agent are resumed from the point-of-failure.

Configure Job Restartability at the CommServe Level

  1. From the CommCell Console ribbon, click the Home tab, and then click Control Panel.
  2. Under System, click Job Management.

    The Job Management dialog box appears.

  3. Click Job Restarts tab.
  4. From the Job Type list, select the appropriate item.
  5. Select the Restartable check box to make the job restartable.
  6. In the Max Restarts box, change the maximum number of times the Job Manager will try to restart a job.
  7. In the Restart Interval (Mins) box, change the time interval between attempts for the Job Manager to restart the job.
  8. Click OK.

Configure Job Restartability for an Individual Job

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Sybase | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  1. Click Advanced.
  2. In the Advanced Backup Options dialog box, click the Job Retry tab.
  3. Select Enable Total Running Time and specify the maximum elapsed time before a job can be restarted or killed.

    Select Kill Running Jobs When Total Running Time Expires to kill the job after reaching the maximum elapsed time.

  4. Select Enable Number Of Retries and specify the number of retries.
  5. Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspend

Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.

Resume

Resumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting.

Kill

Terminates a job.

Suspending a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.
  2. The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Resume.
  2. As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Kill.
  2. Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

Additional Options

The following table describes the available additional options to further refine your backup operations:

Option Description Related Topics
Startup Options

The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and click Startup tab.
  3. Select the Change Priority checkbox.
  4. Enter a priority number - 0 is the highest priority and 999 is the lowest priority.
  5. Select the Start up in suspended State check box to start the job in a suspended state.
  6. Click OK.
Refer to Job Priority and Priority Precedence.
Alerts

This option enables users or user groups to get automatic notification on the status of the data protection job. Follow the steps given below to set up the criteria to raise notifications/alerts:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Alert tab.
  3. Click Add Alert.
  4. From the Add Alert Wizard dialog box, select the required threshold and notification criteria and click Next.
  5. Select the required notification types and click Next.
  6. Select the recipients and click Next.
  7. Click Finish.
  8. Click OK.
Refer to Alerts and Notifications.
Vault Tracker

This feature provides the facility to manage media that is removed from a library and stored in offsite locations. Depending on your Vault Tracker setup, select the required options. Use the following steps to access and select the Vault Tracker options.

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Vault Tracking tab.
  3. Select the required options.
  4. Click OK.
Refer to Vault Tracker.
Extended Data Retention

This option allows you to extend the expiration date of a specific job. This will override the default retention set at the corresponding storage policy copy. Follow the steps given below to extend the expiration date:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Media tab.
  3. Select one of the following options:
    • Infinite - Select this option to extend the expiration date by infinite number of days
    • Number of day - Select this option to specify the number of days to extend the expiration date and then enter the number of days.
  4. Click OK.
Refer to Extended Retention Rules.
Allow Other Schedules To Use Media Set

The Allow Other Schedules to use Media Set option allows jobs that are part of the schedule or schedule policy and using the specific storage policy to start a new media. It also prevents other jobs from writing to the same set of media.

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Media tab.
  3. Select the Allow Other Schedules To Use Media Set check box.
  4. Click OK.
Refer to Creating an Exportable Media Set.
Mark Media Full

This option marks the media as full, two minutes after the successful completion of the data protection job. This option prevents another job from writing to this media. Follow the steps given below:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select Media tab.
  3. Select the Mark Media Full on Success check box.
  4. Click OK.
Refer to Start New Media.
Start New Media

The Start New Media option enables you to start the data protection operation on a new media. This feature provides control over where the data physically resides. Use the following steps to start the data protection operation on a new media:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Media tab.
  3. Select the Start New Media check box.
  4. Click OK.
Refer to Start New Media.
Data Path Options

Data Protection operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path:

  1. From the CommCell Browser, navigate to Client Computers  | <Client> | Sybase | <Instance>.
  1. Right-click the Subclient in the right pane and click Backup.
  2. Click Advanced and select the Data Path tab.
  3. Select the MediaAgent and Library.
  4. Select the Drive Pool and Drive for tape library.
  5. Click OK.
Refer Change Data Path.
CommCell Readiness Report The CommCell Readiness Report provides you with vital information such as connectivity and readiness of the Client, MediaAgent, and CommServe. It is useful to run this report before performing a backup or a recovery operation. Follow the steps given below to generate the report:
  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Readiness.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | CommServe | CommCell Readiness in the left pane.
  4. Select the Computers tab, and then click Modify below the Computers list.
  5. In the dialog box that appears, clear Include All Client Computers and All Client Groups.
  6. Select the appropriate client from the Exclude list, and then click Include >.
  7. Click OK.
  8. Select the MediaAgent tab, and then clear Include All MediaAgents.
  9. Select the appropriate MediaAgent from the Exclude list, and then click Include >.
  10. Click Run.

    The report appears in your default Web browser.

Refer to CommCell Readiness Report.
Backup Job Summary Report The Backup Job Summary Report provides you with information about all of the backup jobs that are run in last 24 hours for a specific subclient. You can get information such as status, time, data size, and so on for each backup job. It is useful to run this report after performing the backup. Follow the steps given below to generate the report:
  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Summary.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | Jobs | Job Summary in the left pane.
  4. On the General tab, select Data Management.
  5. Select the Computers tab.
  6. Select Subclient, and then select the Edit sub tab.
  7. Navigate to Client Computers | <Client> | File System | Backup Set | <Subclient>.
  8. Click Run.

    The report appears in your default Web browser.

Refer to Backup Job Summary Report.