11-13-2014 07:21 AM
Hello, I need help.
Since BE 2014 sp1 update my file server (virtual server) restarts when starting a backup job.
I have found no information on similar cases, will this be a new option that can be selected? an agent error?
These events are not recorded as events, as it happens, the connection is lost with mapped network drives by customers as well as the RD connections.
In the job history for the server issues an exception stating crash consistent recorded.
11-13-2014 07:39 AM
11-13-2014 08:04 AM
BE 2014 running on a Dell R320
The physical server is a Dell R720 connected via SCSI to a PoweVault MD3220i. Here I have a license for Hyper-V
The backup job is done against this physical server where are hosted, among others, the domain controller, Exchange and file server, respectively existing license database and windows.
Everything works fine except as detailed for the File Server, at first I did not realize that the server is restarted, not finding events and because it is a time where there are no users connected, but as I was making progress in resolving the exception, run live work and see how this virtual server is lost when starting the backup.
All equipment is installed with Windows Server 2008 R2 SP1, then the virtual machines have been updated as patches that were released, while the physical server is maintained with the first version. Could this be the problem?
11-13-2014 05:32 PM
BE 2014 running on a Dell R320
The physical server is a Dell R720 connected via SCSI to a PoweVault MD3220i
I am confused. Is the R720 a separate server? Is BE running in a VM or on the physical R320?
11-13-2014 08:25 PM
Any errors in the Hyper-V VMMS logs ?
11-14-2014 04:15 AM
BE running on physical R320
R720 hace Hyper-V roll
No error on logs.
Now I detected informative saved state events and verify that the virtual server is assigned a different drive for shadow copy of volume G: (volume of data). I'm understanding that it should be assigned the same letter.