Adamm Mover Error Device
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 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest adamm mover error deviceio helps you quickly narrow down your search results by suggesting possible matches as you type. adamm mover error read failure Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : ADAMM mover error and adamm mover error getdriveinfo failure low compression ratio, relat... VOX : Backup and Recovery : Backup Exec : ADAMM mover error and low compression ratio, relat... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to backup exec 33152 adamm mover error the Top Bookmark Subscribe Printer Friendly Page ADAMM mover error and low compression ratio, related? YonatanC Level 5 12-03-2014 07:03 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, About 3 weeks ago we had a malfunction in our IBM TS3200 tape library (a small plastic piece broke inside and the robot was stuck). In order to fix this the technician opened
Adamm Mover Error Deviceio Backup Exec
the entire library case and removed the obstacle. Soon after that I noticed that Drive 1 (out of four installed) is not compressing as always - it dropped from 3:1 on the daily backups to 1.6:1 (same data). I also noticed a sequence of 4 events in the eventlog that occure twice a day at the same time: [2872] 12/02/14 18:14:29 Adamm Mover Error: DeviceIo: 01:00:02:00 - Device error 1117 on "\\.\Tape1", SCSI cmd 0a, 1 total errors [2872] 12/02/14 18:19:29 Adamm Mover Error: DeviceIo: 00:00:02:00 - Retry Logic: Retry logic was engaged on device: IBM ULT3580-HH5 [2872] 12/02/14 18:19:29 Adamm Mover Error: DeviceIo: 01:00:02:00 - Refresh handle on "\\.\Tape1", SCSI cmd 00, new handle 1098, error 0 [2872] 12/02/14 18:19:39 Adamm Mover Error: DeviceIo: 00:00:02:00 - Retry Logic: Original settings restored on device: IBM ULT3580-HH5 The send time it happens is around 23:30 I checked again and again and there are no backups that start or end at these times (there are backups in action during that time). We're using the Symantec drivers version 5.1.37.0 from 12.02.2008 for the tapes. All jobs are defined with hardware compression. I've tried replacing the fabric cable, restart the library and restart the BE server but same results. Tonight I'll try to use software compression for this tape and see if t
making me rip my hair apart for some time… And a fix for you experiencing the same.
Event Id 33152
Equipment: HP Proliant DL360 G6 Server (with a P800 Controller) running Server 2012 R2 and Backup Exec 2014 HP MSL-2024 Tape Library with a single HP SAS LTO-6 Tape Drive Symptoms: -After a clean restart, a backup job completes successfully. Subsequent jobs fail until server or services restarted. -While the initial backup does complete, errors/warnings can https://vox.veritas.com/t5/Backup-Exec/ADAMM-mover-error-and-low-compression-ratio-related/td-p/679211 be seen in the adamm.log and the Event Viewer even when successful. -Subsequent backups failing report that the device is offline. The Windows Device Manager reports everything is fine. -Windows Server itself does not report any device errors whatsoever. Observations: [5648] 03/05/16 07:50:46 Adamm Mover Error: DeviceIo: 03:07:00:00 - Device error 1167 on "\\.\Tape0", SCSI cmd 0a, 1 http://www.stephenwagner.com/?p=1011 total errors [5648] 03/05/16 07:55:46 Adamm Mover Error: DeviceIo: 03:07:00:00 - Refresh handle on "\\.\Tape0", SCSI cmd 00, new handle 214, error 0 [5648] 03/05/16 07:55:46 Adamm Mover Error: DeviceIo: 00:00:00:00 - Retry Logic: Retry logic was engaged on device: HP Ultrium 6-SCSI [5648] 03/05/16 07:55:46 Adamm Mover Error: DeviceIo: 00:00:00:00 - Retry Logic: Original settings restored on device: HP Ultrium 6-SCSI Event ID 58053 Backup Exec Alert: Storage Error (Server: "WhatsMySRVRname") The device state has been set to offline because the device attached to the computer is not responding. Ensure that the drive hardware is turned on and is properly cabled. After you correct the problem, right-click the device, and then click Offline to clear the check mark and bring the device online. [09968] 03/05/16 01:42:08.426 DeviceIo: 03:07:00:00 - Refresh handle on "\\.\Tape0", SCSI cmd 17, new handle ffffffff, error 32 [09968] 03/05/16 01:42:08.426 DeviceIo: 03:07:00:00 - Refresh handle on "\\.\Tape0", SCSI cmd 1a, new handle ffffffff, error 32 [09968] 03/05/16 01:22:07.867 PvlSession::DismountMedia( 0, 0, 0 ) Job = {JOBHEXNUMBERZZZZZZ} "ServerBackup-Full" Changer =
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 https://www.experts-exchange.com/questions/23431640/Adamm-Mover-Error-Write-Failure-during-a-backup-process.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Adamm Mover Error: Write Failure! during a backup process http://symantec849.rssing.com/chan-4694894/all_p221.html Want to Advertise Here? Solved Adamm Mover Error: Write Failure! during a backup process Posted on 2008-05-25 Storage Software Storage 1 Verified Solution 3 Comments 6,761 Views Last Modified: 2013-12-01 I have two devices: - adamm mover HP ML350 Server with a SCSI Adapter connected via PCI: LSI Adapter, Ultra320 SCSI 2000 Series. - HP LTO Ultrium-3 drive with a 1x8 G2 autoloader (x86based) connected to the SCSI Adapter.. Windows 2003 R2 Server installed with the last drivers of the tape installed. It seems installed correctly due to the SCSI adapter, plus the tape drive and the medium changers are detected fine in the device manager. At adamm mover error least without errors. Using the Backup Exec utility to do the backups write errors were detected. After that i could execute the HP StorageWorks Library and Tape Tools to check if the problem is in the device or in backup exec drivers. These tools detected the same error, which was written in the event viewer errors: Event viewer Error 1: Adamm Mover Error: Write Failure! Error = ERROR_IO_DEVICE Drive = "HP 1" {F4F2A1B4-8FF5-4C50-8842-D
or contact us about this channel Embed this content in your HTML Search confirm cancel Report adult content: click to rate: Account: (login) More Channels Showcase RSS Channel Showcase 1408440 RSS Channel Showcase 5269039 RSS Channel Showcase 5296096 RSS Channel Showcase 7164333 Channel Catalog Subsection Catalog Articles on this Page (showing articles 4401 to 4420 of 7148) 10/06/14--07:16: _Trouble establishin... 10/06/14--07:21: _Event id 33152 10/06/14--08:06: _Backup Exec 2014 SP... 10/06/14--09:20: _Adding Linux VMs 10/06/14--09:51: _relationship of com... 10/06/14--10:59: _Change Dedupe Maint... 10/06/14--11:25: _Backup Exec 2014 & ... 10/06/14--13:09: _B2D subfolders 10/07/14--01:29: _Remote Agent: The p... 10/07/14--05:41: _Backup Exec 2014 no... 10/07/14--06:12: _View changes to job... 10/07/14--06:31: _Restoring data on L... 10/07/14--06:46: _Upgraded to 2014 fr... 10/07/14--13:35: _On site full required? 10/07/14--18:30: _Can a backup-to-dis... 10/07/14--19:00: _Directory not found 10/08/14--06:34: _Backing up Synology... 10/08/14--06:37: _Create backup job f... 10/08/14--07:01: _Exchange Daten Wied... 10/08/14--07:06: _CentOs 5.11 - RALUS... (showing articles 4401 to 4420 of 7148) Browse the Latest Snapshot Browsing All Articles (7148 Articles) Live Browser older | 1 | .... | 218 | 219 | 220 | (Page 221) | 222 | 223 | 224 | .... | 358 | newer 0 0 10/06/14--07:16: Trouble establishing trust between BUE server and RHEL 6.5 agent after upgrading to BUE 2014 Contact us about this article I need a solution I have Backup Exec 2014 running on a Windows 2008 Server, and I currently have the BUE client installed on three different Windows servers, which are communicating properlyw ith the BUE server. However, I'm having problems establishing trust between my RHEL 6.5 server and the Backup Exec server. RALUS installed without a problem on my RHEL 6.5 server and I can ping the RHEL server's dedicated network interface from the BUE server. However, when I attempt to add the RHEL 6.5 server to the BUE server list, the "inserting server..." window pops up, the progress wheel turns, but nothing ever happens. After 30-45 minutes of waiting (the process doesn't time out) I have to go through the disconnect routine—clicking the "Disconnect" button and then confirming my decision—twice before the process completes. Once the connection/trust establishment process fails, my RHEL server is listed with a status of "Connection not establishe