Is there any chance to have Hyper-V Replica to work over IP address instead of NETBIOS/FQDN?
Without messing with DNS / hosts file (%windir%\system32\drivers\etc).
Scenario: Sending replica traffic over dedicated network.
Network Constraint (control which networks HR runs upon, based on network interface).
Having a VM with a replica. Now I will change the size of a harddisk at the primary site (most of the time to increase the volume size).
After I do that the replica is broken and I must completly restart the replica with lost of all previous replicas.
Please find a way to do this online without break the replica!15 votes
I really do appreciate the live migration of VMs, so that I can seamlessly maintain hosts. I also cherish the async replication between hosts for disaster recovery. What I do miss is the option to live migrate, using the already replicated storage, to the target host. This would save enormous amount of resources.18 votes
Well done for implementing shared vhdxs, and making guest clustering a possibility. But how are we supposed to make use of replication when you are unable to replicate a shared vhdx? We would like to be able to maintain a backup solution that we can failover to if need be.
Please can you implement this feature so that we can contine to rely on the benefits of replication.
Add an option to syncronize (or not) configuration changes (CPU, Memory, Disk, NIC, etc) from primary VM to replica VM, when Hyper-V Replica is enabled.34 votes
- Don't see your idea?