> In regard to: Re: [Networker] NSRCK -L7 question, Michael Leone said
(at...:
>
> >> Just a heads up - bootstrap doesn't mean anything when you are
talking
> >> about restoring indexes. You will need to have a backup tape that
has
> >> indexes on it.
> >
> > Well, our bootstrap tapes are where we save the indexes. We don't save
the
> > index with each job; we do a "savegrp -O full" every day. That's what
I
> > refer to as a "bootstrap" ..
>
> By doing that, you're confusing other NetWorker admins, because
bootstrap
> has a very specific meaning to NetWorker. I recommend you adjust your
> terminology -- maybe call them "disaster recovery" tapes or something.
The job that does the index backups was set up by the EMC tech. That job
saves to a group he created called "bootstrap". He also set things up so
that index backups are not saved with the backup jobs, but instead are run
via script on a scheduled task (the "savegrp -O full" I mentioned
earlier). That script (that he wrote) is called "bootstrap.CMD".
So you can see why I refer to the tape that holds the client indexes as
"bootstrap" tape. :-)
I will endeavor to use more specific terms in future.
>
> >> If those are expired, or don't exist, you won't be able
> >> to restore indexes. You will have to use the scanner command (to
rebuild
> >> the index), or do a saveset restore.
> >
> > Ratz! Yeah, those bootstrap tapes have expired, I think. I know I mark
the
> > EOM savesets as "expire in 7 years", but it appears I forgot to market
the
> > index job savesets that way ...
> >
> > So I may have to scan the tapes directly .... yes, I am unfortunately
> > quite familiar with "scanner -i" ...
>
> No, you don't have to. You just have to go through a much lengthier and
> more frustrating process to get the indexes reintegrated.
>
> See the knowledgebase article I mentioned in my previous post. If you
> have the index savesets, you should be able to get them to load using
> the procedure there.
>
> Tim
>
> >> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
> >> EDU]
On
> >> Behalf Of Michael Leone
> >> Sent: Tuesday, September 07, 2010 1:50 PM
> >> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >> Subject: [Networker] NSRCK -L7 question
> >>
> >> So I will be needing to do a "nsrck -L7", to rebuild client indexes,
> >> that
> >> have expired. I've never done that, so I have a couple questions:
> >>
> >> I've read that I can do a "-t nsavetime -c client", to rebuild the
index
> >>
> >> for a specific saveset. But what if I want to rebuild the index for a
> >> specific client, from whatever is on the tape? For example, I have a
> >> bootstrap tape for 2008-06-30. If I wanted to rebuild all the indexes
> >> for
> >> a specific client for that client for that date, do I need to do a
"-t
> >> nsavetime -c client" for each saveset? Or will "-c client" rebuild
all
> >> the
> >> indexes that are on the tape, for that client?
> >>
> >> I have a client that has 10 savesets in each job; I'd rather not
issue
> >> the
> >> command 10 times, to rebuild the indexes for all those savesets, for
a
> >> job
> >> run on a certain date.
> >>
> >> Will nsrck know to only rebuild whatever client indexes are on the
> >> currently loaded tape? Or will issuing just a "-c client" want to see
> >> all
> >> the bootstrap tapes I've ever made?
> >>
> >> Basically, I want to mount that bootstrap tape, and tell networker to
> >> rebuild all the client indexes for "client-1" that are on that
> >> particular
> >> tape, preferably using one command (or rebuild all indexes made for
> >> "client-1 " on a certain date, that are on that tape).
> >>
> >> Is that possible?
> >>
> >> --
> >> Michael Leone
> >> Network Administrator, ISM
> >> Philadelphia Housing Authority
> >> 2500 Jackson St
> >> Philadelphia, PA 19145
> >> Tel: 215-684-4180
> >> Cell: 215-252-0143
> >> <mailto:michael.leone AT pha.phila DOT gov>
> >>
> >> To sign off this list, send email to listserv AT listserv.temple DOT edu
> >> and
> >> type "signoff networker" in the body of the email. Please write to
> >> networker-request AT listserv.temple DOT edu if you have any problems with
this
> >> list. You can access the archives at
> >> http://listserv.temple.edu/archives/networker.html or
> >> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://
> listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
> --
> Tim Mooney Tim.Mooney AT ndsu DOT edu
> Enterprise Computing & Infrastructure 701-231-1076
(Voice)
> Room 242-J6, IACC Building 701-231-8541
(Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://
> listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
