Adamm Mover Error Read Failure Error
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 adamm mover error read failure error crc Blogs Groups Vision 2016 Sign In adamm mover error read failure error error io device CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results adamm mover error read failure 11d by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Adamm Mover
Adamm Mover Error Read Failure Error Error Invalid Function
Error: Read Failure! Backup Exec 12 VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! Backup Exec 12 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Adamm Mover Error: Read Failure! Backup Exec 12 adamm mover error getdriveinfo failure EdafioJS Level 3 Partner Accredited Certified ‎04-30-2008 07:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I am running Backup Exec 12 (Rev. 1364) and using an HP LTO 4 Ultrium 1840 tape drive.The server running the backup is running Windows Server 2003 SP2.We keep getting device errors in the application Log when we run backup jobs using harware encryption. I have checked with Symantec and HP documentation and hardware encryption is supported with this tape drive in this version of Backup Exec. The backup job rus completes sucessfully, and test restores from the backup jobs have confirmed that the backup runs sucessfully.I have not been able t find a resolution for the device error in the Symantec Knowledge Base. Anyone have any suggestions?Below is a copy of the error from the application event log n the server running Backup Exec:Event Type:ErrorEvent Source:Backup ExecEvent Category:DevicesEvent ID:33152Date:4/30/2008Time:6:31:16 AMUser:N/AComputer:SRVMAIN1Description:Adamm Mover Error:
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 adamm mover error deviceio CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your
33152 Adamm Mover Error
search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX :
Backup Exec 33152 Adamm Mover Error
Backup and Recovery : Backup Exec : Event Log: Adamm Mover Error: Read Retry! VOX : Backup and Recovery : Backup Exec : Event Log: Adamm Mover Error: Read Retry! Subscribe to RSS https://vox.veritas.com/t5/Backup-Exec/Adamm-Mover-Error-Read-Failure-Backup-Exec-12/td-p/186322 Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Event Log: Adamm Mover Error: Read Retry! Joe_Abraham Level 4 ‎05-11-2005 02:20 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content All,I have this error on the event log from last nites back up.I cannot https://vox.veritas.com/t5/Backup-Exec/Event-Log-Adamm-Mover-Error-Read-Retry/td-p/23561 find any specific reference to this type error ANYWHERE. Well anyways today I think it maybe needing cleaning. We'll see if this error is still on tomorrow. My hardware doesnt inform me when it needs cleaning. How do I get the hardware to message it needs cleaning. My old drive had an LCD screen that displays it needs cleaning.Anyways:Windows Server Machines 2000ASBack Up 9.0PowerVault 110t 320 drive using SDLT tapes.ThanksJoeEvent Type:WarningEvent Source:Backup ExecEvent Categoryevices Event ID:33152Date:5/11/2005Time:8:14:48 AMUser:N/AComputer:Description:Adamm Mover Error: Read Retry!Error = ERROR_INVALID_FUNCTIONDrive = "DELL 1" {E87560BC-3B50-4CD8-9167-2E13FD24EE27}Media = "DLT000009" {1BCDDE56-F994-40CB-98A4-3DFC42FA4B5A}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(1), ScsiPass(1) Data:0000: 00 00 00 00 00 00 00 00 ........0008: 00 00 00 00 00 00 ...... Labels: 10.x and Earlier Backup and Recovery Backup Exec 1 Kudo Reply 8 Replies Re: Event Log: Adamm Mover Error: Read Retry! Chaitanya_Khurj Level 6 ‎05-16-2005 05:08 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi,You can deactivate write Single Block Mode.Also ensure that you are not getting event IDs 7,9, 11, 15 on your SCSI card in system Logs. Check if you have updated the SCSI firmware. Ensure that the Removable
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from http://www.eventid.net/display-eventid-33152-source-Backup%20Exec-eventno-3488-phase-1.htm Windows servers and workstation via the Splunk Universal Forwarder. read more... Event ID: https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 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 BlogVendor PagesWindows Events Event 33152 (Error) Source: Backup Exec How important 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 = "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 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 y