Determine how many SAP Replication Servers to deploy and where to deploy them in various cloud replication scenarios.
When EC2 security groups
allow your on-premises machine to access the RS port (a custom TCP port)
on the EC2 instance and your firewall allows the EC2 instance to access
the on-premises machine's RS port, you can install two Replication
Servers—one on your premises, near the primary database, and one on the
EC2 instance where the target database is running. Installing
Replication Servers at both ends of the connection, where configuration
permits, can reduce the effect of network latency on replication
performance. The two Replication Servers in this scenario can
communicate using the TDS protocol:
In a restricted network environment
where EC2 security groups do not allow your on-premises machines to
access the EC2 RS port, install Replication Server on your premises near
the primary database. It can communicate with the target database on EC2
through ODBC or TDS:
If your firewall does not allow the
EC2 instance you are replicating to to access the RS port on your
on-premises database machine, you can install Replication Server on the
EC2 instance alongside the target database. A Replication Agent on your
on-premises machine captures data and transfers it to the EC2
Replication Server through the TDS protocol:
When security groups on EC2
instance A (running the primary database) allow EC2 instance B to access
EC2 A's RS port (a custom TCP port), and security groups on EC2 B
(running the target database) allow EC2 A to access EC2 B's RS port, you
can install two Replication Servers—one on EC2 A, with the primary
database, and one on EC2 B, with the target database. Installing
Replication Servers at both ends of the connection, where configuration
permits, can reduce the effect of network latency on replication
performance. The Replication Servers in this scenario can communicate
using the TDS protocol:
In a restricted
network environment where security groups on EC2 instance B, where the
target database runs, do not allow EC2 instance A to access EC2 B's RS
port, install Replication Server on EC2 A, near the primary database. It
can communicate with the target database on EC2 B through ODBC or TDS.
If security groups
on EC2 instance A (running the primary database) do not allow EC2
instance B to access EC2 A's RS port, you can install Replication Server
on EC2 B alongside the target database. A Replication Agent on EC2 A
captures data and transfers it to the target database on EC2 B through
the TDS protocol:
When EC2 security groups
allow your on-premises machine to access the RS port (a custom TCP port)
on the EC2 instance and your firewall allows the EC2 instance to access
the on-premises machine's RS port, you can install two Replication
Servers—one on the EC2 instance where the primary database is running
and one on your premises with the target database. Installing
Replication Servers at both ends of the connection, where configuration
permits, can reduce the effect of network latency on replication
performance. The Replication Servers in this scenario can communicate
using the TDS protocol:
If your firewall does not allow the
EC2 instance running your primary database to access the RS port on your
on-premises database machine, you can install Replication Server on the
EC2 instance with the primary database. It can communicate with the
target database on your premises through ODBC or TDS:
In a restricted network environment
where EC2 security groups do not allow your on-premises machine to
access the EC2 RS port, install Replication Server on your premises,
near the target database. A Replication Agent on the EC2 instance
captures data and transfers it to the on-premises Replication Server
through the TDS protocol: