Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Backup on seperate NIC

Updated: 21 May 2010 | 7 comments
vpro's picture
0 0 Votes
Login to vote

Hi

We are planning to do backup on a different NIC. Could anyone guide me with any best practises that need to be followed for the same?

Also wat other things should be considered?

Comments

Mouse's picture
04
Nov
2009
1 Vote +1
Login to vote

use another hostname for second interface

and put "REQUIRED_INTERFACE=<hostname>" to bp.conf of the client or its equivalent in Windows Client Properties.

Nicolai's picture
04
Nov
2009
1 Vote +1
Login to vote

Static routes may be required too.

Mouse is right, but you may also need to add static routes to the client, if our master/media  server is more than one sub-network away from the client, else data will be send via the default gateway.

Assumption is the mother of all mess ups.

If this post solved you’re questions please send a gratitude by marking it as a solution.

 

Stuart Green's picture
04
Nov
2009
1 Vote +1
Login to vote

Doing a backup on a different

Doing a backup on a different NIC is a good consideration, but also consider putting that backup data on a VLAN back to the Master Server, so it is entirely segragated from the production LAN.

We have that setup.

For example:
Server hostname: fred (NIC#1)
NetBackup hostname: fred-b (NIC#2)

So any reference in NetBackup we use the fred-b hostname as the client. We also maintain local hosts file entries for this client and the master server which also has a VLAN IP address.

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

Jeff Sundin's picture
04
Nov
2009
0 Votes 0
Login to vote

 Stuart has the right idea

 Stuart has the right idea here.  I have found that once you start introducing static routes, you need to be careful so you remember what you did 2 years from now when someone has a problem and cannot figure out why it is not working.  Leave the hostname alone and add the new version of the hostname for backups, like Stuart shows.


Nicolai's picture
04
Nov
2009
0 Votes 0
Login to vote

VLAN

Please do remember that big VLAN's are exposed to spanning tree protocol issues. For larger networks go for IP routing

Some of the cost you take when configuring a dedicated NIC for backup traffic are:

  • Static routes (Sorry - But you can't avoid them unless you have a flat network structure)
  • REQUIRED_INTERFACE entries.
  • alternate client names e.g host-bu
  • Performing restore must be done with alternate client.
  • Database backup (MS SQL, Oracle, SAP etc.) has it own set of issues.
  • Issues for separating real traffic from backup traffic (E.g making sure Windows only register with one name i AD)

Assumption is the mother of all mess ups.

If this post solved you’re questions please send a gratitude by marking it as a solution.

 

vpro's picture
04
Nov
2009
0 Votes 0
Login to vote

And what about jumbo frames

And what about jumbo frames should they be also be configured when planning for seperate NIC for backup??

Nicolai's picture
05
Nov
2009
0 Votes 0
Login to vote

Pretend on your'e network

Jumbo frame support need to be configured simulations, what's impossible in our company network. If you have the ability to configure switches and routers for jumbo frames, go for it.

Assumption is the mother of all mess ups.

If this post solved you’re questions please send a gratitude by marking it as a solution.