- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Hi,
my migrate export file is about 5.1GB size, is it normal?
i have about 60 GWs, 4 policy packages, total of about 1000 rules & most of blades enabled.
i run r80.10 gaia, but it was around this size also on r77.30
Thanks
To me, that does not seem to be an unreasonable size for a migrate export, especially given the number of rules and objects involved.
You need check are there any Revision Control packages?
Otherwise it is an unreasonable size for a migrate export.
Hi, coming back here, is it possible to you that an exported db from an R80 smart-1 is about 20GB???
I deleted the revisions older than 2019. What do you suggest?
Thanks
Could well be the issue from sk164270: Migrate export file is abnormally large
you right... try to convince the customer and go head deleting them
Having an excessive number of old IPS updates hanging around can significantly drive up the size of a migrate export in R80+ into the multi-GB range. Under Threat Prevention...Threat Tools...Updates...IPS...Update Now...Switch to Version you can see how many old IPS updates are present. If there are a lot, see here for the cleanup procedure:
To reduce the export size you can also try purging old published sessions on the Manage & Settings...Revisions screen, just right click the various sessions and select Purge.
Hi Timothy, thanks for the answer. I deleted all the old log files.
Then I tried to used the $MDS_FWDIR/scripts/run_groovy_script.sh $MDS_FWDIR/scripts/IpsDomainFilesCleanup.groovy command but I got:
groovy.util.ResourceException: Cannot open URL: file:/opt/CPsuite-R80/fw1/cpm-server/dummy/opt/CPsuite-R80/fw1/scripts/IpsDomainFilesCleanup.groovy
at groovy.util.GroovyScriptEngine.getResourceConnection(GroovyScriptEngine.java:371)
at groovy.util.GroovyScriptEngine.loadScriptByName(GroovyScriptEngine.java:504)
at groovy.util.GroovyScriptEngine.createScript(GroovyScriptEngine.java:564)
at groovy.util.GroovyScriptEngine.run(GroovyScriptEngine.java:551)
at com.checkpoint.management.groovy_client.ManagementGroovyClient.runScript(ManagementGroovyClient.java:11)
at com.checkpoint.management.cpm.commands.GroovyClient.run(GroovyClient.java:14)
at com.checkpoint.management.cpm.Cpm.main(Cpm.java:70)
Indeed I checked the IPS update and the oldest one is dated 2017, but if this command does not work I don't know how to remove the old unnecessary files.
I also removed the published sessions correctly. I guess removing the IPS signatures will reduce the size of the db finally.
If that script doesn't work with the latest SMS versions you'll probably need to engage with TAC, hopefully they have a more recent copy you can use. About how many IPS update packages are you seeing? If it is more than 10 I'd definitely try to clean it up before the migrate export as I've seen lots of old IPS packages spike a migrate export past 20GB.
raising an SR to TAC. I'll let you know.
thanks
Hi,
TAC from CheckPoint jsut told me that IPS signatures are cumulative. If I'd delete one signature I'll loose some specific configuration.
So I have signature of 2017 that are still being used??
I'm pretty sure that is not correct unless something radically changed in R80.20 or later, as far as I know an IPS Update is a standalone file that contains all IPS ThreatCloud Protections; you don't need to have the older IPS Update files for the newer ones to work.
But perhaps only the deltas are being sent in the latest IPS updates? We will probably need an answer from R&D on this one, paging @PhoneBoy ...
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY