migrate_server Import - Run Multiple Times

[Yeti]

What is recommended when a "migrate_server import" operation fails or stops unexpectedly?   I've noticed the script just stall if you try to reimport after a failure.  Is there a need to "reset" a flag or similar within a linux file?  

[PhoneBoy]

migrate_server import will only run on a freshly installed management server.
I presume with migrate_server import failing, the management database is no longer "freshly installed."
The only way to reset is to reinstall the management server.

When you do that, complete the First Time Wizard and configure the OS appropriately.
Then, take a snapshot.
If migrate_server import fails again, you'll be able to revert to a state where you can run it again.
Please engage the TAC if this occurs again.

[Yeti]

Thank You! That's the info I was looking for...  Experienced issues Migrating from R80.20 to R81.10 fresh ISOmorphic install.  In hindsight it may have been better to perform an in place upgrade to R80.40 or possibly R81.10 and then decide on whether or not to perform a clean install...   

[PhoneBoy]

In your situation, I would have done the same thing (clean install/advanced migration).
This is because we've made changes to the partitioning and filesystem used in R80.40, which improves performance.
A clean install from ISO is the only way to apply those changes.

[the_rock]

Based on your description, I assume it does not show you any reason for the failure?

[Yeti]

The Upgrade Report showed it failed on "Importing Management Database" Check Point Data - System Data - Error Message

"Failed to execute command /opt/CPupgrade-tools-R81.10/bin/migrate import --config_only -n -l -x --include-uepm-msi-files --smartlog /var/log/temp-export/a0eebc99-afed-4ef8-bb6d-fedfedfedfed.tgz. Failed to execute"

[the_rock]

Okay...just to make sure (as I dont like to assume anything), did you follow below process?

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...

[Yeti]

Yes, followed this exactly.  Tripple checked the BuildNumbers were correct on both export and import...

[Alex-]

I see you're importing an Harmony Endpoint server with MSI files. This one took me a few tries also.

Make a fresh install on the target server, run the FTW and then do not install the jumbo. It always failed to import the export when I did it first.

Run the migrate-server import procedure on R81.10 on the newly installed SMS then when done install the jumbo, which can take about one hour for the EPS component.

Make sure your migration tools are up to date on the source and target servers as per sk135172 - Upgrade Tools package for upgrade from R80.20 and higher (checkpoint.com)

In my case, also I had to use the --ignore-warnings flag. Also, make sure you have plenty of disk space available in your partitions. Even with a few MSI in the store, my export was more than 6GB.

[Yeti]

This is just a Standalone appliance, no Harmony Endpoint functionality...

[G_W_Albrecht]

Why --include-uepm-msi-files - this is only used with Endpoint ?

[Yeti]

I did not include that switch in the original command.  That error was from the HTML upgrade report produced from the script...

[ivdolbnia]

Facing exact same issue with my migrate_server import - were you able to resolve this ?