Final error: 0xe00084ec - A backup storage read/write error has occurred.
Good morning, I recently gotten this error everytime my schedule job run on Symantec Backup Exec 2010 Final error: 0xe00084ec - A backup storage read/write error has occurred. If the storage is tape based, 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. If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations. Final error category: Backup Media Errors Tried to reinstall backup exec and repluging all cable but still fail. Any solution or idea?7.9KViews0likes15CommentsBIOS is not ACPI compatible
Hello all, I've got a problem with the backup exec system recovery disc 2010. When I try to boot with the CD (on USB CD Drive) or USB Key, I have this message : Status: 0xc0000225 Info : Windows failed to load beacause the firmware (BIOS) is not ACPI compatible. A kb on symantec website tells to change the option in the BIOS but I don't have any option about ACPI. http://www.symantec.com/business/support/index?page=content&id=TECH57513 I found that the CD BESR is a Windows PE 2.5 (Vista). But the hardware which I try to restore isn't compatible with vista. Is there any solution for this problem like a Windows PE XP ? Thanks.4.2KViews1like12CommentsInformation Store shows 0kb, can't backup Exchange 2010 with BE 2010 R2
Hello. I've read several technotes about this, and threads, and haven't found the answer yet. I have moved Backup Exec 2010 R2 to a WIndows Server 2008 R2 x64 machine so that I could backup my Exchange 2010. My Exchange 2010 server is a VM within ESXi 4.1, for reference, but the RAWS is installed on the Exchange 2010 VM, and so is VMWare Tools. I have installed the Exchange 2010 Management tools on the new BE Media server. The Exchange 2010 server already has the MAPI/CDO 1.2.1 installed. I am getting this when trying to choose selections for doing a GRT backup of the Exchange 2010 server...notice that the Information Store shows 0kb for both the Mailbox Database and the Public Folder Database: I found out that I did NOT have the Backup Exec system account set in the Local Admin group on the Ex2010 server, and did NOT have that account in the "Organization Management" role group. I fixed both things, and verified that the account is a Local Admin on the mail server and is in the "Organization Management" role group. Yet, I still can't get the Information Store to populate and backup. I tried just selecting the Information Store here anyways thinking maybe it was a glitch, and when running the backup, I received this error: Can anyone tell me what I'm doing wrong and how to get the Exchange 2010 GRT backup to work?Solved3.8KViews0likes22CommentsHow get Backup Exec to delete snapshots?
With Advanced Open File option turned on in Backup Exec, snapshots are created for VMWare virtual machines. These snapshots are not deleted after the backup completes, however. How can I get these snapshots to automatically delete?Solved3.3KViews0likes4CommentsWho supports MySymantec website?
Under Products and Maintenance no current products are listed only products from 2007 also i get errors when trying to create case Submit the Case "Your attempt to submit a case to Symantec has failed due to an invalid Product/Version. You can check the product/version and resubmit the case, or contact technical support Symantec Technical Services" Who do I contact? And how to select the correct Product name to get to correct queue for the correct supportSolved3.2KViews1like61CommentsEvent ID 4107 CAPI2 error everybackup
I have two Server 2008R2DC's. Both have BESR 2010 ver.9.0.1.36527installed. One runs a backup at 10PM the other at 10:15PM. BESR 2010 has been installed for almost 7 months with no issues until 2 weeks ago. I have been receiving Event ID 4107 on both DCs at exact time the backup runs every night for the past 2 weeks. I have two other servers with BESR 2010 installed and are not experiencing these events (They are Server 2003R2 however) All backups seem to be completing fine.... Any thoughts on how to troubleshoot this? Event 4107, Source CAPI2: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. . XML: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" /> <EventID Qualifiers="0">4107</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2010-07-26T02:00:21.806127200Z" /> <EventRecordID>6002</EventRecordID> <Correlation /> <Execution ProcessID="1304" ThreadID="5012" /> <Channel>Application</Channel> <Computer>PCDC1.PCDOMAIN.local</Computer> <Security /> </System> - <EventData> <Data>http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab</Data> <Data>A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.</Data> </EventData> </Event>3.2KViews0likes3CommentsProblem BESR 2010 ( 8.5 ) with XenServer 5.6 ( XenTools )
We got massive Problems with the new Xentools 5.6 und BESR. After Installation of the Xentools 5.6 the SystemGui hangs ( for about 2 min you cannot do anything, then the System reacts for 1-2 sec.). If you stop the BESR services or go back to the 5.5 Version of the Xentools, everything is working fine again. We can reproduce the error on SBS 2003, 2008, WinXP... I open a thread here and on the Xenside, because i don't know who is guilty. All I know is, that we need a solution for this problem, because we have many combinations of Xen/BESR on customers side. Regards Achim Heisler3.1KViews0likes44CommentsBackup failing. "Process cannot access the file because another process has locked a portion of the file"
I have one PC that fails it's backup every now and then with this particular error: Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. This PC is backing up to an external drive, G:, and it runs successfully some of the times. Here's the latest series of entries in the Backup Exec System Recovery.log file: 12/3/2012 23:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, * - Backup to G:, has been started automatically. 0x00 (Backup Exec System Recovery) 12/4/2012 0:47:38 AM High Priority Warning: 0x800706BA (Backup Exec System Recovery) 12/4/2012 0:47:38 AM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: * - Backup to G:. Error E7D1001F: Unable to write to file. Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. 0xE7D1001F (Backup Exec System Recovery) (UMI:V-281-3215-6071) I cannot figure out what is locking the file and I don't know what file is actually locked. I've been using a program called Processlock: (http://windowsxp.mvps.org/processlock.htm) to try to figure out what has the file locked, but I need to provide the exact file name in order to do so. I've found a few Symantec knowledge base documents about this error, but they always reference backing up to a network share/admin share as the issue and this isn't the case here as this is a local external drive. Is there anywhere where I can find more detailed logging to see what file actually is being locked and therefore cannot be accessed? Thanks2.9KViews0likes6CommentsCan`t install Backup Exec Sytem recovery
Hello, I have the same issue as in this topic "https://www-secure.symantec.com/connect/forums/besr-2010-cannot-uninstall" After successfull uninstalliation with batch file "UninstallBESR2010", I`m trying to reinstall BESR again (clean install), but I get an error (see attach) what can this be ?2.9KViews2likes33Comments