Hi Isat,
Whats the OS running on the Client server and the master/media server. If the client is running Linux is xinetd running on there. If yes have you added the relevant services to hosts.allow?
edit /usr/openv/netbackup/bp.conf to include the line:
ALLOW_NON_RESERVED_PORTS = yes
If the file /etc/hosts.allow exists then these entries will need to be appended to it:
bpcd: 10.
vopied: 10.
bprd: 10.
vnetd: 10.
The ports are sufficient for client backups to work if you want to be secure.
13720
13721
13724
netstat -a | grep bpcd
bpcd is the daemon that listens for netbackup requests. It must be running.
- Hostname resolution consistency is very important in netbackup, and it's one of the first things worth checking if netbackup can't connect to the new client. Netbackup provides the command /usr/openv/netbackup/bin/bpclntcmd to check DNS through netbackup.
telnet <client> bpcd
Check for firewall, or if netbackup itself is closing the connection.
- On Redhat, you may need to install compat-libstdc++-296-2.96-132.7.2.i386.rpm. On x86 architecture, install libgcc-3.4.6-8.i386.rpm first.
- On Linux, you may also need to install and/or start xinetd - don't forget to use chkconfig to ensure it starts on boot
Host Properties -> Master Servers -> right-click hambck01 and select 'Properties'
Select Firewall, click Add, enter hostname, click Add then Close. Client will be added to the bottom of the list. Select the new client, and change the attributes to match the other clients, ie:
Select Connect Options tab, and in BPCD connect back, select 'VNETD port'
In Ports, select 'Connect on non-reserved port'
Daemon Connection - 'VNETD port'
Can you confirm if this works after using the above steps.