Restore Troubleshooting - Sybase Data Agent

The following section provides information on troubleshooting restores.

Browse Failures

Point in time Table Browse Failures When you have encryption enabled for the client, point in time table browse operation fails with the following error message:

Pass-phrase protection is on for client [80], but pass-phrase was not specified.

Make sure that the pass phrase is exported to the MediaAgent when encryption is enabled for the client.

  1. From the CommCell Browser, right-click the <Client> and then click Properties.
  2. Click the Encryption tab.
  3. Click Via Pass-Phrase.
  4. Click Export.
  5. In the Destination Computer box, select the MediaAgent.
  6. In the Pass-Phrase box, type the pass-phrase used for encryption.
  7. In the Re-enter Pass-Phrase box, re-type the pass-phrase to confirm.
  8. Click Export.
  9. Click OK.

Restore Failures

Failure of Backups and Restores performed from a remote desktop on windows Currently, backups and restores cannot be performed from a remote desktop on Windows.

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
Full Server Restore is failing on a Windows setup Issue:

This issue may occur when you use Sybase 15.0 ESD #7 on Windows.

Restoring an entire Sybase server may fail after changing the master database devise size with the following error message:

3952 7a8 04/24 10:28:56 1500012 CvSybDB::AlterDatabase() - ExecuteJob(alter database tempdb on master="6M" , tempdbdev="6M") failed
3952 7a8 04/24 10:28:56 1500012 CvSybDBRecovery::AdjustDatabaseUsage() - AlterDatabase failed
3952 7a8 04/24 10:28:56 1500012 JM Client CVJobClient::setPendingCause(). same messageid is being sent for the same job id within a short time period. so dropping the JPR
3952 7a8 04/24 10:28:5Email6 1500012 CvSybDBRecovery::setPendingCause() - Failed to set the pending cause. please check the logs
3952 7a8 04/24 10:28:56 1500012 CvSybSybRecovery::PostLoadDatabase() - AdjustDatabaseUsage failed
3952 7a8 04/24 10:28:56 1500012 ClSybRestore::Restore() - PostLoadDatabase failed
3952 7a8 04/24 10:28:56 1500012 ClSybRestore::Restore() - Completed count: 1
3952 7a8 04/24 10:28:56 1500012 ClAgentSybJobUnit::NotifyCommServe() - Entering..
3952 7a8 04/24 10:28:56 1500012 Sending FAILED complete message to JM, 1500012

This issue may occur on a Windows setup if you change the database devise size and then take a backup of all the databases except the master database.

Resolution/Workaround:

Whenever you change the devise size on a Windows setup with Sybase 15.0 ESD #7, perform a backup of master database along with all the other databases.

Restoring multiple databases in one job may fail Sometimes, restoring multiple databases in one job may fail if different streams are used for data and log backups. If you need to restore multiple databases in one job, use the same streams for data and log backups.
Cross Server Restores Fail Cross server restore will fail if the max page size in destination server is different from that of the source server.

When restoring Sybase databases to a different server, the max page size of source server should be the same as the destination server.

When you browse for the destination server, you will do it based on Max page size. By default, it is 2048 (2k).

You can query in sybase server to get the max page size of the server:

Example:

1> select @@maxpagesize 2> go ----------- 4096 (1 row affected)

Recovering data associated with deleted clients and storage policies

Symptom

In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:

  • Deleted storage policy
  • Deleted client, agent, backup set or instance

Before You Begin

This procedure can be performed when the following are available:

  • You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.
  • Media containing the data you wish to recover is available and not overwritten.
  • If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
    • IP Address Change license
    • CommCell Migration license

    See License Administration for more details.

  • A standby computer, which is used temporarily to build a CommServe.
Recovering Deleted Data
  1. Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.
    • Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
    • If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
    • If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:
      • If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.
      • If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.
  2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.
  3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool for step-by-step instructions.)
  4. Verify and ensure that the NetApp Client Event Manager NetApp Communications Service (EvMgrS) is running.
  5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
  6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

    When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.

  7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

    This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

  8. You can now browse and restore the data from the appropriate entity.

    As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.

Restore Fails because of a Stream Error

The number of streams the restore uses is the same number that is  configured on the subclient for data backup or transaction log backups. When the number of streams are not available, you will get the following JPR error.

JPR: Error Code: [62:455] Description: Drive in which Media is mounted is not ready to use. Source: leonard64, Process: MediaManager

JM log:
1]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].
12528 2df0 10/21 16:22:05 143280 Scheduler Ignored pending cause
[The operation could not be completed as there are not enough drives that are unreserved and online with an active controller.]::Client [leonard64] Application [MediaManager] Message Id
 [1040187471] RCID [0] Reservation Id [-1]. Level [0] flags [0] id [0]
overwrite [0] append [0] CustId[0].

Example

The subclient is configured for 4 primary backup data streams. You run a secondary copy to the table library and there are only 2 streams available. The restore fails.

SYB0006: Performing a Sybase Server Restore When You Have Deleted Databases

Symptom

Use this procedure when you want to perform a Sybase Server Restore on a backup that contains deleted databases.

