Search <book_title>...

Veritas NetBackup™ Status Codes Reference Guide

Last Published: 2017-07-21

Product(s): NetBackup (8.0)

NetBackup status code: 2803

Message: Sybase policy restore error

Explanation: An error caused the restore of the Sybase data to fail.

Recommended Action: Try the following possible solutions in the order presented:

Ensure that the client server list contains entries for the master server and any media servers that can be used during a backup or restore.
Examine the status or the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.
Check ownership and permission on the Sybase instance that you restore and on the directories where files are restored.
Check the NetBackup sybackup log for additional failure information.

Create the following log folders, then retry the restore:

On the client:

/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/bprestore
/usr/openv/netbackup/logs/tar
/usr/openv/netbackup/logs/sybackup
chmod 777 /usr/openv/netbackup/logs/sybackup
chmod 777 /usr/openv/netbackup/logs/bphdb

On the media server:

/usr/openv/netbackup/logs/bptm
/usr/openv/netbackup/logs/bpbrm

On the master server:

/usr/openv/netbackup/logs/bprd

Correct the problems that you find and retry the restore.

To set the debug level on UNIX and Linux clients, enter the following line in the bp.conf file:

VERBOSE = 5

For a Sybase alternate client restore, the user ID (UID) of the restoring Sybase backup server must match the UID of the Sybase backup server from the source host.

For an alternate client restore, the user/group/other permissions must be able to read the No.Restrictions file, or authorize the alternate client to access images for the original client.

UNIX or Linux master server: /usr/openv/netbackup/db/altnames/No.Restrictions

Windows master server: install_path\NetBackup\db\altnames\No.Restrictions

Verify that the alternate client can browse the backup images for the original client:

UNIX or Linux master server: /usr/openv/netbackup/db/altnames/No.Restrictions

Windows master server: install_path\NetBackup\db\altnames\No.Restrictions

# /usr/openv/netbackup/bin/bplist -C <origClient> -t 7 -l -R /

# install_path\netbackup\bin\bplist -t 7 -l -R /

On the alternate client, use the bpclntcmd command to test connectivity and name resolution. The command should display the name of the master server on the first line. The second line must contain the IP address of the network interface that the alternate client used when communicating with the master server. The first word on the second line is the name of the alternate client as resolved on the master server from the IP address. The second word on the second line may be 'NULL' if the alternate client is not being backed up. Otherwise, it is the name of the alternate client (or an alias) which is defined in a backup policy on the master server.

# /usr/openv/netbackup/bin/bpclntcmd -pn

Make sure that CLIENT_READ_TIMEOUT on the alternate client and media server is set large enough to allow the tapes to be read, the data transferred, and the database instance to write the data to disk.

Information is available about what to do if a Sybase restore fails with Unrecoverable I/O errors.

http://www.veritas.com/docs/TECH92495

Information is available about steps to a Sybase alternative client restore operation.

http://www.veritas.com/docs/TECH24125

Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.