Error 33152 Backup Exec
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 backup exec error 57665 Blogs Groups Vision 2016 Sign In
Backup Exec 33152 Adamm Mover Error
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search backup exec event id 33152 adamm database results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Backup adamm mover error deviceio backup exec Exec Error EventID: 33152, 57665, 34113 VOX : Backup and Recovery : Backup Exec : Backup Exec Error EventID: 33152, 57665, 34113 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 Error EventID: 33152, 57665, 34113 whitehurstge Level
Event Id 33152 Backup Exec 2014
3 ‎05-13-2013 12:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I am getting the following errors randomly from my backup server. EventID 33152. Below are the details of the message. [4400] 05/10/13 23:25:10 Adamm Mover Error: DeviceIo: 05:00:06:00 - Device error 1117 on "\\.\Tape0", SCSI cmd 08, 1 total errors %2 %3 %4 %5 %6 %7 %8 Adamm Mover Error: Read Failure! Error = ERROR_IO_DEVICE Drive = "CERTANCE 0001" {B8B580A5-280E-4954-BE43-F89B217F68A9} Media = "Tape 20" {89E1C0C3-3441-463A-90B7-1D3038BACBA5} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) EventID 57665 Storage device "CERTANCE 0001" reported an error on a request to read data from media. Error reported: The request could not be performed because of an I/O device error. . For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml EventID 34113 Backup Exec Alert: Job Failed (Server: "Server1") (Job: "Daily Backup") Daily Backup -- The job failed with the following
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 event id 33152 backup exec 15 for subscribers Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error adamm mover error: deviceio: ndmpsendrequest->connection error to Description:Adamm Database Error:
E_pvl_db_lost_connection
English: This information is only available to subscribers. An example of English, please! Concepts to understand: What is Adamm? Comments: Anonymous This helped me: EV100273 (Tape Drive Configuration Settings available in Backup Exec). x 7 https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-Error-EventID-33152-57665-34113/td-p/587099 EventID.Net The adamm.log file may contain more verbose information about the source of the problem. See EV100262 (How to read the ADAMM.LOG file, and what various errors mean within the log). x 6 EventID.Net From a support forum: I was getting this event with 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). Event details: Adamm Mover http://www.eventid.net/display-eventid-33152-source-Backup%20Exec-eventno-3488-phase-1.htm Error: GetDriveInfo Failure! Error = ERROR_IO_DEVICE After a lot of effort troubleshooting this, the fault has appeared to be with the one of the on-board SCSI controller channels (the on-board SCSI controller of the Proliant ML350). x 7 EventID.Net In our case, we were getting: Adamm Mover Error: Write Failure! Error = ERROR_IO_DEVICE Drive = "HP 2" It turned out that one of the SCSI terminators on the HP LTO Ultrium-3 tape drive was damaged. x 5 EventID.Net Event details: Adamm Mover Error: GetDriveInfo Failure! Error = ERROR_NOT_READY Drive = "IBM 1" According to a support forum, this message was recorded on a system using an IBM tape drive. Using the IBM DLT-DDS tape drive diagnostics v5.8.3, the user narrowed down the problem to a damaged tape. Once the tape was replaced, the problem disappeared. x 6 Peter Appel In my case following warning came up along with the error event id 11from ADIC1000 after starting an inventory job on a Dell PowerVault 132 connected to a PowerEdge Server with an Adaptec controller Card. Description: Adamm Mover Error: Unload Status Retry! Error = ERROR_NOT_READY Drive = "IBM 1" {53E9358B-3B22-4C44-B872-1065BE6DB73C} Media = "" {00000000-0000-0000-0000-000000000000} Check for bad cable SCSI connection and controller card / mainboard slot. After rebooting the PowerVault first and the
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 Event 33152 (Error) Source: Backup Exec How important is this event? (3 http://itknowledgeexchange.techtarget.com/itanswers/adamm-error-with-backupexec-11d/ 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 backup exec 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: 33152 backup exec 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 ago 2 Comments 7,505 Views Others from Backup Exec 34113 57755 33808 33919 58068 57476 57860 34114 See More IT's easier with? Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced community members ADAMM error with BackupExec 11d Lonewolfbw 525 pts. Tags: Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Backup Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Backup Exec Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Symantec Backup Exec 11D Good morning, I have just taken over the position of backup operator in my department, so please forgive any seemingly obvious questions. I have received several puzzling errors in the past few days, and hope I can get some answers as to what is causing them. First, this is the setup I am using: We have a Dell PowerEdge 2950 as our backup server, using BackupExec 11d (Media Server version 11.0, Rev. 7170) - installed updates Service Pack 4, Hot Fixes 62, 63, 64, 65. Our current configuration is to run a full backup of our main disk array/fileserver on Friday, at 11:00PM. Then, a differential backup will run on M, T, W, Th at 11:00PM. I first noticed a problem when I came in on Saturday and found the following error after the full backup job had 'finished': Job ended: Saturday, August 01, 2009 at 12:28:00 PM Completed status: Failed Final error: 0xe00084ec - A tape read/write error has occurred. 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 issues. Final error category: Backup Media Errors For additional information regarding this error refer to link V-79-57344-34028 Backup- \192.168.0.152M: LRDCVOLStorage device "Drive 1" reported an error on a request to write data to media. Error reported: A tape read/write error has occurred. This is usual