Forum Discussion

JesseP's avatar
JesseP
Level 3
18 years ago

Initialization failure on: "Shadow?Copy?Components

A client of mine is running BackupExec 10d on an Windows Server 2003 SBS w/SP2 system.  Periodically the nightly backup will fail with the following error:  "AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).  Snapshot provider error (0x8007000E): Ran out of memory."

Based on the referenced Veritas Support Document (#278779) this is being caused by a "problem with non-paged pool allocation.", referring you to Microsoft KBase 887827.  The event log entry referenced in the document does not show up in the System Log, however there are Volsnap event errors (ID 21) listed: "The flush and hold operation for volume C: was aborted because of low available system memory."

The update referenced in the KBase article does not apply as SBS SP2 installed newer versions of the files referenced in the article.

Disabled Shadow Copy for C: and purged all related devices from Device Manager and then re-enabled Shadow Copy.  This has not corrected the issue.

Any suggestions would be appreciated.

  • Were you able to make any progress on this issue?

    I am having the same issue on a windows 2000 box running Backup Exec 10.1 rev5629. I looked through the suggested hotfixes provided by Symantec and Microsoft, but nothing is pertains to Windows 2000 servers. Everything is for 2003.

    Symantec phone support is no help, seeing as they keep you on hold for 30+ minutes and then hang up randomly. 

    Anyone have any insight on this issue? All replies are appreciated.
  • I'm afraid not.  Nor have I been able to find anything concerning the VSS error ID 21 that I'm finding in the event logs.  There is an MS Kbase article that talks about it (KBase 907875) but the only thing it has to say is that this can be caused by drive fragmentation and that I should defragment the drives on the server.  This is of no help since there is little to no drive fragmentation on that box.  It gets defragmented on a regular basis.
     
    I would greatly appreciate it if someone at Symantec would offer up some suggestions as to the cause of this issue.  At the very least, a response acknowledging the issue would be nice. 
  • I was able to get this working. The VSS in question was on a virtual server, so I decided to reboot the virtual server last evening in hopes that it would clear out anything in the cache pertaining to VSS settings or however it is setup. I checked the backup this morning after a successful reboot last night and it was successful.

    Note that the backup exec was not installed on the virtual server, only the agent was.

    Im not sure if that helps you any, but it is worth a try if you haven't tried it already.  Im assuming that during startup of the VSS something can be corrupted if not started properly.