Still no cigar. NetWorker still writes the client index to the regular
nightly pool every darn time. Here's what I tried for the custom pool:

1. Listed: ^index:client_name under save sets, no other criteria
selected

2. Same as 1 but listed client_name under clients

3. Same as 1 but listed server_name under clients

4. Same as 1 but selected the affected group and listed client_name
under clients.

5. Same as 1 but selected the affected group and listed server_name
under clients.

Can't think of anything else. Yes, the pool is enabled. All devices are
selected.

Even if there is a way to make this work, I still need to get
client_name:/var also to this same pool. Clearly, that's not going to
work unless I specify the client, which I can't do under the saveset
listing. I mean, you can do that with the index, but not with other
savesets, right? Okay, so I'll have to have the client_name listed under
clients so it knows whose /var we're talking about, but it seems that
the suggestions were not to list anything under the clients criteria;
only criteria listed should be the savesets. Hmm ...

George


Davina Treiber wrote:
>
> On Wed, 15 Oct 2003 18:53:52 -0400, George Sinclair
> <George.Sinclair AT NOAA DOT GOV> wrote:
>
> >I checked the admin guide, and here's all I could find:
> >
> >"Directing Client Indexes and Bootstrap to a Separate Pool
> >
> >You can use regular expression matching to direct the client indexes and
> >bootstrap to a different pool than you send the backup data.
> >
> >In the following example, the client file indexes are in index. To send
> >the
> >NetWorker server?s bootstrap and all the client file indexes from this
> >filesystem to the same pool, create a pool (in the Pool resource) with
> >the
> >following attributes:
> >
> >Table 32. Example Attributes for Sending Bootstrap to a Separate Pool"
> >
> >Attribute |  Value
> >----------+-------
> >Name      | Index
> >Pool Type | Backup
> >Save Sets | bootstrap
> >          | index
> >
> >I'm not interested in sending the bootstrap to this custom pool.
>
> George, it's an example. You are perfectly free to adapt it to meet your
> needs.
>
> > Sounds like they want you to do that?
> Or how about they're suggesting that it's a good idea and that you might
> want to do it.
>
> > Maybe I have to do that to get it to
> >work? Moreover, I only want to send just this one client's index to this
> >pool, not all the other clients.
> OK, so you change the regular expression so that it does what you want.
> Take out the bit for bootstrap. Leave in the bit for index, although the
> example is not very good because as someone else pointed out it will match
> the word "index" anywhere in a save set name. Better to specify ^index:
> then it will only pick index at the beginning of a line - i.e. NetWorker 6+
> index naming convention. (YMWV for NW5 and below). Then since you want only
> a specific client, add this in too. So you end up with a regular expression
> like so:
> ^index:yourclientname$
>
> > All the other client's indexes should
> >still go to the standard pool. I'm beginning to think that this is not
> >possible,
> Of course it is possible - this is NetWorker!
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=