Advanced Upgrade and Database Migration

In This Section: Before and After Database Migration Supported Upgrade Paths, Platforms and Products Legacy Hardware Platforms Requirements for Advanced Upgrade and Migration Migration Workflow Migrate Command Reference

Before and After Database Migration

Before Database Migration

After Database Migration

Item	Description		Item	Description
1	Source computer		1	Target R77 computer connected to network
2	Management database migration path
3	R77 target computer, not connected to the network
		Important - If the source environment uses only IPv4 or only IPv6, you cannot migrate to an environment that uses only the other type of addresses.

Supported Upgrade Paths, Platforms and Products

Make sure that the upgrade version and products are supported on the target operating system and hardware platform. For a list of supported upgrade paths, platforms and products, see the R77 Release Notes.

Solaris: You can migrate a Solaris database to Gaia.

Legacy Hardware Platforms

A legacy platform is a hardware platform unsupported for new installations but still supported for database migration.

Solaris is a legacy platform. You can migrate the Solaris database to Windows and SecurePlatform and Gaia. But only from Check Point versions in the supported upgrade path. See the R77 Release Notes.

• For Security Management Server

  The database migration procedure for Solaris is the same as for SecurePlatform and Gaia, as described in this chapter.

• For SmartDomain Manager

  To export the SmartDomain Manager database from a legacy platform, use the R77 SecurePlatform DVD. Only two menu options are available:

  • preupgrade verification
  • mds export

Requirements for Advanced Upgrade and Migration

Required Disk Space:

• The hard disk on the target machine must be at least 5 times the size of the exported database.
• The size of the /var/log folder on the target must be at least 25% of the size of the /var/ log directory on the source machine.

Required Network Access:

• The source and target servers must be connected to a network.
• The connected network interface must have an IP address.

IPv4 or IPv6:

If the source environment uses only IPv4 or only IPv6, the target must use the same IP address configuration. You cannot migrate to an environment that uses only the other type of addresses.

Target Version and Products:

You can only upgrade or migrate the version of the server or set of products. The target must have the same or higher version and the same set of installed products.

Migration Workflow

In this section: General Workflow Preparing the Source Server for New IP Address Understanding IPv4 and IPv6 Address Issues During Migration Getting the Migration Tools Package Using the Pre-Upgrade Verification Tool Exporting the Management Database Importing the Management Database Migrating the Database of a Secondary Security Management Server Completing Migration to a New IP Address Migrating to a Server with a Different Platform SmartReporter and SmartEvent Database Migration for Non-Windows SmartReporter and SmartEvent Report Results Migration for Windows SmartReporter Database Migration for Windows SmartEvent Events Database Migration for Windows

This section includes a procedural overview for database migration and continues with detailed procedures for each platform. Also included are special procedures for migrating:

• A secondary Security Management Server
• To a server with a different IP address
• SmartReporter
• SmartEvent

Migration Workflow

1. Prepare the source Security Management Server for export.
2. Install the R77 Security Management Server or a standalone deployment on the target server.
3. Export the management database from source Security Management Server.
4. Import the management database to the target Security Management Server.
5. Test the target deployment.
6. Connect the target Security Management Server to the network.

General Workflow

On the source server:

1. Get the migration tools package.
2. Extract the downloaded package.

   Important - Put all extracted files in the same directory, and run the tools from this directory.

3. Make sure the files have executable permissions. For example, In the temporary directory, run
   chmod 777 *
4. Run fw logswitch to close the SmartView Tracker log files and the SmartLog data. Only closed logs are migrated.
5. Close all Check Point GUI clients that are connected to the Security Management Server.

   Alternatively, if this is a computer that is not in production, run cpstop on the source computer.

   Important - If you do not close the GUI clients or run cpstop, the exported management database can become corrupted.

6. Make sure the source server and the target server have network access.
   • The source and target servers must be connected to a network.
   • The connected network interface must have an IP address.
   • On SecurePlatform, the ifconfig command output must show that the interface is UP.
   • On Windows, the interface must be enabled in the Network Connections window.
7. Run the pre_upgrade_verifier command.
8. Correct all errors before continuing.
9. If the target server must have a different IP address than the source server, make the necessary changes on the source server.
10. Export the management database.
    • If SmartReporter is installed on the source server, export the Log Consolidation database.
    • If SmartEvent is installed on the source server, export the Events database.

