I'm not sure that will work because as I explained, when I removed the
client from the group, and re-ran the group, all the other clients in
the group still backed up their indexes to this pool. The key is the
save set: 'index'. I think as soon as NetWorker sees this as a save set
name, it sends any client's index to this pool, assuming, of course, the
client is running.
So, creating a separate group just for this client will not solve the
problem with other clients sending their indexes to this pool because
whatever groups they're in, they'll likewise send their indexes to this
same pool when they donw running. Perhaps, though, by selecting the
group in the pool config window, as an additional criteria, might force
only members indexes of this group to this pool. I'll try creating
another instance of the client with only the /var file system listed,
and then I'll select that group in the pool window, and I'll list
'index' under the save sets window. I guess I'll also have to list the
client and the server name under the clients window, but it will not be
necessary in this case to list /var also under the save sets window
because I'm going to specify it under the client instance. I'm thinking
I have to do that because otherwise it will back up 'All', and I'm
already backing up all from the first client instance.
Will post a follow-up of my findings.
George
Dale Mayes wrote:
>
> George,
>
> You're correct.
>
> I didn't fully test additional clients (just with the one particular
> client).
>
> I just used the preview feature for multiple clients in the
> group...which shows a different result than starting the group.
>
> Probably another bug in NetWorker...you should report it.
>
> In the interim...Why not just create a separate group for the particular
> client?
>
> Dale
>
> -----Original Message-----
> From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> Sent: Thursday, October 16, 2003 3:47 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] [Fwd: Re: [Networker] Can't get index to backup
> to custom pool]
>
> Well, I tried that, and now it works -- the key, as you pointed out was
> to also include the server in the client list -- but there's one major
> *PROBLEM*. Every client now sends its index to this pool -- well, all
> the clients in the group I was running. I tested this by removing the
> "special" client from the group I was running. I then ran the group, and
> the other clients in the group still send their indexes to this custom
> pool. Their savesets, however, go to the regular pool, which is good,
> but I don't want their indexes going to the custom pool, only the
> "special" client. Next, I tried changing the saveset: "index" instead to
> "client_name:index", hoping this would allow only the named client to
> send its index to this pool. I then added the "special" client back to
> the group and reran the group, and this time all the clients backup
> their indexes to the regular pool, including the "special" client.
> Finally, I tried changing "client_name:index" to "^client_name:index"
> and once again, all the indexes go to the regular pool. There just
> doesn't seem to be a way to tell NetWorker to only send a specific
> client's index to this pool and not everyone else.
>
> When you tested this, did you try adding more than one client to the
> group you were running? Try adding another client, and I bet you'll find
> that while only the one sends /home to the new pool, both will send
> their indexes to the new pool.
>
> Any ideas?
>
> Thanks.
>
> George
>
> Dale Mayes wrote:
> >
> > George,
> >
> > I created a pool, inserted the client name under "Clients:", inserted
> > the save set (i.e. /home) under "Save sets:", inserted index under
> > "Save sets:", inserted the name of the NetWorker server under
> > "Clients:" and specified the appropriate devices (since I have mixed
> > media in my jukebox).
> >
> > It worked just fine.
> >
> > All filesystems except for /home were saved to the "default" pool
> > while "/home" and the "index" for the client were written to the new
> > pool.
> >
> > HTH...Dale
> >
> > -----Original Message-----
> > From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> > Sent: Thursday, October 16, 2003 11:46 AM
> > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject: Re: [Networker] [Fwd: Re: [Networker] Can't get index to
> > backup to custom pool]
> >
> > 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.
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
