Networker

Re: [Networker] problem adding second nic

2005-06-01 06:35:10
Subject: Re: [Networker] problem adding second nic
From: Davina Treiber <Treiber AT HOTPOP DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 1 Jun 2005 11:34:50 +0100
g. henry wrote:
> hello all,
> networker (5.5.1 on solaris/sparc) works.
> On storage node, i added a second nic, idem on client.
> Before, i had:
> storage node: machine1
> client: machine 2
> 
> and after:
> storage node: machine1-backup
> client: machine2-backup
> 
> but when i tried to backup client, it exited
> 06/01/05 11:01:04 savegrp: command 'savefs -s machine1 -c machine2-backup -g
> Default -p -l full -R -v -F /export/home/henry/test ' for client
> machine2-backup exited with return code 9.
> 06/01/05 11:01:04 savegrp: machine2-backup:probe unexpectedly exited.
> * machine2-backup:/export/home/henry/test Host machine1-backup cannot
> request command execution
> 
> i don't understand why command savefs continues to use old storgae node name?

When you refer to storage node, you are in fact talking about the
NetWorker server, is that right?

The error message indicates that the client is not allowing a backup to
be initiated from the NEW name of the server. To fix this you need to
add machine1-backup to the servers file on machine2, and restart
NetWorker on machine2.

If you want to force the backup traffic from savefs to go via the backup
network you will need to modify the "server network interface" field for
the client, or possibly the storage node affinity list for the client.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>