Have a client that we are simply providing a dedicated server to them with Hyper-V 2012 installed. They are talking about replicating their entire environment consisting of a domain controller, SQL databases, SharePoint, and much more. Is it really safe to just replicate these entire VM's to another Hyper-V server and spin them up in case of a disaster?
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
-
Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Hyper-V Replicating DC, SQL, SharePoint, etc
- Thread starter KapsZ28
- Start date
Very much depends on the VM replication type/method and the AD structure. Are there any other DCs in the environment? If so you may run into AD replication issues after a DR migration. As an example, for one of my clients, I do a similar scenario, between a pair of Dell T610s running Win2k8R2, and use Hyperoo to do RDX backup and replicate the VM's to the secondary Server where the VMs are built, but not running. It's not a perfect solution but it's point-in-time tested and in budget.
How often is it replicating? If it's in real time, or very short intervals, it shouldn't be a problem. The main concern will be the DC like Nate stated. SP is all database driven. So the restore will just be at the cost of some data loss (The amount lost depends on the replication schedule).
HyperV 2012 should have the ability for an Active/Passive cluster with replication that would be exactly what the client wants. I know the full version does, I just don't know the limitations of HyperV 2012 (assuming you mean the free hypervisor).
HyperV 2012 should have the ability for an Active/Passive cluster with replication that would be exactly what the client wants. I know the full version does, I just don't know the limitations of HyperV 2012 (assuming you mean the free hypervisor).
The replication is real time but sharing a 10mbps connection. Don't know how much data they have. This is the free Hyper-V 2012.
I would like the biggest issue would be the different IP addresses on the replicated VMs. If they hard coded IP addresses instead of DNS, it could be a real issue. Personally I don't see the point of replicating a domain controller VM. I would just setup a second domain controller in the DR site and keep an active connection. Also setup DNS with all the correct A records and IP addresses of the second site.
I believe this client is simply just enabling replication and hoping to spin up all the VMs in the DR site and it will just work.
I would like the biggest issue would be the different IP addresses on the replicated VMs. If they hard coded IP addresses instead of DNS, it could be a real issue. Personally I don't see the point of replicating a domain controller VM. I would just setup a second domain controller in the DR site and keep an active connection. Also setup DNS with all the correct A records and IP addresses of the second site.
I believe this client is simply just enabling replication and hoping to spin up all the VMs in the DR site and it will just work.
Within WS2012 Datacenter Ed. /w Hyper-V, not sure about any other versions as I haven't tested, when setting up replication of a VM you can specify a separate static IP in the options to get around the hard coded IP issue.
But as you mentioned I'd also suggest setting up a secondary DC instead of replicating a single DC VM.
But as you mentioned I'd also suggest setting up a secondary DC instead of replicating a single DC VM.
Within WS2012 Datacenter Ed. /w Hyper-V, not sure about any other versions as I haven't tested, when setting up replication of a VM you can specify a separate static IP in the options to get around the hard coded IP issue.
But as you mentioned I'd also suggest setting up a secondary DC instead of replicating a single DC VM.
I know about that. I don't mean that type of hard coding. Say if they setup SharePoint to point to a DB server and in the SharePoint configuration they entered in the DB server IP address instead of DNS name. Stuff like that becomes an issue.
I know about that. I don't mean that type of hard coding. Say if they setup SharePoint to point to a DB server and in the SharePoint configuration they entered in the DB server IP address instead of DNS name. Stuff like that becomes an issue.
Hyper V replication works best on a Local LAN. I tried using WAN link and it doesn't work worth shit. If you want offsite replication I strongly recommand a product like Veeam to do that. Its expensive but well worth the money.
Hyper V replication works best on a Local LAN. I tried using WAN link and it doesn't work worth shit. If you want offsite replication I strongly recommand a product like Veeam to do that. Its expensive but well worth the money.
Well, this is what our salesperson sold the client, I am only responsible for setting up the server in our datacenter.
I did do a test from my home to a server in a datacenter and it worked fine. The latency was 11ms. However, the latency for our client is more like 50ms.
warlord1312
n00b
- Joined
- Aug 14, 2013
- Messages
- 21
Hyper V replication works best on a Local LAN. I tried using WAN link and it doesn't work worth shit. If you want offsite replication I strongly recommand a product like Veeam to do that. Its expensive but well worth the money.
I would disagree here completely. I have done Hyper-V replication over Comcast connections and it works great. If fact I have even had to failover the replicated VM back to the source server after it was rebuilt because it failed (2 hard drives went bad at the same time).
You can also seed the VM to external drives and ship them and then replicate the changes.
To answer your original question it is possible to replicate domain controllers now that are running Windows Server 2012 (http://technet.microsoft.com/en-us/library/dn250021.aspx) but as others have stated building out another domain controller at the remote site is a better idea. For other applications if they have built in HA/DR capabilities you should use them instead such as using Database Available Groups in Exchange. Other then that replication works great for anything else that doesn't fall in that category.
Sure its possible to that but if you don't have a fat cable connection replication is MEH. Still rather have veeam. Much more efficient.I would disagree here completely. I have done Hyper-V replication over Comcast connections and it works great. If fact I have even had to failover the replicated VM back to the source server after it was rebuilt because it failed (2 hard drives went bad at the same time).
You can also seed the VM to external drives and ship them and then replicate the changes.
To answer your original question it is possible to replicate domain controllers now that are running Windows Server 2012 (http://technet.microsoft.com/en-us/library/dn250021.aspx) but as others have stated building out another domain controller at the remote site is a better idea. For other applications if they have built in HA/DR capabilities you should use them instead such as using Database Available Groups in Exchange. Other then that replication works great for anything else that doesn't fall in that category.