Symantec NetBackup status code 611 to status code 615

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

NetBackup status code: 611Message: no connection to readerExplanation: A connection to the bptm or the bpdm reader process does not exist
to communicate with the reader.Recommended Action: This error should not occur. Submit a problem report
along with 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: 612Message: cannot send extents to bpsynthExplanation: This error code is no longer used.Recommended Action: Submit a problem report along with 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: 613Message: cannot connect to read media serverExplanation: The bpsynth process was unable to connect to the media server to
read a backup image.Recommended Action: Ensure that network connectivity exists between the
master server and the specified media server. Examine the NetBackup error log
for any error messages that bpsynth logged. For more information, refer to the
debug logs for bpsynth on the master server and bpcd and bptm or bpdm on the
media server.
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: 614Message: cannot start reader on the media serverExplanation: The bpsynth process was unable to start the bptm or the bpdm process
to read a backup image to be synthesized.Recommended Action: Do the following, as appropriate:
¦ Examine the NetBackup error log for any errors that bpsynth logged. For more
information, refer to the following debug logs: for bpsynth on the master server
and for bpcd and bptm or bpdm on the media server. Ensure that the bptm or
the bpdm binaries on the media server are executable and are not corrupt. Try
running bptm or bpdm commands locally on the media server to ensure that
the binary is executable and not corrupt. For instance, you can run the following
command
/bp/bin/bptm -count -rn 0 -rt 8
where robot number is 0 and the robot type is 8. The robot type that
corresponds to the robot number can be taken from the command line that is
logged in the debug log for bptm. This command displays the counts for the
up, shared, and assigned drives in the robot.
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: 615Message: internal error 615Explanation: This error code is no longer used.Recommended Action: Submit a problem report along with 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.

With codeplex shutting down, we have moved SQL Nexus to github with a new release (6.0). Now both Pssdiag/SQLDiag manager and SQL Nexus are on github. Where to get it As you navigate to SQL Nexus, you can download code and released binary files. If you choose to download binary files, you can go to...

SQL Server : large RAM and DB Checkpointing Hi everyone, This post’s purpose is to establish a summary of the specific behaviors with relation to DB Checkpoint that may happen within SQL Server when running with a large quantity of allocated memory and when applicable, how to best address them. SQL Server 2016 improves...

Recently we got an inquiry from a customer who received the following message in errorlog and wanted to know why. [INFO] HkDatabaseTryAcquireUserMemory(): Database ID: [7]. Out of user memory quota: requested = 131200; available = 74641; quota = 34359738368; operation = 1. This is my first time to see this error. As usual, I relied...

Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases...

In a previous blog, I talked about memory optimized table consumes memory until end of the batch. In this blog, I want to make you aware of cardinality estimate of memory optimized table as we have had customers who called in for clarifications. By default memory optimized table variable behaves the same way as...

I worked on an interesting issue today where a user couldn’t restore a backup. Here is what this customer did: backed up a database from an on-premises server (2008 R2) copied the file to an Azure VM tried to restore the backup on the Azure VM (2008 R2 with exact same build#) But he got...

Recently, I looked an In-Memory OLTP issue with Principal Software Engineer Bob Dorr who is still my office neighbor. After restoring a database that had just one memory optimized table, we dropped the table. Even without any memory optimized tables,number of checkpoint files keep going up every time we issue a checkpoint. For a while,...

In this blog Added per-operator level performance stats for Query Processing, Senior PM in QP talks about extending operator level performance stats. They include stats related to reads, CPU and elapse time. These are very helpful to track down query performance issues. We worked on recent case where we put ActualElapsedms in a good...

In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count. I was actually investigating an out of memory issues with the following error. Msg 701, Level 17, State 103, Line 11There is insufficient system memory in resource pool...

I was working with a customer to troubleshoot memory optimized table issues. In this scenario, our customer uses a memory optimized table variable. He put 1 million rows of data into the table variable and then process it. Based on what he said, I tried to come up with a repro to see if...