This section describes about the Revert operation.

Important:

This outcome is irreversible. The system will revert back to the TCA 2.3 state known at the beginning of the migration. The TCA 3.1 VMs will be permanently deleted, and the TCA 2.3 VMs will be rebooted. Ensure that the input and VM details (VM names) are proper. The intention is to delete failed VMs (3.1 VMs). The migration tool has some safety checks for wrongly specified VM names in the input. If the VM names point to non-TCA VMs or unsupported TCA version, the tool fails the revert operation. This operation is recommended to revert entire topology. The tool does not check whether appliances are successfully migrated and it deletes all the specified appliances.

To revert the migration, run the revert CLI to delete the new 3.1 VMs and power on the 2.3 VMs.

revert CLI Help

$ tcamigctl revert -h 
usage: tcamigctl revert [-h] input_file

Reverts the migrated setup to original setup. Deletes new appliance(s) and powers on the old appliance(s). Run it with caution as the outcome of this operation is irreversible. Runs the operation in the background

positional arguments:  
  input_file  input file containing TCA manager and TCA-CP details

options:  
  -h, --help  show this help message and exit

Following is the usage:

revert CLI

tcamigctl revert input.json

If you retry migration after revert, wait for three minutes for the 2.3 VMs to power on and initialize.

Note:

If you revert to 2.3 setup and use it for a while before trying again, ensure that you delete old backups by using -c option with e2e-migrate or backup CLI to migrate new or modified data.