V-79-57344-65245 Shadow?Copy?Components Shadow?Copy?Components

[Aaron_English]

I'm using BE V10.1 Rev 5629 and all other updates on a Windows 2003 R2 server SP1. We get the V-79-57344-65245 (A failure occurred accessing the object list.
- The item Shadow?Copy?Components\System?Service\File Server Resource Manager\FSRM Global Configuration in use - skipped.

I have tried installing the hotfixes suggested in the following kb: http://seer.support.veritas.com/docs/280671.htm

I have also installed the follwoing Veritas updates:
http://seer.support.veritas.com/docs/282818.htm
http://seer.support.veritas.com/docs/284103.htm

None of the hotfixes or updates have made a difference.

All ther backup jobs, both locally and on remote servers, finish successfully. But any job that backs up the Systems State, either to tape or to disk, fails with the error message above.

I ran VSSADMIN and no errors were reported.
http://seer.support.veritas.com/docs/261993.htm

NTbackup is able to successfully backup the System State.

I do not use AOFO, and there are no messages in the Application or System event logs.

Any suggestions on what I can try next would be greatly appreciated.

[Louis_McCutchen]

I'm having this same problem. It happened with the latest version of 10.1 and upgrading to 11d didn't resolve the problem. I can back up without problem using ntbackup.

[jesus_asphalt]

The application is too buggy and just doesn't work well in 2003.

That's why the symantec support jockeys haven't posted an answer.

Try segregating everything by OS version first. Don't share selection lists or use policies to create the jobs. They add to your misery.

I am battling a similar issue and have only gotten things to work by separating everything by OS version and application version no policies no shared back up selection lists.

I recommend Bacula at www.bacula.org. If you are smart enough to read their documentation and edit a text file, I think you will find it an excellent alternative.

[Deepali_Badave]

Hello,

We suggest you to take a backup on the backup to disk folder and verify the result.

Also what errors are ocurring in the event logs.

Regards,

[Louis_McCutchen]

Same error in backup to disk folder :

V-79-57344-65245 - A failure occurred accessing the object list.

The item Shadow?Copy?Components\System?Service\File Server Resource Manager\FSRM Global Configuration in use - skipped.


Only error recorded in event log is application error:

Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:34113
Date:12/5/2006
Time:6:32:01 AM
User:N/A
Computer:FILESERVER
Description:
Backup Exec Alert: Job Failed
(Server: "FILESERVER") (Job: "Shadow Copy Compnents") Shadow Copy Compnents -- The job failed with the following error: A failure occurred accessing the object list.


For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

[Aaron_English]

A backup to disk receives the same results:
------------------------------------------------
Job Completion Status
Job ended: Saturday, December 16, 2006 at 1:02:08 AM
Completed status: Failed
Final error: 0xe000fedd - A failure occurred accessing the object list.
Final error category: Resource Errors

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


Errors
Click an error below to locate it in the job log
Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65245 - A failure occurred accessing the object list.



Exceptions
Click an exception below to locate it in the job log
Backup- Shadow?Copy?Components Shadow?Copy?ComponentsThe item Shadow?Copy?Components\System?Service\File Server Resource Manager\FSRM Global Configuration in use - skipped.

-----------------------------------------------------------------------------

I am able to successfully use NTBACKUP to backup the system state without problem.

[Louis_McCutchen]

Check the post in the 11.x section for a fix that seems to have worked for me :

http://forums.symantec.com/discussions/thread.jspa?threadID=69678

[Aaron_English]

I think that may have fixed the issue. A test backup to disk job completed successfully.

---------------------------------
Open notepad and save a file into c:\system volume information\srm\reports folder and save the file with .xml extension. Doesnt matter what the first part of the filename is just as long as the extension is .xml.

You may have to grant some right to get into system volume information folder. Remember its hidden.


VSS is looking for xml file to be populated in this folder and the Microsoft OS is not putting them there.

[Fanflame]

Dear Aaron,

You may still be monitoring this issue; But I have exactly the same issue as you did. I have tried what you have said and just wondered if this fixed your problem? I tried everything and having the same version as you have now tried your fix of adding an .xml file in the to the c:\system volume information\srm\reports folder.

I am now running a full back-up but just wondered if you have any other tips for me ??

Many thanks

Fanflame

[Fanflame]

Dear all,

If you are having this issue and are reading this Thread then I just want to let you know that this did the trick for me . After weeks of mess and Back-up failures creating a n log.xml file in the c:\system volume information\srm\reports folder sorted it!

Thanks guys for your recorded suggestions.

Fanflame