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 backup exec event id 33152 adamm database Vision 2016 Developers Blogs Groups Vision 2016 Sign In adamm mover error deviceio backup exec CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly event id 33152 backup exec 2014 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
Adamm Mover Error: Deviceio: Ndmpsendrequest->connection Error To
: Backup Exec : Backup Exec 10d - Event ID 33152 - 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 event id 33152 backup exec 15 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
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? e_pvl_db_lost_connection (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 https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-10d-Event-ID-33152-Adamm-Mover-Error-GetDriveInfo/td-p/111430 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: https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 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,449 Views Others from Backup Exec 34113 57755 33808 33919 58068 57476 57860 34114 See More IT's easier with help Join millions of IT pros working smarter and faster together COMMUNITY STATS 200K+ 10K+ 5M+ Product Reviews How-tos & Scripts Posts Connect with OR Join - It's Free Have an account? Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join milli? 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. http://itknowledgeexchange.techtarget.com/itanswers/adamm-error-with-backupexec-11d/ Tags: Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Backup Thanks! https://www.experts-exchange.com/questions/21846754/Backup-Exec-I-O-Device-Errors.html 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 backup exec 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 adamm mover error 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 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. V-79-57344-34028 - 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 per
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 I/O Device Errors Want to Advertise Here? Solved Backup Exec I/O Device Errors Posted on 2006-05-11 Operating Systems 1 Verified Solution 8 Comments 21,039 Views Last Modified: 2012-01-19 Recently I have installed Veritas Backup Exec (10.0 Rev 5520) onto an IBM xSeries 236 (Windows 2003 Standard Server), and installed an Ultrium 1 tape device (FRU 39M5635), which had previously been used in a xSeries 235 (Windows 2000 Standard). The tape drive is using the onboard SCSI interface/controller (Controller 1 / SCSI Channel 1). The HDD's use Controller 1 / SCSI Channel 2 and are configured as RAID1 2x 73GB(Array A), RAID 5 3x 140GB(Array B), plus a 140GB hotspare Since the reconfiguration, there have been numerous Backup Exec and Event Viewer device errors, as listed below: Backup Exec Job Errors: Job Log for Daily Job Information Job server: S001 Job name: Daily Job started: 11 May 2006 at 12:59:19 Job type: Backup Job Log: BEX_S001_00072.xml Drive and media mount requested: 11/05/2006 12:59:19 V-79-57344-33039 - Error - Mount failed. User canceled a Physical Volume Library operation. Job Completion Status Job ended: 11 May 2006 at 13:08:01 Completed status: Canceled The job was canceled by user RACKLINE\_serviceDA. Errors Click an error below to locate it in the job log V-79-57344-33039 - Error - Mount failed. User canceled a Physical Volume Library operation. Job ended: 11 May 2006 at 12:40:18 Completed status: Failed Final error: 0xe00084eb - The storage device was reset. Final error category: Backup Device Errors For additional information regarding this error refer to link V-79-57344-34027 Errors Click an error below to locate it in the job log VerifyStorage device "HP 2" reported an error on a request to read data from media. Error reported: The I/O bus was reset. V-79-57344-34027 - The storage device was r