Configure the Migration Channel

This topic explains the steps to configure migration channel.

To migrate data from Classic On-Premises to the Virtual Appliance, configure the NFS channel that is used to secure connection and mount the NFS server on both the Classic On-Premises environment and the Virtual Appliance. This setup enables data transfer between the two systems. Follow these steps to configure the NFS server for data migration:

Ensure that VA services are stopped, you can check using the following command:

CODE 
appdcli ping

The VA services status appears as Not Installed.

Sample Output:
CODE 
+----------------------+---------------+
| Service Endpoint     | Status        |
+======================+===============+
| Controller           | Not Installed |
+----------------------+---------------+
| Events               | Not Installed |
+----------------------+---------------+
| EUM Collector        | Not Installed |
+----------------------+---------------+
| EUM Aggregator       | Not Installed |
+----------------------+---------------+
| EUM Screenshot       | Not Installed |
+----------------------+---------------+
| Synthetic Shepherd   | Not Installed |
+----------------------+---------------+
| Synthetic Scheduler  | Not Installed |
+----------------------+---------------+
| Synthetic Feeder     | Not Installed |
+----------------------+---------------+
| AD/RCA Services      | Not Installed |
+----------------------+---------------+
| SecureApp            | Not Installed |
+----------------------+---------------+
| OTIS                 | Not Installed |
+----------------------+---------------+
| ATD                  | Not Installed |
+----------------------+---------------+
| UIL                  | Not Installed |
+----------------------+---------------+
  1. Log in to the Virtual Appliance node and edit the globals.yaml.gotmpl file.
    CODE 
    cd /var/appd/config
vi globals.yaml.gotmpl
    1. Disable self-monitoring for Virtual Appliance, set the enableClusterAgent parameter to false.
      CODE 
      enableClusterAgent: false
    2. Enable data migration for Elasticsearch datastores, set the migration.elasticsearch.fs.enabled parameter to true.
      CODE 
      # Migration config for datastores
migration:
  elasticsearch:
    fs:
      enabled: true
    3. Ensure the license.lic file exists in /var/appd/config.
  2. Run the following command to establish secure connection and mount NFS server on Classic On-Premises and Virtual Appliance.
    CODE 
    python3 ./migration_tool.py setup migration-channel
  3. Log in to the Virtual Appliance node and start the Virtual Appliance services:
    CODE 
    appdcli start appd <profile>

    If the Virtual Appliance is already installed, restart it using the following command:

    CODE 
    appdcli stop appd
appdcli start appd <profile>
  4. (Optional) Verify the NFS channel before starting the migration tool.
    CODE 
    python3 ./migration_tool.py validate nfs-channel
  5. Shutdown the Controller in Virtual Appliance.
    CODE 
    kubectl scale deployment controller-deployment -n cisco-controller --replicas=0
  6. Run the command to edit the Controller deployment configuration.
    CODE 
    kubectl edit deployment controller-deployment -n cisco-controller
  7. Update the livenessProbe, readinessProbe, and startupProbe values.
    CODE 
    livenessProbe:
  failureThreshold: 10
  ...
  periodSeconds: 30
  successThreshold: 1
  timeoutSeconds: 120

readinessProbe:
  failureThreshold: 3
  ...
  initialDelaySeconds: 420
  periodSeconds: 30
  successThreshold: 1
  timeoutSeconds: 120

startupProbe:
  failureThreshold: 300
  ...
  initialDelaySeconds: 420
  periodSeconds: 30
  successThreshold: 1
  timeoutSeconds: 120