As a matter of best practices, you should be prepared to replace or recover a network load balancer that handles requests for your Hybrid Data Pipeline service. The following guidelines should be followed to ensure quick recovery of the service in case your network load balancer fails.

  • Back up all load balancer configuration information, as described in Backing up Hybrid Data Pipeline deployments.
    • The SSL certificate used to provide SSL termination at the load balancer should be backed up. The backup should be secured with the same access controls as the standing certificate.
    • The settings for session affinity should be documented.
    • The host names passed in the Host header should be documented.
    • The configuration for supplying the X-Forwarded-Proto header should be documented.
    • The configuration for supplying the X-Forwarded-For header if the client IP address is needed for Hybrid Data Pipeline access logs should be documented.
    • Routing and port information for configuration of default routing and for configuration of routing to on-premises data stores. Refer to Load balancer configuration in the Deployment Guide for details.
      Note: If you are using HAProxy as your load balancer, you should backup the haproxy.cfg file as a matter of best practice. Once you spin up HAProxy on a new machine, you can quickly configure HAProxy to handle Hybrid Data Pipeline requests by adding the haproxy.cfg file to the /etc/haproxy folder and executing the command /etc/init.d/haproxy reload.
  • Consider having a backup load balancer in place and ready to handle requests for the service should the standing load balancer go down.
  • Be prepared to direct traffic to a backup load balancer. Once you have a backup load balancer in place, you should be prepared to update the DNS record of the load balancer such that the hostname of the load balancer resolves to the IP address of the backup load balancer. Note that the name of the server hosting the load balancer must remain the same between the standing load balancer and the backup with which it is being replaced.
Note: If you are running a cloud load balancer such as the AWS Application Load Balancer or the Azure Application Gateway, best practices recommend that you document and backup your load balancer configuration. Refer to your cloud load balancer vendor documentation for details. For information specific to Hybrid Data Pipeline deployments using cloud load balancers, refer to Load balancer configuration in the Deployment Guide for details.