| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Is the backup option on Voyager OK for backing up the checkpoint parts as well? We will only be backing up the configuration whenever we make changes not regularly so will be doing it manually. This would make things a lot easier than backing up both systems separately. Does anyone else do it this way? any other recommendations? Has anyone ever restored a system doing it this way? Thanks, HH __________________ Fishing for a clue on exactly what to do.... |
| |||
| It will back up the Check Point data that is on the firewall. If your management station is on another appliance then it will not back up all that you will need. In fact, if your managment station is on another appliance it's useless to backup Check Point on the firewall. |
| |||
| What Lackie has stated is correct. If you also plan to use the automated ftp transfer of the backup file created from within Voyager you may find it does not work even though you can ftp\tftp with the same credentials from the command line of the device. Well that is my experience........... |
| |||
| Thanks guys appreciate your time to respond to this. We will be manually FTPing the Nokia backups. The management station is on another system so we will back that up separately - silly question in the first place now I think about it. Just more procedures for me to write seeing as they didn't have any when I started here - inheriting other peoples work is a nightmare - wish i could have just started from scratch. __________________ Fishing for a clue on exactly what to do.... |
| |||
| it's also fairly easy to do an 'ipso backup' using on the CLI (which can be restored using the Voyager GUI). set all the variables you want in clish.. or in voyager.. or using dbet and then a simple: // /etc/backup -f /var/etc/backup_vars.sh // will create the backup tar ball. -- Iain |
| |||
| The backup tarball is very useful. I do one now after every major change so that I can just drop it on another Nokia Chassis if need be - which I have had to do in my very short time working on them. |
| |||
| Quote:
|
| |||
| When you use the Nokia restore, you need to make sure that the CP products and IPSO are the same version and HFA level as they were originally before you do the restore or you're going to get weird warnings. It does work, but frankly it doesn't take that long to completely rebuild a new enforcement module by installing all new packages. If you do printouts of all of the screens and routing stuff, a restore may be more hassle than manually re-entering everything. That being said, I do keep a Nokia backup on my SmartCenter. I also keep the current IPSO image, the current HFA and the current CP wrapper on it as well in case I have to rebuild an enforcement module. I've had to do it once with an IP120 due to a hard drive failure. The replacement came with IPSO 3.8.1 and R55P while we were using IPSO 3.7.1 and R55. It took about an hour to rebuild it the way it used to be, and I was doing it remotely across a WAN from the other side of the country. Ray |
![]() |
| Thread Tools | |
| Display Modes | |
| |