[docs] vDB PostgreSQL Cluster Multi-AZ — VI + EN

English/SUMMARY.md

@@ -852,6 +852,7 @@
       * [Extensions for PostgreSQL Standalone](vdb/relational-database-service-rds/postgresql/postgresql-standalone/vdb-postgresql-standalone-extensions.md)
     * [PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/README.md)
       * [Create and Manage PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/create-and-manage-postgresql-cluster.md)
+      * [Create a Multi-AZ PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/create-multi-az-postgresql-cluster.md)
       * [Parameters for PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/postgresql-cluster-parameters.md)
       * [Extensions for PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/vdb-postgresql-cluster-extensions.md)
       * [Migrate from PostgreSQL Single to PostgreSQL Cluster](vdb/relational-database-service-rds/postgresql/postgresql-cluster/migrate-from-postgresql-single-to-cluster.md)

English/vdb/README.md

@@ -58,4 +58,4 @@ vDB includes many types of services for each type of database, currently we are
 
 #### Cluster Mode:
 
-<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>
+<table><thead><tr><th>Engine</th><th>Kafka</th><th>OpenSearch</th><th>PostgreSQL (New)</th><th>Redis</th></tr></thead><tbody><tr><td>Version</td><td>3.6.0, 3.6.1, 3.7.0</td><td>2.15, 2.17</td><td>15, 16, 17</td><td>7.0, 7.2</td></tr><tr><td>Supported AZ</td><td>HCM 1a</td><td>HCM 1a, 1b, 1c</td><td>HCM 1a, 1b, 1c; HAN 1a, 1b</td><td>HCM 1a, 1b, 1c</td></tr><tr><td>Multi-AZ Replication</td><td>no</td><td>no</td><td>yes</td><td>coming soon</td></tr><tr><td>Auto Failover</td><td>yes</td><td>yes</td><td>yes</td><td>yes</td></tr><tr><td>Scale Up Flavor</td><td>yes</td><td>yes</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Scale Up Storage</td><td>yes</td><td>yes</td><td>yes</td><td>n/a</td></tr><tr><td>Scale out (read-replica)</td><td>no</td><td>no</td><td>up to 9</td><td>up to 9</td></tr><tr><td>Scale out (writer)</td><td>up to 10</td><td>up to 9</td><td>n/a</td><td>n/a</td></tr><tr><td>Configuration Group</td><td>yes</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Monitoring</td><td>metric + log</td><td>no</td><td>coming soon</td><td>coming soon</td></tr><tr><td>Backup Method</td><td>n/a</td><td>n/a</td><td>Full</td><td>Full</td></tr><tr><td>Auto Backup</td><td>n/a</td><td>n/a</td><td>Hourly, Daily, Weekly, Monthly</td><td>Hourly, Daily, Weekly, Monthly</td></tr><tr><td>Integrate vBackup</td><td>no</td><td>no</td><td>yes</td><td>yes</td></tr><tr><td>Backup Location</td><td>n/a</td><td>n/a</td><td>HCM or HAN</td><td>HCM or HAN</td></tr><tr><td>Authentication</td><td>SASL/mTLS</td><td>Username/Password</td><td>Username/Password</td><td>Password</td></tr><tr><td>Encryption at-rest</td><td>yes</td><td>no</td><td>no</td><td>no</td></tr></tbody></table>

English/vdb/relational-database-service-rds/postgresql/postgresql-cluster/README.md

