Unsolved
This post is more than 5 years old
202 Posts
0
967
hyper-v backup error
Dear Experts!
We are backing up Hyper-v 2012 CSV cluster with Networker 9.0.1.
This config is worked a several months ago, but currently is not working.
The we try to debug the backup flow, but is fails with several errors: (2 error)
1. Error
06/16/17 13:49:47.755820 Reverse DNS lookup failed for fe80::c8c4:4293:4c32:ec5e: No such host is known.
We dont use ipv6, but MS cluster is want to use it. So we cannot switch off.
2. Error
0 1497613799 1 5 0 22852 23480 0 hyper-v.hostname nsrnmmsv NSR notice 5 %s %s 2 0 24 06/16/17 13:49:59.771854 0 77 clu_hosts_matchbyname() comparing 10.0.124.210 and clustername
0 1497613799 1 5 0 22852 23480 0 hyper-v.hostname nsrnmmsv NSR notice 5 %s %s 2 0 24 06/16/17 13:49:59.771854 0 27 clu_hosts_matchbyname:ENTRY
0 1497613799 1 5 0 22852 23480 0 hyper-v.hostname nsrnmmsv NSR notice 5 %s %s 2 0 24 06/16/17 13:49:59.771854 0 52 host1=10.0.124.210, host2=clustername
0 1497613799 1 5 0 22852 23480 0 hyper-v.hostname nsrnmmsv NSR notice 5 %s %s 2 0 24 06/16/17 13:49:59.771854 0 35 clu_hosts_matchbyname:EXIT: b_ret=0
144023 1497613851 3 0 0 22852 23480 0 hyper-v.hostname nsrnmmsv NSR error 26 Hyper-V CSV backup failed 0
It seems that some lookup routine doesnt find the hostname. Dns is ok.
Customer using hostnames with upper cases, in the dns there are lower cases, but the aliases always contains both.
Questions:
- What can be the backup error?
- Wizards are working well.
Thanks in advance.
BR:
Pal
l.walid
26 Posts
1
July 6th, 2017 10:00
Hi,
First you can safely ignore the "Reverse DNS lookup failed" on IPv6 address, since you are working with IPv4.
Then i need you to run this command and check that all the writers are in "Stable" in each server of the Hyperv Cluster :
In powershell type : vssadmin list writers (report here the output)
If there is a writer that is not stable, you may require to restart the host.
Check the Event Viewer -> System for errors on the time of backup.
If nothing of these show you the error, go the client configuration and enable debug level : nsrnmmsv -D5 (on the backup command), and check the output at the hyper-v host (C:\Program Files\EMC Networker\nsr\applogs\nsrnmmsv.raw (you may need to format it)
Good Luck