Backup Exec 11D fails to backup system state

[buxton1]

I'm having an issue when backing up one of our DC's, i receive the errors below.

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

Backup- \\SERVER2\System?State \\SERVER2\System?StateWARNING: "\\SERVER2\System?State\System Files\System Files" is a corrupt file.
This file cannot verify.
Verify- \\SERVER2\System?State \\SERVER2\System?StateWARNING: "System Files" is a corrupt file.
This file cannot verify.

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

I have one member server running Backup Exec 11D and this backs up 2 Domain Controllers via agents. One DC backs up ok every night but the second DC generates this one error but seems to backup every thing else on the drive ok. If i run a backup with windows backup, it works and verifies ok.
The second DC is only a couple of weeks old but i've never seen an error on the box and Netdiag and DCdiag don't show any issues in fact it's working perfectly other than this backup error.

Both DC's are running Windows Server 2003 SP2 R2 and the member server 2003 SP2. The only difference is that this last DC was installed from slipstreamed media.

I enabled debug logging but i'm not quite sure which file is the issue, i've posted what i think is the problem area if anyone can shed any light i'd be gratefull.

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

[2552] 06/19/08 10:54:32 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\windows\system32\' 'setupapi.dll' 'c:\windows\system32\setupapi.dll'
[2552] 06/19/08 10:54:32 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\setupapi.dll
[2552] 06/19/08 10:54:32 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\windows\system32\' 'sfc.dll' 'c:\windows\system32\sfc.dll'
[2552] 06/19/08 10:54:32 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\sfc.dll
[2552] 06/19/08 10:54:32 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\windows\system32\' 'sfc.exe' 'c:\windows\system32\sfc.exe'
[2552] 06/19/08 10:54:32 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\sfc.exe
[2552] 06/19/08 10:54:32 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\windows\system32\' '' 'c:\windows\system32\'
[2552] 06/19/08 10:54:32 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\
[2552] 06/19/08 10:54:32 brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object  c:\windows\system32\
[2552] 06/19/08 10:54:32 Status FS_NO_MORE (0x2000FE07) for Component System Files in SHADOW::ReadComponent
[2552] 06/19/08 10:54:32   AD:Status FS_READING_OBJECT_FAILURE (0xE000FEDF) calling FS_ReadObj in SystemState::ReadObj:233
[2552] 06/19/08 10:54:32 Informational: Closing Component 'System Files'
[2552] 06/19/08 10:54:32 Informational: calling IVssBackupComponents::SetBackupSucceeded with status 'FS_READING_OBJECT_FAILURE (0xE000FEDF)' for Component

'System Files' in SHADOW::CloseComponent
[2552] 06/19/08 10:54:32 Writer SYSVOL include file list:
[2552] 06/19/08 10:54:32 Writer SYSVOL exclude file list:
[2552] 06/19/08 10:54:32   o: c:\windows\ntfrs\jet\* /s
[2552] 06/19/08 10:54:32   o: C:\WINDOWS\debug\NtFrs\NtFrs*
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\domain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\* /s
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog\* /s
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\staging\domain\NTFRS_*
[2552] 06/19/08 10:54:32 Informational: Opening Writer 'System?State\SYSVOL'
[2552] 06/19/08 10:54:32 Informational: Writer System?State\SYSVOL has no files present to protect in SHADOW::OpenWriter
[2552] 06/19/08 10:54:32   AD:Status FS_EOF_REACHED (0x2000FE0C) calling FS_ReadObj in SystemState::ReadObj:233
[2552] 06/19/08 10:54:32 Informational: Closing Writer 'System?State\SYSVOL'
[2552] 06/19/08 10:54:32   AD:Status FS_EOF_REACHED (0x2000FE0C) calling FS_ReadObj in SystemState::ReadObj:233
[2552] 06/19/08 10:54:32 Component 27389d1d-c2c0-4c1b-a38e9bd9f384ed84 file list:
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\* /s
[2552] 06/19/08 10:54:32 Component 27389d1d-c2c0-4c1b-a38e9bd9f384ed84 Writer's exclude file list:
[2552] 06/19/08 10:54:32   o: c:\windows\ntfrs\jet\* /s
[2552] 06/19/08 10:54:32   o: C:\WINDOWS\debug\NtFrs\NtFrs*
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\domain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\* /s
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog\* /s
[2552] 06/19/08 10:54:32   o: c:\windows\sysvol\staging\domain\NTFRS_*
[2552] 06/19/08 10:54:32 Informational: Opening Component '27389d1d-c2c0-4c1b-a38e9bd9f384ed84'
[2552] 06/19/08 10:54:32 Generating Component: 27389d1d-c2c0-4c1b-a38e9bd9f384ed84 exclusion list:
[2552] 06/19/08 10:54:32    Adding initial c:\windows\ntfrs\jet\ directory to the backup file list
[2552] 06/19/08 10:54:32    Adding c:\windows\ntfrs\jet\log\  directory to the backup file list
[2552] 06/19/08 10:54:32    Adding c:\windows\ntfrs\jet\log\edb.log to the backup file list
[2552] 06/19/08 10:54:32    Adding c:\windows\ntfrs\jet\log\edb00002.log to the backup file list

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

Can anyone shed any light?

Cheers.

[buxton1]

I appears to be caused by Nlite i found an answer here.

https://forums.symantec.com/syment/board/message?board.id=103&message.id=37952

[Tiz]

Bumping this thread.. I'm having the exact same problem on an SBS 2003 R2 machine with SP2.

According to the other thread, you're supposed to reinstall (reapply) SP1. But what exactly do you do if you have a more recent install - like we do - with SBS 2003 R2 and with SP2 already included? Do you only reapply SP1? Or do you reinstall SP2 or the R2 part as well?

I hope someone can elaborate. Thanks!

[buxton1]

Hi

My server was 2003 R2 Standard with SP2 not SBS it was also a DC but the solution should still work the same on SBS (remember to get a good backup first).

All i did was re apply 2003 SP2 even though SP2 was already installed and the problem was solved.

[Tiz]

Thanks. Reapplying SP2 did the trick for me too.

By the way, Symantec support says this:

To resolve the corrupt file the customer will have to try the following:

1. If their OS was installed with a Service Pack - such as SP1 for Windows 2003 - they will need to re-apply the service pack and download all Windows updates.

2. If they are using Windows 2003 R2 - they can run an in-place upgrade to R2 and apply updates

3. If the customer does not want to re-install the service pack or apply R2 to their existing OS then they will need to speak with Microsoft to resolve the corrupt file.

So I tried reinstalling R2 first (I'm using R2, right?), which now seems totally pointless. It had no effect at all. I then ran SP2 and that did the trick. Symantec, please update your solution because it's vague and inaccurate. At least to me it still doesn't make sense.

Thanks again for your reply, buxton1.

[buxton1]

Yes i couldn't see reinstalling R2 working either so i just went for reapplying SP2, as you say Symantec could do with making this more clear.

Glad you sorted it.