Backup Exec Error End Marker Unreadable
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision
Backup Exec 2012 Tape End Marker Unreadable
2016 Sign In backup exec 12 end marker unreadable CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches backup exec 11d end marker unreadable as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Tape status: 'Not Appendable (End marker unreadabl...
End Marker Unreadable Backup Exec 2010
VOX : Backup and Recovery : Backup Exec : Tape status: 'Not Appendable (End marker unreadabl... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Tape status: 'Not Appendable (End marker unreadable)' and Duplication failure Kvothe Level 2 09-11-2013 07:17 AM Options Mark
End Marker Unreadable Backup Exec 2014
as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, We have a Quantum Superloader 3 tape library (LTO 6) running Backup Exec 2012 (SP2) Windows Server 2008 R2 SP1 Incremental jobs for 34 servers run nightly at 11pm to the incremental media set (infinite - Allow append). These backups are consitent in that they backup successfully up until the following point of failure: After approximately one month of usage, I noticed that one of the incremental tapes had become 'Not Appendable (End marker unreadable)' Checking through the forums lead me to investigate further and work through the following: check backup exec job engine service (bengine.exe) around time media failed (couldn't locate any instances of the service state starting / stopping that could have caused this) run live update (SP2 Installed) check memory errors check scsi controller drivers to address soft write errors (also run the cleaning tape job) check windows update firmware on tapedrive sy
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners veritas end marker unreadable Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign
Backup Exec Media Not Appendable
In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest not appendable media full backup exec 2012 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 https://vox.veritas.com/t5/Backup-Exec/Tape-status-Not-Appendable-End-marker-unreadable-and-Duplication/td-p/633003 : Backup and Recovery : Backup Exec : getting Not Appendable (End marker unreadable) VOX : Backup and Recovery : Backup Exec : getting Not Appendable (End marker unreadable) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe https://vox.veritas.com/t5/Backup-Exec/getting-Not-Appendable-End-marker-unreadable/td-p/225912 Printer Friendly Page Solved! Go to Solution getting Not Appendable (End marker unreadable) rblumenthal0 Level 4 03-16-2009 12:42 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have Backup Exec 11d. Ijust ran an inventory on some of the tapes in our library (we have a Dell Powervault Tl2000) and 4 of them came back with 'Not appendable (end marker unreadable)'. what could be causing this? The media sets are configured to inifinte - allow appendable. Thanks Solved! Go to Solution. Labels: 11.x and Earlier Backup and Recovery Backup Exec Basics Configuring 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! RE: getting Not Appendable (End marker unreadable) Ken_Putnam Level 6 Trusted Advisor 03-16-2009 12:52 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Cont
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help https://www.experts-exchange.com/questions/23612287/Backup-job-fails-with-End-marker-unreadable.html Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup job fails with End marker unreadable. Want to Advertise http://arstechnica.com/civis/viewtopic.php?t=83301 Here? Solved Backup job fails with End marker unreadable. Posted on 2008-07-31 Storage Software Windows Server 2003 1 Verified Solution 3 Comments 5,296 Views Last Modified: 2013-12-01 I have a PowerVault 114T with a Ultrium backup exec 3 LTO tape drive in it. Every few weeks the backup job will hang and the only error I can find is END MARKER UNREADABLE in the "Append until". Yes, all the settings for the library are correct. It works most weeks. The tape still has a lot of room left also. I change the tape every week, cleaned the drive, changed the SCSI cable. I have not changed the SCSI end marker unreadable card out yet which I read someone else that it fixed it. I tried to upgrade the firmware on the tape drive but can not find it. The one I thought it was, was not the right one. Does anyone know what causes this error and where I can get the firmware upgrade for this drive (I can't find it on dell). Last resort will be to replace the SCSI card. 0 Question by:realslimshaddy Facebook Twitter LinkedIn Google LVL 23 Active 3 days ago Best Solution byIamthecreator This happens when the job engine or the beremote service terminates before backup exec is able to write the END MARKER which is written at the very end of the backup job.The only option now to use the Go to Solution 3 Comments LVL 23 Overall: Level 23 Storage Software 20 Windows Server 2003 6 Message Active 3 days ago Accepted Solution by:Iamthecreator2008-08-01 This happens when the job engine or the beremote service terminates before backup exec is able to write the END MARKER which is written at the very end of the backup job.The only option now to use the tape is to QUICK ERASE it as to why its happening you will need to investigate into why the JOB
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries Help with Symantec Backup Exec 12 36 posts MCSE_in_training Ars Scholae Palatinae Registered: Jan 30, 2008Posts: 631 Posted: Fri Jun 12, 2009 11:38 am Up until recently Backup Exec has worked pretty well. Last week I had to reboot the server. No backup job has run successfully since then!When the machine first boots, the backup exec job engine service isn't running. I manually start it. It starts fine. I can then start a backup job, it runs for about 25 minutes or so then the status changes to "communication stalled". If I wait long enough it errors would with a communication problem with the media services. By the time that happens the backup exec job engine service has stopped again. This is the only error in the event log:Faulting application bengine.exe, version 12.0.1364.134, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.I've re-applied the settings for the user the service runs as. No change. I've tried running Live Update, it finds 2 updates and downloads them but it won't actually install them. Any ideas?I would have noticed this sooner but I've been busy getting our new file server up and running. Luckily I can run backups on the critical servers via NTBackup and dump them to the brand new empty file server. But that is a short term fix only. BulkRate Ars Schola