1) MML Error - Server Status: Cannot connect on socket

Usually this MML error is because bp.conf entry is incorrect .

Verify BP.conf file at below location:
cat /usr/openv/netbackup/bp.conf
SERVER = nbkmstrblk-wc-1p-bu.westchester.pa.bo.comcast.net
SERVER = nbkmstrblk-wc-1p.westchester.pa.bo.comcast.net
SERVER = nbkmediablk1-wc-1p-bu.westchester.pa.bo.comcast.net
CLIENT_NAME = sikdb-wc-c1p-bu.westchester.pa.bo.comcast.net
By default, when NetBackup client is installed, they will be populated with default
entries, and these entries should be updated correctly by SA Team.

If you see entires are incorrect the raise a ticket with Unix L1 Team using Service
Catalog .

2) MML Error - Server Status: Access to the client was not allowed
OR
MML Error - Server Status: Communication with the server has not been initiated or
the server status has not been retrieved from the server
OR
MML Error - ORA-19511: Error received from media manager layer, Server Status:
can't connect to client

For any of the above errors, please follow the below steps to remediate the issue:

Step 1 -
Check NetBackup RPM�s installed.
rpm �qa | grep -i netbackup

Should return
comcast-idea-Netbackup75-Client-1.0.0-3.noarch
comcast-idea-Netbackup7506-Client-1.0.0-1.noarch
Step 2 -
Check NetBackup Processes running
ps �ef | grep netbackup

This command will result in 2 lines

root 13159 1 0 Aug06 ? 00:00:07 /usr/openv/netbackup/bin/vnetd -standalone

root 13164 1 0 Aug06 ? 00:00:09 /usr/openv/netbackup/bin/bpcd �standalone

Step 3 -
Check the routers are correctly configured with respect its Network Zone.
NetworkZone -
https://wiki.io.comcast.net/display/IDEA/Static+Routes+to+Netbackup+servers

To verify the routers, use the below command

/sbin/route -n

The correct route for this server is as follows:

Destination Gateway Genmask Flags Metric Ref Use Iface

172.24.184.0 172.27.7.65 255.255.255.240 UG 0 0 0 eth2

If Destination or Genmask is incorrect as per the Static Routes to NetBackup

servers, work with SA team to correct it.

Step 4 -
Verify the Backup Interface is correctly configured
To verify the backup interface is correctly configured, use the below command

/sbin/ifconfig eth2

Should Return
eth2 Link encap:Ethernet HWaddr 00:26:B9:50:60:AA
inet addr:172.27.7.78 Bcast:172.27.7.127 Mask:255.255.255.192

NOTE: You will get different information for your host. It should look similar to
the following:
nslookup 172.27.7.78
Should return with correct IP's and names for you host

Server: 69.252.80.80
Address: 69.252.80.80#53

Non-authoritative answer:

78.7.27.172.in-addr.arpa name = sikdb-wc-c1p-bu.westchester.pa.bo.comcast.net

Step 5 -
Verify the connectivity is happening between Backup Interface and NetBackup Master
Server.
To get the NetBackup server information:

https://wiki.io.comcast.net/display/IDEA/Static+Routes+to+Netbackup+servers

NOTE: The following will be different per host but will look similar to the
following.

ping -I eth2 172.24.184.5

Where eth2 is Backup Interface

And 172.24.184.5 is NetBackup Master Server IP Address.
If the ping is not happening, work with SA team to fix it.

3) MML Error - Server Status: The specified policy does not exist in the
configuration database Backup server is down

Check with Backup team regarding that and raise ticket to L1 Cloud Ops