On the target server:

1. Install the R77 Security Management Server or a standalone deployment. Configure as required.
2. Get the most updated migration tools package for the target platform (recommended) or use the installed migration tools in $FWDIR/bin/upgrade_tools on Unix platforms or %FWDIR%\bin\upgrade_tools on Windows.
3. Import the management database from the source server to the target.
   • If SmartReporter is installed on the source server, import the Log Consolidation database.
   • If SmartEvent is installed on the source server, import the SmartEvent Events database.
4. If the target server has a different IP address than the source server, make the necessary changes to the license and target computer.

   If the target server is a different platform that the source server, edit the database.

5. Test the target installation.
6. Disconnect the source server from the network.
7. Connect the target server to the network.

Preparing the Source Server for New IP Address

Licenses are related to the Security Management Server IP address. If you migrate the Security Management Server database to a server with a new IP address, there will be licensing issues. We recommend that you keep the same IP address for the target Security Management Server. If this is not possible, you must prepare the source database before the export and edit the target database after the import.

There are additional steps for a Security Management Server that manages VSX Gateways in these configurations:

• From a Security Management Server to a new Domain Server or Security Management Server
• From a Domain Server to a new Domain Server

On the source computer before migration:

1. Create a new host object in SmartDashboard with the IP address of the target Security Management Server.
2. Define a Firewall rule that lets this new Security Management Server connect to Security Gateways.

   Source	Destination	Service
   new server	any	FW1 (TCP 256) CPD (TCP 18191) FW1_CPRID (TCP 18208)

3. Install the new security policy on all gateways.
4. For configurations that include VSX Gateways, to these steps:
   1. Define the previous Firewall rule again for the VSX policy.
   2. Install the policy on the VSX Gateways.

Understanding IPv4 and IPv6 Address Issues During Migration

If you migrate from a Security Management Server or Domain Server to a target with a different IP address configuration, you must configure the source before you export the database:

• Configure IP address assignments
• Enable IPv6 from the Portal or mdsconfig

After you import the database, add or remove IPv4 and IPv6 addresses as required.

Security Management Server

When migrating from a Security Management Server with only IPv4 addresses to:

Target	You need to:
Security Management Server with only IPv4 addresses	Follow the normal migration process.
Security Management Server with only IPv6 addresses	Enable IPv6 on the Source Operating System before exporting the database After importing the database, change the IP address of the management
Security Management Server with a mixture of IPv4 and IPv6 addresses.	Enable IPv6 on the Source Operating System before exporting the database After importing the database, add the IPv6 addresses
Domain Server with IPv4 addresses	Follow the normal migration process.
Domain Server with a mixture of IPv4 and IPv6 addresses	Enable IPv6 on the Source Operating System before exporting the database After importing the database, add the IPv6 addresses

When migrating from a Security Management Server with only IPv6 addresses to:

Target	You need to:
Security Management Server with only IPv4 addresses	After importing the database, change the IPv6 address of the management to IPv4
Security Management Server with only IPv6 addresses	Follow the normal migration procedure
Security Management Server with a mixture of IPv4 and IPv6 addresses.	After importing the database, add the IPv4 addresses
Domain Server with IPv4 addresses	After importing the database, remove IPv6 addresses from the management object in SmartDashboard and add IPv4
Domain Server with a mixture of IPv4 and IPv6 addresses	After importing the database: Enable IPv6 on the Operating System Change the IP address of the management to IPv4

When migrating from a Security Management Server with a mixture of IPv4 and IPv6 addresses to:

Target	You need to:
Security Management Server with only IPv4 addresses	After importing the database: Disable IPv6 on the Operating System Change the IP address of the management to IPv4
Security Management Server with only IPv6 addresses	After importing the database, remove the IPv4 address from the management
Security Management Server with a mixture of IPv4 and IPv6 addresses.	Follow the normal migration procedure
Domain Server with IPv4 addresses	After importing the database, remove the IPv6 address from the management object in SmartDashboard
Domain Server with a mixture of IPv4 and IPv6 addresses	Follow the normal migration procedure

Domain Server

When migrating from a Domain Server with only IPv4 addresses to:

