Unsolved
This post is more than 5 years old
7 Posts
0
7839
June 18th, 2018 00:00
NDMP-Backup Error >> Failed to propagate handle; TimeOut after inactive
hello COmmunity,
After switching to a new backup server and a platform change from Linux to Windows, we get errors in certain processes when backing up NDMP file systems
suppressed 138 bytes of output.
.144324:nsrndmp_save: Adding attribute *policy workflow name = eNAS-VDM-016
.144324:nsrndmp_save: Adding attribute *policy action name = backup
.06/18/18 07:52:22.821430 NDMP Service Debug: The process id for NDMP service is 0x5a670b0
42909:nsrndmp_save: Performing DAR Backup..
83320:nsrndmp_save: Performing incremental backup, BASE_DATE = 44478769945
42794:nsrndmp_save: Performing backup to Non-NDMP type of device
174908:nsrdsa_save: Saving the backup data in the pool 'dd3 enas'.
175019:nsrdsa_save: Received the media management binding information on the host 'bkpmgmnt01.sis.net'.
174910:nsrdsa_save: Connected to the nsrmmd process on the host 'bkpmgmnt01.sis.net'.
175295:nsrdsa_save: Successfully connected to the Data Domain device.
129292:nsrdsa_save: Successfully established Client direct save session for save-set ID '2854701209' (eNAS1-DM-01:/root_vdm_9/VDM-16_fs2) with Data Domain volume 'enas_001'.
42658:nsrdsa_save: DSA savetime = 1529301142
85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 10.109.130.100, port = 8912
42952:nsrndmp_save: eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 NDMP save running on 'bkpmgmnt01.sis.net'
84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:\Program Files\EMC NetWorker\nsr\bin\nsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)
84118:nsrndmp_save: Failed to propagate handle 0000000000000000 to C:\Program Files\EMC NetWorker\nsr\bin\nsrndmp_2fh.exe child process: Das Handle ist ungültig. (Win32 error 0x6)
accept connection: accepted a connection
42953:nsrdsa_save: Performing Non-Immediate save
42923:nsrndmp_save: NDMP Service Error: Medium error
42923:nsrndmp_save: NDMP Service Warning: Write failed on archive volume 1
42617:nsrndmp_save: NDMP Service Log: server_archive: emctar vol 1, 93 files, 0 bytes read, 327680 bytes written
42738:nsrndmp_save: Data server halted: Error during the backup.
7136:nsrndmp_save: (interrupted), exiting
--- Job Indications ---
Termination request was sent to job 576172 as requested; Reason given: Inactive
eNAS1-DM-01:/root_vdm_9/VDM-16_fs2: retried 1 times.
eNAS1-DM-01:/root_vdm_9/VDM-16_fs2 aborted, inactivity timeout has been reached.
Strangely, these messages do not occur on all file systems, but rather randomly.
Does anyone know this error message and knows where the problem lies? The evaluation of the Celerra logs has so far revealed nothing.
Best Regard
Cykes
umichklewis
3 Apprentice
•
1.2K Posts
0
June 18th, 2018 08:00
If you haven't do so, open ticket with EMC Support. You will need to increase the NDMP logging level on the Celerra (you'll find instructions here on the forums) to capture more error information.
Based on the information above, I'd assume you're using Networker. You may also wish to open a Networker ticket, and tie the two support issues together. That way, both teams can collaborate on a fix.
Let us know if that helps!
Karl
cykes1
7 Posts
0
July 2nd, 2018 02:00
The SR is already open, but so far the support has not found a solution.
Ram.P
16 Posts
0
September 28th, 2018 00:00
Hi Cykes,
Was your case resolved? We are also getting same error for our new NetApp NDMP backup on DD VTL Devices.
Appreciate your quick response.
Thx
Rainer_EMC
4 Operator
•
8.6K Posts
0
September 30th, 2018 03:00
If you have a Problem with your Netapp I would suggest to contact NetApp support
cykes1
7 Posts
0
September 30th, 2018 22:00
Hello,
The problem has now been solved. It was a shot in our firewall. The firewall disconnected an open connection between the NW server and the NDMP device before the list of files to be backed up could be submitted. This caused the timeouts.
cykes1
7 Posts
0
October 1st, 2018 05:00
The network connection between the NW server and the eNAS with Wireshark was monitored for a while. The reset of a connection was detected.
Frame 383372: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
Encapsulation type: Ethernet (1)
Arrival Time: Aug 6, 2018 06:49:25.745367000 Eastern Daylight Time --------------> 12:49 CET
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1533552565.745367000 seconds
[Time delta from previous captured frame: 0.000000000 seconds]
[Time delta from previous displayed frame: 0.000000000 seconds]
[Time since reference or first frame: 355.675781000 seconds]
Frame Number: 383372
Frame Length: 60 bytes (480 bits)
Capture Length: 60 bytes (480 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp]
[Coloring Rule Name: TCP RST]
[Coloring Rule String: tcp.flags.reset eq 1]
Ethernet II, Src: Private_03:00:0a (10:00:00:03:00:0a), Dst: Clariion_7a:48:98 (00:60:16:7a:48:98)
Destination: Clariion_7a:48:98 (00:60:16:7a:48:98)
Address: Clariion_7a:48:98 (00:60:16:7a:48:98)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
Source: Private_03:00:0a (10:00:00:03:00:0a)
Address: Private_03:00:0a (10:00:00:03:00:0a)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
Type: IPv4 (0x0800)
Padding: 000000000000
Internet Protocol Version 4, Src: xx.xxx.xxx.xxx, Dst: 10.109.0.39
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
0000 00.. = Differentiated Services Codepoint: Default (0)
.... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
Total Length: 40
Identification: 0xbc9b (48283)
Flags: 0x00
0... .... = Reserved bit: Not set
.0.. .... = Don't fragment: Not set
..0. .... = More fragments: Not set
Fragment offset: 0
Time to live: 255
Protocol: TCP (6)
Header checksum: 0x67cf [validation disabled]
[Header checksum status: Unverified]
Source: xx.xxx.xxx.xxx
Destination: xx.xxx.x.xx
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]
Transmission Control Protocol, Src Port: 9861, Dst Port: 62425, Seq: 1, Len: 0
Source Port: 9861
Destination Port: 62425
[Stream index: 9]
[TCP Segment Len: 0]
Sequence number: 1 (relative sequence number)
Acknowledgment number: 0
0101 .... = Header Length: 20 bytes (5)
Flags: 0x004 (RST)
000. .... .... = Reserved: Not set
...0 .... .... = Nonce: Not set
.... 0... .... = Congestion Window Reduced (CWR): Not set
.... .0.. .... = ECN-Echo: Not set
.... ..0. .... = Urgent: Not set
.... ...0 .... = Acknowledgment: Not set
.... .... 0... = Push: Not set
.... .... .1.. = Reset: Set
[Expert Info (Warning/Sequence): Connection reset (RST)]
[Connection reset (RST)]
[Severity level: Warning]
[Group: Sequence]
.... .... ..0. = Syn: Not set
.... .... ...0 = Fin: Not set
[TCP Flags: ·········R··]
Window size value: 0
[Calculated window size: 0]
[Window size scaling factor: 4]
Checksum: 0x2f57 [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0
With a new FW rule, the connection remains open even when no data is being transferred.
Rainer_EMC
4 Operator
•
8.6K Posts
0
October 1st, 2018 05:00
thanks for the feedback
yes that makes sense - and it difficult to troubleshoot
just curious - how did you find out that the Firewall was the Problem ?