-------- Original Message --------
Subject: Re: [Networker] Can't get index to backup tocustom pool
Date: Mon, 20 Oct 2003 12:04:55 -0400
From: George Sinclair <george.sinclair AT noaa DOT gov>
Reply-To: george.sinclair AT noaa DOT gov
To: mtremcinsky AT iccc DOT cz
References: <41256DC5.00553E7A.00 AT iccc DOT cz>
Interesting. I will try that, but I have a sneaking suspicion that it
will only work if I also list the server as a client, and as explained
in the prior postings, this causes a whole slew of unwanted effects. Wil
play with this and post a follow up.
Thanks.
George
mtremcinsky AT iccc DOT cz wrote:
>
> hello George,
>
> I tried it some month ago and it worked in my configuration. I have
> NetWorker 6.2 now.
>
> Try to set the Save set for the pool as "index:client_id" not
> "index:client_name"
>
> I have configured my pool for the client index as follows:
>
> name: ClientIndex
> save sets: index:client_id
>
> You can see the Client id in the setup client general tab.
>
> If I remember correctly - the saveset name "index:client_name" worked in
> versions before 6.x.
> >From version 6.x I must set the save set name to "index:client_id" if I
> want to backup the client index to the custom pool.
>
> Hope this helps.
>
> Milos
>
> George Sinclair <George.Sinclair AT noaa DOT gov> na 17.10.2003 18:47:52
>
> Odpovìzte prosím - george.sinclair AT noaa DOT gov
> Komu: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Kopie: (Na vìdomí: Milos Tremcinsky/ICCC)
> Pøedmìt: Re: [Networker] Can't get index to backup tocustom pool
>
> Content-type: text/plain; charset=us-ascii
>
> I have come to the conclusion that it is not possible. In other words,
> you cannot send a client index to its own pool without also causing one
> of the following things to occur, neither of which are desireable in our
> case:
> A. sending all other client indexes to this same pool (this happens when
> you fail to select a group in the pool configuration window -- ideally,
> a group that only contains the desired client)
> B. sending the server's index to this same pool and causing the server
> to also back itself up, although not necessarily to this pool. In fact,
> in our case, it sent it's backups to the standard pool (that's good) but
> wanted to send its index to this "new" pool.
> The fact is that if you attempt to avoid A. by selecting a group,
> NetWorker will then complain that the server MUST be a member of this
> group and will not let you save the changes to the pool until you have
> done so. After you add the server to the group and then select the group
> in the pool you will be doomed because then the server will back itself
> up every time you run this group, and, of course, will send its index
> here. Kinda sucks, but that's NetWorker for you.
> George
>
> > Craig Ruefenacht wrote:
> >
> > Hi,
> >
> > When I was playing aroud with directing client indexes to different
> > pools earlier this year, I also tried the saveset "index:client" and
> > various other forms (such as "^index:client$") with no luck. In the
> > pool configuration, I had to specify the index saveset as just
> > "index", which, of course, applies to all clients, not to an
> > individual client, so your not the only one not able to get regular
> > expressions to work either.
> >
> > After poking around yesturday (and doing some tests) I remember now
> > exactly what I did when playing around with getting indexes go to go
> > different pools earlier this year. It isn't exactly what you are
> > trying to do, and, in fact, is what you've said you were able to get
> > working.
> >
> > --
> > Craig Ruefenacht
> > UNIX Administrator
> > USANA Health Sciences
> > http://www.usanahealthsciences.com
> >
> > -----Original Message-----
> > From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> > Sent: Thursday, October 16, 2003 4:26 PM
> > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject: Re: [Networker] [Fwd: Re: [Networker] Can't get index to
> > backup
> > tocustom pool]
> >
> > I don't think that will work because you have to list the server under
> >
> > the pool configuration "clients:" section in order to send the desired
> >
> > client index to this pool, and because you list the server, NetWorker
> > will then insist that the server be a member of this group which means
> >
> > that the server will back up its file systems to the normal pool, but
> > will insist on sending its index to this "new" pool. So, you can get
> > the
> > desired client to backup its index to this pool, and, yes, through
> > proper pool selection, you can prevent other clients from backing up
> > to
> > this pool, but I don't see how you can keep the server from wanting to
> >
> > send its index here, too. Furthermore, by having the server as a
> > member
> > of the group, that means that the server will back itself up when ever
> >
> > you run the group. Seems kinda silly to do that when all you want is
> > just the client's index to get backed up (maybe one other file system
> > on
> > the client) when you run the group and not the server, too.
> >
> > I still can't seem to get this regular expression syntax to work for
> > the
> > save sets. NetWorker seems to ignore things like: "index:client" or
> > "^index:client$".
> >
> > George
> >
> > "Shelley L. Shostak" wrote:
> > >
> > > Hi George,
> > >
> > > You will need additional groups to match the selection criteria.
> > >
> > > Shelley
> > >
> > > On Thu, 16 Oct 2003, George Sinclair wrote:
> > >
> > > > Date: Thu, 16 Oct 2003 13:46:31 -0700
> > > > From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
> > > > 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.
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
