Welcome to the Microsoft Q&A and thank you for posting your questions here.
Thanks for sharing the details I see you are trying to move data between two Azure Database for PostgreSQL Flexible Servers in different resource groups (RG1 and RG2). Let’s go through a few things that could be causing the issue with selecting your source server for migration:
1.Same Region Check: Azure DMS doesn’t support cross-region migration for PostgreSQL Flexible Servers. So, it’s important to double-check that both PSQLServer1 (the source) and PSQLServer2 (the target) are in the same Azure region. If they ae not, you might need to create a new server in the same region as the destination server and migrate it that way.
2.Permissions: Make sure the account you are using for DMS has the right permissions (at least Contributor or Owner) for both resource groups (RG1 and RG2). Without the correct access, the migration service won’t be able to detect the source server.
3.Network Setup: Look over the firewall settings for both PostgreSQL servers and ensure the migration services IP ranges are allowed. If the servers are in different VNets, make sure they are properly VNet peered.
4.Check DMS Setup: Make sure your Azure Database Migration Service is configured properly and is located in the same region as the source and destination servers. If the source server still isn’t appearing, try using Azure CLI to see if you can select it that way, or take a look at the Activity Log for any clues.
5.Manual Migration Option: If DMS keeps giving you trouble, you can always try doing a manual migration using pg_dump to back up the data and pg_restore to load it into the new server.
Do let us know if you have any questions and queries.
Thanks,
Manoj