Networker

Re: [Networker] Database hosed after upgrading to 7.4?

2007-11-09 15:28:28
Subject: Re: [Networker] Database hosed after upgrading to 7.4?
From: jee <jee AT ERESMAS DOT NET>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 9 Nov 2007 20:14:20 +0000
Hi Pete,

The mminfo output you are showing here does not contain any information that 
would help with the recover. It does show, however, that there are savesets 
for that client.

 The problem here is that you cannot do a file recover (which is what you 
tried to do),. However you should be able to do a saveset recover, but you 
need to know the save set ID (ssid) for that particular save set first.

The error message "No index was found on the server " means that there are no 
index records foir that client on the NetWorker server. It doesn't say there 
are no entries on the media db. Media db and Client File Index  are two 
different things.

 Run mminfo and use "ssid" on the report. With the ssid value you can instruct 
recover to do a save set recover.  

Example mminfo command: 

mminfo -q"client=ClientName" -r"name,ssid,volume,ssflags"

(ssflags will tell you if the save set is healthy and can be recovered)


For file recoveries you also need to have the associated Client File Index 
(CFI) entries on the Netwoker server. Your nsrck -X command shows that 
the /nsr/index/ClientName directory is empty (I mean no index records at all) 
for thast client.


Please note that index backups are NW_server backups and not client backups 
(they are  also a special type of save set).

Don't query the volume, use the name of the index save set instead ( just in 
case the index you are looking for is somewhere else).


Try mminfo with  -q"name=index:ClientName" and use (at least)
 -r"name,savetime,ssretent,volume" on the report


Do another mminfo query for that client and that particular save set (if you 
can remember the path -- otherwise don't restrict the query but print the 
name on the -r report), including ssretent.  This will tell you if the 
saveset has expired.


If the index backup exists, then you should be able to recover it using 
"nsrck".  However if the ssretent time of the backup (i.e. the client saveset 
and not the index saveset) has expired you won't be able to recover the 
associated index straight away. You will need to change retention time and 
status for the **client saveset** first.

Use nsrmm twice in order to
 1st:  set the retention time somewhere in the future
 2nd: change the saveset mode to  "notrecyclable".


Then and only then you can expect "nsrck" to recover the index with the 
follwing command:

 nsrck -L7 -t "ChooseSomeDate"  ClientName

(Note:
- use same date as savetime to guarantee index backup is within date range
- check date format -- not sure right now if you need "mm/dd/yyyy" or 
"dd/mm/yyyy"  that should be documented on the man page
 )



I hope this may be of some help.

Jee



On Wednesday 07 November 2007 19:18, Peter Grace wrote:
> Hi fellow NetWorkers,
> 
> This may be a really simple fix but I'm not sure where to attack.  I'm
> trying to restore stuff from when I used 7.2 on this machine.  The
> machine is now 7.4, but it says the client doesnt have any backed up
> save sets.  See below example, I can clearly query the media database
> and see the tape I need is for ninmp3.  Even when I specifically specify
> -c ninmp3, it still tells me there's no index.
> 
> Is there a command I can run to regenerate the media index based on
> what's in the database, or am I stuck rescanning the tapes I saved in
> 7.2 into 7.4?
> 
> [root@ninmp3 catalogs]# mminfo -r nsavetime,client -q volume=TPI674SV
>   save time client
>  1191568955 ninmp3
>  1191571672 ninmp3
>  1191574449 ninmp3
>  1191576799 ninmp3
>  1191578939 ninmp3
>  1191581235 ninmp3
> [root@ninmp3 catalogs]# recover -c ninmp3 /
> 39584:recover: No files have been backed up for this client. No index
> was found on the server for the path / on this client.
> 
> 
> Thanks,
> 
> Pete
> 
> 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