I'm trying to help a non-Profit troubleshoot their server, so know up front that I didn't configure this server and until I started helping them out I had never used Systems Recovery 2011(I've had experience a LONG time ago with BackupExec back when it was owned by Veritas).
The issue they are having is that their Server reboots shortly after a full backup is kicked off... usually within 10 minutes. There doesn't seem to be any smoking gun in the Event Logs and it doesn't even record any BSOD info, just an entry stating that the last reboot was unexpected.
Their server has the following Roles: Domain Controller, DNS, DHCP, Exchange and Hyper-V... with Hyper-V serving up 5 VMs. At first I thought the reboot was related to SSR and Hyper-V not playing nice, as originally they had all of their VMs within Hyper-V to only start up if it was previously started. After encountering one of these reboots, I saw two VMs(which are running Linux) in a shutdown state and not running, which would suggest they were put into a non-running state just before the Server unexpectedly rebooted.
I found a few articles talking about similar situations with SSR not playing nice with Hyper-V, such as this article: https://www-secure.symantec.com/connect/forums/system-recovery-20102011-server-2008-r2-and-hyper-v
They all had to do with a Microsoft issue that was resolved by a hotfix(as pointed out here: http://www.symantec.com/business/support/index?page=content&id=TECH127102&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1355890380457TpF2W0yHP68HW0Dt2VTrJ20908d50L729X556)
However, this server already has SP1 installed, which includes this hotfix, and yet it still encounters this issue. The server will just reboot and the backup will be missed. The odd thing is is that the server doesn't always crash and reboot...sometimes it can go a week or two without an incident, sometimes it'll happen 3 or 4 times in the same week... it seems to be hit and miss.
I've since configured their VMs to start up when the server starts up regardless of their last running state... this at least prevents the office for being down for hours instead of just the few minutes it takes the server to reboot.
So with that, I don't know if it is sitll possibly an issue with SSR and Hypver-V not playing nice. Is there anything else that could be causing this lockup? I just don't honestly know where to look next, so any help is appreciated!
-Henry
