Connectivity from master to client netbackup 7

[Merv]

Hi,

Got a question on connectivity requuirements between master and client. The client is configured to connect to a media server over a dedicated backup lan(not routable), while the master is setup to talk to clients and media server over the public network only. We want backups to take place over the backup network only. How can we configure the master to talk to the client?

Possibe solution by defining entries in the hostfile where 10.10.10.x is the public network and 192.168.1.x is the backup network. As the master server has no connectivity to the client, I'm not sure reference the backup network hostname but pointing that to the public network will work:

NetBackup Master Server( has 1 NICs Public LAN 

10.10.10.1 master_01

10.10.10.2 media_01_bk #actual ip on backup lan is 192.168.1.2 but master can only communicate to media via public ip 10.10.10.2

10.10.10.3 client_01_bk  #actual ip on backup lan is 192.168.1.3 but master can only communicate to media via public ip 10.10.10.3

NetBackup Media Server has 2 NICs on public LAN and backup LAN

10.10.10.1 master_01

192.168.1.2 media_01_bk

192.168.1.3 client_01_bk

NetBackup Client has 2 NICs on public LAN and backup LAN

10.10.10.1 master_01

192.168.1.2 media_01_bk

192.168.1.3 client_01_bk

Let me know if any of your have exp with this kind of config. Thanks.

[Vijay8007 · Accepted solution]

Make an entry in host file of Mater server and Client, then you will have connectivity between Master Server and Client.

Ex :

Master Server Host File:

Backup Lan IP Address of Client (192.*.*.*               Client Host Name (BKP1)

Client Server Host File:

Backup Lan IP Address of Master Server                  Master Server Host Name

[Mark_Solutions · Accepted solution]

If it helps, the Master does not need to communicate to a client unless that client performs a database backup that uses what is effectively a user backup (such as SQL) or to collect BMR data.

For BMR data collection you could use a Media Server as a BMR Boot Server if you wish

If a client cannot connect (ping) the Master i am not sure how you could route anything though - if it can ping then hosts files will do the job for you.

If you need to connect to a clients host properties you could do it via a Media Server.

Hope this helps

[Omar_Villa]

only add the REQUIRED_INTERFACE = client-backup  under the client bp.conf this will force the client to answer back through the backup NIC and you will only communicate with the master if you have a special setting under this client like if it haves Multiplestreams enabled or BMR or if the client is a Media Server or SAN Client, this kind of special features will demand to send Metadata to the master, but if is a regular client with no multiplestreams enabled it only needs to communicate with the media server.

[Merv]

thanks guys - glad to know that it should work. Will try both methods - required interface and host file and come back to confirm