Merge pull request #277375 from varun-dhawan/varund-jul

[PostgreSQL] updates scenario for using virtual endpoint for PITR or snapshot restores

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-read-replicas-virtual-endpoints.md

@@ -4,7 +4,7 @@ description: This article describes the virtual endpoints for read replica featu
 author: AlicjaKucharczyk
 ms.author: alkuchar
 ms.reviewer: maghan
-ms.date: 04/27/2024
+ms.date: 6/5/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.topic: conceptual
@@ -52,11 +52,33 @@ The sections below delve into how these endpoints react to both [Promote to prim
   * **If Read-Only Endpoint Points to Replica**: The Read-Only endpoint is redirected from the promoted replica to point to the primary server.
   * **If Read-Only Endpoint Points to Primary**: The Read-Only endpoint remains unchanged, continuing to point to the same server.
 
+### Using Virtual Endpoints for Consistent Hostname During Point-in-Time Recovery (PITR) or Snapshot Restore
 
-Learn how to [create virtual endpoints](how-to-read-replicas-portal.md#create-virtual-endpoints).
+This section explains how to use Virtual Endpoints in Azure Database for PostgreSQL - Flexible Server to maintain a consistent hostname during Point-in-Time Recovery (PITR) or Snapshot Restore, ensuring application connection strings remain unchanged.
+
+### Steps:
+1. Add Virtual Endpoint to Primary Server:
+    - Browse to your primary server instance in the Azure Portal.
+    - Navigate to “Replication” Tab, and under "Virtual Endpoints," click "Add Virtual Endpoint."
+    - Configure the virtual endpoint with a consistent hostname (e.g., `mydb-virtual-endpoint.postgres.database.azure.com`).
+    - Save the configuration.
+    - Update your application to use this virtual endpoint in the connection string.
+
+2. Perform Point-in-Time-Restore (PITR) or Snapshot Restore:
+    - Initiate Recovery:
+        - Go to the "Backups" section of your primary server.
+        - Choose the appropriate restore option (PITR or snapshot) and specify the desired point in time.
+    - Update Virtual Endpoint:
+        - Once the new instance is created, navigate back to the primary server settings.
+        - Remove the virtual endpoint from the original primary server.
+        - Add the same virtual endpoint to the newly created server.
+
+3. Validation:
+    - Ensure that your application connects using the virtual endpoint and verify the database operations post-recovery.
 
 ## Related content
 
+- [create virtual endpoints](how-to-read-replicas-portal.md#create-virtual-endpoints).
 - [Read replicas - overview](concepts-read-replicas.md)
 - [Geo-replication](concepts-read-replicas-geo.md)
 - [Promote read replicas](concepts-read-replicas-promote.md)