Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 19461

basic replication questions

$
0
0

We are getting started with Hyper-V. Presently, we have 2 physical installations of WS2012 with Hyper-V installed. One of those machines is hosting a VM. The other machine is doing nothing right now but the plan is to replicate the VM to it.

We have decided not to allocate a budget for shared storage volumes at this time (e.g. iSCSI or fibre channel). All VHDs are on the local machine.

Am I correct that I can do replication and planned failover without a failover cluster? What is the difference between using a failover cluster and not using one? How do I decide whether to use one or not?

If using a cluster is not necessary and I decide not to use one, is there still a benefit to running the Validate Configuration report?

On the VM we want to replicate, we have these 3 VHDs. The VHDs for C: and D: reside on C: and D: of the host. A third VHD, E:, is used to store temporary files and log files which do not need to be replicated. When I use the Enable Replication wizard, a VM is created on the destination host, but the C: and D: VHDs are both on C: of the host, and there is no E: (I selected not to replicate E:), and I cannot change the properties of the VM because it is being replicated. Is it possible to set up replication so that:
- The destination VHDs for the VM's C: and D: will reside on C: and D: of the host?
- Drive E: will not replicate, but the destination VM will still have a drive E: that it can use when it comes on line?

Thank you in advance for the advice.

Cam


Viewing all articles
Browse latest Browse all 19461

Trending Articles