High Availability Mount Issues
Issues with High Availability Mounts are typically caused by connectivity or access permission problems.
Failed Status
A backend enters Failed status when its connections to the remote server have failed.
Verify that the remote system is online and available. Check that the Remote Server's authentication credentials and connection settings are correct, and that those credentials have the access permissions needed for the remote folder paths, including the path for the canary file. Active health checks need read and write access to the canary file; passive checks need read access to an existing file.
If the backend was previously Healthy, verify that the authentication credentials, their permissions, or the connection settings have not changed recently.
Desynced Status
A backend enters Desynced status when its health checks are out-of-date or unreadable.
Check that the path to the canary file has the permissions required by the selected health check mode for the authentication credentials used for the corresponding Remote Server. For active checks, the remote folder must allow reading and writing. For passive checks, use an existing file the connection can read.
For example, if the Mount is configured to use a Remote Folder path of path/to/folder on the Remote Server, the canary file path must also point to a location within path/to/folder.
Shared Storage Configuration
All backends must point to the same shared storage location with identical access permissions. Misconfigured backends are a common cause of Failed and Desynced statuses.
Canary File Placement
Health checks fail when the canary file is placed in a location that is regularly purged or used as the source or destination of a Sync, Automation, or file processing script.
Primary Remote Server Requirement
When setting up High Availability, one of the backends must be the same Remote Server originally used when setting up the Mount.
If the original primary Remote Server is missing from the list of backends, editing a backend produces the following error:
Remote server mount requires at least one backend for primary remote server