Upgrade Tools

Important - You must always use the latest version of the R81.10 Upgrade Tools from sk135172 to:

Notes:

If the Management Server / Log Server Dedicated Check Point server that runs Check Point software to store and process logs. is connected to the Internet and you enabled the "Allow Download" consent flag (see sk111080), then the server downloads and installs the latest version of the Upgrade Tools automatically.

To enable the "Allow Download" consent flag:
- In the Gaia Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. First Time Configuration Wizard, you selected the option Automatically download Blade Contracts, new software, and other important data.
- In SmartConsole Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on., you selected the option Automatically download Contracts and other important data in Menu > Global properties > Security Management.
If the Management Server / Log Server is not connected to the Internet, then you must install the latest version of the Upgrade Tools manually.

These Upgrade Tools:

Make sure it is possible to upgrade the current management database without issues.
Generate an upgrade report with the list of detected issues that can fail the upgrade.

The upgrade report shows these messages:

Message Category	Instructions
Action items before the upgrade	Errors you must repair before the upgrade. Warnings of issues for you to decide whether to fix before upgrade. An example of an error you must fix before the upgrade is an invalid policy name.
Action items after the upgrade	Errors and warnings that you must fix after the upgrade.
Information messages	Items to be aware of. For example, an object type is not supported in the higher version, but is in your database and it is converted during the upgrade.

Message Category

Instructions

Action items before the upgrade

Errors you must repair before the upgrade.

Warnings of issues for you to decide whether to fix before upgrade.

An example of an error you must fix before the upgrade is an invalid policy name.

Action items after the upgrade

Errors and warnings that you must fix after the upgrade.

Information messages

Items to be aware of.

For example, an object type is not supported in the higher version, but is in your database and it is converted during the upgrade.

The most important files in the Upgrade Tools package:

Package	Instructions
`migrate_server`	Exports and imports the management database and applicable Check Point configuration. For details, see the R81.10 CLI Reference Guide > Chapter Security Management Server Commands > Section migrate_server.
`migrate.conf`	Contains configuration settings for Advanced Upgrade / Database Migration Process of: (1) Installing the latest Security Management Server or Multi-Domain Server version from the distribution media on a separate computer from the existing Security Management Server or Multi-Domain Server (2) Exporting the management database from the existing Security Management Server or Multi-Domain Server (3) Importing the management database to the new Security Management Server or Multi-Domain Server This upgrade method minimizes upgrade risks for an existing deployment..

Package

Instructions

migrate_server

Exports and imports the management database and applicable Check Point configuration.

For details, see the R81.10 CLI Reference Guide > Chapter Security Management Server Commands > Section migrate_server.

migrate.conf