08-13-2015 09:34 PM
Specifics:
Noticed that every time we logged into this server, there was an unexpected shutdown notification prompt (daily). Searched through the logs and found that these, "Windows-has-started-after-an-unexpected-shutdown" event do actually occur once daily around 1700-ish (+/- 30-90 mins). Asked one of the techs if that meant anything to them and they said there was a Symantec job that runs around that time. So we checked on the server and noticed that the Domain Controller job was failing (daily) also. But, just to verify, we initiated a backup at 0900 the following morning and 20-ish minutes later (still during the backup job), the DC BSOD'd again.
It is worth noting that it completely finishes on one of the other DCs before failing on the one in question. I'm currently trying to download and bring over the 2K8 R2 symbols to debug the dump to see if I can identify the faulting module/function but if it's a Symantec DLL and not a MS DLL, I won't have that available.
It is worth noting that in trying to troubleshoot any associated information, the System and Application logs show nothing of note. System shows normal DC-operations, then a 15-ish minute break in events, and then a system startup event. There is nothing of note in the Application log.
In hunting for Symantec logs, I'm not sure if it's relevant or not but I found a log named (PDVFS)[Datetime].LOG under C:\Program Files\Symantec\Backup Exec\RAWS\logs\PDVFS. There are daily logs around the same 1700ish timeframe with 2 entries (which are always the same):
[Datetime] (2852:2856) PDVFS - CPersistentConnection::RemoveConnection: RegDeleteKey failed with error: 2250
[Datetime] (2852:2856) PDVFS - CDiskManager::UnmapDrive: caught exception; error: -536870909
Is anyone aware of anything similar to this that we might need a hotfix/patch for?
08-13-2015 10:10 PM
Does the DC crash if you run a native Windows backup ?
Could you attach the entire Application & System logs of the DC over here ? Thanks.
The PDVFS error indicates an issue with the DeDupe folder however not aware of that causing a server crash. Try running the DC backup to a non-DeDupe storage device as well.
08-13-2015 10:33 PM
The Windows backup is currently running to the same SAN target (CIFS Share) that Backup Exec rights to (just a different folder and probably different data store).
I can't attach the logs because they're on a closed network that I can't bring the logs over from.
Regardless of how the Windows backup runs, I'll test the Symantec Backup to a local physical disk on the physical backup server and see if that changes.
08-14-2015 12:06 AM
The Windows backup to CIFS share succeeded without incident. I'm about to leave for the weekend but will post back on Monday when I can configure a backup job just for the one DC to local physical storage and test that operation.
Also... per another post you were helping someone on, I checked the state of the VSS Writers and they're all showing a State of [1] Stable with No error as all of their Last error: fields.
Thanks.