Limits

Updated at:

This topic describes the limits on the async replication feature of Hybrid Disaster Recovery (HDR).

Limits on regions and zones

The async replication feature is available in the following regions and zones. Additional regions may be added over time. For the latest availability, check the region options when you create a site pair.

  • China (Hangzhou): Zone B, Zone F, Zone G, Zone H, Zone I, Zone J, and Zone K

  • China (Shanghai): Zone B, Zone E, Zone F, Zone G, Zone K, Zone L, Zone M, and Zone N

  • China (Qingdao): Zone B and Zone C

  • China (Beijing): Zone D, Zone F, Zone G, Zone H, Zone I, Zone J, Zone K, and Zone L

  • China (Zhangjiakou): Zone A, Zone B, and Zone C

  • China (Hohhot): Zone A and Zone B

  • China (Ulanqab): Zone A, Zone B, and Zone C

  • China (Shenzhen): Zone C, Zone D, Zone E, and Zone F

  • China (Heyuan): Zone A and Zone B

  • China (Guangzhou): Zone A and Zone B

  • China (Chengdu): Zone A and Zone B

  • China (Hong Kong): Zone B, Zone C, and Zone D

  • Singapore: Zone A, Zone B, and Zone C

  • Japan (Tokyo): Zone A, Zone B, and Zone C

  • South Korea (Seoul): Zone A

  • Philippines (Manila): Zone A

  • Thailand (Bangkok): Zone A and Zone B

  • Malaysia (Kuala Lumpur): Zone A, Zone B, and Zone C

  • Indonesia (Jakarta): Zone A, Zone B, and Zone C

  • Germany (Frankfurt): Zone A, Zone B, and Zone C

  • UK (London): Zone A and Zone B

  • US (Silicon Valley): Zone A and Zone B

  • US (Virginia): Zone A and Zone B

  • UAE (Dubai): Zone A and Zone B

  • SAU (Riyadh - Partner Region): Zone A and Zone B

  • China East 2 Finance Cloud: Zone G, Zone K, and Zone Z

  • South China 1 Finance Cloud: Zone B, Zone D, and Zone E

  • (Invitational preview) China (Beijing) Finance Cloud: Zone L and Zone K

Important

Alibaba Finance Cloud and the Alibaba Cloud public cloud are isolated from each other. Async replication for disaster recovery cannot be performed between them.

Limits on specifications and ECS disks

The following table lists specification limits for async replication and replication pair-consistent groups.

Item

Limit

Replication pairs per disk

1

Replication pairs per replication pair-consistent group

17

Replication cycle

15 minutes

Replication rate

Up to 100 MB/s. Varies based on system load.

Primary disk category

ESSD or ESSD AutoPL disks

Secondary disk category

Must match the primary disk in category, performance level, and capacity

The following table lists disk operation limits for async replication and replication pair-consistent groups.

Note

Notes referenced in the table:

  • After a replication pair is activated, the secondary disk becomes read-only.

  • Due to the RPO, a snapshot of the primary disk may differ from a snapshot taken at the same time on the secondary disk.

  • Both disks in a replication pair must be either encrypted or unencrypted. Cross-replication between encrypted and unencrypted disks is not supported.

Operation

Primary disk

Secondary disk

Read and write

Read and write

Read-only (see note 1)

Disk deletion

Not supported

Not supported

Disk initialization

Not supported

Not supported

Disk resizing

Not supported

Not supported

Disk attaching

Supported

Not supported

Snapshot creation

Supported

Supported (see note 2)

Rollback based on snapshots

Supported

Not supported

Disk category change

Not supported

Not supported

Performance level change

Not supported

Not supported

Disk encryption

Supported

Supported (see note 3)

Multi-attach

Not supported

Not supported

Disk migration with instances

Not supported

Not supported

Limits on ECS networks

The following limits apply to Elastic Compute Service (ECS) networks:

  • A single network interface card (NIC) has the following limitations:

    After a failover, the primary ENI cannot be automatically configured for some operating systems at the disaster recovery site. After these operating systems are started at the disaster recovery site, you must configure the primary ENI. For more information, see Configure a secondary ENI.

  • The following limitations apply to multiple network interface cards:

    • After a secondary ENI is bound to an ECS instance, some images cannot automatically identify the IP address of the secondary ENI or add a route. As a result, the secondary ENI cannot work properly.

    • If an ECS instance is configured with a secondary ENI, check the IP address of the secondary ENI after a failover to ensure that the secondary ENI works as expected. For more information, see Configure a secondary ENI.

  • Sites do not support elastic network interfaces (ENIs) or ECS instances outside a VPC.

Limits on configuration quotas

  • A single user can create a maximum of 1,000 disaster recovery site pairs.

  • Each disaster recovery site pair supports a maximum of 512 protection groups.

  • Each protection group supports a maximum capacity of 32 TB and a maximum of 17 disks.

Limits on consistency guarantee

The async replication feature supports only crash consistency and does not support application consistency. For applications and databases that have high requirements for consistency, we recommend that you configure direct writes of data to disks based on application and database documentation. This ensures data consistency and reduces the risk of extended recovery time due to asynchronous data writes when a disaster occurs.