Description
In the pre-rename report of NBServerMigrator update's rename operation, the following list of issues can be observed:
1) Cluster is configured and the cluster name is cluster_name, rename for cluster based server is not supported.
- A Clustered NetBackup primary server is not supported for rename operation.
2) Server name in database is different than primary name.
- Primary server name and the EMM Server name are different.
The first entry in the bp.conf or the SERVER entry in registries is different then the EMM server name in the output of nbemmcmd -listhosts command.
Please contact Veritas technical support
3) Catalog archiving has been done.
- Kindly restore the archived images before the rename operation (using bpcatres).
Please refer to the command reference guide
https://www.veritas.com/support/en_US/doc/15263389-162556708-0/v14659962-162556708
4) Intelligent Catalog Archiving is enabled and images have been archived
- Unarchive the images before proceeding with the rename operation.
5) Catalog archiving not there but images are missing.
- Please refer to https://origin-www.veritas.com/support/en_US/article.100016710. Kindly contact Veritas technical support.
6) Files file compression has been done.
- Decompress catalog before proceeding with the Rename
7) Provided hostname <current_name> not matching with NetBackup hostname <primary_server'shostname>.
- The current_name provided in the nbserver_update command is different then the hostname of the primary server.
Please run /usr/openv/netbackup/bin/bpclntcmd -pn command on the primary server to get the exact hostname with which the NetBackup primary server is configured.
8) No server name found/No primary name found
- No server name found, Please check nbemmcmd -listhosts.
For further troubleshooting, Please contact Veritas technical support.
9) No Active license found.
- Please run bpminlicense -list_keys -verbose command.
Kindly refer to https://www.veritas.com/support/en_US/article.100059061
10) More than one primary server entries present in the database.
- Please contact Veritas technical support.
11) If there is unsupported hostname (existing or new) for NetBackup.
- New_name should be as per the NetBackup hostname standards.
Please refer: https://www.veritas.com/support/en_US/article.100047335
12) If the new name and old name are the same.
- For a rename operation, current_name and the new_name cannot be same
13) Minimum and maximum NetBackup version.
- Minimum supported version: 10.x
Maximum supported version: 10.4.0.1
14) wrong server type.
- Rename is not supported for a media server. Please run rename on a NetBackup primary server.
15) If it NBFS or NBA.
- Rename is not supported for an NBA and Flex Scale
16) If the 4112070 EEB of 10.1.1 is not present.
- Kindly install EEB 4112070 and run the report again.
17) space requirement.
- Please create adequate space mentioned in the log message.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.