Hi Isabel,

A bit late, but here is my take on this.

Hyper-V replication is indeed something you can use in order to have a backup available which you can easily spin up in case of problems on the primary location.

• Network considerations: Not immediately something special I can think off, except of course the network traffic. If you run the database locally on the DMA, all the changes written to the database will also need to be replicated to the backup location. That could be 1 or maybe 2 Mbps of network traffic.
• Licensing of DataMiner: The replication image might indeed have other MAC addresses. I would recommend to test this by running a test failover and see if DataMiner starts up. A test failover has no impact on the VM running in production. In case you would run in to licensing issues, you can reach out to licensing@skyline.be.
• Licensing of Windows: As far as I know, no special license is needed for Hyper-V replication and you only need to license the running VMs. Replicating a VM is just like creating a copy of the VHD(X) file, but as soon as you want to spin up that VM you would need a valid Windows license on that host. I'm not a specialist on the licensing of Microsoft, so it might be best to double check this.

I hope this was helpful. If there is anything else, let us know.

Bert