Symantec NetBackup status code 636 to status code 640

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

NetBackup status code: 636
Message: read from input socket failed
Explanation: The read from an input socket failed. The underlying connection
has been broken.
RecommendedAction: The bpsynth process encountered an error while reading
from an input socket. The socket may be between bpsynth and bptm or bpdm.
The errno that was logged to the NetBackup error log indicates the reason for the
failure. For more information, refer to the following: the debug log for bpsynth
(on the master server) and for the bptm or the bpdm reader or writer processes (on
the media server). Check the network connectivity between the master and the
media server. Rerun the synthetic backup job. 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: 637
Message: write on output socket failed
Explanation: The write to an output socket failed. The underlying connection
has been broken.
RecommendedAction: The bpsynth process encountered an error while writing
to an output socket. The socket is between bpsynth and bptm or bpdm.
The errno that logged to the NetBackup error log indicates the reason for the
failure. For more information, refer to the following: the debug log for bpsynth
(on the master server) and for the bptm or the bpdm reader or writer process (on
the media server). Check the connectivity between the master and the media
server. Retry the synthetic backup job. 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: 638
Message: invalid arguments specified
Explanation: The bpsynth command fails with this error code if incorrect
arguments were specified.
RecommendedAction: Refer to the bpsynth command line arguments (by using
-help) for the correct argument specification. If the synthetic backup job was
started manually by the command line, correct the arguments to bpsynth and
rerun the job. If the synthetic backup job was scheduled or started with the console,
ensure that the bpsynth and the nbjm binaries match the installed NetBackup
version.

NetBackup status code: 639
Message: specified policy does not exist
Explanation: The policy that was specified on the bpsynth command does not
exist in the database. Either the command line or nbjm initiated the bpsynth
command. If nbjm initiated it, the policy may have been deleted after nbjm started
bpsynth and before bpsynth issued the database query.
Recommended Action: If bpsynth is initiated with the command line, rerun the
command for an existing policy. If the problem persists after you verify the
following, contact customer support and send the appropriate logs:
¦ The synthetic backup job was scheduled or started by using the NetBackup
Administration Console (manual start).
¦ The policy exists in the bppllist command configuration.
¦ Check the logs for nbjm, which uses unified logging (OID 117).
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: 640
Message: specified schedule was not found
Explanation:The schedule on the bpsynth command did not exist in the specified
policy definition in the database due to either of the following:
¦ The command line initiated the bpsynth command
¦ The specified schedule was deleted from the policy after nbjm started bpsynth,
before bpsynth issued the database query.
Recommended Action: If the command line initiated bpsynth, do the following:
rerun the command with the correct synthetic schedule label defined in the policy
of the synthetic backup job to be run. If the synthetic backup job was scheduled
or started with the NetBackup Administration Console, define a new schedule
in the policy and retry the job. 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.

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 *