- Products
- Learn
- Local User Groups
- Partners
- More
What's New in Check Point SASE
Wednesday, 9 September @ 5pm CET / 11am EDT
The State of Ransomware Q2 2026:
This Quarter's Trends, and Their Impact on Your Defenses
AI Security Masters
Implementing the AI Security Trifecta
CheckMates Go:
Half is Not Enough
Hi everyone,
I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:
1. Does purging previous revisions affect our current database/policy?
2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?
3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?
Thank you.
Regards
Hi everyone,
I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:
1. Does purging previous revisions affect our current database/policy?
2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?
3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?
Thank you.
Regards
Hi everyone,
I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:
1. Does purging previous revisions affect our current database/policy?
2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?
3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?
Thank you.
Regards
1. it affects the database - but only the revisions stored in it, and not the current policy/config
2. yes
3. Use that from here: https://sc1.checkpoint.com/documents/latest/APIs/index.html#cli/set-automatic-purge~v1.7%20
1. it affects the database - but only the revisions stored in it, and not the current policy/config
2. yes
3. Use that from here: https://sc1.checkpoint.com/documents/latest/APIs/index.html#cli/set-automatic-purge~v1.7%20
Im not so sure purging bunch of revisions will do anything for CPU. Has anyone actually determined what process is causing cpu issue?
Andy
Im not so sure purging bunch of revisions will do anything for CPU. Has anyone actually determined what process is causing cpu issue?
Andy
there are few things has been done with tac so far & still going on:
view cpu processes, cpmdoc, clearing objects without worksession (based on cpmdoc), healthcheck, hw diag, cpinfo, migrate export for tac's lab & after generating cpmdoc report (again), tac suggested to purge old revisions.
No exact conclusion yet. I assume it might be spec issue. But the customer will need a clear statement from tac, at least.
there are few things has been done with tac so far & still going on:
view cpu processes, cpmdoc, clearing objects without worksession (based on cpmdoc), healthcheck, hw diag, cpinfo, migrate export for tac's lab & after generating cpmdoc report (again), tac suggested to purge old revisions.
No exact conclusion yet. I assume it might be spec issue. But the customer will need a clear statement from tac, at least.
Personally, just my view, I dont see how purging old revisions would do anything in this case. Maybe if say mgmg server was lagging a bit or dashboard was slow. What process is consuming most cpu?
Andy
Personally, just my view, I dont see how purging old revisions would do anything in this case. Maybe if say mgmg server was lagging a bit or dashboard was slow. What process is consuming most cpu?
Andy
Something about java cpsead logindexer etc. (if I'm not mistaken bcs no access to customer's environment currently).
& doctor log shows sizing error as the appliance can only support 300 logging/s, while the current average is 2000+ logs/s.
Something about java cpsead logindexer etc. (if I'm not mistaken bcs no access to customer's environment currently).
& doctor log shows sizing error as the appliance can only support 300 logging/s, while the current average is 2000+ logs/s.