Thanks for the info regarding the restore.

I only see that message if I run the 'changetime' command. Otherwise I can restore from the latest backup without any issue. If changetime is within the last week, it's good.

Current working directory is /root/
recover> changetime 10/07/2010
6497:recover: time changed to Thu 07 Oct 2010 11:59:59 PM PDT

Have you verified you have backups from that date?

Hi,

Let me answer your question first. To recover the index files all you have to do is run "nsrck -L7 -t backup_date client_name".

Secondly, do you see the same message the moment you run the recover command or just when you do a changetime?

HTH,

Rovin D'Souza.

I have verified the backups are good. On a testing server, I have been able to rebuild the database and successfully restore servers, folders, and files from the dates in question. It's just sort of tedious to wait for mmrecov and scanner commands to complete.

If I run the versions command, I only see back to Oct 07.

mmrecov and scanner I used to rebuild the tape indexes/databases on a test server for me to ensure that the backups were working.

Basically, I ran mmrecov with the bootstrap ID of the tape which creates a new res.R folder that replaces the one that networker has.

Then I run scanner -m to rebuild the media indexes followed by nsrck -L7 to verify clients can be recovered.

When you are doing the restore what do you see if you type versions instead of changetime?

Can you explain what the significance of running the mmrecov and scanner commands is?  Have you rebuilt your Networker server?  Did you run nsrck -L7 to recover the indexes after mmrecov?

Running that command for one of the clients I'm working with shows results that go back to Sept 2 2010 on the prod backup server. On the test server, I see a different result as it is an older media database that goes back to Aug 30th. I see the tapes that were used as well as which volumes were backed up each time.

For background, I'm having to restore a bunch of different app logs that we across 8 different servers. I would do it all on our production server but I don't know how to get around the fact that I can't browse more than one week in the past. That seems to be the root of my problem, as I have a browse policy of one month on the backup server, so I was expecting to be able to browse back one month. So I'm using a test server to rebuild indexes in the past in order to retrieve logs that are more than 7 days old as to not interfere with our production server.

I'm sure there's a better way but I don't know what it is

Is there any kind of break in the savesets or do you have a daily backup from Sept 2 to the present?

There is a much easier way, just restore the indexes for the date you want to recover from:

nsrck -L7 -t "6 October 2010" clientname

Which should make the indexes browsable as per that date (it won't affect any indexes currently in existence, only add to them). If we still appear to have issues after that we could try doing recovery direct from the savesets.  My suspicion is that you are backing up with a one week browse time and a one month retention time though I know that is contrary to what you have initially told us - it would be useful if you could double check how your backups have been set up.

I really appreciate the assistance you have been providing.

There were a couple of backups missed due to human error on Oct 4th and 5th but otherwise backups have been done each day.

I have double checked the settings and it is configured with a browse policy of one month in nsradmin.

I'll have a go at using the nsrck command and see how that goes.