Re: create second MSDP on other media
Hi,
I took the activity of guilhemflo on NBU in our company and the problem is still here. This is the original post https://vox.veritas.com/t5/NetBackup/create-second-MSDP-on-other-media/m-p/869768#M240818
To resume, we want to create a second msdp on new media server in addition to our first msdp on the first media server
I checked a lot of topic without success.
I added a new licence VERITAS NETBACKUP 8.1 PLATFORM BASE COMPLETE EDITION LICENSE on the new server but nothing changes.
I start bptestbpcd -client new_media_server -debug -verbose
18:03:14.723 [10512.10040] <2> bptestbpcd: VERBOSE = 0
18:03:14.723 [10512.10040] <2> check_vnetd_process_dup_permission: OpenProcessToken() failed: 5
18:03:14.723 [10512.10040] <2> vnet_check_windows_privileges: enabled SeDebugPrivilege privilege
18:03:14.755 [10512.10040] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
18:03:14.833 [10512.10040] <2> logconnections: PROXY CONNECT FROM X.X.X.X.61131 TO X.X.X.X.1556 fd = 760
18:03:14.833 [10512.10040] <2> logconnections: BPCD CONNECT FROM 127.0.0.1.61133 TO 127.0.0.1.61134 fd = 760
18:03:14.833 [10512.10040] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0000000003F15B30
18:03:14.833 [10512.10040] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
18:03:14.927 [10512.10040] <8> do_pbx_service: [vnet_connect.c:2579] via PBX VNETD CONNECT FROM X.X.X.X.61135 TO X.X.X.X.1556 fd = 768
18:03:14.927 [10512.10040] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
18:03:14.927 [10512.10040] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:483] ipc_string 52793
18:03:15.161 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
1 1 1
127.0.0.1:61133 -> 127.0.0.1:61134 PROXY X.X.X.X:61131 -> X.X.X.X:1556
127.0.0.1:61137 -> 127.0.0.1:61138 PROXY X.X.X.X:61135 -> X.X.X.X9:1556
18:03:15.177 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
18:03:15.208 [10512.10040] <2> bpcr_get_peername_rqst: Server peername length = 23
18:03:15.223 [10512.10040] <2> bpcr_get_hostname_rqst: Server hostname length = 7
18:03:15.255 [10512.10040] <2> bpcr_get_clientname_rqst: Server clientname length = 19
18:03:15.270 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
18:03:15.286 [10512.10040] <2> bpcr_get_platform_rqst: Server platform length = 7
18:03:15.302 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
18:03:15.364 [10512.10040] <2> bpcr_patch_version_rqst: theRest == > <
18:03:15.364 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
18:03:15.411 [10512.10040] <2> bpcr_patch_version_rqst: theRest == > <
18:03:15.411 [10512.10040] <2> bpcr_get_version_rqst: bpcd version: 08100000
LOCAL_CERT_ISSUER_NAME = /CN=broker/OU=root@master.intra.cea.fr/O=vx
LOCAL_CERT_SUBJECT_COMMON_NAME = d2509c73-7b3a-4e43-98af-ab9a9c365607
PEER_CERT_ISSUER_NAME = /CN=broker/OU=root@master.intra.cea.fr/O=vx
PEER_CERT_SUBJECT_COMMON_NAME = d1bd35b4-db15-45bf-8a70-2f812f4c317e
PEER_NAME = master.intra.cea.fr
HOST_NAME = NEW_MEDIA
CLIENT_NAME = MEDIA_01.intra.cea.fr
VERSION = 0x08100000
PLATFORM = win_x64
PATCH_VERSION = 8.1.0.0
SERVER_PATCH_VERSION = 8.1.0.0
MASTER_SERVER = master
EMM_SERVER = master
NB_MACHINE_TYPE = MEDIA_SERVER
SERVICE_TYPE = VNET_DOMAIN_CLIENT_TYPE
PROCESS_HINT = d1bd35b4-db15-45bf-8a70-2f812f4c317e
18:03:15.552 [10512.10040] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0000000003F06820
18:03:15.567 [10512.10040] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
18:03:15.645 [10512.10040] <8> do_pbx_service: [vnet_connect.c:2579] via PBX VNETD CONNECT FROM X.X.X.X.61139 TO X.X.X.X.1556 fd = 724
18:03:15.645 [10512.10040] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
18:03:15.645 [10512.10040] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:483] ipc_string 52798
127.0.0.1:61141 -> 127.0.0.1:61142 PROXY X.X.X.X:61139 -> X.X.X.X:1556
<2>bptestbpcd: EXIT status = 0
Do you see something that's wrong with the log ? If you want more precisions, i'll try to answer you.
It seems that the new media server setup was done differently.
Please have a look at the differences - firstly the license that you added to new media server is different:
MachineName = "MEDIA01.domain.fr"
FQName = "MEDIA01.domain.fr"
MachineFlags = 0x17
MachineNbuType = media (1)
MachineState = active for tape and disk jobs (14)
MasterServerName = "MASTER01.domain.fr"MachineName = "NEW_MEDIA_SERVER"
FQName = "NEW_MEDIA_SERVER.domain.fr"
MachineFlags = 0x10
MachineNbuType = media (1)
MachineState = active for disk jobs (12)
MasterServerName = "MASTER01.domain.fr"PLATFORM BASE COMPLETE EDITION LICENSE should've enabled all options - disk and tape, not only disk ( 'active for disk' normally means Basic Disk).
Then it seems that you have added the master server name as FQDN (MASTER01.domain.fr) on NEW_MEDIA_SERVER, but entered EMM server name as shortname (MASTER01):
MasterServerName = "MASTER01.domain.fr"
Server Type Host Version Host Name EMM Server
MASTER 8.1 MASTER01.domain.fr MASTER01.domain.fr
MEDIA 8.1 NEW_MEDIA_SERVER MASTER01
MEDIA 8.1 MEDIA01.domain.fr MASTER01.domain.frExtremely important to be consistent with naming convension and to double-check and confirm license key on the media server.
Lastly - carefully check all the steps that you have followed....
You will need to remove all remnants of failed config on new media server before you try again.
When you try again, please take screenshots of each step.