3. Requirements and Considerations for Configuration

Sample System Diagram



[Figure] Example of System Configuration

Table of Contents


System Requirements

Hardware

CPU

At least 1Ghz or faster 32-bit (x86) or 64-bit (x64) processor.

Memory

Following memory capacity is needed to run MCCS service.
At least 1GB or more memory for system
At least 200MB or more for MCCS service

Disk

At least 500MB is needed.

Network Interface Card

It is recommended 3 NICs(Network Interface Card) as below are needed to configure a mirror disk.

  • NIC for Service
  • NIC for Heartbeat
  • NIC for Mirror

It is recommended 2 NICs(Network Interface Card) as below are needed to configure a shared disk.

  • NIC for service
  • NIC for Heartbeat


Operating system

MCCS supports the following operating system.

  • Windows 2008 Standard, Enterprise Edition SP2 32bit or 64bit
  • Windows 2008 R2 Standard, Enterprise Edition SP1
  • Windows 2012 Standard, Datacenter Edition 
  • Windows 2012 R2 Standard, Datacenter Edition
  • Windows 7 Enterprise SP1 32bit or 64bit
  • Windows 8 Enterprise ,Windows 8.1 Enterprise 32bit or 64bit


Note

MCCS dose not support Windows 2008 SMB and 2012 Essential Edition



Pre-installation Consideration

MCCS supporting browsers

MCCS provided the web management console through a web browser. The following types of browsers are supported.

  • Internet Explorer 8.0 or higher
  • Google Chrome 7 or higher
  • Firefox 4 or higher

Operating System and Software

Two servers should have the same environment as below for server redundancy.

  • Windows OS version, Service Pack & Windows update (both)
  • Same WorkGroup/Domain Environment
  • Same administrator account and password
  • Same OS time

Network Interface Card

At least 2 NICS as listed below are needed for shared disk environment.

  • NIC for service : Used to client connection. This is also used for 2nd heartbeat.
  • NIC for heartbeat : Used to communication path between nodes.

At least 3 NICs as listed below are needed for mirror disk environment.

  • NIC for service : Used to client connection.  This is also used for 3rd heartbeat.
  • NIC for heartbeat : Used to communication path between nodes.
  • NIC for mirror : Used to replicate the data of local disk to target disk. This is also used for 2nd heartbeat.

