Adamm Mover Error Read
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 Sign In adamm mover error read failure CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search adamm mover error getdriveinfo failure results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup adamm mover error deviceio and Recovery : Backup Exec : Adamm Mover Error: Read Failure! Backup Exec 12 VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! Backup Exec 12 Subscribe to
Backup Exec 33152 Adamm Mover Error
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 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: Read Failure!Error = 0xE0008121Drive = "HP-1840" {93F0C990-7E8E-4E01-ADDD-B06AA513461B}Media = "104" {C931D92F-FDDC-4B11-8CCA-8E5CE4E578EE}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(1), ScsiPass(1) Labels: 12.x and Earlier Backup and Recovery Backup Exec Drivers 0 Kudos Reply 6 Replies Re: Adamm Mover Error: Read Failure! Backup Exec 12 Ken_Putnam Level 6 Trusted Advisor 04-30-2008 11:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Probably won't have any effect on your error, but if th
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 CommunityCategoryBoardResourcesUsers 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 https://vox.veritas.com/t5/Backup-Exec/Adamm-Mover-Error-Read-Failure-Backup-Exec-12/td-p/186322 and Recovery : Backup Exec : Adamm Mover Error VOX : Backup and Recovery : Backup Exec : Adamm Mover Error 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 568516268 Level 2 03-17-2005 https://vox.veritas.com/t5/Backup-Exec/Adamm-Mover-Error/td-p/13115 12:39 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content My backup job sits on Loading Media.In my server logs I get:Adamm Mover Error: Unload Status Failure!Error = ERROR_NOT_READYDrive = "Seagate 1" {E8773A65-95C0-4667-B122-9667A6BA86F1}Media = "" {00000000-0000-0000-0000-000000000000}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(0), ScsiPass(0) I've read the article on this happening during an Eject but this is during scheduled backups. It is Backup Exec 9.0 on Windows 2000. Labels: 10.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 5 Replies Re: Adamm Mover Error moshker Level 2 04-01-2005 07:15 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I am having the same error message. I think my error is happening even when the backup device (A Dell Powervault 132T) isn't being used. I am still looking into it.A
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 CommunityCategoryBoardResourcesUsers https://vox.veritas.com/t5/Backup-Exec/Adamm-Mover-Error-After-Upgrading-to-SP4-on-Backup-Exec-2012/td-p/651615 turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting http://www.eventid.net/display-eventid-33152-source-Backup%20Exec-eventno-3488-phase-1.htm possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Adamm Mover Error After Upgrading to SP4 on Backup... VOX : Backup and Recovery : Backup Exec : Adamm Mover Error After Upgrading to SP4 on Backup... Subscribe to RSS Feed Mark Topic as adamm mover New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Adamm Mover Error After Upgrading to SP4 on Backup Exec 2012 clovett Level 4 05-13-2014 01:14 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Since upgrading to sp4 on Backup Exec 2012 I am seeing this error on a couple servers pretty adamm mover error frequently. Before sp4 I was not seeing this error. [6484] 05/13/14 15:45:01 Adamm Mover Error: DeviceIo: ndmpSendRequest->connection error to 192.168.3.70:10000, 10054 Labels: 2012 Backing Up Backup and Recovery Backup Exec Patch Troubleshooting Windows Server (2003-2008) 0 Kudos Reply 7 Replies Hello, Check Windows Events lmosla Level 6 05-13-2014 01:29 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, Check Windows Events for System Errors: Event ID's 5,7,9,11,15 These errors point to hardware errors: Event ID 5. This error indicates SCSI parity errors. This error can be caused by a faulty SCSI card or a faulty SCSI termination. for this error contact the hardware's manufacturer. Event ID 7. This error indicates that bad blocks exist and can be caused by an outdated tape device driver, faulty media, or dirty read/write heads on the tape drive. Try updating to the most recent Backup Exec tape device drivers, run a cleaning job, and replace the media with new media, if possible. If the error continues, contact the hardware vendor. Event ID 9. Points to SCSI bus timeouts. To correct this, slow down the SCSI bus and install the most recent SCSI drivers and firmware. & so
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 using just one server, these days that's no longer the case. New computers are added to 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... Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error: