This Help File Page was issued on 09/30/2017
❑Failover Testing Procedure:
•While logged into MKMSCS on workstations being managed in a Cluster:
✓Verify the MKS Cluster application is running on each Server within the Cluster.
✓Verify that the Secondary Server Backup screen indicates "Waiting for next page".
•On the Primary Server (Server #1)
✓Stop the SPA application as follows:
i.Click on Stop button
ii.Wait a few seconds or until the Stop button turns to a Start button.
iii.Click on the Exit button.
✓Stop the Sybase® Adaptive Server Anywhere database engine as follows:
▪If the Sybase® Adaptive Server Anywhere database engine is not running as a Windows® Service:
oLocate for the SQL® Anywhere Network Server Icon in the hidden icons tray
System tray displays SQL & SPA Icons
(Unless SQL is a Windows Service)
oRight-Click on the Icon in the hidden icons tray to display its menu.
oChoose the Shut down option.
Anywhere Network Server - Shut down option
▪If the Sybase® Adaptive Server Anywhere database engine is running as a Windows® Service:
oRight-Click the Start Icon on the Windows 10® task bar.
oSelect the Search option on the menu presented
oEnter Control Panel
oSelect Administrative Tools.
oLocate and Right-Click on the Adaptive Server Anywhere database engine
•Once Adaptive Server Anywhere was stopped manually, or halted as a Windows® Service:
✓Visually verify that neither the SQL or SPA Icons are now in the hidden icons tray on the Primary Server.
✓All active Cluster modules will now show a message indicating that a disconnect from the Primary Server has occurred
✓Wait the user defined Timeout (in seconds) before attempting to locate and connect to another Adaptive Server Anywhere database engine.
•The Secondary Server (Server #2) will:
✓Wait 10 seconds.
✓Scan all Servers within the Cluster attempting to locate an active Server.
•Since no Server has an active Adaptive Server Anywhere database engine
✓The Secondary Server will assume that role and start Adaptive Server Anywhere and then start SPA on that Secondary Server.
✓The remaining Cluster modules, except the Primary Server, should automatically reconnect to the newly activated Secondary Server and continue with their normal backup and monitoring functions.
❑This Failover Test Procedure may be repeated through the additional Servers.
➢Important: Any failure where the Adaptive Server Anywhere database engine service and SPA changes from one Server to another is considered a Technical Support issue.
a.Recovery to the normal operating state (all Clusters operating in their original role) is not automatic.
b.IT Technicians at your Central Station must diagnose the cause of failure and then resolve the reason for that failure.
c.Once this failure has been resolved, Micro Key Solutions™ Technical Support should be contacted to resolve any Micro Key Solutions™ related issues, if they exist.