Target	You need to:
Security Management Server with only IPv4 addresses	Follow the normal migration procedure
Security Management Server with only IPv6 addresses	After importing the database: Enable IPv6 on the Operating System Change the IP address of the management to IPv6
Security Management Server with a mixture of IPv4 and IPv6 addresses.	Enable IPv6 on the Operating System Add IPv6 addresses
Domain Server with IPv4 addresses	Follow the normal migration procedure
Domain Server with a mixture of IPv4 and IPv6 addresses	After importing the database: Enable IPv6 on the Operating System Add IPv6 Addresses

When migrating from a Domain Server with a mixture of IPv4 and IPv6 addresses to:

Target	You need to:
Security Management Server with only IPv4 addresses	Disable IPv6 on the source Operating System before exporting the database After importing the database, change the IP address of the management to IPv4
Security Management Server with only IPv6 addresses	After importing the database, remove the IPv4 address from the management.
Security Management Server with a mixture of IPv4 and IPv6 addresses.	Follow the normal migration procedure
Domain Server with IPv4 addresses	Disable IPv6 on the source Operating System before exporting the database Remove the IPv6 address from the target Domain Server object in SmartDashboard
Domain Server with a mixture of IPv4 and IPv6 addresses	Follow the normal migration procedure

Getting the Migration Tools Package

It is important that you use the correct migration tools package. Download the latest version of the migration tools from the Support Center. This is the best way to make sure that you get the most recent version.

Alternatively, you can get the migration tools package from the target computer.

To get the migration tools package from the target computer:

1. Install R77 on the target computer.
2. Copy the complete directory from the target computer to the source computer:
   • SecurePlatform / Gaia - $FWDIR/bin/upgrade_tools
   • Windows - %FWDIR%\bin\upgrade_tools

   Use FTP, SCP or similar. The source directory can be anywhere, such as /var/tmp.

The migration tool files are contained in a compressed package. The files in the package are:

• migrate
• migrate_conf
• migrate export
• migrate import

Using the Pre-Upgrade Verification Tool

We recommend that you run the pre-upgrade verifier on the source server before exporting the management database. The pre-upgrade verifier analyzes compatibility of the management database and its current configuration. A detailed report shows the steps to do before and after the upgrade.

The pre-upgrade verifier can only verify a database that is intended for import into a different major version (for example, R77.xx to R77). It cannot be used on a database that is intended for import into the same major version.

Action Items

• Errors - Issues that must be resolved before you can continue with the upgrade. If you proceed without correcting these errors, the upgrade may fail, or you may have problems after upgrade.
• Warnings - Issues that are recommended to resolve before or after the upgrade.

Exporting the Management Database

On Gaia and SecurePlatform - CLI

To create a management database export file on the source computer:

1. Log in to the expert mode.
2. Get the R77 migration tools.
3. Run:
   <path to migration tools directory>/migrate export <exported database name>.tgz.
4. Do the instructions shown on the screen. This creates the <exported database name>.tgz file.

On Gaia and SecurePlatform - GUI on DVD

To create a management database export file on the source computer:

1. Insert the R77 DVD into source computer drive.
2. At the command prompt, run: patch add cd
3. Select SecurePlatform R77 Upgrade Package.
4. Enter y to confirm the checksum calculation.
5. You are prompted to create a backup image for automatic revert. There is no need to create a backup image now because exporting the management database does not change the system.

   Note - Creating a backup image can take up to twenty minutes, during which time Check Point products are stopped.

6. The welcome screen opens. Press n.
7. Press Y to accept the license agreement.
8. From the Security Management Upgrade Option screen, select Export Security Management configuration. Press N to continue.
9. Select a source for the upgrade utilities.

   We recommend that you select Download the most updated files from the Check Point website to get the latest files. You can also select Use the upgrade tools contained on the CD.
   Press N to continue.

10. If the Pre-Upgrade Verification fails, correct the errors and restart this procedure from the step 2. Otherwise, press N to continue.
11. In the Export window, press N to continue. The management database is saved in /var/tmp/cpexport.tgz.
12. Press E to exit the installation program.

On IPSO

To create a management database export file on the source computer:

1. Get the R77 migration tools.
2. Run:
   <path to migration tools directory>/migrate export <exported database name>.tgz.
3. Do the instructions shown on the screen. This creates the <exported database name>.tgz file.

