You can check the status of the migration at any time using the following status CLI command.

$ tcamigctl status -h 

usage: tcamigctl status [-h] [-o {json}] [-w] [input_file]

Get status of the migration operation and migration status of the appliance(s)

positional arguments:  
  input_file            specify input file containing TCA Manager and TCA-CP details as a filter. If specified, only those appliance status details are shown

options:  
-h, --help                           show this help message and exit  
-o {json}, --output-format {json}    formats status in the given format  
-w, --watch                          if specified, the live status details are shown on the terminal. Press Ctl+C to stop

You can see the status of all the appliances which are migrated, in the format of a table as shown in the following example:

$ tcamigctl status

Table 1. Status CLI output

`============Appliance Status Summary===========` `Last Triggered Operation: 'e2e-migrate' (PID: 1574, Input File: /migrationVolume/topology-output-172_16_192_71.json), Status: Running`
	`Appliance\Status`	`Deploy`	`Backup`	`Migrate`	`Revert`	`Messages`	`Timestamp`
`0`	`VM_tcaMgr-1_2_3_4`	`success`	`success`	`In progress`	`-`	`Post-Migrate: Waiting for TCA appliance services to be ready. This may take a few minutes.Start time: 21:46:58.394619. Timeout is 1800s.`	`2024-02-08 21:49:57.569460.`
`1`	`VM_tca-cp-1_2_3_5`	`success`	`success`	`success`	`-`		`2024-02-08 21:49:57.569584`

You can filter specific VM or specific topology using the input file filter. The Input file format is same as specified in the Fill Template File Details section.

Status CLI filter:

tcamigctl status input.json

You can format the status in JSON using status CLI json command as shown in the following example. For programmatic access, json output is also provided. For clients, that are monitoring background operations, check the status periodically and make sure _last_operation.status is not RUNNING state for the exit condition.

$ tcamigctl status -o json 
{  
"VM_tcaMgr-1_2_3_4": {    
  "messages": "Post-Migrate: Waiting for TCA appliance services to be  
               ready. This may take a few minutes. Start time: 
               21:46:58.394619. Timeout is 1800s.",    
  "migrate": "In Progress",    
  "deploy": "success",    
  "backup": "success"  
},  
"VM_tca-cp-1_2_3_5": {    
   "messages": "",    
   "migrate": "success",    
   "deploy": "success",    
   "backup": "success"  
},  
"_last_operation": {    
   "name": "e2e-migrate",    
   "pid": 1234,    
   "input_file": "/migrationVolume/topology-output-1_2_3_4.json",      
   "status": "RUNNING"  
  }  
}

Running the CLI with -w option, you can watch the live status of migration. The table refreshes in the console.

$ tcamigctl status /migrationVolume/topology-output-1_2_3_4.json -w



`============Appliance Status Summary===========` Last Triggered Operation: 'e2e-migrate' (PID: 1574, Input File: /migrationVolume/topology-output-1_2_3_4.json), Status: Running
	`Appliance\Status`	`deploy`	`backup`	`migrate`	`revert`	`reason`	Timestamp
`0`	`VM_tcaMgr-1_2_3_4`	`success`	`success`	In progress	`-`	Post- Migrate: Waiting for TCA appliance services to be ready. This may take a few minutes. Start time: 21:46:58.394619. Timeout is 1800s.	2024-02-08 21:49:57 . 569460
`1`	`VM_tca-cp-1_2_3_5`	`success`	`success`	`success`	`-`		2024-02-08 21:49:57 . 569584
2	VM_tca-cp-1_2_3_6	`success`	`success`	In progress	`-`	Restore is running ... restore completed for Secret	2024-02-08 21:49:57 . 569663