Solved

Restore Nas file > Failed to seek to the correct location on the media to start the data restore

  • 26 January 2022
  • 12 replies
  • 1113 views

Userlevel 4
Badge +14

 

Hello,

All my backup are completed successfully Since 3 months

backup source is Netapp, the backup target is a HPE StoreOnce

When I try to restore a nas file, I get this error message in Commvault console :(

Ticket is also opened at Commvault side

any clue ? Thanks !

 

Error Code: [62:473]
Description: Failed to seek to the correct location on the media to start the data restore.
Source: bripmasrv01, Process: cvd

 

here is an extract of the media agent log file nasRestore.log

2541369 26c749 01/26 12:28:29 15485 NDMP INFO[masrv01] 0: CVNRS: Accepted incoming NDMP data connection from the file server IP: [127.0.0.1] Port: [39520] to local IP: [127.0.0.1] Port: [56115].
2541369 26c749 01/26 12:30:02 15485 Mover Halt: received NDMP_MOVER_HALTED reason [NDMP_MOVER_HALT_MEDIA_ERROR]
2541369 26c749 01/26 12:30:02 15485 NDMP message processing (from the socket) in data mover returned error.
2541369 26c749 01/26 12:30:02 15485 NDMP data restore processing was not successful.
2541369 26c749 01/26 12:30:02 15485 NDMP_LOG_FILE [NDMP_FILE_NOT_FOUND] [Br_Controlling/Contabilità/Monthly report/2021/ITC02/Cap var Other/Cap_template_BR_122021.xlsx]
2541369 26c749 01/26 12:30:02 15485 Data Halt: received DATA_HALT with reason [NDMP_DATA_HALT_ABORTED]
2541369 26c749 01/26 12:30:02 15485 NDMP INFO[cvsrv01] 0: Total number of files sent for recovery :: 1,Total number of files recovered successfully :: 0,Total number of files which skipped to be recovered :: 0,Total number of files which failed to be recovered ::1
2541369 26c749 01/26 12:30:03 15485 NDMP_DATA_ABORT: successful
2541369 26c749 01/26 12:30:03 15485 NDMP_DATA_STOP: successful
2541369 26c749 01/26 12:30:04 15485 NasRestore::OnMsgCloseArchive() - NdmpRestore::restoreDump failed for archive file id [25594]
2541369 26c749 01/26 12:30:04 15485 NasRestore::OnMsgCloseArchive() - Paths restored successfully:[0], Paths Failed[1].
2541369 26c749 01/26 12:30:04 15485 FclRestore::processRestoreMsgs(4898) - Processing FSR_MSG_WAIT_ARCHIVE_CLOSED
2541369 26c749 01/26 12:30:04 15485 FclRestore::OnMsgRestoreEnd(6858) - Restore on client [masrv01] subclient [Workgroups] completed...
2541369 26c749 01/26 12:30:04 15485 FclRestore::OnMsgRestoreEnd(6859) - File Statistics:

Total [1], Succeeded [0], Skipped [0] Failed [2]

icon

Best answer by Mike Struening RETIRED 21 April 2022, 23:50

View original

If you have a question or comment, please create a topic

12 replies

Userlevel 7
Badge +23

@Bloopa can you share the case number here?  Seek errors are usually related to the library itself, but not always.  I’d like to see how far the engineer has gotten so far!

Userlevel 4
Badge +14

Hello @Mike Struening ,

 

Commvault ticket is 220126-156 

I have opened also an HPE ticket 5361656195

thanks !

 

Userlevel 7
Badge +23

Appreciate the update.  Keep us posted on HPE!

Badge

Hi

One has some solucion,  I have this with Storage Hitachi and HP Storeonce 

Userlevel 4
Badge +14

Hi

One has some solucion,  I have this with Storage Hitachi and HP Storeonce 

Hi Commvault has delivered a patch that correct this issue. the patch must be deployed on all our media agent. This issue takes a long time to be resolved.

 

 

Badge

Which patches the it solves? version?

Userlevel 4
Badge +8

Hi @Infraestructura 

The issue is seen with SP24 and above. Let me know the version and can share the patch. It has be installed on top of latest HPK.

Userlevel 7
Badge +23

@Bloopa , can you share the patch details for @Infraestructura ?

Thanks!!

Userlevel 4
Badge +14

@Infraestructura @Mike Struening 

my version was 11.24.29, I had to upgrade to 11.24.38 then apply this patche on MA
 
 v11SP24_Available_Diag4474_linux-x8664.tar


https://cloud.commvault.com/webconsole/browse/MyDrive.do?shareFolderId=852106&path=8e1b995e4bd54ed6b5a434629b84c2db&iP=PUBLIC&_gl=1*emya6o*_gcl_aw*R0NMLjE2NDM3ODk1MTEuRUFJYUlRb2JDaE1JcnItQmpjbmc5UUlWTW85b0NSMEVHd1hoRUFBWUFTQUFFZ0pUd1BEX0J3RQ..*_gcl_dc*R0NMLjE2NDM3ODk1MTEuRUFJYUlRb2JDaE1JcnItQmpjbmc5UUlWTW85b0NSMEVHd1hoRUFBWUFTQUFFZ0pUd1BEX0J3RQ..

 

incident number is 220126-156

Userlevel 7
Badge +23

Sharing solution:

Dev created the update UpdateBundle_Build1108123_Form4474 for this issue.

If anyone else has this issue, please mention the form when creating the case so it can be provided.

Userlevel 1
Badge +5

Hello @Mike Struening 

I have a similar issue and case is with dev engineer who confirmed that chunk is corrupted.

But there is no sign of corruption just that commvault is not able to read the header correctly.

 

We had similar issue 1 month back which was fixed by a key on MA. Can you please review the case 220427-122  and advise if this is related?

Userlevel 7
Badge +23

@shailu89 It doesn’t look exactly the same based on my cursory review, though feel free to send a link to your engineer so they can better prepare the two issues.