This topic describes the differences between a cross-zone high-availability (HA) and a standalone file gateway.
A cross-zone HA file gateway and a standalone file gateway have the following differences.
Cross-zone HA file gateway | Standalone file gateway | |
Usage | Virtual IP addresses are required to use a cross-zone HA file gateway. You can change virtual IP addresses. | The IP address is automatically assigned and cannot be changed. |
|
| |
Architecture | Two nodes are deployed in two zones to ensure service availability in case of single points of failures. | Only a single node is available. A standalone file gateway becomes unavailable if the zone fails. |
Read/Write bandwidth limits | A cross-zone HA file gateway is deployed on two nodes. The maximum read bandwidth of a cross-zone HA file gateway is twice that of a standalone file gateway. The maximum write bandwidth of a cross-zone HA file gateway is the same as that of a standalone file gateway. | |
Read/Write latency | A cross-zone HA file gateway utilizes data replication internally, resulting in higher write latency compared with a standalone file gateway. The write latency of a cross-zone HA file gateway is influenced by the network latency between zones. However, the HA architecture does not affect read latency. |