Home > Backup Exec > Backup Exec Adamm Mover Error 33152

Backup Exec Adamm Mover Error 33152

Contents

I thought I could get telephone support from Veritas/Symantec with this, but not without a cost! Errors Click an error below to locate it in the job log V-79-57344-33039 - Error - Mount failed. To install the necessary roles, go to Server Manager, and select Add Roles and Featu… Windows Server 2012 Storage Software Storage Advertise Here 846 members asked questions and received personalized solutions Browse by Topic AS/400 Business Intelligence Career Development Channel Cloud Computing Compliance Consumerization Content Management CRM Data Management Database DataCenter Desktop Management Development Email Administration Hardware IT Strategy Linux Lotus Domino http://gatoisland.com/backup-exec/backup-exec-33152-adamm-mover-error.php

Following Share this item with your network: MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing http://www.bacula.org/en/ (Replay from BW) Update on this situation: Over time, I've been monitoring this continued problem, and after repeatedly dealing with Quantum (the provider of both the autoloader and the tapes), Concepts to understand: What is Adamm? But - since turning on encryption - the job engine crashes on my weekend jobs several hours into the backups.

Backup Exec Event Id 33152 Adamm Database

There were signs of internal damage (and this was on freshly purchased tapes.) Quantum tried to tell me to go read their tape handling documentation, but I literally take these tapes However, I found the following three errors in Windows Event Viewer on the backup server, in the Application log: Error #1) Date: 8/1/2009 Time: 1:16:58PM Type: Warning User: N/A Computer: BackupServer x 3 EventID.Net See "Veritas Support Document ID: 270568" for information about this event. x 11 Private comment: Subscribers only.

  1. x 5 Peter Van Gils Our IBM tape library often gave hardware errors, which would also show in the event log: twice a warning and once an error.
  2. Error = ERROR_NOT_READY Drive = "Drive 1" {A2B872F4-4681-4D45-B6BB-4FDE132C962E} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Error #3) Date: 8/1/2009 Time: 1:17:28PM Type: Error User: N/A Computer:
  3. Don't know if this is useful for anyone...? - Capturing to C:\Program Files\VERITAS\Backup Exec\NT\logs\SGMon.logbeserver: 12/18/06 12:20:27 20 Auto Clear Alerts Querybeserver: 12/18/06 12:20:40 -1 SQLLog(1930):AgeSession m_threadMap: SessionThreadID:350, CurrentThreadID:1100beserver: 12/18/06 12:21:28 20
  4. If this doesn't work you need to check your SCSI cable and make sure you don't have a bent pin in the connector.
  5. Stats Reported 7 years ago 2 Comments 7,482 Views Others from Backup Exec 34113 57755 33808 33919 58068 57476 57860 34114 See More IT's easier with help Join millions of IT
  6. I don't drop them or toss them about, so I have no concern that it is my tape handling that is at fault.
  7. http://www.bacula.org/en/ (Replay from BW) Update on this situation: Over time, I've been monitoring this continued problem, and after repeatedly dealing with Quantum (the provider of both the autoloader and the tapes),
  8. Suggested Solutions Title # Comments Views Activity Could you point the better approach on PostgreSQL backup/ restore ? 4 35 113d MSL2024 - Mix Tape Drives 9 72 81d ProCurve ACL
  9. Then, a differential backup will run on M, T, W, Th at 11:00PM.
  10. Afterwards, the errors didn't reoccur anymore.

