Backup Exec Adamm Mover Error Deviceio
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers backup exec 33152 adamm mover error turn on suggestions Auto-suggest helps you quickly narrow down your search results by backup exec event id 33152 adamm database suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery :
Event Id 33152 Backup Exec 15
Backup Exec : Adamm Mover Error After Upgrading to SP4 on Backup... VOX : Backup and Recovery : Backup Exec : Adamm Mover Error After Upgrading to SP4 on Backup... Subscribe to RSS Feed Mark
Adamm Mover Error: Deviceio: Ndmpsendrequest->connection Error To
Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Adamm Mover Error After Upgrading to SP4 on Backup Exec 2012 clovett Level 4 05-13-2014 01:14 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Since upgrading to sp4 on Backup Exec 2012 I am seeing this error on a couple servers pretty frequently. Before sp4 I was not seeing this error. [6484] 05/13/14 15:45:01 Adamm Mover Error: DeviceIo: ndmpSendRequest->connection error to 192.168.3.70:10000, 10054 Labels: 2012 Backing Up Backup and Recovery Backup Exec Patch Troubleshooting Windows Server (2003-2008) 0 Kudos Reply 7 Replies Hello, Check Windows Events lmosla Level 6 05-13-2014 01:29 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, Check Windows Events for System Errors: Event ID's 5,7,9,11,15 These errors point to hardware errors: Event ID 5. This error indicates SCSI parity errors. This error can be caused by a faulty SCSI card or a faulty SCSI termination. for this error contact the hardware's manufacturer. Event ID 7. This error indicates that bad blocks exist and can be caused by an outdated tape device driver, faulty media, or dirty read/write heads on the tape drive. Try updating to the most recent Backup Exec tape device drivers, run a cleaning job, and replace the media with new media, if possible. If the error continues, contact the hardware vendor. Event ID 9. Points to SCSI bus timeouts. To correct this, slow down the SCSI bus and install the most re
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error:
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 BlogVendor PagesWindows Events Event 33152 (Error) Source: Backup Exec How important https://www.experts-exchange.com/questions/26919327/backupexec-constant-checksum-error.html is this event? (3 votes) 1 2 3 4 5 not important very important Description Adamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database = "" Adamm Database Error: Error = Server = "" Active Node = "" Instance backup exec = "BkupExec" Database = "" Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages message adamm mover error string data: Adamm Mover Error: DeviceIo: 00:00:08:00 - Retry Logic: Original settings restored on device: QUANTUM ULTRIUM 4
Jan 15, 2010 Adamm Mover Error: Write Failure! Error = ERROR_CRC Drive = "HP Ultrium" {7820F5AA-1854-49B6-A0A8-D88F3031876C} Media = "000010L3" {AD17CD33-B409-48A9-ADDA-E15C76A597E1} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Dec 29, 2010 Adamm Mover Error: GetDriveInfo Failure! Error = ERROR_IO_DEVICE Drive = "Dell DLT" {7A0C1DBD-D245-4FA1-A01D-D9E4B3EB67DD} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Nov 21, 2011 Adamm Database Error: Driver Connect Failure! Error = ERROR_DATABASE_DOES_NOT_EXIST Server = "ESTER" Active Node = "" Instance = "BKUPEXEC" Database = "BEDB" May 15, 2013 Comments Pure Capsaicin May 26, 2011 peter Non Profit, 101-250 Employees all help greatly appreciated Pimiento Jul 18, 2011 Craig1286 Manufacturing We have found with this that power cycling the tape drive resolves this issue. Probably indicating that there is a loss of comms with the SCSI device Add your comments on this Windows Event! Join the IT Network or Login. Stats Reported 7 years agoHelp Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > backupexec... constant checksum error Want to Advertise Here? Solved backupexec... constant checksum error Posted on 2011-03-29 Storage Software Storage Windows Server 2003 1 Verified Solution 10 Comments 2,284 Views Last Modified: 2012-05-11 Hey guys, I have a windows server 2003 running BackupExec 2010 with an HP StorageWorks backup to tape device. For months now I have been getting a checksum of data has failed daily and cant figure out what the cause is. I have cleaned the device, new tapes, and updated the drivers and still get this constatn annoying error. It seems when I uncheck the verification process I dont get the error anymore but I dont like doing that.. according to Symantec its a CRC error and I dont know if its a faulty error or something I should be concerned about. If I go into my event viewer on the server I see the following errors: Application Log: Event Type: Error Event Source: Backup Exec Event Category: Devices Event ID: 33152 Date: 3/29/2011 Time: 10:33:54 AM User: N/A Computer: SERVER Description: Adamm Mover Error: DeviceIo: 00:00:03:00 - Retry Logic: Retry logic was engaged on device: HP Ultrium 2-SCSI %2 %3 %4 %5 %6 %7 %8 System log: Event Type: Error Event Source: symmpi Event Category: None Event ID: 9 Date: 3/29/2011 Time: 1:28:00 AM User: N/A Computer: SERVER Description: The device, \Device\Scsi\symmpi1, did not respond within the timeout period. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0f 00 10 00 01 00 66 00 ......f. 0008: 00 00 00 00 09 00 04 c0 .......À 0010: 01 01 00 50 00 00 00 00 ...P.... 0018: 01 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 00 00 00 03 00 00 00 ........ 0030: 00 00 00 00 07 00 00 00 ........ Any suggestions?? This is really a frustrating issue... 0 Question by:sb