Backing up Exchange 2010 failed

[Baps_CPC]

I tried to backup my exchange server 2010 with Backup Exec 2012 and get the following error.

FQDN_Server Full Server-Backup -- The job failed with the following error: An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more details.

When I click on View Job log, I have this message:

---------------------------------------------------------------------------------------------------------

Backup- \\FQDN_Server\Microsoft Information Store\Public Folder Database
V-79-57344-65146 - An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more details. V-79-57344-65146 - An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more details.

Backup- \\FQDN_Server\Microsoft Information Store\My MailBox Name
V-79-57344-65146 - An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more details. V-79-57344-65146 - An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more details.

Backup
V-79-57344-65218 - A failure occurred accessing the SnapShot handle. 

From Event viewer on Exchange 2010, I have the event ID 6: Cmdlet failed. Cmdlet Get-MailboxDatabaseCopyStatus, parameters {Identity=Public Folder Database\*, Active=True}.

Cmdlet failed. Cmdlet Get-PublicFolderDatabase, parameters {Identity=MyMailBoxName}.

--------------------------------------------------------------------------------------------------

I have Backup Exec 2012 and Win Server 2008 R2 Standard  fully patched.

Please provide a fix if you already have this issue.

[VJware]

Regarding the cmdlets error - www.symantec.com/business/support/index?page=content&id=TECH169638

Are there any other errors logged ? Ensure AOFO is not checked in the backup job properties & also check the status of the VSS writers..

[Baps_CPC]

Thank you for quick response VJware. 

AOFO is not checked and all VSS writers give no error.

I perform a test yesterday by creating a new job for the Mail server and use a local storage where the backup server is hosted. The job run successfully.

Create a 2nd job for a file server and use a Storage from the NAS server, backup run successfully, but exchange, SQL and Sharepoint always failed if a use storage on the NAS server.

So my architecture is : 1 NAS hosting backup storage, 1 server witha backup server and each other server with backup agent.

Any idea????

By the way, I use the same backup setting when creating a job.

[VJware]

Run vssadmin list providers on the exchange server.. Are there any other providers present apart from the Microsoft VSS provider ?

[Baps_CPC]

Resullt of VSSAdmin list 

Provider name: 'Microsoft Software Shadow Copy provider 1.0'

   Provider type: System

   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}

   Version: 1.0.0.7

[Baps_CPC]

Hello,

Anyone can provide a solution for this issue?

[Baps_CPC]

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

[pkh]

Rebooting the server will cure the writer failure problem.  You might want to re-register the VSS dll's.  See this document.

http://www.symantec.com/business/support/index?page=content&id=TECH70486

[Baps_CPC]

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.

[Donald_Eady]

I would also suggest rebooting the server then running the vssadmin list writers command again to see if the failing writer appears in a state 1 stable state. I would caution you against re-registering the Vss dll's as in doing so has the potential to cause Significant issues.