That sounds like a clientID issue or something related to name resolution 
misconfiguration.

Specifically the nsrinfo/missing-volume bit. I saw that once. 

We tried deleting and recreating the client using the same client id but 
networker complained because the client was already linked to a different 
client Id that was hidden under the current one(!?). 

To resolve that we created a dummy client to using the hiddden client Id, Once 
we got rid of the hiddden client Id  we recreated the client with the known 
client id.  This time the unknown volume issue went away.

nsrinfo issues are linked to client index issues which are in most cases 
caused by  problems with the name resolution and client Id.


jee





On Thursday 05 Sep 2013 10:59:40 Bernd wrote:
> Single item backups of AD objects work. Single items can be browsed. Single
> items cannot be recovered. backup server linux RedHat 6.1. NW 8.1 linux,
> client is windows 2008R2 64 bit, NW 8.0.2.3, NMM 2.4.1. Items can be
> marked. Click on view required volumes gives: UNKOWN.
> 
> Error messages in daemon.log:
> NSR info Failed to recover selected object:Cannot find the volume needed
> A query with mminfo return the correct volume and location of the volume.
> Recovery on a test server work.
> This could be a problem in AD, but I'm not sure.
> 
> Suggestions appreciated.
> 
> regards
> Bernd