{"id":284,"date":"2009-08-22T14:59:42","date_gmt":"1999-01-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/?p=284"},"modified":"2021-07-27T16:46:29","modified_gmt":"2021-07-27T16:46:29","slug":"shell-script-checkpoint-backup","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/firewalls\/check-point\/shell-script-checkpoint-backup.html","title":{"rendered":"Shell Script – Check Point Backup"},"content":{"rendered":"
This script will determine which operating system is running then backup the OS accordingly, once complete it will securely send it to the manager.<\/p>\n
The script is based on R65 and all backups will be sent to “\/var\/tmp\/backups” on the manager.<\/p>\n
Each time the backup is run it will write a system log confirming if it was successful or unsuccessful.
\nIf successful it will include the MD5 within the log message that you can use prior to any restores.<\/p>\n
You can download the script here.<\/a><\/p>\n Installation<\/strong><\/p>\n Server:<\/strong><\/p>\n Client:<\/strong><\/p>\n Server:<\/strong><\/p>\n How it Works \/ How to restore<\/strong><\/p>\n SPLAT<\/strong> To allow all the arps and routes to be saved with the use of the backup command the following should be used,<\/p>\n Note : At the point of the SPLAT backup being run on the manager you will need to run a cpstart afterwards to restore dashboard access. This at some future point will be written into the script. <\/em><\/p>\n IPSO<\/strong> Solaris<\/strong> Additional Notes<\/strong><\/p>\n If you have any issues with the script you can run it in debug mode by using the command `sh -x cp_backup.sh`<\/p>\n If you have any issues with the file being sent using the ssh keys you can debug this by using either,<\/p>\n * `ssh -vvv user@[manager ip]` on the client or This script will determine which operating system is running then backup the OS accordingly, once complete it will securely send it to the manager. The script is based on R65 and all backups will be sent to “\/var\/tmp\/backups” on the manager. Each time the backup is run it will write a system log confirming if … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"yoast_head":"\n\n
\n
\n
\nWhen running this script on SPLAT you will be running the `backup` command.
\nTo restore your backup use the `restore` command. You will need to restore the backupfile named “splat-backup_[hostname]_[date].tgz” using the restore command. The `restore` command will not restore the init.d scripts (such as the arp or route scripts). Because of this these are backed up separately within the file “[hostname]_runconfig_[date].txt” which is included within the tgz file “splat-backup_[hostname]_OS_[date ].tgz”.<\/p>\n\n
\nWhen running this script on IPSO you will be running the `manual backup` command within clish.
\nThis will backup up the whole operating system including all proxy arps and routes.
\nTo restore you backup use the command `clish -c “set restore manual \/[path]\/[filename].tgz”`<\/p>\n
\nwhen running this script on Solaris you will be backing up the main operating system files.
\nTo restore you will need to extract the necessary files from the tgz within Solaris.<\/p>\n
\n* `\/usr\/sbin\/sshd -d -p [port]` on the manager<\/p>\n","protected":false},"excerpt":{"rendered":"