- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
CheckMates Fest 2026
Watch Now!AI Security Masters
Hacking with AI: The Dark Side of Innovation
CheckMates Go:
CheckMates Fest
Hello. I have a few questions. We are upgrading the system from R81 20 JH T 118 to R82. We have sms, smart event and syslog servers each on a separate server. We upgraded sms to R82 via CPUSE but we get the error as shown in the picture on smart event and syslog servers, we found another way. I run ''./migrate_server verify -v R82'' and get a warning upgrade_report. I saw sk in the report sk175089 but it says about Security Management Server. Even if these problems are solved, the size of the syslog server is more than 60 TB. In this case, will ''./migrate_server export -v R82 [-l | -x] /<Full Path>/<Name of Exported File> '' and import work? If the exported_file.tgz is also close to 60TB, there is no space on the disk to get it. What can I do? maybe there are other ways? Thanks for any ideas!
Please attach the image with the error?
Small correction.
Check Point logging is not syslog, it is a proprietary logging solution.
That can offer option for migration with the log files, which can be handled separately.
Can you share more on the platforms, VMs or appliances?
Also if its migration to new platforms or in-place upgrades?
The upgrade guide covers many scenarios.
It sounds like your logs are too big to consider including them in an export.
Javoblar uchun rahmat! Men yuqoridagi havolalarni ko'rib chiqaman. Aslida, o'z joyida yangilanishlar biz uchun yaxshi yechim bo'lardi. Men rasmlarni joylashtiraman.
That looks like Uzbek language to me, Im sure I had seen it there :). Anyway, looks like it succeeded with warnings.
Without -l / -x
It exports the management database and Check Point configuration only (objects, policies, blades config, etc.). Logs are not included.
For a log server it is not a full database export equal to the primary management server but there is a postgres database export which exports what is synced from the primary and also the actual configuration of the log server.
It will be hundreds of MB rather than TB.
There does not appear to be anything attached to your post. Is there space issue?
Based on the screenshots, appears it did work, but its complaining about secondary server...management HA?
sms, smart event and syslog are each separate servers and work separately. It is not high availability. The picture showing 2 errors belongs to the syslog server and 1 error belongs to smart event.
So then why would it show below?
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 52 | |
| 40 | |
| 14 | |
| 13 | |
| 13 | |
| 11 | |
| 11 | |
| 8 | |
| 8 | |
| 7 |
Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesMon 23 Feb 2026 @ 11:00 AM (EST)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - AMERTue 24 Feb 2026 @ 10:00 AM (CET)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - EMEAThu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesMon 23 Feb 2026 @ 11:00 AM (EST)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - AMERTue 24 Feb 2026 @ 10:00 AM (CET)
Latest updates on Quantum Spark including R82 features and Spark Management zero touch - EMEAFri 06 Mar 2026 @ 08:00 AM (COT)
Check Point R82 Hands‑On Bootcamp – Comunidad DOJO PanamáAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY