Before you begin:

  • The Hybrid Data Pipeline deployment should be backed up according to Backing up Hybrid Data Pipeline deployments.
  • You should have the installation program for the version of the product used in the previous deployment of the service.
  • You should have load balancer SSL certificate files used for server installation and load balancer configuration. (Depending on your environment, a single SSL certificate file may be used.)
  • You should have the credentials for the system database.

About this task:

Take the following steps to restore the service after a disaster or other system-wide failure.

  1. Restore the system database on a new machine, according to your database vendor documentation.
  2. Copy the contents of the backup key location to a new key location accessible to the nodes in the new environment.
  3. Delete the <key_location>/db directory and the <key_locaton>/global.properties file from the key location.
  4. Spin up a server to host a new load balancer for the new environment.
    Note: Load balancer configuration takes place in Step 7 after the nodes for the new environment have been installed.
  5. Perform a Custom installation on a new machine with the version of the product used in the standing deployment of the server.
    Note: The purpose of this installation is to restore the previous deployment of the service. Therefore, with the exception of hostname and system database information, the values specified should be the same as those specified during the previous installation or upgrade of the service.
    1. From a command-line prompt, navigate to the directory where you saved the product file. Alternatively, place the product file directory on your path before proceeding to the next step.

      The product file has the format PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin, where nn is the version of the product.

    2. Make the file an executable using the chmod command. Then, press ENTER. For example:

      chmod +x ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

    3. Run the executable.
      • Console mode

        ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console

      • GUI mode

        ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

        Note: If the installer cannot continue with a GUI installation, a message is displayed and the installation continues in console mode
    4. Accept or enter the fully qualified hostname for the Hybrid Data Pipeline server. By default, the installer suggests the name of the current machine.
    5. When prompted, choose a Custom installation.
    6. Specify the key location created in Step 2. This is the key location for the new environment.
    7. When prompted, provide the load balancer SSL certificate file. This should be the file, or a backup of the file, used in the previous deployment of the service.
    8. When prompted, enter the host and credential information of the restored system database.
      Important: The information provided should be the information for the system database restored in Step 1.
    9. Review and confirm port numbers.
    10. Review the installation summary, and proceed with the installation.
  6. Perform a Custom installation on each additional node in the new environment.
    Note: When performing subsequent installations on additional nodes, you must specify the key location created in Step 2 (and specified in Step 5, Substep f). The installer uses the files written to the key location during the initial installation to install the server on additional nodes. Hence, for installations on additional nodes, the installer bypasses prompts for load balancing, SSL, external database, and On-Premises Connector configurations.
    1. Run the executable.
      • Console mode

        ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin -i console

      • GUI mode

        ./PROGRESS_DATADIRECT_HDP_SERVER_nn_LINUX_64_INSTALL.bin

        Note: If the installer cannot continue with a GUI installation, a message is displayed and the installation continues in console mode
    2. Accept or enter the fully qualified hostname for the Hybrid Data Pipeline server. By default, the installer suggests the name of the current machine.
    3. When prompted, choose a Custom installation.
    4. Specify the key location for the new environment established in Step 2.
    5. Review port numbers.
    6. Review the installation summary, and proceed with the installation.
  7. Configure the load balancer set up in Step 4 for the new environment.
    Note: The load balancer must be configured to manage incoming traffic among the nodes in the new environment. If the On-Premises Connector is being used to connect with a data store behind a firewall, the load balancer must also be configured to communicate with the On-Premises Connector. In addition, you will need to specify the SSL certificate file to enable SSL termination in the load balancer.
  8. Reinstall client-side components (such as the On-Premises Connector or the ODBC and JDBC drivers). If the load balancer configuration changed during reinstallation of the server, client-side components will need to be reinstalled. The component(s) must be reinstalled with the configuration and certificate files written to the redist folder during installation of the server on nodes in the new environment.

    The four configuration and certificate files are:

    • config.properties
    • OnPremise.properties
    • ddcloud.pem
    • ddcloudTrustStore.jks
  9. Test the restored service to ensure it is performing as expected.

What to do next:

As a matter of best practices, monitor functionality and performance in the newly restored environment.