Link to home
Start Free TrialLog in
Avatar of eveljkov
eveljkov

asked on

Backup Exec 10.1 5629 AOFO init error on MS Information Store

I have a job failing.  Not sure what's going on with it.  I know the MIS is there so its not a matter of it not being there.  Is there some cross-server permissions that I'm missing?


AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE00084AF): The directory or file was not found, or could not be accessed.

Check the Windows Event Viewer for details.
Note: Backup Exec did not perform a snapshot of all volumes simultaneously because the option 'Process logical volumes for backup one at a time' was selected as a backup job property.
Note: Resource: "\\SERVER\" is not snappable. Attempting to back up directly from the source volume.
Network control connection is established between XXX.XXX.X.X:3883 <--> XXX.XXX.X.X:10000
Network data connection is established between  XXX.XXX.X.X:4137 <--> XXX.XXX.X.X:1326
Avatar of AdamRobinson
AdamRobinson

Simple question for ya: Have you tried unchecking process logical volumes for backup one at a time?  I encountered this error a few times on a remote backup job.  Created a new job, removed the "one at a time," and it went through after that.

Avatar of eveljkov

ASKER

well, that got rid of "Note: Backup Exec did not perform a snapshot of all volumes simultaneously because the option 'Process logical volumes for backup one at a time' was selected as a backup job property."

but the AOFO init error is still there.
ASKER CERTIFIED SOLUTION
Avatar of Member_2_231077
Member_2_231077

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I don't think I'm 100% clear on AOFO.

Would it hurt to turn it off for whole job?  It's really just the Exchange information on the server that is important.  We have some other information but nothing will be open when the job is running.  

How about forcing the whole job to use VSP?  
If nothing's open except Exchange then definitely turn off the AOFO, why bother to troubleshoot each snapshot problem (and there are lots of them) if you can disable snapshots? There may be a few odd files open but you can generally ignore them, wins, dhcp and bits have files locked open but you don't need to back them up anyway.