NBServerMigrator: Hostname with which the Target Primary server should be configured

Description

NBServerMigrator supports same-name migrations. For this, the hostname of the source primary server and the target primary server should be identical.
In the pre-migration report, due to hostname mismatch, the following issues are reported:
a) hostname of source and target are different.
This occurs when the hostname of source primary server and target primary server are not identical.

b) 'server' (xxxxxx) entry does not match 'master' name (xxxxxxx.domain) in EMM
This can occur for source and/or target primary servers.

To define the hostname with which the target primary server is to be configured, please run the following commands on the source primary server:
1) Linux/Unix: /usr/openv/netbackup/bin/admincmd/nbemmcmd -listhosts
    Windows: <install_path>\veritas\netbackup\bin\admincmd\nbemmcmd -listhosts
Example:
[root@host-name]# /usr/openv/netbackup/bin/admincmd/nbemmcmd -listhosts
NBEMMCMD, Version: 10.2
The following hosts were found:
ndmp              host-name.domain.com
server            host-name.domain.com
primary           host-name.domain.com
Command completed successfully.

Please note down the "primary" entry from the output (For NetBackup versions < 10.2, please note down the "master" entry).

2) Linux/Unix: /usr/openv/netbackup/bin/admincmd/bpgetconfig -h SERVER
    Windows: <install_path>\veritas\netbackup\bin\admincmd\bpgetconfig -h SERVER
Example:
[root@host-name]# /usr/openv/netbackup/bin/admincmd/bpgetconfig -h SERVER
SERVER = host-name.domain.com
[root@host-name]#

The primary entry and the SERVER entry from the above-mentioned commands should match.
Using the hostname obtained from above, the target primary server should be configured.


The issue mentioned in point b) in the pre-migration report is due to a mismatch between the Primary and the SERVER entry in the above-mentioned commands in the respective server.

Please contact Technical support for the resolution.