Backup Exec 11D fails to backup DC

[cookie_monster]

I'm having an annoying issue with BE it keeps failing to backup the system state on a new DC with a corrupt files error indicating that the system state is corrupt. If i run a backup and verify of the system state with windows backup it reports no errors.

The server seems to be running fine i haven't seen any errors and Netdiag and Dcdiag don't report any issues i've also run sfc and it didn't solve the issue.

This server is running 2003 R2 SP2 and is being backed up using a BE 11D remote agent, i'm backing up another DC via remote agent without issue and as far as i can tell they're setup the same.


When i run the agent in debug mode this is the error that seems to indicate that system32 is missing, it's like it thinks it's a file

[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:

I found this post online where Veritas suggested it can be causes by installing from slipstreamed media (WTF) well i did install from a slipstreamed 2003 SP2 CD but i've done that on other servers without issue.

I spoke a long time with the Veritas support and they find out that there is
a missing entry in the active directory which Backup Exec can not handle.
Here the details:

(log from beromte tool)
beremote: [5772] 12/12/06 11:54:08 brUtilenActiveObject ´
Information: Active Object is a File C:\windows\system32\sfc.exe beremote:
[5772]
12/12/06 11:54:08 brUtil:etupDLE Succesfully set up to read the object 'C:'
'\windows\system32\' '' 'c:\windows\system32\' beremote: [5772] 12/12/06
11:54:08 brUtilenActiveObject Information: Active Object is a File
C:\windows\system32\
beremote: [5772] 12/12/06 11:54:08 brUtilenActiveObject Error: 0x2000FE07
Could not find the object c:\windows\system32\

As you can see the entry "c:\windows\system32\" is missing. Why ever...
The sad that the problem is because I installed the server with a slip
streamed cd rom.

The povided me two solutions:
- install the server new (no comment ...)
- using sfc.exe (which I did, the same error as every)

[Michael]

Can you use BE to backup to a file (like you can with NTBackup) and does this work?

Are there any updates you can apply to BE from their website?

If all else fails use NTBackup. It works very well for me.

[cookie_monster]

Yep i've used a backup to file and it fails with the same error.

All updates are applied.

I've tried NTBackup and it works but apparently NT backup skips corrupt files and doesn't log it even on detailed logging

From Symantec:

Another way to confirm that this file is corrupt is by running a backup of the System State with NT Backup. Note** NT Backup will not fail with any errors during the backup, instead the report from the backup will need to be reviewed.

[Michael]

It's really odd I have to say. If there was a problem with the system state, you'd know about it, as it includes the registry and active directory (if the server's a DC).

I know with R2 you have to update the schema. I wonder if this is the problem? There are minor differences with 2003 SP2 and 2003 R2 SP2.

[cookie_monster]

True but my other R2 DC's backup ok.

I've got a horrible feeling that it's to do with the CD being created using Nlite.

https://forums.symantec.com/syment/b...ssage.id=37952

[Michael]

You may be right there, it seems the most likely source of the problem. The article mentioned re-installing 2003 SP1 or SP2 (whichever you're using), but I am not sure how this works as you have R2 installed on top, and once that's installed, you cannot uninstall or re-install the SP you're on.

This could get very messy indeed. As a short term solution, use NTBackup and perform a server re-build during the summer?

[cookie_monster]

You can't reapply SP2 to an R2 box? I'm running 2 DC's that were R2 SP1 then upgraded to SP2 can i not reapply SP2 to them?

[Michael]

If you were running 2003 SP2 and installed R2, I know for a fact you cannot uninstall SP2, but as for re-installing SP2, I may be wrong and I hope I am for your sake

If you go into Add/Remove programs, and you installed 2003 SP1, then SP2 manually and then R2, then SP2 will not be listed.

[cookie_monster]

I might have to install a VM and see if i can reapply SP2.

I have an R2 box that was SP1 R2 then upgraded to SP2 and SP2 is listed (it was R2 before SP2) but as this one was slipstreamed it's not.

I suppose as a last resort i could DCpromo if to a member server and try it so i don't trash a DC then DCpromo it back to a DC if it works.

[cookie_monster]

Well i've just installed a 2003 SP2 VM then made it R2 then ran DCPromo, i then re applied SP2 and it all seems ok so far the event log says "Windows Server 2003 Service Pack 2 was installed (Service Pack 2 was previously installed)."

[cookie_monster]

Ok re applied SP2 this morning and a backup completed successfully so things are looking up

This will be worth remembering for anyone that uses Nlite and Backup Exec.



Glad that worked as a rebuild with different media would of been tricky, Nlite was the only way i could get the DL140 to build as F6 with a USB floppy just resulted in a blue screen or not finding the RAID controller.

[Michael]

Good to hear it worked cookie_monster

[DMcCoy]

I really wouldn't use nlite to make server disks, just use the provided slipstream methods :P

All you really need to do is extract the MS boot sector from a disk, and the rest is easy.

[cookie_monster]

I haven't used Nlite for servers before and i won't again, the only reason i used it was out of desperation due to RAID driver issues.

HP DL140 G3, anyone got one?