Backing up a Hybrid Data Pipeline deployment is a precondition for full recovery of a Hybrid Data Pipeline service. As described in Backing up Hybrid Data Pipeline deployments, the following features of a Hybrid Data Pipeline load balancer deployment should be backed up.

  • System database
  • Key location
  • Load balancer and load balancer configurations (including certificates used to provide SSL termination)

In a complete system failure scenario, the Hybrid Data Pipeline service can be recovered with these backups. The recovery begins with restoring the system database and reestablishing a key location. The server must then be reinstalled on host machines, and the load balancer must be setup and configured to manage requests. In addition, if any client-side components (such as the On-Premises Connector or the ODBC and JDBC drivers) were lost during the failure event, these components must be reinstalled.

Note: If you are running a cloud load balancer such as the AWS Application Load Balancer or the Azure Application Gateway, you should consult your vendor documentation about backing up your deployment. For information specific to Hybrid Data Pipeline deployments using cloud load balancers, refer to Load balancer configuration in the Deployment Guide for details.