High Availability Mount Issues

For an HA problem, identify the backend's status, the failed health check, and whether the expected shared files remain accessible through another connection. A connection can be reachable while exposing the wrong folder, so a successful login alone does not establish that it is a usable alternate backend.

Failed or Degraded Status

Check the affected Remote Server's hostname, route, credentials, and access to the configured remote folder. For active checks, the account must write and read its canary file; passive checks need an existing readable file. Verify the canary operation as well as ordinary folder access.

Compare recent credential, firewall, folder, or permission changes with the last successful check. Stability thresholds determine how many consecutive results are needed for Failed or Healthy. Degraded can occur while results are inconsistent or a threshold has not been met.

Healthy backends take precedence over degraded ones. If the mount selects an unexpected backend, compare health first and priority second; lower priority numbers are preferred within the same health category.

Desynced Status

Desynced indicates inconsistent current canary data between backends. Check that every backend reaches the same intended shared folder and current files, rather than a separate copy or stale storage view. Then check canary paths and their permissions through those connections.

Confirm the shared data before resetting the status. Restored network access does not establish that the storage views agree. Once the cause is corrected, use Reset to restore the backend's eligibility and review its health-check results.

Canary File Placement

Keep canaries within the configured shared location and outside folders purged or processed by Syncs, Automations, or scripts. A canary removed or changed by another process can make a working connection appear failed or inconsistent. Health-check modes require different file operations, so match permissions to the selected mode.

Primary Remote Server Requirement

The backend set must retain the Remote Server originally used by the Mount. Without it, a configuration change can produce:

Remote server mount requires at least one backend for primary remote server

Keep or restore that backend before configuring its alternatives. The backend configuration reference explains the shared-storage and connection requirements.