This won't work - the client must be able to communicate directly with the
server.  Not only is the index updated by metadata communicated directly
from client to server, but the actual save is instigated by the server
sending the save command to the client.  Also, the client has to be
validated against the server directly.

On Tue, 8 Apr 2003 09:42:33 -0400, George Sinclair
<George.Sinclair AT NOAA DOT GOV> wrote:

>Hi,
>
>Is it possible for the primary server to update a client index if it
>cannot communicate with the client but the storage node can? In other
>words, if the primary server can communicate with the storage node and
>the storage node can back up the client, can the primary server update
>the client's index via the storage node? Clearly, it could write the
>index to tape since the index resides on the main server, but I'm not
>sure how the index would get updated while backups are running.
>

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