Windows MSCS 群集安装手册一、安装前的准备工作1．系统请求环境硬件要求·群集服务节点的硬件，必须满足Windows 2000 Advanced Server或Windows 2000 DataCenter Server的硬件要求。
·有所安装的Windows 2000 Advanced Server或Windows 2000 DataCenter Server的启动盘。
该启动盘不能位于下面所描述的共享存储总线上。
·共享的磁盘有独立的PCI存储适配器（SCSI或光纤）。
启动盘适配器除外。
·群集里的每台计算机有两块PCI网络适配器。
·有外部存储单元，它跟所有的计算机相连。
它被作为群集磁盘使用。
·对于所有节点的所有硬件，每个插槽，每个卡，都应该是一样的。
这将简化配置，消除潜在的兼容性问题。
软件要求·在群集里的所有计算机上，都安装了Microsoft Windows 2000 Advanced Server或Windows 2000 DataCenter Server。
·名称解析手段，如域名系统（DNS），HOSTS。
网络要求·唯一的NetBIOS群集名。
·五个独立的、静态的IP地址：两个用于内部网的网络适配器，两个用于外接公众网的网络适配器，一个用于群集本身。
·一个群集服务的域名用户帐号（所有节点必须是同一个域的成员）。
·每个节点应该有两个网络适配器，一个用于外接公众网，另一个用于点对点的群集内部网。
共享磁盘要求·所有的共享磁盘，包括定额磁盘，都必须跟共享总线保持物理连接。
·将所有的共享磁盘都设置为基本（不是动态的）。
·将所有的磁盘分区都格式化为NTFS。
·建议对所有的磁盘，都使用容错的RAID配置（这不是强制要求）。
这里的关键是容错RAID配置-不能是无奇偶校验的阵列集。
Windows2008R2系统+SQL2008R2群集1、安装环境说明按照原有群集信息分配群集资源，如下：准备工作：1、网络配置（IP地址、优先级、NetBIOS设置）、机器名、共享磁盘连接测试（一次只开启一个节点连接共享磁盘）2、加入域。
3、创建群集2 创建故障转移群集1、分别在两台服务器中添加“故障转移群集”功能，按照安装向导完成安装2、验证故障转移群集打开“故障转移群集管理”，选择“验证配置”在“请选择服务器或群集”中，分别输入Serv-SQLA和Serv-SQLB，点击“添加”，“下一步”，之后，按照验证配置向导完成验证，验证完成后会出现验证报告，可根据验证报告检查出现的问题。
注意：1、要求所有的测试都通过，如果哪个测试没有通过，一定要找出原因，修改好后重新验证，直到所有验证通过，才能进行下一步。
2、在加入到节点的服务器的心跳网卡的NetBIOS设置为禁用。
3、创建群集第一步，在“故障转移集群管理”中，选择“创建一个群集”第二步，按照创建群集向导，选择服务器Serv-SQLA和Serv-SQLB（跟验证时一样）。
第三步，在“用于管理群集的访问点钟”输入集群名称“HNPCHA”，并且配置一个相应IP 地址“10.20.2.4”。
第四步，配置向导开始配置群集，等待群集配置完成，确认创建群集完成。
可以点击“查看报告””来看集群创建的结果。
4、群集测试Cluster安装成功后，可以测试一下群集是否可以工作：可以到域控服务器上查看AD中，多了个叫HNPCHA的机器，这是群集对外的机器名。
在DNS服务器上，多了一条A记录，可以看到HNPCHA的IP为刚才配置的虚拟IP。
用其它机器Ping HNPCHA或者虚拟IP可以ping通。
3、安装和配置MSDTC群集在安装MSDTC群集前，必须在两台服务器中安装配置相应的服务器角色“应用程序服务器”。
1、安装MSDTC所需要的服务器角色第一步，在角色管理中，添加角色“应用程序服务器”选择“添加必需的功能”，点击“下一步”第二步，在“角色服务”中，选择“传入远程事务处理”和“传出远程事务处理”按照向导，完成角色的添加。
SystemManager Version 6.3 Manager (Windows Version) Duplication Setup Guide (ExpressCluster X Edition)June 2016CONTENTSChapter 1Preface (3)Chapter 2Configuration Procedure (4)2.1Setting up ExpressCluster X (4)2.2Setting up MasterScope SystemManager (10)2.3Set up the start setting of MasterScope SystemManager (12)Chapter 3Uninstalling SystemManager (16)3.1Uninstalling SystemManager (16)3.2Deleting Files (16)Chapter 4Other Notes (16)4.1Registering Licenses (16)DisclaimerThe contents of this document are subject to change without notice.NEC Corporation takes no responsibility for any technical or editorial errors, or omissions, in this document.In addition, you are responsible for installing and using the software in accordance with the descriptions in this document in order to obtain the expected results.NEC Corporation owns the copyright to the contents of this document. You are not permitted to reproduce, modify, or translate this document in whole or in part without the permission of NEC Corporation.Trademark informationCLUSTERPRO® X is a registered trademark of NEC Corporation.Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and other countries.Other product names and slogans in this document are trademarks or registered trademarks of their respective companies.Other system names, company names, and product names are trademarks or registered trademarks of their respective companies.Chapter 1 PrefaceThis document provides an example procedure for using ExpressCluster X to set up a cluster configuration that has two nodes (for duplication). ExpressCluster X is an NEC product that can be used to switch running processes between nodes in a duplicated system.In this document, a host system included in a cluster is referred to as a node.Supplemental informationUpgrading an OSIf the incorrect procedure is used to upgrade the OS on a cluster server, failovers might occur at unexpected times. In the worst case, this might damage the system.Only upgrade the OS in accordance with the procedure on the setup card.This also applies when applying a service pack.Application rangeThis document describes ExpressCluster X 1.0 for Windows.ExpressCluster X® is a registered trademark of NEC Corporation.Microsoft® and Windows®are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.Other system names, company names, and product names are trademarks or registered trademarks of their respective companies.Chapter 2 Configuration ProcedureThis chapter provides a procedure for configuring a MasterScope SystemManager cluster environment.2.1 Setting up ExpressCluster XThis document assumes that ExpressCluster X is installed and that a cluster environment has been set up. For details about how to configure a cluster environment, also see the ExpressCluster X documents.* These documents can be downloaded from the following website: /en/global/prod/expresscluster/en/support/manuals.html?Creating failover groupsFor ExpressCluster X, nodes connected to the cluster are managed using units called failover groups (referred to as groups below).For details about how to create groups, see the relevant ExpressCluster X document (chapter 5 in the Installation and Creation Guide).Figure 2-1 WebManagerSetting up shared resourcesThe following describes how to set up shared resources for a failover group.Here, the following shared resources are assumed:⏹Floating IP address: 192.168.1.10⏹Shared (mirror) disk: Y drive⏹Service:Manager: MasterScope UMF Operations Manager_n (The italicized n representsa number.)Start Builder, and then select a failover group. (Here, select [MasterScope].)Figure 2-2 Group PropertiesRight click the group, and then select [Add Resource] from the displayed pop-up menu. The [Definition of a resouce] dialog box is displayed.First, set up the shared disk. For [Type], select [disk resource] or [mirror disk resource], and then enter the group name of the shared disk in the [Name] text box. Set up the disk in accordance with the instructions in the dialog box.Figure 2-3 Definition of a resouce (Shared Disk)Next, set up the floating IP address. Right click the group, select [Add Resource] from the displayed pop-up menu, select [floating ip resource] for [Type], and then enter the group name in the [Name] text box.Figure 2-4 Definition of a resouce (Floating IP Address)Specify the floating IP address in the [IP Address] text box.Figure 2-5 Floating IP Address AdditionSwitching between connected nodesTo switch between the active and standby nodes, use the following method.Open a command prompt, and then enter the following command:* A direct command can be entered because the environment variable PATH isregistered when ExpressCluster X is installed.The nodes can also be switched by right clicking the icon next to a group namedisplayed in the left WebManager pane and then selecting [Move] from the displayedpop-up menu.Figure 2-6 Switching Between Connected Nodes2.2 Setting up MasterScope SystemManagerInstall the MasterScope SystemManager manager on the Windows computers to be used as active and standby servers.For details about how to do so, see the Release Notes supplied with the product.As described in 2.1 Setting up ExpressCluster X, the following shared resources are assumed:∙Virtual host name: vhost1∙Shared disk: Y driveNotes* Install MasterScope SystemManager on the active server first, and then on the standby server.* It must be possible to reference the shared disk when installing the active server manager.* Use the same drive and folder as the installation destination for MasterScope SystemManager on the active and standby servers.* vhost1 is a host name that can be resolved to a floating IP address (192.168.1.10).The following describes the procedure for installing the MasterScope SystemManager manager.First, start up the cluster from the active node, and then install MasterScope SystemManager on the active node.In the installation settings window, specify the following settings:\Manager\sg is automatically added to the data area folder, and settings that must be shared are stored here.After installation finishes, confirm that \Manager\sg has been created in the data area folder.Next, set up the MasterScope SystemManager manager on the standby node.In the installation settings window, specify the following settings:After installation finishes, change the service startup attributes on both the active and standby nodes.In the [Start] menu, click [Administrative Tools] and then [Services]. Next, stop the [MasterScope UMF Operations Manager_1] service, and then change the [Startup type] in the properties from [Automatic] to [Manual].Figure 2-7 Service Properties* If using the bundled DB, change the [Startup type] for the bundled DB service to [Manual] in the same way.2.3 Set up the start setting of MasterScope SystemManagerSet up the service. Right click the group, select [Add Resource] from the displayed pop-up menu, select [execute resource] for [Type], and then enter the group name in the [Name] text box.Figure 2-8 Definition of a resouce (Service)Specify the Windows service name for the product in the [Service Name] text box.Figure 2-9 Service Name SpecificationThe service name varies depending on the node, so enter the following service name.* serial-number represents a number. Check the actual value in the Windows [Administrative Tools].To set up the dependencies, clear the [Follow the default dependence] check box, and then add resources that depend on the floating IP address and shared disk.Figure 2-10 Dependency SpecificationAfter specifying the settings, return to the failover group properties, and then confirm that the settings have been applied (by confirming that the window is like the one shown in Figure 2-2).* If using the bundled DB, add the resource for the bundled DB service in the same way. Set up the resource dependencies so that the bundled DB is dependent on SystemManager.Service name is [fdb_wfdbn].n indicates a service number of 1 or higher.(The value is set during installation of MasterScope products.)This manual describes startup settings for failover groups.Separately set up service monitoring in accordance with the relevant ExpressCluster X document.This concludes the ExpressCluster X setup.Chapter 3 Uninstalling SystemManager3.1 Uninstalling SystemManagerTo uninstall SystemManager, perform the procedure described in the SystemManager Release Memo (relememo.pdf).3.2 Deleting FilesAfter uninstalling SystemManager, files and directories remain on the shared disk.Manually delete directories on the shared disk specified during installation.Chapter 4 Other Notes4.1 Registering LicensesRegister licenses for a cluster environment on both the active and standby nodes.。
