Restore Crosswork Network Controller data to a newly deployed cluster after a natural or human-caused disaster destroys the original cluster.
Use this task when the original Cisco Crosswork cluster has been destroyed due to a natural or human-caused disaster. A new cluster must be deployed with the same configuration as the original before restoring data.
Before you begin
Before you begin:
-
Obtain the full name of the backup file from the SCP backup server (typically the most recent backup). Backup filenames follow this format:
backup_JobName_CWVersion_TimeStamp.tar.-
JobName is the user-entered name of the backup job.
-
CWVersion is the platform version of the backed-up system.
-
TimeStamp is the date and time when backup file was created.
Example:
backup_Wednesday_7-2_2026-01-25-12-00.tar. -
-
Ensure the new cluster uses the exact versions of all applications and the platform as the original cluster. Any mismatch can cause data loss or restore failure.
-
Use the same IP addresses, number and types of nodes, and software image as the original cluster. Internal certificates depend on these details.
-
Keep backups current. If you installed new applications or patches since the last backup, create a new backup.
-
If only a single hybrid node or one or more worker nodes are malfunctioning, do not perform disaster recovery. Use cluster management features to replace or redeploy these nodes. If multiple hybrid nodes are malfunctioning and the system is nonfunctional, deploy a new cluster and restore using a recent backup.
-
Smart licensing registration for applications is not restored and must be registered again after the restore.
-
If recovery fails, contact Cisco Customer Experience for assistance.
-
After restore, use the Configuration Database CLI tool to identify and reload any missing SR policies or RSVP-TE tunnels. See Orphaned SR-TE policies and RSVP-TE tunnels for more details.
Procedure
| 1. | Deploy a new cluster as described in the Cisco Crosswork Network Controller 7.2.x Installation Guide. |
|
| 2. | From the main menu, go to . |
|
| 3. | Click to open the Data Disaster Restore dialog. |
|
| 4. | In the Backup File Name field, enter the backup file name to restore. |
|
| 5. | Click Start Restore. To monitor progress, use the progress dashboard link. |
The new cluster restores its data from the specified backup file. The configuration and data state return to the point of the last backup.
What to do next
-
Re-register smart licensing for all restored applications.
-
Use the Configuration Database CLI to identify and reload any missing SR policies or RSVP-TE tunnels.