none
VM replication and licensing RRS feed

  • Question

  • I have a site running a couple of physical 2012 R2 Std servers and running Hyper V.

    One is running 2 x 2012 Std VMs and the other just one. I replicate the running VMs between the servers every 15 mins.

    In the event of one of the physical Hyper V servers going down, the idea is to bring up the replicated VM on the remaining server. If this happened then there would be 3 x VMs running on a Windows Server 2012 R2 Std.

    How is licensing affected in this scenario and would it stop me from starting the 3rd VM? I'm guessing not.

    Wednesday, February 7, 2018 2:05 PM

All replies

  • What OS is on Hyper-V ? In std version you can have 2 „free” VM per server (in cluster it is a bit diffrent). In dtc version you can have unlimited VM for free.

    Best Regards,
    Łukasz Antoniak


    Please do take a moment to "Vote as Helpful" and/or "Mark as Answer", wherever applicable. Thanks!

    Wednesday, February 7, 2018 9:07 PM
  • It's 2012 Standard, as I said. I know what the licensing says but how does this work in terms of replication?
    Wednesday, February 7, 2018 9:46 PM
  • If you have software assurance you can use it as could backup.

    http://download.microsoft.com/download/6/C/5/6C576C0C-F740-48E2-86E1-25B15BE23879/dr_brief.doc

    But to be 100% sure you should cały MS


    Best Regards,
    Łukasz Antoniak


    Please do take a moment to "Vote as Helpful" and/or "Mark as Answer", wherever applicable. Thanks!

    Wednesday, February 7, 2018 10:18 PM
  • Note: I don't work for Microsoft and am not giving legal advice.

    For Windows Server, the usual rule is that a server needs to be licensed for the maximum number of Windows Server virtual machines it could ever run at one time. A lot of organizations buy Windows Server Datacenter just for this reason.

    This report might help: https://www.directionsonmicrosoft.com/sample/2016/10/windows-server-2016-licensing-changes

    Rob

    Thursday, February 8, 2018 5:22 PM
  • That's for 2016, the OP is 2012.

    You'll be out of compliance if you move your VM.  

    That said only Microsoft can give you a the legally answer, "someone on the forums said it was ok" isn't a valid reason.

    Ideally, repost in the appropriate Hyper-V forum here:

    https://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads

    This one is for Virtual Server 2005.

    Thursday, February 8, 2018 5:52 PM