Symantec NetBackup status code 321 to status code 325

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

NetBackup status code: 321
Message: container cannot hold any media from the specified robot
Explanation: This error occurs while trying to place media from an unexpected
EMM database host into a container. All the media that are placed in a container
should belong to the sameEMMdatabase host. For example, you have media from
a robot that belongs to one EMM database host. Then you try to put this media
into a container that already holds media from the robots that belong to a different
EMM database host.
Recommended Action: Verify that you specified the correct container ID and
media IDs. 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: 322
Message: cannot find vault in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified Vault name
into the Vault configuration file. Note that the Vault configuration file is located
at install_path/netbackup/db/vault/vault.xml.

Recommended Action: Verify that you specified the correct Vault name. 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: 323
Message: cannot find robot in vault configuration file
Explanation: NetBackup Vault cannot find an entry for the specified robot number
in the Vault configuration file. Note that the Vault configuration file is located at
install_path/netbackup/db/vault/vault.xml.
RecommendedAction: Verify that you specified the correct robot number. 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: 324
Message: invalid data found in retention map file for duplication
Explanation: This error occurs when the retention mapping file (either generic
or for a specific vault) contains invalid data. If the file contains too much or too
little data or the user defines invalid retention levels in the file, this error occurs.
The retention mapping file is used as follows: in a Vault session when a Vault
profile duplication is configured with the Use mappings retention level configured
for one of the copies for duplication. The product installs a mapping file template
named retention_mappings in install_path/netbackup/db/vault.
To specify a mappings file for any single vault, copy the retention_mappings
template to another file and append the name of the vault. For example,
netbackup/db/vault/retention_mappings.V1
Recommended Action: Check the entries in the retention_mappings file.

NetBackup status code: 325
Message: unable to find policy/schedule for image using retention mapping
Explanation: This error occurs with duplication of the backup policy or the
schedule of an image by Vault. The Use mappings option on the Duplication tab
of the Profile dialog box is selected, but the policy or the schedule no longer exists.
Recommended Action: Verify whether or not the backup policy or the schedule
that created the image still exists. If either one or both do not exist, the image is
not duplicated through the Vault profile.

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 *