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

Backup exec 2010 R3

Created: 30 Jan 2013 • Updated: 30 Jan 2013 | 3 comments

Hello we are running a sbs 2011 server and Backup Exec 2010 R3. The backup does 2 daily backups 1 to a ext 4TB hdd and 1 to a ext 1TB Hdd, the 1 TB ext drive is swapped daily. We are having alot of issues with the backups failing with vss errors when it is backingup exchange - we get the following errors -

 

 

Backup
V-79-57344-65233 - AOFO: Initialization failure on: "\\SBSSVR\Microsoft Information Store\Mailbox Database". 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: "\\SBSSVR\Microsoft Information Store\Public Folder Database 1822720368". 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-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

V-79-57344-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

V-79-57344-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

V-79-57344-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

V-79-57344-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

V-79-57344-65085 - There was a problem running the DBCC.

A database snapshot cannot be created because it failed to start.

I have done a vssadmin list writers from a command prompt and got the following -

 

 

icrosoft Windows [Version 6.1.7601]
opyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
:\Users\Admin>vssadmin list writers
ssadmin 1.1 - Volume Shadow Copy Service administrative command-line
C) Copyright 2001-2005 Microsoft Corp.
 
riter 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
 
riter 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
 
riter 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
 
riter name: 'System Writer'
  Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
  Writer Instance Id: {220eab50-0bff-492d-a7ab-ef530010d3a8}
  State: [1] Stable
  Last error: No error
 
riter name: 'FSRM Writer'
  Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
  Writer Instance Id: {624e45b1-acec-48b8-8de8-80d777a3aab7}
  State: [1] Stable
  Last error: No error
 
riter name: 'SqlServerWriter'
  Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
  Writer Instance Id: {8e05e4ca-4301-4242-85f7-c9b39165a1f9}
  State: [1] Stable
  Last error: No error
 
riter name: 'FRS Writer'
  Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
  Writer Instance Id: {dce6ab9b-bb6f-4eb8-9e62-5cc1595dbc1b}
  State: [1] Stable
  Last error: No error
 
riter name: 'SharePoint Services Writer'
  Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
  Writer Instance Id: {2bd0eb1c-c5af-4abe-903d-63791a4974f8}
  State: [1] Stable
  Last error: No error
 
riter name: 'ASR Writer'
  Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
  Writer Instance Id: {9694cced-0a37-4e5e-b496-ef454d1e9b94}
  State: [1] Stable
  Last error: No error
 
riter name: 'NPS VSS Writer'
  Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
  Writer Instance Id: {379df987-977c-4931-b5be-9f02b2e97d70}
  State: [1] Stable
  Last error: No error
 
riter name: 'IIS Config Writer'
  Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
  Writer Instance Id: {a08d9123-3db4-4ee1-b1dd-6e0570b4bcd1}
  State: [1] Stable
  Last error: No error
 
riter name: 'Shadow Copy Optimization Writer'
  Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
  Writer Instance Id: {8a67507b-619c-4118-8c4d-6efbf7f33090}
  State: [1] Stable
  Last error: No error
 
riter name: 'WMI Writer'
  Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
  Writer Instance Id: {54192e93-44f7-46e1-9963-9f932589a075}
  State: [1] Stable
  Last error: No error
 
riter name: 'IIS Metabase Writer'
  Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
  Writer Instance Id: {4cd24c4c-aa1d-4135-8009-767641f571f0}
  State: [1] Stable
  Last error: No error
 
riter name: 'Registry Writer'
  Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
  Writer Instance Id: {16b012e6-3571-4b36-a31c-7a6e91449a55}
  State: [1] Stable
  Last error: No error
 
riter name: 'TS Gateway Writer'
  Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
  Writer Instance Id: {6efc4e35-b909-4abc-b967-88adc88f004c}
  State: [1] Stable
  Last error: No error
 
riter name: 'Microsoft Exchange Writer'
  Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
  Writer Instance Id: {14412c74-63a0-4f61-a7d5-daf28954f34e}
  State: [1] Stable
  Last error: Retryable error
 
riter name: 'COM+ REGDB Writer'
  Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
  Writer Instance Id: {74e9fdfe-516a-4b13-b4ba-7bc7f710b384}
  State: [1] Stable
  Last error: No error
 
riter name: 'Dhcp Jet Writer'
  Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
  Writer Instance Id: {bb3fc8aa-4b4c-492d-8727-2f97786ae833}
  State: [1] Stable
  Last error: No error
 
riter name: 'NTDS'
  Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
  Writer Instance Id: {9d0b1dad-7808-4cba-9ea4-634f953fdd32}
  State: [1] Stable
  Last error: No error
 
riter name: 'Certificate Authority'
  Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
  Writer Instance Id: {99e73531-9c8c-4460-8ad8-f03d15d5860a}
  State: [1] Stable
  Last error: No error
 
riter name: 'MSSearch Service Writer'
  Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
  Writer Instance Id: {3aae826f-d489-4db1-83f5-06ad2e3831fd}
  State: [1] Stable
  Last error: No error
 
The only error i can see is the MS exchange writer - error retryable, has anyone got any advice on this.
 
Thanks in advance
 
Phil

Comments 3 CommentsJump to latest comment

Colin Weaver's picture

Possibly not causing this specific error but if the 4TB drive is using a 4k sector size then that can cause problems with GRT backup operations. I would not normally associate the error you mentioned with this sector size however.

 

With regards the retryable VSS error does it clear if you reboot the SBS server and does it then come back when you run a new backup?

Geddey's picture

Hello Colin, unfortunaltly i cannot reboot the server since its an active server 24 hours a day, is their anyway you know to clear this error without a reboot. The only time we can reboot it is at a weekend.

Geddey's picture

OK restarted the information store service last night and run vssadmin list writers and the writers are now clear including the exchange writer, i have not done an exchange backup yet, it only runs tonight.