Skip to main content
NetApp Knowledge Base

Commvault NDMP restore fails with Input error

Views:
11
Visibility:
Public
Votes:
0
Category:
ndmp
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • NDMP
  • Commvault

Issue

  • NDMP restore fails for a  volume which is controlled by the DMA (Commvault) .The restore fails in Phase I.
  • NDMP debug logs:

0000001a.004d02dc 077a8f30 Fri Dec 27 2024 14:12:07 +05:30 [kern_ndmpd:info:6222] [65995] INFO: DATA notification state 5 (SESS_STATE: HALTING) event 7 (EVENT: I/O ERROR)
0000001a.004d02dd 077a8f30 Fri Dec 27 2024 14:12:07 +05:30 [kern_ndmpd:info:6222] [65995] DEBUG: DATA finish_operation: errnum 0 (Success or No Error) errstr 'EVENT: I/O ERROR' op DATA_OP_HALT_UNKNOWN

  • BACKUP logs:

rst Thu Dec 27 15:11:23 IST 2024 /vs1/vol1/ Start (Level 5, NDMP:1107)
rst Thu Dec 27 15:11:23 IST 2024 /vs1/vol1/ Options (b=0, d, y, H, TCP recv buffer size = 33192, TCP send buffer size = 33192)
rst Thu Dec 27 15:11:23 IST 2024 /vs1/vol1/ Tape_open (ndmp)
rst Thu Dec 27 15:22:38 IST 2024 /vs1/vol1/ Log_msg (rcv_ndmp_check_sock_err Socket err 0x3c)
rst Thu Dec 27 15:22:38 IST 2024 /vs1/vol1/ Error (Input Error)

  • DMA logs:

1714833 1a2a91 05/27 17:39:40 1688566 FclRestore::initialize2(1661) - Fail for Seek Failure selected (job option), restore would fail if seek failures happen.
1714833 1a2a9f 05/27 17:39:45 1688566 NasRestore::OnMsgNasSeekArchive() - Have received [1] source paths.
1714833 1a2a91 05/27 17:57:32 1688566 FclRestore::finalize() - Seek Decision: Samples = 1, Time = 0.0 Sec(s), Average = 0.0 Sec/Sample
1714858 1a2aaa 05/27 17:39:51 1688566 Restore will seek pipeline using logical offset
1714858 1a2aaa 05/27 17:39:53 1688566 Set pipeline option FLUSH_BUFFER_AFTER_SEEK for restore
1714858 1a2ac9 05/27 17:39:58 1688566 Seeking pipeline to offset:[0].
1714858 1a2ac9 05/27 17:56:56 1688566 stat- NRS [Total Pipeline   ][0.00 MBytes/Sec][72940 Bytes][95.9% (92.0% Read, 0.0% Seek, 0.0% Misc)][14 Secs (13 Read Secs, 0 Seek Secs, 0 Misc Secs)

  • Packet traces confirms that there is a communication issue within the network where either sides are not receiving acks and communications are closed abruptly.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.