This scenario can happen when you perform a backup and then delete the databases on the Sybase server. The SnapProtect backup contains databases that no longer exist on the Sybase server.

You can exclude the databases from the restore.

Resolution

  1. From the CommCell Browser, expand Client Computers > client > Sybase.
  2. Right-click the instance, point to All Tasks and then click Browse and Restore.

    The Browse and Restore Options dialog box is displayed.

  3. On the Time Range tab, click View Content.
  4. On the client screen:
    1. In the right pane, select the server that you want to restore..
    2. In the left pane, clear all entries for databases that you deleted after the backup completed.
    3. Click Recover All Selected.

      The Restore Options dialog box is displayed.

  5. On the General tab, select the Sybase Create Devices check box.
  6. Click OK to start the restore.

SYB0007: Restore failed because of corrupt database

Symptom

If the Sybase master database is corrupt, you see the following Job Pending Reason (JPR):

Error Code: [71:40] Description: Connection to Sybase DataServer failed, Please make sure that Sybase SA user's password is empty before restoring master database or choose create device option in GUI. Source: sybserver5_3, Process: ClSybAgent

The software sends the following message.

13009 32d1 09/10 19:08:17 136542 CvSybSysRecovery::StartServerInRecoveryMode() - 00:00:00000:00000:2015/09/10 19:08:17.25 kernel The configuration area in device '/sybase/syb155/data/master.dat' appears to be corrupt. The server cannot continue and will shut down.

Resolution

  • Manually restore the Sybase master database.

SYB0008: Restore failed because the configuration file is not configured in the CommCell Console

Symptom

If the Sybase configuration file is not set in the CommCell Console Instance Properties for the database, you see the following Job Pending Reason (JPR):

Error Code: [71:40] Description: Connection to Sybase DataServer failed, Please make sure that Sybase SA user's password is empty before restoring master database or choose create device option in GUI. Source: sybserver5_3, Process: ClSybAgent

The following message is in the client log.

Configuration Error: Configuration file, '/usr/sybaset/sybase150/ASE-15_0', does not exist.

Resolution

  • Verify the Sybase configuration file location and name and set that value in the Instance Properties dialog box, Configuration File box.

SYB0010: A Restore of the Sybase syssecurity database fails

Symptom

If you restore a Sybase syssecurity database and the SA user does not have the Sybase system security officer role, you receive the following error

19355 f7f9e720 11/04 17:36:22 3741916 CvSybDB::SetEnableAuditing() - ExecuteJob(exec sp_configure "auditing",0) failed
19355 f7f9e720 11/04 17:36:22 3741916 CvSybGenRecovery::PreLoadDatabase() - exec sp_configure "auditing", 0 failed with an error [You must have any of the following role(s) to execute this command/procedure: 'sso_role' . Please contact a user with the appropriate role for help.]

Resolution

  • Configure the SA user to have  the system security officer role.

SYB0011: A Restore of an on-demand backup fails

Symptom

If you restore an on-demand backup and you have set the  set 'enable concurrent dump tran' to 1, you may receive the following error

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.

Resolution

  • set 'enable concurrent dump tran' to 0

SYB0012: The Sybase tempdb database does not start after a restore and displays error 806

Symptom

After a successful Sybase server restore, the tempdb database does not start and an error message similar to the following is displayed.

7143678 1 06/04 13:57:15 284437 CvSybSysRecovery::StartServerInRecoveryMode() - 00:00000:00001:2016/06/04 13:57:15.37 server Could not find virtual page for logical page 2048 in database 'tempdb'.

Resolution

For more information on the error, go to the SAP website, Error 806.

  1. Restart the Sybase Adaptive Server when the error message indicates the tempdb, because Sybase rebuilds the tempdb database during a restart.
  2. If the restart does not work, contact your software provider.

SYB0013: A master database restore marks the tempdb suspect if the segments of the tempdb are extended on the master

Symptom

If the system tempdb is extended on the master device apart from the default allocation, a master database restore marks the tempdb suspect.

Example

The tempdb is allocated on the master database as follows

alter database tempdb on master = "10M"
go
alter database tempdb on master = "2M"
go
alter database tempdb on mytempdev = "10M"
go:

The following error message is displayed.

3256 ed051820 06/16 05:36:37 516499 CvSybSysRecovery::StartServerInRecoveryMode() - 00:0006:00000:00001:2016/06/16 05:36:37.64 server Database 'tempdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause

Resolution

For more information on the error, go to the SAP website, Error 806.

  1. Shut down the database and start it in recovery mode
  2. See the SAP recommended KB article https://launchpad.support.sap.com/#notes/2195104 or run the following queries.

This query returns a value that indicates that the tempdb is marked suspect

select status from master..sysdatabases where dbid = 2
go

After this query, only the first row is affected.

use master go begin transaction go update sysdatabases set status = status ^ 256 where status & 256 = 256 and name="tempdb"
go

Check the status of the tempdb. The value is 77 or another value.

select status from master..sysdatabases where dbid = 2
go
commit transaction
go