Networker

Re: [Networker] old index restore, deleted client

2009-06-03 17:43:15
Subject: Re: [Networker] old index restore, deleted client
From: "Browning, David" <DBrown AT LSUHSC DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 3 Jun 2009 16:38:30 -0500
To answer your question, no answer, it was just trying to restore an
index from a different date - it was ignoring the date option, it
appears. 

Just as we were about to call Legato, believe it, or not, we just
figured it out.

We used 08/06/05 instead of 08/06/2005, and it worked!  I thought that
we had used the 4 digit year before, but maybe not. 

Strange, but then I've seen worse... 

Thanks for the response. 

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 Tim Mooney
Sent: Wednesday, June 03, 2009 4:33 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] old index restore, deleted client

In regard to: [Networker] old index restore, deleted client,
Browning,...:

> I'm having a brain spasm, and can't quite figure this one out.
>
> We do restores of old client indexes all the time, using the nsrck -L7
> -t (date) command, and it has never failed, until today.  We are
trying
> to go back to 2005, and as I said, we've done this before.

What's the exact error you're getting?  We've had signficant problems
with
-L7 NOT being able to load indexes since going from 7.2.2 to 7.4.2.  We
have a case open with EMC about this issue right now.  The person I'm
working with from EMC (who's been great, BTW) has found at least a few
other escalations of this exact same issue.

Are you seeing an error for nsrindexasm when it tries to merge the old
client index, or errors from nsrmmdbd in your (rendered) daemon log
about
"Save set eligibility can not be cleared"?

> My guess is that we must have deleted the original client, then added
it
> back in a couple of years ago, and it came up with a different client
> id.  Otherwise, the nsrck -L7 command would work.  I don't know the
> client id from 2005, so I can't check this for sure.

If you still have the savesets, you can probably figure it out, though.

        mminfo -q ssid=OLD_SS_NUMBER_HERE -r
clientid,client,name,savetime

Tim
--
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