Video Screencast Help

AOFO or no AOFO Exchange 2007 on 2003 Server Backup Exec 12

Created: 01 Mar 2013 | 5 comments

I have read a lot of posts on not to use AOFO for Exchange 2007 on Server 2003 and Backup Exec 12.  I was using it successfully and was able to successfully restore my exchange 2007 DB to a recovery Storage Group and then my backups started having issues.  I started googling and found lots of posts to not use AOFO.  We then set our backups up not to use AOFO, and ran the backup.  It now takes over 20 minutes to process a snapshot and out of 16 DBs i had 5 DBs fail with the following error:

80042306 - 0x80042306 (2147754758)

 

I google that error and find an article stating that we should enable AOFO.

Thoughts suggestions?

Operating Systems:

Comments 5 CommentsJump to latest comment

CraigV's picture

Hi,

 

Generally don't use AOFO with backups of databases...I've had issues restoring Exchange 2003 where it wouldn't do the restore directly, and also SQL where I couldn't do a redirected restore to a test server...lots of grey hairs doing a restore of a Navision production database to another instance on the Navision production server...

Making a long story short, I was advised by a Symantec engineer NOT to use AOFO with DBs and rather split my jobs up between databases (AOFO off) and files (AOFO on).

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

VJware's picture

When you run vssadmin list providers on the exchange server, which vss providers are listed ?

Is any other backup application is installed on the exchange server ?

MattHDallas's picture

VJware,

There are two providers:

Microsoft Software Shadow Copy provider 1.0

Data ONTAP VSS Hardware Provider

 

SnapManager is also installed on Exchange which I believe is a backup application that was used in the past.

 

 

 

VJware's picture

Hardware VSS provider gets the top priority & hence the error. I believe the KB which you found to enable AOFO was about setting AOFO & choosing the system microsoft vss provider over the hardware provider.

MattHDallas's picture

That is what I have done.  I did enable AOFO and chose Microsoft VSS Provider.  So for my setup, that should be the best way to do this correct?  When I do this, the snapshot takes a couple of minutes, versus waiting 20-30 minutes on the Hardware provider.