On Windows - CLI

To create a management database export file on the source computer:

1. Get the R77 migration tools.
2. From the Windows command prompt, run:
   <path to migration tools directory>\migrate.exe export <exported database name>.tgz.
3. Do the instructions shown on the screen. This creates the <exported database name>.tgz file.

On Windows - GUI on DVD

To create a management database export file on the source computer:

1. Log in to Windows using Administrator credentials.
2. Insert the R77 DVD in the optical drive.

   If the wizard does not start automatically, run setup.exe from the DVD.

3. Click Next in the Thank you window.
4. Accept the terms of the License Agreement and click Next.
5. Select Export.
6. Use one of these options to get the upgrade utilities.
   • Download the most recent upgrade utilities from the Support center.
   • Use the upgrade utilities that you downloaded to your local disk.
   • Use the upgrade utilities on the DVD.
7. When prompted, do not disable the Perform Pre-Upgrade verification now option.

8. If there are pre-upgrade verification errors, correct them and start this procedure again from step 3. Otherwise, click Next to continue.
9. Enter path and management database export file name. The default is:
   c:\temp\cp_db_configuration.tgz.
10. When the export completes, click OK.

Importing the Management Database

To import the management database file to the target computer:

1. Log in to the expert mode.
2. Copy the management database file that you exported from the source computer to a directory of your choice on the target computer. Use FTP, SCP or similar.
3. Run:
   <path to migration tools directory>/migrate import <path to the file>/<exported database name>.tgz.
4. Do the instructions on the screen to import the management database.

To Gaia and SecurePlatform

To import the management database file to the target computer:

1. Log in to the expert mode.
2. Copy the management database file that you exported from the source computer to a directory of your choice on the target computer. Use FTP, SCP or similar.
3. Run:
   <path to migration tools directory>/migrate import <path to the file>/<exported database name>.tgz.
4. Do the instructions on the screen to import the management database.

To IPSO

To import the management database file to the target computer:

1. Copy the management database file that you exported from the source computer to a directory of your choice on the target computer. Use FTP, SCP or similar.
2. Run:
   <path to migration tools directory>/migrate import <path to the file>/<exported database name>.tgz.
3. Do the instructions on the screen to import the management database.

To Windows

To import the management database file to the target computer:

1. Copy the management database file that you exported from the source computer to a directory of your choice on the target computer. Use FTP, SCP or similar.
2. From the Windows command prompt, run:
   <path to migration tools directory>\migrate.exe import <path to the file>\<exported database name>.tgz.
3. Do the instructions on the screen to import the management database.

Migrating the Database of a Secondary Security Management Server

1. Export the database file from the primary Security Management Server.

   If the Primary Security Management Server is not available, convert the Secondary Security Management Server to a Primary Security Management Server. To get assistance with this step, contact Check Point Support or your vendor.

2. Install a new Primary Security Management Server.
3. Import the management database file to the new Primary Security Management Server.
4. Install new Secondary R77 Security Management Server.
5. Establish SIC with the Secondary Security Management Server.
6. Synchronize the new Secondary Security Management Server with the new Primary Security Management Server.

Completing Migration to a New IP Address

Licenses are related to the Security Management Server IP addresses. You must update the license and configure the environment to recognize the new Security Management Server.

1. Update the Security Management Server licenses with the new IP address. If you use central licenses, they must also be updated with the new IP Address.
2. Run cpstop
3. Run cpstart
4. Connect to the new IP address with SmartDashboard.
5. Remove the host object and the rule that you created before migration.
6. Update the primary Security Management Server object to make the IP Address and topology match the new configuration.
7. Reset SIC for all SmartEvent distributed servers.
8. Run evstop and evstart on SmartEvent and SmartReporter distributed servers.
9. On the DNS, map the target Security Management Server host name to the new IP address.

Migrating to a Server with a Different Platform

If you migrate the management database to a server with a platform or operating system that is different from the source server, you must update the primary management object's properties accordingly.

Warning - Failure to do so may cause security issues.

After migration:

1. Connect with the SmartDashboard to the target Security Management Server.
2. Edit the primary object:
   • Update the target computer platform.
   • Update the target computer operating system.
3. Save the database.

Example:

If you migrate from a Windows Security Management Server to an appliance:

