The NBServerMigrator utility does not support the following:
1) NetBackup Access Control (NBAC)
NBAC is used to make NetBackup communication secure and to provide a level of role-based access control for individual users. The NBAC database is not migrated using the NBServerMigrator tool.
2) Bare Metal Recovery (BMR)
The BMR database is a relational database that sits alongside the NBDB and contains information used during bare metal recovery operations. It cannot be migrated using the NBServerMigrator tool.
3) OpsCenter
The OpsCenter database usually resides on the primary server and is used for reporting purposes; however, it is not part of the NetBackup Catalog. The NBServerMigrator utility does not support migration.
4) Cloud configurations
The NBServerMigrator utility does not support the migration of the cloud configuration from the source to the target server. Cloud configuration should be done using manual steps.
5) Non-English locales
Currently, the NBServerMigrator utility supports only English locale. If the source or target servers are using any other system locale than English, please change it to English before the migration activity and revert to the original locale once done.
6) Cluster migrations
Currently, clusters as a source or target primary server are not supported for this version.
7) Flex Scale with DR configuration (example: 2x FlexScale clusters )
Migrations for Flex scale with two or more clusters as target is not supported.
8) Resume option for jobs initiated on the source primary server.
The option to resume any suspended, canceled, or incomplete jobs on the target primary server is not available after the migration. Complete all the jobs before starting the migration.
9) Universal shares
Universal share configured on a Flex media server (Flex Appliance configured as a Source Media server) is not supported for server migration. Duplicate the backups to another storage unit before migration.
Note:
a) Catalog archival
It is strongly recommended to restore the archived catalog images prior to performing the same name migration.
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.