waspsoft.com


Home > Backup Exec > Backup Exec Adamm Mover Error Getdriveinfo Failure

Backup Exec Adamm Mover Error Getdriveinfo Failure

Please contact the person who gave you the link to see if there is an error. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue. I thought I could get telephone support from Veritas/Symantec with this, but not without a cost! Please note: JavaScript is required to post comments. have a peek here

Chris_Campbell Level 2 ‎12-28-2006 07:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi Shweta,Thanks for your standard reply. One lucky winner will receive 500 Connect points! * Take the survey. I need to force restore from specific media, just like I could in BE 2010. Church WordPress Theme by themehall.com HOME | SEARCH | REGISTER RSS | MY ACCOUNT | EMBED RSS | SUPER RSS | Contact Us | Symantec Connect - Backup and Recovery http://www.symantec.com/connect/zh-hant/item-feeds/all/711/feed/all/all/all

See the problems report or the client's logs for more details". Alternately, replace existing drivers with either BE drivers or with latest from the device manufacturer. 4.) Try another SCSI card. 0 LVL 2 Overall: Level 2 Message Expert Comment by:Kalti2006-05-12 x 7 EventID.Net In our case, we were getting: Adamm Mover Error: Write Failure! Probably indicating that there is a loss of comms with the SCSI device Add your comments on this Windows Event!

Windows Event Viewer (Application): Source: Backup Exec Category: None Event ID: 34113 Backup Exec Alert: Job Failed (Server: "S001") (Job: "Eject Drive 00004") Eject Drive 00004 -- The job failed with They have intelligent, helpful support personnel who would rather ship a replacement unit than hold up your client any longer than is necessary. Go ahead and follow the quick steps in this video to learn how to Request Attention to your question. *Log into your Experts Exchange account *Find the question you want to Any ideas?

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. x 7 Dilip Kamlakar See EV100121 (Symantec Article TECH87166). i checked the logs    PolicyAgent7x NBBACKUP.as.pir.com getVirtualMachines failed DefaultExceptionHandler handleException NBSLOpException message : ErrorCode -  25 : cannot connect on sock  

0 0 07/04/13--06:16: Scratch pools Contact us It is a files backup job.

Scroll up to Enable and set to YES. Also in the Event Viewer I get these two messages, they seem fairly generic to me, but maybe the "Aha" for someone reading this?? (I hope so!).Under Application Log -Date: DateTime: Can someone please assist as we are seriously considering moving over to another backup solution vendor as this new version's interface is simply aweful to work with and we are havinng alot of See example of private comment Links: Veritas TechNote ID: 264273, Veritas Support Document ID: 280508, Veritas Support Document ID: 270568 Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue

  1. 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!
  2. And also why it costs to obtain support for such a Product?
  3. All they want to do is tell you to change hardware - the drive, cable, SCSI card, etc etc. (And quite often, they are right - it is often hardware.)Frankly, you'll
  4. Help Desk » Inventory » Monitor » Community » MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups
  5. Labels: 10.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 6 Replies Re: Backup Exec 10d - Event ID 33152 - Adamm Mover Error: GetDriveInfo Failure!
  6. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
  7. PLEASE HELP!
  8. that is ...backup should complete within 2 hours ..but after 12 hours and more ...the data transfer is still happening....  Could you please suggest what we need to check to resolve
  9. See the problems report or the client's logs for more details.   ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 0 0 07/05/13--04:12: Backup Exec 2012 Trial Agent Contact us about this article I need a solution Hi
  10. Surely you don't have to 'buy' a support contract!

What happened to the email support or the telephone support or even just the good old Veritas!I await your response,Thanks and Regards,Chris 0 Kudos Reply Re: Backup Exec 10d - Event Error reported: The I/O bus was reset. Description: Adamm Mover Error: Unload Status Retry! Still anybody got any suggestions? 0 Kudos Reply Re: Backup Exec 10d - Event ID 33152 - Adamm Mover Error: GetDriveInfo Failure!

Error = ERROR_IO_DEVICE Drive = "HP 2" {46DD4729-DF6F-4033-B4F0-400779D29D63} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(0), ScsiPass(0) Source: Backup Exec http://waspsoft.com/backup-exec/backup-exec-33152-adamm-mover-error.html The Server is a HP DL 380P Gen8 with 2 * 6 Core CPU's. Join the community Back I agree Powerful tools you need, all for free. Privacy Policy Site Map Support Terms of Use Symantec Connect Entire Site Search Tips Home Community:All Communities Overview Login or Register to participate English English 简体中文 Français Deutsch 日本語 Español Help

Veritas does not guarantee the accuracy regarding the completeness of the translation. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. No Yes How can we make this article more helpful? http://waspsoft.com/backup-exec/backup-exec-adamm-mover-error-33152.html Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

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. When we try to make a SDR Restore to another Server (HP ML350 G6) we got an error when it is restoring the System State : "A Failure occured creating a Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc.

Are you an IT Pro?

User canceled a Physical Volume Library operation. 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 Errors Click an error below to locate it in the job log V-79-57344-33039 - Error - Mount failed. It chills me everytime I update the OS on my phone, (http://www.experts-exchange.com/articles/18084/Upgrading-to-Android-5-0-Lollipop.html) because one time I did this and I essentially had a bricked … Android Smartphone Programming Cell Phones Operating

We have multiple customers which run Backup Exec 2012  and we are expierencing frequent backup failures using Backup Exec 2012 on SBS2011 with VSS problems. Join our community for more solutions or to ask questions. 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 http://waspsoft.com/backup-exec/backup-exec-adamm-mover-error-deviceio.html The Backup Exec 2012 all the while is working fine, until the day when I renew my Backup Exec 2012 license and I noticed that there's additional column indicating I'm using

Chris_Campbell Level 2 ‎12-19-2006 06:14 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Ok, going to order a separate Do I need to set anything on the Remote Agent on the client? 2) I ran the same full backup to dedupe storage job two times in a roll. After rebooting the PowerVault first and thereafter the server, the error was gone. Backup Exec 2012 Rev 1798 Service Pack 4 (TECH212772).   Applies ToBackup Exec 2012 SP2 Enterprise Support Option Terms of use for this information are found in Legal Notices.

Related Articles

x 3 Bill Bethel See Veritas TechNote ID: 264273 for details on this error. The 1st job took 11 min and 2nd job took 18 min. Access Denied Confidential!The information on the page you requested has been marked private.To view the page, you will need to log in or register for Symantec Connect.If you are already logged but i noticed after the upgrade, my users data alone takes about 3 taped alone to run a full weekly backup.

It is possible that updates have been made to the original version after this document was translated and published. Error = ERROR_INVALID_HANDLE Drive = "HP 2" {46DD4729-DF6F-4033-B4F0-400779D29D63} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(0), ScsiPass(0) Source: Backup Exec I already checked the Hardware Compatibility list for this device, its compatible. Need to get the client B to recover the data over SAN.   Please help.

0 0 07/04/13--05:38: 2 out of 4 tape drives offline Contact us about this article