1. Change OS from Windows to SecurePlatform.
2. Change Hardware from Open server to UTM-1.

SmartReporter and SmartEvent Database Migration for Non-Windows

To migrate the SmartReporter and SmartEvent database from a non-Windows platform to a non-Windows platform, use this procedure. You can also use this procedure to backup and restore the databases.

Tools

• Use the evs_backup utility to back up the SmartEvent and SmartReporter database and configuration files, and place them in a compressed file. Use the version suitable for the target platform. Download it from the Support Center, or from the $RTDIR/bin directory on the target Unix platform.
• Use the evs_backup_extractor utility to restore the backup file.
• Use the migration tools to backup and restore the Security Management database and files. Use the version suitable for the target platform. Download it from the Support Center, or from $FWDIR/bin/upgrade_tools/ directory on the target Unix platform.

Backup Procedure

Run the following commands in Expert mode. Use different file name for each of the utilities:

# cd $FWDIR/bin/upgrade_tools/ # ./migrate export <file name 1> # cd $RTDIR/bin # ./evs_backup [-filename <file name 2>] -ExportPreUpgrade

Restore Procedure

Copy the backup files to the target platform and run these commands in Expert mode:

# cd $FWDIR/bin/upgrade_tools/ # ./migrate import <file name 1> # cd $RTDIR/bin # ./evs_backup_extractor [-filename <file name 2>] -ImportPostUpgrade

SmartReporter and SmartEvent Report Results Migration for Windows

If you have SmartReporter or SmartEvent reports on the source server, you can back them up and copy them to the target server.

Use this procedure to back up reports from a Windows platform or to a Windows platform.

To backup and restore SmartReporter and SmartEvent reports:

On the source server:

1. Open the file: %FWDIR%/conf/reporting_configuration.C
   On a non-Windows platform:
   $FWDIR/conf/reporting_configuration.C
2. Search for the entry:
   generation_result_location

   For example:
   :generation_result_location ("/var/opt/CPrt-R77/Results")

3. Create an archive of the files in the directory specified by this entry. In this example:
   /var/opt/CPrt-R77/Results .
   We will refer to this directory as <results dir>.

   cd <results dir>
tar zcvf /var/tmp/results.tgz <results dir>

4. Copy /var/tmp/results.tgz to the target server.

On the target server:

1. If the target server has a newer version than the source server, create a new directory with the same name as <results dir>:
   mkdir –p <results dir>
2. Untar all the files from results.tgz:

   cd <results dir>
tar xzvf results.tgz

SmartReporter Database Migration for Windows

To migrate SmartReporter database from a Windows platform or to a Windows platform use this procedure.

The database migration procedure automatically migrates the SmartReporter management database to the target server. However, it does not migrate the SmartReporter consolidation database. If you have SmartReporter installed on the source server, you must do several additional steps to migrate the database to the target.

Starting R75.40VS and R75.45, SmartReporter can have MySQL or PostgreSQL as the underlying database for consolidated records data. MySQL is still used for upgrades, and PostgreSQL is used in new installations.

To export and import the SmartReporter database, use the procedure that is appropriate for the underlying database: MySQL or PostgreSQL.

To determine the database that SmartReporter is using, run:

%CPDIR%/bin/cpprod_util CPPROD_GetValue "Reporting Module" DefaultDatabase 1

Exporting the SmartReporter MySQL Database

To create the SmartReporter MySQL database export file on the source server:

1. Run cpstop.
2. Find and open the MySQL configuration file using a text editor:
   • On SecurePlatform: $RTDIR/Database/conf/my.cnf.
   • On Windows: %RTDIR%\Database\conf\my.ini

   Use this file to locate directory names for use in the next steps.

3. Delete the contents of the directory specified in the
   innodb_log_group_home_dir= <xxx> setting.
4. Create the database export file. Assign the name datadir.tgz to this file.
   1. Go to the directory specified by the datadir= <xxx> parameter in the MySQL configuration file.

      This directory contains the database files.

   2. Use GNU tar/gzip utilities to create an archive file containing all files in the directory specified by the datadir=<xxx> setting. For example on SecurePlatform use:

      tar zcvf datadir.tgz <datadir setting>

