- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi Community,
we backup our Management with Backbox. Currently the backup fails due to the following message in Backbox Log:
14-04-2025 03:01:00 $FWDIR/bin/upgrade_tools/migrate export -n /var/log/BackBox/CheckPointR_MigrateExport.tgz
14-04-2025 03:01:08 Execution finished with errors. See log file '/opt/CPshrd-R81.20/log/migrate-2025.04.14_03.01.06.log' for further details
14-04-2025 03:01:08 Session Migrate Export (SSH) execution finished. Session Result:FAILURE, Message: Execution finished with errors
If we take a look into /opt/CPshrd-R81.20/log/migrate-2025.04.14_03.01.06.log we see:
"Operation failed. The target version does not support 'Network Group' objects that contain inner groups with 'Data Center Objects'. The following 'Network Group' objects contain inner groups with 'Data Center Objects':
EncDom_Remote_Access"
The network group "EncDom_Remote_Access" contains a network group, which again contains 3 Domain Objects and 2 Updatable Objects.
So basically "migrate export" fails.
If I manually "migrate_server export" instead, the export is successful.
What would be the way to go?
When I follow https://community.checkpoint.com/t5/Management/migrate-server-export-versus-migrate-export/m-p/13531... migrate_server uses the same legacy "migrate export" when target version stays the same. So what would be the issue here?
No use to discuss that - remember that you refer to a CheckMates post from 01-12-2021 ! In the following information sources, this is never mentioned (and seems not to be true today):
https://support.checkpoint.com/results/sk/sk135172
https://support.checkpoint.com/results/sk/sk164932
https://support.checkpoint.com/results/sk/sk163814
Issue here is that Backbox uses the legacy migrate export instead of the currently supported migrate_server - so i would ask Backbox for help, not CheckPoint 😉
I almost expected an answer like that...
I realize that migrate is legacy, but if migrate_server uses migrate in the background, as in the linked article, when exporting to the same version, I still wonder why one works and the other doesn't:
"migrate_server is the new tool for upgrade, but even if you use it for migration within the same version - behind the scenes it will automatically run the legacy migrate for you (which can also be run manually)."
No use to discuss that - remember that you refer to a CheckMates post from 01-12-2021 ! In the following information sources, this is never mentioned (and seems not to be true today):
https://support.checkpoint.com/results/sk/sk135172
https://support.checkpoint.com/results/sk/sk164932
https://support.checkpoint.com/results/sk/sk163814
Which types of Data Centers do you have?
Do you have NSX data center perhaps?
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 16 | |
| 15 | |
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY