Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Exchange backup issues - VSS

Created: 11 Mar 2010 • Updated: 21 Sep 2010 | 5 comments

  I have been working on trying to get a decent backup of Exchange consistently for months.  I will go through times where it works and times where it never works.  

Exchange Server: Server 2003 Enterprise 64
Backup Exec: 12.5 SP3
B2D to Local storage on Machine
 
Anyways, recently things have gotten worse, I am only getting one day a week that might actually work, right after a server restart.  I have tried changing the job to different styles of backups, this does not help.  What I have been getting recently is "Volume Shadow Copy" service remains in a "Stopping" state and the jobs fail.  
 
The error from that:
Backup- 
- AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11253 - Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details. 
 
I have recently tried and deleted and recreated the jobs and am getting this issue now:
Backup- 
V-79-57344-65233 - AOFO: Initialization failure on: "\\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: Stable (1). 
 
This is the VSS:
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {ae032779-723f-492b-b8e1-3394a1580466}
   State: [1] Stable
   Last error: Retryable error
 
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {45ef3ad0-022e-4dbe-bef5-4909459df3ef}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {12562b1f-9ba0-4b53-8eec-52856ab53189}
   State: [7] Failed
   Last error: No error
 
The backup job looks like this:
B2D
Overwrite
Advanced Open File: Use Microsoft Software Shadow Copy Provider (after long support call a while back this was how we got exchange working again)
Exchange: Using GRT, Backup from the Active copy, no other checks selected

I have tried changing the AOF: to Automatically select open file technology

Does not work.  Is this just what I should expect from BE?  Guess NetBackup will have the same issues?  Can I ever get this to work!!!!

Comments 5 CommentsJump to latest comment

Dev T's picture

Hello,

It is not recomended to Backup Databases like Exchange, SQL using snapshot (VSS). It is always recomended to Backup Exchange IS in a seperate job.

Uncheck AOFO in the Backup job and run the job again. If you still want to use VSS based backups, please install the VSS Rollup Patch : http://support.microsoft.com/kb/940349 (REBOOT REQUIRED) and perform backups....

Hope this helps....

Its a best practice to have a "Support Contract" with Symantec...
 

Matt34's picture

 I have taken off AOFO from the backup (now have to restart to server to get VSS all correct).

I have also checked what Updates are installed an KB940349-v3 is already installed on that server.

Dev T's picture

Hello Matt,

Are the backups working now?

Its a best practice to have a "Support Contract" with Symantec...
 

Dev T's picture

Hello,

Reboot the exchange server and then perform the backups again. I was facing the same issue a reboot helped....

Its a best practice to have a "Support Contract" with Symantec...
 

Dev T's picture

Hello,

Any news here?

Its a best practice to have a "Support Contract" with Symantec...