5. Backup these items to a different device (USB drive, DVD, FTP server, network location, etc.):
   • The datadir export file (datadir.tgz).
   • The MySQL configuration file (my.cnf or my.ini). After copying the file to a backup device, rename the file by appending a .old suffix to the file name. For example, rename file my.cnf to my.cnf.old. (Import scripts require this suffix.)
   • Company logo image files located in the $RTDIR/bin (%RTDIR%\bin on Windows) directory.
   • Custom distribution scripts located in $RTDIR/DistributionScripts (%RTDIR%\DistributionScripts on Windows).

Importing the SmartReporter MySQL Database

On the target server:

1. If you have not already done so, install R77 and SmartReporter, on the target server.
2. Run cpstop.
3. Copy:
   • For SecurePlatform: my.cnf.old to $RTDIR/Database/conf/
   • For Windows: my.ini.old to %RTDIR%\Database\conf.

   Note - If you are migrating to a platform where the name of configuration file is different (for example, migrating from Windows to SecurePlatform) rename the configuration file accordingly.

4. Copy these files from the backup device to the target server:
   • The SmartReporter exported database file (datadir.tgz) to the one of these locations:
     • SecurePlatform: $RTDIR/bin
     • Windows: %RTDIR%\bin
   • Company logo image files to the $RTDIR/bin (%RTDIR%\bin on Windows) directory.
   • Custom distribution scripts to the $RTDIR/DistributionScripts (%RTDIR%\DistributionScripts on Windows) directory.

Completing the SmartReporter MySQL Database Upgrade

To complete the SmartReporter upgrade:

1. When upgrading from a version before R75.40VS:
   1. Run cpstop
   2. Run:

      cpprod_util CPPROD_SetValue "Reporting Module" DefaultDatabase 1 "MySQL" 1

2. Run:
   ./EVR_DB_Upgrade -mysql "<absolute path to file>/<SmartReporter database export file>.tgz"

   For example, if datadir.tgz is located in $RTDIR/bin, run:
   EVR_DB_Upgrade -mysql "$RTDIR/bin/datadir.tgz"

3. If you are not using the default directory paths, change these fields in the MySQL configuration file to match the locations of these directories:

   datadir=

   innodb_log_group_home_dir=

   innodb_data_file_path=

4. Run cpstart
5. In SmartDashboard, from the Policy menu, select Install Database.
6. In SmartReporter, from the Consolidation tab, remove the existing consolidation session and create a new one.

Exporting the SmartReporter Postgresql Database

To create the SmartReporter Postgresql database export file on the source server:

1. Run cpstop
2. On Gaia/SecurePlatform/Linux, run
   cd $RTDIR/bin

   On Windows, run
   cd %RTDIR%\bin

3. On Gaia/SecurePlatform/Linux, run
   eva_db_backup.csh -filename <backupfilename> -database EvrDb

   On Windows run:
   eva_db_backup.bat -filename <backupfilename> -database EvrDb

   Where <backupfilename> is the full path and name of the database records backup file. Create the file in /var/log or another partition or disk with enough space. See the R77 Release Notes for the database disk space requirements.

Importing the SmartReporter Postgresql Database

On the target server:

1. If you have not already done so, install R77 and SmartReporter on the target server.
2. Run cpstop
3. Copy the file backupfilename from the backup device to this directory on the target server:
   • On Gaia/SecurePlatform/Linux:
     /var/$RTDIR
   • On Windows:
     %RTDIR%\bin
     However, if you have another unused partition or disk, save it there.
4. On Gaia/SecurePlatform/Linux, run
   $RTDIR/bin/eva_db_restore.csh -filename <backupfilename> -database EvrDb

   On Windows run:
   %RTDIR%/bin/eva_db_restore.bat -filename <backupfilename> -database EvrDb

   Where <backupfilename> is the full path and name of the database records backup file.

5. Run cpstart
6. In SmartReporter, from the Consolidation tab, remove the existing consolidation session and create a new one.

SmartEvent Events Database Migration for Windows

To migrate SmartEvent Events database from a Windows platform or to a Windows platform use this procedure.

While the database migration procedure automatically migrates the SmartEvent management database to the target computer, it does not migrate the SmartEvent events database. If you have SmartEvent installed on the source server, you must do more to migrate the events database to the target.

