Ah, now you hit the nail on the head: adding the savesets (At least for
the indexes) to the save sets list in the pool configuration window.
Eureka! I had never considered this. Didn't realizer you could do this.
Will play around with this. Thanks, Shelley!
BTW, why would I want to add the bootstrap? Isn't this for the server
only? I don't want the server's bootstrap to go to this pool.
George
"Shelley L. Shostak" wrote:
>
> On Mon, 29 Sep 2003, George Sinclair wrote:
>
> >
> > Well, what I think what I'm actually asking is really two questions:
> >
> > 1. Is it possible to have more than one index for a given client wherein
> > one index would be populated with the data that's getting backed up by
> > instance 1, and the data in the second index would come from the backups
> > for the second client instance? For example, let's say I have a client
> > with / and /disk2 file systems. If I create two client instances, one
> > listing /, and the other listing /disk2, both being in two different
> > groups and associated schedules, could the backups for one instance
> > affect one index and the backups for the other affect the other index
> > rather than there just being one index?
> >
>
> Hi George,
>
> There is only one index per client. There is no way to fool Networker into
> having multiple indexes for a single client. I tried this. I played games
> with DNS and it never worked. It might work if your client can support
> virtual IPs since the hostname would be different.
>
> The problem is that depending on levels and times of backup, you may not be
> getting exactly what you want on each tape.
>
> > 2. If I have clientA:/disk2 going to POOL_2 and clientA:/ going to the
> > POOL_1 then how do I get the index for clientA to go to POOL_2 and not
> > POOL_1? POOL_2 is controlled by group, and not level. POOL_1 is
> > controlled by level only so no groups are selected. I'm thinking the
> > only way around this would be to just back up all the savesets on
> > clientA to POOL_2 so you'd get the index by default. So there would be
> > just one instance of clientA, not two, and all file systems would be
> > listed. Otherwise, maybe I could create a clone pool (POOL_2_c) and
> > clone the index there?
> >
>
> Cloning has the same problems as the original backups. There should be a way
> to set up getting the indexes to go where you want them to go with the pool
> selection criteria.
>
> You can specify "bootstrap" and "index" in the Save sets for Pools. You
> should be able to direct the indexes for a single client based on group. In
> the Pools window, add the appropriate save set (bootstrap, index), check mark
> the right group, and create two clients and put them in different groups.
>
> Shelley
>
> > George
> >
> > "Shelley L. Shostak" wrote:
> > >
> > > George,
> > >
> > > I am not sure what you are asking for here, but yes, an index is an
> > > autonomous
> > > item. You cannot write pieces of an index to tape. But indexes do have
> > > levels. Let's take an example. Say you have client X, which belongs to
> > > group
> > > A and group B. Group A is the regular backups and group B is your special
> > > archive backup. Saturday night you do a level 5 in client X in group A.
> > > Networker will back up the records in the index that correspond to the
> > > level
> > > 5. You then later on Saturday do a level 9 of client X in group B. The
> > > index
> > > backed up will be level 9, so only the index entries that correspond to
> > > the
> > > level 9 backup will be written to tape. I *think* this is what you are
> > > asking.
> > >
> > > The hard part is when the backups overlap, or the index backup of group A
> > > fails and you end up with the index in group B, or even worse, the index
> > > backup in group B fails and you get the index backup in group A.
> > >
> > > This is another reason to avoid Networker for archival backups.
> > >
> > > Shelley
> > >
> > > On Mon, 29 Sep 2003, George Sinclair wrote:
> > >
> > > > Date: Mon, 29 Sep 2003 10:28:07 -0700
> > > > From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
> > > > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > > > Subject: Re: [Networker] How to back up indexes to a separate pool?
> > > >
> > > > It sounds like everything on the given client will have to go to that
> > > > pool rather than just the desired file system path on the client. After
> > > > all, I see no way to get just a part of an index to go there. I mean,
> > > > it's pretty much all or nothing. So I'll have to put that client in its
> > > > own group and then add that group just to that pool and have it be the
> > > > only group listed for the pool which would make it unique with no
> > > > overlap. I can't use exclusively level because then every other backup
> > > > at that level might go there, too. I guess just getting the index, and
> > > > only the index, to go there is not possible.
> > > >
> > > > "Shelley L. Shostak" wrote:
> > > > >
> > > > > The fine manual contains the following about pool selection:
> > > > >
> > > > > How the NetWorker Server Uses Pool Criteria to Sort Data
> > > > >
> > > > > When you configure the NetWorker server, you can create additional
> > > > > pools
> > > > > and sort data by pool type and any combination of the following
> > > > > criteria:
> > > > >
> > > > > o Group (backup group)
> > > > > o NetWorker client
> > > > > o Save sets (file or filesystems)
> > > > > o Backup levels (full, levels [1-9], incremental, manual)
> > > > >
> > > > > Prview mode is great for checking to see what pool Networker will use
> > > > > for
> > > > > data.
> > > > >
> > > > > Shelley
> > > > >
> > > > > On Fri, 26 Sep 2003, George Sinclair wrote:
> > > > >
> > > > > > Date: Fri, 26 Sep 2003 16:19:35 -0700
> > > > > > From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
> > > > > > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > > > > > Subject: [Networker] How to back up indexes to a separate pool?
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm not sure how to explain what I'd like to do, but I'll try my
> > > > > > best.
> > > > > > We have two main pools we use: FUL, ATL. The FUL pool is used for
> > > > > > only
> > > > > > full savesets and the ATL pool is used for all incrementals and
> > > > > > levels
> > > > > > (5, 4, 3, 2, etc.) except 0. Client indexes go to one of the two
> > > > > > pools
> > > > > > depending on the level of the backup.
> > > > > >
> > > > > > I'd like to create a new pool (ARC) for some special data so it
> > > > > > will be
> > > > > > on its own set of tapes. My plan is to have this data get backed up
> > > > > > to
> > > > > > this pool and only this pool regardless of level. The problem with
> > > > > > having this data go to the other pools is that I never want to
> > > > > > recycle
> > > > > > it, so it makes it difficult to extricate the data when I want to
> > > > > > recycle tapes in the FUL and ATL pools. I would end up having to
> > > > > > cloan
> > > > > > the special data savesets before I could recycle the affected
> > > > > > tapes, and
> > > > > > I want to avoid that.
> > > > > >
> > > > > > Getting the desired data to go to the new pool, and only the new
> > > > > > pool,
> > > > > > should not be too hard since I can set up a group and place only
> > > > > > that
> > > > > > group in that pool, but how would I get the index for that client to
> > > > > > write to that pool? The problem is that there is other data on the
> > > > > > client that would be fine to go to the other pools, but I guess
> > > > > > there's
> > > > > > no such thing as multiple client index instances? I mean, each
> > > > > > client
> > > > > > has one and only one index, so I'm thinking that I can't have the
> > > > > > index
> > > > > > for the special data go to the ARC pool and the rest of the index
> > > > > > go to
> > > > > > the other pools as usual? I guess not as there's one and only one
> > > > > > index
> > > > > > per client. Regardless, if I did want to send that client's index
> > > > > > to the
> > > > > > ARC pool, how can I do it? I'm thinking that this may not be
> > > > > > possible,
> > > > > > so I might have to manually clone the indexes to a clone pool like
> > > > > > ARC_clone? Isn't it true that client indexes go to whatever server
> > > > > > is
> > > > > > listed first in the storage node servers field for the primary
> > > > > > server
> > > > > > client?
> > > > > >
> > > > > > If I do this, how would I recover them (or merge older versions in:
> > > > > > nsrck -L7 -t date) from this pool and not have NetWorker use the
> > > > > > indexes
> > > > > > it had backed up to the other pools?
> > > > > >
> > > > > > Any help would be appreciated.
> > > > > >
> > > > > > George
> > > > > > George.Sinclair AT noaa DOT gov
> > > > > >
> > > > >
> > > > > --
> > > > > 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
