Hi George,

The way I understand it is that you cannot use two different SN's at the same 
for backup from a single client (even though they are in the same pool).

The client will try and connect to the Storage Node Host (as you know) and once 
that requirement has been met (with the first available one going down the 
list), then that attribute is set, and only that host will be used. Meaning, if 
half way through the tape on that node gets full or the device fails (etc), 
that backup will fail (or will be pending).

So your understanding, is the same as I understand it - as your tests would 
have shown.

I am not sure if there is another way around it - apart from having to manually 
re-do the storage node affinity list every time you want the priority to change.

Regards,
Riaan

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On Behalf Of George Sinclair
Sent: Tuesday, March 08, 2005 1:17 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Using multiple storage nodes for same client?

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.6.4 - Release Date: 3/7/05
 

--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=