Note - The Events Database can be very large, and the manual migration take time. These steps explain how to use the eva_db_backup and eva_db_restore scripts with the default options. By default, the commands are run without options. You must have write permissions for the current directory.

To see more options:

• On SecurePlatform, run: $RTDIR/bin/eva_db_backup.csh --help
• On Windows, run: %RTDIR%\bin\eva_db_backup.bat --help

When upgrading from R70.20 and higher:

1. On the source machine, go to the directory.
   • On SecurePlatform, run cd /var/*
   • On Windows, run: cd \
2. Run the backup tool:
   • On SecurePlatform, run: $RTDIR/bin/eva_db_backup.csh
   • On Windows, run: %RTDIR%\bin\eva_db_backup.exe
3. Copy the backup file created by the tool to the destination machine. By default, the name of a backup file is: <current date>-events_db.backup.
4. Build the Event database on the destination machine by running: cpstart.
   • Wait until all processes show as up and running in cpwd_admin list (status is E)
   • Run: cpstop
5. Run the restore tool:
   • On SecurePlatform, run: $RTDIR/bin/eva_db_restore.csh -filename <path to the backup file>
   • On Windows, run: %RTDIR%\bin\eva_db_restore.exe -filename <path to the backup file>
6. Open the eventia_upgrade.C file in $RTDIR/conf or %RTDIR%\conf.

   If it has DONE in online_status or background_status attribute of the Database section, delete DONE and save the file.

7. Run: cpstart

When upgrading from a version older than R70.20:

On Source server:

Copy the database file ($RTDIR/events_db/events.sql or %RTDIR%/events_db/events.sql file by default) from source machine to the destination machine.

On Destination server:

1. Run: cpstop
2. Run the PostgreSQL daemon:
   • SecurePlatform: $CPDIR/database/postgresql/util/PostgreSQLCmd start
   • Windows: "%CPDIR%\database\postgresql\util\PostgreSQLCmd.bat" start
3. Drop the previous PostgreSQL database content.
   1. Log in to the postgres database:
      • SecurePlatform: $CPDIR/database/postgresql/bin/psql -U cp_postgres -p 18272 postgres
      • Windows: "%CPDIR%\database\postgresql\bin\psql.exe" -U cp_postgres -p 18272 postgres
   2. Run: drop database events_db;

      If you get an error that the database does not exist, ignore it.

   3. Run "\q" to exit the database.
4. Run the database upgrade tool twice:
   • DbUpgradeSqliteToPostgres online <full path to events.sql file>
   • DbUpgradeSqliteToPostgres background <full path to events.sql file>

     The second action may take a long time, depending on the Source machine database size.

5. Stop the PostgreSQL daemon:
   • SecurePlatform: $CPDIR/database/postgresql/util/PostgreSQLCmd stop
   • Windows: "%CPDIR%\database\postgresql\util\PostgreSQLCmd.exe" stop
6. Open the eventia_upgrade.C file in $RTDIR/conf or %RTDIR%\conf

   If it shows DONE in the online_status or background_status attribute of the Database section, delete DONE and save the file.

7. Run: cpstart
8. Delete the events.sql file from destination machine.

Migrate Command Reference

The migrate command exports a source Security Management Server database to a file, or imports the database file to a target Security Management Server. Use absolute paths in the command, or relative paths from the current directory.

Before you run this command for export, close all SmartConsole clients or run cpstop on the Security Management Server.

Before you run this command for import, run cpstop on the Security Management Server.

Syntax:

migrate {export | import} [-l] [-n] <filename> [--exclude-uepm-postgres-db] [--include-uepm-msi-files]

Parameters	Description
export import	One of these actions must be used. Make sure services are stopped.
-l	Optional. Export or import SmartView Tracker logs and SmartLog data. Only closed logs are exported. Use the fw logswitch command to close the logs before you do the export.
-n	Optional. Run silently (non-interactive) using the default options for each setting. Important: If you export a management database in this mode, to a directory with a file with the same name, it is overwritten without prompting. If you import using this option, the command runs cpstop automatically.
--exclude-uepm-postgres-db	Skip over backup/restore of PostgreSQL database of the Endpoint product.
--include-uepm-msi-files	Export/import the uepm msi files.
filename	Required. Enter the name of the archive file with the server database. The path to the archive must exist.