cancel
Showing results for 
Search instead for 
Did you mean: 

backup ip for appliance 5220

demo4119
Level 6
Partner Accredited Certified

currently im trying to configuring the appliance 5220 to act as a Media server deduplication for my vstorage and netbackup agent backup via backup ip .

Below is my current backup configuration .

master server nbu 7.1.0.4

media server nbu 7.1.0.4

appliance 5220 v2.0.3

host files for all the media and appliance and nbu client

1.1.1.1 master

192.168.1.1 master_bk

1.1.1.2 media

192.168.1.2 media_bk

1.1.1.3 appliance

192.168.1.3 appliance_bk

i have did a test backup from the master& media server to the appliance storage unit the backup traffice is going via backup lan .

But when i perform a test backup from the netbackup client to appliance storageunit , i found that the traffic is via production lan .

Can i configured the appliance ost-plugin\pd.conf to enforce the backup via backup lan ?

13 REPLIES 13

chashock
Level 6
Employee Accredited Certified

Is master_bk in the servers list of the client? 

Don't you still have to set the Required Network Interface to be master_bk on the master?

demo4119
Level 6
Partner Accredited Certified

yes. i have set it .

i have run a bptestbpcd and bpclntcmd from master, media  and appliance to the client successful.

bpclntcmd from client to both master ,media and appliance .

chashock
Level 6
Employee Accredited Certified

Is the client in the hosts files?

chashock
Level 6
Employee Accredited Certified

Try running bptestnetconn -f --prefnet -H <clientname> from your master and media server and post the output.

Chad_Wansing2
Level 5
Employee Accredited Certified

maybe a dumb question, but if the client is using the 5220 as the media server, does the client have a NIC and name resolution for the 5220 NIC on the backup network?

Mark_Solutions
Level 6
Partner Accredited Certified

It may be a routing issue if you did your config from the GUI as everything will have the same gateway.

Try re-doing the network setting from the command lines (CLISH) so that each IP set has its own correct gateway set and get rid of the default gateway.

Hope this helps

 

Chad_Wansing2
Level 5
Employee Accredited Certified

to add onto Mark's comments above, make sure you use the IPv4 command and not the "Configure" command.  IPv4 doesn't require the input of a DEFAULT gateway.  Although you WILL want to go back in via the "Gateway" command to assign the correct gateways for each NIC.  Key thing is that you don't want a default gateway.

That will get you connectivity.  For making the backup traffic go down that connection you either need the names to ONLY resolve to those NIC's or configure the "preferred network" setting in NBU.  I believe the details for that are in the admin guide vol I.  Be careful if you take the naming path.  If you're adding DNS names after the initial configuration of NBU, NBU may not recognize the new DNS names as belonging to the host at an application level.  This has caught me several times.  Basically all the communication can be dead on, but if a client is calling the master "master.backupnetwork.local" and the master only knows himself as "master.prodnetwork.local", he'll deny the connection.  You can see what names NBU has stored for a host at the application level through the "nbemmcmd -machinealias -getaliases -machinename <machinename> -machinetype <machinetype>" command (pardon any errors in syntax, that was off the top of my head but should be pretty close).  To get the machine name/type run "nbemmcmd -listhosts" to get a listing from the EMM processes.

demo4119
Level 6
Partner Accredited Certified

thanks will check on the aliases.

where can i check the MSDP is currently using production or backup ip beside the hosts file i have put in for appliance? it is possible to force the MSDP to backup via the backup lan ip address?

below are the 2 setting i can found from the pd.conf , can i set the local setting to 1 and remove the remark for BACKUPRESTORERANGE and type in my backup ip address of the appliance and subnet?

Please advise.

#

# Determines if server-side settings from storage unit should be used

# 0 - Server settings can override local pd.conf settings

# 1 - Local pd.conf settings will always be used; server settings are ignored

LOCAL_SETTINGS = 0

# Specify the local NIC for backup/restore

# BACKUPRESTORERANGE = 192.168.1.1/32

 

 

Chad_Wansing2
Level 5
Employee Accredited Certified

I wouldn't mess with this in the pd.conf, that would just add a layer of unnecessary complexity I think.  Make sure your standard network name resolution is how it should be (even if you're using host file entries for some of it), then make sure that all of your master and media servers are recognized by their different names you need them to be using in the NBU environment through the nbemmcmd -machinealias command.  If all of your different network names aren't showing up in there, make sure they're added.  That will keep NBU from denying a session just because something is trying to hit a name NBU doesn't know about.

If you want to control the NIC being used for backup/restore operations, I would go with the better known option of the preferred interface settings for NBU.  

 

One other thing to watch out for, the appliance eth0 port comes from the factory with a 192.168.1.1 address assigned.  Make sure that you don't accidentally connect that up and wind up stepping on one of your other systems.

JJ_Zhang
Level 2
Partner Accredited

just to show u the strange traffic. seems i have no way to divert the traffic from the appliance to a backup ip define inside the host file.

the 10.x.x.x is the Prod LAN.

the 192.x.x.x is the BackUP LAN.

