[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 10519
  • Last Modified:

Backup Exec is giving me an error and I cannot figure out why the backup is failing. Failure querying the Writer status.

Backup Exec is giving me an error and I cannot figure out why the  backup is failing other than possible space related issues.  Failure querying the Writer status.  Below is the error message.  Could this be a space issue.?

Error:
Job ended: Tuesday, January 29, 2008 at 4:30:25 AM
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors

Backup- SERVERNAME- AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Registry, Writer ID: {xxxxxxx-xxxx-xxxxx-xxxx-xxxxxxxxxxx}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Failed during prepare snapshot operation (8).
Backup- \\FILE SERVERNAME\D: FILE SERVERV-xx-xxxxx-xxxxx - AOFO: Initialization failure on: "\\FILE SERVERNAME\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: COM+ Class Registration Database, Writer ID: {xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Failed during prepare snapshot operation (8).
Writer Name: Registry, Writer ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Failed during prepare snapshot operation (8).

0
just_survivin_12
Asked:
just_survivin_12
1 Solution
 
ryansotoCommented:
How much memory do you have in your machine?
I was getting the same issue and I talked to a symnatec engineer about it and they had my put in the /3b switch in my boot.ini file.
I felt this was a futile attempt at an answer but it turned out it worked.
0
 
just_survivin_12Author Commented:
I have about 380 mb left in my memory.  I am currently looking at freeing up some space, but I really need to get a good backup.  What switch are you talking about the " /3b in boot ini "  can you illustrate.  Or should we just call the Symantec guy too?
0
 
ryansotoCommented:
Here is my boot.ini


boot.txt
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
scrathcyboyCommented:
"Writer Name: Registry, Writer ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Failed during prepare snapshot operation (8)."

I think this last message is giving you the key.  The VSC service on the system is failing to correctly snapshot the crucial registry files in the time allotted to it.  YOu could increase the number of reads of data before failure, or you could backup the system state SEPARATE from the rest of the drive.

This problem can also happen because backup exec's drivers for your particular backup device are not correct or up to snuff, that is a big problem on failed backups, the drivers for the backup device are not working correctly.

The other thing you need to try is to choose in the backup setup -- erase the tape before backup.  i.e. do not try to "ADD" a backup to an existing backup.  That is also a common failure of this software.
0
 
Iamthecreator OMAdministrateur Systeme et ReseauxCommented:
Apply the latest service pack and hotfixes on you Windows OS
Also apply the following patch for VSS
I can go in great detail about the issue and also the reason I am asking you to apply the SP and the patch but am unfortunately a little short of time.
Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues
http://support.microsoft.com/kb/940349
I may post later
Also refer to the following articles
Backup jobs fail with "out of memory" error or memory and handle leaks appear when creating snapshots with Microsoft Volume Shadow Copy Service providers.
http://support.veritas.com/docs/273562 

Backup fails with the error "AOFO: Initialization failure on: "\\<Server Name>\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0x8007000E): Ran out of memory"
http://support.veritas.com/docs/278779 



Why backups can fail with a "V-79-57344-34110 - AOFO: Initialization failure" when the Advanced Open File Option (AOFO) is selected in the Backup Job Properties
http://support.veritas.com/docs/275975 
0
 
just_survivin_12Author Commented:
I will try some of these solutions and get back to you guys.  Time is very short at this moment.  
I will post any additional errors I encounter after trying fixes.  This one is messed up
0
 
mmenteleCommented:
This can also happen if your program is installed on a drive that is low on space...
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now