A cross-zone high-availability (HA) file gateway deploys across multiple zones to eliminate the single point of failure of a standalone file gateway.
Features
Cross-availability zone high-availability file gateways are available only in the China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), and China (Hong Kong) regions.
Automatic failover and virtual IP address
If an ECS instance fails or a zone becomes unavailable, the cross-zone HA file gateway automatically detects the issue and fails over to a healthy node to ensure service continuity.
During a failover, the gateway automatically updates the VPC routing table. This ensures the virtual IP address used for mounting remains unchanged, allowing applications to connect without interruption.
You can mount an HA file gateway the same way you mount a standalone file gateway, with no changes to your application architecture.
Efficient data replication
A cross-zone HA file gateway uses an efficient data replication strategy that optimizes bandwidth on the replication link while ensuring data reliability.
This strategy reduces unnecessary replication requests and improves the overall bandwidth usage of the file gateway instance.
Architecture
A cross-zone HA file gateway uses a two-node deployment, with each node located in a different zone. Data synchronizes efficiently between the nodes to ensure consistency. Elastic network interfaces (ENIs) are bound to the nodes to connect the gateway to your virtual private cloud (VPC). You can then access the gateway services through a virtual IP address by using the ENIs.
The cross-zone HA file gateway provides a single virtual IP address for mounting. The gateway then creates a corresponding entry in the routing table to direct traffic to the primary node.
During a failover, the gateway service seamlessly switches from the failed node to a healthy node. The gateway then updates the routing table to point the virtual IP address to the healthy node, which becomes the new primary node. This process ensures high availability and protects against a single point of failure. Because the virtual IP address for mounting does not change, you can use the HA file gateway the same way as a standalone file gateway, with no changes to your application.