Olaf,
        What is happening is that the indexes for the remote clients are
waiting to be written. The indexes belong to the networker server hence
the request to have a tape loaded locally for the server.

        There are two ways round this,
1 You can add the remote storage node in the networker server client
config (this way the indexes will be saved to the remote pool - probably
not what you intended)

2 Change the 'Foo' pool selection to the remote clients instead of the
group. That way the remote client data will go to the storage node and
the indexes will go local to the networker server.

I favour option 2 myself.

Regards
Bob

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Olaf Zaplinski
Sent: 20 July 2004 12:52
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] another storage node question


Hi all,

I have another question about my new storage node.

On the storage node, I labeled every tape for a separate pool ("Foo"),
so this pool's volumes reside only in the storage node's jukebox.

But when I start the group that is assigned to that pool, I finally get
a "waiting for 1 volumes to backup pool 'Foo' - on the server, not the
storage node.

So is it true that I need at least one volume on the server's jukebox
that belongs to pool Foo?

Olaf

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

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