You can create a Global Database Network (GDN) by using an existing cluster or purchasing a new one. A GDN enables cross-region disaster recovery and active geo-redundancy.
Limits
Cluster versions
Database engine:
Edition: Enterprise Edition
: Single zone (with hot standby storage cluster disabled)
Supported regions
GDN is available in more than 10 regions worldwide, including the Chinese mainland, China (Hong Kong), and other regions outside the Chinese mainland.
Primary cluster region | Secondary cluster region |
All regions in the Chinese mainland | The same region as the primary cluster, or any other region in the Chinese mainland. For example, if the primary cluster is in China (Hangzhou), the secondary cluster can be in China (Hangzhou) or any other region in the Chinese mainland. Note If you have other region requirements, submit a ticket to contact us. |
Regions outside the Chinese mainland | China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and UK (London). |
For regions outside the Chinese mainland, you must sign the Cross-Border Data Transfer Compliance Agreement before you create a secondary cluster.
Feature limits
Clusters in a GDN do not support the database and table restoration feature.
Other limits
A GDN can consist of one primary cluster and up to four secondary clusters.
The primary cluster and secondary clusters must have the same database engine version: .
The node specifications of a secondary cluster must be greater than or equal to those of the primary cluster. We recommend that you keep the specifications consistent.
A cluster can belong to only one GDN.
Billing
Cross-region data transfer traffic for a GDN is free of charge. You are charged only for the PolarDB .
Create a global database network
-
Log on to the PolarDB console. In the left-side navigation pane, click Global Database Network (GDN).
-
On the Global Database Network (GDN) page, click Create GDN.
-
In the Create GDN dialog box, configure the following parameters.
Parameter
Description
Compatibility
Select or .
Edition
Set to Single-active Version.
Name
Enter a descriptive name to help you identify the GDN. The name does not need to be unique.
Primary Region
Select the region of the primary cluster.
NoteBefore you proceed, determine which cluster to use as the primary cluster and select its region here.
Primary Cluster
Select an existing cluster to serve as the primary cluster of the GDN.
Global domain name
This feature is not currently supported. Keep it disabled.
-
Click OK. You can view the created GDN in the Global Database Network (GDN) list. You can then to the GDN.
Delete a global database network
-
You can delete a GDN only if it contains no secondary clusters.
-
A GDN cannot be restored after it is deleted. Proceed with caution.
-
After you delete a GDN, applications that are connected to it can no longer access the database. You must promptly update the connection strings in your applications.
-
Log on to the PolarDB console. In the left-side navigation pane, click Global Database Network (GDN).
-
On the Global Database Network (GDN) page, find the target GDN, and click Delete in the Operation column.
NoteA grayed-out Delete button indicates that the GDN contains secondary clusters, which you must delete first.
-
Read the warnings in the dialog box that appears. After you confirm that the information is correct, click OK to delete the GDN.
Related documents
-
: Provides an overview of GDN, its architecture, and application scenarios.
-
: Describes how to add a secondary cluster to a Global Database Network (GDN).
-
: Describes how to connect to a Global Database Network (GDN).
Related APIs
|
API |
Description |
|
Creates a Global Database Network. |
|
|
Deletes a Global Database Network. |
|
|
Queries the information about a specified Global Database Network. |
|
|
Queries information about all Global Database Networks. |
|
|
Modifies the information about a Global Database Network. |