Netbackup 7.6 Network issue

Question

Hi all;

I'm newbie in Symantec Netbackup , i will be grateful if you could help me .

i have a problem regarding to Network in netbackup 7.6 as we implement 2 Network for Netbackup , one network for Netbackup management "public" and one private vlan for backup.

Master/Media Server and all the clients have 2 interfaces , one for public connections and one for private connections.
	please check below:

Master Server/Media Server &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;clients
	192.168.1.10" public" ------------------------------&gt; &nbsp; &nbsp; 192.168.1.11 " public"
	10.0.0.10 "private"-------------------------------&gt; &nbsp; &nbsp; &nbsp; 10.0.0.11 &nbsp; &nbsp;"private"

while i am login to Netbackup via public Network , i push client installation to the client on the private network .
	after successful installation of &nbsp;agent&nbsp;on the client&nbsp;, the client status " can't connect to socket "

&nbsp;

Notice : there is no DNS . and the backup Vlan is private " no connections to the public".

&nbsp;

please Advice&nbsp;

Thanks

Deyaa

marianne · Accepted Answer

SERVER = dataguard-bck&nbsp;
	is only needed if the client is also a media server, but then you need to add that that line to the client's bp.conf as well.

CONNECT_OPTIONS
	is only needed if you want to override the default NBU connect options.

If connection and backups are working, then all is fine.

Suggested master/media bp.conf:

SERVER = netbackup
	SERVER = netbackup-bck
	CLIENT_NAME = netbackup-bck

&nbsp;

Client bp.conf :

SERVER = netbackup-bck
	CLIENT_NAME = dataguard-bck

michael_g_ander · Answer

Have you ensured that the client name uses the name on the private network ?

Be aware that installation use the hostname, which probably is the name on the public network

As you have no DNS, you will have to create entries the hosts files for the private network names, if havnt already

Hope this helps

&nbsp;

nicolai · Answer

There is a couple of pits to avoid.

Netbackup clients must have two different host names for public and private networks
	Use private network names in Netbackup
	Netbackup MUST be able to resolve private host names either by DNS or host files.

What is the subnet mask for the two networks ?

&nbsp;

marianne · Answer

This is how we have been doing it:
	Add /etc/hosts entries and use the backup NIC hostnames in NBU config...

For example:

# Public network
	192.168.10.1 &nbsp;master
	192.168.10.2 &nbsp;media1
	192.168.10.3 &nbsp;client1
	192.168.10.4 &nbsp;client2

# Backup network
	10.10.10.1 master-bk
	10.10.10.2 media-bk
	10.10.10.3 client1-bk
	10.10.10.4 client2-bk

Update hosts entries on all servers and clients.
	Edit bp.conf to add SERVER&nbsp;entries for -bk servers on all server and clients.&nbsp;
	If master server was installed with Public network address, you need to keep that name as 1st entry.

Change CLIENT_NAME in bp.conf on all clients to -bk name.

Change all policies to -bk client names.

After hosts entries were updated, remember to clear NBU host cache:
	bpclntcmd -clear_host_cache
	http://www.symantec.com/docs/TECH136792

Test connectivity as follows:

Ensure firewall rules are in place and/or OS firewall is disabled on server and client(s).
	Use bpclntcmd to test forward and reverse name lookup:&nbsp;http://www.symantec.com/docs/TECH27430
	Create bpcd log folder under /usr/openv/netbackup/logs
	Run this command on master and/or media server(s):&nbsp;
		bptestbpcd -client &lt;client-name&gt; -debug -verbose
	Check output and client's bpcd log.
		&nbsp;

deyaa · Answer

Hi Michael ;

- yes i configured each client with 2 names , one for public and one for private and both are in /etc/hosts :

Master /Media Server :

192.168.1.10 &nbsp; netbackup &nbsp; &nbsp; &nbsp; loghost
	#---------------backup---------------#
	10.0.0.10 &nbsp; netbackup-bck
	10.0.0.11 &nbsp; &nbsp;dataguard-bck

&nbsp;

Client&nbsp;:

192.168.1.11 &nbsp;&nbsp;dataguard &nbsp; &nbsp; &nbsp;&nbsp;loghost

192.168.1.10 &nbsp; netbackup
	#-------------backup----------------#
	10.0.0.10 &nbsp; netbackup-bck
	10.0.0.11&nbsp; &nbsp; dataguard-bck

&nbsp;

there is routing between 192.168.1.0/24 and 10.0.0.0/24.

all ips are pingable , and i push install the client via private hostname "dataguard-bck". but the netbackup server Console work on public ip as the private ip is not reachable .&nbsp;

BR

Deyaa

&nbsp;

nicolai · Answer

Ensure the mastser servers private network interface is the first name on the server list (bp.conf if on UNIX).

Forum Discussion

Netbackup 7.6 Network issue

11 Replies

Related Content

NetBackup Client Network Statistics

NetBackup Storage Space Full issue

EV 15.0 Indexing Issue

Netbackup AIR - Replication Network Interface

Re: oracle backup problem when we migrate client networker to netbackup

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date