@@ -23,6 +23,7 @@ To create and manage a PostgreSQL Cluster, please refer to the guide [here](crea
 | **Scale Read**        | No                                       | Yes (Read traffic distributed to Readers)                        |
 | **Backup**            | Automatic daily backup (legacy)          | Integrated with Backup Center (Auto Backup + Manual Backup)      |
 | **Number of nodes**   | 1                                        | 2 - 10                                                           |
+| **Availability & Durability** | Single-AZ                              | Single-AZ or Multi-AZ                                            |
 | **Use Case**          | Development, Testing, small applications | Production, Mission-critical, applications requiring high uptime |
 
 ### When should you use PostgreSQL Cluster?
@@ -60,13 +61,23 @@ To create and manage a PostgreSQL Cluster, please refer to the guide [here](crea
 
 ***
 
+## Availability & Durability modes
+
+A PostgreSQL Cluster has two deployment modes, selected in the **Availability & Durability** field of the Basic configuration step:
+
+* **Single-AZ**: every Node sits in one Availability Zone. Suitable when you need High Availability at the Node level with the simplest configuration.
+* **Multi-AZ**: Nodes are spread across two or more Availability Zones. The cluster keeps serving traffic when one Availability Zone fails.
+
+Multi-AZ is currently available in the HCM region only and requires a VPC with DNS enabled. For the full guide, see [Create a Multi-AZ PostgreSQL Cluster](create-multi-az-postgresql-cluster.md).
+
+***
 ## Backup Center Integration
 
 PostgreSQL Cluster is integrated with **Backup Center (vBackup)**, providing a comprehensive backup & restore solution:
 
 * **Auto Backup**: Mandatory configuration when creating a cluster. Backup runs automatically according to the schedule of the selected Backup Policy.
 * **Manual Backup**: Allows creating a **Full Snapshot** manually at any time from the cluster detail page.
-* **Restore**: Create a new cluster from an available restore point in Backup Center. The Storage Size of the new cluster must be greater than or equal to the Backup Size.
+* **Restore**: Create a new cluster from an available restore point in Backup Center. The new cluster needs more storage than the backup itself; the system shows the required minimum on the **Storage size** field once you select a backup.
 
 {% hint style="warning" %}
 **Note about Backup when deleting a Cluster:**
@@ -84,6 +95,7 @@ PostgreSQL Cluster is integrated with **Backup Center (vBackup)**, providing a c
 | Limitation             | Description                                              |
 | ---------------------- | -------------------------------------------------------- |
 | **Number of nodes**    | Minimum 2, maximum 10 nodes per cluster                  |
+| **Availability Zones**  | A Multi-AZ Cluster requires at least 2 zones, one Subnet per zone |
 | **Writer node**        | Always exactly 1 Writer per cluster                      |
 | **Database Proxy**     | Not supported in current version (Coming Soon - Phase 2) |
 | **Concurrent backups** | Only 1 backup/restore job allowed at a time per cluster  |
@@ -116,8 +128,12 @@ When the Writer node encounters an issue, the system will **automatically failov
 
 ### 3. Can I create a cluster from an existing backup?
 
-**Yes.** When creating a new cluster, you can select a restore point from Backup Center to restore data. Note that the Storage Size of the new cluster must be greater than or equal to the Backup Size of the backup.
+**Yes.** When creating a new cluster, you can select a restore point from Backup Center to restore data. The new cluster needs more storage than the backup itself; the system shows the required minimum on the **Storage size** field once you select a backup.
 
 ### 4. What is Database Proxy and when will it be available?
 
 Database Proxy provides connection pooling and load balancing for the cluster. This feature is under development and will be released in **Phase 2**. Please follow the [Announcements and Updates](../../../announcements/release-notes.md) page for the latest information.
+
+### 5. How does Multi-AZ differ from Single-AZ?
+
+**Single-AZ** places every Node in one Availability Zone; **Multi-AZ** spreads Nodes across two or more Availability Zones, so the cluster keeps running when one Availability Zone fails. Multi-AZ is currently available in the HCM region only, requires a VPC with DNS enabled, and needs at least 2 zones. See [Create a Multi-AZ PostgreSQL Cluster](create-multi-az-postgresql-cluster.md).

English/vdb/relational-database-service-rds/postgresql/postgresql-cluster/create-and-manage-postgresql-cluster.md

@@ -24,6 +24,7 @@ On the Database management interface, click **Create Database**. The creation pr
 * **Cluster Name**: Enter a name for the cluster (6-20 characters, must start with a letter).
 * **Database Engine**: Select **PostgreSQL**.
 * **Deployment Type**: Select **Cluster** (this option only appears when the Engine is PostgreSQL).
+* **Availability & Durability**: Select **Single-AZ** or **Multi-AZ**. For Multi-AZ, see the dedicated guide at [Create a Multi-AZ PostgreSQL Cluster](create-multi-az-postgresql-cluster.md).
 
 {% hint style="info" %}
 When selecting **Cluster** as the Deployment Type, the label changes from "Database Instance Name" to "Cluster Name".
@@ -74,6 +75,7 @@ When selecting **Cluster** as the Deployment Type, the system also displays a **
 
 * **Cloud Network (VPC & Subnet)**: Select the VPC and Subnet for the cluster. If you don't have one yet, you can create a new one following the guide [here](../../../../vserver/compute-hcm03-1a/vpc/virtual-private-cloud-vpc.md).
 * **Public Accessibility**: Enable if you want the cluster to have a Public IP and be accessible from the Internet; disable if you only want access via Private IP.
+* **Multi-AZ**: if you selected **Multi-AZ** in Step 1, this step requires a VPC with DNS enabled and shows a **Subnets** table for zone selection instead of a single Subnet — see [Create a Multi-AZ PostgreSQL Cluster](create-multi-az-postgresql-cluster.md).
 
 {% hint style="warning" %}
 **Note:** The Public Accessibility setting can only be selected **once** at the time of creation and cannot be changed afterwards.