Hybrid Data Pipeline requires a system database (sometimes referred to as an account database) for storing user and configuration information. To promote the continuous availability of the service, the system database should be replicated or mirrored, and the system database should be routinely backed up. In the event that the system database fails, the backup database can be integrated with the standing deployment of Hybrid Data Pipeline.

Integrating the backup system database with a standing deployment requires performing an upgrade of the server on each node in the deployment. This is a two part process. First, a Modify settings upgrade must be performed on one of the nodes in the cluster. Second, an Express upgrade must be performed on each additional node in the cluster. These upgrades must be performed with the same version of the product used in the standing deployment of the service. Before you proceed with this two-part process, you must have the following information and resources.

  • A mirror of the external system database.
  • The installation program. The installation program must be for the same version of the product used in the standing deployment of the server.
  • Administrator and user credentials for the external system database. The credentials of the mirror database should be the same as those of the original database.