Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 2803
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, authorize the alternate client to access images for the original client.
Verify that the alternate client can browse the backup images for the original client:
# /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.
See the following technical article for information about the steps for a Sybase alternative client restore operation:
https://www.veritas.com/support/en_US/article.100016002
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.