2.1. Resource Planning and Configuration for VMware

In this guide we will be performing a migration from VMware to the Virtuozzo Hybrid Infrastructure Platform; Before we can start with the migration, we need to ensure certain resources are available on the VMware Platform, such as a user with some specific permissions and the HVRAgent (Hystax Replication Agent for VMware) deployed on each of the ESXi Hypervisors. Replication agents are used to replicate the workloads between VMware ESXi Hypervisors (Source Platform) and the Virtuozzo Hybrid Infrastructure Platform (Target Platform/Target Project). From now on we will be referring to the VMware Platform as the Source Platform, and the Target Project or Platform when referring to the Virtuozzo Hybrid Infrastructure Platform.

Hystax Acura Migration Solution Architectural Overview

../_images/intg-hystax-vmware-architecture.png

Ports needed for correct agent work:

  • vSphere host - tcp/443

  • ESXi host(s) - tcp/udp/902

  • Send logs to the Acura cluster - udp/12201

Hystax VMware Replication Agent requires the following user permissions in vSphere (the “VMware Consolidated Backup user” role in vCenter):

  • Virtual machine - Configuration - Disc Lease

  • Virtual machine - Provisioning - Allow read-only disk access

  • Virtual machine - Provisioning - Allow virtual machine files upload

  • Virtual machine - Snapshot management - Create snapshot

  • Virtual machine - Snapshot management - Remove Snapshot

Permission to access CBT is necessary for the correct performance of the application. To enable CBT:

  • Virtual machine - Configuration - Disc change tracking

Additionally, it is recommended to include the following global permissions:

  • Global - Disable methods

  • Global - Enable methods

  • Global - Licenses

Note

In case of using vCloud, vCenter user requires one extra permission to operate: Profile-driven storage > Profile-driven storage view.

Hystax VMware Replication Agent uses VMware snapshots and VMware CBT API in order to create consistent replicas of machines’ data.

This implies the following considerations regarding VMware storage:

  • VMware snapshots consume storage to retain copy-on-write buffer, so it is recommended to have at least 10% free space available on VMware storage.

  • VMware puts additional load on storage while creating snapshots or running machines with existing snapshots.

Please consider that storage performance warning thresholds need to be adjusted in order to meet this increased load during replication.

Important

The source machine must have VMware Tools installed manually prior to any replication procedures for it to display its network information in the target VMware ESXi correctly.

  1. Login to your vCenter.

    ../_images/intg-hystax-vmware-login-vcenter.png
  2. Create a user, in this example we will create a user named hystax-user. On your VMware vCenter client go to Administration > Single Sign On > Users and Groups, select your domain in the Domain drop-down menu and click ADD.

    ../_images/intg-hystax-vmware-add-hystax-user.png
  3. Create a role, we will clone the role VMware Consolidated Backup user and name it Hystax-HVRAgent. On Administration tab, go to Access Control > Roles, select VMware Consolidated Backup user, and click CLONE. Give it a meaningful name and ensure it has the following permissions selected:

    • Virtual machine - Configuration - Disc Lease

    • Virtual machine - Provisioning - Allow read-only disk access

    • Virtual machine - Provisioning - Allow virtual machine files upload

    • Virtual machine - Snapshot management - Create snapshot

    • Virtual machine - Snapshot management - Remove Snapshot

    • Virtual machine - Configuration - Disc change tracking

    ../_images/intg-hystax-vmware-edit-role.png
  4. Assign the role to the user. Go to Inventory > Permissions, select the previously created user, and click Edit. Search for the newly created role and add the role to the user.

    ../_images/intg-hystax-vmware-change-role.png

At this point, the hystax-acura user has the necessary permissions to perform the migrations.