This document may give you a hand figuring out the cause of the problem.

http://support.veritas.com/docs/326302

Hello,

I believe the error message V-79-57344-34110 - AOFO: Initialization failure on: "D:". is on Windows Server 2003. If so, please follow the steps below:
1  : Open the job properties.
2  : Navigate to the "Advance Open File" Opion
3  : Check the Radio Button "Microsoft Volume shadow copy service"
4  : Snapshot provider dropdown..select the second option "System:Use Microsoft Shadow Copy Provider"

We need to make sure that "Shadow Copies" are enabled on the D-Drive of that particular Server
1  : Go to the properties of the D-Drive
2  : Click on the "Shadow Coipes" TAB
3  : We must see all the Partitions under "Select a Volume"

Please let me know the results...

Hi

I am agree with you that he need to change the snapshot provider to Microcoft Shadow Copy Providerbut no need to enable shadow copy on D volume.

The steps for setup AOFO is as follows. These steps are as per the guidelines

1. Install remote agent with AOFO on remote server and reboot the server. If it is local backup serever then no need to install remote agent.
2. On remote server make sure that you have sufficient free space available on any drive
3. The data which you need to backup, should not be resides on that drive.
4. Minimum free space should be 20-25% of data which you want to backup.
5. Create a folder on that valume (name can be AOFO)
6. Set this folder to store the snaps

To manually set this folder as a snapshot folder please find the configuration steps below

1. Open backup exec console on backup server
2. Click Tools-->Wizards-->Advanced Open File Option Wizard
3. Click Next, Select the server, Provide authentication & click Next
4. Uncheck Use Default, "drive letter"\AOFO, click insert & then click next
5. "Number of seconds during which  there can be no disk activity.............." set value to 3 sec & click next
6. Click OK  & Click finish

Perform the backup job again.

Just make sure you dont reduce the quiet time more than 2 secs

Make sure the Antivirus is not configured to scan cache folder for AOFO at the same time job runs  

hi,

Exclude *.vsp from antivirys scanning.........
Also if backups run in non working hours simply dont use AOFO...
Please install latest Hotfix of VSS from microsoft.

Definately solves problem

regards
KK

Forgot to tell you...

Also exclude *.vsp & vsp.sys from AV scanning on the remote server

vsp.sys file will be available in windows\system32 folder

Please check and confirm

To resolve this problem, follow these steps:

Click Start, click Run, type Regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
Exit Registry Editor.
Click Start, click Run, type services.msc, and then click OK.
Right-click the following services one at a time. For each service, click Restart:
COM+ Event System
COM+ System Application
Microsoft Software Shadow Copy Provider
Volume Shadow Copy
Click Start, click Run, type cmd, and then click OK.
At the command prompt, type vssadmin list writers, and then press ENTER.
If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps.

If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Note The last command may not run successfully.
At the command prompt, type vssadmin list writers, and then press ENTER.
Confirm that the VSS writers are now listed.