Migrating from Virtual Machine to Docker

Preparing to Migrate

This procedure contains instructions on how to migrate from one of the following releases:

• Legacy orchestrator virtual machine (23.12 or prior version) to the same version of Legacy orchestrator Docker
• Legacy orchestrator virtual machine (23.12 or 23.12.1 version) to Legacy orchestrator Docker 24.09

Migration involves setting up a new Legacy orchestrator Docker (target installation) that will be used to import the database configuration of the Legacy orchestrator virtual machine installation (source installation). This requires, at a minimum:

• The deployment of the virtual appliance
• The configuration of its hostname, IP addresses, NTP time sources (highly recommended), timezone (highly recommended)
• The selection of its deployment profile.

For redundant environments, two new Legacy orchestrator Dockers will be required and for hot standby environments, the need for three interfaces per appliance on distinct subnets remains.

These procedures are written assuming the target installation will be hosted in a new environment with new net IP addresses. It is expected that new firewall implementations will be required to ensure the application can connect to the network and that end users can access the application interfaces.

The installation of these new Legacy orchestrator Dockers is beyond the scope of this article. These procedures are already captured in the Legacy orchestrator Docker Deployment​ article and should be used in the preparation for your migrating activity. The important point to consider while installing your Legacy orchestrator Docker is the deployment profile. The software ships with four deployment profiles:

• 5K profile (default)
• 15K profile
• 30K profile
• 60K profile.

The profiles reference the number of network elements the system can manage. Larger profiles have larger memory, CPU, and disk requirements. The selection of the profile is dictated by the current number of network elements in your source installation.

Please consult your Cisco sales engineer if you need guidance on the profile to choose for your Legacy orchestrator Docker. The deployment profile can be changed (during a maintenance window) at any time, but when doing so, adequate memory, CPU, and disk resources need to be assigned to the Docker host.

Once the Legacy orchestrator Docker is in place, with IP addresses assigned, deployment profile selected, and networking rules in place, the high-level process of migrating entails the following tasks:

1. Taking a database backup of your source installation
2. Stopping the software on your source installation
3. Transferring all resync DAT files on each mediation folder to your target installation
4. Transferring the performance session data to your target installation
5. Importing the database backup into the target installation
6. Starting up the software on your target installation.

Before starting the migration process from Legacy orchestrator virtual machine (version 23.12 or 23.12.1) to Legacy orchestrator Docker 24.09, follow the steps below to ensure there is no offline data (all Resync DAT files) on the source installation (only version 23.12 or 23.12.1):

1. Open an SSH terminal session to Legacy orchestrator on port 22.
2. Log in as the visionems user.
3. Run the following command:

find /data/medn*instance/s*/ -type f -name "*RESYNC*" | wc -l

If the output is 0, it indicates there is no offline data.

Otherwise, offline data exists in the Legacy orchestrator virtual machine. In this case, you must wait for the Legacy orchestrator virtual machine to process all offline data by generating the CSV file and sending all CSV files to the SFTP/Rsync destination. If this step is not completed, the offline data will be lost during the migration.

Migration Procedure

Source Installation Procedures

Precondition

On the source installation, ensure that the Internal License Server key needs to be added before performing the migration process.

To import an Internal License Server key

1. Obtain the appropriate key file from Technical Support.
2. Save the key file on the local file system (for example, on the desktop) and extract this file.
3. Access the Admin ▶ Feature Activation page.
4. Click the Choose File button.
5. Select the Internal License Server key file on your local file system from the file selector dialog.
6. Click the Import button.

Backing up the Data Store

In order to rehome, a database backup of the source installation is required. If running a hot standby configuration, the hot standby license file must be copied as well.

To back up and transfer the data store

1. Open an SSH terminal session to Legacy orchestrator on port 22.

2. Log in as the visionems user.

3. Change to the scripts directory by entering:

cd /opt/accedian/skylight/scripts

4. Create a backup of the data store by entering:

./ems_backup_mysql.sh -d

The backup is created and saved in the /opt/accedian/backups directory.

5. Rename the database backup file to migrate.tar.gz and transfer it to the new Legacy orchestrator Docker (target installation) under the /tmp directory.

Stopping the Application

It is best to stop the application on the source installation while doing the migrating procedure. The procedure to stop the application differs for hot standby setups.

If you are operating in a Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator on port 2200.
2. Log in as the visionems user.
3. Stop the Hot Standby process by entering:

redundancy control stop

Otherwise

1. Open an SSH terminal session to the Legacy orchestrator on port 2200.
2. Log in as the visionems user.
3. Stop the application by entering:

service stop app_server

Transferring All Resync DAT Files

When migrating from the Legacy orchestrator virtual machine (version 23.12 or prior) to Legacy orchestrator Docker of the same version, follow these steps to ensure the historical performance monitoring data is preserved and transferred to the target installation.

