cancel
Showing results for 
Search instead for 
Did you mean: 

Backup fails with the error - AOFO: Initialization failure on: "Shadow?Copy?Components"

huskydog1977
Level 2
Dear Experts,

I have been experiencing issues with Backup Exec job failure and need your assistance.


[Job Completion Status]
Job ended: Tuesday, June 09, 2009 at 5:50:12 AM
Completed status: Failed
Final error: 0x80042306 - 0x80042306 (2147754758)
Final error category: Other Errors


[Error Message]
Backup- G: - AOFO: Initialization failure on: "Shadow?Copy?Components". 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.

[Event Log (System)]
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 20
Date: 6/9/2009
Time: 5:47:15 AM
User: N/A
Computer: servername
Description:
The shadow copies of volume F: were aborted because of a failed free space computation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 58 00 ......X.
0008: 00 00 00 00 14 00 06 c0 .......À
0010: 02 00 00 00 9a 00 00 c0 ....š..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


[My Environment]
Symantec Backup Exec 12.5 for Windows Servers
Media Server: Version 12.5 Rev. 2213
Installed Updates: Service Pack 2, Hotfix 322898

OS: Windows Server 2003 R2 (32bit)
Version 5.2 R2 (Build 3790.srv03_sp2_gdr.090319-1204:Service Pack2)


[Steps I took]
1. Rebooted server as http://seer.entsupport.symantec.com/docs/290987.htm recommended.
     After VSSADMIN LIST WRITERS command, the writers are all showing a state of "Stable."
     However, the job still fails.
2. Checked Microsoft Software Shadow Copy Provider Service and the Volume Shadow Copy Service.
     Both services are set to "Manual" and currently NOT running.
      I am wondering if I should set them to "Automatic" and force then running.


[Other Information]
I do not use AOFO from the begin with. I don't know why AOFO error is showing.

Highly appreciate if any help can be provided.
1 ACCEPTED SOLUTION

Accepted Solutions

huskydog1977
Level 2
So after excluding  "System State" and "Shadow Copy Components" from Backup selections, job completed without any issues.
This is not really solving the issue, but at least meeting our requirement.

View solution in original post

3 REPLIES 3

CraigV
Moderator
Moderator
Partner    VIP    Accredited
"The shadow copies of volume F: were aborted because of a failed free space computation." <-- that is interesting!
http://support.microsoft.com/kb/833167 <-- this might clear that up.

Lastly: http://seer.support.veritas.com/docs/265927.htm

huskydog1977
Level 2
 Hi CraigV,

Thanks for your comment.

For http://support.microsoft.com/kb/833167, I've already downloaded and tried to install. Basically it cannot be installed if SP2 is installed. SP2 is newer and hotfix is not necessary.

For http://seer.support.veritas.com/docs/265927.htm, I am wondering if it's safe to set both Microsoft Software Shadow Copy Provider Service and the Volume Shadow Copy Service "Automatic" and force running.

[Additional Information]
I called Symantec support in my country. A tech guy said if rebooting server doesn't solve the issue, call Microsoft. Hey, thank you for your BRILLIANT support!!

Anyway, I called the support again and talked to another guy a few minutes later. He mentioned that if system recovery is not required, I can omit "System State" and "Shadow Copy Components" from Backup selections. He says selecting this 2 components will initiate Volume Shadow Copy Service and end up failing my backup jobs.

Now, I excluded these 2 component and waiting for the result. I will update the result tomorrow.

huskydog1977
Level 2
So after excluding  "System State" and "Shadow Copy Components" from Backup selections, job completed without any issues.
This is not really solving the issue, but at least meeting our requirement.