Symantec NetBackup status code 606 to status code 610

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 606 to Status Code 610 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 606
Message: no robot on which the media can be read
Explanation: bpsynth returns this error when it cannot find a robot on which to
read a particular media ID that contains backup images to be synthesized. The
media ID is included in the message that bpsynth logs. This error should not occur.
Recommended Action: Contact customer support and provide appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 607
Message: no images were found to synthesize
Explanation: The database query to obtain the images to synthesize for the given
policy did not return any images.
Recommended Action: Ensure that a synthetic full backup has one full image
(real or synthetic) and one or more subsequent incremental images (differential
or cumulative) to synthesize. For a cumulative synthetic backup, there must be
two or more incremental (differential or cumulative) images to synthesize. Adjust
your schedules so the appropriate backup jobs complete successfully before the
synthetic job is run. The scheduler does not retry a synthetic backup job that fails
with this error code.

NetBackup status code: 608
Message: storage unit query failed
Explanation: The database query to obtain all storage units failed.
Recommended Action: Verify that the bpdbm process is running and that no
errors were logged to the NetBackup error log. Restart the bpdbm process (on UNIX
and Linux), or the NetBackup Database Manager Service (on Windows) and retry
the synthetic backup job. If the problem persists, contact customer support and
send the appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 609
Message: reader failed
Explanation: The bptm or the bpdm reader process was terminated with an error.
Recommended Action: Refer to the NetBackup error log for the errors that the
bpsynth and bptm or bpdm reader logged. The error message should contain the
actual error that the bptm or the bpdm reader reports. Refer to the NetBackup
Troubleshooting Guide for information on the error that the bptm or the bpdm
reader reports. The media may not be present or is defective or the drive that was
used for reading the media is defective. If the problem persists, contact customer
support and send appropriate logs.
A complete list of required logs and configuration information is available.
See “Logs to accompany problem reports for synthetic backups” in the
Troubleshooting Guide.

NetBackup status code: 610
Message: end point terminated with an error
Explanation: An error indication was received on the connection to the bptm or
the bpdm process.
Recommended Action: Review the errors in the NetBackup error log that the
following processes logged: bpsynth and bptm or bpdm. Refer to the debug logs for
these processes for more information. The connection may have broken due to
the following: an error condition that the bptm or the bpdm process detects or
network problems between the master and the media server. Check the network
connectivity between the master and the media server. Retry the job and if the
problem persists, contact customer support and send the appropriate logs.
A complete list of required logs and configuration information is available.

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 *