| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.
스텐드얼론 옵션 사용 방법
다음은 MCCS 서버를 스텐드얼론 옵션을 사용하여 실행시키는 방법입니다.
...
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.
MCCS 에이전트 서비스를 시작합니다.
[그림] 스탠드얼론 모드 전환 화면
상화별 스텐드얼론 동작 방법
미러 리소스가 포함되어 있을 경우, 사용자 데이터의 안전을 위해 한 노드에서 자동으로 동작하는 부분에 제한을 갖게 됩니다. 따라서 미러 리소스가 포함되어 있는 유무에 따라서 상황별 동작 방법이 2가지로 나눠지게 됩니다.
<미러 리소스가 포함되어 있지 않는 경우>
| 번호 | 상황 | AutoStart 설정값에 따른 자동 그룹 시작 여부 | 수동 그룹 시작 여부 |
|---|---|---|---|
| 1 | 두 노드가 종료된 상태에서 한 노드만 부팅할 때 | 가능 | 가능 |
| 2 | 한 노드 구성에서 부팅할 때 | 가능 | 가능 |
| 3 | 두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 종료된 상태에서 한 노드에서만 MCCS 가 시작 될 때 | 불가능 | 자동비활성화 해제 후 가능 |
| 4 | 두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 실행중인 상태에서 한 노드에서만 MCCS 가 종료되었을 때 | N/A | 자동비활성화 해제 후 가능 |
| 5 | 두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 실행중인 상태에서 한 노드가 종료할 때 | N/A | 가능 |
<미러 리소스가 포함되어 있는 경우>
...
두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 종료된 상태에서 한 노드에서만 MCCS 가 시작 될 때
(스텐드얼론 옵션을 주었을 때만 적용됨)
...
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.