Adamm Mover Error Read Failure Backup Exec 12
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
Adamm Mover Error Deviceio Backup Exec
2016 Sign In CommunityCategoryBoardResourcesUsers event id 33152 backup exec turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! 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! Charles_Wieland Level 2 03-03-2005 01:03 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I get this when starting a job. All patches/firmware are up to date.Adamm Mover Error: Read Failure!Error = ERROR_IO_DEVICEDrive = HP LTO Ultrium-2 Tape Drive {F2528203-BAA3-41D9-B0C9-BF71A0831762}Media = {00000006-0000-0000-0000-000000000000}Read Mode: SingleBlock(0), ScsiPass(1)Write Mode: SingleBlock(1), ScsiPass(1) Labels: 10.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 3 Replies Re: Adamm Mover Error: Read Failure! Sheetal_Risbood Level 6 04-04-2005 05:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi,This seems to be a device related issue. Please refer the following Technote for resolving it :How to troubleshoot issues with a Robotic Library or Tape Drive in Backup Exec 9.x and 10.0 http://support.veritas.com/docs/255501Thanks. 0 Kudos Reply Re: Adamm Mover Error: Read Failure! Abhinav_Bindroo Level 6 04-08-2005 12:05 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content In reference to our previous reply to your post, we would request you to update us o
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 A backup or restore job fails with the error "0xe00084ed - A https://vox.veritas.com/t5/Backup-Exec/Adamm-Mover-Error-Read-Failure/td-p/10845 hardware error occurred." Article:000030489 Publish: Article URL:http://www.veritas.com/docs/000030489 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print http://support.veritas.com/docs/280508 Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem A backup or restore job fails with the error "0xe00084ed". Error Message Final error: 0xe00084ed - A hardware error occured. Final error category: Backup Device Errors. UMI Value: V-79-57344-34029 Cause A hardware error occurred caused the job to fail. Check the Application Event log for errors (with Event Source: Backup Exec) that occurred at the time when job failed, for example: Event Type: Error Event Source: Backup Exec Event Category: Devices Event ID: 33152 Description: 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) Solution Check the System Event Log for Event ID 5, 7, 9, 11 or 15. These errors indicate a hardware issue. Microsoft Article on these event Ids : http://support.microsoft.com/kb/154690Refer to the Related
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company http://www.eventid.net/display-eventid-33152-source-Backup%20Exec-eventno-3488-phase-1.htm using just one server, these days that's no longer the case. New computers are added to https://www.experts-exchange.com/questions/27540017/Backup-Exec-A-backup-storage-read-write-error-has-occurred.html the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... backup exec Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error:
Help 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 > Backup Exec - A backup storage read/write error has occurred Want to Advertise Here? Solved Backup Exec - A backup storage read/write error has occurred Posted on 2012-01-17 Storage Software Storage Disaster Recovery 2 Verified Solutions 3 Comments 2,654 Views Last Modified: 2012-05-12 Hi all, Our nightly backup failed last night, with the error of: Completed status: Failed Final error: 0xe00084c7 - A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issuesp . This occurs every couple of weeks; so i clean the drive, and the backup seems to work fine that night, however it shouldn't need cleaning this much? There is also an error in the Event viewer, Adamm Mover Error: Read Failure! Error = ERROR_CRC Drive = "HP DAT 160 USB" {CD2854D1-94D7-4585-AFC0-E