Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backing up Exchange 2010 failed with Backup Exec 2012

Created: 06 Sep 2012 | 10 comments

Hello Everybody, 

I have a seriouse issue backing up my exchange 2010 with Backup exec 2012. 

When I perform a backup in the first place I received those error:

Only Mails-Full -- The job failed with the following error: A failure occurred querying the Writer status.  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: Failed during prepare snapshot operation (8).

Only Mails-Incremental -- The job failed with the following error: A failure occurred querying the Writer status.  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: Failed during prepare snapshot operation (8).

Base to some discussion from symantec faq, I restart the mail store service and perform a backup. The job run but stuck at 50 Gb for about 20 hours and the status is loding media. The backup job was running perfectly fine with a good speed, but after 50 Go it goes to the state loading. Please see picture below of the status.

Wainting for an idea

Comments 10 CommentsJump to latest comment

Riyaj S's picture

Run "vssadmin list writers" command on the exchange server to check the exchange writer status. If the writer is in failed status, reboot the Exchange server and re-run the job. Also check if Windows operating system and Exchange application is fully patched.

Hope this helps.

Thanks,

Riyaj

Try out the new Backup Exec Support Tool that diagnoses many common issues found in Backup Exec and Symantec System Recovery environments. 
 
http://www.symantec.com/docs/TECH126539
Baps CPC's picture

Hello Riyaj,

I run VSSadmin on Exchange server and no error. Only Exchange writer give status Waiting for completion. Result is

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {efd8dbe5-3de2-4260-a55f-2a2094c49f76}
   State: [1] Stable
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {a06813ae-e5eb-4fa9-ad24-6989bae98ac9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {1eb7c3b0-7706-4b9d-be64-fb8e5f4ef358}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {47d2e18c-69da-4c04-8810-2f24e731b8ed}
   State: [5] Waiting for completion
   Last error: No error
 
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {99e7005a-9ff7-4296-bcf1-eb5eee430411}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ca66eb53-5c91-46a5-b1d5-e17b5784cdc3}
   State: [1] Stable
   Last error: No error
 
Writer name: 'CvWriter'
   Writer Id: {248a30d3-9216-4200-8201-29ac21d6c307}
   Writer Instance Id: {445b7371-a999-40de-86c0-357b03157fba}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {86fd5e81-e393-4939-b3d5-ff4673ad33bd}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {da2214de-7332-4d2c-a900-da3756819c84}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fbf78dba-b367-41bb-a983-040859dc595b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f92bee9a-da5a-4a05-b9dc-e9c60e7bfda9}
   State: [1] Stable
   Last error: No error
 
The server is fully patched. what the message from the exchange writer status mean? "Waiting for completion". And how to resolve it.
ZeRoC00L's picture

Run "vssadmin list writers" on the exchange server directly after a failed backup !

If this response answers your concern, please mark it as a "solution"

Baps CPC's picture

On the backup server I have 1 error:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
(C) Copyright 2001-2005 Microsoft Corp.
 
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {8e2212ac-38a7-4a54-990b-9d28319b8f29}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {eee538e2-5ce6-4515-8e92-9eccae9ed241}
   State: [1] Stable
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {e0f8cf56-5973-48c0-a39e-a21d94f38a20}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {18e0c995-a323-4760-8164-3ad4a3fc4b22}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {65a6c570-adeb-4a41-863c-fee9d492d56e}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {b6853d8b-b471-4b2c-b534-48e87988793a}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {22fde336-5d8f-48b4-87fa-9743bfd050a8}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ccae39e4-30e8-469b-a606-8947e7dc408f}
   State: [1] Stable
   Last error: No error
 
On Exchange server, after backup failed, their no more error on the VSS. Result is:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {efd8dbe5-3de2-4260-a55f-2a2094c49f76}
   State: [1] Stable
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {a06813ae-e5eb-4fa9-ad24-6989bae98ac9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {1eb7c3b0-7706-4b9d-be64-fb8e5f4ef358}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {86fd5e81-e393-4939-b3d5-ff4673ad33bd}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ca66eb53-5c91-46a5-b1d5-e17b5784cdc3}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {99e7005a-9ff7-4296-bcf1-eb5eee430411}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {47d2e18c-69da-4c04-8810-2f24e731b8ed}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fbf78dba-b367-41bb-a983-040859dc595b}
   State: [1] Stable
   Last error: No error
 
Writer name: 'CvWriter'
   Writer Id: {248a30d3-9216-4200-8201-29ac21d6c307}
   Writer Instance Id: {445b7371-a999-40de-86c0-357b03157fba}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {da2214de-7332-4d2c-a900-da3756819c84}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f92bee9a-da5a-4a05-b9dc-e9c60e7bfda9}
   State: [1] Stable
   Last error: No error
Frotack's picture

Rebooting the exchange server will get the VSS writers back in good shape,  this is the first thing to try.

Baps CPC's picture

I already try it many times, but the problem still occur. What is the next solution?

Problem occur during backup, before I start the backup, VSS are in stable state, but during the backup, if the job state goes in loading media, VSS writer goes wrong.

Please advise.

Frotack's picture

in CMD run vssadmin list providers

if you have another provider apart from microsoft then you can select to use the other provider in backup exec as above

Baps CPC's picture

Thank you for the reply Frotack,

The only provider I have on the 3 servers is Microsoft Shadow copy

Here is the result:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 
Actually, I have one Backup Server, agent on each server excepte the NAS and a NAS (MS 2008 Data center) that host all Backup Jobs.
 
But I realize in the Backup server (MS 2008 Enterprise) always has ASR writer time out when the job failed. And in the Exchange server I have Waiting for completion for the status of Microsoft Exchange Writers.
Baps CPC's picture

Hello PKH,

I have a Windows SRV 2008 R2 and the link you sent mentioned to not applied to an WIN SRV 2008 R2.

Please advise.