High Availability Mount Issues

Issues with High Availability Mounts are typically caused by connectivity or access permission problems.

Shared Storage Requirements

All backends must point to the same shared storage location with identical access permissions. For example, if the Mount points to a folder named path/to/folder on the remote server with Read+Write access, each backend must also point to path/to/folder with Read+Write access.

Different backends can use different connection methods, as long as they all point to the same folder. This setup ensures that, during a failover, the secondary node can access the same files and folders as the primary node.

Troubleshooting a 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. The canary file path must be readable and writable by those credentials.

If the backend was previously Healthy, verify that the authentication credentials, their permissions, or the connection settings have not changed recently.

Backends automatically return to Healthy status after successful health checks.

Troubleshooting a 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 is readable and writable by the authentication credentials used for the corresponding Remote Server. The remote folder containing the canary file must allow both reading and writing.

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.

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

Preserving the Canary File

Place the canary file in a location where it will not be deleted, moved, renamed, or modified by other processes.

For example, do not place the canary file in a location that is regularly purged, or that is used as the source or destination of a Sync, Automation, or file processing script.