Symantec NetBackup status code 671 to status code 802

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 671 to Status Code 802 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 671
Message: query for list of component images failed
Explanation: A new synthetic image cannot be formed because of a problem with
the required component images. For example: a new, synthetic full backup is tried
from the previous full image from Sunday and from the five differential
incremental images from Monday through Friday. This error occurs if any of those
images (except the most recent image on Friday) has expired.
Recommended Action: Run a non-synthetic backup (either a new full or new
cumulative), depending on the type of backup that failed.

NetBackup status code: 800
Message: resource request failed
Explanation: The nbjm process was unable to get the required resources for a job.
An EMM reason string that appears in the Activity Monitor job details display
and in the nbjm debug log accompanies this status code. The EMM reason string
identifies the reason for the failed resource request.
Recommended Action: Locate the EMM reason string, correct the problem, and
rerun the job.
Some generic EMM reason strings (such as Disk volume is down) may require
generating some reports to determine the cause of the failure. Generate the report
by using either bperror or various log entry reports, such as Reports > Disk
Reports > Disk Logs in the NetBackup Administration Console.

NetBackup status code: 801
Message: JM internal error
Explanation: The nbjm process encountered an internal error.
RecommendedAction: If the problem persists, submit a report with the following
items.
¦ Unified logging files on the NetBackup server for nbpem (originator ID 116),
nbjm (117), nbrb (118), and PBX (103). All unified logging is written to
/usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs
(Windows).
¦ Legacy logs:
¦ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,
and nbproxy
¦ On the media server for bpcd, bpbrm, and bptm or bpdm
¦ On the client for bpcd and bpbkar
Legacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX
and Linux) or install_path\Netbackup\logs\ (Windows). If the directories
do not exist, create directories for each of these processes and rerun the job.
¦ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) or
install_path\NetBackup\db\jobs\trylogs (Windows).
¦ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs.

NetBackup status code: 802
Message: JM internal protocol error
Explanation: nbjm returns this error whenever a protocol error occurs with an
external process that tries to communicate with nbjm. External processes include
bptm, tpreq, bplabel, dqts, vmphyinv, or nbpem.
Recommended Action:
Ensure that the NetBackup software on the master and the media server is from
an official NetBackup release.
If the problem persists, submit a report with the following items.
by using either bperror or various log entry reports, such as Reports > Disk
Reports > Disk Logs in the NetBackup Administration Console.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *