Id 33152 Adamm Mover 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 Blogs Groups Vision 2016 backup exec 33152 adamm mover error Sign In CommunityCategoryBoardResourcesUsers
Event Id 33152 Backup Exec 2014
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches backup exec event id 33152 adamm database as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Backup Exec 10d - Event ID 33152 -
Adamm Mover Error Deviceio Backup Exec
Adamm Mover Err... VOX : Backup and Recovery : Backup Exec : Backup Exec 10d - Event ID 33152 - Adamm Mover Err... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup Exec 10d - Event ID 33152 - Adamm Mover Error: GetDriveInfo Failure! Chris_Campbell Level 2 12-18-2006 03:52 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Application: Backup Exec 10d for Windows Servers 10.1.5629Platform: Windows Server 2003 R2 Standard EditionTape Drive: HP DAT72 Drive C7438ABackup Exec Updates Applied: Service Pack 2Hotfix 43Hotfix 46Hotfix 45Latest Veritas Tape Drivershttp://seer.support.veritas.com/docs/284707.htmProblem Description:Backup Exec 10d running on a Brand new HP ML350 with on-board SCSI controller for the HP DAT72 Drive. (Separate RAID Controller for Disks).Have removed/updated both the Tape Drive and Backup Exec sooooo many times now im stuck with the below problem, please can anyone help? I thought I could get telephone support from Veritas/Symantec with this, but not without a cost! Anyway.... can anyone help with the below? U'll be given a God status!Tape device has been detected by Backup Exec and the relevant drivers installed,Driver Provider: Symantec CorporationDriver Date: 23/06/2006Driver Version: 5.1.23.0Prior to this of course was the latest HP drivers, 1.5.32.Device is there and viewable under All Devices with correct inform
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup or restore job fails with Final error: 0xe00084ed - A hardware error has occurred. Article:000037104 Publish: Article URL:http://www.veritas.com/docs/000037104 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-10d-Event-ID-33152-Adamm-Mover-Error-GetDriveInfo/td-p/111430 Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup or restore job fails with Final error: 0xe00084ed - A hardware error has occurred. Error Message Completed status: FailedFinal error: 0xe00084ed - A https://www.veritas.com/support/en_US/article.000037104 hardware error occurred.Final error category: Backup Device Errors. Backup job to Robotic Library fails with error as shown in Figure 1: Figure 1 Also, the following error would be logged in system logs in the event viewer: Event Type: ErrorEvent Source: Backup ExecEvent Category: Devices Event ID: 33152Description:Adamm Mover Error: Unload Rewind Failure! Error = ERROR_IO_DEVICEDrive = "TapeDrive 1"{DC0CA7FF-815E-4CA9-AB0E-5BC8FE5B5396}Media = ""{00000000-0000-0000-0000-000000000000}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(1), ScsiPass(1) Cause If Backup Exec reports the above mentioned error, a hardware level SCSI error is likely to have occurred. Often the Event Viewer will contain additional errors that will help to determine where the problem lies. Solution The following article contains useful information that can help to pinpoint the source of the error: http://www.symantec.com/docs/TECH24414 If the error persists, please contact the hardware vendor for additional assistance. They have utilities and device specific configurations that they can recommend to get the hardware functioning properly, and are the best source of information in determining if a device has failed to the point that it needs to be replaced. NOTE: Even Fiber attached libraries and tape drives communicate using basic SCSI co
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 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 http://www.myeventlog.com/search/show/625 not important very important Description Adamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database = "" Adamm Database backup exec 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 adamm mover error 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.Category: 1 Message: Adamm Mover Error: Unload Rewind Failure!
Error = ERROR_IO_DEVICE
Drive = "HP 2"
2E6FDCE6-51A8-4918-B499-9233C643E041
Media = ""
00000000-0000-0000-0000-000000000000
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
User Information Only an Email address is required for returning users. Email: Name / Alias: Hide Name Solution Your solution: * Additional Links Name: URL: Copyright 2016 Netikus.net. All rights reserved. myeventlog.com and eventsentry.com are part of the netikus.net network .