AWS fsx: Clarify failover transparency and client-side multipathing
Summary
Reworded failover transparency description to note that for iSCSI and NVMe/TCP block storage protocols, transparency depends on client-side multipathing that must be configured, and added links to iSCSI and NVMe/TCP provisioning guides.
Security assessment
The change is about high-availability failover behavior and client multipathing configuration; it improves availability guidance but does not address a vulnerability, authentication, or encryption concern.
Evidence
+When failing over from one file server to another, the new active file server automatically begins serving all file system read and write requests to that HA pair. For Multi-AZ file systems, when the preferred file server is fully recovered and becomes available, Amazon FSx automatically fails back to it, with failback usually completing in less than 60 seconds. For Single-AZ and Multi-AZ file systems, a failover typically completes in less than 60 seconds from the detection of the failure on the active file server to the promotion of the standby file server to active status. For NFS and SMB clients, failovers are transparent because the endpoint IP address that clients use to access your data remains the same, so Linux, Windows, and macOS applications resume file system operations without manual intervention. For the iSCSI and NVMe/TCP block storage protocols, failover transparency instead depends on client-side multipathing, which you must configure on the client so that it automatically fails over between your file servers.
Diff
diff --git a/fsx/latest/ONTAPGuide/high-availability-AZ.md b/fsx/latest/ONTAPGuide/high-availability-AZ.md index e1da687c5..28ae94e1b 100644 --- a//fsx/latest/ONTAPGuide/high-availability-AZ.md +++ b//fsx/latest/ONTAPGuide/high-availability-AZ.md @@ -89 +89 @@ For second-generation file systems with multiple HA pairs, each HA pair's failov -When failing over from one file server to another, the new active file server automatically begins serving all file system read and write requests to that HA pair. For Multi-AZ file systems, when the preferred file server is fully recovered and becomes available, Amazon FSx automatically fails back to it, with failback usually completing in less than 60 seconds. For Single-AZ and Multi-AZ file systems, a failover typically completes in less than 60 seconds from the detection of the failure on the active file server to the promotion of the standby file server to active status. Because the endpoint IP address that clients use to access data over NFS or SMB remains the same, failovers are transparent to Linux, Windows, and macOS applications, which resume file system operations without manual intervention. +When failing over from one file server to another, the new active file server automatically begins serving all file system read and write requests to that HA pair. For Multi-AZ file systems, when the preferred file server is fully recovered and becomes available, Amazon FSx automatically fails back to it, with failback usually completing in less than 60 seconds. For Single-AZ and Multi-AZ file systems, a failover typically completes in less than 60 seconds from the detection of the failure on the active file server to the promotion of the standby file server to active status. For NFS and SMB clients, failovers are transparent because the endpoint IP address that clients use to access your data remains the same, so Linux, Windows, and macOS applications resume file system operations without manual intervention. For the iSCSI and NVMe/TCP block storage protocols, failover transparency instead depends on client-side multipathing, which you must configure on the client so that it automatically fails over between your file servers. @@ -91 +91 @@ When failing over from one file server to another, the new active file server au -To ensure that failovers are transparent to clients connected to your FSx for ONTAP Single-AZ and Multi-AZ file systems, see [Accessing data from within the AWS Cloud](./supported-fsx-clients.html#access-environments). +To ensure that failovers are transparent to clients connected to your FSx for ONTAP file systems, see [Accessing data from within the AWS Cloud](./supported-fsx-clients.html#access-environments). To configure client-side multipathing for iSCSI and NVMe/TCP clients, see [Provisioning iSCSI for Linux](./mount-iscsi-luns-linux.html) and [Provisioning NVMe/TCP for Linux](./provision-nvme-linux.html).