Skip to content

Commit b751bfa

Browse files
Merge pull request #246774 from shriram-muthukrishnan/networkingtsg
Changing public vs private scenarios
2 parents 40f834d + 7fc150e commit b751bfa

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/postgresql/migrate/troubleshooting-networking-and-connectivity-issues.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,9 +44,16 @@ If both Single and Flexible server are in public access, you are unlikely to hit
4444
Let us look at these scenarios in detail.
4545

4646
## Private access in source and public access in target
47-
This network configuration is not supported by Single to Flex migration tooling. In this case, you can opt for other migration tools to perform migration from Single Server to Flexible server.
47+
This network configuration is not supported by Single to Flex migration tooling. In this case, you can opt for other migration tools to perform migration from Single Server to Flexible server such as [pg_dump/pg_restore](../single-server/how-to-upgrade-using-dump-and-restore.md).
4848

4949
## Public access in source and private access in target
50+
There are two possible configurations for your source server in this scenario.
51+
- Public access in source without private end points.
52+
- Public access in source with private end points.
53+
54+
Let us look into the details of setting network connectivity between the target and source in the above scenarios.
55+
56+
### Public access in source without private end points
5057
In this case, single server needs to allowlist connections from the subnet in which flexible server is deployed. You can perform the following steps to set up connectivity between single and flexible server.
5158

5259
1. Go to the VNet rules sections in the Connection Security blade of your single server and click on the option **Adding existing virtual network**.
@@ -59,6 +66,8 @@ In this case, single server needs to allowlist connections from the subnet in wh
5966

6067
Once the settings are applied, the connection from flexible server to single server will be established and you'll no longer hit this issue.
6168

69+
### Public Access in source with private end points
70+
In this case, the connection will be routed through private end point. Refer to the steps mentioned in the following section about establishing connectivity in case of private access in source and private access in target.
6271
## Private access in source and private access in target
6372

6473
1. If a single server is in private access, then it can be accessed only through private end points. Get the VNet and subnet details of the private end point by clicking on the private endpoint name.

0 commit comments

Comments
 (0)