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

Backup Exec 2010R3 AOFO Failure on Windows Server 2012

Created: 03 Oct 2013 • Updated: 03 Oct 2013 | 3 comments
This issue has been solved. See solution.

Hi,

added 2 new 2012 servers this week - last night was the first backup of them but the job completed with exceptions, tripping up on the 2 new Server 2012 machines.

Backup - myserver1

- AOFO Inilization Failure on "\\myserver1\C:" . Advanced Open File Option Used: Microsoft Volume Shadow Copy Service (VSS)

V-79-10000-11213-

Backup - myserver2

- AOFO Inilization Failure on "\\myserver2\L:" . Advanced Open File Option Used: Microsoft Volume Shadow Copy Service (VSS)

V-79-10000-11213-

The AOFO option is selected in my job - using Auto select technology.

The VSS service on both servers is set to Manual

ANybody any suggestions - job has run perfectly for months until these 2 new 2012 servers were added to the selection list.

Thanks

Operating Systems:

Comments 3 CommentsJump to latest comment

Andrew` Thompson's picture

Makes no difference Jaydeep.

I am seeing many access denied errors in the event log of 1 of the 2012 servers.

1 of them to a reg key

Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.

Volume Shadow Copy Service error: Unexpected error calling routine  OpenService (shSCManager, 'VSS', SERVICE_QUERY_STATUS).  hr = 0x80070005, Access is denied.

Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x80070005, Access is denied.

Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x80070005, Access is denied.

I have given the backup exec user full control over that reg key but a test job just run still completes with the same behaviour.

Andrew` Thompson's picture

I have found out the problem.

The backup exec user has to be part of the local admins group on the remote 2012 machines.

Job now runs successfully.

SOLUTION