Cisco Crosswork Network Controller 7.2.x Administration Guide

PDF

Cisco Crosswork Network Controller 7.2.x Administration Guide

Migrate data using backup and restore

Updated: August 14, 2026

Want to summarize with AI?

Log in

Use backup and restore operations to migrate Crosswork configuration and operational data to a new installation or software version.

Migrate your data to a new installation or software version using backup and restore operations.

Use this task when upgrading your Crosswork installation to a new software version or moving data to a new installation. Data migration using backup and restore ensures that your configuration and operational data are preserved during transition. Perform these actions during a scheduled maintenance or upgrade window, and ensure users do not access the system during migration.

Before you begin

  • Configured a destination SCP server for storing data migration files (a one-time setup).

  • The hostname or IP address and the port number of a secure SCP server.

  • A file path on the SCP server to use as the destination for your data migration backup files.

  • User credentials for an account with file read and write permissions to the remote path on the SCP server.

  • Ensured that the Crosswork cluster and SCP server use the same IP environment (IPv4 or IPv6 as required).

  • Captured a screenshot of Data Gateways and recorded their assigned IP addresses and names for redeployment.

Procedure

1.

Configure the SCP backup server as your migration destination.

  1. In the Crosswork UI, go to Administration > Backup and Restore.

  2. Open Destination and enter the required server details.

  3. Save the backup server configuration.
2.

Create a migration backup.

  1. Log in as an administrator to the Crosswork installation you want to migrate.

  2. Go to Administration > Backup and Restore.

  3. Select Actions > Data backup and enter the necessary details, including a job name for the backup.

  4. (Optional) Select Force to allow backup in case of application or microservice issues.

  5. Complete any remaining required fields and adjust the destination if needed.

  6. Start the backup operation.

  7. Monitor backup progress in the Backup and Restore Job Sets table. Review job status and details as needed.

  8. If the upload fails, retry using Upload backup. Update the destination if required before retrying.
3.

Migrate the backup to the new installation.

  1. Log in as an administrator on the target Crosswork installation.

  2. Go to Administration > Backup and Restore.

  3. Select Actions > Data migration and enter the backup file name to restore from.

  4. Click Start migration. Monitor progress in the job list or dashboard.
4.

Deploy and verify Crosswork Data Gateways.

  1. Log out and log in to the Crosswork UI at https://<new_crosswork_ip>:30603. Acknowledge the Action to be taken pop-up after redeploying Data Gateways.

  2. Delete old Data Gateway VMs and install new gateways with identical IPs and names as previously recorded.

  3. Verify that each Data Gateway is deployed and registered with Crosswork.

  4. Check Data Gateway status in Administration > Data Gateway Management > Virtual Machines. Ensure Operation and Administration state are UP.

  5. After all gateways are active, confirm pool migration at Administration > Data Gateway Management > Pools and that Data Gateways are automatically enrolled.

  6. Log out and log back in again to Crosswork UI to trigger the Action to be taken pop-up, then click Acknowledge to complete migration.

    Do not use browser history links with a child path to access the UI; this prevents the pop-up from appearing.

  7. If NSO is set to read-only mode, disable it.

Data and configuration are successfully migrated to the new Crosswork installation. Data Gateways are redeployed and operational in the target environment.

What to do next

  • Verify all migrated services and Data Gateways are operational.

  • Go to Device Management > Network Devices and ensure that all devices are reachable and all the nodes are active. Then, select Actions, and choose Detailed sync all devices.

    This initiates a synchronization of all devices, ensuring their configurations and operational status reflect the most recent migration.

  • Perform any required post-migration configuration.