Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Volumes Needed: UNKNOWN

Status
Not open for further replies.

esserc

Technical User
Sep 25, 2001
54
US
Help!!!
I have one client out of 104 that I can't recover. When I try to recover using nwrecover or recover either on the host (Solaris) or redirected to another host, I can browse the files and see versions, but when I check what volumes are needed it says 'UNKNOWN' for every file and every version.

I did an nsrck -L3 to crosscheck the media index and it removed every client index.

I did an nsrck L7 and recovered the online index from 4 different times over the past 3 weeks with the same error.

I scanned in several tapes trying -i, -m, and -im with the same error.

I did an nsrck -R -Y to remove all the indexes and did another backup with the same error.

I deleted the client and created a new one with the same client id and did a backup and got the same error.

I have also done the following things with no sucess:
nsrck -L6
nsrim
nsrck -m

All the other clients work fine. No errors are reported by nsrck or nsrim. The savesets for this host show up in mminfo reports. The client id matches in nsradmin and mminfo.

The only thing I know of that I can still do is to delete and re-create the host with a new client ID, but if I do that I will not be able to use any of my old backups even if I scan them in.

Any Ideas?
 
This may be unlikely but check the date on your client. I had a similar problem once and found the client sysadmin had changed the server date to a year earlier. There were no save sets for that date causing the error.
 
Yep,
The savesets do not show up at all.
 
I figured it out!
The client was showing up in the media index as 2 different client IDs. This is not supposed to be able to happen, and it confuses the heck out of Networker.

How to produce this::
Create HostA and back it up.
Delete HostA.
Create HostB with HostA as an alias.
Backup HostB.

At this point, any savesets that HostA and HostB have in common will go in the media db under HostA's client ID. Making them unrecoverable because HostA does not exist!

The only way I figured out how to fix this was to delete any saveset that's linked to HostA's client ID. Then do a nsrck -L3 HostB, nsrck -m, nsrim, and backup HostB with save -c HostB. That seems to clear everything up. At least so far.

The problem with this, is that you only notice it when you try to recover. Which is the worst possible time to find out that your backups are toast. I ran:

mminfo -av -r client,clientid | sort -u

to find any other cases and it came up clean for everything else, but a few of you might want to run this to check your configurations. Especally if you have a very dynamic enviroment like me.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top