Good day all,
The catch here, as Byron correctly noted is that the index files actually
exist on the backup server. Thus although one thinks of the Index "Logically
Belonging" to the client, the index files "Actually Belong" to the server.
When the index saveset is backed up, it is backed up under the Networker
Server's Client.
Since you specified your client in your index pool, the indexes go to your
other pool (probably a default with no client specified)

Remember the priority for filtering savesets for pool allocation (See AG
pp207)Group, Client, Saveset, Level. THe first match will decide the pool.

Thus to create a pool to catch all indexes, you need a pool where the only
criteria is the saveset "index". If you want to catch the bootstraps as well
then add "bootstrap", but in this case remember that device servicing the
pool will have to be on the Networker server, since bootstraps may ONLY be
saved on a server attached device)

Also remember that the saveset definition can be a regular expression.
I have had cases where the word index appears in other savesets, and these
are then also captured in the index pool. In this case you may need specify
more precisely,

eg /nsr/index
HTH

John Gowing

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