Home > Backup Exec > Backup Exec Adamm Mover Error

Backup Exec Adamm Mover Error


Join Now For immediate help use Live now! The event log is CLEAN, and Adamm.log is clean, and the "Faulting application name: wmiprvse.exe" errors in the event log no longer occur. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Please note, that on Windows Server 2012 R2 with Backup Exec, it's best practice to use the HP driver for the tape drive, and use the generic Microsoft "Unknown Medium Changer" http://gatoisland.com/backup-exec/backup-exec-33152-adamm-mover-error.php

So despite the 33152 errors I am fortunately able to get successful backups and restores, and after the job engine crashes as long as I reset the tape drives, then I'm I will post an update with my results. -There is a chance the registry key is needed for the HP software to co-exist with Backup Exec backups for this configuration. -There Check if you have updated the SCSI firmware. Doing the same in Windows Device Manager and rebooting did not fix the problem. 2.

Adamm Mover Error Backup Exec 2012

Joe_Abraham Level 4 ‎06-06-2005 08:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content The problem is fixed. Thanks Brian Stephen says: 04/27/2016 at 5:36 AM Hi Brian, I've tried both the HP Driver and the Microsoft Driver, I also tried using the HP driver on the Tape Library You may also need to check for problems with cables, termination, or other hardware issues. In case its not 10d, do update to it as it is currently the latest version.

Privacy Policy Site Map Support Terms of Use MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website I don't drop them or toss them about, so I have no concern that it is my tape handling that is at fault. Then, a differential backup will run on M, T, W, Th at 11:00PM. Adamm Mover Error Unload Status Failure Perform a powercycle of the backup server and the tape library.

Next steps for me will be to try the generic drivers and using the registry entries you have listed above. Backup Exec 2014 Adamm Mover Error 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! during a backup process Posted on 2008-05-25 Storage Software Storage 1 Verified Solution 3 Comments 6,777 Views Last Modified: 2013-12-01 I have two devices: - HP ML350 Server with a SCSI Seriously, apply the registry fixes, and uninstall the WBEM providers, then restart the system.

Clean the tape drive, and then try the job again. 0xe00084f4 Backup Exec 2014 Add a key named Storport under Device Parameters (if there is not one there already). 4. Solved Backup Exec stuck in Loading Media state, error 33152 in Windows Event Viewer Posted on 2007-06-19 Storage Software 2 Verified Solutions 5 Comments 10,400 Views Last Modified: 2013-12-01 I'm using 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.

Backup Exec 2014 Adamm Mover Error

Bring the tape library online first and once the status of the library is ready on the LCD or the green light is lit, bring the backup server online. Run "winmsd" and check if there is any port conflict for the SCSI device with the NIC or any other device. Adamm Mover Error Backup Exec 2012 By submitting you agree to receive email from TechTarget and its partners. Backup Exec Error 34113 x 3 Bill Bethel See Veritas TechNote ID: 264273 for details on this error.

This would help us to see the sequence of events. http://gatoisland.com/backup-exec/backup-exec-adamm-mover-error-getdriveinfo-failure.php See EV100262 (How to read the ADAMM.LOG file, and what various errors mean within the log). If this Go to Solution 5 Comments LVL 19 Overall: Level 19 Storage Software 2 Message Assisted Solution by:MrLonandB2007-06-19 I am not in front of my machine now and am Register Hereor login if you are already a member E-mail User Name Password Forgot Password? Backup Exec Error Code E00084f9

bhanu 0 Message Author Comment by:thyet2008-05-26 Thanks for your quick answer, let me check it and i'll tell you about it. In addition, the problem seems to have tapered off as of mid-December. Fixed! http://gatoisland.com/backup-exec/backup-exec-adamm-mover-error-33152.php x 11 Private comment: Subscribers only.

Any suggestions?ThanksDan Labels: 10.x and Earlier Backup and Recovery Backup Exec 1 Kudo Reply 8 Replies Re: Adamm Mover Error? Adamm Mover Error Read Failure We'll send you an e-mail containing your password. 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

Add a key name called BusyRetryCount.

About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Backup Exec 12 VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! Thanks for the help, Brian Stephen says: 04/27/2016 at 6:31 AM Hi Brian, No worries! 🙂 The registry entries WILL have an effect no matter what driver you use. Adamm Mover Error Getdriveinfo Failure We get each one twice.Event Type:WarningEvent Source:Backup ExecEvent Categoryevices Event ID:33152Date:9/21/2006Time:11:36:32 PMUser:N/AComputer:Description:Adamm Mover Error: Unload Status Retry!Error = ERROR_NOT_READYDrive = "DELL 1" {259D9939-E791-4321-9A6E-B9E8558FF3BC}Media = "" {00000000-0000-0000-0000-000000000000}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(1),

These tools detected the same error, which was written in the event viewer errors: Event viewer Error 1: Adamm Mover Error: Write Failure! Then run a backup this should resolve if the issue was with the PCI conflict. I also went in the HP Management Agents in the control panel and disabled anything to do with SCSI, SAS or Tape. Check This Out In some cases they may refuse to provide any support if you take the solution of a supportable configuration.

My initial thought is it's something installed by the latest Proliant Support Pack. Following Follow Backup Thanks! I don't drop them or toss them about, so I have no concern that it is my tape handling that is at fault.

© Copyright 2017 gatoisland.com. All rights reserved.