It is recommended to use the migration tool for deploying or powering on the appliances. However, you can also manually perform these actions in case the VC is unapproachable or there are firewall issues from the migration container and so on.

The following fields are not required:

  • vcEndpoint

  • vcUsername

  • vcPassword

  • vcThumbprint

  • oldVmName

  • newVmName

The following are required steps:

  1. Manually deploy the 3.0 VMs via vSphere UI (Deploy OVA) using the same IP and details as 2.3 VM. Do not power on. (Outside Maintenance window).

  2. Run backup CLI to generate backup for the appliances. (Within Maintenance window).

  3. Manually power off 2.3 appliances via vSphere UI. (Within Maintenance window).

  4. Manually power on 3.0 appliances via vSphere UI. (Within Maintenance window).

  5. Run migrate CLI to migrate.

Note:

In case you encounter any issue, you need to manually revert (delete 3.0 VMs and power on 2.3 VMs).