Backup Exec 12.5 SP 2 + System State error

[gcjv]

Hello,

Currently backup exec is failing all his backup tasks because of the following error:
Final error: 0xe000fedd - A failure occurred accessing the object list.
Final error category: Resource Errors

Errors
Click an error below to locate it in the job log
Backup- System?State V-79-57344-65245 - A failure occurred accessing the object list.

Exceptions
Click an exception below to locate it in the job log
Backup- System?State The item System?State\System Files\System Files in use - skipped.

The .DR file that is required for Intelligent Disaster Recovery is not updated.

The consistency check of the snapshot for the Microsoft Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database and transaction logs ntds was successful.
V-79-57344-65245 - A failure occurred accessing the object list.

The item System?State\System Files\System Files in use - skipped.
The .DR file that is required for Intelligent Disaster Recovery is not updated.

I already looked in the KB, but didn't find any solution for this.

Could someone tell my how I can fix this?
Thanks for you help!

[CraigV]

Try reinstalling the RAWS agent, and make sure AOFO is also installed.

[CraigV]

Try reinstalling the RAWS agent, and make sure AOFO is also installed.

[gcjv]

Hello,

I did those things and the backup still fails. Also, after the backup failed, SQL uses up to 3GB of ram!

Set type               : Backup
Set status             : Completed
Set description        : Backup 00001

Resource name          : \\SRV\System?State
Logon account          : 
Encryption used        : None

Error                  : e000fedd - A failure occurred accessing the object list.

Agent used                     : Yes
Advanced Open File Option used : Microsoft Volume Shadow Copy Service (VSS)

Byte count             : 10.792.882.833 bytes
Rate                   : 409,00 MB/Min

Files                  : 7.086
Directories            : 1
Skipped files          : 1
Corrupt files          : 0
Files in use           : 0

Start time             : zaterdag 12 september 2009 0:46:39
End time               : zaterdag 12 september 2009 1:11:47

Media used             : B2D000001
File was skipped       : System?State\System Files\System Files


I've got also another error...

Set Detail Information - Backup \\SRV\Microsoft SQL Server "MICROSOFT##SSEE"
Set type               : Backup
Set status             : Completed
Set description        : Backup 00001

Resource name          : \\SRV\Microsoft SQL Server "MICROSOFT##SSEE"
Logon account          : 
Encryption used        : None

Error                  : e0008485 - The item could not be opened while in use.

Agent used                     : Yes
Advanced Open File Option used : Microsoft Volume Shadow Copy Service (VSS)




Byte count             : 2.607.732.208 bytes
Rate                   : 1.156,00 MB/Min

Files                  : 0
Directories            : 0
Skipped files          : 0
Corrupt files          : 0
Files in use           : 0

Start time             : zaterdag 12 september 2009 0:41:04
End time               : zaterdag 12 september 2009 0:43:13

Media used             : B2D000001

[gcjv]

Can someone help please?
I'm not able to backup System State at all.

[gcjv]

I believe I found the error:

BEREMOTE: [09/22/09 14:58:31] [0000]     [45384] 09/22/09 14:58:31 Status 0x0000007B returned calling FindFirstFile for \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy200\watchguard\wsm11.0\wmserver\..\apache\bin\apache.e... in brUtil::GenerateFileList
BEREMOTE: [09/22/09 14:58:31] [0000]     [45384] 09/22/09 14:58:31 brUtil::SetObjectsList( :( Failed to apply the component exclusion list
BEREMOTE: [09/22/09 14:58:31] [0000]     [45384] 09/22/09 14:58:31 Status CODE (0x0000007B) generating Component System Files file list in SHADOW::OpenComponent
BEREMOTE: [09/22/09 14:58:31] [0000]     [45384] 09/22/09 14:58:31 Informational: calling IVssBackupComponents::SetBackupSucceeded with status FALSE for component System Files in SHADOW::OpenComponent
BEREMOTE: [09/22/09 14:58:31] [0000]     [45384] 09/22/09 14:58:31   AD:Status FS_OBJECT_LIST_FAILURE (0xE000FEDD) calling FS_OpenObj in SystemState::OpenObj:172

It looks like this error: http://seer.entsupport.symantec.com/docs/326350.htm

Could someone help me to solve this? Thanks

[pkh]

Go to the server that is having the error and check whether you can backup the system state using ntbackup.  ntbackup is the built-in back-up program provided by Microsoft.  Just start up a command prompt and key in ntbackup.  You can just select to backup the system state only.  See what errors do you get.  If the system state cannot be backed up by ntbackup, then BE will fail too.

What is the OS of the server in question?

[gcjv]

It's an SBS 2008.
I'm not able to use NTBACKUP because i have a RD 1000 (DELL).

However I googled and someone else got the same problem:
http://209.85.229.132/search?q=cache:GDyaXwO8fi4J:www.experts-exchange.com/Storage/Backup_Restore/Ba...

"

MonyMony:

I had not seen the particular issue posted until now and had been working with Symantec one and off on this issue for the past two weeks.  We resolved this by going to the registry under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wmserver_service
 

In ImagePath correcting the path as the entry appeared incorrect.  The entry on our server contained "\..\" which was causing the backup to fail..  

We changed the path from:

"C:\Program Files\WatchGuard\wsm10.2\wmserver\..\apache\bin\apache.exe" -k runservice -f
"C:\ProgramData\WatchGuard\wmserver\conf\httpd.conf"

To:

"C:\Program Files\WatchGuard\wsm10.2\apache\bin\apache.exe" -k runservice -f
"C:\ProgramData\WatchGuard\wmserver\conf\httpd.conf"
 

After this the System State backup ran correctly and we are not noticing any issues with Watchguard Management Server either.

Hope this helps!"

[pkh]

I am glad you solved your problem.

I was suggesting that you use ntbackup as a test.  Since the system state is pretty small, you can back it up to disk.

[gcjv]

It would be nice that a Symantec responsable could create a KB on this...

[David_Levine]

This issue is actually documented in the Symantec KB here:

http://seer.entsupport.symantec.com/docs/337876.htm