High Availability Mount Issues

Issues that occur with High Availability Mounts are typically caused by connectivity or access permission issues.

Shared Storage Requirements

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

You can use different connection methods for each backend but they must all point to the same exact folder location. 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 Failed status for a backend can occur when 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.

Check that the authentication credentials on the remote system have the correct access permissions for remote folder paths, including the path for the canary file.

Check that the path to the canary file is readable and writable by the authentication credentials of the remote system.

If the health check had previously showed a Healthy status then verify that the authentication credentials, the permissions of the authentication credentials, or the connection settings have not changed recently.

After successful health checks, backends automatically return to a Healthy status.

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.

For example, if the Mount is configured to use a Remote Folder path of path/to/folder on the Remote Server then make sure that the canary file path is also pointing to a location within path/to/folder.

Make sure the remote system folder containing the canary file allows both reading and writing.

Primary Remote Server Requirement

When setting up High Availability, one of the backends must be the same one you used when setting up the Mount.

If the original primary Remote Server is missing from the list of backends, you will see the following error message when trying to edit a backend:

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

Preserving the Canary File

Place the canary file into a location that avoids the canary file being deleted, moved, renamed, or changed by other methods.

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