We don't do any rman backups. 

I agree that it used to not be this way.  I've been using networker
since the 4.4 days back in the late 90's.   We have always had a 90 day
browse/retention policy, so we are constantly having to restore indexes
around here.   Back in the 7.2 days, we simply did a plain nsrck -L7
with a date, and it would work, even though the index and data were in
an "recyc" status.   

That's not true anymore.  Not sure when it changed - 7.3, 7.4, or 7.5.. 

That's been our experience, I just assumed that was everyone else's
experience.  We had to open a case with EMC a while ago (can't remember
the timeframe), and they were the ones that told us about the nsrmm -e
and -o commands.  

Lucky for us, this has always worked, and have only used the scanner
command 1 time, when I was looking for the bootstrap information during
a disaster recovery. 

David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk

 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Albert, Eddie
Sent: Thursday, September 09, 2010 3:47 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NSRCK -L7 question
Importance: High

Further consideration...

>From my experience, I have never had to restore indices for each file
service as you suggest below. Is it possible you are doing something
different or unique? Absolutely am NOT suggesting your way is wrong,
just curious as to how you did yours vs how I have done mine in the
past.

Also, are your rman backups going to the same place as your file system
backups?

What I have discovered is that SOME backup admins (prounounced NOT ME),
split the load between two backup servers (file systems to one networker
backup server and databases to a different backup server) only ran
indices for the file system forgetting to run an index for the db.

Which of course meant scanning in tapes for antique data... I almost
wonder if older versions of networker did NOT run an index for rman
backups. /shrug

Semper fidelis, /ALE

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Browning, David
Sent: Thursday, September 09, 2010 2:58 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NSRCK -L7 question

And to be clear, as I wasn't the other day, you must do this for each
saveset for the client. 

For example, this morning, I had to restore a D:\, E:\, and F:\ drive
from 5 years ago (long ago expired).   I had to run the nsrmmm -e and
nsrmm -o command 4 times - 1 for the index, and 1 each for the D, E, and
F, drive savesets.   I then ran the nsrck -L7 command. 

If you don't do it for each saveset, it won't restore those index
entries.   

David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk

 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of jee
Sent: Thursday, September 09, 2010 1:51 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NSRCK -L7 question

Yes you can extend your retention time on expired savesets.

You need to change the browse time of the SSID/CLONEID to some recent or
even 
better future time (e.g. . tomorrow's date) using
# nsrmm -e -t <new date> (...)
 **AND**
 change the mode of the SSID/CLONEID to "notrecyclable" using
 # nsrmm -o notrecyclable (...)

then you can run nsrck -L7 to recover the index for that saveset  

j


On Wednesday 08 September 2010 03:20:12 Michael Leone wrote:
(...)
>
> However, I do this on savesets that have not yet expired. I didn't
think
> you could extend the retention time on savesets that had already
expired.
> So I can still do a "nsrck -L7" on currently expired, yet still
retained,
> savesets? I had no idea ...
>

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

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