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

AOFO Error when not selected ?

Created: 20 Dec 2013 | 4 comments
Jennings's picture

Hi,

Runnings BE 2010 R3 (fully patched) on a SBS 2011 server.

We run 2 backup jobs on an evening to an LTO3 drive

First full backup does everything on server apart from exchange and uses AOFO (this seems to run fine every night)

Second backup appends the tape with a full backup of Exchange and does NOT use AOFO

The second backup randomly fails ( average twice a week) with the following error.

V-79-57344-65233 - AOFO: Initialization failure on: "\\SERVER1\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. See the job log for details about the error.

Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

V-79-57344-65233 - AOFO: Initialization failure on: "\\SERVER1\Microsoft Information Store\Public Folder Database 2052815782". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.

Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).

But why do I get AOFO related errors when I am not using nor selecting it for this backup job ?

I would appreciate any help on this.

Many thanks

Operating Systems:

Comments 4 CommentsJump to latest comment

CraigV's picture

Hi,

Not necessarily AOFO errors, but VSS...run: "vssadmin list writers" on the Exchange server, and see if the writers are all stable.

If not, a server restart normally returns them to a running and stable state.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Jennings's picture

Hi,

Many thanks

The command you suggested returned all stable apart from below

Microsoft Exchange Writer that says failed with last error as timed out.

We have been rebooting to cure the problem but rebooting twice if not 3 times a week is going to be an issue.

Are there any long term fixes other than rebooting. ?

Cheers

CraigV's picture

...rebooting, while it does help, isn't a fix. You might want to see if Microsoft have a fix for this too...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Colin Weaver's picture

Just for info

Historically the only thing that used VSS was AOFO hence our error messages were coded to always mention AOFO if errors were reported from VSS

However most Windows backup types now use VSS (with or without AOFO) unfortunately some of the error messages returned in job logs may need some tweaking as they stil mention AOFO because of the past use.

With regards the problem you have, CraigV is giving a good first place to look, however also look in the Windows event logs (Application & System) on the Exchange server to review for VSS or possibly Exchange problems.