Symantec NetBackup status code 181 to status code 185

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

NetBackup status code: 181
Message: tar received an invalid argument
Explanation: One of the parameters that was passed to tar was not valid.
Recommended Action: Do the following, as appropriate:
¦ On a UNIX or Linux client:
¦ Ensure that the tar command in /usr/openv/netbackup/bin is the one
provided by NetBackup. If you are in doubt, reinstall it.
¦ Check /usr/openv/netbackup/bin/version on the client to verify that
the client is running the correct level software. If the software is not at the
correct level, update the software per the directions in the NetBackup
release notes.
¦ On a Windows client, create a tar debug log directory, retry the operation,
and check the log.
¦ On a Macintosh client, check the version file that is in the bin folder in the
NetBackup folder in the Preferences folder. If the software is not at the correct
level, install the correct software.
See the NetBackup Installation Guide for UNIX.

NetBackup status code: 182
Message: tar received an invalid file name
Explanation: tar cannot write to the file that is specified with the -f parameter.
Recommended Action: Do the following, as appropriate:
¦ Create a bpcd debug log directory on the client (on a Macintosh, NetBackup
creates the log automatically).
¦ On a Windows client, create a tar debug log directory.
¦ Increase the logging level on the client:
¦ On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
¦ On PC clients, increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
¦ Rerun the operation, check the resulting debug logs for the parameters that
were passed to tar and call customer support.

NetBackup status code: 183
Message: tar received an invalid archive
Explanation: The data that was passed to tar was corrupt.
Recommended Action: Do the following, as appropriate:
¦ If the problem is with a UNIX or Linux client, create a
/usr/openv/netbackup/logs/tar debug log directory on the client and rerun
the operation.
¦ Check the tar debug log file for any error messages that explain the
problem.
¦ Restart the client to see if it clears the problem.
¦ When you finish with your investigation of the problem, delete the
/usr/openv/netbackup/logs/tar directory on the client.
¦ If the problem is with a Microsoft Windows, NetWare, or Macintosh client, do
the following in the order presented:
¦ Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
¦ On a Windows client, create a tar debug log directory.
¦ Increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
¦ Rerun the operation and check the resulting debug logs.
¦ Restart the client to see if it clears the problem.

NetBackup status code: 184
Message: tar had an unexpected error
Explanation: A system error that occurred in tar.
Recommended Action: Do the following, as appropriate:
¦ If the problem is with a UNIX or Linux client, create a
/usr/openv/netbackup/logs/tar debug log directory on the client and rerun
the operation.
¦ Check the tar debug log file for any error messages that explain the
problem.
¦ Restart the client to see if it clears the problem.
¦ When you finish your investigation of the problem, delete the
/usr/openv/netbackup/logs/tar directory on the client.
¦ If the problem is with a Microsoft Windows, NetWare, or Macintosh client:
¦ Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
¦ Increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
¦ On a Windows client, create a tar debug log directory.
¦ Retry the operation and check the resulting debug logs.
¦ Restart the client to see if it clears the problem.

NetBackup status code: 185
Message: tar did not find all the files to be restored
Explanation: The tar file list contained files that were not in the image.
Recommended Action: Do the following, as appropriate:
¦ If the problem is with a UNIX or Linux client:
¦ Enable bpcd debug logging by creating the
/usr/openv/netbackup/logs/bpcd directory on the client.
¦ Rerun the operation, check the resulting bpcd log file for the parameters
that were passed to tar, and call customer support.
¦ If the problem is with a Microsoft Windows, NetWare, or Macintosh client:
¦ Create a bpcd debug log directory on the client (on a Macintosh NetBackup
creates the log automatically).
¦ Increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
¦ On a Windows client, create a tar debug log directory.
¦ Retry the operation.
¦ Check the resulting debug logs for the parameters that were passed to tar
and call customer support.

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 *