Migrate signals data between Fusion 4.x environments with a fresh install

Goal

Migrate existing signals data from a Fusion 4.2.5 deployment to a freshly installed Fusion 4.2.6 SP3 environment.

Environment

Fusion 4.2.5 and Fusion 4.2.6 SP3 (Self-hosted)
This approach is applicable when:

• The target Fusion 4.2.6 SP3 instance was installed fresh (not upgraded in place).

• Signal collections already exist in the target environment and are named identically to those in the source environment.

• Solr collections are co-located on the Fusion leader nodes.

Guide

Confirm collection structure

Before copying data:

• Ensure the same signals collections (including aliases, if applicable) exist on the new Fusion 4.2.6 SP3 instance.

• Collection schemas and configurations should match to prevent indexing or query issues after the transfer.

Identify leader node locations

Copy data only from the leader node of each relevant Solr collection. Use the Solr Admin UI or API to identify the node hosting the leader shard for each signals collection.

Use rsync to copy index data

Use the rsync utility to copy collection index data from the leader node of the Fusion 4.2.5 environment to the leader node in the Fusion 4.2.6 SP3 environment.

Run the following command from the source leader node:

rsync -va /path/to/source/index/data /path/to/target/index/data

Flags used:

• -v: verbose — shows progress during the transfer

• -a: archive — preserves permissions, timestamps, symbolic links, etc.

Example:

rsync -va /var/solr/data/signals_shard1_replica_n1/ /var/solr/data/signals_shard1_replica_n1/

Make sure you:

• Match the collection and shard names exactly.

• Only copy the index data for leader replicas. Solr followers will sync automatically from the leader upon startup or reinitialization.

Restart Solr or reload collections (if necessary)

Depending on your environment configuration, a Solr pod restart or collection reload may be required to recognize the transferred index data.

Use the Solr Admin UI or API to reload the collection if the changes do not appear immediately.

Verify data integrity

Once the data is copied and collections are active:

• Perform queries against the signals collections to confirm the presence and accuracy of migrated data.

• Check logs for errors related to indexing or collection state.