Symantec NetBackup status code 326 to status code 330

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

NetBackup status code: 326
Message: specified file contains no valid entry
Explanation: The specified file contains no valid entries for media IDs or the
alphanumeric equivalent of bar codes. As per the expected format, each line should
contain only one string that represents either a media ID or the bar code numeric
equivalent.
RecommendedAction: Verify that each entry in the specified file does not exceed
the string size limit: six characters for media IDs and 16 characters for the numeric
equivalent of bar codes. Correct the invalid entries in the specified file and try
the same operation again. Read the relevant log file under the directory
install_path/netbackup/logs/vault for more details. Be aware that if this
directory does not already exist, a log file is not created.

NetBackup status code: 327
Message: no media ejected for the specified vault session
Explanation: This error occurs while moving media ejected by the specified Vault
session to a container. Either the specified Vault session has not ejected any media,
or you specified an incorrect Vault name or session ID.
Recommended Action: Verify that you have specified the correct combination
of Vault name and session ID. Verify that the specified Vault session has ejected
at least one piece of media. Read the relevant log file under the directory
netbackup/logs/vault for more details. Be aware that if this directory does not
already exist, a log file is not created.

NetBackup status code: 328
Message: invalid container id
Explanation: This error occurs while adding a container record to the container
database. The container ID is found invalid. Note that the container database
exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the container ID does not contain any space
characters, and that the string size is a maximum of 29 characters long.

NetBackup status code: 329
Message: invalid recall status
Explanation: This error occurs while adding a container record to the container
database. The container recall status is found invalid. Note that the container
database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
Recommended Action: Verify that the recall status is either 1 or 0.

NetBackup status code: 330
Message: invalid database host
Explanation: This error occurs while adding a container record to the container
database. The EMM database host name is found invalid. Note that the container
database exists in file cntrDB, which is located at
install_path/netbackup/vault/sessions/cntrDB.
RecommendedAction: Verify that theEMMdatabase host name does not contain
any space characters, and that the string size is a maximum of 256 characters
long.

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 *