So today we had to failover to one of our standby VM's due to it's physical counterpart suddenly dying. It went well for the most part but I did find a few things that hung me up.
The protected machine is (was) a Windows 2008r2 DC and our standby server runs 2012r2 Hyper-V.
Plan for the initial boot time. Booting, installing the services disk, network configuration and rebooting took probably 30 min at least.
Installing the integration services disk assigned the virtual optical drive the same letter as one of our mapped drives. I had to go into disk management and reassign them
Right away I noticed our mapped drives did not work so I had to reshare the data volume and remap it. Users then reported that all their files were "read only" so I had to go back and assign rights to the shared volume.
Fail back should be fun. I am thinking the server probably has a bad motherboard and the RAID array is OK. If it is I will simply do a live restore of the data volume from the newest backup as opposed to a BMR. Fingers crossed that the next scheduled backup runs w/o anything funky happening. I paused the export for the time being for obvious reasons.
I would love to hear any advice or feedback about the permissions and drive mapping issues.
