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
First thing I would suggest is to check you are on the latest service pack (SP3 aka 10.0.3) of SSR (check in Help/About for version details).
If going to SP3 does not help, this will require a support case with either us (Symantec) and/or Microsoft. A memory dump will need to be captured and then analyzed to see what is causing the crash.
Server just crashed again on Chistmas day... SP3 has already been installed(shows as 10.0.3.45857). Memory dumps are enabled, however, it doesn't appear to be making them...which is a bit of a problem since there will be nothing to analyze!