Migrate from 24.2.15.5 to 24.10.10.70 - How to verify status

[EF]

Hi Team,

I was connecting for ssh to the new server (rel 24.10.10.70) and launch the script in the step 9 of the migration guide (https://emc.extremenetworks.com/content/oneview/install/migration_from_24_2.htm😞

sudo /usr/local/Extreme_Networks/NetSight/scripts/migrateFromVersion24_2.sh -s <IP-of-the-source> -u <username-for-OS-access>

After 3 hours I lost SSH to rel 24.10 server. I few hours later the the GUI of the new server (https://IP:8443/) doensn´t respond, so I dont know if the script is still working in background and it doesn´t end or if the script stopped when I lost the SSH session.

Is there any way to verify the status of migration?

Regards

EF

[OscarK · Accepted solution]

I could not find a log so checking process could be a method.

However, if the migration takes that long, if possible it would be good to reduce retention time for end system events and after the DB decreased enough try again ?

You can rerun the migrate script, it will wipe the database again and restart.

[Zdeněk_Pala · Accepted solution]

If you run it again, it is recommended that you do so from the console. Losing connectivity will not affect the console.

[EF]

Hi Team,

At the end, as is a fresh installation I depoy a new machine a rerun the script from hypervisor´s console, after 5 hours all was done.

Thanks for your answers.

Regards

EF

[Robert_Haynes · Accepted solution]

See https://extreme-networks.my.site.com/ExtrArticleDetail?an=000120709.

If the migration of the database takes a very long time or appears to stall, even via console, then please collect the logs per the article and open a case.

See also https://extreme-networks.my.site.com/ExtrArticleDetail?an=000115302 as this is a potential database source that results in prolonged or hung migration activity.

As OscarK pointed out a large Control End Systems table so see an older article @ https://extreme-networks.my.site.com/ExtrArticleDetail?an=000110091 and the section about changing data persistence settings.

[Zdeněk_Pala · Accepted solution]

If you run it again, it is recommended that you do so from the console. Losing connectivity will not affect the console.

[OscarK · Accepted solution]

I could not find a log so checking process could be a method.

However, if the migration takes that long, if possible it would be good to reduce retention time for end system events and after the DB decreased enough try again ?

You can rerun the migrate script, it will wipe the database again and restart.