I want to setup Hyper-V VMs with a shared vhdx or vhds virtual disk. I have a W10 VM that has the main file space and setup a shared folder to allow two other W10 VMs to map a drive and share the data. I suspect performance may be better is I use a shared VHD in Hyper-V. The host computer is Server 2016 Std. I can create the shared VHD but when I try to attach it to a VM, I get an error that says the VHDX location doesn't support sharing. I found several articles saying I need to enable it but I cannot find where to enable it. I have two 2016 servers in a datacenter and several VMs on each but no clustering is setup.
We are a small outfit, and I am running 4 webservers, 2 SQL servers, and a Reporting Server as VM's in Hyper-V on WinServer2016 (datacentre edition). I want to be able to have a failover from this machine (Dell R620) to a copy of it. The servers are not on AD - I'm a dev wearing a Admin hat badly.
Is there something out there that can do this?
Already have replication running from [live] machine to [backup/failover] machine.
However, if stuff goes down, all info that was committed to sql databases since last replication would be lost, and this is the main problem.
I have no AD training at all, and the current setup is a mongrel that started as a BusinessServer2003, migrated to 2008 then to hybrid cloud based by previous employee that has left. I employed a tech thereafter for a period but fired him after he proved incompetent and in process of stealing source code. Sigh.
Not sure if this is do-able, but I want to attack the biggest headaches first.
Should Hyper-V replication carry changes to underlying VM settings, such as increasing memory, adding a vCPU, or in this specific case, adding a NIC?
I'm running Server 2016 Datacenter edition and Hyper-V replication is via Failover Cluster Manager and a replication broker. I added a NIC to two VM's this morning, verified that replication is working, and the replica's do not have the new NIC after a half-hour and multiple successful replication cycles.
I'm running this on Windows Server 2016 Essentials. There's a single local VM set up in the Hyper-V. The guest VM is Windows 10 Pro. Again, that VM runs from the same physical server.
When the host OS boots up, and I attempt to run this VM, it sometimes shows this error during the boot process of the guest/VM:
The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.
Note that there are no other users or VMs present. This VM is set up on the same physical host machine. Also waiting for a few minutes doesn't help. The only resolution is not force-close the VM and restart it.
Any idea how to fix this?
Been trying to test Hyper-v 2016 this afternooon but I am unable to get my R630 to boot from the USB I configured using the following instructions https://technet.microsoft.com/library/ee731893(ws.10).aspx
I used the exact same guide on Hyper-v 2012 R2 with no problems.
Anyone have any luck with this?