Appendix D- StandAlone
- 정은진
- 환기장
- 헌규임
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
MCCS intends to provide interruption-free service by dualizing the server.
However, during service operation, as some nodes experience physical failures or OS failures, nodes may be unable to perform heartbeat communication with each other.
MCCS agents works as a pair. If they don't work as a pair, all operation by MCCS such as web console access will be failed. As a result, stand alone execution will be done.
In this situation, only one server is used for MCCS service, and you need to switch to the stand alone mode.
How to use Standalone Mode
The following are the steps to operate MCCS in Standalone mode.
- Stop MCCS agent server (service mccs_agent stop)
Add "-standalone" option at the top of %MCCS_HOME%\bin\MccsServer.ini
- Start MCCS Agent server(service mccs_agent start)
Standalone Action According to situation
If mirror resource is included, it is limited to auto action in one node for user data safety. Therefore, according to the situation, there are 2 actions according to the existence of mirror resource.
<When Mirror disk resources is not included>
| NO. | Circumstances | AutoStart group according to Auto Start 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 resources 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.