> -----Original Message-----
> From: Davina Treiber [mailto:treiber AT HOTPOP DOT COM] 
> Sent: donderdag 21 augustus 2003 14:09
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] forcing recover to use a specific drive
>
> >- change the Storage Node affinity list for client Node1 to "Node2 
> >(,Node1)".
>
> The storage node affinity list does not apply to restores.

I've had this problem before, and as far as I remember, we solved it by
changing the storage nodes.
If the required volume is not mounted somewhere, Networker will continue
on the first storage node from the list which has access to the jukebox
where the volume is located. 
I've the impression that it will do this even if this node is down, or
if this device is disabled !?
If the storage nodes don't have access to the volume, it will continue
with the ReadHostname mentioned for the jukebox.

This is what is mentioned in the V6.2 Admin Guide, p. 435 :

"Normally, when a recovery is requested, the NetWorker software matches
the host that
is controlling the device required for the recovery with the hosts
listed in the
Storage Nodes list located in the Client resource. After the first
match, the
recover or clone operation takes place. If there is no match, then the
request
reverts to the host listed in the Read Hostname attribute."

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