Coriolis integrates the platform Plugin on the Appliance itself, this way there is no need for agents to be deployed on platforms to establish the communication between the platform and the Coriolis components. Using this type of architecture,
Coriolis guarantees the connection to the supported platform set up to be used as either Source or Destination, as long as the requirements are met.
VMWare platform is supported via Coriolis Plugins as a stand-alone ESXi or vCenter. Also with our newer releases, Coriolis supports VMWare as both Source and Destination Endpoints for Replica/Migration tasks.
Deployment requirements and supported vSphere/ESXi versions
The Coriolis worker components need network access to the API endpoint of the vCenter/ESXi host. (usually HTTPS/443)
For CBT-enabled Coriolis Migrations, as well as Coriolis Replicas (DRaaS), the Coriolis worker components will need TCP/902 network access to the ESXi host. If using a multi-host vSphere, any ESXi host can perform the CBT export so network access to all of them is required.
NOTE both the suggested standard management port (443) and backup port (902) are configurable so that they may differ from environment to environment.
In a vSphere environment, the Coriolis virtual appliance must also be able to connect over port TCP/902 to each and all ESXi nodes. This might require additional network setup consideration if the ESXi nodes reside on a separate or private network.
Refer to the Network Ports Requirements page for more details.
Coriolis can work with any vCenter/ESXi host greater or equal to version 6.0. VMware products that are EOL might continue to work as-is, however, technical support will be limited.
For full compliance and support, consider reviewing the VMware Products Lifecycle page.
If performing Coriolis Replicas (DRaaS), the VMs being replicated must have their storage hosted on a CBT-compatible datastore (VMFS or NFS), and not use any kind of raw disk mappings.
The Coriolis virtual appliance comes by default with a pre-installed version of vixDiskLib, which can range from version 7.0 to 8.0, depending on the Coriolis release. The vixDiskLib version is compatible with later versions of ESXi, up to the latest version, so matching it to the VMWare version is not mandatory.
For information on updating the vixDiskLib, please check the Updating vixDiskLib for Coriolis document.
vSphere as a source cloud
For more information on using vSphere/ESXi as a source cloud for Replica/MIgration, please check the VMWare as a source cloud page.
vSphere as a destination cloud
For more information on using vSphere/ESXi as a destination cloud for Replica/MIgration, please check the VMWare as a destination cloud page.
vSphere/ESXi connection parameters
To connect to vSphere/ESXi to perform a migration/replica from that cloud, the following connection parameters are required:
Example of connection info JSON to be passed to the VMWare vSphere plugin
Each parameter represents:
- host (string) – the address or resolvable domain name of the vSphere host
- port (integer) – the port on the host to which to connect to
- username (string) – the username of the vSphere user to login with (must include the “@domain” part)
- password (string) – the password of the vSphere user to login with
- allow_untrusted (boolean) – whether to skip certificate verification if the vSphere endpoint has self-signed certificates (default is false)
When using hostnames for the ESXi/vCenter hosts, Coriolis needs to be able to resolve them.
VMware platform specifics
|Supported Actions:||Migration (CMaas) Source/Destination – Replica (DRaaS) Source/Destination||Comments|
|Plugin identifier||vmware_vsphere||Identifies the plugin. Used for the –provider CLI parameter|
|Credentials needed||Standard vSphere user credentials, not necessarily with administrative rights||Necessary credentials to give to Coriolis|
|Deployment requirements||Coriolis worker component(s) need network access to the vCenter/ESXi API endpoint. Network access to the ESXi hosts, (not necessarily the one the VM is on) is also required.||Coriolis deployment and environment connectivity requirements|
|Source disk export requirements||All VM disks must be normal virtual disks located on a datastore of a simple type like VMFSChanged Block Tracking (CBT) must be available for use and enabled on all the disks of the VMs which will be replicatedCoriolis can be optionally configured to enable CBT itself granted the VM has no pre-existing snapshotsPassthrough/remote/iSCSI disks cannot have CBT enabled on them, so they are not supported||Requirements to use the replica export (DRaaS source) (DRaaS source) (DRaaS source) (DRaaS source) features|
|Instance identification scheme||Slash-separated VM inventory path starting with datacenter(ex: “DC1/somevmfolder/The VM”)If VM is at top-level, datacenter may be omitted (ex: “DC1/The VM” can be “The VM”)||How instances to migrate/replicate are identified on a source cloud handled by this plugin|
|Network identification scheme||Names of VM Networks (ex: “VM Network Local”)If a VM is attached to a Distributed Virtual Switch (DvS), the name of the DvS Port Group is referenced.||How the plugin identifies networks. Required for the network_map field of the –destination-environment|
|Storage identification scheme||Names of datastore hosting the virtual disks(s)||How the plugin identifies storage backends. Required for the storage_map field of the –destination-environment|
VMware Coriolis plugin known issues
For further information regarding VMWare Plugin’s known issues, please check the documentation page.