2.2. Deploying HVRAgent on VMware ESXi Hypervisor

There are three types of replication agents:

  • VMware agent - an external agent to replicate VMware virtual machines without installing any software directly on VMs. Please refer that the agent requires access to VMware CBT API and network access to vCenter or ESXi host is mandatory. Note that the agent from the same ova template must be deployed to all ESXi hosts where machines need to be protected.

  • Windows agent - an internal agent which can be deployed to any number of customer Windows virtual or physical machines.

  • Linux agent - an internal agent which can be deployed to any number of customer Linux virtual or physical machines.

As we are performing a migration from VMware as the Source Cloud Platform, we will be using the VMware Agent. When any of the agents are deployed, the machine with it (or all machines on the same ESXi host where the agent is located) will appear in Hystax Acura Control Panel under customer dashboard in the Discovered state.

  1. Login to the Hystax Acura portal by going to https://floating-ip-acura-instace.

  2. Click on the customer you wish to perform the migration for, in our example we will be performing a migration from VMware as Source Cloud to Virtuozzo Hybrid Infrastructure platform. Any time you wish to go back to the main menu click on the Hystax logo on the top left.

  3. Click Install agents.

  4. Select the VMware agent and click Next.

  5. You will be asked to provide credentials for the vSphere environment. Provide the credentials created previously.

  6. Now download the OVA file and deploy it on each ESXi host in your VMware cluster that you want to migrate workloads from.

  7. Deploy the agent:

    1. Use the Deploy OVF Template wizard to deploy the HRVAgent. Right click on the ESXi server you would like to deploy the agent. You’ll need to repeat this procedure for each ESXi server available that you wish to migrate workloads from.

    2. Select Local file, click Upload files, and choose the OVA file.

    3. Follow the deployment wizard and provide the necessary information (compute resource, storage, networks) HVRAgent. The HVRAgent should be able to access the vCenter internal IP.

  8. Once the HVRAgent VM is up, check the console and verify all is correct.

  9. Click on the Hystax logo on the top left and on the customer, you’d like to manage. You will see the machines running on your ESXI server have been discovered.

  10. Click on Start Replication. If everything is correctly configured, replication of the remote instance will start on your target cloud. Replication will take some time, depending on how much data will be replicated and the connection between your source and target cloud.

    ../_images/intg-hystax-vmware-start-replication.png ../_images/intg-hystax-vmware-replication-progress.png
  11. Wait until the instance is synced.

  12. While the image is being synced, let’s create a target network (the network that will be used by our instance on the replicated target cloud). Go to your VHI self-service portal on “vhi-admin-panel-fqdn:8800” and login to the target project.

  13. Once you’ve logged in, check the Virtual machines tab and you will see that the Acura cloud agent has been deployed automatically.

  14. Go to Networks, click Create virtual network, and follow the steps. I will create the network using exactly the same CIDR ( as the instance being replicated. You could use any other network CIDR, this is just to show an example of a migration with exactly the same IP address source and remote.

  15. Add a migration plan. Start by adding a machine. Click on the ellipsis icon “…”, then click Add machine > Default, and select discovered machine.

  16. Next, configure the subnets for your new instance. Expand the view for your instance. You will see information regarding Machine ID, Flavor (important to check the flavor you choose have enough resources for your instance), and Port (network). Also, on the left you’ll see information regarding the network to be used.


    We will replace the Flavor name with one that is available on our cloud. You can check available flavors by going to Virtual machines and Flavors. Also, we will find the subnet ID for our newly created network and paste it there.

  17. Source the information regarding the subnet ID.

    1. Login to your Virtuozzo Hybrid Infrastructure Admin panel via SSH.

    2. Source the admin-openrc.sh file.

      # source /etc/kolla/admin-openrc.sh
    3. Run the command openstack network list --insecure and identify the subnet ID.

  18. Add the subnet ID.

  19. Add a secondary Port. Add a subnet by clicking the “+” button on the Subnets section, we will be adding a floating IP.

  20. Click on the Subnet ID* drop down menu for your new subnet and select the Public IP you wish to use. By leaving the Port IP field blank you are specifying DHCP. Provide a name for the plan and click Save.

  21. Click on Run test migration and select the migration plan.

  22. Create a cloud site by giving a name, a cloud site is a way to logically group a migration plan with a snapshot to be used for the migration. Give the Cloud Site a name, select a snapshot and click on Run migration.


If all went well you will see your replicated instance available on your target cloud. When you are done reviewing the migration test you can delete the resources, by deleting the cloud site, then you can redo the migration, or you could detach.

../_images/intg-hystax-vmware-virtual-machines.png ../_images/intg-hystax-vmware-jenkins-login.png

For the final cutover, just detach Hystax Acura from the migration and Hystax Acura will stop tracking any resources belonging to this migration.

../_images/intg-hystax-vmware-detach-instance.png ../_images/intg-hystax-vmware-cloud-site.png

Now you can manage your resources from VHI as you would normally do.