{"id":38234,"date":"2019-10-31T22:22:28","date_gmt":"2019-10-31T19:22:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/migratsiya-s-check-point-s-r77-30-na-r80-10\/"},"modified":"2019-10-31T22:22:28","modified_gmt":"2019-10-31T19:22:28","slug":"migratsiya-s-check-point-s-r77-30-na-r80-10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/migratsiya-s-check-point-s-r77-30-na-r80-10","title":{"rendered":"Migration from Check Point from R77.30 to R80.10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Migration
\n
\nHello colleagues, welcome to the lesson on migrating Check Point databases from R77.30 to R80.10.<\/p>\n

When using Check Point products, the need to migrate existing rules and object databases arises sooner or later for the following reasons: <\/p>\n

    \n
  1. When purchasing a new device, it is necessary to migrate the database from the old device to the new device (to the current version of GAIA OS or higher).<\/li>\n
  2. It is necessary to upgrade the device from one version of GAIA OS to a higher version on the local machine.<\/li>\n<\/ol>\n

    \nTo address the first task, only the tool called Management Server Migration Tool, or simply Migration Tool, is suitable. For task #2, the CPUSE solution or Migration Tool can be used.
    \nNext, let's take a closer look at both methods.
    \n<\/a><\/noindex><\/p>\n

    Upgrading to a new device<\/h3>\n

    \nDatabase Migration<\/b> involves installing the latest version of the Management on the new machine, and then migrating the database from the existing security management server to the new one using the Migration Tool. This method minimizes the risk of upgrading for the existing configuration.<\/p>\n

    To migrate the database using the Migration Tool, you must meet the requirements<\/b>:<\/p>\n

      \n
    1. There must be more free disk space than five times the size of the exported database archive.<\/li>\n
    2. The network settings on the target server must match those of the source server. <\/li>\n
    3. Creating a backup. The database export should be performed to a remote server.
      \nThe GAIA operating system already includes the Migration Tool, which can be used when importing a database or for migration to a version of the operating system identical to the initial one. In order to migrate the database to a higher version of the operating system, you need to download the Migration Tool of the corresponding version from the \u2018Tools\u2019 section on the Check Point R80.10 support website: <\/li>\n
    4. Backup and migration of SmartEvent \/ SmartReporter Server. The \u2018backup\u2019 and \u2018migrate export\u2019 utilities do not include SmartEvent database \/ SmartReporter database data.
      \nFor backup and migration, you need to use the \u2018eva_db_backup\u2019 or \u2018evs_backup\u2019 utilities.
      \nNote: Article sk110173 in the CheckPoint knowledge base.<\/li>\n<\/ol>\n

      \nLet's take a look at the functions this tool contains:<\/p>\n

      \"Migration
      \n
      \nBefore proceeding with data migration, first unpack the downloaded Migration Tool into the folder \"\/opt\/CPsuite-R77\/fw1\/bin\/upgrade_tools\/\". The database export should be done using commands from the directory where you unpacked the tool.<\/p>\n

      Before running the export or import command, close all SmartConsole clients or run cpstop on the Security Management Server. <\/p>\n

      To create an export file<\/b> of the management database on the source server:<\/p>\n

        \n
      1. Enter expert mode.<\/li>\n
      2. Run the pre-check tool: pre_upgrade_verifier -p $FWDIR -c R77 -t R80.10. If there are errors, fix them before proceeding.<\/li>\n
      3. Run: .\/migrate export filename.tgz. This command exports the contents of the Security Management Server database to a TGZ file.<\/li>\n
      4. Follow the instructions. The database is exported to the file you named in the command. Make sure you defined it as TGZ.<\/li>\n
      5. If SmartEvent is installed on the source server, export the event database.<\/li>\n<\/ol>\n

        \nNext, we will import the security server databases that were exported. Before you start: install the R80 Security Management Server. Note that the network settings of the new R80.10 Management Server must match those of the old server. <\/p>\n

        To import the configuration<\/b> of the management server:<\/p>\n

          \n
        1. Enter expert mode.<\/li>\n
        2. Transfer (via FTP, SCP, or similar) the exported configuration file to the remote server compiled from the source to the new server.<\/li>\n
        3. Disconnect the source server from the network. <\/li>\n
        4. Transfer the configuration file from the remote server to the new server.<\/li>\n
        5. Calculate the MD5 for the transferred file and compare it with the MD5 calculated on the source server: # md5sum filename.tgz<\/li>\n
        6. Import the database: .\/migrate import filename.tgz <\/li>\n
        7. Update check. <\/li>\n<\/ol>\n

          \nAt the end of step 7, we summarize that the database migration was successful using the Migration Tool. In case of failure, you can always turn on the source server, so that operations are not affected.<\/p>\n

          It is worth noting that migration from a standalone server is not supported.<\/p>\n

          Local update<\/h3>\n

          \nCPUSE (Check Point Upgrade Service Engine)<\/b> automatically updates Check Point products for the Gaia OS. Software update packages are divided into categories, namely major releases, minor releases, and Hotfixes. Gaia automatically finds and displays available software update packages and images relevant to the version of Gaia OS to which you can upgrade. Using CPUSE, you can perform a clean installation of the new version of GAIA OS, as well as upgrade the system with database migration.<\/p>\n

          To upgrade to a higher version or perform a clean installation using CPUSE, the machine must have sufficient free (unallocated) space \u2014 at least the size of the root partition.<\/p>\n

          The transition to a new version is performed on a new partition of the hard disk, while the \"old\" partition is converted into a Gaia Snapshot (the new partition space is taken from unallocated space on the hard disk). It is also advisable to take a snapshot before upgrading the system and upload it to a remote server.<\/p>\n

          Upgrade Process<\/b>:<\/p>\n

            \n
          1. Check the update package (if you have not done so already) \u2014 verify that this package can be installed without conflicts: right-click on the package \u2014 click \"Verifier.\"\n

            The result should be approximately as follows:<\/p>\n