Importing RND 3.0 and RND 3.5 Configuration Data to the RND 4.0 Database

You can import RND 3.0 MongoDB or RND 3.5 PostgreSQL data to the RND 4.0 PostgreSQL database.

Complete the following steps to import data from RND 3.0 MongoDB or RND 3.5 PostgreSQL to the RND 4.0 database.

  1. Log in to the Admin portal.
  2. On the menu, go to Admin > Backup & Restore.
    The Backup & Restore window is displayed.

    Backup & Restore Window

  3. To import RND 3.0 configuration file, complete the folowing steps:
    1. In the R3.0 Config Restore pane, click Upload to import RND 3.0 configuration file.
      The R3.0 DB Config Import dialog box is displayed.

      R3.0 DB Config Import Dialog Box

    2. In the R3.0 DB Config Import dialog box, click Choose File to navigate and choose the rnd30-data.tar.gz file to import RND 3.0 configuration file.
      The R3.0 DB Config Import dialog box is displayed.
    3. Click Upload. A message is displayed to confirm whether you want to override the database configuration.
    4. Click OK to confirm. A confirmation message is displayed indicating that the RND 3.0 database configuration is successfully imported to the PostgreSQL database.
  4. To import RND 3.5 configuration file, complete the folowing steps:
    1. In the Config Restore pane, click Upload to import RND 3.5 configuration file.
      The DB Config Import dialog box is displayed.

      DB Config Import Dialog Box

    2. In the DB Config Import dialog box, click Choose File to navigate and choose the rnd-config-backup-(date).gz file to import RND 3.5 configuration file.
      The DB Config Import dialog box is displayed.
    3. Click Upload. A message is displayed to confirm whether you want to override the database configuration.
    4. Click OK to confirm. A confirmation message is displayed indicating that the RND 3.5 database configuration is successfully imported to the PostgreSQL database.

    If the backup configuration contains a large amount of data, data migration will be slow because it involves validation of each record before importing the data. In such a scenario, it is recommended to set low network latency between the nodes. For example, in a two-node cluster environment, if the RND 3.0 and RND 3.5 backup configuration contains more than 24,000 records and the registration rules count is above 2,000, it is recommended to set low network latency between the nodes. That is, when the two-node RND cluster is set with a network latency of 3 ms, it takes 39 minutes to import RND 3.0 and RND 3.5 backup configuration data to RND 4.0, whereas it takes only 8 minutes to import the same amount of configuration data to RND 4.0. without any latency time (0 ms) set between the nodes.

Parent topic: Migrating RND 3.0 Configurations Data to the RND 4.0 Database