V11 SP8
Loading...

Backup Troubleshooting - Sybase iDataAgent

Table of Contents

SYB0001:  CLSybBrowse150.exe - System Error when Configuring Sybase Instance on Windows Configuration

Issue

On a Windows configuration, the following error message is received when configuring an instance.

CLSybBrowse150.exe - System Error

Resolution

Verify the following paths are added to the System Variables.

%SYBASE%\%SYBASE_ASE%\bin

%SYBASE%\%SYBASE_ASE%\jobscheduler\bin

%SYBASE%\%SYBASE_ASE%\dll;

%SYBASE%\%SYBASE_OCS%\lib3p64;

%SYBASE%\%SYBASE_OCS%\lib3p

%SYBASE%\%SYBASE_OCS%\dll

%SYBASE%\%SYBASE_OCS%\bin

%install_path%\Base

Variable Definition
%SYBASE% SYBASE HOME - the base install path
%SYBASE_ASE% The Sybase ASE folder name
%SYBASE_OCS% The Sybase OCS name
%install_path% The software install directory name
Expand All

Example

SYBASE HOME is E:\sybase\syb157

SYBASE_ASE folder is ASE-15_0

SYBASE_OCS folder is OCS-15_0

Verify the following System Path entries

 E:\sybase\syb157\ASE-15_0\jobscheduler\bin

E:\sybase\syb157\ASE-15_0\dll;

E:\sybase\syb157\ASE-15_0\bin

E:\sybase\syb157\OCS-15_0\lib3p64;

E:\sybase\syb157\OCS-15_0\lib3p ·

E:\sybase\syb157\OCS-15_0\dll

E:\sybase\syb157\OCS-15_0\bin ·

C:\install_path\Base

SYB0002: Instance Configuration Error

Issue

Sometimes, you may receive an error while configuring Sybase server instance. You may receive this error when you try to set the Sybase server parameter net password encryption to 2.

Resolution

As a workaround, add the following entries manually in OCS.CFG file to avoid the error:

[DEFAULT]
CS_SEC_EXTENDED_ENCRYPTION = CS_TRUE

[isql]
CS_SEC_EXTENDED_ENCRYPTION = CS_TRUE

[ClSybAgent]
CS_SEC_EXTENDED_ENCRYPTION = CS_TRUE
 

You can find the OCS.CFG file at the following location:

Unix
$SYBASE/$OCS/config/ocs.cfg
Windows
$SYBASE/$OCS/ini/OCS.CFG

SYB0003: Invalid Argument

Issue

Sometimes, backup jobs may fail with the following error:

Invalid Argument.

This issue occurs when you use Sybase 15.5 ESD #4. The backups will not fail if you use 15.5 GA binary (backupserver and sybmultbuf).

Resolution/Workaround

Set the block size.

SYB0004: Failure of Backups Performed from a Remote Desktop on Windows

Issue

Currently, backups and restores cannot be performed from a remote desktop on Windows.

Resolution/Workaround

Use any one of the following solutions that suits your setup:

  • Login to remote desktop using the following command:

    mstsc /v:winclient /console

  • Use netmeeting
  • Use telnet
  • Use the clients console

SYB0005: Backup Failure Due to Incorrect Backup Server Name

Issue

If there is a mismatch between an actual backup server name and the name existing in sysservers table of master database, backup fails with the following error message:

Could not establish communication with Backup Server 'SYB_BACKUP'. Please make sure that there is an entry in Sysservers for this server, and that the correct server is running.

Resolution/Workaround

Verify and update the srvnetname of backupserver in sysservers table:

update master.dbo.sysservers set srvnetname = "<Backup-Server-Name>" where srvname = "SYB_BACKUP"

Verify the backupserver entry in interface file and that the backup server name is same as mentioned in instance properties.

SYB0006: Backup Fails After an Upgrade to Commvault V11

Issue

The Sybase backup may fail after you upgrade to Commvault V11, or when you reinstall the Sybase Data Agent, with the following error.

"ClSybAgent::VerifySybVersion() - Sybase is not installed with latest Galaxy package for Home [/Apps/sybase/syb157] 684 2ac 03/11 08:02:33 389627 ClSybAgent::DoBackupOrRestore() - VerifySybVersion failed 684 2ac 03/11 08:02:33 389627 main() - DoBackupOrRestore failed"

Resolution/Workaround

The Commvault file called libSybGalaxy.so is updated when you create a Sybase instance. After you upgrade, save the instance properties.

  1. From the CommCell Browser, expand Client Computers > client >Sybase.
  2. Right-click the instance, and then click Properties.

    The Instance Properties dialog box appears.

  3. On the General tab, click OK.

SYB0007: A Sybase Cumulative Incremental Backup Goes to a Job Pending State

Issue

When you back up multiple Sybase databases and there is a database that does not have the "allow incremental dump" option enabled, the job goes to a pending state.

Resolution

All the databases must have the option enabled.

  1. Use the sp_dboption system procedure to enable this option.

    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.
  2. After you enable the option, perform a full backup.

Completed with one or more errors

Backup jobs from Sybase iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  • If the subclient contains multiple databases, killing a backup job when some of the database backup jobs are not completed.
  • If the subclient contains multiple databases, if some of the databases in the subclient are corrupted or removed.