SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
NetWorker configuration on a secondary network
Author Message
Post NetWorker configuration on a secondary network 
I’ve built a simple networker environment, based on Sun Solaris and W2K
systems ( no cluster, thanks … ), using server, clients and storage nodes
definitions. The main customer requirement was to use only ( or mainly, at
its best ) a management network, instead of the production one.

Let me indicate the terminology, concerning production and management
network names:

Srv: server on the production network, and hostname
Srv_adm: server on the management network


Stn: storage node on the production network
Stn_adm: storage node on the management network

Cln_adm: client on the management network

I’ve installed NetWorker v7.2 server on a Solaris box, and the srv client
was installed automatically.

I’ve defined the Jukebox, with the server srv and the storage node stn
as storage nodes.

I had to configure stn ( also as client ) on the production network
because I’ve seen that, even if I tried to configure stn_adm, on the
storage node the nsrmmd daemons are always started with the “-s srv”
option and never with “-s srv_adm” option.

So I think that in this case mount/umount commands run on the production
network. What about media database informations??

Any client is always defined as cln_adm ( and cln is defined as its
alias ) ;I defined its “server network interface” as srv_adm and “storage
nodes” as stn_adm ( or srv_adm instead of nsrserverhost if the client has
to use the networker server as its storage node ).

I’ve added srv_adm as an alias of srv, and stn_adm as an alias of stn.

I only doubt about storage node configuration in the Jukebox and the fact
that the nsrmmd daemons seem to contact the server hostname and, for what
I know, there is no way to let them speak with srv_adm.

Post NetWorker configuration on a secondary network 
You are very close. You can make everything happen over the _adm network, you just have to do it initially that way in the jukebox setup.

When you build your jukebox start "jbconfig -s srv_adm"; when it asks jukebox prefix, give stn_adm:

On a storage node, the hostname is a prefix to the jukebox name.
Enter the hostname to use as a prefix? [stb] STN_ADM

Your device/jukebox for the storage node should be: rd=STN_ADM:/dev/rmt/Xcbn
The "rd=Server" is your communication path.

This will run your mount/umount commands over _adm network now. However, I did that previously and I seem to recall occasional problems (but I also had 1 master, 3 storage nodes)....YMMV.

PS. "( Ithink the only way is to change server hostname from srv to srv_adm EUR )" -- Don't do it, bad idea.
---
The client config for STN_ADM is a different item. If you configure the client as STN_ADM and treat it normally ("I defined its EURoeserver network interfaceEUR as srv_adm and EURoestorage nodesEUR as stn_adm"), it will run it's backups over the _adm network, but the client config has nothing to do with the jukebox communications.
---
We setup our Storage Nodes the way you have it now with STN_ADM as the client setup (STN_ADM has a Server Network Interface of Srv_adm and a Storage Node of Stn_adm) but we don't have a problem w/ the minimal mount/umount traffic on the production network.....it is miniscule compared to the level of traffic occurring on the _adm network. Again, YMMV. Thanks.

--Ted


-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU]On Behalf Of Pierpa
Sent: Monday, March 14, 2005 8:01 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] NetWorker configuration on a secondary network


IEUR(tm)ve built a simple networker environment, based on Sun Solaris and W2K
systems ( no cluster, thanks EUR ), using server, clients and storage nodes
definitions. The main customer requirement was to use only ( or mainly, at
its best ) a management network, instead of the production one.

Let me indicate the terminology, concerning production and management
network names:

Srv: server on the production network, and hostname
Srv_adm: server on the management network


Stn: storage node on the production network
Stn_adm: storage node on the management network

Cln_adm: client on the management network

IEUR(tm)ve installed NetWorker v7.2 server on a Solaris box, and the srv client
was installed automatically.

IEUR(tm)ve defined the Jukebox, with the server srv and the storage node stn
as storage nodes.

I had to configure stn ( also as client ) on the production network
because IEUR(tm)ve seen that, even if I tried to configure stn_adm, on the
storage node the nsrmmd daemons are always started with the EURoe-s srvEUR
option and never with EURoe-s srv_admEUR option.

So I think that in this case mount/umount commands run on the production
network. What about media database informations??

Any client is always defined as cln_adm ( and cln is defined as its
alias ) ;I defined its EURoeserver network interfaceEUR as srv_adm and EURoestorage
nodesEUR as stn_adm ( or srv_adm instead of nsrserverhost if the client has
to use the networker server as its storage node ).

IEUR(tm)ve added srv_adm as an alias of srv, and stn_adm as an alias of stn.

I only doubt about storage node configuration in the Jukebox and the fact
that the nsrmmd daemons seem to contact the server hostname and, for what
I know, there is no way to let them speak with srv_adm.

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB