Support for running the Reflection for Secure IT server in a Microsoft Cluster is not working in the 8.0 shipping version (8.0.125). If a running server on the active node fails, the Microsoft Cluster Service will fail to start the Reflection server automatically on the backup node, and a manual restart will also fail. To resolve this issue, upgrade to version 8.1 or higher.
Upgrading in a Cluster Environment
For information about upgrading in a cluster environment, see the product documentation topic: http://docs.attachmate.com/reflection/rsit-ssh/8.1/winserver/help/index.htm?toc.htm?rsit_winserver_configure_cluster_pr.htm.
Using a Server Cluster
The Microsoft cluster service helps ensure that users have continuous access to your server. By providing failover support, if one server within the cluster becomes unavailable, another server takes over the shared resources (shared disk, IP address, DNS name, and Reflection service) and continues to run using the same configuration. The change of servers is transparent to new session connections; however, active sessions are disconnected and need to establish new sessions. For a detailed overview, see "Using a Server Cluster" in the Reflection for Secure IT Windows Server user guide: http://docs.attachmate.com/reflection/rsit-ssh/8.1/winserver/help/rsit_winserver_cluster_ov.htm.
Configuring Reflection to Run in a Cluster
Detailed instructions are available in the Reflection for Secure IT Windows Server user guide topic, "Configure a Reflection for Secure IT Cluster": http://docs.attachmate.com/reflection/rsit-ssh/8.1/winserver/help/rsit_winserver_configure_cluster_pr.htm.
Legacy KB ID
This document was originally published as Attachmate Technical Note 2453.