This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
This tool creates a backup of all GAIA gateway configurations with one CLI command "ebackup":
- Only one CLI command "ebackup" - Backup of all Gaia gateway configurations (Check Point appliances, Open Server, SMB appliances 11xx, 14xx) - Migrate export on SMS - Migrate-server on MDS - Backup all files to one TGZ file - FTP upload support backup file - CP upload support for backup file via cprid_util
- MDS > All CMA's are read out and their gateways backuped. - SMS > All gateways are read out and backuped.
Note: - Tested with R80.10, R80.20 and R80.30. - If the tool is started on a MDS, a mdsstop and mdsstart is performed during the migrate_server export.
CLI Parameter
Syntax
Description
-s
The option -s performs a cpstop and cpstart when the migrate export tool is executed.
-v
The option -v shows the gateway OS, JHF, Kernel, Type of all gateways.
-l
The option -l shows all ebackup tgz files in /var/log/.
-d
The option -d delete all ebackup tgz files in /var/log/.
-no_migrate / -n
The option -no_migrate has the consequence that no migrate export is executed.
-port <sms port> / -p <sms port>
The option -port <sms port> add the management server port, if it's not running on port 443.
-ftpserver <ftp server ip> -ftpuser <username> -ftppw <password>
The ftp options allow to upload the tar file to a ftp server.
- cpupload <cp_system_ip>
The option -cpupload performs a backup upload to a other Check Point gateway or SMS via cprid_util.
Example
# ebackup -> Backup all GAIA configs from all gateways + migrate export with locale backup file (/var/log/[date]_ebackup.tgz) # ebackup -s -> Backup all GAIA configs from all gateway + migrate export with cpstop and cpstart for migrate export # ebackup -no_migrate -> Backup all GAIA configs from all gateway without migrate export # ebackup -ftpserver 1.1.1.1 -ftpuser username -ftppw test123 -> Backup all GAIA configs from all gateway + migrate export with ftp upload
# ebackup -cpupload 1.1.1.1 -> Backup all GAIA configs from all gateway + migrate export with cp upload via cprid_util
Install Tool
Use this auto installer script from "Spoiler" on the SMS or MDS as CLI command in expert mode:
If an FTP upload is too insecure for you, you can also transfer the backup file to another Check Point system with the option -cpupload via cprid_util.
- Add parameter -s for cpstop/cpstart - Add ftpserver/ ftpuser and ftppw parameters for ftp upload.
0.1 03-15-2020 - oneliner to show backup clish configs 0.6 03-23-2020 - GA version ebackup 0.7 03-25-2020 - add parameter -s for cpstop/cpstart 0.8 03-26-2020 - add parameter -no_migrate (no migrate export) 0.9 03-26-2020 - bug fixed (special thanks to Paul_Gademsky) 1.0 03-27-2020 - bug fixed (SMS and MDS) 1.1 03-30-2020 - add option -port 1.2 03-30-2020 - bug fixed 1.3 03-31-2020 - ftp upload function (-ftpserver, -ftpuser, -ftppw)
2.0 04-04-2020 - MDS support 2.1 04-06-2020 - bug fixed 2.2 04-07-2020 - add option -v 2.3 04-09-2020 - add option -cpupload (upload tgz file to a other Check Point gateway or SMS)
3.0 06-20-2023 - Support for R81.20
➜ CCSM Elite, CCME, CCTE ➜ www.checkpoint.tips
asy Backup Tool
Features
This tool creates a backup of all GAIA gateway configurations with one CLI command "ebackup":
- Only one CLI command "ebackup" - Backup of all Gaia gateway configurations (Check Point appliances, Open Server, SMB appliances 11xx, 14xx) - Migrate export on SMS - Migrate-server on MDS - Backup all files to one TGZ file - FTP upload support backup file - CP upload support for backup file via cprid_util
Disclaimer: Check Point does not provide maintenance services or technical or customer support for third party content provided on this Site, including in CheckMates Toolbox. See also our Third Party Software Disclaimer.
We have also figured out that with MDM 80.30 and ebackup the path to the migrate export is wrong and we had to set that manually inside the ebackup script. here the infos about it:
We have also figured out that with MDM 80.30 and ebackup the path to the migrate export is wrong and we had to set that manually inside the ebackup script. here the infos about it:
Do you plan an option to include only sms without gateways in the backup file?
Also, I found when I run ebackup -v, I see that cpstop/cpstart are still executed. Shouldn't they be executed with -s flag only? I'm running R80.40 in AWS.
Regards,
Nikolay
Hi Heiko,
Thank you for the utility.
Do you plan an option to include only sms without gateways in the backup file?
Also, I found when I run ebackup -v, I see that cpstop/cpstart are still executed. Shouldn't they be executed with -s flag only? I'm running R80.40 in AWS.
Since we're using a Security product, could you also look at the option of copying the backup over scp with user/pass and a certificate or .key file? 😉
Thank you in advance.
Nikolay
Hi Heiko,
Thank you so much.
Since we're using a Security product, could you also look at the option of copying the backup over scp with user/pass and a certificate or .key file?
😉
I have copied the script onto an R80.40, and it's giving an error which is attached. This error has also been reported in the Easy View Tool (Easy View Tool - Check Point CheckMates) yet the solution didn't work for me.
Any ideas pls?
David
Hi Heiko,
Thank you very much for sharing this tool.
I have copied the script onto an R80.40, and it's giving an error which is attached. This error has also been reported in the Easy View Tool (Easy View Tool - Check Point CheckMates) yet the solution didn't work for me.
Hi @Amir_Arama, the ebackup script is written to run it on a Management Server too. Just install it on the Management Server and you can use the command "ebackup" to run. It will collect a "migrate_export" and "save configuration" from the management itself and all Gateways. Check the content of the output file in the end and you will see.
Hi
@Amir_Arama, the ebackup script is written to run it on a Management Server too. Just install it on the Management Server and you can use the command "ebackup" to run. It will collect a "migrate_export" and "save configuration" from the management itself and all Gateways. Check the content of the output file in the end and you will see.
There may be an issue with the ebackup script on a clean R81.10 SMS install. I have been running this on my SMS for a while now and everything has been working great. I think I started using ebackup around 80.30 or 80.40? I had done a clean install of R81 and imported my export, then reinstalled ebackup. I did an inplace upgrade to R81.10 back in July and my most recent backup from this past Monday has everything as expected. So ebackup was still running well.
I rebuilt my SMS today with a clean install of R81.10 and did a successful import and policy install. After installing ebackup and running "ebackup -s" the migrate exports fail in both the ebackup process and a manual process. As a sanity check, I rebuilt my SMS again, imported my previous export and everything was good. I was able to successfully migrate export to a file. Next I installed ebackup again, ran it, and the migrate export failed, along with my manual attempt after that.
There may be an issue with the ebackup script on a clean R81.10 SMS install. I have been running this on my SMS for a while now and everything has been working great. I think I started using ebackup around 80.30 or 80.40? I had done a clean install of R81 and imported my export, then reinstalled ebackup. I did an inplace upgrade to R81.10 back in July and my most recent backup from this past Monday has everything as expected. So ebackup was still running well.
If you run the command api status on your SMS, does it return "API readiness test SUCCESSFUL. The server is up and ready to receive connections"? If not, something else may be off/incorrect.
I might also look at your Management API Advanced Settings within Smart Console. I don't believe anything needs to be changed here, but worth a look. In SmartConsole, Manage & Settings, Blades, Management API Advanced Settings. For me, mine is set to Accept API calls from Mgmt server only.
If you run the command api status on your SMS, does it return "API readiness test SUCCESSFUL. The server is up and ready to receive connections"? If not, something else may be off/incorrect.
I might also look at your Management API Advanced Settings within Smart Console. I don't believe anything needs to be changed here, but worth a look. In SmartConsole, Manage & Settings, Blades, Management API Advanced Settings. For me, mine is set to Accept API calls from Mgmt server only.
Can you confirm the format of your Cronjob command in the documentation. It shows as 22 00 * * 6 for 10:00PM on Saturday but when I look at Cron formats that would be at 12:22. 10:00pm would be 00 22 * * 6. Can you confirm?
Thanks,
Hello Heiko,
Can you confirm the format of your Cronjob command in the documentation. It shows as 22 00 * * 6 for 10:00PM on Saturday but when I look at Cron formats that would be at 12:22. 10:00pm would be 00 22 * * 6. Can you confirm?