only Failed SureBackup Jobs after upgrading to v8

[odi66]

Case # 01673867

Hello,

Since Updating from V7 to V8 some Weeks ago we experience our surebackupjob to fail every day.
The Job is testing both Domaincontrollers, one exchangeserver and one additional server.
Stangely the job shows that the DC-Scripts run OK and only fail with exchange.
If i log into the exchangeserver in the surebackupjob i can see that no domaincontroller is available.
Both DC's are up and running in the Surestore Environment but in the eventlog i can see that Directory Services can not start.

i've found out that using the burflag on one DC and rebooting will result in a positive surebackupjob.
as mentioned this behaviour occured since the update (of course it could be the result of other changing in the network?!)

did anyone have the same experience?

[foggy]

How the DC's are added to the SureBackup job, via application group or linked backup job? SureBackup performs an authoritative restore of the DC in the application group, so having two of them there and designating both as DC's makes them compete for supremacy, not sure how the sync-up process could succeed before the upgrade. You can disable DC and GC roles for one of the DC's and set it to start some time after the first one.

[odi66]

Thank you foggy.
Yes, sounds logical.
This Job exist for 1 Year at least. Allways Green.
Will give it a try and remove the DC-Scripts from the second one

[odi66]

unfortunately now the DC do not even come up!!!

Windows-Start-Manager

\windows\system32\winload.exe not found

Status 0xc000000e

I've moved the VM to different store and host.
I've resettet CBT.

nothing helps.

Cloning the Machine with the vcenter will work fine.

[veremin]

unfortunately now the DC do not even come up!!!

You mean the one that still has DC and GC roles assigned? If so, it'd be better to contact support team for closer investigation. Thanks.

[odi66]

As requiered the support case ID is in my first Post.

I'd like to get rid of this failure a little faster. Its a inconvenient feeling to know that the DC is in a unrecoverable state.
I'm writing here hoping someone else had a similar occurence and solved it already.

I've done a testrestore and can see that \windows\system32\winload.exe is at its place.
So for any reason the windows-start manager will not find winload.exe

[odi66]

It looks like Bitdefender was the Problem.
After removing, the DC's are comming up again.