- Products
- Learn
- Local User Groups
- Partners
- More
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Improve Your Security Posture with
Threat Prevention and Policy Insights
Overlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Greetings all.
According to the R82 Release Notes it is not supported to do an in-place upgrade of a management server running on open hardware or VM more than once. Is there a specific reason for this? It's not mentioned anywhere in the documentation.
I can fully accept that a fresh install is necessary every now and then but to expect one every two versions seems a little excessive.
Good question.
You are referring to this:
"Notes:
On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed."
And the text in https://support.checkpoint.com/results/sk/sk168335
"On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed. See here for more information,
To upgrade again, use an Advanced Upgrade (with Clean Install) or an Upgrade with Migration - see Upgrade Methods."
The 'here' link in the SK is broken and probably should point to here: https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_RN/Content/Topics-RN/HW-Requiremen...
But that doesn't explain in it.
I have put this feedback forward for the SK:
"On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed. See here for more information,"
The link in 'here' is broke (not found) and there does not seem to be a reason or any details for the limitation.
What is the reason?
Is this still valid?
Is there a technical block?
Check Point release new major versions every 18 months or so on average.
Considering the nature of the platform and the history (changes to file systems (ext3 --> xfs) and new default partition sizes for new builds)) and how some solutions are originally designed and deployed it is often not a bad idea to consider the clean build and import every 3 to 5 years.
One example of a change in design for clean builds is the IPS database updates now go to /var/log (and not / ) but only if you do a clean install R81.20 or R82, not an upgrade.
It can be configured/changed manually after an upgrade but if not then the root partition is still used, meaning that free disk issues are more of a risk.
It does put the burden on the customer to do the extra work (export -> rebuild -> import but it is an opportunity to get up to speed with best practices (some out-of-the box) and clean old legacy configurations up.
https://www.checkpoint.com/support-services/support-life-cycle-policy/#software-support
Hopefully they can update the SK and RN.
In the past, there were specific changes where this was needed to address some underlying issues:
The only way to "fix" those issues is a complete reinstall.
Not sure if this is the reason for the stated policy, only providing some justification for doing an advanced migration every so often.
Good question.
You are referring to this:
"Notes:
On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed."
And the text in https://support.checkpoint.com/results/sk/sk168335
"On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed. See here for more information,
To upgrade again, use an Advanced Upgrade (with Clean Install) or an Upgrade with Migration - see Upgrade Methods."
The 'here' link in the SK is broken and probably should point to here: https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_RN/Content/Topics-RN/HW-Requiremen...
But that doesn't explain in it.
I have put this feedback forward for the SK:
"On an Open Server / Virtual Machine that runs a Management Server / Log Server , only one upgrade is allowed. See here for more information,"
The link in 'here' is broke (not found) and there does not seem to be a reason or any details for the limitation.
What is the reason?
Is this still valid?
Is there a technical block?
Check Point release new major versions every 18 months or so on average.
Considering the nature of the platform and the history (changes to file systems (ext3 --> xfs) and new default partition sizes for new builds)) and how some solutions are originally designed and deployed it is often not a bad idea to consider the clean build and import every 3 to 5 years.
One example of a change in design for clean builds is the IPS database updates now go to /var/log (and not / ) but only if you do a clean install R81.20 or R82, not an upgrade.
It can be configured/changed manually after an upgrade but if not then the root partition is still used, meaning that free disk issues are more of a risk.
It does put the burden on the customer to do the extra work (export -> rebuild -> import but it is an opportunity to get up to speed with best practices (some out-of-the box) and clean old legacy configurations up.
https://www.checkpoint.com/support-services/support-life-cycle-policy/#software-support
Hopefully they can update the SK and RN.
Thanks for the reply Don.
I fully agree with everything you've said, I just don't see why this should only apply to open servers / VMs and not also to Smart-1 appliances.
True. Especially considering a Smart-1 appliance could have a supported life span of 7 years (9 if End of Engineering Support is included).
If upgrades after the first one is not technically blocked then I would be happy to go for it but they've got that documented so for a TAC they can always recommend or push a clean install and import to get full support.
For that reason I would follow their guidance but it is ideal if it's explained in more detail.
PS. I have received the acknowledgement for the feedback for the SK and will post the response in here what I hear back.
Wow, goot catch there, never noticed that before.
In the past, there were specific changes where this was needed to address some underlying issues:
The only way to "fix" those issues is a complete reinstall.
Not sure if this is the reason for the stated policy, only providing some justification for doing an advanced migration every so often.
I wasn't aware of that either.
However, we always perform upgrades using clean installation and migrate export and import.
Therefore, the question does not arise for us.
I also believe thats the best approach.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 8 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Wed 03 Dec 2025 @ 10:00 AM (COT)
Última Sesión del Año – CheckMates LATAM: ERM & TEM con ExpertosThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAThu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasWed 03 Dec 2025 @ 10:00 AM (COT)
Última Sesión del Año – CheckMates LATAM: ERM & TEM con ExpertosThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAThu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY