Highlighted

System State Backup Problem (Final error: 0xe0000352)

Hi Experts,

I'm using Windows Server 2008 R2 Ent, 64bits and Symantec Backup Exec 2010 R3.

One of my backup jobs for system state has been failing with the following errors:

-> Job ended: Monday, April 20, 2015 at 6:46:11 AM
-> Completed status: Failed
-> Final error: 0xe0000352 - The specified volume does not exist. Recreate the volume, and then try the job again.
-> Final error category: Resource Errors

-> For additional information regarding this error refer to link V-79-57344-850

No problem backing up other data, only system state.

Had checked "vssadmin list writers" and no errors.

Had searched and google around, but still could not find any solution yet.

Can anybody help me?

Thank you.

 

- Blue

3 Replies

Is BE 2010 R3 and the remote

Is BE 2010 R3 and the remote agent completely patched up ?

Try these KBs -

https://support.symantec.com/en_US/article.TECH136185.html

https://support.symantec.com/en_US/article.TECH129238.html

Also, assign a drive letter to the system reserved partition and try again.

Lastly, does a native Windows backup (wbadmin) of system state complete successfully ?

Hi VJware, Thanks for your

Hi VJware,

Thanks for your reply.

Is BE 2010 R3 and the remote agent completely patched up ?

-> Yes.

https://support.symantec.com/en_US/article.TECH136185.html

-> Patch 980794 is not applicable to our system.

-> Had tried ExcludedBinaryPaths, but not working.

https://support.symantec.com/en_US/article.TECH129238.html

-> Does not find it helpful.

Also, assign a drive letter to the system reserved partition and try again.

-> What do you mean?

Unable to test wbadmin as the feature is not enable.

However, I don't have any problem backing up the system state on other servers running the same OS version. Weird?

 

Open Disk Management and you

Open Disk Management and you would see a small volume marked as System Reserved Partition. Right-click and choose Assign Drive Letter.

Rerun the backup. If this still fails, would recommend to enable wbadmin and run a native backup to isolate if the issue is with system state or BE.