Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

클러스터 맴버 노드로 정의된 다른 노드의 합류를 고려하지 않고, 정의된 노드의 구성파일을 기반으로 하나의 노드에서 서비스를 운영 할 수 있도록 엔진을 동작 시키는 것을 말합니다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

Column
width350px
Panel

이 페이지의 주요 내용

Table of Contents
maxLevel4

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

...

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> included> 

NO.CircumstancesAutoStart group according to Auto Start setting valueStart Group Manually
1

When boot one node while both nodes are offline

AbleAble
2

When boot in one node configuration

AbleAble
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)

DisabledAble 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/AAble 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/AAble


<When Mirror disk resources is included>

No.CircumstancesAutoStart group according to AutoStart setting valueStart Group Manually
1두 노드가 종료된 상태에서 한 노드만 부팅할 때When boot one node while both nodes are offlineDisabledAble after remove auto disable function
2

두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 종료된 상태에서 한 노드에서만 MCCS 가 시작 될 때
(스텐드얼론 옵션을 주었을 때만 적용됨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)

DisabledDisabled
3두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 실행중인 상태에서 한 노드에서만 MCCS 가 종료되었을 때When two servers are booted and running - When MCCS is terminated in one node while MCCS is executing in both nodesN/AAble after remove auto disable function
4두 서버가 부팅되어 운영 중일 때 - 양 노드에서 MCCS 가 실행중인 상태에서 한 노드가 종료할 때When two servers are booted and running - When one node is terminated with MCCS is executing in both nodesN/AAble

 

스탠드얼론 모드의 해제 절차

문제가 있었던 서버가 정상 상태로 돌아오면 서버 관리자는 스탠드얼론 모드를 해제하고, 다음과 같이 서버 이중화 작업을 다시 진행해야 합니다.
MCCS 에이전트 서비스를 중지하거나 재시작해도 운영 중인 서비스에는 어떠한 영향도 없습니다.
스탠드얼론 모드의 해제 절차는 다음과 같습니다.

...

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.
 

 

  1. Stop the MCCS service on the server that had problem.
  2. Stop the MCCS service on server that had problem.
  3. Delete '-standalone' in MccsServer.ini file and save on active server.
  4. Start MCCS agent service on active server.
  5. Start the MCCS agent service on the server that had problem.
  6. Connect to MCCS console and check the state of MCCS service.