1. Prerequisites:
   

   1. Production HyperV node is up and running. All the HyperV VMs running on this node have both vhdx and config files hosted on a local storage.

   2. Build a DR HyperV server having identical hardware configuration
      

2. EMS> Install and configure Engine on production environment as Primary =>
   

   1. Hyper V Plugin is installed automatically and detects VM data to be protected

   2. AMC> Uninstall System plugin by Remove protected application from Application> Summary 
      

   1. 
      

   3. EMS> Add DR node using Assisted Cloning (without actually cloning the server - we need just the configuration). Make sure you:
      

      1. Choose Different Public IP and set this to DR node intended IP
         

      1. 
         

      2. Check this deployment doesn't need DNS Update

      3. Define Channel connection 
         

      1.                                                                                                                                                          

   4. EMS> Delete the cloning operation in progress
      

   1. 
      

   5. Production Server is ready
      

3. Prepare DR node: mandatory it should meet all the Secondary/Standby node requirements

4. EMS> Install Engine on DR server (perform a Primary type install)

5. EMS> Remove DR server from EMS protected servers

6. On the DR node
   

   1. Stop Engine service

   2. Configwiz>

      1. Reconfigure DR node as Secondary Identity

      2. Configure Channel connection (the same one configured on the production server), Replication will start - wait till all Production VM data is moved to Secondary… (It might take a while…)

   3. Start Engine
      

7. Once the Full System Check is completed, Switchover to S/A=>P/-

8. [Optional]: If production HyperV server stores VM configuration files in multiple folders make sure ALL are added to the file protected set (User-Defined)

9. On Secondary active, use HyperV Manager to register all the production VMs onto DR HyperV node.

   1. Since the HV server identities are different there are 2 actual HyperV server nodes (Prod and DR). This means you won’t see any VMs registered in HyperV Manager on the DR node after making the DR node active. Workaround: Register all the production VMs as new VMs (Import as Copy) in DR node’s HyperV Manager. VM configuration files shouldn't be replicated. Virtual hard-disk files must be replicated (and shared between Prod and DR VM instances). Each VM should be imported individually as a copied VM (new unique ID). Thus, one by one process all the production VMs. For each VM:
      

      1. Locate folder: Select the production VM folder containing configuration files. Then select desired VM

         1. 

      2. Chose Import Type: Copy the virtual machine (create new unique ID). This is required as this VM will be imported under a different ID on the DR HyperV node.

         1. 

      3. It is mandatory to store the DR imported VMs configuration files in a different location than Production store folder (each node must have and use its own VM configuration files - don’t overwrite them)

         1. 

      4. Storage folders: choose the same folder location (implicitly vhdx file) for DR VM storage as the one used on Production Node.
         

      1. 
         

10. License the non-Identical deployment: you need to generate and add one License Keys for each node.

    1. On the active server, stop Engine, then use Configwiz to add the two required license keys
       

Known Limitations due to non-identical CE HyperV nodes configuration:

• Post-install: Any changes performed to Production VM configuration must be repeated on the corresponding DR VM. Remember, this scenario involves 2 distinct HyperV servers not replicating the VM configuration files.