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)
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