You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/postgresql/migrate/troubleshooting-networking-and-connectivity-issues.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,9 +44,16 @@ If both Single and Flexible server are in public access, you are unlikely to hit
44
44
Let us look at these scenarios in detail.
45
45
46
46
## 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).
48
48
49
49
## 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
50
57
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.
51
58
52
59
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
59
66
60
67
Once the settings are applied, the connection from flexible server to single server will be established and you'll no longer hit this issue.
61
68
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.
62
71
## Private access in source and private access in target
63
72
64
73
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