Yes,  I think you probably have the solution here in Bobs mail.


----- Original Message -----
From: "Wood, R A (Bob)" <WoodR AT CHEVRONTEXACO DOT COM>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Friday, April 25, 2003 11:34 AM
Subject: Re: [Networker] NDMP clients indexes gets backed up to pool
Default - how to solve?


> It may be worth remembering that the index, although containing details
> of the client, actually belongs to the Networker server.
>
> Your issue may be down to the selection criteria used in the pool. If
> you select by client name then that client data will go to that pool
> (not the index unless the Networker server is listed). If, on the other
> hand, you use group as the selection criteria, both user data and index
> will go to that pool. The whole setup can be pretty flexible, decide
> what you want and, if you can't find out how to do it from the manual,
> ask here - someone will know. :-)
>
> Bob
>
> -----Original Message-----
> From: Mark T Wragge [mailto:storage AT TTT DOT IE]
> Sent: 25 April 2003 10:37
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] NDMP clients indexes gets backed up to pool
> Default - how to solve?
>
>
> My experience with NDMP is that:
> The filers data will be backed up to the NDMP Tape Device as you would
> expect.  But this drive can only be used for NDMP backups.  The backup
> of the client index is not an NDMP backup as the index is data belonging
> to the backup server.
>
> So to back this index up we must use a Non-NDMP tape device.  We must
> have a tape available to this device.  If there is no device then we
> must use a file device to backup the index and allow the backup to
> complete
>
> Usually the networker server would make a request for a tape from the
> NDMP pool and I would label one.  If the non-NDMP device is in a
> seperate library then you can label just one tape.
>
> But in my system the tape which is requested is always from the
> NDMP-pool. Not the default pool.  Why yours is doing this I am not sure.
>
> Is your NDMP tape device and non-NDMP tape devices in the same library?
>
>
> ----- Original Message -----
> From: "Oscar NOSPAM Olsson" <spam1 AT QBRANCH DOT SE>
> To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
> Sent: Friday, April 25, 2003 9:16 AM
> Subject: [Networker] NDMP clients indexes gets backed up to pool Default
> - how to solve?
>
>
> > We have recently begun backing up a netapp filer via NDMP. We run
> > snapimage on the backup server, and one jukebox tape on the backup
> > server has been reassigned as a dedicated NDMP device. However, the
> > indexes that belong to the NDMP clients gets backed up to the pool
> > Default. This is undesirable since that pool can't be edited, and thus
>
> > recycle to/from other pools can't be enabled.
> >
> > As far as I have understood, only NDMP data may be backed up to the
> > NDMP drive, and only NDMP data should be written to the pool that is
> > specificly assigned for NDMP clients, correct?
> >
> > Our normal clients are grouped in different groups, and the pools
> > match the client group. Then the indexes for a specific client gets
> > written down to the same pool as the client. The NDMP clients are
> > grouped in a specific group that is dedicated for only NDMP clients.
> > The NDMP dedicated pool matches only client names. Why not match by
> > group this time as well, one may ask? Well, its because I have
> > understood that one needs to separate NDMP data from other normal
> > legato data, which the indexes still are, correct?
> >
> > So what I have tried is creating a new pool that matches the client
> > names and saveset data in the format (without ")
> > "therealnsrservername:therealclientname:index" - however it still
> > wishes to write indexes to the default pool. The backupserver itself,
> > when backed up, is matched by group membership, as everything else,
> > when networker decides to what pool the backup should be written to.
> >
> > So how can I solve this without creating a tape or file device that
> > has a tape beloning to group Default mounted? Perhaps matching the
> > nsrservername and the specific index savesets to a specific pool?
> >
> > I'm asking because I'd like to select the best solution from the
> > beginning.  So, any ideas? Huh? Huh? ;)
> >
> > file://Oscar
> >
> > --
> > 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=