Symantec NetBackup status code 65 to status code 70

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

NetBackup status code: 65
Message: client timed out waiting for the continue message from the media
manager
Explanation: The tape manager, bptm, reported that the media did not load and
position within the allotted time.
Recommended Action: Verify that the requested volume is available and the
required device is in an UP state.
Create a bptm debug log directory on the server.
On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf
file. On a Windows NetBackup server, set the Verbose logging level option on
the Logging tab in the Master Server Properties dialog box.
See “Using the Host Properties window to access configuration settings” in
the Troubleshooting Guide.
Retry the operation and check the bptm debug log file for information on the
drive, robot, and tape that causes the timeout.
On a Windows NetBackup server (master or media): check the Event Viewer
Application log for the error messages that indicate why the tape mount did
not complete.

NetBackup status code: 66
Message: client backup failed to receive the CONTINUE BACKUP message
Explanation: The client bpbkar process did not receive the message from the
server that indicates that the server is ready to continue.

NetBackup status code: 67
Message: client backup failed to read the file list
Explanation: The client did not read the list of files to back up.
Recommended Action: Do the following, as appropriate:
Verify that the server did not crash.
Set up debug logging.
On the server, create a bpbrm debug log directory.
On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.
On other PC clients except Macintosh, create a debug log directory for bpcd
(the bpcd log is created automatically on Macintosh).
Increase the amount of information that appears in the logs.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
Retry the operation and check the resulting debug logs.

NetBackup status code: 68
Message: client timed out waiting for the file list
Explanation: The client did not receive the list of files to back up within the
allotted time. This list comes from the server.
Recommended Action: Do the following, as appropriate:
Verify that the server did not crash.
Set up debug logging.
On the server, create a bpbrm debug log directory.
On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.
On other PC clients except Macintosh, create a debug log directory for bpcd
(the bpcd log is created automatically on Macintosh).
Increase the amount of information that appears in the logs.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
Retry the operation and check the resulting debug logs.

NetBackup status code: 69
Message: invalid filelist specification
Explanation: The file list from the server had invalid entries.
For the Enterprise Vault Agent: A policy contains some directives that cannot be
specified together in the same policy.
Recommended Action: Do the following, as appropriate:
Check the policy file list. If wildcards are used, verify that the bracket characters
([ and ]) in the list match. If the file list contains UNC (Universal Naming
Convention) names, ensure that they are properly formatted.
This error can occur if nbjm was running and a Sharepoint job re-discovery returns
a 0 or 1 and the policy file list is empty. Examine the nbjm unified log (originator
ID 117) for more detail on the cause of the error.
For NetBackup Snapshot Client only:
In an off-host backup (NetBackup Media Server or Third-Party Copy Device),
code 69 may indicate that the file list contains the ALL_LOCAL_DRIVES entry.
NetBackup does not support the ALL_LOCAL_DRIVES entry for off-host backup.
Remove the ALL_LOCAL_DRIVES entry from the file list.
For the Enterprise Vault Agent only:
See the Troubleshooting section of the NetBackup for Enterprise Vault Agent
Administrator’s Guide.

NetBackup status code: 70
Message: an entry in the filelist expanded to too many characters
Explanation: The wildcards, which were used in one of the file list entries,
specified too many files.
RecommendedAction: Change the wildcards in the file list to specify fewer files.

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 *