Video Screencast Help

Dedicated backup LAN configurations.

Created: 01 Aug 2013 • Updated: 08 Nov 2013 | 4 comments
RickAndrei's picture
This issue has been solved. See solution.

Hi All,

We need to configure a dedicated LAN for our Netbackup. Currently our Netbackup using the Production LAN then we will transferred it Backup LAN.

What are the configurations need to edit or re-configure?

hosts file?

bp.conf?

 

Operating Systems:

Comments 4 CommentsJump to latest comment

Marianne's picture

Yes, you first of all need to config backup network at OS level.

Each backup interface will need a new hostname associated with the IP address. e.g.

# 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.
Add 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.

If you have already done backups for clients with Public Network hostnames, before you change all policies to -bk client names, create symbolic links in image folder to -bk names. e.g:
# cd /usr/openv/netbackup/db/images
# ln -s client1 client1-db
This will ensure that images are stored in same folder and that restores will work using both names.

See these sections in NBU Troubleshooting Guide for detailed info:

Example of host name and service entries on UNIX clients in multiple networks
 
Example of host name and service entries on UNIX server that connects to multiple networks
 
Please ignore all references to 'service entries' as this is no longer used in NBU 7.x and should have been removed from the manual...
 
More reading matter: 
DOCUMENTATION: How network interfaces are selected in NetBackup 6.x/7.x when there are multiple NICs on a NetBackup host. 
http://www.symantec.com/docs/TECH54733
 
How to verify name resolution for Veritas NetBackup (tm) systems, using the "bpclntcmd" command
http://www.symantec.com/docs/TECH27430
 
DOCUMENTATION: When and how to clear the NetBackup host cache
http://www.symantec.com/docs/TECH136792

 

Hope this helps!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
RickAndrei's picture

HI Marianne,

 

Need confirmation for this.

For the example that you showed below. The backup network example 10.10.10.1 master-bk this can be set on the DNS server or just put it to the hosts file?

For bp.conf I will just add the server name in the bp.conf example SERVER = master-bk?

 

Each backup interface will need a new hostname associated with the IP address. e.g.

# 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

 

 

 

Omar Villa's picture

You can use the REQUIRED_INTERFACE or PREFERED_NETWORK entry in bp.conf is not the best way but if you dont want change all your clients configuration I think it can help to expidite the implementation and also is easier to roll it back in case something goes wrong, just be sure the clients can communicate with the media servers through the Backup LAN.

 

Hope this helps.

Regards.

Omar Villa

Netbackup Expert

Twiter: @omarvillaNBU

 

Marianne's picture

It is really your choice to whether you use DNS or hosts files.

At a minimum, you will need to add each machine's own backup interface to its hosts file in order to bind the IP address to a hostname.
Ensure OS-level forward and reverse lookup before you make any changes to NBU.

Yes, you will need bp.conf SERVER entries on master, media server(s) and all clients (as per my post as well as the section in Troubleshooting Guide Guide that I have referred to above).

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links