Unsolved

This post is more than 5 years old

41 Posts

5378

July 21st, 2009 11:00

Recovering old files no longer in index

I'm currently running networker 7.3.2 and I'm trying to recover file from a tape that's no longer in the system index. I ran the command (nsrck -t 01/06/2009 -L7 servername) and the system starts looking for the tape. I've inventoried the tapes needed and they show up but the system continues to wait for the tape as if it has no knowledge of it being in the library. Get the message waiting for LTO ultrium 3 tape 000091L3. What is the best way about restoring a file that's on a tape no longer in the index?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 21st, 2009 13:00

It is not clear for me if system is waiting for index tape for nsrck -L7 or is it for restore after nsrck -L7 completed? Anyway, if you know exact (case sensitive) file path you can do also ssid recover or directory (assuming they are no spread across the save set as in that case browsable restore is much better option).

41 Posts

July 21st, 2009 14:00

This is the first time I've ever had to restore something that no longer resides in the index. What I've done is install the tape containing the saveset I needed and tried doing a nsrck -L7 to restore the index for that tape. What happens is the unit will not retrieve the tape. Is there a better way to perform this restore? IF so what is the command line needed to complete, Thanks again

2 Intern

 • 

2K Posts

July 21st, 2009 19:00

I would recommend mounting the tape manually into the drive and running scanner -i \\.\tape0 assuming that \\.\tape0 is the device path name. Ensure that nothing unmounts the tape when scanner is running since it is not Networker aware and could halt the process in between.

You can use other scanner options with SSID to recover your specific files/save sets.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 22nd, 2009 01:00

It might be that we need to take a look at your logs and media db status via mminfo. If I understand correctly, you get this problem during index recovery. For that, you must make sure you have tape with required index first in library. Putting it into library only might not be enough as you will need to run inventory for that slot as well. So, run nsrck -L7 -t bla bla clientname as before, see which tape asks for, make sure that tape is in library and see in which slot it is, run nsrjb -Iv -S and after that NW should be able to read the data from it. After you brought back index you can start your restore.

2 Intern

 • 

1.1K Posts

July 22nd, 2009 03:00

You need to recover your index if it still exists, otherwise try scanning the tape in - you seem to know which tape the data resides on so load the tape in the drive and scan in to create a new index with:

scanner -i devicepath

Should sort out your problem though it may take a couple of hours to scan your tape in!

41 Posts

July 22nd, 2009 05:00

Also when I right -click on the tape in NW and choose mount I get an error saying that a Device name is required. Only option is to hit OK.

41 Posts

July 22nd, 2009 05:00

I've installed the tape in the library but I cannot get it to mount, do I need to mount it manually from the Library unit front panel? I ran the following cmd since I know what tape the info is on. The tape is in slot 76. nsrjb -lv -s 76. This is the error I get.
setting verbosity level to `1'
nsrjb: cannot connect to NSR service on 76
nsrjb: RPC error: Remote system error

If on a storage node, enter the NSR server hostname? [76]


I tried scanner -i device path is the device path the slot number of the tape? When I run the following

scanner -i 76 nothing happens.

2 Intern

 • 

1.1K Posts

July 22nd, 2009 05:00

You want to add an n switch to load without mount and use an upper case S to specify slot (not server as with lower case s!):

nsrjb -nlv -S 76

That will do the trick!

41 Posts

July 22nd, 2009 06:00

Ok I think I'm getting somewhere, I ran nsrjb -nlv -S 76 and the tape was mounted. I ran the following command scanner -i \\.\tape1 and the appears that it's scanning the savesets on that particuliar tape, although NW monitoring shows everything is idle. Does this process take time?

2 Intern

 • 

1.1K Posts

July 22nd, 2009 07:00

Yes, go get yourself a coffee or 3, it can take 2 hours or more to scan a tape in!

41 Posts

July 22nd, 2009 08:00

It appears the the scan has completed, so I kicked off nsrck -t 01/06/2009 -L7 vyshared1, to restore the savesets on that tape.Eventhough the tape is in Drive \\.\tape1 networker monitor shows that is waiting on the tape. Not sure if it's doing anything.

2 Intern

 • 

1.1K Posts

July 22nd, 2009 09:00

We have a couple of errors on these clients, probably because the client resource has been deleted since the backup:

vtycnennp006
vtydretsp001.enne.entergy.com

We also have this error:

scanner: write failed, Broken pipe

This is a result of a process failing to respond within a given time - check for connectivity errors then run the scanner again

2 Intern

 • 

1.1K Posts

July 22nd, 2009 09:00

You don't need to do that - the scan will have built a new index. Just go ahead and restore your files.

41 Posts

July 22nd, 2009 09:00

This is the error I recieve when I run the scanner -i \\.\tape1.

scanner: scanning LTO Ultrium-3 tape 000091L3 on \\.\tape1
scanner: LTO Ultrium-3 tape 000091L3 already exists in the media index
scanner: Media DB error: invalid query for client id map database
scanner: Media DB error: client name must be specified
scanner: ssid 2372012143: SYNCHRONIZED at 520 GB, 1301260 file(s)
scanner: (ssid 2372012143) Can't open session for client vtycnennp006 to index
ervice on vtydretsp001.enne.entergy.com
scanner: File index error: `vtycnennp006' is not a registered client
scanner: write failed, Broken pipe

41 Posts

July 22nd, 2009 09:00

Not sure what's wrong.

Basically the clients

vtydretsp001 is my backup server
vtycnennp006 is the server which backups are on the tape I'm wanting to restore.


All I'm trying to do is restore a backup job from a tape that's already been mounted in a drive but can't because the index/saveset for that timeframe is no longer available. I thought if I could restore the index, then when I preformed I restore the paticuliar saveset for the date I needed would appear.
No Events found!

Top