cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Backup Exec 2012- Differentials fail on Exchange

MGITCX
Not applicable

‎08-31-2012 06:14 AM

Hi, I was wondering if anyone could offer any advice regarding a problem I'm having on sites where we have Backup Exec 2012 deployed.  Spent a week or so changing settings now, it's getting a bit frustrating because 2010R3 used to just work in identical scenarios:

Both Servers are running MS Small Business Server 2012 (so Exchange 2010) with Backup Exec 2012 Small Business.

 

Backup- SBS

V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\SBS.wt.local\Microsoft Information Store\Public Folder Database 0379027957". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

 

Snapshot technology 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: Failed during prepare backup operation (7).

 

At the moment the problem is only on the differential or incremental backups, the end of week full jobs work correctly, I've created seperate jobs for the data until I get this sorted.

Aside from tweaking selections steps I've taken so far include turning off circular logging and turning off advanced file open.  The only time I've got a differential to work was when I deleted every single shadow copy on the disk holding exchange which isn't something I can do long term.  If I do a vssadmin list writers they all show as stable.  I've checked for a shadow copy with the ID shown in the error but there isn't one.  I've also done the usual reboots and restarts of services.

Any suggestions would be most welcome, I can possibly put one the sites to only do full backups on exchange in the mean time as storage isn't an issue, but the other one takes to long for that to be feasible because it's over a wireless link.

5 REPLIES 5

Backup_Exec1
Level 6
Employee Accredited Certified

‎08-31-2012 07:03 AM

Hi First of all would request to open a case with Symantec to investigate this issue as you have described same was working fine with BE2010 and now not working with BE2012. Thanks
0 Kudos

sbora
Level 6
Employee Accredited Certified

‎09-10-2012 05:06 AM

Can you attach application log from exchange servers (saved in .txt format and zipped)?

0 Kudos

tolu
Level 3

‎09-10-2012 05:36 AM

Here is the log file during backup operation.

0 Kudos

sbora
Level 6
Employee Accredited Certified

‎09-10-2012 06:48 AM

Hello Tolu,

Following events are logged in application log when the backup failed:

 

Error 10.9.2012 9:11:55 ESE 459 Logging/Recovery "Information Store (1892) Mailbox Database 2011093014: The file C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 2011093014\E0000013AC9.log is missing and could not be backed-up. 
 
 
Error 10.9.2012 9:11:55 ESE 2002 ShadowCopy "Information Store (1892) Shadow copy instance 2 encountered error -569 on freeze. 
 
Error 10.9.2012 9:11:55 MSExchangeIS 9611 Exchange VSS Writer Exchange VSS Writer (instance 64e94131-e054-4ff6-933f-cacd3f521d5a:2) failed with error code -569 when freezing the database(s). 
 
 
The above events lead to backup failure. You need to figure out more on the missing log file which is leading to VSS snap/backup of database to fail. Some of the documents that you can refer:
http://www.symantec.com/docs/TECH189353 
http://www.symantec.com/docs/TECH179220
 
 
Application log also shows following warnings related to SharePoint:
 
Warning 10.9.2012 9:11:58 VSS 8230 None "Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key. 
 
Operation:
   PostSnapshot Event
 
Context:
   Execution Context: Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {e4e63b41-9f52-4f3c-a931-00e9e2a2e1c8}
 
Error-specific details:
   Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.

 

 

A quick google search lead to following MS KB article for VSS warnings above:

http://support.microsoft.com/kb/2537096

 

0 Kudos