I have(1) VXA320 1U x10 Exabyte autoloader (current firmware)(1) installed VXA3 packet loader (current firmware)BU Exec 11D (all current patches / fixes)Adaptec 39160 Dual channel scsi cont (also with updated / We'll email you when relevant content is added and updated. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Adamm Mover Error: Deviceio: Ndmpsendrequest->connection Error To Try shutting down the tape device first.

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 Also, I/O errors and tape errors can be caused by drives that haven't been cleaned in awhile. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Power on the server.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Backup Exec Error EventID: 33152, 57665, 34113 VOX : Backup and Recovery : E_pvl_db_lost_connection In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. Thanks people. 0 Message Expert Comment by:ricorguy2008-10-23 Here's what I have done in the past (with backup exec 9 & 10) when I've gottent this. 1) Stop and disable all I'm switching to Bacula.

Adamm Mover Error Deviceio Backup Exec

Have also considered the following (which you guys may or may not have thought of all ready):Removable storage service: Unless you're using nativeNT B/U, this needs to be stopped and disabledBad These are: Message 1: -------------- Event Type: Warning Event Source: Backup Exec Event Category: Devices Event ID: 33152 Date: 20/6/07 Time: 11:09:02 User: N/A Computer: BNEFILES1 Description: Adamm Mover Error: Unload Backup Exec Event Id 33152 Adamm Database This article seems to suggest not to have any of the boxes checked if the drive is attached locally via SCSI interface, which this drive is.I'll let you know how tonight's Event Id 33152 Backup Exec 2014 Make sure that you select the write test and that you have stopped all the BE services beforehand. 0 Kudos Reply I have a Dell PowerVault 114T whitehurstge Level 3 ‎05-14-2013

I had some adpu160m in the eventlog and at 16:47 they dissappeared again 17:27 they re-appeared. http://gatoisland.com/backup-exec/backup-exec-adamm-mover-error-getdriveinfo-failure.php Click here it's easy and free. Then stop all the backup exec svcs. Submit your e-mail address below. Event Id 33152 Backup Exec 15

Anyway, you can experience a scsi timeout because of this.bottom line - I'm getting much better and more effective support from the HW mfg than I ever get from Symantec. Trying running the backup job... 0 LVL 9 Overall: Level 9 Storage Software 3 Message Accepted Solution by:iCoreKC2007-06-19 Here is what I do in these cases. Rob_Pelletier Level 4 ‎12-29-2006 12:34 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I sympathize.I won't recommend BackupExec any have a peek here Error reported: The request could not be performed because of an I/O device error. .

We had a bit more luck in that we were able to back up , but restores never worked. Following Follow Backup Exec Thanks! 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

the job just keeps running, and running, and running doesn't actually stop unless I stop it myself.

I'm getting 33152 events. Still anybody got any suggestions? 0 Kudos Reply Re: Backup Exec 10d - Event ID 33152 - Adamm Mover Error: GetDriveInfo Failure! Featured Post How your wiki can always stay up-to-date Promoted by Quip, Inc Quip doubles as a “living” wiki and a project management tool that evolves with your organization. I'm seeing the exact same types of errors as the two of you.

Backup Exec 12 VOX : Backup and Recovery : Backup Exec : Adamm Mover Error: Read Failure! If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. 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 Check This Out Join the community Back I agree Powerful tools you need, all for free.

For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml These errors happen at randowm times and there seems to be no rhyme to when they might happen. Error = ERROR_NOT_READY Drive = "D51 Drive" {2FF4F000-7C59-4E09-A09F-FBA9A0C9E9F9} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) ----------- Message 2 See EV100262 (How to read the ADAMM.LOG file, and what various errors mean within the log). Anyway.....

In the Windows event log, I get a set of three messages every few minutes. What a POS. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml EventID 34113 Backup Exec Alert: Job Failed (Server: "Server1") (Job: "Daily Backup") Daily Backup -- The job failed with the following error: The x 3 Bill Bethel See Veritas TechNote ID: 264273 for details on this error.

Join our community for more solutions or to ask questions. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By submitting you agree to receive email from TechTarget and its partners. Error = ERROR_IO_DEVICE Drive = "CERTANCE 0001" {B8B580A5-280E-4954-BE43-F89B217F68A9} Media = "Tape 20" {89E1C0C3-3441-463A-90B7-1D3038BACBA5} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) EventID 57665 Storage device "CERTANCE 0001" reported

I'm switching to Bacula. 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

© Copyright 2017 gatoisland.com. All rights reserved.