| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Can someone give me a rough estimate of the size ofthe file that will be created when I create my backup export file using upgrade_export? This is one smartcentre/enforcement module running on windows with about 40 rules, & one set of remote access vpns, nothing complicated? |
| |||
| I think it may also depend on logs you have in the $FWDIR/logs and any revision controls you have in the repository. If your file is larger than you expected, open it up with winzip and look at it to figure out why. If its smaller than you expected try restoring it (say in a VM) to see if everything is there. |
| |||
| My configuration is slightly larger than yours and has Edge boxes and site-to-site VPNs. On R55, it ran around 35 MB and on R62 it ran around 55 MB. As you add database revisions, it does grow at several megabytes for each revision. I usually keep a half dozen or so and my upgrade_export file hovers around 65 MB to 70 MB. Ray |
| |||
| I saw that the upgrade_export output from R62 to R65 is much bigger! Here's what I see: Upgrade_export R62: ~75 MB Upgrade_export R65: ~170 MB Regards Martijn |
| |||
| I think that if you have any packages in SmartUpdate, it will also increase the size. I noticed a rather large increase in mine (r60) when I deployed HFA_04 via SmartUpdate. My exported db size grew significantly when I imported those packages for SPLAT and IPSO. Those files are already compressed and it grew by almost the exact amount of those files so I'm guessing this was the cause. __________________ There's no place like 127.0.0.1 |
![]() |
| Thread Tools | |
| Display Modes | |
| |