Migrating Database Between R81.20 Security Management Servers
This procedure lets you export the entire management database from one R81.20 Security Management Server Dedicated Check Point server that runs Check Point software to manage the objects and policies in a Check Point environment within a single management Domain. Synonym: Single-Domain Security Management Server. and import it on another R81.20 Security Management Server Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server..
|
Important - Before you migrate the database:
|
Procedure:
-
On the source R81.20 Security Management Server, export the entire management database
Step
Instructions
1
Connect to the command line on the current R81.20 Security Management Server.
2
Log in to the Expert mode.
3
Go to the
$FWDIR/scripts/
directory:cd $FWDIR/scripts/
4
Export the management database:
If the "Endpoint Policy Management" blade is disabled on this Security Management Server-
And this Security Management Server is connected to the Internet, run:
./migrate_server export -v R81.20 [-l | -x] /<Full Path>/<Name of Exported File>
-
And this Security Management Server is not connected to the Internet, run:
./migrate_server export -v R81.20 -skip_upgrade_tools_check [-l | -x] /<Full Path>/<Name of Exported File>
If the "Endpoint Policy Management" blade is enabled on this Security Management Server-
This Security Management Server is connected to the Internet, run:
./migrate_server export -v R81.20 [-l | -x] [--include-uepm-msi-files] /<Full Path>/<Name of Exported File>
-
This Security Management Server is not connected to the Internet, run:
./migrate_server export -v R81.20 -skip_upgrade_tools_check [-l | -x] [--include-uepm-msi-files] /<Full Path>/<Name of Exported File>
For details, see the R81.20 CLI Reference Guide - Chapter Security Management Server Commands - Section migrate_server.
5
Calculate the MD5 for the exported database files:
md5sum /<Full Path>/<Name of Database File>.tgz
6
Transfer the exported databases from the source Security Management Server to an external storage:
/<Full Path>/<Name of Database File>.tgz
Note - Make sure to transfer the file in the binary mode.
-
-
Install a new R81.20 Security Management Server
Step
Instructions
1
See the R81.20 Release Notes for requirements.
2
Perform a clean install of the R81.20 Security Management Server on another computer.
-
On the R81.20 Security Management Server, import the databases
Step
Instructions
1
Connect to the command line on the R81.20 Security Management Server.
2
Log in to the Expert mode.
3
Make sure a valid license is installed:
cplic print
If it is not already installed, then install a valid license now.
4
Transfer the exported database from an external storage to the R81.20 Security Management Server, to some directory.
Note - Make sure to transfer the file in the binary mode.
5
Make sure the transferred files are not corrupted.
Calculate the MD5 for the transferred files and compare them to the MD5 that you calculated on the source Security Management Server:
md5sum /<Full Path>/<Name of Database File>.tgz
6
Go to the
$FWDIR/scripts/
directory:cd $FWDIR/scripts/
7
Import the management database:
-
If this Security Management Server is connected to the Internet, run:
./migrate_server import -v R81.20 [-l | -x] /<Full Path>/<Name of Exported File>.tgz
-
If this Security Management Server is not connected to the Internet, run:
./migrate_server import -v R81.20 -skip_upgrade_tools_check [-l | -x] /<Full Path>/<Name of Exported File>.tgz
Important - The "
migrate_server import
" command automatically restarts Check Point services (runs the "cpstop
" and "cpstart
" commands).For details, see the R81.20 CLI Reference Guide - Chapter Security Management Server Commands - Section migrate_server.
-
-
Test the functionality on the R81.20 Security Management Server
Step
Instructions
1
Connect with SmartConsole to the R81.20 Security Management Server.
2
Make sure the management database and configuration were upgraded correctly.
-
Disconnect the old Security Management Server from the network
Disconnect cables from the old Security Management Server.
-
Connect the new Security Management Server to the network
Connect cables to the new Security Management Server.