I have a problem with our MediaServer, that shows Offline(instead of Active for Disk).
We have two media servers, one with master server and the other one(MediaServer2) was added later.
Everything was good while the Master and new MediaServer were in same subnet and location. At some point we moved the additional server to other site(server IP changed, VPN tunnel)
After that new MediaServer(MediaServer2) is in Offline state.
I can ping IP-s both ways. Also server names are added to host file, so names resolve fine.
From master, i have tried:
./bptestbpcd -client MediaServer2
1 1 1
127.0.0.1:41091 -> 127.0.0.1:56196 PROXY MasterServerIP:50117 -> MediaServer2IP:1556
127.0.0.1:41091 -> 127.0.0.1:56200 PROXY MasterServerIP:36539 -> MediaServer2IP:1556
127.0.0.1:41091 -> 127.0.0.1:56208 PROXY MasterServerIP:60061 -> MediaServer2IP:1556
same result from media server
./nbemmcmd -listhosts -verbose
ClusterName = ""
MachineName = "MediaServer2"
FQName = "MediaServer2"
LocalDriveSeed = ""
MachineDescription = ""
MachineFlags = 0x77
MachineNbuType = media (1)
MachineState = not reachable by master (4)
MasterServerName = "MasterServerName"
NetBackupVersion = 22.214.171.124 (820000)
OperatingSystem = linux (16)
ScanAbility = 5
./nbemmcmd -updatehost -machinename <media_server_name> -machinestateop set_disk_active -machinetype media -masterserver <master_server_name>
./nbemmcmd -updatehost -machinename <mediaserver hostname> -machinetype media -machinestateop set_master_server_connectivity -masterserver <masterserver hostname>
After the second command i see that Media server is Active_for_disk, but after some minutes goes OFFLINE again.
./vmoprcmd -hoststatus -h MediaServer2
CURRENT HOST STATUS
Host MediaServer2 is OFFLINE
Tried also ./vmoprcmd -activate_host -h MediaServer2.
Netbackup 8.2 version on RedHat
Any ideas, what to check more?
It is a long shot, but take a look at this article.
You mentioned a VPN connection, meaning there is likely a firewall somewhere.
What you are seeing is definitely network related.
Thank You for your responses.
For us, it wasn't network issue, it was the other one - DNS :)
For troubleshooting i used commands:
bpclntcmd -hn <media server name>
Turned out that there was still an old IP in the internal DNS cache
Solution was to run command:
All good now