Forum Discussion

manioro's avatar
manioro
Level 3
14 years ago

AOFA: Initialization failure

Hi,

I have noticed that my recently my daily and weekly file backup completes the backup process with following exception:

 

Backup
 - AOFO: Initialization failure on: "F:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

My AOFO is set to Automatically select open file technology, I have never changed it. This exception has been appearing since I added new iSCSI drive to our server. 

Does anyone know how to resolve this issue

  • I called Microsoft Support and they advised it is because of the nonpaged pool memory not having enough resource, their fix is to upgrade the server to x64 or create a smaller LUN. They have also removed /3GB /USERVA=3030 from the boot.ini, after server restart everything seems to be fine with my backups.

    They have also advised to applying following fix if above did not work: http://support.microsoft.com/kb/312362

    Hope it will be useful for someone else.

  • Hello

    Refer to the below article.

    http://www.symantec.com/docs/TECH76626

  • Thanks for suggestion, I'll give it go and will check once the back up is done.

     

    Kind Regards
    Lukasz

  •  Hello,

     

    If its W2003, Install the VSS rollup patch : http://support.microsoft.com/kb/940349 (REBOOT REQUIRED)

     

    Hope this helps...

  • Still the same issue, I'm just applying a following updates and will keep you updated after back up finishes. Hope it will help.

  • I called Microsoft Support and they advised it is because of the nonpaged pool memory not having enough resource, their fix is to upgrade the server to x64 or create a smaller LUN. They have also removed /3GB /USERVA=3030 from the boot.ini, after server restart everything seems to be fine with my backups.

    They have also advised to applying following fix if above did not work: http://support.microsoft.com/kb/312362

    Hope it will be useful for someone else.