(Number of virtual IP can be different according to the customer's environment) 
When configure Active-Standby server environment, virtual IP for service is managed in cluster and it should be the same bandwidth as IP of active and standby server.
Giga LAN is recommended for network for data mirroring.
Before installing MCCS, all network connection should be checked first through Ping test. Latest driver installation of NIC manufacturer is recommended for driver of network card.

When you assign an IP address on each NIC for service, heartbeat and mirror, Each IP address should not be on the same subnet among them. But each pair of them between nodes must be on the same subnet.

IP Address

Each node in a cluster should have at least one IP address for every NIC to be used by MCCS. Virtual IP addresses which is switchable between nodes which communicate to clients also should be reserved.
(The number of virtual IP address can be variable according to the clients' needs.)
When you reserve virtual IP addresses, this must be on the same subnet as the real IP address of the NIC of node.
For example, if the real IP address of the NIC is 10.10.10.10/255.255.255.0, virtual IP addresses that MCCS uses on that NIC must be in the form 10.10.10.x/255.255.255.0 where x is any unassigned number from 1 to 254.

Firewall

MCCS basically uses TCP/UDP port from 14321 to 14324 and it is done mostly automatically. 
Three processes which are Mccs Web Console.exe, MccsServer.exe, and MccsAgentService.exe are registered in the window firewall during installation automatically.
The ports that are registered during installation automatically: 137, 138, 139, 445, 9999, plus ports in the 10000 to 10025 range, depending upon which volume letters you plan on replicating.

Web port is not registered in the firewall.

For example, if it is E-drive for mirror disk, 10004 port should be used.

Character

Port

Character

Port

Character

Port

Character

Port

A

10000

H

10007

O

10014

V

10021

B

10001

I

10008

P

10015

W

10022

C

10002

J

10009

Q

10016

X

10023

D

10003

K

10010

R

10017

Y

10024

E

10004

L

10011

S

10018

Z

10025

F

10005

M

10012

T

10019



G

10006

N

10013

U

10020



Disk

Mirror Disk

  • Set the disk type as basic disk. (MCCS do not support dynamic disk.) 
  • Either volume size should be the same on both servers or volume size of standby server should be bigger for mirror disk environment.
  • Character should be the same for drive letter on both servers.
  • MCCS supports DAS, SAN, iSCSI
    (However, MCCS does not replicate the data on network driver like NAS.)

Note

In case of the mirrored disk which was added to the domain environment, it is essential to work by an account of a local administrator or higher.

Shared Disk

  • Supports SAN, DAS, iSCSI.

SCSI Reservation Disk

  • Supports shared storage that supports SCSI 3- SCSI among SAN protocols.
  • Virtual environments(VMware) have the following limitations:
    • Support only for RDM devices.
    • Must operate on an isolated ESXi server.
    • Not supported for VMDK storage.


User defined program

MCCS detects not only the physical resources but also the user defined program listed below.

  • Process service in a form of single process such as '.EXE'.
  • Application service that consists of several processes of application.
  • Window services that are managed by SCM.

When failure occurred in a group, MCCS will online the service resources on the standby which runs the same resources on the active. Users need to add the user program mentioned above to manage by MCCS.
Please refer to "Chapter 7. Resource of MCCS Manual" for more details about adding a resource. 
Before adding a resource, user should decide what kind of service of resource and read the following in advance and these attributes will be set.

  1. Process Service
    • folder where program of Process is registered
    • program name of '.exe' extension
    • name and password of the account that execute '.exe'.
    • Domain name in case of domain environment
    • WORKGROUP in case of general environment
  2. Application Service
    • Folder location of batch files of the program to register Application.
      (Please refer to "7.4 Applications of MCCS Manual" for more details.)
    • Name and password of the account to execute application
    • Domain for domain environment
    • WORKGROUP for general environment
  3. Window Service
    • Change the start type of service to 'Manual' in Windows Service Management.
    • Service name that was registered in Windows Service Management.

Checklist for Installation and Configuration

Following is the checklist for installation and configuration for MCCS.

ComponentNode1Node2

Active(Source)Standby(Target)
Network Info.Hostname

Service NetworkNIC Name

IP Address

Subnet Mask

Virtual IP Address

Heartbeat NetworkNIC name

IP Address

Subnet Mask

Mirroring NetworkNIC name

IP Address

Subnet Mask

Disk Info.Shared Disk Volume Letter


Mirrored Disk Volume Letter


Application Info.Protection Windows Service


Protection Process


Protection Application



Following is a sample checklist for MCCS installation and configuration.

ComponentNode1Node2


Active (Source)

Standby (Target)

Network Info.











Hostname

tom

jerry

Service Network




NIC name

Public

Public

IP Address

210.169.4.2

210.169.4.3

Subnet

255.255.255.0

255.255.255.0

Virtual IP

210.169.4.1 / 255.255.255.0


Heartbeat Network



NIC name

Heartbeat

Heartbeat

IP Address

10.10.10.1

10.10.10.2

Subnet

255.255.255.0

255.255.255.0

Mirroring Network



NIC name

Mirroring

Mirroring

IP Address

20.20.20.1

20.20.20.2

Subnet

255.255.255.0

255.255.255.0

Disk Info.


Shared Disk Volume Letter


D:


Mirrored Disk Volume Letter


E:


Application Info.



Protection Windows Service


MS-SQL Server 
MS-SQL Agent 
IIS


Protection Process


NotePad


Protection Application


Wordpad