Unsolved
This post is more than 5 years old
5 Posts
0
3261
Unable to restore files from the old Netapp Filer (NDMP) to the new one
I'm unable to recover from the old NDMP netapp filer to the new one. I tried both GUI and command line with no luck. When using GUI I can't pass the first "select the recovery hosts" window (the "next" button is grayed out). When using "nsrndmp_recover" command I get "Failed to connect to port 10000 at host 'nma-nie-netap02'", "Couldn't connect to service", and "not able to connect or authorize the recover host 'nma-nie-netap02'" errors.
The old nma-nie-netap02 filer no longer exists in our network environment.
The Networker server properly resolves nslookup DNS queries (forward and reverse ones) for both "nma-nie-netap02" and "netap05ndmp" hosts.
All backups and recoveries of the new netap05ndmp filer work flawlessly.
Thanks in advance for any tips regarding the issue.
ble1
14.3K Posts
0
November 27th, 2016 00:00
I thought this would permissions (remote access of old client should contain new filer), but what confuses me is why would recover process try to contact old filer over port 10000 if old filer is not involved in restore process... Your fastest route on this one is most likely support ticket. Without this port 10000 thingy I would bet permissions, but with that I'm not sure really...
bingo.1
2.4K Posts
0
November 27th, 2016 02:00
The message indicating the NMDP incompatibility worries me.
Could it just be that the NetApp versions are different:
- the new filer runs OnTap 9
- the old one worked with OnTap 8
With respect to NetApp recoveries, the NetWorker NDMP User Guide clearly states:
Cross platform recoveries
You can recover NDMP data to different NDMP client however, you cannot perform a cross platform recover. Recover NDMP
data to an NDMP client that is the same brand, a compatible model, and the same operating system as the original NDMP
client.
ble1
14.3K Posts
0
November 27th, 2016 03:00
I might have missed it, but where do you see new one runs OnTap9? (that was was released 5-6 month ago and I'm not even sure what kind of support by NW does it have, but still error seems to indicate NW is trying to connect to old filer... as for cross platform thingy.... ontap8->9 should be seen as same platform IMHO).
bingo.1
2.4K Posts
0
November 27th, 2016 04:00
I might be wrong but it is just my assumption due to the incompatibility error.
informatyka1
5 Posts
0
November 27th, 2016 14:00
I don't think it's incompatibility related cause the nsrdmp_recovery command syntax from my screenshot worked fine although I had to manually find the corresponding ssid (mminfo). GUI didn't work at all from the 9.x upgrade. A few weeks ago I had to recreate peer information certificates for all hosts and from then on the ndmp_recovery process fails :-/
ble1
14.3K Posts
0
November 28th, 2016 00:00
If this happens since peer thingy, did you check if you get any peer errors now? I normally use something like:
]# cat /nsr/scripts/peer.sh
#!/bin/ksh
#
#set -x
clear
OUT=$(/usr/bin/nsr_render_log -S 'today 00:00:00' /nsr/logs/daemon.raw | grep "Conflicting NSR peer information resources detected for host" | cut -d\' -f2 | awk '{print $1}' | sort -u)
echo "Following host(s) have been found to have conflicting NSR peer information:"
echo "==========================================================================="
IFS=" "
BZZ=$(print - "$OUT")
echo $OUT
echo ""
unset IFS
if [ "`echo -n`" = "-n" ]; then
n=""
c="\c"
else
n="-n"
c=""
fi
echo $n "Do you wish to continue? [y/n]: $c"
read ANSWER
if [ "$ANSWER" = "n" -o "$ANSWER" = "N" ]; then
echo "Screw you guys... I'm going out!"
exit 0
elif [ "$ANSWER" = "y" -o "$ANSWER" = "Y" ]; then
for HOST in $BZZ
do
echo "Running printf \"delete type: NSR peer information; name: $HOST\\\n\" | /usr/sbin/nsradmin -p 390113 -i -"
printf "delete type: NSR peer information; name: $HOST\n" | /usr/sbin/nsradmin -p 390113 -i -
echo "NSR peer record for $HOST removed"
done
else
echo "Wrong answer... Bye bye"
exit 0
fi
This only makes check for current day. NMC also contains peer information so for GUI to work you need to clean peer information there as well most likely. If you have issues like that, you will find clues in daemon.raw
informatyka1
5 Posts
0
November 28th, 2016 01:00
Hrvoje Crvelin, how should I make use of the script you wrote ? Thanks
R_Friberg
34 Posts
0
November 29th, 2016 02:00
Hi,
I had similar issues with the NMC restore a while back. In my case it was the new NDMP box had ndmp vendor information correclty set while the old NDMP box that was removed had that field blank. The field is greyed out and not editable from NMC. So we had to add the ndmp vendor information from nsradmin which worked out fine. I think our DSE published a KB regarding this too, so search for "ndmp vendor information" and you should probably get a hit. The NMC restore for NDMP backups was still a bit tricky to get working, but that was one of the obstacles that we solved.
For you CLI restore, there is no -R in your command, hence it is trying to connect to the old box for the restore.
R_Friberg
34 Posts
0
November 29th, 2016 06:00
Hmm, I might have jumped the gun on the CLI thing. -m should still be valid (I thought it had been removed for some reason before actually opening the manual), but you still need to use :: which isn't in your command.
As always, you should be careful with these types of restores.
ble1
14.3K Posts
0
December 1st, 2016 16:00
That's only to check peer issue on backup server name. If you have peer issue on NMC server, you will see it from daemon.raw (it will be recorded there) and then you can remove it via nsradmin (either CLI command or go to visual mode and remove existing entry).
informatyka1
5 Posts
0
December 7th, 2016 01:00
I noticed that depending on the existence of "-r" switch (in command line syntax) I get two different errors:
Besides, the "ndmp vendor information" may be a good way to go for but I can't find any info in the community for how to manually update/edit this field. Here is what I've got for both old (netap02) and new (netap05ndmp "cluster mode" enabled) IBM Netapp Filers:
Thanks !
R_Friberg
34 Posts
1
December 7th, 2016 09:00
Here is the KB:
https://support.emc.com/kb/490721
informatyka1
5 Posts
0
December 16th, 2016 07:00
R.Friberg, your vendor info tip did the trick. And although I still can't choose the new filer as the destination (using GUI) I'm able to succefully recover using command line. Thanks 4 help !