1. Open an SSH terminal session to Legacy orchestrator on port 22.
2. Log in as the visionems user.
3. Initiate the transfer by entering:

For Virtual Machine version 23.04.1 or prior

cd /data
rsync -R -v medn1instance/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation1>

cd /data/medn2instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation2>

cd /data/medn3instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation3>

cd /data/medn4instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation4>

cd /data/medn5instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation5>

cd /data/medn6instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation6>

cd /data/medn7instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation7>

cd /data/medn8instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation8>

cd /data/medn9instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation9>

cd /data/medn10instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation10>

cd /data/medn11instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation11>

cd /data/medn12instance
rsync -R -v datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation12>

For Virtual Machine version 23.12

cd /data
rsync -R -v medn1instance/s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation1>

cd /data/medn2instance
rsync -R -v s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation2>

cd /data/medn3instance
rsync -R -v s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation3>

cd /data/medn4instance
rsync -R -v s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation4>

cd /data/medn5instance
rsync -R -v s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation5>

cd /data/medn6instance
rsync -R -v s*/datfiles/*/*_RESYNC.* skylight@<ip_docker_host>:<path_of_data_volume_for_mediation6>

If migrating to a redundant configuration, transfer the files over to the virtual appliance that will be used as the preferred site.

Transferring the Performance Session Data

To preserve the historical performance session data, it must be transferred over to the target installation by following these steps.

1. Open an SSH terminal session to Legacy orchestrator on port 22.
2. Log in as the visionems user.
3. Initiate the transfer by entering:

rsync -av /data/sdmm skylight@x.x.x.x:/<directory>

where x.x.x.x is the IP address of the target installation.
where < directory > is the bizn1instance directory under so-data volume

If migrating to a redundant configuration, transfer the files over to the virtual appliance that will be used as the preferred site.

Target Installation Procedures

These procedures guide you through the database import and rebalancing process that is to be executed on the target installation of Legacy orchestrator Docker.

Requirements

Ensure that all configurations related to network, interface, NTP server, Hamon, timezone (highly recommended), and so on will be configured manually and same as the configuration on the virtual appliances (source installation) to ensure all devices are reachable on the Legacy orchestrator Docker (target installation). Please refer to the Docker Deployment articles for additional information.

Ensure the data volume(s) is configured to store all performance session data and performance metrics data.

Stopping the Legacy orchestrator Services

Stopping Hot Standby Process and Legacy orchestrator Services on Hot Standby Configuration

Active Site

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Stop the Hot Standby process by entering:

redundancy control stop

Stopping Legacy orchestrator Services on Non-Hot Standby Configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Stop services by entering:

services stop

Importing the Database

Ensure the user ‘skylight’ has read access to the archive that was copied in the /tmp folder. The backup file that needs to be restored must be placed on the appliance file system in the /tmp directory.

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

2. Log in as the skylight user.
3. If migrating from Legacy orchestrator virtual machine (23.12 or prior version) to the Skylight orchestrator Docker of the same version, restore the backup by entering:

database restore <filename_of_the_backup_archive>

OR

3. If migrating from the Skylight orchestrator virtual machine (23.12 or 23.12.1 version) to the Skylight orchestrator Docker 24.09 version, restore the backup by entering:

database migrate <filename_of_the_backup_archive>

Starting the Legacy orchestrator Services

This procedure will start the application.

Starting the application for Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator designated as the preferred active site on port 2200.

2. Log in as the skylight user.

3. Configure the preferred site, the site which transferred the files at ‘Transferring All Resync DAT Files’ step, enter:

redundancy config preferred {site-a | site-b}

4. Start the Hot Standby process by entering:

redundancy control start

5. Verify redundancy status, enter:

redundancy show status

Starting Legacy orchestrator services on Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Start services by entering:

services start

Rollback Procedure

The migrating operation can be rolled back by stopping the application on the target installation and restarting the application on the source installation.

Target Installation Procedures

Stopping Hot Standby Process and Legacy orchestrator Services on Hot Standby Configuration

Active Site

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Stop the Hot Standby process by entering:

redundancy control stop

Stopping Legacy orchestrator Services on Non-Hot Standby Configuration

1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Stop services by entering:

services stop

Source Installation Procedures

This procedure will start the application.

Starting the application for Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator designated as the preferred active site on port 2200.
2. Log in as the visionems user.
3. Configure the preferred site to the last active site, enter:

redundancy config preferred {site-a | site-b}

4. Start the Hot Standby process by entering:

redundancy control start

5. Verify redundancy status, enter:

redundancy show status

Starting the application for Non-Hot Standby configuration

1. Open an SSH terminal session to the Legacy orchestrator on port 2200.
2. Log in as the visionems user.
3. Start the application by entering:

service start app_server