route the data to second lan card for omniback

[Madanagopalan S]

I need to configure the omniback to make use of second lan card for the backup/restore of other servers. all the
second lan cards are connected to one hub; there is no
gateway for that.

How can I route the omniback connection to second lan.
I configured the second lan card hostname in omni but
still it utilize the first lan; I watched this is thru glance;

Pls help me out to solve the problem

[Isabel Romero]

I think you need to map the IP of the new card to a name. You must change the name of the omniback cell manager. To do this you can use the command:
omnidbutil -change_cell_name
Then you export and import all the clients.
If you have the map of name-ip correctly this will may work ok.

[Madanagopalan S]

I changed the cell manager to new ip;
configured all the clients second lan card name only;
added the ip;name to .omnirc file

but some time its goes onto second lan card and
some time it goes to the first lan card;

what could be the probs?

[Andreas Kromat]

I'm not sure, but maybe the following hints will help.

- disable ip_forwarding (ndd -set /dev/ip ip_forwarding 0 for hpux 11)
- set ip_strong_es_model (ndd -set /dev/ip ip_strong_es_model 1); this helped me at another problem.

[Eric SAUBIGNAC]

Hi,

I don't know anything about omniback, but i think your trouble is a routing problem.

Are the network address of the lan cards in the same IP network ? If so, the only way
to force omniback traffic, initiated by the omniback server, to use a specific interface
is to add some routing information about the omniback clients.

For example : route add host

But all the traffic to these clients (telnet, ftp, ...) will then use this second interface.
I have no knowledge about a routing method based on the type of service ? Does anyone know ?

Eric

PBFWME : Please Be Fair With My English

[Steven Sim Kok Leong]

Hi,

I have a dedicated private LAN for my Omniback Cell after relocating omniback's use of the public LAN to the use of the private LAN.

To maximise flexibility and minimise changes, I simply modify the following few things (without any need to change my backup specifications or add a new hostname to the cell).

The following works to relieve the production network off the omniback remote backup by relying on the fact that inter-server communication for non-backup purposes is usually minimal in comparison to client-server communication.

Steps:
----------------------------------------------
1) Modify your /etc/hosts file to isolate the network backup communication via the private LAN. Also configure your secondary NIC card LAN IP along with its netmask correctly.

Example:

a. At the Omniback Client (disk agent),
======================================
In /etc/hosts,

Instead of:
CellServer_Hostname 133.133.133.133 (public LAN IP)
Media
MediaAgent_Hostname 133.133.133.134 (public LAN IP)

Change it to:
CellServer_Hostname 10.0.0.133 (private LAN IP)
MediaAgent_Hostname 10.0.0.134 (private LAN IP)

In /etc/rc.config.d/netconf, configure your secondary NIC card:
IP address: 10.0.0.135
Netmask: 255.0.0.0

b. At your Omniback Client (media agent),
========================================
In /etc/hosts,

Instead of:
CellServer_Hostname 133.133.133.133 (public LAN IP)
DiskAgent_Hostname 133.133.133.135 (public LAN IP)

Change it to:
CellServer_Hostname 10.0.0.133 (private LAN IP)
DiskAgent_Hostname 10.0.0.135 (private LAN IP)

In /etc/rc.config.d/netconf, configure your secondary NIC card:
IP address: 10.0.0.134
Netmask: 255.0.0.0

c. At your Cell Manager,
=======================
In /etc/hosts,

Instead of:
MediaAgent_Hostname 133.133.133.134 (public LAN IP)
DiskAgent_Hostname 133.133.133.135 (public LAN IP)

Change it to:
MediaAgent_Hostname 10.0.0.134 (private LAN IP)
DiskAgent_Hostname 10.0.0.135 (private LAN IP)

In /etc/rc.config.d/netconf, configure your secondary NIC card:
IP address: 10.0.0.133
Netmask: 255.0.0.0



2) Configure your nsswitch settings so that /etc/hosts name resolution is used before DNS name resolution (include NIS if using it):

In /etc/nsswitch.conf on all three servers ie. CellServer, MediaAgent and DiskAgent, change your hosts entry:

hosts: files [NOTFOUND=continue] dns
----------------------------------------------

As such, there are no changes required on your Omniback Cell configuration at all. And if your secondary LAN should fail (eg. hub failure), you can always switch back to the primary LAN interface by modifying /etc/hosts on all 3 servers back to their original configuration.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com