Appendix D. StandAlone
- 박준남 (Unlicensed)
- 정은진
- 헌규임
Without considering merges of other nodes defined as cluster member nodes, based on the configuration file of the defined node, run the engine to operate service at one node.
Table of Contents
Standalone Mode
Necessity
The purpose of MCCS is to provide clients a continuous service with server redundancy.
However, there is a possibility that heartbeat connection has problem due to physical failure or Operating system.
MCCS Agent works in pairs. If it cannot work in pair due to a reason, nothing can be done and so it has to be executed alone.
In this case, only one server can be used to continue MCCS service, so it is needed to change to Standalone Mode.
How to use the standalone option
The following example shows how to run the MCCS server by using the standalone option.
- Terminate the MCCS agent service for the server that will be configured in standalone mode.
(Start → Management Tools → Service → 'MCCS Agent')
[Figure] Standalone Mode Switching At the top of the %MCCS_HOME%\bin\mccsserver.ini file, add the '-standalone' option.
[Figure] Standalone Mode Switching- Start an MCCS agent service.
How to operate in stand alone mode
If the mirror resource is included, for the user data safety, automatic operation at a single node will be limited.
Thus, depending on whether the mirror resource is included, there can be two different operation methods.
<When Mirror disk resource is not included>
| No. | Circumstances | AutoStart group according to AutoStart setting value | Start Group Manually |
|---|---|---|---|
| 1 | When boot one node while both nodes are offline | Able | Able |
| 2 | When boot in one node configuration | Able | Able |
| 3 | When two servers are booted and running - When MCCS is started in only one node while MCCS is terminated in both nodes (Apply only when Standalone option is given) | Disabled | Able after remove auto disable function |
| 4 | When two servers are booted and running - When MCCS is terminated in one node while MCCS is executing in both nodes | N/A | Able after remove auto disable function |
| 5 | When two servers are booted and running - When one node is terminated with MCCS is executing in both nodes | N/A | Able |
<When Mirror disk resource is included>
| No. | Circumstances | AutoStart group according to AutoStart setting value | Start Group Manually |
|---|---|---|---|
| 1 | When boot one node while both nodes are offline | Disabled | Able after remove auto disable function |
| 2 | When two servers are booted and running - When MCCS is started in only one node while MCCS is terminated in both nodes (Apply only when Standalone option is given) | Disabled | Disabled |
| 3 | When two servers are booted and running - When MCCS is terminated in one node while MCCS is executing in both nodes | N/A | Able after remove auto disable function |
| 4 | When two servers are booted and running - When one node is terminated with MCCS is executing in both nodes | N/A | Able |
Steps to remove Standalone Mode
When the server with problem is back to normal, server operator should remove Standalone mode and continue server redundancy process as shown below.
Operating services will not be affected by MCCS agent being stopped and restarted.
Steps to remove Standalone mode are shown below.
- Stop the MCCS service on the server that had problem.
- Stop the MCCS service on server that had problem.
- Delete '-standalone' in MccsServer.ini file and save on active server.
- Start MCCS agent service on active server.
- Start the MCCS agent service on the server that had problem.
- Connect to MCCS console and check the state of MCCS service.