If you want the data at the storage node and the indexes at the nsrhost
then just select the client instead of the group in the pool selection
(the indexes belong to the networker server but you've selected
everything in the group go to that pool).

Bob

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Davina Treiber
Sent: 12 May 2004 22:12
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Dedicated Storage Node


johan.gislen AT hik DOT se wrote:
> I'm currently in the process of setting up a dedicated storage node 
> with a jukebox attached to it, and thought it would be a good idea to 
> create a dedicated volume pool for the media in that jukebox.
>
> In the settings for the volume pool (called "StorageNodePool"), I 
> selected the group "StorageNode" which contains only the client that 
> is the dedicated storage node. The client data gets written to the 
> locally attached jukebox, but when it gets to the client index it 
> wants a volume from the "StorageNodePool" at the main Networker 
> server.
>
> Is there any way that I can direct the storage node client's index to 
> the "Main" pool that I use for the rest of my backups?
>
> Platform: Windows 2000
> Networker: 7.1.1

This is expected behaviour. I'm not sure that creating this pool is a
particular wise move. IMHO you should have a very good reason for
creating a new pool, and I wouldn't usually class having a storage node
as one of these reasons. Normally the best reason is to accommodate
different retention policies, or perhaps because you have some specific
offsite requirement.

However I'm not telling you how to configure your system, so let's
consider the question. You can configure a pool to receive your indices
(and bootstraps if required) although I'm not sure whether it's going to
be so easy to make that pool the same one as you are using on your
server-as-a-storage-node. What you would do is as follows: for the index
pool, configure the save sets fields with values of ^index: and
^bootstrap$. You should recognise these as standard regular expressions
that match the index and bootstrap save sets. Now - I'm not sure whether
doing this to your main pool will create further complications, I'll
leave that to you to consider.

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