Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1: Backup- E: DataV-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). When runningVSSADMIN LIST WRITERS - command from prompt I'm given the following output: C:\Documents and Settings\xxx>VSSADMIN LIST WRITERS vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0} State: [10] Failed Last error: Retryable error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a} State: [1] Stable Last error: No error The following warnings and errors is shown in Windows Event Viewer: Event Type: Error Event Source: ESENT Event Category: ShadowCopy Event ID: 2004 Date: 09-10-2012 Time: 01:09:09 User: N/A Computer: SERVER01 Description: wins (3316) Shadow copy 13 time-out (70000 ms). Event Type: Warning Event Source: VSS Event Category: None Event ID: 12290 Date: 09-10-2012 Time: 01:09:29 User: N/A Computer: SERVER01 Description: Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402. hr = 0x00000000. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 09-10-2012 Time: 06:20:30 User: N/A Computer: SERVER01 Description: Backup Exec Alert: Job Failed (Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status. The data selected for the backup-job is pure files and System State. The server is a Windows Small Business Server 2003 SP2.Solved18KViews1like12Comments
Backup stuck on QUEUED forever!
Hi, Ihave Backup exec 12.5 Rev2213 with all the latest patches installed on my server. Iam trying to backup a remote server (which used to work fine a few days ago) however, the job sits on QUEUED forever. It also gives no indication what it's waiting for. Ihave restarted both the backup and remote server, cleaned the drive, paused &unpaused the device, checked and cleared all the alerts and tried a different tape. Iam now out of ideas. Any suggestions/advice would be greatly appreciated.15KViews1like16Comments
The Backup Exec user interface can only be run as a fully trusted application under .NET security policies
I downloaded and installed BEWS 12.5on our Windows 2008 Small Business Server (64-bit) this morning without problem. Following installation, Live Update ran and applied a bunch of patches including SP3. I then rebooted the server and tried launching Backup Exec for the first time. I immediately get the following error: The Backup Exec user interface can only be run as a fully trusted application under .NET security policies. This means you must run it from a directory on your local computer or you must configure .NET security to fully trust the application from a network location. (For more information, see http://entsupport.symantec.com/umi/V-259-0012) The application is being run from C:\Program Files\Symantec\Backup Exec, which is about as local as I can get. The referenced URL link opens Document ID 290571, which has absolutely nothing to do with this issue. The problem details are: Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: bkupexec.exe Problem Signature 02: 12.5.2213.152 Problem Signature 03: 4addee38 Problem Signature 04: mscorlib Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a7cb192 Problem Signature 07: 2d18 Problem Signature 08: 79 Problem Signature 09: System.Security.Security OS Version: 6.0.6001.2.1.0.305.9 Locale ID: 1033 Any ideas or suggestions?12KViews0likes24Comments
Can you export BE config and import it to new server?
Hello, my question is does BE version 12 or 2010(sorry cant remember) have the ability to export it's configuration (to include jobs and policies) and then import that info into a new installation? I have a customer that is using BE inside a VM as well as a bunch of other applications that are starting to make the VM perform bad. He wants to create a new VM and move the BE config to it. I do not know this product and i am unsure if this is possible. If it is possible, i would think some of the steps would be like this: 1 Export Config 2 Create new VM 3 Install BE on new VM 4 Import Config Is this even possible? I am trying to see if we can aviod having to recreate all the backup policies Thanks for your help.11KViews1like8CommentsError E000FED1 - Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Full error as below: Backup- Exchange2007.peacehospice.org.uk V-79-57344-65233 - AOFO: Initialization failure on: "\\Exchange2007.peacehospice.org.uk\Microsoft Information Store\First Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5). V-79-57344-65233 - AOFO: Initialization failure on: "\\Exchange2007.peacehospice.org.uk\Microsoft Information Store\Second Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5). It's running Exchange 2007 on a Windows Server 2008 Enterprise. I have it set up to only backup from active copy (as I understand there's a problem with passive copy). It's using Advanced Open File Copy set to use the System snapshot provider. When I look at the event viewer logs there's quite a few errors on both VSS and MSExchangeIS. Since there's quite a few errors I don't know which one is the root cause of the problem. Here's a list of the errors in chronological order. Log Name: Application Source: VSS Date: 23/05/2012 13:04:08 Event ID: 8193 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid. hr = 0x80070539. Operation: OnIdentify event Gathering Writer Data Context: Execution Context: Shadow Copy Optimization Writer Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Name: Shadow Copy Optimization Writer Writer Instance ID: {17d3dd3a-2e09-49ca-ba28-d9c0194bbd50} Log Name: Application Source: MSExchangeIS Date: 23/05/2012 13:04:15 Event ID: 9840 Task Category: General Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: An attempt to prepare the storage group 'First Storage Group' for backup failed because the storage group is already in the process of being backed up. The error code is 1293. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.) Log Name: Application Source: ESE Date: 23/05/2012 13:04:15 Event ID: 2007 Task Category: ShadowCopy Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Information Store (3620) Shadow copy instance 56 aborted. Log Name: Application Source: MSExchangeIS Date: 23/05/2012 13:04:15 Event ID: 9609 Task Category: Exchange VSS Writer Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Exchange VSS Writer (instance 24649fd2-a0a8-447d-8c83-19e677f2146a:56) failed with error code 1293 when preparing for Snapshot. Log Name: Application Source: MSExchangeIS Date: 23/05/2012 13:04:20 Event ID: 9702 Task Category: Exchange VSS Writer Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Exchange VSS Writer (instance 24649fd2-a0a8-447d-8c83-19e677f2146a:56) failed with error code 1295 when processing the post-snapshot event. Log Name: Application Source: VSS Date: 23/05/2012 13:04:21 Event ID: 8193 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid. hr = 0x80070539. Operation: OnIdentify event Gathering Writer Data Context: Execution Context: Shadow Copy Optimization Writer Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Name: Shadow Copy Optimization Writer Writer Instance ID: {17d3dd3a-2e09-49ca-ba28-d9c0194bbd50} Log Name: Application Source: MSExchangeIS Date: 23/05/2012 13:04:21 Event ID: 9617 Task Category: Exchange VSS Writer Level: Error Keywords: Classic User: N/A Computer: Exchange2007.peacehospice.org.uk Description: Exchange VSS Writer (instance 24649fd2-a0a8-447d-8c83-19e677f2146a:56) failed with error code 1295 when processing the backup completion event. What's the problem? What can I do to fix it? Thanks, David.Solved10KViews0likes7Comments
Backup jobs Hängen "In der Warteschlange"
Hallo, habe ein mittelschweres Problem... Egal ob Inventarisierung oder Auswerfen eines Bandes die Jobs bleiben immer mit Auftragsstatus "In der Warteschlange" hängen... habe schon die DB reorganisiert bla... ALLES was das BEutility halt machen kann... jobs gelöscht die noch geplant waren und nochmal versucht... anmeldekonto nochmal das Passwort eingetragen dienste neugestartet, Server neugestartet... Habe auch den Medienserver schon angehalten neugestartet... da bekomme ich ne Meldung: Der server kann icht angehalten werden und beim Starten dass er nicht wiederaufgenommen werden konnte... Habe dann auch das Bandlaufwerk aus BE entfernt und nochmal neu erkennen lassen und treiber nachinstalliert von SYM erst wenn ich die Dienste neustarte kassiere ich ne Fehlermeldung: E0008821 Ansonsten kann ich sagen: Windows 2003 Server 32bit Full Patched Backup Exec 12.5 for Windows Full Patched... Im Oktober bzw. November lief alles absolut einwandfrei... Ich wäre sehr dankbar für tipps!Solved10KViews1like8CommentsBackup Exec 12.5 x64 bit - Download
Does anyone know where I can download x64 bit Backup Exec 12.5 for Windows? I am running a Windows Server 2008 R2 OS. I have tried BE 2010 and am not impressed so far at the backup to disk speeds, nor the scenario with backing up Netware (most of my data). I am trying to evaluate whether to leave my current BE 12.5 32-bit server in place or install 64-bit 12.5 on my new server. If BE 12.5 isn't going to work with 2008 R2, then I will probably use the server for an other purpose rather than move to BE 2010. Does anyone have the binaries for 12.5 x64 ???? cheers,Solved8.5KViews1like8Comments
How to configure the Backup Exec Oracle Agent - Practical Step by Step Instructions
Hi All, I had a few problems with this, even after a support call, so I thought I would publish a detailed "click-here", "click-there" how-to article. 1. First, this should work for at least versions 11d and 12 since I did this on version 12 and compared it to a version 11d installation. I cannot verify that it will work for any other versions. This should also work for DB2 by substituting the DB2 component where I mention an Oracle component since they appear to configure the exact same way, but again, I could not verify this with certainty since I do not have a DB2 database. 2. Start the “Backup Exec Remote Agent Utility” from the “Backup Exec for Windows Servers” start menu group or if the shortcut is missing, from “c:\Program Files\Symantec\Backup Exec\vxmon.exe”. 3. On the “Status” tab, check the “Start the Remote Agent Utility every time you log on” check box. 4. On the “Publishing” tab, check the “Enable the Remote Agent to publish information to the media servers in the list” check box. Click “add” and add the media server IP address or server name. Assuming that your main Backup Exec application is on that server, I recommend using the local host IP address (127.0.0.1) for ease since you would never have to change it if you later change the server name or IP address. NOTE: The definition of Symantec term “media server” is the server where the main Backup Exec services reside. 5. On the “Oracle” tab, click new, and select the “instance” you wish to backup. The user name here should be the Oracle “SYS” user and the proper password. Enter the media server IP address or server name. Again, I recommend using the local host IP address, 127.0.0.1. This user will correspond to the user we will create later during step 7 in the main program in “Network>Logon Accounts”. 6. On the “Database Access” tab, check the “Enable media server authentication for Oracle and DB2 operations” check box. Enter the user as Domain\Administrator and click the “Change password” button and set the proper password for the Domain\Administrator account. This user will correspond to the user we will create later during step 8 in the main program in “Tools>Options>Oracle>Modify List”. Check the “Use the full computer name or IP address for Oracle and DB2 operations” check box. Enter the “Name or IP address” of the Oracle Server. Again, since our Oracle was on that server, I used the local host IP address, 127.0.0.1. NOTE: The documentation states that whatever you filled in here to backup, you must use the same exact value to restore. If you use the server name to back up, you will need to use the server name to restore, etc. 7. Go to the main Backup Exec for Windows Servers program. Go to the menu item “Network>Logon Accounts” and click “New”. Add the Oracle user “SYS” with the proper password and hit “OK”. This needs to match the user you created in Step 5 on the “Oracle” tab. If it does not exist, also add the Domain\Administrator user also and set it as default by clicking the “Set as default” button to the right. Add this user even if “System Logon Account” already exists since they need to match the format exactly with the user you entered in the “Database Access” tab of the “Backup Exec Remote Agent Utility” per the Symantec/VERITAS support article 292442. 8. Go to the menu item “Tools>Options>Oracle>Modify List” and click “New”. Add the IP address of the Oracle Server and pick the Domain\Administrator account from the “Logon Account” drop-down box and hit “OK”. This needs to match the user you created in Step 6 on the “Database access” tab. Again, I used the local host IP address, 127.0.0.1, since our Oracle database is on the same server as the Backup Exec. All the information you entered here should correspond to the information you entered in the “Database Access” tab. 9. You should now be able to select your Oracle database as a backup resource. You should also check the credentials for your job by going to the “Job Setup” tab and double-clicking any backup selections you have in the “Backup Selection Lists” pane, then going to the “Resource Credentials” in the left pane, and then hit “Test All”. The computer level at the top should use the Domain\Administrator account, the rest will inherit from that, with the exception of the “Oracle Database”, which should be using the SYS account we created in step 7. If not, highlight it and click “Change” on the right side. Other common problems include the database needing to be placed in “automatic archive log mode” as described in Symantec/VERITAS support article 266835; and the need to change the “Archive Log Mode” from “NOARCHIVE LOG” to “ARCHIVE LOG” (in version 9, in the Oracle Enterprise Manager Console, go to “Network>Databases>DatabaseName>Instance>Configuration” and then to the “Recovery” tab, and check “Archive Log Mode” box. This needs to be done as the Oracle SYS user and this can be changed in “Configuration>Edit Local Preferred Credentials” if necessary. KEYWORDS: 0xe0001403; 0xe0001014; “Failed to access Oracle database”; “Cannot start an Oracle session. Check that the logon credentials are correct, and have sufficient privileges.”; “The database is in NOARCHIVELOG mode and is OPEN. To back up the database when it is in NOARCHIVELOG mode, the database must be MOUNTED but not OPEN.” Relevant Symantec/VERITAS support articles regarding common errors, setup, backup, and restoration using the Oracle agent: 266835; 292497; 292442; 300135; 300134; 300133; 300130; 300119; 300125; 300123; 300118; 300116. You may also go to this page for a complete list of Backup Exec for Windows Server support articles, including those regarding the Oracle agent: http://seer.entsupport.symantec.com/docs/BEWNT_index.htm. Best Regards, Kevin Cotreau MCSE+I, MCNE, et al.Solved8KViews3likes8CommentsBackup Exec 12 error V-79-57344-34029
Encounter backup error while backup. Every 2 day, backup exec will backup whole server data, 1st backup process will complete successful. When perform 2nd backup on same data catridge (LTO3), will encounter error code V-79-57344-34029. Try with brand new data catridge also encounter same scenario during 2nd bakcup in progress. Below is the job log details on error part Backup- D: DATAPART1 Storage device "IBM 2" reported an error on a request to write data to media. Error reported: The request could not be performed because of an I/O device error. V-79-57344-34029 - A hardware error occurred. A selection on device C: was skipped because of previous errors with the job. A selection on device E: was skipped because of previous errors with the job. A selection on device [Server Name] Partition was skipped because of previous errors with the job. A selection on device Shadow?Copy?Components was skipped because of previous errors with the job. Backup- XYZ Storage device "IBM 2" reported an error on a request to read data from media. Error reported: Incorrect function. V-79-57344-34030 - An invalid command was sent to the storage device. Verify Storage device "IBM 2" reported an error on a request to read data from media. Error reported: Incorrect function. V-79-57344-34030 - An invalid command was sent to the storage device. In DELL OpenManage Server Administrator Page, there is no connection error on the LSI Logic 1020/1030 Ultra320 SCSI Adapter. Below is the Backup Exec information. Symantect Backup Exec 12 for windows Server Media server : Version 12.0 Rev 1364 Adminsitration Console : Version 12.0 Rev 1364 Desktop and Laptop Option : Version 3.1 Rev 3.38.61a Installed update : Service Pack 5, Hot fix 358179 & Hot Fix 155482 Kindly adviseSolved8KViews0likes9Comments
Tape drive keeps going offline
I have a backup configured on a HP storage works DAT 160 SAS tape drive. Every so often the backup fails and the HP tape drive goes offline. I can then right click the tape drive and select online and it comes online but when i click inventory the drive goes offline again. I have checked the cables and made sure that they are plugged in and the only way to fix the problem for a short while is to stop the backup exec services turnoff and turn on the tape drive then restart the services. Can anyone please help with this problem? Thanks, JoshSolved7.6KViews1like10Comments
Backup stuck on QUEUED forever!
Hi, Ihave Backup exec 12.5 Rev2213 with all the latest patches installed on my server. Iam trying to backup a remote server (which used to work fine a few days ago) however, the job sits on QUEUED forever. It also gives no indication what it's waiting for. Ihave restarted both the backup and remote server, cleaned the drive, paused &unpaused the device, checked and cleared all the alerts and tried a different tape. Iam now out of ideas. Any suggestions/advice would be greatly appreciated.The Backup Exec user interface can only be run as a fully trusted application under .NET security policies
I downloaded and installed BEWS 12.5on our Windows 2008 Small Business Server (64-bit) this morning without problem. Following installation, Live Update ran and applied a bunch of patches including SP3. I then rebooted the server and tried launching Backup Exec for the first time. I immediately get the following error: The Backup Exec user interface can only be run as a fully trusted application under .NET security policies. This means you must run it from a directory on your local computer or you must configure .NET security to fully trust the application from a network location. (For more information, see http://entsupport.symantec.com/umi/V-259-0012) The application is being run from C:\Program Files\Symantec\Backup Exec, which is about as local as I can get. The referenced URL link opens Document ID 290571, which has absolutely nothing to do with this issue. The problem details are: Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: bkupexec.exe Problem Signature 02: 12.5.2213.152 Problem Signature 03: 4addee38 Problem Signature 04: mscorlib Problem Signature 05: 2.0.0.0 Problem Signature 06: 4a7cb192 Problem Signature 07: 2d18 Problem Signature 08: 79 Problem Signature 09: System.Security.Security OS Version: 6.0.6001.2.1.0.305.9 Locale ID: 1033 Any ideas or suggestions?Can you export BE config and import it to new server?
Hello, my question is does BE version 12 or 2010(sorry cant remember) have the ability to export it's configuration (to include jobs and policies) and then import that info into a new installation? I have a customer that is using BE inside a VM as well as a bunch of other applications that are starting to make the VM perform bad. He wants to create a new VM and move the BE config to it. I do not know this product and i am unsure if this is possible. If it is possible, i would think some of the steps would be like this: 1 Export Config 2 Create new VM 3 Install BE on new VM 4 Import Config Is this even possible? I am trying to see if we can aviod having to recreate all the backup policies Thanks for your help.