cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup 7.6 Network issue

Deyaa
Level 4

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                                  clients
192.168.1.10" public" ------------------------------>     192.168.1.11 " public"
10.0.0.10 "private"------------------------------->       10.0.0.11    "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  agent on the client , the client status " can't connect to socket "

 

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

 

please Advice 

Thanks

Deyaa

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

SERVER = dataguard-bck 
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

 

Client bp.conf :

SERVER = netbackup-bck
CLIENT_NAME = dataguard-bck

View solution in original post

11 REPLIES 11

Michael_G_Ander
Level 6
Certified

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

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Nicolai
Moderator
Moderator
Partner    VIP   

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 ?

 

Marianne
Level 6
Partner    VIP    Accredited Certified

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  master
192.168.10.2  media1
192.168.10.3  client1
192.168.10.4  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 entries for -bk servers on all server and clients. 
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: 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): 
    bptestbpcd -client <client-name> -debug -verbose
  • Check output and client's bpcd log.
     

Deyaa
Level 4

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   netbackup       loghost
#---------------backup---------------#
10.0.0.10   netbackup-bck
10.0.0.11    dataguard-bck

 

 

Client :

192.168.1.11   dataguard       loghost

192.168.1.10   netbackup
#-------------backup----------------#
10.0.0.10   netbackup-bck
10.0.0.11    dataguard-bck

 

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 . 

BR

Deyaa

 

Nicolai
Moderator
Moderator
Partner    VIP   

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

Deyaa
Level 4

Hi marianne ;

Thanks so much really appreciated your help ;

the problem solved when i do the below :

1- Edit bp.conf to add SERVER entries for -bk servers on all server and clients. 

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

 
Master/Media Server:

SERVER = netbackup
CLIENT_NAME = netbackup-bck
MEDIA_SERVER = netbackup
SERVER = dataguard-bck

 

Client :

SERVER = netbackup-bck

CLIENT_NAME = dataguard-bck
CONNECT_OPTIONS = localhost 1 0 2

 

is the above configuration Correct ? , please confirm .

Thanks;

Deyaa

 

 

Deyaa
Level 4

Hi Nicolai ;

the  master server was installed with Public network address so i  need to keep that name as 1st entry .

BR

Deyaa

Deyaa
Level 4

Thanks so much ​

Marianne
Level 6
Partner    VIP    Accredited Certified

SERVER = dataguard-bck 
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

 

Client bp.conf :

SERVER = netbackup-bck
CLIENT_NAME = dataguard-bck

Deyaa
Level 4

thanks marianne ;

Really apreciated your Help.

 

BR

Deyaa

Nicolai
Moderator
Moderator
Partner    VIP   

No - its the server list on the client I meant.

Client need to contact the master server on the private network - therefor the host name of the master servers private network need to specified as master server.