Forum Discussion

TonyP4you4me's avatar
9 years ago

Backup failure - tape device error

The consistency check of the snapshot for the Microsoft Exchange database Database was successful.
Storage device "IBM 1" reported an error on a request to write data to media.
Error reported:
A device attached to the system is not functioning.
V-79-57344-34036 - An unknown error has occurred.

After this, the next two jobs run OK, but to another tape in the library.  This job's tape has an unreadable end-marker.  I asked my onsite contact how old the cleaning tape was, and he didn't know so we are getting him a new one asap.  Hopefully that does it. 


relevant bengine log snippet. 

[3076] 09/21/15 23:34:59 TF_NDMPStartWrite(): Started MediaServerWriteThread 4680
[1840] 09/21/15 23:36:18 DeviceManager: timeout event fired
[1840] 09/21/15 23:36:18 DeviceManager: processing pending requests
[1840] 09/21/15 23:36:18 DeviceManager: going to sleep for 900000 msecs
[1840] 09/21/15 23:51:18 DeviceManager: timeout event fired
[1840] 09/21/15 23:51:18 DeviceManager: processing pending requests
[1840] 09/21/15 23:51:18 DeviceManager: going to sleep for 900000 msecs
[4680] 09/21/15 23:54:48 ProcessMoverError default case!  mvrRet = 0x0000001f.  Returning 0xe00084f4.
[3076] 09/21/15 23:54:49 TF_NDMPGetResult(): MediaServer thread done, returning TFLE 0xE00084F4
[3076] 09/21/15 23:54:49 BaseBSDProcessor::MessagePumpAndWaitForResults(): TF_NDMPGetResult() returned 0xE00084F4
[3076] 09/21/15 23:54:49 TF_FreeTapeBuffers: from 0 to 0 buffers
[3076] 09/21/15 23:54:49  data halted: SUCCESSFUL
[3076] 09/21/15 23:54:49 BaseBSDProcessor::PollDataServer: Shutting down.
[3076] 09/21/15 23:54:49 RABackupBSDProcessor: MessagePumpAndWiatForResults() returned -536836876 (0xe00084f4)
[3076] 09/21/15 23:54:49 ERROR: 13 Error: Invalid state to process request
[3076] 09/21/15 23:54:49 BackupMessageHandler::CDB_EndCurrentCatalogOperation(  ) -- entered
[3076] 09/21/15 23:54:49 BackupMessageHandler::CDB_EndCurrentCatalogOperation(  ) is calling PerBSDDataVector[engine_id]->EndCatOperation( )
[3076] 09/21/15 23:54:49 EndCatOperation succeeded
[3076] 09/21/15 23:54:49 BackupMessageHandler::CDB_EndCurrentCatalogOperation(  ) -- returning
[3076] 09/21/15 23:54:49 BackupMessageHandlerForBackupJob::process( eng_msgs::close_catalog & msg ) called
[3076] 09/21/15 23:54:49 Not: 'm_bCatalogDrivenBackup && CatBuildVector[engine_id] && GetCarryFwdCatalogInfoForRemainingObjs( )'
[3076] 09/21/15 23:54:49 ERROR: CatBuildVector[engine_id] is NULL!!!!!
[3076] 09/21/15 23:54:49 TF_FreeTapeBuffers: from 0 to 0 buffers
[3076] 09/21/15 23:54:49 TF_CloseSet
[3076] 09/21/15 23:54:49 Error detected
[3076] 09/21/15 23:54:49 FreeFormatEnv( cur_fmt=0 )
[3076] 09/21/15 23:54:49 PDI backup - done. result = e00084f4
[3076] 09/21/15 23:54:49 Enter NDMPSnapHostBackupEngine::TrackSnappedBSD
[3076] 09/21/15 23:54:55 Exit NDMPSnapHostBackupEngine::TrackSnappedBSD
[3076] 09/21/15 23:54:55 NDMPSnapHostBackupEngine::ProcessBSDs Top of the loop
[3076] 09/21/15 23:54:55 snapResult = 0x0, result = 0xe00084f4
[3076] 09/21/15 23:54:55 NDMPSnapHostBackupEngine::ProcessBSDs Top of the loop
[3076] 09/21/15 23:54:55 snapResult = 0x0, result = 0xe00084f4
[3076] 09/21/15 23:54:55 Exit NDMPSnapHostBackupEngine::ProcessBSDs
[3076] 09/21/15 23:54:55 @@@@@@@MyCloseSocket called with sockfd = 1904(0x770)    retval = 0
[3076] 09/21/15 23:54:55 NDMPAgentConnector::EndConnection(): Data Server = LIEX-MAIL
[3076] 09/21/15 23:54:55 Setting rewind flag to true for older device.  This will likely degrade the performance of the current job.

 

  • I'm not sure why this thread was split.  it's not 2 issues.  I originally said the symptom was the end-mark being unreadable.  

    https://www-secure.symantec.com/connect/forums/be2010-job-fails-mid-week-every-week#comment-11377031

6 Replies

  • This is a different problem from the VSS problem which you reported earlier so I have branched it off as another discussion.

    It would appear that your tape drive is giving problems as well.

    Is your media server a VM?

    1. You should change the tape to a new one.

    2. Clean the tape drive

    3. Run the manufacturer's diagnostics utility against the tape drive. Make sure you select the write test and that you stopped ask the BE services beforehand

  • If it works with other tapes, and your tape giving you errors is marked unreadable, then check for Hard Write Errors and Soft Write Errors in the tape statistics in BE. If there are multiple HWE's, then the tape is faulty and I would suggets trying that job with another tape.

    Thanks!

  • There are only soft write errors.  I've run a brand new cleaning tape last night.  Sometimes it takes a while for people to agree with your diagnoses and pay a whopping $50 for a tape, and then that tape gets lost in the mail ...Murphy and his damn law... 

    Anyway, I'll wait a week for it to run without this issue again and then close the thread.  The sporadic nature of this issue is the reason it's open for so long. 

    Thanks for all the help, all. 

     

     

  • After this, the next two jobs run OK, but to another tape in the library.  This job's tape has an unreadable end-marker.

    The end-marker-unreadable is a symptom of a backup that was interrupted for one of many reasons.  It is a symptom of the problem but not the actual problem itself.  It MAY be a symptom of a bad tape cartridge, in which case the cartridge should be retired.  It may be a symptom of something else, in which case moving the tape to "scratch" or erasing the tape makes that cartridge perfectly healthy and re-usable again.

  • I'm not sure why this thread was split.  it's not 2 issues.  I originally said the symptom was the end-mark being unreadable.  

    https://www-secure.symantec.com/connect/forums/be2010-job-fails-mid-week-every-week#comment-11377031