Master Server bptestbpcd to my mail_client1 and media024 traffic.
E:\VERITAS\NetBackup\bin>bptestbpcd -host mail_client1
1 1 1
10.192.22.22:54863 -> 10.192.22.16:1556
10.192.22.22:54864 -> 10.192.22.16:1556

E:\VERITAS\NetBackup\bin>bptestbpcd -host mail_client1_bk

1 1 1
192.118.10.10:54865 -> 192.118.10.17:1556
192.118.10.10:54866 -> 192.118.10.17:1556

E:\VERITAS\NetBackup\bin>bptestbpcd -host media024

1 1 1
10.192.22.22:54867 -> 10.192.22.196:1556
10.192.22.22:54868 -> 10.192.22.196:1556

E:\VERITAS\NetBackup\bin>bptestbpcd -host media024_bk
1 1 1
192.118.10.10:54869 -> 192.118.10.54:1556
192.118.10.10:54870 -> 192.118.10.54:1556

bptestbpcd test from the media server to the master and nbu 5220

C:\Users\Administrator>bptestbpcd
1 1 1
192.118.10.46:52368 -> 192.118.10.46:1556
192.118.10.46:52369 -> 192.118.10.46:1556

C:\Users\Administrator>bptestbpcd -host master_bk
1 1 1
192.118.10.46:52372 -> 192.118.10.10:1556
192.118.10.46:52373 -> 192.118.10.10:1556

C:\Users\Administrator>bptestbpcd -host nbu5220_bk
1 1 1
192.118.10.46:52375 -> 192.118.10.54:1556
192.118.10.46:52376 -> 192.118.10.54:1556

C:\Users\Administrator>bptestbpcd -host mail_client1_bk
1 1 1
192.118.10.46:52377 -> 192.118.10.17:1556
192.118.10.46:52378 -> 192.118.10.17:1556

 

bptestbpcd from the nbu5220 to the master, media and client

nbu5220:/usr/openv/lib/ost-plugins # clear
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd
1 1 1
10.192.22.196:43302 -> 10.192.22.196:1556
10.192.22.196:49482 -> 10.192.22.196:1556
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd -host master
1 1 1
10.192.22.196:43885 -> 10.192.22.22:1556
10.192.22.196:41242 -> 10.192.22.22:1556
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd -host master_bk
1 1 1
192.118.10.54:56483 -> 192.118.10.10:1556
192.118.10.54:55845 -> 192.118.10.10:1556
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd -host media024_bk
1 1 1
192.118.10.54:46347 -> 192.118.10.46:1556
192.118.10.54:54475 -> 192.118.10.46:1556
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd -host mail_client1_bk
1 1 1
10.192.22.196:41885 -> 192.118.10.17:1556
10.192.22.196:57901 -> 192.118.10.17:1556
nbu5220:/usr/openv/lib/ost-plugins # bptestbpcd -host mail_client1
1 1 1
10.192.22.196:36754 -> 10.192.22.16:1556
10.192.22.196:56395 -> 10.192.22.16:1556
nbu5220:/usr/openv/lib/ost-plugins #

 

 things to take note:

-as long as the bptestbpcd traffic is fine between any 2 points through backup IP, backup will goes through the backup lan, ie, bptestbpcd from media024 and nbu5220 is via backup lan ip, hence, backup from media024 to the nbu5220 disk will be via backup lan ip 192.x.x.x

-notice from the nbu5220 to the client, no matter how i change the hosts files on nbu5220 or clients, bptestbpcd will ALWAYS goes through my nbu5220 prod ip.

even more strange is, the production network and the backup network is totally no link between them.

is the nbu5220 acting as a router itself in someway  so it's actually publishing its production IP out through the backup lan interface ?

 

any kind advise would be cool at this point of time. thanks.

 

 

chashock
Level 6
Employee Accredited Certified

Have you set the preferred network?

Chad_Wansing2
Level 5
Employee Accredited Certified

This is probably because you've set up the networking via the web gui which uses the "Configure" networking command in the background and that command in turn requires the input of a default gateway which WILL route EVERYTHING to that default gateway.

Just to make sure though; the 5220 is the only one that won't talk on the backup network, correct? If so, see the below.

 

Try this:

  1. Unconfigure all of your networking (may need to do this from the CLISH
  2. go into "networking --> gateway" and make sure that there isn't an entry for 0.0.0.0 0.0.0.0 (the default gateway)
  3. go into the CLISH
  4. under the "networking" main menu use the IPv4 command to configure all your networking
  5. use the "gateway" command to create gateway for the particular NIC's you need them assigned to, but DO NOT configure a default gateway.  In Windows it seems that the default gateway is more of a recommendation whereas Linux seems to consider it more of a routing rule.

Please let me know if this helps.

JJ_Zhang
Level 2
Partner Accredited

hi wan sing,

 

thanks for your suggestions.

i've tried your suggestion before as well.

infact, the output above are captured when there is no gateway configured.

results are the same.

finally, as advise by the singapore symantec consultant, i re-setup the appliance again, making the 192.118.x.x subnet as the primary ip. i make the 5220 talks to the master , media and all clients via backup ip to produciton hostname.

after that, i add in the 10.192.x.x subnet as the secondary ip address. i named this subnet nbu5220_mgt now.

this works so far till date.