cancel
Showing results for 
Search instead for 
Did you mean: 

Production/backup LAN split

lumir2
Level 3
Partner

Hello.

I need to split backup traffic from production. I have read many articles about multihomed and change name/domain here but still I'm not sure about solution.

Please, let me know your opinion. Thanks

Lumir

-------------

Current status

===========

Netbackup uses FQDN. Master server hostname (long) is the same as DNS name for production interface IP address. This DNS name is used by all NBU clients now.

Master server

-------------------

Hostname: master.domain.local

Prod IP address: 192.168.54.20 --->resolved to-->  master.domain.local

 

NBU Client

----------------

Hostname: client1.domain.local

Prod IP address: 192.168.54.100 --->resolved to--> client1.domain.local

 

 

Planned

======

Master server and NBU are assembled by new NIC. New IP adresses form a new LAN segment are configured for NBU clients and master server.

The new IP addresses have got aliases in DNS. No master server hostname change.

 

Master server

--------------------

Hostname: master.domain.local

Prod IP address: 192.168.54.20 --->resolved to-->  master.domain.local

Backup IP address: 192.168.85.20--->resolved to master.backup.local

 

NBU Client

----------------

Hostname: client1.domain.local

Prod IP address: 192.168.54.100 --->resolved to--> client1.domain.local

Backup IP address: 192.168.85.100--->resolved to--> client1.backup.local

 

Q:

If I create a new policy where the new clients (from backup segment) are placed, will it be working?

If I use some db backups initiated from client and I change master server name in config  file to the backup one (master.backup.local), will it be working?

Or,  have I to bind the original (production) DNS name to the new backup NIC?

Thanks

5 REPLIES 5

INT_RND
Level 6
Employee Accredited

This is tricky and can lead to all sorts of problems down the line. First, you need to force the master server to use the backup network with the preferred network interface option. Then the big problem you may run in to is that the client must be able to create a reverse tunnel on the same subnet.

EXAMPLE:

If master makes the outgoing connection using backup IP 192.168.85.20 and then client creates a socket outgoing on it's production IP 192.168.54.100 then the backup will fail.

Your proposed solution sounds like it will work. Change everything to use backup DNS entries and keep all communications on the backup subnet.

READ THIS:

"Best practices for Preferred Network, usage, and how it affects source and destination"

http://www.symantec.com/business/support/index?page=content&id=HOWTO60779

Yogesh9881
Level 6
Accredited

Hi,

Backup IP address: 192.168.85.20--->resolved to master.backup.local

I can see hostname getting changed here .... I have a doubt about thisindecision

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified
Please make a new post with your problem. Its unclear what you want.

Walker_Yang1
Level 5
Employee

hi, lumir

Here is a similar config to yours for your reference.

Production LAN:

NBU role Hostname NetBackup Name IP Address(NIC1) Comments
Master/Media masterprod masterprod 10.20.16.108 DNS resolution
Client clientprod clientprod 10.20.16.109 DNS resolution

 Add a new network card(NIC2) on master and client to build backup LAN.

Production & Backup LAN:

NBU role Hostname NetBackup Name IP Address(NIC1) IP Address(NIC2)
Master/Media masterprod masterprod 10.20.16.108 192.168.1.108(no dns resolution)
Client clientprod clientprod 10.20.16.109 192.168.1.109(no dns resolution)

Add Master/Client hosts file:

192.168.1.108     masterbackup

192.168.1.109     clientbackup

NOTES: In my config, production & backup LAN can't access each other. Not sure your production and backup LAN can ping each other. But anyhow, i think, both configs should work fine.

So far, before we can backup with backup LAN, we should make some changes to netbackup itself.

  1. On NetBackup Master side, add SERVER entry to include “masterbackup”. Host Properties->Master Servers->Servers->Additional Servers.
  2. On NetBackup Client side, add SERVER entry to include “masterbackup”.

After doing this, verify if it works fine from netbackup side.

On master:

c:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -host clientbackup

1 1 1

192.168.1.108:50275 -> 192.168.1.109:1556

192.168.1.108:50276 -> 192.168.1.109:1556

From output, we can see that master builds the connection to client from backup LAN.

Next, create your policy with backup client name "clientbackup", it should work fine.

During backup, i observe the backup LAN network, all data trafic passes through the backup LAN netwrok, not production LAN netwrok.

Hence, for your questions,

If I create a new policy where the new clients (from backup segment) are placed, will it be working?

Yes, but need to make seom changes to nbu. see my 2 steps.

If I use some db backups initiated from client and I change master server name in config  file to the backup one (master.backup.local), will it be working?

Yes.

Or,  have I to bind the original (production) DNS name to the new backup NIC?

No, it don't have to.

 

any questions about this, please let me know.

 

Thanks

 

 

wojo
Level 3

I too had a prod/backup configuration and I found it helpful to put a line in the bp.conf file which pointed to the desired network.

 

REQUIRED_INTERFACE = <place system backup IP here>

 

dont forget to re-read your bp.conf...................

PS. My systems were Solaris10