| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Within SmartDashboard, I'd configure daily log rotation, generally at midnight. Then (assuming you're using a Unix variant as your log server), I'd run a script to compress anything older than a week, and then copy them to wherever you want them copied to for backup - e.g. scp them somewhere else, or copy to tape, or however it is you want to back them up. One thing to consider is how long you will be backing them up for, and whether it is acceptable to store them in Check Point format, or if you need to store them in a plaintext format. Consider what might happen if you needed to read a logfile from 7 years ago - it would probably be in 4.1 format, and you would have to set up a 4.1 server to read them - but you probably wouldn't be able to find the installation CD. So some places have a policy of running fw logexport, then backing up the text files. |
| |||
| hi mate thanks a lot for ur reply .mate does running the upgrade export on the log servers will backup the logs as well. and can we set the log backup from daily to weekly as well. thanks a lot buddy. regards sebastan |
| |||
| It's been a while since I configured it, but off the top of my head, the backup option on SPLAT included an option as to whether or not to include the logs. Can't remember if upgrade_export includes them - think not. Yes you can set the logs to rotate whenever you want. Set up a time object for the right time/frequency, then configure it on the management server object in SmartDashboard. Otherwise use fw logrotate from cron. |
| |||
| Quote:
|
| |||
| Correct. On SPLAT there is a switch to allow the backup command to include logs - but that means it backs up all the logs in your $FWDIR/log directory, which can make your backups pretty huge. |
![]() |
| Thread Tools | |
| Display Modes | |
| |