In this case, you'd need to upgrade to a version that supports this.BE 2010 R3 would work well. In most of the cases I have seen, the problem is connected to a permissions issue related to the account being used to run the service. Jalapeno Jan 30, 2011 Eric-t Other, 501-1000 Employees Same event is logged when a open file (for example a PST file) couldn't be backupped ("Corrupt data encountered"); and same event is Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Source
Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. No Yes Did this article save you the trouble of contacting technical support? RE: Error The device, \Device\Tape0, is not ready for access yet Malcolmf (IS/IT--Management) 28 Oct 02 03:59 I am having the same problem with a Compaq ML 370 G2 Server and Create/Manage Case QUESTIONS?
If that doesn't work, check the Application and System logs in the Event Viewer. Then start the media server and perform additional testing. 7. If the device is connected to a fiber switch, reboot the switch and resume testing. 6.
This error occurs multiple times and refers to many different files and folders. Backup Exec Error 1053: The service did not respond to the Start or Control Request in a timely fashion This is one of the Backup Exec errors that can be caused For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlDec 29, 2009 Backup Exec Alert: Job Failed (Server: "SIFILE01") (Job: "Daglig Backup") Daglig Backup -- The job failed with the following error: Event Id 11 See the job log for details.
It occurs when one or more Backup Exec services will not start. Backup Exec Device Offline Make sure that it is running under the Local System account. - If the issue is unresolved, please go to Tools, Options, Network Tab, select the "Use any available Network adapter" the server only has a single hard drive in it so I am not sure what this error is referring to) Event ID 3. Everytime.I have to disable the DLT thur Backup Exec scsi configuration and then re enable it to get it back on line.As soon as the scheduled job starts up at night
Thank You! The following information was included with the event: \Device\RaidPort1 Event ID 57. Disconnect the tape hardware (drive/library) from the server and reboot the server. If the problem persists, try a different tape.
I tried loading Ankur_Dubey Level 3 05-08-2012 01:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks Craig. http://gatoisland.com/backup-exec/backup-exec-alert-device-error.php Four data copy management misconceptions that affect your business What are some flat backup misconceptions? Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. This issue may occur after the upgrade. 2 . Event 11
Still no luck ;( 0 Kudos Reply Mmm...IBM have a tape testing CraigV Moderator Partner Trusted Advisor Accredited 05-08-2012 02:14 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Has this drive always given you issues, or has it worked before? By joining you are opting in to receive e-mail. have a peek here Login Join Community Windows Events Backup Exec Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event
This is usually caused by dirty read/write heads in the tape drive. Four data copy management misconceptions that affect your business Data protection methods: Mounting backups vs. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlMar 29, 2012 Backup Exec Alert: Job Failed (Server: "myServer") (Job: "myServer-VS1 - HyperV - myServer-sql3 - SnapShots") myServer-VS1 - HyperV - myServer-sql3
I have gone through the files/folders randomly and checked that the backup user has permissions on the files - they have all checked out fine. If the error continues, contact the hardware vendor. Event ID 9: This error usually occurs when the SCSI bus resets itself, or when the SCSI hardware does not respond quickly. Review the resource credentials for the job, and then run the job again. No Yes Did this article save you the trouble of contacting technical support?
This can be the result of SCSI host adapter configuration issues or other problems. Check if is there any tape stuck in the Tape Drive of Tape library. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlJun 13, 2014 Backup Exec Alert: Job Failed (Server: "WHP1") (Job: "Catalog 00004") Catalog 00004 -- The job failed with the following error: Check This Out For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml May 09, 2012 Backup Exec Alert: Job Failed (Server: "YORK") (Job: "Backup Userdata to Tape (Tue,Thu)") Backup Userdata to Tape (Tue,Thu) -- The
After backing up the system, open the Registry Editor and navigate through the registry tree to HKEY_CLASSES_ROOT\TypeLib. Violin flash upgrade: Is it a high note or swan song? If Backup job does not work on B2D also then perform following steps: 1. To verify if this service is stopped go to Start | Run | Services.msc - Start the Service.