Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Configuring the Server Manager Main Server to Run with NAT

Configuring the Server Manager Main Server to Run with NAT

Data Replication supports deployment topologies in which the Server Manager Main server is secured with Network Address Translation (NAT). NAT translates IP addresses for internal use in a local area network (LAN) to IP addresses for external use. Often, the LAN is behind a firewall. Data Replication does not support NAT for Server Manager subservers.
The following image shows a topology in which the source database and the Server Manager Main server are deployed in a LAN and the target database and Server Manager subserver are deployed on a remote server:
Server Manager behind the NAT
When the Server Manager Main server sends data to the Server Manager subserver on the remote system, NAT converts the IP address that is used in the LAN to a public IP address.
Data Replication tries to use faster bidirectional connections by default. However, NAT prevents the Server Manager subserver from initiating a connection to the Server Manager Main server. Bidirectional connections work only if the Server Manager subservers can address the Server Manager Main server directly without NAT.
Alternatively, you can enable unidirectional connections that allow the Server Manager Main server in the LAN with NAT to communicate with subservers on remote servers. To do so, perform the following steps for the Server Manager Main server and each subserver in the replication configuration:
  1. On the
    Server Manager
    tab >
    Configs
    view, connect to the Main server as the idradmin user.
  2. On the
    Server Manager
    tab >
    Servers
    view, select a server.
  3. Click the
    Properties
    icon button on the Server Managers toolbar.
  4. On the
    Advanced Settings
    tab, select
    AsyncHttpEnabled
    and click the
    Edit
    icon button.
  5. Enter the value of 1 for
    AsyncHttpEnabled
    and click
    OK
    .
  6. Click
    Save
    .
  7. Restart the Server Manager for the change to take effect.

0 COMMENTS

We’d like to hear from you!