Backup Exec Error Event Id 33152
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside
Backup Exec 33152 Adamm Mover Error
Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign event id 33152 backup exec 2014 In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest backup exec event id 33152 adamm database 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
Adamm Mover Error Deviceio Backup Exec
: Backup and Recovery : Backup Exec : Backup Exec Error EventID: 33152, 57665, 34113 VOX : Backup and Recovery : Backup Exec : Backup Exec Error EventID: 33152, 57665, 34113 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark
Event Id 33152 Backup Exec 15
Subscribe Printer Friendly Page Backup Exec Error EventID: 33152, 57665, 34113 whitehurstge Level 3 05-13-2013 12:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I am getting the following errors randomly from my backup server. EventID 33152. Below are the details of the message. [4400] 05/10/13 23:25:10 Adamm Mover Error: DeviceIo: 05:00:06:00 - Device error 1117 on "\\.\Tape0", SCSI cmd 08, 1 total errors %2 %3 %4 %5 %6 %7 %8 Adamm Mover Error: Read Failure! 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 an error on a request to read data from media. Error reported: The request could not be performed because of an I/O device error. . For more
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample e_pvl_db_lost_connection report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error:
? Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced community members ADAMM error with BackupExec 11d Lonewolfbw 525 pts. Tags: Thanks! We'll email http://itknowledgeexchange.techtarget.com/itanswers/adamm-error-with-backupexec-11d/ youwhen relevant content isadded and updated. Following Follow Backup Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Backup Exec Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Symantec Backup Exec 11D Good morning, http://www.winsysadminblog.com/2010/08/backupexec-unable-to-read-or-write-to-the-database/ I have just taken over the position of backup operator in my department, so please forgive any seemingly obvious questions. I have received several puzzling errors in the past few days, and hope I can get some answers as backup exec to what is causing them. 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 Pack 4, Hot Fixes 62, 63, 64, 65. Our current configuration is to run a full backup of our main disk array/fileserver on Friday, at 11:00PM. Then, a differential backup will run on M, T, W, Th at 11:00PM. I first noticed a event id 33152 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 PM Completed status: Failed Final error: 0xe00084ec - A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. Final error category: Backup Media Errors For additional information regarding this error refer to link V-79-57344-34028 Backup- \192.168.0.152M: LRDCVOLStorage device "Drive 1" reported an error on a request to write data to media. Error reported: A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. V-79-57344-34028 - A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. Having seen this, I immediately ran the
to read or write to the Database Today when checking one of the servers I manage, I got an error when opening up the BackupExec 12.5 management console. The error was "Unable to read or write to the Database" which I found a bit puzzling. I checked to make sure SQL Server which hosted the BE database was running, and it was. After having a quick look in the Application Event Log, I found an error relating to the issue I was experiencing. Event ID: 33152. Thankfully the fix for this error is quite simple. Open up the Backup Exec Services Manager and click on Stop All Services. Now open up the SQL Server Configuration Manager and restart the instance of SQL Server hosting your Backup Exec database. Once it restarts, return to the Backup Exec Services Manager and click on Start All Services to start them all up again. Once they're up, open the management console. If all went well it should now log you in successfully and show you the current status of your server. Share this post with others:EmailLinkedInFacebookGoogleTwitterRedditMorePrintTumblrPinterest Related 5,219 views Posted on August 31, 2010 by John 3 Comments Posted in BackupExec, Symantec, Windows Server Post navigation Letting Exchange accept Mail from other domains Check to see if your KMS can be contacted 3 thoughts on “BackupExec unable to read or write to the Database” Steve says: A quick Google found this article, breathed a sigh of relief. A nice and easy fix. Thanks. [Reply] Reply October 1, 2010 at 8:12 pm aparadekto says: Hey, I can't view your site properly within Opera, I actually hope you look into fixing this. [Reply]John Reply:November 5th, 2010 at 8:50 amHey aparadekto, the site is displaying fine in the latest version. What version of Opera are you using? [Reply] Reply October 26, 2010 at 8:45 pm Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email. Notify me of new posts by email.Click to cancel replyNotify me of follow-up comments via e-mail Search this blog… Search for: Other PagesAbout Downloads Code Library Useful Documents and Guides OS Deployment with MDT 2013 Subscribe to Blog via Email Enter your email address to subscribe to this bl