Description

This article explains the issue wherein the data migration from 23.1 to 24.1 SDI server fails at 75%.


Links followed are as follows:


For the setup of the new VM:

https://www.juniper.net/documentation/us/en/software/nm-apps24.1/sd-insights-gsg/topics/topic-map/sd-insights-ova-install.html


For the data migration:

https://www.juniper.net/documentation/us/en/software/nm-apps24.1/sd-insights-gsg/topics/task/sd-insights-data-migration.html



Symptoms

Error messages seen during the migration status check:


Output for the data migration


############################


Core#(applications)# show data-migration status

Data migration started at: Wed Feb 26 12:09:40 2025


Migrating configuration data

Migrating configuration data complete

Migrating database

Migrating database complete

Migrating log data

Progress: [==============================         ] 75.444%

2025-03-06 14:45:33.836306 - ERROR: Encountered error while migrating log data. Restoring backups...


############################


In the /var/log/cyos/datamigration/ , you can see the following error messages:


Reindexing elasticsearch index cy-event-2024.11.20

2025-03-07 09:17:29.757972 - Waiting for reindex tasks to complete

2025-03-07 14:45:22.641600 - Detected no reindex tasks running, migration completed

2025-03-07 14:45:33.719004 - Elasticsearch data migration failed with completed task error body=<!DOCTYPE html>

<html>

<head>

<title>Error</title>

<style>

   body {

       width: 35em;

       margin: 0 auto;

       font-family: Tahoma, Verdana, Arial, sans-serif;

   }

</style>

</head>

<body>

<h1>An error occurred.</h1>

<p>Sorry, the page you are looking for is currently unavailable.<br/>

Please try again later.</p>

<p>If you are the system administrator of this resource then you should check

the error log for details.</p>

<p><em>Faithfully yours, nginx.</em></p>

</body>

</html>



Solution

The data migration usually fails at 75% due to an issue at the 23.1 server side as the data is still being collected from there at this stage.

 

Here are the things to check to correct the error messages seen:

 

  1. Check if the CPU on the 23.1 SDI server is high.
  2. If yes, then please check if the live traffic from the devices has been diverted to the 24.1 server or not. The live traffic plus the data migration task is bound to cause high CPU on the 23.1 server which can lead to the failure of the data migration.

In case the issue is not resolved, please contact JTAC for further assistance.

Modification History

2025-04-29 : Article Created