Unsolved
This post is more than 5 years old
5 Posts
0
1783
recover error : cannot see the needed volume. NW 7.4SP4
Hi everybody,
I'v see there others discussion about it but no one resolved my problem.
Like the others, I'v a SSID I want to restore, see it in my media, but when I run cmd recover, it cannot see the needed volume.
I do all the things I see differents discussions :
my SSID ( 1683816600 ) is on these volumes ( FULLSDLT.010 and FULLSDSLT.011) :
- 1 : check the device :
run the scanner cmd, scanner -i \\.\Tape1
then run nsrck -L6
nscrk -L7 -t datetime
2- : verify information :
mminfo -av -q etc....
the report seems to be ok :
I see my volume ( FULLSDLT.010 and FULLSDSLT.011) the SSID ( 1683816600 ) and the level ( FULL) and is it recoverable ( flag vF)
3- run cmd recover :
mount the volume on device
recover -d destination -s nsrserver -S ssid /myoriginalpath
and then the error : cannot see the needed volume.
So for now, I don't know what to do more. I'm dreaming about a cmd that force networker to read the SSID on device, something like this :
recover -d -s \\.\Tape1 -S
It is very frustrating to see in NMC the volumes with SSID recoverable, see in scanner command that it see the SSID on the volume, volumes are correctly mounted, and then it cannot find the volumes..... argh...
Anyone have a good new incredible fantastic magic idea ?
Thanks a lot,
Christian
coganb
736 Posts
0
December 19th, 2011 07:00
Hi Christian,
You could have a duplicate clientid issue. How to check for that and what to do to resolve it are explained here:
'Unknown volume' - Troubleshooting 'client id' issues.
Another possibility is described here: http://solutions.emc.com/EMCSolutionView.asp?id=esg118286&usertype=C
Recover fails: 'ansrd Cannot find the volume needed'
-Bobby
ble1
14.3K Posts
0
December 19th, 2011 13:00
Not sure if this is issue with client id, but you can easily verify it by running on server:
mminfo -avot -q client= -r clientid | sort -Unique
(last part above makes sense if using powershell in Windows env)
If you have just one, then:
recover -s -d -S is all you need.
I do not understand why you run scanner nor why you used tape name in recover example. Of course, if you want to recover something specific from ssid, you need to add path of that at the end (be aware it is case sensitive).
chroma3
5 Posts
0
December 20th, 2011 01:00
Hi Hrvoje, hi Bobby,
Thanks for your answers,
I've made what you describe, and I give you the resuls in attach files.
First, the Client-clientid is the same,
then I do what Bobby suggest to do : identify if the saveset is incomplete ( case esg118286)
the result of it is in attach file SSID168.csv
Maybe the problem is here, 'cause I didn't see fragment with a first value of 0, so the true head volume is missing ?
Right ?
Best Regards,
Christian
4 Attachments
clientid.txt
SSID168.csv
ssid.txt
ssid2.txt
coganb
736 Posts
1
December 20th, 2011 02:00
Hi,
Yes, it looks like you're missing some head fragments which are on another volume. There is no 0 first value and the total of the fragsize values does not equal the totalsize value. You will need to follow the instructions in the article to find the missing fragments.
-Bobby