Simplified Configuration-Only Migration from Non-Hot Standby Docker to Docker

Preparing to Migrate

This procedure provides instructions on how to migrate from one of the following releases by migrating the database only:

• Legacy Orchestrator Docker (21.08 or later version) to the Cisco Crosswork Assurance Sensor Management Docker (25.07.1-LTS) (new operating system version: Ubuntu 24.04/Red Hat 9.6)

Note: Does not support cross-operating system migration between Docker hosts, which means it will NOT allow:

• Migration from Ubuntu 20.04/Ubuntu 22.04/Ubuntu 24.04 to Red Hat 9.3/Red Hat 9.6 operating system version
• Migration from Red Hat 8.8/Red Hat 9.3/Red Hat 9.6 to Ubuntu 20.04/Ubuntu 22.04/Ubuntu 24.04 operating system version

Migration involves setting up a new Target Installation Docker with the new operating system version that will be used to import the database configuration of the Source Installation with the old operating system version. This requires, at a minimum:

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

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 the new Target Installation Docker is beyond the scope of this article. These procedures are already captured in the Sensor Management Docker Deployment article and should be used in the preparation for your migrating activity. The important point to consider while installing your Target Installation 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.

Consult your Cisco sales engineer if you need guidance on the profile to choose for your Target Installation 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 Target Installation 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. Importing the database backup into the target installation
4. Starting up the software on your target installation.

Migration Procedure

Source Installation Procedures

Backing up the Data Store

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 the Legacy Orchestrator CLI on port 2200.
2. Log in as the skylight user.
3. Create a backup of the data store by entering:

database backup

Note: The backup is generated as a tar.gz file in the folder backups of the so-mysql volume.

4. Rename the database backup file to migrate.tar.gz and transfer it to the new Target Installation Docker under the /tmp directory.

Stopping the Legacy Orchestrator Services

It is best to stop the Legacy Orchestrator services on the source installation while doing the migrating procedure. The procedure to stop the Legacy Orchestrator services:

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

services stop

Target Installation Procedures

These procedures guide you through the database import and rebalancing process that is to be executed on the Target Installation Docker.

Requirements

Ensure that all configurations related to network, interface, NTP server, Hamon, and timezone (highly recommended) are configured manually and match the configuration on the virtual appliances (source installation) to ensure all devices are reachable on the Target Installation Docker. Refer to the Sensor Management 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 Target Installation Docker Services

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

services stop

Note: If the services are stopped, skip this step.

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 Target Installation CLI on port 2200.
2. Log in as the skylight user.
3. Restore the backup by entering:

database migrate <filename_of_the_backup_archive>

Note: You must provide only the filename of the archive, not the path which is assumed to be /tmp.

Starting the Target Installation Services

This procedure will start the application.

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 Target Installation Services

1. Open an SSH terminal session to the Target Installation 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 Legacy Orchestrator services

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

services start