MasterScope Virtual DataCenter Automation v3.0

Transcription

1 MasterScope Virtual DataCenter Automation v3.0 Cluster Construction Guide For Windows/EXPRESSCLUSTER X 1st Edition June, 2016 NEC Corporation

2 Disclaimer The copyrighted information noted in this document shall belong to NEC Corporation. Copying or revising this document, in whole or in part, is strictly prohibited without the permission of NEC Corporation. This document may be changed without prior notice. NEC Corporation shall not be liable for any technical or editing errors or omissions in this document. NEC Corporation shall not be liable for the accuracy, usability, or certainty of information noted in this document. Copyright Information SigmaSystemCenter, MasterScope, Network Manager, NEC Storage, ESMPRO, EXPRESSBUILDER, EXPRESSSCOPE, SIGMABLADE, UNIVERGE, and ProgrammableFlow are registered trademarks of NEC Corporation. VMware is a trademark or registered trademark of VMware, Inc. in the United States and other countries. Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, and Hyper-V are trademarks or registered trademarks of Microsoft Corporation in the United States of America and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States of America and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the United States of America and other countries. Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of Apache Software Foundation. Oracle, Solaris, Java, and WebLogic are registered trademarks of Oracle Corporation and its subsidiaries and affiliates in the United States of America and other countries. SAP is a trademark or registered trademark of SAP AG in Germany and other countries. Fortinet, FortiGate, and FortiGuard are registered trademarks of Fortinet, Inc. Other Fortinet products contained in this guide are trademarks of Fortinet, Inc. Thunder Series and AX Series of A10 Networks is a registered trademark of A10 Networks, Inc. Catalyst, IOS, Cisco IOS, Cisco, Cisco Systems, and Cisco logo are trademarks or registered trademarks of Cisco Systems, Inc. in the United States of America and other countries. F5, F5 Networks, F5 logo, and product names in the text are trademarks or registered trademarks of F5 Networks, Inc. in the United States of America and other countries. Other system names, company names, and product names in this document are trademarks or registered trademarks of their respective companies. i

3 The and marks are not included in this document. s on exporting this product If this product (including its software) is subject to regulation under the Foreign Exchange and Foreign Trade Law, it will be necessary to follow the procedures required by this law when exporting this product, such as obtaining an export license from the Japanese Government. If you require documents from NEC in order to obtain an export license, please contact the dealer where you purchased your MasterScope product, or your local NEC sales office. ii

4 Preface Target Readers and Objective This document is intended for system administrators who configure the cluster system for the Virtual DataCenter Automation management server and includes details of how to configure it. Notation Rules of This Document This document describes precautions, important items, and related information as follows. Indicates precautions, warnings, and supplementary notes for the function, operation, and setting Tip Indicates the location of reference destination information Notation rules In addition, the following notation rules are applied in this document. Notation How to use Example XXXXX " " XXXXX [ ] in a command line Monospace font (courier new) Italicized monospace font (courier new) < > Used before and after the items (text boxes, check boxes, or tabs, etc.) to be displayed in the dialog box or used for screen names (dialog boxes, windows, and others). Used used before and after other manual name. Indicates that the specification of the value in [ ] can be omitted. Indicates the outputs (messages, prompts, and others) from the command line or system. Indicates the items to be replaced with a valid value and input by users. When a space is included in the value, place before and after the value. Enter the machine name in the Machine name text box. All check box Setting window "Installation Guide" Installation Guide add [/a] Gr1 Perform the following command. replace Gr1 add GroupName InstallPath="Install Path" <Install DVD> iii

5 Contents Chapter 1. Overview Target Software Configuration Software Configuration Hardware Configuration Network Interface Card HBA (Host Bus Adapter) Shared disk Mirror Disk Sample Scripts...4 Chapter 2. Preparation Installing Windows Server Setting Up the Shared and Mirror Disks Installing EXPRESSCLUSTER X Installing the Required Software Installing SQL Server DHCP Server Configuration Setting Up the Windows Firewall...7 Chapter 3. Cluster Configuration for a Global Management Server [Active] Checking the SQL Server Startup Status [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation [Active] Setting Up the Operation Management Function Services [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users Positioning and modifying the SQL scripts Detaching a Database File Moving a Database File Attaching the Database Re-creating Database Users Acquiring the SID and Modifying an SQL Script Detaching a Database File [Active] Changing the Procedure of Starting an SQL Server Service [Active] Application Server SSL Settings [Active] Configuring the Application Server Environment Setting Up Monitoring Moving to the Standby System [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation..14 iv

6 3.11 [Standby] Stopping the FW Product Services and Changing the Startup Settings [Standby] Copying Data from the Active System [Standby] Detaching and Attaching a Database, and Re-creating Users Attaching a Databases Re-creating Users Detaching a Database [Standby] Changing the Procedure of Starting an SQL Server Service [Standby] Application Server SSL Settings [Standby] Configuring the Application Server Environment Moving to the Active System Setting Up the Script Resources Saving and Uploading Cluster Information Suspending the Cluster [Active] Registering the License to the Operation Management Function [Standby] Registering the License to the Operation Management Function [Active] Initializing the Operation Management and Asset Management Functions Setting the Service Governor Setting up the Property File for the Service Governor Resuming the Cluster Rebooting the Cluster...21 Chapter 4. Cluster Configuration for a Management Server [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version Upgrading an Existing Instance Adding the New Instance [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation [Active] Setting Up the SigmaSystemCenter Services [Active] Setting Up the IIS Server Certificate [Active] Detaching the SigmaSystemCenter Database [Active] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database [Active] Checking the SQL Server Startup [Active] Setting Up the Operation Management Function Services [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users Positioning and Modifying the SQL Scripts Detaching a Database File Moving a Database File Attaching the Databases Re-Creating Database Users Acquiring the SID and Modifying an SQL Script...33 v

7 4.9.7 Detaching a Database File [Active] Copying a SigmaSystemCenter Database File Modifying an SQL Script [Active] Changing the Procedure of Starting an SQL Server Service [Active] Copying a File or Folder Used by ESMPRO/ServerManager Copying the Work Folder Setting Up the Access Rights Copying the Service Folder and Editing the Configuration File Copying the DB Folder Copying the Package Storage Folder [Active] Editing ESMPRO/ServerManager Configuration Files [Active] Copying the Folder Used by DPM [Active] Copying the SystemProvisioning Local Script [Active] Revising the SigmaSystemCenter Related Registry Revising the Registry Used by ESMPRO/ServerManager Revising the Registry Used by DPM Registry Used by PVM Setting Up Monitoring Creating NWAutomation Folder Moving to the Standby System [Standby] Adding Upgrade and Instance to the SQL Server 2014 Product Version [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation [Standby] Setting Up the SigmaSystemCenter Services [Standby] Setting Up the IIS Server Certificate [Standby] Detaching the SigmaSystemCenter Database [Standby] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database [Standby] Stopping the FW Product Services and Changing the Start Setting [Standby] Copying Data from the Active System [Standby] Detaching and Attaching a Database, and Re-creating Users Attaching the Database Re-Creating Users Detaching the Database [Standby] Changing the Procedure of Starting an SQL Server Service [Standby] Editing ESMPRO/ServerManager Configuration Files Moving to the Active System Setting Up the Registry Synchronous Resources Setting Up the Script Resources Saving and Uploading Cluster Information Suspending the Cluster...45 vi

8 4.37 [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder [Active] Registering the License in SigmaSystemCenter [Active] Registering the License in the Operation Management Function [Standby] Registering the License in the Operation Management Function [Active] Registering a Subsystem in SigmaSystemCenter [Active] Setting Up the Linkage of the Operation Management and SigmaSystemCenter Functions [Active] Initializing the Operation Management Functions [Active] Setting monitoring definition of Management Server performance monitoring [Active] Linkage Settings with Global Management Server [Active] Setting the Accumulation Period of Statistical Information [Active] Changing the Environment Configuration of SystemMonitor Performance Monitoring Perform the Cluster Resume Reboot the Cluster...49 Chapter 5. Cluster Configuration of the VM Monitoring Server [Active] Using the Virtual DataCenter Automation Installer for Installation [Active] Setting Up the Services [Active]Checking the SQL Server Startup [Active] Detaching the Database, and Moving and Attaching a Database File Positioning and Modifying the SQL Scripts Detaching a Database File Moving a Database File Attaching the Database Re-Creating Database Users Acquiring the SID and Modifying an SQL Script Detaching the Database [Active] Changing the Procedure of Starting an SQL Server Service Moving to the Standby System [Standby] Using the Virtual DataCenter Automation Installer for Installation [Standby] Setting Up the Services [Standby] Copying Data from the Active System [Standby] Re-Creating Database Users Attaching the Database Re-Creating Users Detaching the Database [Standby] Changing the Procedure of Starting an SQL Server Service Moving to the Active System Setting Up the Script Resources...58 vii

9 5.14 Saving and Uploading Cluster Information Suspending the Cluster [Active] Registering License [Standby] Registering License [Active] Default Setting of the VM Monitoring Server Setting the Service Governor Resuming the Cluster Resume Rebooting the Cluster...61 Chapter 6. Cluster Configuration for an ID Management Server Assumption [Active] Installing the MasterScope Identity Manager Installation Changing the Service Start Setting Setting the System Environment Variable [Active] Setting Up MasterScope Identity Manager Changing the Database Directory and Log Directory Changing the Control File Moving to the Standby System [Standby] Installing MasterScope Identity Manager [Standby] Setting Up MasterScope Identity Manager Changing the Database Directory and Log Directory Changing the Control File Moving to the Active System Setting Up the Registry Synchronous Resources Setting Up the Script Resources Setting Up Service Resources Setting Up the Monitor Resources Saving and Uploading Cluster Information Suspending the Cluster Resuming the Cluster Rebooting the Cluster Cautions Actions to take when a failover occurs Stopping the EDS Protocol Server service When stopping Tomcat...70 Chapter 7. Cluster Configuration for a Management Agent Assumption Installing the Management Agent [Active] Setting up the Data Area Folder of the Management Agent...72 viii

10 7.4 Moving to the Standby System [Standby] Setting up the Data Area Folder of the Management Agent Moving to the Active System [Active] Configuring Management Agent...74 Chapter 8. Cluster Configuration for a Database Server Chapter 9. Upgrading the Cluster Environment Upgrading the Global Management Server Suspending the cluster [Active] Stopping the service [Active] Backup of the service governor [Active] Upgrading the global management server [Active] Updating the database [Active] Switching back the Service Governor Setup [Active] Changing the Procedure of Starting a service governor and stopping the services [Standby] Upgrading the global management server [Standby] Switching back the Service Governor Setup [Standby] Changing the Procedure of Starting a service governor and stopping the services Setting up the Script Resource Saving and Uploading Cluster Information Setting up the Service Governor [Active] Starting the service Resuming the cluster Applying the standard workflow template Editing Trace Log Settings of Resource Management Function Upgrading the Management Server Suspending the cluster [Active] Stopping the service [Active] Upgrading the management server [Active] Updating the database [Active] Stopping the service [Standby] Upgrading the management server [Standby] Stopping the service [Active] Starting the service Resuming the cluster Upgrading the SigmaSystemCenter Applying the standard workflow template Upgrading the VM Monitoring Server Suspending the cluster [Active] Stopping the service [Active] Upgrading the VM monitoring server [Active] Updating the database [Standby] Upgrading the VM monitoring server [Standby] Stopping the service...86 ix

11 9.3.7 [Active] Starting the service Resuming the cluster Upgrading the ID Management Server [Active] Extracting the existing data Uninstalling MasterScope Identity Manager on the ID Management Server Cluster configuration for an ID management server [Active] Reflecting the existing data Upgrading the Management Agent Stopping the failover group Starting the disk resource and floating IP resource [Active] Stopping the service [Active] Upgrading the management agent [Active] Starting the service Stopping the disk resource and floating IP resource Starting the disk resource and floating IP resource [Standby] Stopping the service [Standby] Upgrading the management agent [Standby] Starting the service Stopping the disk resource and floating IP resource Starting the failover group...91 Chapter 10. Rolling update in the cluster environment Rolling update the Global Management Server [Active] Updating the database [Active] Backup of the service governor [Standby] Upgrading the global management server [Standby] Changing the Procedure of Starting a service governor and stopping the services [Standby] Switching back the Service Governor Setup Stopping the failover group Setting up the Script Resource Saving and Uploading Cluster Information Starting the failover group Applying the standard workflow template [Active] Upgrading the global management server [Active] Changing the Procedure of Starting a service governor and stopping the services [Active] Switching back the Service Governor Setup Moving to the Active System...97 Chapter 11. Upgrading from NW Automation on the Cluster Environment Upgrading the Global Management Server Preparation Suspending the cluster [Active] Stopping the service [Active] Upgrading the global management server x

12 [Active] Changing the Procedure of Starting a service governor and stopping the services [Standby] Upgrading the global management server [Standby] Changing the Procedure of Starting a service governor and stopping the services Setting up the Script Resource Saving and Uploading Cluster Information [Active] Starting the service Setting up the global management server Resuming the cluster Upgrading the Management Server Preparation Stopping the failover group Starting the disk resource and floating IP resource [Active] Starting the SQL server [Active] Attaching the databases [Active] Re-creating database users [Active] Upgrading the management server [Active] Setting up the SigmaSystemCenter [Active] Stopping the service [Active] Detaching the databases [Active] Stopping the SQL server Stopping the disk resource and floating IP resource Starting the disk resource and floating IP resource [Standby] Starting the SQL server [Standby] Attaching the databases [Standby] Re-creating database users [Standby] Upgrading the management server [Standby] Setting up the SigmaSystemCenter [Standby] Stopping the service [Standby] Detaching the databases [Standby] Stopping the SQL server Stopping the disk resource and floating IP resource Starting the failover group Setting Up the registry synchronous resources Setting up the script resources Saving and Uploading Cluster Information Suspending the cluster Registering and setting up the management server Resuming the Cluster Rebooting the cluster Upgrading the ID Management Server Changing the registry Chapter 12. Changing a single configuration (non-cluster) environment to a cluster configuration Applying a cluster configuration to the global management server xi

13 Stopping the service Moving the data area folder Create a link to the data area folder Editing the SysMonMgr.ini Editing the registry Cluster Configuration for a Global Management Server Applying a cluster configuration to the management server Stopping the service Moving the data area folder Create a link to the data area folder Editing the SysMonMgr.ini Editing the registry Cluster Configuration for a Management Server Applying a cluster configuration to the VM monitoring server Stopping the service Moving the data area folder Create a link to the data area folder Editing the SysMonMgr.ini Editing the registry Cluster Configuration for a VM Monitoring Server Chapter 13. s Appendix A. Revision History Appendix B. User Customizable Files and Folders xii

14 List of Figures Figure 1-1 Figure 1-2 System configuration example of a shared disk type cluster...2 System configuration example of a mirror disk type cluster...3 xiii

15 List of Tables Table 1-1 IP address setting...3 Table 1-2 Floating IP address setting...4 Table 3-1 Setting values for global management server...10 Table 4-1 Setting value of management server...25 Table 5-1 Setting value of VM monitoring server...52 Table 6-1 When not replicating...67 Table 6-2 When replicating...68 Table 6-4 When not replicating...68 Table 6-5 When replicating...68 xiv

16

17 Chapter 1. Overview Chapter 1. Overview This document provides example procedures for configuring clusters for a Virtual DataCenter Automation global management server, management server, and VM Monitoring server with two nodes. In this document, the host system included in a cluster is referred to as a node. Contents 1.1 Target Software Configuration Software Configuration Hardware Configuration Sample Scripts...4 1

18 Chapter 1. Overview 1.1 Target Software Virtual DataCenter Automation v3.0 EXPRESSCLUSTER X 3.3 for Windows 1.2 Configuration In this document, a shared or mirror disk type failover cluster system as shown below is configured. Each of them consists of two nodes: "active" and "standby". The active system is used for usual operation, and when it goes down, the standby system takes over (one-way standby configuration). Only one failover group is used. The procedures in this document are described based on these configuration examples. Please replace the IP address, drive letter, or other elements in accordance with your environment. Figure 1-1 System configuration example of a shared disk type cluster 2

19 Chapter 1. Overview Figure 1-2 System configuration example of a mirror disk type cluster 1.3 Software Configuration In the configuration examples in this document, the following software is installed in each of the nodes. Each is installed onto the local disk of each node. OS Cluster software DBMS Windows Server 2012 R2 EXPRESSCLUSTER X 3.3 for Windows SQL Server 2014 For the Virtual DataCenter Automation operating environment, refer to Chapter 6. Operating Environments/ System Requirements in the Virtual DataCenter Automation First Step Guide. 1.4 Hardware Configuration Network Interface Card In the configuration examples in this document, the interconnect LAN is also used as a public LAN. A floating IP address is set for this interface. In the configuration examples above, " " is assigned to the active server, " " is assigned to the standby server, and " " is assigned to the floating IP address. Also, another host name is defined for the floating IP address, and name resolution from the host name to the floating IP address is set up. In this document, the hostname that can solve the floating IP address is called "Virtual hostname". Table 1-1 IP address setting Server IP address Host name Active server vdca1 Standby server vdca2 3

20 Chapter 1. Overview Table 1-2 Floating IP address setting Server Floating IP address Virtual host name Active server vdca Standby server vdca HBA (Host Bus Adapter) Logical disks are assigned to the HBAs of the active and standby systems constituting the shared disk type cluster so that the shared disk and server are connected Shared disk This disk, which contains the data used for the Virtual DataCenter Automation management server, is used to transfer the resources to the standby system. The shared disk to be used in EXPRESSCLUSTER X is created on the storage Mirror Disk This disk, which contains the data used for the Virtual DataCenter Automation management server, is used to transfer the resources to the standby system. The mirror disk to be used in EXPRESSCLUSTER X is created on the node of each of the active and standby systems. 1.5 Sample Scripts The scripts included in this document are samples. Attaching or detaching the database used in Virtual DataCenter Automation and starting or stopping the service can be controlled by registering any of said scripts, as the script sources, in EXPRESSCLUSTER X, or by copying them to the local disk of each of the active and standby nodes and editing them as appropriate. The sample spricts are stored in the following directory of the installation DVD. <Install DVD>:\script 4

21 Chapter 2. Preparation Chapter 2. Preparation This chapter describes the preparations required for configuring clusters for a global management server, management server, and VM monitoring server. Be sure to perform these preparations. Contents 2.1 Installing Windows Server Setting Up the Shared and Mirror Disks Installing EXPRESSCLUSTER X Installing the Required Software DHCP Server Configuration Setting Up the Windows Firewall...7 5

22 2.1 Installing Windows Server Install Windows Server in the active and standby systems. For the system requirements, refer to Chapter 6. Operating Environments/System Requirements in the Virtual DataCenter Automation First Step Guide. 2.2 Setting Up the Shared and Mirror Disks Set up the partition and drive letter for the shared disk or mirror partition according to Setup after Hardware Configuration in the EXPRESSCLUSTER X Installation and Configuration Guide. 2.3 Installing EXPRESSCLUSTER X Install EXPRESSCLUSTER X in the active and standby systems and initialize it according to the EXPRESSCLUSTER X Installation and Configuration Guide. Create failover group "failover", and register only the floating IP and shared disk resources to ensure all the settings allow switching between active and standby systems. Any procedure in the next or subsequent chapter must be performed with the system switched to the active system. 2.4 Installing the Required Software Install software according to 2.2 Software Required to be Installed in Advance in the Virtual DataCenter Automation Installation Guide. Perform the installation for both the active and standby nodes Installing SQL Server 2014 Install SQL Server 2014 Standard Edition or Enterprise Edition. Express Edition is not available in a cluster environment. Perform the installation process for both the active and standby nodes. Install the server according to Installing SQL Server in Virtual DataCenter Automation Installation Guide. 2.5 DHCP Server Configuration Prepare the DHCP server according to the DHCP Server Configuration in the Virtual DataCenter Automation Installation Guide. Chapter 2. Preparation If the DHCP server is installed in the same machine as the Virtual DataCenter Automation management server, the DHCP server will offer its service by using the IP address being set in the node, whereas the Virtual DataCenter Automation management server will offer its service by using the floating IP address. In this case, it is necessary to set up the Virtual DataCenter Automation management and DHCP servers on the assumption that they are operating in separate machines. 6

23 2.6 Setting Up the Windows Firewall Chapter 2. Preparation If the Windows firewall is currently enabled, it is necessary to perform the exception settings that are not set during installation. Add it to the exception list according to Setting Up the Windows Firewall and Appendix C. Network and Protocol in the Virtual DataCenter Automation Installation Guide. 7

24 Chapter 3. Cluster Configuration for a Global Management Server Chapter 3. Cluster Configuration for a Global Management Server Contents 3.1 [Active] Checking the SQL Server Startup Status [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation [Active] Setting Up the Operation Management Function Services [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users [Active] Changing the Procedure of Starting an SQL Server Service [Active] Application Server SSL Settings [Active] Configuring the Application Server Environment Setting Up Monitoring Moving to the Standby System [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation [Standby] Stopping the FW Product Services and Changing the Startup Settings [Standby] Copying Data from the Active System [Standby] Detaching and Attaching a Database, and Re-creating Users [Standby] Changing the Procedure of Starting an SQL Server Service [Standby] Application Server SSL Settings [Standby] Configuring the Application Server Environment Moving to the Active System Setting Up the Script Resources Saving and Uploading Cluster Information Suspending the Cluster [Active] Registering the License to the Operation Management Function [Standby] Registering the License to the Operation Management Function [Active] Initializing the Operation Management and Asset Management Functions Setting the Service Governor Setting up the Property File for the Service Governor Resuming the Cluster Rebooting the Cluster

25 Before starting the work described in this chapter, perform the work described in "Chapter 2. Preparation (page 5)". The procedures in this chapter assume that those in the subsequent sections must be performed in the order as described. [Active] and [Standby] represent the systems in which to perform the procedures described in this section. All procedures in subsequent sections must be performed after the failover group created in the preparation has been switched so that access can be obtained from the active system to the shared (or mirror) disk. In this document, the following IP addresses, host names, and virtual host names (host name by which the floating IP address is resolved) are set for the respective nodes. Active server: , gm1 Standby server: , gm2 Floating IP: , gm The S: drive is used for the shared disk of the active and standby servers. Chapter 3. Cluster Configuration for a Global Management Server 3.1 [Active] Checking the SQL Server Startup Status Check that the following services are active. If they are not active, start them. SQL Server (FWCMDB) SQL Server Browser If the SQL Server Agent (FWCMDB) is specified to start automatically, change the setting to Disabled. 9

26 3.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation Install the server according to the procedure in 2.3 Installing the components of Global Management Server in the Virtual DataCenter Automation Installation Guide. On the integrated management server setting screen of Virtual DataCenter Automation, enter the following setting values. The configuration examples in this document use the settings shown below. The sections in bold face differ from the configuration examples in Virtual DataCenter Automation Installation Guide. Install Directory Path Table 3-1 Setting values for global management server Setting Default value Value Self Hostname <Global management server name> *1*2 Management Server/Agent Port Viewer Port Change Data Directory Data Directory Store Initial Setting Data Application Server Type (default value) (default value) Yes Application Server - HTTP Port Application Server - HTTPS Port Tomcat - Management Port Tomcat - AJP/1.3 Port Portal - SQL Server Host Name Portal - SQL Server Instance Name Portal - SQL Server Port WebService Port 8081 Database - Hostname Database - Instance Name Chapter 3. Cluster Configuration for a Global Management Server S:\vDCA\GM\FW Yes (default value) Tomcat(default value) localhost(default value) FWCMDB(default value) 1433(default value) localhost(default value) FWCMDB(default value) Database - Database Name GM_<Global management server name> *1*2 Database - Authentication Type Database - Password Windows authentication(default value) No(default value) *1 For the setting values of the host names, see "Chapter 13. s (page 117)" *2 Specify the host name of the global management server. For a cluster configuration, specify the virtual host name of the global management server (host name by which the floating IP address is resolved). In the configuration examples in this chapter, <global management server name> is gm. Once installation has finished, restart the system. 10

27 Chapter 3. Cluster Configuration for a Global Management Server When restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so that EXPRESSCLUSTER X will not regard it as an abnormal end. 3.3 [Active] Setting Up the Operation Management Function Services Stop the following services, and change [Startup type] to [Manual]. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service VDCGMProxy_n (The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment.) 3.4 [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users Positioning and modifying the SQL scripts Edit the SQL scripts required for database clustering. A sample script is stored in Install DVD:\scr ipt\cluster-pro\gm. After the SQL scripts have been created, place them in the folder in the same path on each of the local disks of the active and standby system hosts. This document provides an example where the script storage location is C:\MSSQL and the database file storage location is S: \MSSQL\Data. Script Description 1 C:\MSSQL\DEACT.sql Used to detach a database file. 2 C:\MSSQL\ACT.sql Used to attach a database file. 3 C:\MSSQL\ACT2.sql Used to re-create a user account. 4 C:\MSSQL\SELECT.sql Used to acquire the SID of an mco database user. 5 C:\MSSQL\RECRTUSR.sql Used to re-create an mco database user. The actual script contents are shown below. If the database storage location (S:\MSSQL and after) differs from that shown here, change the bold-face fields accordingly. "@Password" is internally used by the components of Virtual DataCenter Automation. Do not change this. DEACT.sql ALTER DATABASE GM_<global management server name> SET OFFLINE WITH ROLLBAC K IMMEDIATE EXEC sp_detach_db 'GM_<global management server name>', TRUE 11

28 Chapter 3. Cluster Configuration for a Global Management Server ACT.sql EXEC sp_attach_db 'GM_<global management server = 'S:\MSSQL\Data\GM_<global management server = 'S:\MSSQL\Data\GM_<global management server name>_log.ldf' ACT2.sql use GM_<global management server name> EXEC sp_change_users_login 'Auto_Fix', 'GM_<global management server name>', NULL, 'GM_<global management serv er name>@password' EXEC sp_password NULL, 'GM_<global management server name>@password', 'GM_<global management server name>' SELECT.sql SELECT SUSER_SID('GM_<global management server name>') RECRTUSR.sql ALTER DATABASE GM_<global management server name> SET OFFLINE WITH ROLLBAC K IMMEDIATE EXEC sp_detach_db 'GM_<global management server name>', TRUE EXEC = N'GM_<global management server name>' EXEC sp_attach_db 'GM_<global management server = 'S:\MSSQL\Data\GM_<global management server = 'S:\MSSQL\Data\GM_<global management server name>_log.ldf' CREATE LOGIN GM_<global management server name> WITH PASSWORD = 'GM_<global management server name>@password', DEFAULT_DATABASE = GM_<global management server name>, SID = 0x????, CHECK_POLICY = OFF The "SID = 0x????" field needs to be edited in accordance with your environment. Editing is performed in "3.4.6 Acquiring the SID and Modifying an SQL Script (page 13)", so it is not part of the procedure in this section Detaching a Database File Execute a detach process in the active system host in order to move a database file onto the shared disk. Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output Moving a Database File After the detach processing is complete, move the database file onto the shared disk. If the instance name FWCMDB is in use, the default value of the path in which the source database file is stored is as follows. C:\Program Files\Microsoft SQL\MSSQL12.FWCMDB\MSSQL\DATA 12

29 Chapter 3. Cluster Configuration for a Global Management Server File name GM_<Global management server name>.mdf GM_<Global management server name>_log.ldf Destination S:\MSSQL\Data\GM_<Global management server name>.mdf S:\MSSQL\Data\GM_<Global management server name>_log.ldf Attaching the Database Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log After command execution, view C:\MSSQL\ACT.log to confirm that no error message has been output Re-creating Database Users Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.log After command execution, view C:\MSSQL\ACT2.log to confirm that no error message has been output Acquiring the SID and Modifying an SQL Script Open the command prompt window, and execute the following commands. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \SELECT.sql /o C:\MSSQL\SELECT.log Change <sa_user> and >sa_password< in accordance with your environment. <sa_user> SQL Server administrator user name (sa) <sa_password> SQL Server administrator user name s password After command execution, check the contents of the output log file. This command outputs a hexadecimal number of 32 characters beginning with 0x. Apply this number to the "0x????" field in the script file. SELECT.log Log file name S:\MSSQL\RECRTUSR.sql Destination reflected Detaching a Database File Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output. 13

30 3.5 [Active] Changing the Procedure of Starting an SQL Server Service Stop the following service, and set [Startup type] to [Manual]. SQL Server (FWCMDB) 3.6 [Active] Application Server SSL Settings Setting SSL according to the procedure in SSL Settings of Application Server in Virtual DataCenter Automation Installation Guide. 3.7 [Active] Configuring the Application Server Environment Stop the following service, and set [Startup type] to [Manual]. Apache Tomcat 8.0 ServiceGovernor 3.8 Setting Up Monitoring Set up the monitoring function according to Chapter 6 Setting up MISSION CRITICAL OPERATIONS and Chapter 9 Setting up Monitoring in the Virtual DataCenter Automation Configuration Guide. Set up this monitoring function for either the active or the standby system. 3.9 Moving to the Standby System Chapter 3. Cluster Configuration for a Global Management Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the standby system [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation Install the operation management function and service governor function in the standby system. Perform the same procedure as for installation to the active system("3.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation (page 10)"), except for the following three steps: Set the [Store initial setting data] setting to [No]. Specify the same value as the active system in "Database setting - Database name". After installation has finished, do not restart the system. 14

31 Chapter 3. Cluster Configuration for a Global Management Server Before performing installation on the standby system host, check that you can access the shared disk from the standby system host. If you cannot access the shared disk from the standby system host, perform setting to allow access before installation [Standby] Stopping the FW Product Services and Changing the Startup Settings Stop the following services, and change [Startup type] to [Manual]. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. Once setup has finished, restart the system. To restart the system, use the cluster reboot function of EXPRESSCLUSTER WebManager to avoid the error termination of the EXPRESSCLUSTER X. After cluster reboot, the failover group moves to the active system. Thus, restart the system, and then retry moving to the standby system [Standby] Copying Data from the Active System Copy the files from the active system host to the standby system host as follows. Copy source (active system) C:\Program Files (x86)\nec\vdca\gm\fw\manager\sg\sysmonmgr.ini C:\Program Files (x86)\nec\vdca\gm\fw\manager\sg\configurationsettin gmgr.ini C:\Program Files (x86)\nec\vdca\gm\fw\manager\sg\wfdbmgr\wfdb.ini C:\MSSQL\DEACT.sql C:\MSSQL\ACT.sql C:\MSSQL\ACT2.sql C:\MSSQL\SELECT.sql C:\MSSQL\RECRTUSR.sql Copy destination (standby system) Same path Same path Same path Same path Same path Same path Same path Same path 15

32 3.13 [Standby] Detaching and Attaching a Database, and Re-creating Users Perform the settings in the following sections by using the SQL script copied in "3.12 [Standby] Copying Data from the Active System (page 15)". The <sa_user> and <sa_password> values used in this section need to be changed in accordance with your environment. <sa_user> SQL Server administrator user name (sa) <sa_password> SQL Server administrator user name s password The result from execution of a command line in this section may show a message as listed below, but this is not a problem. Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'GM_<Global management server name>' is not valid login or has no authority Attaching a Databases Execute the following two commands to attach a database. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT.sql /o C:\MSSQL\ACT.log > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT2.sql /o C:\MSSQL\ACT2.log Re-creating Users Execute the following command to re-create the users. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log Detaching a Database Execute the following command to detach the database. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \DEACT.sql /o C:\MSSQL\DEACT.log 3.14 [Standby] Changing the Procedure of Starting an SQL Server Service Stop the following services, and set the [Startup type] to [Manual]. SQL Server (FWCMDB) Chapter 3. Cluster Configuration for a Global Management Server 16

33 3.15 [Standby] Application Server SSL Settings Setting SSL according to the procedure in "3.6 [Active] Application Server SSL Settings (page 14)" [Standby] Configuring the Application Server Environment Stop the following services, and set the [Startup type] to [Manual]. Apache Tomcat 8.0 ServiceGovernor 3.17 Moving to the Active System Chapter 3. Cluster Configuration for a Global Management Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system Setting Up the Script Resources From the EXPRESSCLUSTER WebManager, add the script files included in this document to the failover group as the script resources. File name <Install DVD>:\script\cluster-pro\GM\start.bat <Install DVD>:\script\cluster-pro\GM\stop.bat Service starting script Description Service stopping script Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, change to Config Mode, click failover group, and select the [Add] in the [Edit]. 2. On the displayed dialog, change [Type] to [script resurce], and select [Next]. 17

34 Chapter 3. Cluster Configuration for a Global Management Server 3. On the displayed dialog, select the [Detail] tab, and click the [Add] button to register the script. Edit the script (*.bat) accordingly in the following cases. The path of the shared disk is different. The instance name of SQL Server is different. The number at the end of the service name of MasterScope UMF Operations Web Service is different Saving and Uploading Cluster Information From the EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, the cluster will not operate normally because no configuration information is reflected to the active or standby system Suspending the Cluster From the steps to date, the cluster should be left suspended while the shared (or mirror) disk remains invisible. Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, perform the cluster resume and cluster start actions. 2. Ensure the failover group has started with on the active system. Then, suspend the cluster. 18

35 Chapter 3. Cluster Configuration for a Global Management Server 3. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services [Active] Registering the License to the Operation Management Function Register the code word to the operation management function according to Registering License to Operation Management Function and Registering CodeWord to Operation Management Function in Virtual DataCenter Automation Installation Guide. Install the global management server console if not installed [Standby] Registering the License to the Operation Management Function Register the code word to the operation management function for the standby node. The license key to register must be the same as that defined in "3.21 [Active] Registering the License to the Operation Management Function (page 19)". Use the command line tool for registration. Using the following command, change the current directory before starting the registration. > cd "C:\Program Files (x86)\nec\vdca\gm\fw\manager\bin" 1. Use the following command to list up the registered licenses: > LicenseCmd.exe LIST Acquire the application code from the license information that was output, and apply for the code word. 2. If the license is not registered, register the license key by executing the following command. If the license is already registered, this step is not necessary. Apply for the code word in 3. > LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1> > LicenseCmd.exe ADD <ProductCode_2> <LicenseKey_2> > LicenseCmd.exe ADD <ProductCode_3> <LicenseKey_3> Output the license list again. 3. The code word can be registered by using the following listed commands. 19

36 Chapter 3. Cluster Configuration for a Global Management Server > LicenseCmd.exe REGISTER <LicenseKey_1> <Codeword_1> > LicenseCmd.exe REGISTER <LicenseKey_2> <Codeword_2> > LicenseCmd.exe REGISTER <LicenseKey_3> <Codeword_3> Enter <ProductCode_n>, <LicenseKey_n>, and <Codeword_n> according to the license information [Active] Initializing the Operation Management and Asset Management Functions Initialize the operation management and asset management functions according to Default Settings of Asset Management Function and Default Settings of Operation Management Function in the Virtual DataCenter Automation Installation Guide Setting the Service Governor Perform the procedure in Setting up the Service Governor in Virtual DataCenter Automation Installation Guide. Perform the procedures 1 to 5. in both manners of [Active] and [Standby]. copy the following file onto manner of [Standby] when the service governor is operated in the cluster configuration. C:\Program Files (x86)\nec\vdca\gm\fw\tomcat\vdcapikey.jks 3.25 Setting up the Property File for the Service Governor Perform the same procedures as Setting up the Property File for Service Governor in the Virtual DataCenter Automation Installation Guide. The configuration file of the service governor and the log that is output by the service governor are separately managed for [Active] and [Standby] when the service governor is operated in the cluster configuration Resuming the Cluster From EXPRESSCLUSTER WebManager, resume the cluster. 20

37 Chapter 3. Cluster Configuration for a Global Management Server 3.27 Rebooting the Cluster From EXPRESSCLUSTER WebManager, reboot the cluster. After rebooting the cluster, move the failover group to verify that neither the active nor standby system causes any error. 21

38 Chapter 4. Cluster Configuration for a Management Server Chapter 4. Cluster Configuration for a Management Server Contents 4.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation [Active] Setting Up the SigmaSystemCenter Services [Active] Setting Up the IIS Server Certificate [Active] Detaching the SigmaSystemCenter Database [Active] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database [Active] Checking the SQL Server Startup [Active] Setting Up the Operation Management Function Services [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users [Active] Copying a SigmaSystemCenter Database File Modifying an SQL Script [Active] Changing the Procedure of Starting an SQL Server Service [Active] Copying a File or Folder Used by ESMPRO/ServerManager [Active] Editing ESMPRO/ServerManager Configuration Files [Active] Copying the Folder Used by DPM [Active] Copying the SystemProvisioning Local Script [Active] Revising the SigmaSystemCenter Related Registry Setting Up Monitoring Creating NWAutomation Folder Moving to the Standby System [Standby] Adding Upgrade and Instance to the SQL Server 2014 Product Version [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation [Standby] Setting Up the SigmaSystemCenter Services [Standby] Setting Up the IIS Server Certificate [Standby] Detaching the SigmaSystemCenter Database [Standby] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database [Standby] Stopping the FW Product Services and Changing the Start Setting

39 Chapter 4. Cluster Configuration for a Management Server 4.28 [Standby] Copying Data from the Active System [Standby] Detaching and Attaching a Database, and Re-creating Users [Standby] Changing the Procedure of Starting an SQL Server Service [Standby] Editing ESMPRO/ServerManager Configuration Files Moving to the Active System Setting Up the Registry Synchronous Resources Setting Up the Script Resources Saving and Uploading Cluster Information Suspending the Cluster [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder [Active] Registering the License in SigmaSystemCenter [Active] Registering the License in the Operation Management Function [Standby] Registering the License in the Operation Management Function [Active] Registering a Subsystem in SigmaSystemCenter [Active] Setting Up the Linkage of the Operation Management and SigmaSystemCenter Functions [Active] Initializing the Operation Management Functions [Active] Setting monitoring definition of Management Server performance monitoring [Active] Linkage Settings with Global Management Server [Active] Setting the Accumulation Period of Statistical Information [Active] Changing the Environment Configuration of SystemMonitor Performance Monitoring Perform the Cluster Resume Reboot the Cluster

40 Before starting the work described in this chapter, perform the work described in "Chapter 2. Preparation (page 5)". The procedures in this chapter assume that those in the subsequent sections must be performed in the order as described. [Active] and [Standby] represent the systems in which to perform the procedures described in this section. All procedures in subsequent sections must be performed after the failover group created during preparation has been switched so that the shared (or mirror) disk can be accessed from the active system. In this document, the following IP addresses, host names, and virtual host names (host name by which the floating IP address is resolved) are set for the respective nodes. Active server: , mom1 Standby server: , mom2 Floating IP address: , mom Chapter 4. Cluster Configuration for a Management Server Configure the vcenter cluster environment when using VMWare on the virtual base according to the EXPRESSCLUSTER X for Windows VMWare vcenter Server Cluster System Configuration Guide. 4.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version After SigmaSystemCenter is installed, SQL Server 2014 Express is installed and used as the DBMS. Because it will be used in a cluster configuration, it needs to be upgraded to Standard Edition or Enterprise Edition. If Standard Edition or Enterprise Edition is already being used, this procedure is not necessary. In addition, because another new SQL Server instance will be needed, install the new instance when upgrading. 24

41 4.1.1 Upgrading an Existing Instance Upgrade the database instance by the following procedure. If Standard Edition or Enterprise Edition is already being used, this procedure is not necessary. 1. Insert the media of the SQL Server product version and start the SQL Server installation center. 2. Select [Maintenance] from the left side menu. 3. Select [Edition Upgrade]. 4. Follow the wizard to upgrade the "SSCCMDB" instance. 5. Also perform steps "3. (page 25)" and "4. (page 25)" for the "DPMDBI" instance Adding the New Instance Adds the instance by the procedure in Installing SQL Server in the Virtual DataCenter Automation Installation Guide. This document assumes that "FWCMDB" has been specified as the instance name like in the installation guide. 4.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation Install the server according to the procedure in 2.5 Installing the components of Management Server in Virtual DataCenter Automation Installation Guide. On the management server setting screen of Virtual DataCenter Automation, enter the following setting values. The configuration examples in this document use the settings shown below. The sections in bold face differ from the configuration examples in Virtual DataCenter Automation Installation Guide. Install Directory Path Setting Table 4-1 Setting value of management server Default value Value Self Hostname <Management server name> *1*2 VM Monitoring Server/Agent Port Viewer Port Change Data Directory Data Directory Store Initial Setting Data GlobalManager Hostname GlobalManager Port (default value) (default value) Yes WebService Port 8081 Database - Hostname Database - Instance Name Chapter 4. Cluster Configuration for a Management Server S:\vDCA\MoM\FW Yes (default value) Specify the host name of the global management server. *1* (default value) localhost (default value) FWCMDB (default value) Database - Database Name MoM_<Management server name> *1*2 25

42 Chapter 4. Cluster Configuration for a Management Server Setting Value Database - Authentication Type Windows authentication (default value) Database - Password No (default value) Database - Database for Network Manager External (default value) Database - Port for Network Manager DB (default value) ESMPRO/ServerManager - Administrator Name Determine it. ESMPRO/ServerManager - Administrator's Password Determine it. DeploymentManager - Management Server's IP Address Specify the management server IP address. *4 *1 For notes concerning the host names, see "Chapter 13. s (page 117)". *2 Specify the host name of the management server. For the cluster configuration, specify the virtual host name of the management server (host name by which the floating IP address is resolved). Delete symbols other than underscores (_) from the host name. In the configuration examples in this chapter, <Management server name> is mom. *3 In the configuration examples in this document, the global management server name is gm due to the cluster configuration. *4 Specify the IP address of the management server. For a cluster configuration, specify the floating IP address of the management server. In the configuration examples in this chapter, the address is Once installation has finished, restart the system. When restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so that EXPRESSCLUSTER X will not regard it as an abnormal end. When the EXPRESSCLUSTER X screen is activated, close the screen before installing the management server. 4.3 [Active] Setting Up the SigmaSystemCenter Services Stop the following services, and set the [Startup type] to [Manual]. ESMPRO/SM - Alert Manager Socket(R) Service - Alert Manager WMI Service - DianaScope ModemAgent - Dmi Event Watcher - ESM Alert Service - ESM Base Service - ESM Command Service - ESM Remote Map Service - ESMPRO/SM Base Alert Listener - ESMPRO/SM Base Service 26

43 Chapter 4. Cluster Configuration for a Management Server - ESMPRO/SM Common Component - ESMPRO/SM Event Manager - ESMPRO/SM Web Container Because ESMPRO/SM has dependency between services, stop the services in the following order. Order Display name Service name 1 DianaScope ModemAgent DianaScope ModemAgent 2 ESMPRO/SM Web Container ESMWebContainer 3 ESMPRO/SM Event Manager ESMEventManager 4 ESMPRO/SM Base Alert Listener ESMBaseAlertListener 5 ESMPRO/SM Common Component ESMCommonComponent 6 Alert Manager Socket(R) Service AlertManagerSocketReceiveService 7 ESMPRO/SM Base Service ESMDSVNT 8 Dmi Event Watcher *1 DmiEventWatcher 9 ESM Alert Service ESMASVNT 10 ESM Command Service Nvcmd 11 ESM Remote Map Service Nvrmapd 12 ESM Base Service Nvbase 13 Alert Manager WMI Service AlertManagerWMIService *1 Need not be started unless DMI alerts are received. Add the services indicated by (*1) to "start.bat" and "stop.bat" when using these services because they are not included in "start.bat" and "stop.bat" in the Virtual DataCenter Automation media. In this case, describe "stop.bat" in the above order. Describe "start.bat" in the reverse order of the above. DPM PVM - DeploymentManager API Service - DeploymentManager Backup/Restore Management - DeploymentManager Get Client Information - DeploymentManager PXE Management - DeploymentManager PXE Mtftp - DeploymentManager Remote Update Service - DeploymentManager Schedule Management - DeploymentManager Transfer Management - PVMService Sysmon 27

44 - System Monitor Performance Monitoring Service 4.4 [Active] Setting Up the IIS Server Certificate To enable the use of a WebAPI supported by the SigmaSystemCenter function, set up IIS. Issue any server certificate that is used in a clustered Virtual DataCenter Automation management server in advance. Importing server certificate 1. Start "mmc" after specifying the file name and executing the file. 2. Click [File] - [Add/Remove Snap-in]. 3. Add [Certificates] from the available snap-in items and click [OK]. 4. Select [Computer account] and click [Next]. 5. Select [Local Machine] and click [Finish]. 6. Click [OK]. 7. Click [Certificates (Local Computer)], right-click the logical store name [Person], and click [AllTasks]-[Imoprt]. The import wizard screen for the certificate appears. 8. Click [Next]. 9. Select the file name <certificate>.pfx and click [Next]. 10. Enter "changeit" as the password of the secret key and perform the import according to the wizard. 11. Click [Certificates (Local Computer)], right-click the logical store name [Trusted Root Certification Authorities], and click [AllTasks]-[Imoprt]. 12. Repeat the procedures "8. (page 28)" to "10. (page 28)". Binding the server certificate 1. Start up [Internet Information Services (IIS) Manager]. 2. Right-clicks [Default Web Site] in [Sites] and select [Edit Bindings]. 3. Click [Add]. 4. Configure as the following list and click [OK]. Chapter 4. Cluster Configuration for a Management Server Item Type https IP address All unused IP Addresses Port SSL certificate Preregistered certificate name Value 4.5 [Active] Detaching the SigmaSystemCenter Database Detach the database used for the SigmaSystemCenter function. 1. Start the command prompt, and execute the following command. 28

45 Chapter 4. Cluster Configuration for a Management Server > sqlcmd -E -S "(local)\ssccmdb" 2. Execute the following query, and detach the PVM/SYSMON database file. 1> alter database [PVMINF] set offline with ROLLBACK IMMEDIATE 2> exec sp_detach_db 'PVMINF',TRUE 3> alter database [RM_PerformanceDataBase2] set offline with ROLLBACK IMMEDIATE 4> exec sp_detach_db 'RM_PerformanceDataBase2',TRUE 5> go 3. Start the command prompt, and execute the following command. > sqlcmd -E -S "(local)\dpmdbi" 4. Execute the following query, and detach the DPM database file. 1> alter database [DPM] set offline with ROLLBACK IMMEDIATE 2> exec sp_detach_db 'DPM',TRUE 3> go This concludes detaching the database used for the SigmaSystemCenter function. 4.6 [Active] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database Stop a database instance used for the SigmaSystemCenter function so that it will not start automatically. Stop the following two services, and set [Startup type] to [Manual]. SQL Server (DPMDBI) SQL Server (SSCCMDB) 4.7 [Active] Checking the SQL Server Startup Check that the following services are active. If they are not active, start them. SQL Server (FWCMDB) SQL Server Browser 4.8 [Active] Setting Up the Operation Management Function Services Stop the following services, and change the [Startup type] to [Manual]. FTBase service NvPRO Base Manager NvPRO ResourceManagerAPI Service 29

46 MasterScope UMF Operations Manager_102 MasterScope UMF Operations Web Service vdcmomproxy_n Chapter 4. Cluster Configuration for a Management Server The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. 4.9 [Active] Detaching the Operation Management Function Database, Moving and Attaching a Database File, and Re-creating Users Positioning and Modifying the SQL Scripts Edit the SQL scripts required for database clustering. A sample script is stored in <Install DVD>: \script\cluster-pro\mom. After the SQL scripts have been created, place them in the folder in the same path on each of the local disks of the active and standby system hosts. This document provides an example where the script storage location is C:\MSSQL and the database file storage location is S: \MSSQL\Data. Script Value 1 C:\MSSQL\DEACT.sql Used to detach an mco database file. 2 C:\MSSQL\ACT.sql Used to attach an mco database file. 3 C:\MSSQL\ACT2.sql Used to re-create a user account. 4 C:\MSSQL\SELECT.sql Used to acquire the SID of an mco database user. 5 C:\MSSQL\RECRTUSR.sql Used to re-create an mco database user. 6 C:\MSSQL\NVSELECT.sql Used to acquire the SID of an nvprodb database user. 7 C:\MSSQL\NVRECRTUSR.sql Used to re-create an nvprodb database user. 8 C:\MSSQL\attach_d.sql Used to attach a dpm database file. 9 C:\MSSQL\attach_p.sql Used to attach a pvm database file. 10 C:\MSSQL\detach_d.sql Used to detach a dpm database file. 11 C:\MSSQL\dettach_p.sql Used to detach a pvm database file. The actual script contents are shown below. If the database storage location (S:\MSSQL and after) differs from that shown here, change the bold-faced fields accordingly. Then, replace "MoM_<management server name>" with the string used to specify the database name by using the management server setting value in "4.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation (page 25)". "@Password" is internally used by the components of the Virtual DataCenter Automation. Do not change this. DEACT.sql ALTER DATABASE MoM_<Management server name> SET OFFLINE WITH ROLLBACK I MMEDIATE 30

47 EXEC sp_detach_db 'MoM_<Management server name>', TRUE ALTER DATABASE nvprodb SET OFFLINE WITH ROLLBACK IMMEDIATE EXEC sp_detach_db 'nvprodb', TRUE ACT.sql EXEC sp_attach_db 'MoM_<Management server = 'S:\MSSQL\Data\MoM_<Management server = 'S:\MSSQL\Data\MoM_<Management server name>_log.ldf' EXEC sp_attach_db = = 'S:\MSSQL\Data\nvprodb_log.ldf' ACT2.sql use MoM_<Management server name> EXEC sp_change_users_login 'Auto_Fix', 'MoM_<Management server name>', NULL, 'MoM_<Management server EXEC sp_password NULL, 'MoM_<Management server name>@password', 'MoM_<Management server name>' use nvprodb EXEC sp_change_users_login 'Auto_Fix', 'nvprodb', NULL, 'nvprodb@password' EXEC sp_password NULL, 'nvprodb@password', 'nvprodb' SELECT.sql SELECT SUSER_SID('MoM_<Management server name>') RECRTUSR.sql ALTER DATABASE MoM_<Management server name> SET OFFLINE WITH ROLLBACK I MMEDIATE EXEC sp_detach_db 'MoM_<Management server name>', TRUE EXEC = N'MoM_<Management server name>' EXEC sp_attach_db 'MoM_<Management server = 'S:\MSSQL\Data\MoM_<Management server = 'S:\MSSQL\Data\MoM_<Management server name>_log.ldf' CREATE LOGIN MoM_<Management server name> WITH PASSWORD = 'MoM_<Management server name>@password', DEFAULT_DATABASE = MoM_<Management server name>, SID = 0x????, CHECK_POLICY = OFF The "SID = 0x????" field needs to be edited in accordance with your environment. Editing is performed in "4.9.6 Acquiring the SID and Modifying an SQL Script (page 33)"Script", so it is not part of the procedure in this section. NVSELECT.sql SELECT SUSER_SID('nvprodb') NVRECRTUSR.sql Chapter 4. Cluster Configuration for a Management Server 31

48 Chapter 4. Cluster Configuration for a Management Server ALTER DATABASE nvprodb SET OFFLINE WITH ROLLBACK IMMEDIATE EXEC sp_detach_db 'nvprodb', TRUE EXEC = N'nvprodb' EXEC sp_attach_db = = 'S:\MSSQL\Data\nvprodb_log.LDF' CREATE LOGIN nvprodb WITH PASSWORD = 'nvprodb@password', DEFAULT_DATABASE = nvprodb, SID = 0x????, CHECK_POLICY = OFF The "SID = 0x????" field needs to be edited in accordance with your environment. Editing is performed in "4.9.6 Acquiring the SID and Modifying an SQL Script (page 33)", so it is not part of the procedure in this section Detaching a Database File Execute detach processing in the active system host in order to move a database file onto the shared disk. Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output Moving a Database File After completion of detach processing, move the database file onto the shared disk. If the instance name FWCMDB is in use, the default value of the path in which the source database file is stored is as follows. C:\Program Files\Microsoft SQL\MSSQL12.FWCMDB\MSSQL\DATA File name MoM_<Management server name>.mdf MoM_<Management server name>_log.ldf nvprodb.mdf nvprodb_log.ldf Destination S:\MSSQL\Data\MoM_<Management server name>.mdf S:\MSSQL\Data\MoM_<Management server name>_log.ldf S:\MSSQL\Data\nvprodb.mdf S:\MSSQL\Data\nvprodb_log.ldf Attaching the Databases Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log After command execution, view C:\MSSQL\ACT.log to confirm that no error message has been output Re-Creating Database Users Open the command prompt window, and execute the following commands. 32

49 > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.log After command execution, view C:\MSSQL\ACT2.log to confirm that no error message has been output Acquiring the SID and Modifying an SQL Script Open the command prompt window, and execute the following two commands. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \SELECT.sql /o C:\MSSQL\SELECT.log > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \NVSELECT.sql /o C:\MSSQL\NVSELECT.log Change <sa_user> and <sa_password> in accordance with your environment. <sa_user> SQL Server administrator user name (sa) <sa_password> SQL Server administrator user password Chapter 4. Cluster Configuration for a Management Server After command execution, check the contents of the output log file. This command outputs a hexadecimal number of 32 characters beginning at 0x. Reflect them to the "0x????" field in the script file. SELECT.log NVSELECT.log Log file name S:\MSSQL\RECRTUSR.sql Destination reflected S:\MSSQL\NVRECRTUSR.sql Detaching a Database File Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output [Active] Copying a SigmaSystemCenter Database File Copy a database file onto the shared disk as follows. Copy source C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MS SQL\DATA\PVMINF.mdf C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MS SQL\DATA\pvminf_2.ndf C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MS SQL\DATA\PVMINF_log.ldf Copy destination S:\MSSQL\Data\PVMINF.mdf S:\MSSQL\Data\pvminf_2.ndf S:\MSSQL\Data\PVMINF_log.ld f 33

50 Chapter 4. Cluster Configuration for a Management Server Copy source C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MS SQL\DATA\RM_PerformanceDataBase2.mdf C:\Program Files\Microsoft SQL Server\MSSQL12.SSCCMDB\MS SQL\DATA\RM_PerformanceDataBase2_log.ldf C:\Program Files\Microsoft SQL Server\MSSQL12.DPMDBI\MSS QL\DATA\DPM_DATA.MDF C:\Program Files\Microsoft SQL Server\MSSQL12.DPMDBI\MSS QL\DATA\DPM_LOG.LDF Copy destination S:\MSSQL\Data\RM_Performanc edatabase2.mdf S:\MSSQL\Data\RM_Performanc edatabase2_log.ldf S:\MSSQL\Data\DPM_DATA.MDF S:\MSSQL\Data\DPM_LOG.LDF Each path under "Source" above is available if the default installation has been executed. If the SQL Server version or installation folder differs from that for the default installation, check the path in accordance with your environment Modifying an SQL Script If the destination path of the database file differs from that assumed in this document, edit the database attach scripts attach_p.sql and attach_d.sql to make them identical to that in this document (bold-faced fields below). The script is included in the <Install DVD>\script\cluster-pro\MoM. attach_p.sql create database pvminf on (filename='s:\mssql\data\pvminf.mdf'), (filename='s:\mssql\data\pvminf_log.ldf'), (filename='s:\mssql\data\pvminf_2.ndf') for attach create database RM_PerformanceDatabase2 on (filename='s:\mssql\data\rm_performancedatabase2.mdf'), (filename='s:\mssql\data\rm_performancedatabase2_log.ldf') for attach attach_d.sql create database DPM on (filename='s:\mssql\data\dpm_data.mdf'), (filename='s:\mssql\data\dpm_log.ldf') for attach 4.12 [Active] Changing the Procedure of Starting an SQL Server Service Stop the following service, and set [Startup type] to [Manual]. SQL Server (FWCMDB) 34

51 4.13 [Active] Copying a File or Folder Used by ESMPRO/ServerManager Copying the Work Folder Copythe work folder onto the shared (or mirror) disk. Chapter 4. Cluster Configuration for a Management Server Copy Source C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmwork Copy Destination S:\vDCA\MoM\SSC\SMM \NVWORK Setting Up the Access Rights Set up access rights for the work folder and all its sub-folders. 1. Select S:\vDCA\MoM\SMM\NVWORK and open [Properties]. 2. Select the [Security] tab and set it as follows. Group or user name Administrators Everyone SYSTEM Full control Read and execute Full control Access right Copying the Service Folder and Editing the Configuration File Copy the service folder onto the shared (or mirror) disk. Copy Source C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\wbserver \webapps\esmpro\web-inf\service Copy Destination S:\vDCA\MoM\SSC\SMM\WEB- INF\service After copying, edit S:\vDCA\MoM\SSC\SMM\WEB-INF\service\options.txt as follows. : EU_RM_PKG_DATAPOOL_PATH=S:\vDCA\MoM\SSC\SMM\pkgpool (*1) : CLUSTER_FIP= (*2) (*1) The update package storage folder detailed later. (*2) Floating IP address. (Create the entry if not yet created.) Next, edit "S:\vDCA\MoM\SSC\SMM\WEB-INF\service\esmpro\eventman\indication \subscribesetting.properties" according to the following procedure. Describe "indicationreceiveglobalip" in FIP. The following is a configuration example when setting the FIP address to " ". indicationreceiveglobalip=

52 Copying the DB Folder Copy the DB folder onto the shared (or mirror) disk as follows. Chapter 4. Cluster Configuration for a Management Server Copy Source C:\Program Files (x86)\nec\smm\esmweb\wbserver\webapps\esmpro \WEB-INF\db Copy Destination S:\vDCA\SMM\WEB-INF\db Copying the Package Storage Folder Copy the package storage folder onto the shared (or mirror) disk as follows. Copy Source C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\pkgpool Copy Destination S:\vDCA\MoM\SSC\SMM\pkgpool 4.14 [Active] Editing ESMPRO/ServerManager Configuration Files Edit the configuration files as follows. 1. C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\jslalert\jsl.ini wrkdir=s:\vdca\mom\ssc\smm\web-inf\service stderr=s:\vdca\mom\ssc\smm\web-inf\service\log\jslalert\stderr.log stdout=s:\vdca\mom\ssc\smm\web-inf\service\log\jslalert\stdout.log 2. C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\jslcmn\jsl.ini wrkdir=s:\vdca\mom\ssc\smm\web-inf\service stderr=s:\vdca\mom\ssc\smm\web-inf\service\log\jslcmn\stderr.log stdout=s:\vdca\mom\ssc\smm\web-inf\service\log\jslcmn\stdout.log 3. C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\jslweb\jsl.ini wrkdir=s:\vdca\mom\ssc\smm\web-inf\service stderr=s:\vdca\mom\ssc\smm\web-inf\service\log\jslweb\stderr.log stdout=s:\vdca\mom\ssc\smm\web-inf\service\log\jslweb\stdout.log 4. C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\jslem\jsl.ini wrkdir=s:\vdca\mom\ssc\smm\web-inf\service stderr=s:\vdca\mom\ssc\smm\web-inf\service\log\jslem\stderr.log stdout=s:\vdca\mom\ssc\smm\web-inf\service\log\jslem\stdout.log 5. C:\Program Files (x86)\nec\vdca\mom\ssc\smm\esmweb\wbserver\webapps\ax is2\web-inf\classes\eci.service.properties options.txt.fullpath=s:\\vdca\\mom\\ssc\\smm\\web-inf\\service\\option s.txt Use "\\" as the folder delimiter. 36

53 4.15 [Active] Copying the Folder Used by DPM Copy the folder onto the shared (or mirror) disk. Chapter 4. Cluster Configuration for a Management Server Copy source C:\Program Files (x86)\nec\vdca\mom\ssc\deploymentmanager \Datafile Copy destination S:\vDCA\MoM\SSC \DeploymentManager\Datafile 4.16 [Active] Copying the SystemProvisioning Local Script Copy the folder onto the shared (or mirror) disk. Copy source C:\Program Files (x86)\nec\vdca\mom\ssc\pvm\script C:\Program Files (x86)\nec\vdca\mom\ssc\pvm\conf C:\Program Files (x86)\nec\vdca\mom\ssc\pvm\deployfiles Copy destination S:\vDCA\MoM\SSC\PVM\Script S:\vDCA\MoM\SSC\PVM\conf S:\vDCA\MoM\SSC\PVM\deployf iles 4.17 [Active] Revising the SigmaSystemCenter Related Registry Revising the Registry Used by ESMPRO/ ServerManager HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE Name Initial data New data Communit yname WorkDir GeneralFil ter DiosaFilte r mgr_<computername> C:\Program Files (x86)\nec\vdca\mom \SSC\SMM\NVWORK C:\Program Files (x86)\nec\vdca\mom \SSC\SMM\NVWORK\Alert\filter\generi csg C:\Program Files (x86)\nec\vdca\mom \SSC\SMM\NVWORK\Alert\filter\odiosa sg mgr_esmpro S:\vDCA\MoM\SSC\SMM\NVWORK S:\vDCA\MoM\SSC\SMM\NVWORK\Alert\fi lter\genericsg S:\vDCA\MoM\SSC\SMM\NVWORK\Alert\fi lter\odiosasg HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE\AlertViewer Name Initial data New data AlertPath C:\Program Files (x86)\nec\vdca\mom \SSC\SMM\NVWORK\alert S:\vDCA\MoM\SSC\SMM\NVWORK\alert HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMSM\CurrentVersion\ODBC 37

54 Chapter 4. Cluster Configuration for a Management Server Name Initial data New data LocalFile Directory C:\Program Files (x86)\nec\vdca\mom \SSC\SMM\NVWORK\ESMPRO S:\vDCA\MoM\SSC\SMM\NVWORK\ESMPRO Revising the Registry Used by DPM HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager Name Initial data New data AuReport Dir BmpDir ClientDir DataFileD ir ScenarioD ir SnrReport Dir C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile\Log File\AuReport C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile\bmp C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile\Cli ent C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile\Sce nario C:\Program Files (x86)\nec\vdca\mom \SSC\DeploymentManager\DataFile\Log File\SnrReport S:\vDCA\MoM\SSC\DeploymentManager\D atafile\logfile\aureport S:\vDCA\MoM\SSC\DeploymentManager\D atafile\bmp S:\vDCA\MoM\SSC\DeploymentManager\D atafile\client S:\vDCA\MoM\SSC\DeploymentManager\D atafile S:\vDCA\MoM\SSC\DeploymentManager\D atafile\scenario S:\vDCA\MoM\SSC\DeploymentManager\D atafile\logfile\snrreport HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager_DB Name Initial data New data DBInstall Dir C:\Program Files\MicrosoftSQL Serve r\mssql12.dpmdbi\mssql\data S:\MSSQL\Data Registry Used by PVM HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\DPMProvider\Script Name Initial data New data ScriptFold er C:\Program Files (x86)\nec\vdca\mom \SSC\PVM\Script S:\vDCA\MoM\SSC\PVM\Script HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM Name Initial data New data ConfPath C:\Program Files (x86)\nec\vdca\mom \SSC\PVM\conf S:\vDCA\MoM\SSC\PVM\conf HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\DPMProvider Name Initial data New data DeployFil e C:\Program Files (x86)\nec\vdca\mom \SSC\PVM\deployfiles S:\vDCA\MoM\SSC\PVM\deployfiles 38

55 4.18 Setting Up Monitoring Set up the monitoring function according to Chapter 3 Setting up Network Manager, Chapter 6 Setting up MISSION CRITICAL OPERATIONS and Chapter 9 Setting up Monitoring in Virtual DataCenter Automation Configuration Guide. Set up this monitoring function for either the active or the standby system Creating NWAutomation Folder Create the NWAutomation folder on the shared disk. The path of the created folder is as follows. S:\vDCA\MoM\FW\Manager\sg\NWAutomation 4.20 Moving to the Standby System Chapter 4. Cluster Configuration for a Management Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the standby system [Standby] Adding Upgrade and Instance to the SQL Server 2014 Product Version Also for the standby system, upgrade the database and add the instance by the same procedure as "4.1 [Active] Adding Upgrade and Instance to the SQL Server 2014 Product Version (page 24)" [Standby] Using the Virtual DataCenter Automation Integrated Installer for Installation Install the operation management function in the standby system. Perform the same procedure as the installation into the active system ("4.2 [Active] Using the Virtual DataCenter Automation Integrated Installer for Installation (page 25)"), except the following three: Set the [Store initial setting data] setting to [No]. Specify the same value as the active system in "Database setting - Database name". After installation has finished, do not restart the system. 39

56 4.23 [Standby] Setting Up the SigmaSystemCenter Services Also for the standby system, set up the SigmaSystemCenter function services by the same procedure as "4.3 [Active] Setting Up the SigmaSystemCenter Services (page 26)" [Standby] Setting Up the IIS Server Certificate Also for the standby system, set up the IIS server certificate by the same procedure as "4.4 [Active] Setting Up the IIS Server Certificate (page 28)" [Standby] Detaching the SigmaSystemCenter Database Also for the standby system, detach the database by the same procedure as "4.5 [Active] Detaching the SigmaSystemCenter Database (page 28)" [Standby] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database Stop the following two services, and set [Startup type] to [Manual]. SQL Server (DPMDBI) SQL Server (SSCCMDB) 4.27 [Standby] Stopping the FW Product Services and Changing the Start Setting Stop the following services, and change [Startup type] to [Manual]. FTBase service NvPRO Base Manager NvPRO ResourceManagerAPI Service MasterScope UMF Operations Manager_102 MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment.) Once setup has finished, restart the system. Chapter 4. Cluster Configuration for a Management Server 40

57 To restart the system, use cluster reboot of EXPRESSCLUSTER WebManager. This is in order to avoid an abnormal end from the view of EXPRESSCLUSTER X. Chapter 4. Cluster Configuration for a Management Server After rebooting the cluster, the failover group moves to the active system. Thus, restart the system, and then retry moving to the standby system [Standby] Copying Data from the Active System Copy the files from the active system host to the standby system host as follows. Copy source (active system) C:\Program Files (x86)\nec\vdca\mom\fw\manager\sg\sysmonmgr.ini C:\Program Files (x86)\nec\vdca\mom\fw\manager\sg\configurationsetti ngmgr.ini C:\Program Files (x86)\nec\vdca\mom\fw\manager\sg\wfdbmgr\wfdb.ini C:\Program Files (x86)\nec\vdca\mom\fw\manager\sg\nvpro\nvprobasemgr.ini C:\MSSQL\DEACT.sql C:\MSSQL\ACT.sql C:\MSSQL\ACT2.sql C:\MSSQL\SELECT.sql C:\MSSQL\RECRTUSR.sql C:\MSSQL\NVSELECT.sql C:\MSSQL\NVRECRTUSR.sql C:\MSSQL\attach_d.sql C:\MSSQL\attach_p.sql C:\MSSQL\detach_d.sql C:\MSSQL\detach_p.sql Copy destination (standby system) Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path Same path 4.29 [Standby] Detaching and Attaching a Database, and Re-creating Users Perform the settings in the following sections by using the SQL scripts copied in "4.28 [Standby] Copying Data from the Active System (page 41)". The <sa_user> and <sa_password> values used in this section need to be changed in accordance with your environment. <sa_user> SQL Server administrator user name (sa) 41

58 Chapter 4. Cluster Configuration for a Management Server <sa_password> SQL Server administrator user name s password The result from execution of a command line in this section may show a message as listed below, but this is not a problem. Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'mco' is not a valid login or unauthorized. Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'nvprodb' is not a valid login or unauthorized Attaching the Database Execute the following two commands to attach a database. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT.sql /o C:\MSSQL\ACT.log > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT2.sql /o C:\MSSQL\ACT2.log Re-Creating Users Execute the following two commands to re-create the users. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \NVRECRTUSR.sql /o C:\MSSQL\NVRECRTUSR.log Detaching the Database Execute the following command to detach the database. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \DEACT.sql /o C:\MSSQL\DEACT.log 4.30 [Standby] Changing the Procedure of Starting an SQL Server Service Stop the following services, and set the [Startup type] to [Manual]. SQL Server (FWCMDB) 4.31 [Standby] Editing ESMPRO/ServerManager Configuration Files Also for the standby system, editing ESMPRO/ServerManager Configuration FIles by the same procedure as "4.14 [Active] Editing ESMPRO/ServerManager Configuration Files (page 36)". 42

59 4.32 Moving to the Active System Chapter 4. Cluster Configuration for a Management Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system Setting Up the Registry Synchronous Resources Register the registry synchronous resources into the failover group from EXPRESSCLUSTER WebManager. The following eight registries are the registries to register. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMSM HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMAlertMan\BaseSetting \Receive HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\ESMAlertMan\Socket \Socketr HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Nvbase HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\DeploymentManager_DB HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, change to Config Mode, click failover group, and select the [Add] in the [Edit]. 2. On the displayed dialog, change [Type] to [registry synchronization resource], and select [Next]. 43

60 Chapter 4. Cluster Configuration for a Management Server 3. On the displayed dialog, register the each registry key Setting Up the Script Resources From the EXPRESSCLUSTER WebManager, add the script files included in this document to the failover group as the script resources. File name <Install DVD>:\script\cluster-pro\MoM\vDCA\start.bat <Install DVD>:\script\cluster-pro\MoM\vDCA\stop.bat Service starting script Description Service stopping script Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, change to Config Mode, click failover group, and select the [Add] in the [Edit]. 2. On the displayed dialog, change [Type] to [script resurce], and select [Next]. 44

61 Chapter 4. Cluster Configuration for a Management Server 3. On the displayed dialog, select the [Detail] tab, and click the [Add] button to register the script. Edit the script (*.bat) accordingly in the following cases. The path of the shared disk is different. The instance name of SQL Server is different. The number at the end of the service name of MasterScope UMF Operations Web Service is different. When being different from a default folder in an installation destination of a Management Server, please correct a installed path(2 Points) of a service script(start.bat). rem ******************* rem Set Routing rem ******************* call "C:\Program Files (x86)\nec\vdca\mom\fw\manager\bin\nwautomation \nwa_routerestore.bat" 4.35 Saving and Uploading Cluster Information From the EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, the cluster will not operate normally because no configuration information is applied to the active or standby system Suspending the Cluster From the steps to date, the cluster should be left suspended while the shared (or mirror) disk remains invisible. Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, perform the cluster resume and cluster start actions. 2. Ensure the failover group has started with the active system. Then, select the cluster suspend. 45

62 Chapter 4. Cluster Configuration for a Management Server 3. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder Operate the active system, and perform the actions with the cluster suspended. 1. Create the following two empty folders on the shared (or mirror) disk. S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup S:\vDCA\MoM\SSC\DeploymentManager\Deploy 2. Open the DPM Web console, and log in to the system. The specified IP addresses are floating IP addresses. The initial login ID and password are admin and admin. 3. Select [DPM Server] from the [Management] view. 4. Select the [Detail Setting] in the [Configuration]. 5. Set the [General] sttings as follows. Setting [Server Information] - [IP Address] [Image Setting] - [Forlder for Backup Image] [Image Setting] - [Folder for Image] Value Specify the floating IP address. S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup S:\vDCA\MoM\SSC\DeploymentManager\Deploy 6. For the [DHCP Server] tab, select [DHCP Server is installed on another machine]. 7. Click [OK] to save the settings. Although the error message dialog box may be displayed, close it and click [OK] again because there is no problem. 8. From the [Operations] view, select [Scenarios] - [Built-in Scenarios]. 9. Edit the scenario files System_Backup and System_Restore_Unicast as follows. Setting [Back Up / Restore] - [Image File] Value S:\vDCA\MoM\SSC\DeploymentManager\DeployBackup\backup.lbr 10. Click [OK] to save the settings. 11. This closes the Web console. 46

63 4.38 [Active] Registering the License in SigmaSystemCenter Register the license key according to Registering License to SigmaSystemCenter Function in the Virtual DataCenter Automation Installation Guide [Active] Registering the License in the Operation Management Function Register the code word in the operation management function according to Registering License to Operation Management Function and Registering Code Word to Operation Management Function in the Virtual DataCenter Automation Installation Guide. Install the global management server console if not installed [Standby] Registering the License in the Operation Management Function Register the code word in the operation management function with regard to the standby node. The license key to register must be the same as that defined in "4.39 [Active] Registering the License in the Operation Management Function (page 47)". Use the command line tool for registration on the standby node. Using the following command, change the current directory before starting the registration. > cd "C:\Program Files (x86)\nec\vdca\mom\fw\manager\bin" 1. Use the following command to list up the registered licenses: Chapter 4. Cluster Configuration for a Management Server > LicenseCmd.exe LIST Acquire the application code from the license information that was output, and apply for the code word. 2. If the license is not registered, register the license key by executing the following command. If the license is already registered, this step is not necessary. Apply for the code word in 3. > LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1> > LicenseCmd.exe ADD <ProductCode_2> <LicenseKey_2> Output the license list again. 3. The code word can be registered by using the following listed commands. > LicenseCmd.exe REGISTER <ProductCode_1> <LicenseKey_1> > LicenseCmd.exe REGISTER <ProductCode_2> <LicenseKey_2> Enter <ProductCode_n>, <LicenseKey_n>, and <Codeword_n> according to the license information. 47

64 4.41 [Active] Registering a Subsystem in SigmaSystemCenter Register the DPM server in the SigmaSystemCenter subsystem according to Registering a Virtual DataCenter Automation Component to the SigmaSystemCenter in the Virtual DataCenter Automation Configuration Guide. When registering it, be sure to specify the floating IP address [Active] Setting Up the Linkage of the Operation Management and SigmaSystemCenter Functions Set up the linkage of the operation management and asset management functions according to step 19 or later of Setting up WebAPI for SSC in Virtual DataCenter Automation Installation Guide. For the HostName key in the [SSCAPI] section, specify the floating IP address or virtual host name (host name by which the floating IP address is resolved) [Active] Initializing the Operation Management Functions Chapter 4. Cluster Configuration for a Management Server Initialize the operation management and asset management functions according to Default Settings of Operation Management Function in the Virtual DataCenter Automation Installation Guide [Active] Setting monitoring definition of Management Server performance monitoring Refer to Setting the Monitoring Definition of Management Server Performance Monitoring in Virtual DataCenter Automation Installation Guide, then set monitoring definition for monitoring performance of Management Server [Active] Linkage Settings with Global Management Server Refer to Linkage setting between Global Management Server in Virtual DataCenter Automation Installation Guide, then perform the linkage setting between Global Management Server and Management Server. Upper-level manager name and upper-level manager host name specify floating IP address or virtual host name(host name that can be resolved floating IP address). 48

65 4.46 [Active] Setting the Accumulation Period of Statistical Information Refer to Setting the Accumulation Period of Statistical Information in Virtual DataCenter Automation Installation Guide, then set accumulationperiod of statistical information of managed machine [Active] Changing the Environment Configuration of SystemMonitor Performance Monitoring 1. Execute the SystemMonitor management console. 2. In the "Environment configuration" dialog box, select the [SystemProvisioning] tab and change [SystemProvisioning management server] to "localhost" Perform the Cluster Resume From the EXPRESSCLUSTER WebManager, resume the cluster. Chapter 4. Cluster Configuration for a Management Server 4.49 Reboot the Cluster From the EXPRESSCLUSTER WebManager, reboot the cluster. After rebooting the cluster, move the failover group to verify that neither the active nor standby system causes any error. 49

66 Chapter 5. Cluster Configuration of the VM Monitoring Server Chapter 5. Cluster Configuration of the VM Monitoring Server Contents 5.1 [Active] Using the Virtual DataCenter Automation Installer for Installation [Active] Setting Up the Services [Active]Checking the SQL Server Startup [Active] Detaching the Database, and Moving and Attaching a Database File [Active] Changing the Procedure of Starting an SQL Server Service Moving to the Standby System [Standby] Using the Virtual DataCenter Automation Installer for Installation [Standby] Setting Up the Services [Standby] Copying Data from the Active System [Standby] Re-Creating Database Users [Standby] Changing the Procedure of Starting an SQL Server Service Moving to the Active System Setting Up the Script Resources Saving and Uploading Cluster Information Suspending the Cluster [Active] Registering License [Standby] Registering License [Active] Default Setting of the VM Monitoring Server Setting the Service Governor Resuming the Cluster Resume Rebooting the Cluster

67 The procedures in this chapter are performed only in the case of using the cluster configuration of the VM monitoring server. For the VM Monitoring Server, assume one-way standby configuration similar to those which are described in the "1.2 Configuration (page 2)". In this document, the following IP addresses are set for the respective nodes. Active server: , rm1 Standby server: , rm2 Floating IP: , rm Chapter 5. Cluster Configuration of the VM Monitoring Server The following chapters are described and that are intended to be performed in the order listed. [Active] and [Standby] represent the systems in which to perform the procedures described in this section. All procedures in subsequent sections must be performed after the failover group created in the preparation has been switched so that access can be obtained from the active system to the shared (or mirror) disk. 5.1 [Active] Using the Virtual DataCenter Automation Installer for Installation Installs the operation management functions in the procedure of 2.7 Installing the components of VM Monitoring Server in the Virtual DataCenter Automation Installation Guide On the VM monitoring server setting screen of Virtual DataCenter Automation, enter the following setting values. The configuration examples in this document use the settings shown below. The sections in bold face differ from the configuration examples in Virtual DataCenter Automation Installation Guide. 51

68 Chapter 5. Cluster Configuration of the VM Monitoring Server Table 5-1 Setting value of VM monitoring server Setting Value Install Directory Path Default value Self Hostname <VM monitoring server name> *1*2 Agent Port (default value) Viewer Port (default value) WebService Port 8081 Change Data Directory Yes Data Directory S:\vDCA\RM\FW Store Initial Setting Data Yes (default value) Management Server Hostname Specify the host name of the management server. *1*3 Management Server Port (default value) Database - Hostname localhost (default value) Database - Instance Name FWCMDB (default value) Database - Database Name RM_<VM monitoring server name> *1*2 Database - Authentication Type Database - Password Windows authentication (default value) No (default value) *1 For notes concerning the host names, see "Chapter 13. s (page 117)" *2 Specify the host name of the VM monitoring server. For the cluster configuration, specify the virtual host name of the VM monitoring server (host name by which the floating IP address is resolved). In the configuration examples in this chapter, <VM Monitoring server name> is rm. *3 In the configuration examples in this document, the global management server name is mom due to the cluster configuration. Once installation has finished, restart the system. When restarting the system, use EXPRESSCLUSTER WebManager cluster reboot so that EXPRESSCLUSTER X will not regard it as an abnormal end. When the EXPRESSCLUSTER X screen is activated, close the screen before installing the management server. 5.2 [Active] Setting Up the Services Stops the following services, and then change the [StartupType] to [Manual]. MasterScopeUMF Operations Manager_103 MasterScopeUMF Operations Web Service VDCRMProxy_n The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. 52

69 5.3 [Active]Checking the SQL Server Startup Check that the following services are active. Otherwise start them. SQL Server (FWCMDB) SQL Server Browser 5.4 [Active] Detaching the Database, and Moving and Attaching a Database File Positioning and Modifying the SQL Scripts Edit the SQL scripts required for database clustering. The sample script is stored in <Install DVD>: \script\cluster-pro\rm. After the SQL scripts have been created, place them in the folder in the same path on each of the local disks of the active and standby system hosts. This document provides an example where the script storage location is C:\MSSQL and the database file storage location is S: \MSSQL\Data. Script Value 1 C:\MSSQL\DEACT.sql Used to detach a database file. 2 C:\MSSQL\ACT.sql Used to attach a database file. 3 C:\MSSQL\ACT2.sql Used to re-create a user account. 4 C:\MSSQL\SELECT.sql Used to acquire the SID of an mco database user. 5 C:\MSSQL\RECRTUSR.sql Used to re-create an mco database user. The actual script contents are shown below. If the database storage location (S:\MSSQL and after) differs from that shown here, change the bold-faced fields accordingly. "@Password" is internally used by the components of Virtual DataCenter Automation. Do not change it. DEACT.sql ALTER DATABASE RM_<VM Monitoring server> SET OFFLINE WITH ROLLBACK IMME DIATE EXEC sp_detach_db 'RM_<VM Monitoring server>', TRUE ACT.sql EXEC sp_attach_db 'RM_<VM Monitoring = 'S:\MSSQL\Data\RM_<VM Monitoring = 'S:\MSSQL\Data\RM_<VM Monitoring server>_log.ldf' ACT2.sql Chapter 5. Cluster Configuration of the VM Monitoring Server use RM_<VM Monitoring server> EXEC sp_change_users_login 'Auto_Fix', 'RM_<VM Monitoring server>', NULL, 'RM_<VM Monitoring server>@passw ord' EXEC sp_password NULL, 'RM_<VM Monitoring server>@password', 'RM_<VM Monitoring server>' 53

70 Chapter 5. Cluster Configuration of the VM Monitoring Server SELECT.sql SELECT SUSER_SID('RM_<VM Monitoring server>') RECRTUSR.sql ALTER DATABASE RM_<VM Monitoring server> SET OFFLINE WITH ROLLBACK IMME DIATE EXEC sp_detach_db 'RM_<VM Monitoring server>', TRUE EXEC = N'RM_<VM Monitoring server>' EXEC sp_attach_db 'RM_<VM Monitoring = 'S:\MSSQL\Data\RM_<VM Monitoring = 'S:\MSSQL\Data\RM_<VM Monitoring server>_log.ldf' CREATE LOGIN RM_<VM Monitoring server> WITH PASSWORD = 'RM_<VM Monitoring server>@password', DEFAULT_DATABASE = RM_<VM Monitoring server>, SID = 0x????, CHECK_POLICY = OFF The "SID = 0x????" field needs to be edited in accordance with your environment. Editing is performed in "5.4.6 Acquiring the SID and Modifying an SQL Script (page 55)", so it is not part of the procedure in this section Detaching a Database File Execute a detach process in the active system host in order to move a database file onto the shared disk. Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output Moving a Database File After completion of detach processing, move the database file onto the shared disk. If the instance name FWCMDB is in use, the default value of the path in which the source database file is stored is as follows. C:\Program Files\Microsoft SQL Server\MSSQL12.FWCMDB\MSSQL\DATA File name RM_<VM Monitoring server>.mdf RM_<VM Monitoring server>_log.ldf Destination S:\MSSQL\Data\RM_<VM Monitoring server>.mdf S:\MSSQL\Data\RM_<VM Monitoring server>_log.ldf Attaching the Database Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT.sql /o C:\MSSQL\ACT.log After command execution, view C:\MSSQL\ACT.log to confirm that no error message has been output. 54

71 5.4.5 Re-Creating Database Users Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\ACT2.sql /o C:\MSSQL\ACT2.log After command execution, view C:\MSSQL\ACT2.log to confirm that no error message has been output Acquiring the SID and Modifying an SQL Script Open the command prompt window, and execute the following commands. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \SELECT.sql /o C:\MSSQL\SELECT.log Change <sa_user> and <sa_password> in accordance with your environment. <sa_user> SQL Server administrator user name (sa) <sa_password> SQL Server administrator user password Chapter 5. Cluster Configuration of the VM Monitoring Server After command execution, check the contents of the output log file. This command outputs a hexadecimal number of 32 characters beginning at 0x. Reflect them to the "0x????" field in the script file. SELECT.log Log file name C:\MSSQL\RECRTUSR.sql Destination reflected Detaching the Database Open the command prompt window, and execute the following commands. > osql /E /S localhost\fwcmdb /i C:\MSSQL\DEACT.sql /o C:\MSSQL\DEACT.log After command execution, view C:\MSSQL\DEACT.log to confirm that no error message has been output. 5.5 [Active] Changing the Procedure of Starting an SQL Server Service Stop the following service, and set [Startup type] to [Manual]. SQL Server (FWCMDB) 5.6 Moving to the Standby System In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the standby system. 55

72 Chapter 5. Cluster Configuration of the VM Monitoring Server 5.7 [Standby] Using the Virtual DataCenter Automation Installer for Installation Installs the operation management function in the standby system. Perform the same procedure as the installation into the active system ("5.1 [Active] Using the Virtual DataCenter Automation Installer for Installation (page 51)"), except the following three items: Set the [Store initial setting data] setting to [No]. Specify the same value as the active system in "Database setting - Database name". After installation has finished, do not restart the system. 5.8 [Standby] Setting Up the Services Stops the following services, and change [Startup type] to [Manual]. MasterScopeUMF Operations Manager_103 MasterScopeUMF Operations Web Service VDCRMProxy_n The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. 5.9 [Standby] Copying Data from the Active System Copy the files from the active system host to the standby system host as follows. Copy source (active system) C:\Program Files (x86)\nec\vdca\rm\fw\manager\sg\sysmonmgr.ini C:\Program Files (x86)\nec\vdca\rm\fw\manager\sg\configurationsettin gmgr.ini C:\Program Files (x86)\nec\vdca\rm\fw\manager\sg\wfdbmgr\wfdb.ini C:\MSSQL\DEACT.sql C:\MSSQL\ACT.sql C:\MSSQL\ACT2.sql C:\MSSQL\SELECT.sql C:\MSSQL\RECRTUSR.sql Copy destination (standby system) Same path Same path Same path Same path Same path Same path Same path Same path 56

73 5.10 [Standby] Re-Creating Database Users Re-create a standby system database user. Perform the settings in the following sections by using the SQL scripts copied in "5.9 [Standby] Copying Data from the Active System (page 56)". The <sa_user> and <sa_password> values used in this section need to be changed in accordance with your environment. <sa_user> SQL Server administrator user name (sa) <sa_password> SQL Server administrator user password The result from execution of a command line in this section may show a message as listed below, but this is not a problem. Message 15007, Level 16, Status 1, Server ServerName, Procedure sp_droplogin, Line 26 'mco' is not a valid login or unauthorized Attaching the Database Execute the following two commands to attach the databases. Chapter 5. Cluster Configuration of the VM Monitoring Server > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT.sql /o C:\MSSQL\ACT.log > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \ACT2.sql /o C:\MSSQL\ACT2.log Re-Creating Users Execute the following command to re-create the users. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \RECRTUSR.sql /o C:\MSSQL\RECRTUSR.log Detaching the Database Execute the following command to attach the databases. > osql /U <sa_user> /P <sa_password> /S localhost\fwcmdb /i C:\MSSQL \DEACT.sql /o C:\MSSQL\DEACT.log 5.11 [Standby] Changing the Procedure of Starting an SQL Server Service Stop the following services, and set the [Startup type] to [Manual]. SQL Server (FWCMDB) 57

74 5.12 Moving to the Active System Chapter 5. Cluster Configuration of the VM Monitoring Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system Setting Up the Script Resources Change SQL Server administrator user name and SQL Server administrator user password in the script files start.bat and stop.bat included in this document according to the environment. From the EXPRESSCLUSTER WebManager, add the script files to the failover group as the script resources. File name <Install DVD>:\script\cluster-pro\RM\Start.bat <Install DVD>:\script\cluster-pro\RM\Stop.bat Service starting script Description Service stopping script Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, change to Config Mode, click failover group, and select the [Add] in the [Edit]. 2. On the displayed dialog, change [Type] to [script resurce], and select [Next]. 3. On the displayed dialog, select the [Detail] tab, and click the [Add] button to register the script. 58

75 Chapter 5. Cluster Configuration of the VM Monitoring Server Edit the script (*.bat) accordingly in the following cases. The path of the shared disk is different. The instance name of SQL Server is different. The number at the end of the service name of MasterScope UMF Operations Web Service is different. When being different from a default folder in an installation destination of a VM Monitoring server, please correct a installed path(2 Points) of a service script(start.bat). rem ******************* rem Set Routing rem ******************* call "C:\Program Files (x86)\nec\vdca\mom\fw\manager\bin\nwautomation \nwa_routerestore.bat" 5.14 Saving and Uploading Cluster Information From the EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, the cluster will not operate normally because no configuration information is applied to the active or standby system Suspending the Cluster From the steps to date, the cluster should be left suspended while the shared (or mirror) disk remains invisible. Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, perform the cluster resume and cluster start actions. 2. Ensure the failover group has started with the active system. Then, select the cluster suspend. 59

76 Chapter 5. Cluster Configuration of the VM Monitoring Server 3. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services [Active] Registering License Register the code word of MISSIOM CRITICAL OPERATIONS and SystemManager according to Registering the License to Operation Management Function and Registering Code Word to Operation Management Function in the Virtual DataCenter Automation Installation Guide. Install the VM monitoring server console if it is not installed [Standby] Registering License Register the code word in the operation with regard to the standby node. The license key to register must be the same as that defined in "5.16 [Active] Registering License (page 60)". Use the command line tool for registration. Using the following command to change the current directory before starting the registration. > cd "C:\Program Files (x86)\nec\vdca\rm\fw\manager\bin" 1. Use the following command to list up the registered licenses: > LicenseCmd.exe LIST Acquire the application code from the license information that was output, and apply for the code word. 2. If the license is not registered, register the license key by executing the following command. If the license is already registered, this step is not necessary. Apply for the code word in 3. > LicenseCmd.exe ADD <ProductCode_1> <LicenseKey_1> Output the license list again. 3. The code word can be registered using the following listed commands. > LicenseCmd.exe REGISTER <LicenseKey_1> <Codeword_1> Enter <ProductCode_n>, <LicenseKey_n>, <Codeword_n> according to the license information. 60

77 5.18 [Active] Default Setting of the VM Monitoring Server As a default setting of the VM monitoring server, Default Settings of Operation Management Function, Linkage setting between Management Server and Deleting scenario settings in the Virtual DataCenter Automation Installation Guide Setting the Service Governor Revise the setting according to Setting up the Property File for the Service Governor in the Virtual DataCenter Automation Installation Guide Resuming the Cluster Resume From the EXPRESSCLUSTER WebManager, resume the cluster. Chapter 5. Cluster Configuration of the VM Monitoring Server 5.21 Rebooting the Cluster From the EXPRESSCLUSTER WebManager, reboot the cluster. After rebooting the cluster, move the failover group to verify that neither the active nor standby system causes any error. 61

78 Chapter 6. Cluster Configuration for an ID Management Server Chapter 6. Cluster Configuration for an ID Management Server Contents 6.1 Assumption [Active] Installing the MasterScope Identity Manager [Active] Setting Up MasterScope Identity Manager Moving to the Standby System [Standby] Installing MasterScope Identity Manager [Standby] Setting Up MasterScope Identity Manager Moving to the Active System Setting Up the Registry Synchronous Resources Setting Up the Script Resources Setting Up Service Resources Setting Up the Monitor Resources Saving and Uploading Cluster Information Suspending the Cluster Resuming the Cluster Rebooting the Cluster Cautions

79 6.1 Assumption The procedures in this chapter must be performed when using the ID management server in a cluster configuration in Virtual DataCenter Automation. It is also assumed that the same one-way standby configuration as the description in "1.2 Configuration (page 2)" is used for the ID management server. Before starting the procedures in this chapter, perform the procedures in "2.1 Installing Windows Server (page 6)", "2.2 Setting Up the Shared and Mirror Disks (page 6)", and "2.3 Installing EXPRESSCLUSTER X (page 6)" in "Chapter 2. Preparation (page 5)". All procedures in subsequent sections must be performed after the failover group created during preparation has been switched so that the shared (or mirror) disk can be accessed from the active system. In this document, the following IP addresses are set for the respective nodes. Active server: , sm1 Standby server: , sm2 Floating IP: , sm Chapter 6. Cluster Configuration for an ID Management Server The S: drive is used for the shared disk of the active and standby servers. It is assumed that the procedures in the sections below will be performed in the order described. [Active] and [Standby] represent the systems in which to perform the procedures described in this section. 63

80 6.2 [Active] Installing the MasterScope Identity Manager Installation Using the Virtual DataCenter Automation Integrated Installer, install the MasterScope Identity Manager. Hereafter, it is assumed that the installation directory of MasterScope Identity Manager is: C: \Program Files (x86)\nec\vdca\sm\securemaster Changing the Service Start Setting Select [Start] - [All Programs] - [MasterScope Identity Manager] - [stop WEB_SERVER_TOMCAT]. Stop the following services. Apache Tomcat ForEIM EDS Manager Change [Startup type] to [Manual] for the following services. If the setting is already [Manual], there is no need to change the setting. Apache Tomcat ForEIM EDS Protocol Server Setting the System Environment Variable Chapter 6. Cluster Configuration for an ID Management Server Select [Start] - [Control Panel] - [System and Security] - [System] and add the following two system environment variables from [Advanced system settings] window. If the shared disk is the S drive, the directories are as follows. System environment variable name EDS_REPLICA_LAST EDS_FOR_CLUSTER Value S:\SECUREMASTER\EDS\log\.replicad.last ON 6.3 [Active] Setting Up MasterScope Identity Manager Perform the following procedures for the active system machines. Before starting these procedures, make sure that the following services have been stopped. If they have not been stopped, stop them. Apache Tomcat ForEIM EDS Manager Changing the Database Directory and Log Directory Create the following two directories. 64

81 S:\SECUREMASTER\EDS\ S:\SECUREMASTER\EIDM\ Move the directory from local disk to shared disk as follows. Chapter 6. Cluster Configuration for an ID Management Server Source (local disk) C:\Program Files (x86)\nec\vdca\sm\securemaster\eds\edsdb C:\Program Files (x86)\nec\vdca\sm\securemaster\eds\log C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm\data C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm\log Destination (shared disk) S:\SECUREMASTER\EDS\ EDSDB S:\SECUREMASTER\EDS\ LOG S:\SECUREMASTER\EIDM \DATA S:\SECUREMASTER\EIDM \LOG Execute the following command from the command prompt and create the symbolic link. > cd /d "C:\Program Files (x86)\nec\vdca\sm\securemaster\eds" > mklink /D EDSDB S:\SECUREMASTER\EDS\EDSDB > mklink /D LOG S:\SECUREMASTER\EDS\LOG > cd /d "C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm" > mklink /D DATA S:\SECUREMASTER\EIDM\DATA > mklink /D LOG S:\SECUREMASTER\EIDM\LOG Changing the Control File Move the file from local disk to shared disk as follows. When the source file does not exist, there is no need to move the file. Source (local disk) C:\Windows\EDS\.replicad.last C:\Windows\EDS\.replicad.last_backup C:\Windows\EDS\.dbsaveflush.last C:\Windows\EDS\.dbsaveflush.last_backup Destination (shared disk) S:\SECUREMASTER\EDS\log\.replicad.last S:\SECUREMASTER\EDS\log\.replicad.last_bac kup S:\SECUREMASTER\EDS\log\.dbsaveflush.last S:\SECUREMASTER\EDS\log\.dbsaveflush.last_ backup Execute the following command from the command prompt and create the symbolic link. > cd /d C:\Windows\EDS > mklink ".replicad.last" "S:\SECUREMASTER\EDS\log\.replicad.last" > mklink ".replicad.last_backup" "S:\SECUREMASTER\EDS\log \.replicad.last_backup" > mklink ".dbsaveflush.last" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last" > mklink ".dbsaveflush.last_backup" "S:\SECUREMASTER\EDS\log \.dbsaveflush.last_backup" 65

82 6.4 Moving to the Standby System Chapter 6. Cluster Configuration for an ID Management Server In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the standby system. 6.5 [Standby] Installing MasterScope Identity Manager For the standby system, install MasterScope Identity Manager according to the same procedures as "6.2 [Active] Installing the MasterScope Identity Manager (page 64)". 6.6 [Standby] Setting Up MasterScope Identity Manager Perform the following procedures for the standby system machines. Before starting the following procedures, make sure that the following services have been stopped. If they have not been stopped, stop them. Apache Tomcat ForEIM EDS Manager Changing the Database Directory and Log Directory Delete the following directories. Deletion directory (local disk) C:\Program Files (x86)\nec\vdca\sm\securemaster\eds\edsdb C:\Program Files (x86)\nec\vdca\sm\securemaster\eds\log C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm\data C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm\log Execute the following command from the command prompt and create the symbolic link. > cd /d "C:\Program Files (x86)\nec\vdca\sm\securemaster\eds" > mklink /D EDSDB S:\SECUREMASTER\EDS\EDSDB > mklink /D LOG S:\SECUREMASTER\EDS\LOG > cd /d "C:\Program Files (x86)\nec\vdca\sm\securemaster\eidm" > mklink /D DATA S:\SECUREMASTER\EIDM\DATA > mklink /D LOG S:\SECUREMASTER\EIDM\LOG Changing the Control File Delete the following file. If a deletion source file does not exist, there is no need to delete the file. 66

83 Chapter 6. Cluster Configuration for an ID Management Server Files to Delete (Local Disk) C:\Windows\EDS\.replicad.last C:\Windows\EDS\.replicad.last_backup C:\Windows\EDS\.dbsaveflush.last C:\Windows\EDS\.dbsaveflush.last_backup Execute the following command from the command prompt and create the symbolic link. > cd /d C:\Windows\EDS > mklink ".replicad.last" "S:\SECUREMASTER\EDS\log\.replicad.last" > mklink ".replicad.last_backup" "S:\SECUREMASTER\EDS\log \.replicad.last_backup" > mklink ".dbsaveflush.last" "S:\SECUREMASTER\EDS\log\.dbsaveflush.last" > mklink ".dbsaveflush.last_backup" "S:\SECUREMASTER\EDS\log \.dbsaveflush.last_backup" 6.7 Moving to the Active System In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system. 6.8 Setting Up the Registry Synchronous Resources Register the registry synchronous resources to the failover group from EXPRESSCLUSTER WebManager. The following two registries are the registries to register. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\NEC\PERCIO HKEY_USERS\.DEFAULT\Software\NEC\PERCIO\client 6.9 Setting Up the Script Resources From EXPRESSCLUSTER WebManager, add the script files "start.bat" and "stop.bat" included in this document to the failover group as the script resources. Table 6-1 When not replicating File name cluster-pro\securemaster\no_replica\start.bat cluster-pro\securemaster\no_replica\stop.bat Description Service starting script Service stopping script 67

84 Chapter 6. Cluster Configuration for an ID Management Server Table 6-2 When replicating File name cluster-pro\securemaster\replica\start.bat cluster-pro\securemaster\replica\stop.bat Description Service starting script Service stopping script 6.10 Setting Up Service Resources Register the service resources to the failover group from EXPRESSCLUSTER WebManager. The following service is registered. Apache Tomcat ForEIM 6.11 Setting Up the Monitor Resources Register the following monitor resources used for service monitoring from EXPRESSCLUSTER WebManager. Type Monitor timing Property Monitored resources Interval Time out Number of retries 1 Wait time until start of monitoring Recovery Action Recovery Target service (service monitoring) In activation Value The service resources set in "6.10 Setting Up Service Resources (page 68)". 60 seconds 60 seconds 0 second Executing failover to the recovery target failover group Copy the following script file included in this document to C:\Program Files (x86)\nec\vdca\sm \SECUREMASTER\EDS\bin of the active system and standby system machines. Table 6-4 When not replicating File name cluster-pro\securemaster\no_replica\eds_watch.bat Description Service monitoring script Table 6-5 When replicating File name cluster-pro\securemaster\replica\eds_watch.bat Description Service monitoring script 6.12 Saving and Uploading Cluster Information From the EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. 68

85 Chapter 6. Cluster Configuration for an ID Management Server If the upload is skipped, the cluster will not operate normally because no configuration information is applied to the active or standby system Suspending the Cluster From the steps to date, the cluster should be left suspended while the shared (or mirror) disk remains invisible. Perform the following actions. 1. From the EXPRESSCLUSTER WebManager, perform the cluster resume and cluster start actions. 2. Ensure the failover group has started with the active system. Then, suspend the cluster. 3. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services Resuming the Cluster From the EXPRESSCLUSTER WebManager, resume the cluster Rebooting the Cluster From the EXPRESSCLUSTER WebManager, reboot the cluster. 69

86 After rebooting the cluster, move the failover group to verify that neither the active nor standby system causes any error Cautions Actions to take when a failover occurs If a failover occurs due to an abnormal EDS Protocol Server service, the EDS Protocol Server service of the machine might not stop completely. If a failover occurs again and the cluster group is moved under the above conditions, the incompletely stopped machine cannot start the EDS Protocol Server service correctly. Take the following actions for the machines when a failover occurs. 1. Eliminate the cause of the failover. 2. Restart the machine by using cluster shutdown. (The machine then enters the "restart after shutdown" state.) 3. Select the server in the "condition of restart after shutdown" from EXPRESSCLUSTER WebManager and execute sever recovery to recover the server in the cluster Stopping the EDS Protocol Server service It may be necessary to restart or stop the EDS Protocol Server to change the environment configuration of the EDS Protocol Server or to initialize the database. In this case, stop EXPRESSCLUSTER monitoring once according to the following procedure, and then restart or stop the EDS Protocol Server. For details of the ARMLOADC command, see the EXPRESSCLUSTER documentation. 1. Enter the following command from the command prompt window of the machine whose failover group was activated due to stoppage of the operating monitor function > ARMLOADC EDS_WATCH /W pause * "EDS_WATCH" is the monitoring ID specified in the startup script. 2. Stop the EDS Manager service. 3. Change the environment configuration or initialize the database. 4. Start the EDS Protocol Server service. 5. To resume the monitoring, enter the following command from the command prompt window. > ARMLOADC EDS_WATCH /W continue When stopping Tomcat If the workflow setting is changed, it may be necessary to restart or stop Tomcat. In this case, stop the monitoring of the HTTP service according to the following procedure, and then restart or stop Tomcat. 1. Stop the monitoring of the HTTP service 2. Stop the Apatch Tomcat ForEIM service. 3. Start the Apatch Tomcat ForEIM service. 4. Restart the monitoring of the HTTP service. Chapter 6. Cluster Configuration for an ID Management Server 70

87 Chapter 7. Cluster Configuration for a Management Agent Chapter 7. Cluster Configuration for a Management Agent Contents 7.1 Assumption Installing the Management Agent [Active] Setting up the Data Area Folder of the Management Agent Moving to the Standby System [Standby] Setting up the Data Area Folder of the Management Agent Moving to the Active System [Active] Configuring Management Agent

88 7.1 Assumption The procedures in this chapter must be performed when using the management agent server in a cluster configuration in Virtual DataCenter Automation. It is also assumed that the same one-way standby configuration as the description in "1.2 Configuration (page 2)" is used for the management agent. Before starting the procedure in this chapter, perform the procedures in "2.1 Installing Windows Server (page 6)", "2.2 Setting Up the Shared and Mirror Disks (page 6)", and "2.3 Installing EXPRESSCLUSTER X (page 6)" in the "Chapter 2. Preparation (page 5)". All procedures in subsequent sections must be performed after the failover group created during preparation has been switched so that the shared (or mirror) disk can be accessed from the active system. 7.2 Installing the Management Agent Perform cluster configuration for the management agent for the active and standb systems according to 2.13 Installing the components of Management Agent in the Virtual DataCenter Automation Installation Guide. The components installed are as follows. Chapter 7. Cluster Configuration for a Management Agent Product name MasterScope MISSION CRITICAL OPERATIONS Agent Type The [Choose Components] dialog box is displayed. Select all of the above components. Next, enter setting values for "MasterScope MISSION CRITICAL OPERATIONS" on the [Product Installation Settings] dialog box. For details about the meaning of each setting item, see 2.13 Installing the components of Management Agent in the Virtual DataCenter Automation Installation Guide. For notes concerning the self host name and manager host name, see "Chapter 13. s (page 117)". When restarting the system, use WebManager cluster reboot so that EXPRESSCLUSTER X will not regard it as an abnormal end. When the EXPRESSCLUSTER X screen is activated, close the screen before installing the management server. 7.3 [Active] Setting up the Data Area Folder of the Management Agent Set up a data area folder as the shared disk for the active and standby servers. In the description below, the S:drive is used for the shared disk of the active and standby servers. 1. Stop the services of the management agent. 72

89 Stop the service below manually. MasterScope UMF Operations Agent_n The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. 2. Copy the data area folder of the management agent to the shared disk. Open the command prompt window, and execute the following commands. > xcopy /I "C:\Program Files (x86)\nec\umf\operations\agent\sg \invmcodc" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC" 3. Delete the data area folder of the management agent in the installation folder. Open the command prompt window, and execute the following commands. > rmdir /S /Q "C:\Program Files (x86)\nec\umf\operations\agent\sg \invmcodc" 4. Create a link to the data area folder in the shared disk. Chapter 7. Cluster Configuration for a Management Agent Open the command prompt window, and execute the following commands. > mklink /J "C:\Program Files (x86)\nec\umf\operations\agent\sg \invmcodc" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC" 7.4 Moving to the Standby System In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the standby system. 7.5 [Standby] Setting up the Data Area Folder of the Management Agent Set up a data area folder as the shared disk for the active and standby servers. In the description below, the S:drive is used for the shared disk of the active and standby servers. 1. Stop the services of the management agent. Stop the service below manually. MasterScope UMF Operations Agent_n 73

90 The "n" at the end should be 1 or a greater number. The number varies depending on the installation environment. 2. Delete the data area folder of the management agent in the installation folder. Open the command prompt window, and execute the following commands. > rmdir /S /Q "C:\Program Files (x86)\nec\umf\operations\agent\sg \invmcodc" 3. Create a link to the data area folder in the shared disk. Chapter 7. Cluster Configuration for a Management Agent Open the command prompt window, and execute the following commands. > mklink /J "C:\Program Files (x86)\nec\umf\operations\agent\sg \invmcodc" "S:\vDCA\Agt\FW\Agent\sg\iNvmCODC" 7.6 Moving to the Active System In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system. 7.7 [Active] Configuring Management Agent Install the agent according to the procedure in 2.17 Registering and Setting up the Management Agent in Virtual DataCenter Automation Installation Guide. The path of the configuration file is under the "Data Directory" configured during installation. 74

91 Chapter 8. Cluster Configuration for a Database Server Chapter 8. Cluster Configuration for a Database Server The procedures in this chapter must be performed only when using the database server in a cluster configuration. Perform the installation according to the procedures for configuring a cluster for the database server. 75

92 Chapter 9. Upgrading the Cluster Environment Chapter 9. Upgrading the Cluster Environment This chapter describes the upgrade procedure in the cluster environment. In the following sections, it is assumed that the cluster is operating in the active system. Contents 9.1 Upgrading the Global Management Server Upgrading the Management Server Upgrading the VM Monitoring Server Upgrading the ID Management Server Upgrading the Management Agent

93 9.1 Upgrading the Global Management Server After upgrading the global management server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 4.2 Upgrading the Global Management Server Console in the Virtual DataCenter Automation Installation Guide. <Install folder> is the installation destination folder of Global Management Server. The default value of the installation folder is "C:\Program Files (x86)\nec\vdca\gm" Suspending the cluster To stop process monitoring that is running, suspend the cluster. Chapter 9. Upgrading the Cluster Environment 1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster [Active] Stopping the service Stop the following services. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. In a version earlier than Version 2.2, execute the following command. > otxadmin stop-domain --force --wait_timeout 180 domain1 > otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin In Version 2.2 or later, stop the following service. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. Apache Tomcat 8.0 ServiceGovernor [Active] Backup of the service governor This step is not necessary when updating the version from Version 2.2 or later. Back up the configuration file. Back up the following file in any location. For non-cluster: 77

94 - <Install folder>\fw\webotx\domains\domain1\config\vdcplugins - <Install folder>\fw\webotx\domains\domain1\config\vdcapi.properties - <Install folder>\fw\webotx\domains\domain1\vdcapikey.jks For cluster: - S:\vDCA\domains\domain1\config\vdcplugins - S:\vDCA\domains\domain1\config\vdcapi.properties - S:\vDCA\domains\domain1\vDCApiKey.jks [Active] Upgrading the global management server Upgrade the server according to the procedure in Upgrading the global management server in the Virtual DataCenter Automation Installation Guide [Active] Updating the database 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Copy the database configuration script. Chapter 9. Upgrading the Cluster Environment Copy source <Install DVD>:\fw\Windows\Tools\sql_rupdate Copy destination <Install folder>\fw\manager\sql_rupdate 3. Execute the following command to updating the database. > cd <Install folder>\fw\manager\sql_rupdate\sqlserver > WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance Name> <Database Driver Name> Tip Do not insert a line feed in the command. If a space is included in the value, enclose it in double quotation marks ("). Confirm the value of DATABASE_NAME, SERVER_NAME, SQL_INSTANCE_NAME and DATABASE_DRIVER where the <Database Name>, <Server Name>, <Instance Name> and <Database Driver Name> was indicated on following file. <Install folder>\fw\manager\sg\wfdbmgr\wfdb.ini 4. When the execution log is output to the execution folder after the command is executed, make sure that there is no error. (Any error indicating that the user, role, database, or schema already exists is not a problem.) [Active] Switching back the Service Governor Setup Overwrite the files that were backed up in any location in the procedure in "9.1.3 [Active] Backup of the service governor (page 77)". <Install folder>\fw\tomcat\conf\vdcplugins <Install folder>\fw\tomcat\conf\vdcapi.properties <Install folder>\fw\tomcat\vdcapikey.jks 78

95 9.1.7 [Active] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. If registered the EXPRESSCLUSTER task manager, You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor [Standby] Upgrading the global management server Upgrade the global management server in the standby system. Perform the same procedure as the upgrading the active system Upgrading the global management server in the Virtual DataCenter Automation Installation Guide, except as follows. Set the [Update the Data Directory at startup] setting to [No] [Standby] Switching back the Service Governor Setup Switching back the service governor according to the procedure in "9.1.6 [Active] Switching back the Service Governor Setup (page 78)" [Standby] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor Setting up the Script Resource This step is not necessary when updating the version from Version 2.2 or later. Chapter 9. Upgrading the Cluster Environment 1. Change into the setting mode from EXPRESSCLUSTER WebManager, click the failover group name, select [script] from the [Resources] tab, and then select [Property] from the [Edit] menu. 79

96 Chapter 9. Upgrading the Cluster Environment 2. Select [start.bat] from the displayed dialog box, and then select [Edit]. call otxadmin start-domain WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armload service_bundleapserver /S /WAIT 180 /M /FOV "ServiceGovernor" 3. Select [stop.bat] from the displayed dialog box, and then select [Edit]. call otxadmin stop-domain --force --wait_timeout 180 domain1 call otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armkill service_bundleapserver After changing the settings, click [Apply] and then click [OK] Saving and Uploading Cluster Information This step is not necessary when updating the version from Version 2.2 or later. From EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. 80

97 Chapter 9. Upgrading the Cluster Environment If the upload is skipped, no configuration information is applied to the active or standby system Setting up the Service Governor Perform the procedure in Setting up the Service Governor in Virtual DataCenter Automation Installation Guide Perform the procedures 1 to 5. in both manners of [Active] and [Standby] [Active] Starting the service Start the following services. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. In a version earlier than Version 2.2, execute the following command. > armload service_bundleapserver /S /WAIT 180 /M /FOV "ServiceGovernor" In Version 2.2 or later, start the following service. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. Apache Tomcat 8.0 ServiceGovernor Resuming the cluster 1. From EXPRESSCLUSTER WebManager, resume the cluster. 2. After starting, move the failover group to verify that neither the active nor standby system causes any error. 81

98 Applying the standard workflow template Workflow templates are not updated in overwrite installation. Import workflow templates by referring to Applying the standard workflow template in the Virtual DataCenter Automation Installation Guide Editing Trace Log Settings of Resource Management Function Refer to Editing Trace Log Settings of Resource Management Function of Virtual DataCenter Automation Installation Guide and edit trace log settings of resource management function. 9.2 Upgrading the Management Server After upgrading the management server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 4.4 Upgrading the Management Server Console in the Virtual DataCenter Automation Installation Guide. <Install folder> is the installation destination folder of Management Server. The default value of the installation folder is "C:\Program Files (x86)\nec\vdca\mom" Suspending the cluster To stop process monitoring that is running, suspend the cluster. Chapter 9. Upgrading the Cluster Environment 1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster [Active] Stopping the service Stop the following services. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. Stop the services in the following order. MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. NvPRO ResourceManagerAPI Service NvPRO Base Manager MasterScope UMF Operations Manager_102 82

99 Chapter 9. Upgrading the Cluster Environment FTBase service [Active] Upgrading the management server Upgrade the server according to the procedure in Upgrading the Management Server in the Virtual DataCenter Automation Installation Guide [Active] Updating the database 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Copy the database configuration script. Copy source <Install DVD>:\fw\Windows\Tools\sql_rupdate Copy destination <Install folder>\fw\manager\sql_rupdate 3. Execute the following command to updating the database. > cd <Install folder>\fw\manager\sql_rupdate\sqlserver > WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance Name> <Database Driver Name> Tip Do not insert a line feed in the command. If a space is included in the value, enclose it in double quotation marks ("). Confirm the value of DATABASE_NAME, SERVER_NAME, SQL_INSTANCE_NAME and DATABASE_DRIVER where the <Database Name>, <Server Name>, <Instance Name> and <Database Driver Name> was indicated on following file. <Install folder>\fw\manager\sg\wfdbmgr\wfdb.ini 4. When the execution log is output to the execution folder after the command is executed, make sure that there is no error. (Any error indicating that the user, role, database, or schema already exists is not a problem.) [Active] Stopping the service Stop the following services. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. FTBase service MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Standby] Upgrading the management server Upgrade the management server in the standby system. Perform the same procedure as the upgrading the active system Upgrading the Management Server in the Virtual DataCenter Automation Installation Guide. 83

100 9.2.7 [Standby] Stopping the service Stop the services below manually. FTBase service MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Active] Starting the service Start the following services. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. FTBase service MasterScope UMF Operations Manager_102 NvPRO Base Manager NvPRO ResourceManagerAPI Service MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment Resuming the cluster 1. From EXPRESSCLUSTER WebManager, resume the cluster. Chapter 9. Upgrading the Cluster Environment Upgrading the SigmaSystemCenter Refer to the following procedure manual (Japanese version only) and upgrade SigmaSystemCenter. Paraphrase a SigmaSystemCenter Installer in the procedure manual "<Install DVD>:\ManagerSet up.exe" as the Installer [SigmaSystemCenter Manager] or [SigmaSystemCenter Manager (the cluster environment For stand by system upgrades)] which starts from a custom mode of Virtual DataCenter Automation integration installer. Confirm that an installation folder of a component is the same as before the upgrade installation. 84

101 Applying the standard workflow template Workflow templates are not updated in overwrite installation. Import workflow templates by referring to Applying the standard workflow template in the Virtual DataCenter Automation Installation Guide. 9.3 Upgrading the VM Monitoring Server After upgrading the VM monitoring server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 4.6 Upgrading the VM Monitoring Server Console in the Virtual DataCenter Automation Installation Guide. <Install folder> is the installation destination folder of VM Monitoring Server. The default value of the installation folder is "C:\Program Files (x86)\nec\vdca\rm" Suspending the cluster To stop process monitoring that is running, suspend the cluster. Chapter 9. Upgrading the Cluster Environment 1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster [Active] Stopping the service Stop the following services. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_103 MasterScope UMF Operations Web Service vdcrmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Active] Upgrading the VM monitoring server Upgrade the server according to the procedure in Upgrading the VM Monitoring Server in the Virtual DataCenter Automation Installation Guide [Active] Updating the database 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Copy the database configuration script. 85

102 Chapter 9. Upgrading the Cluster Environment Copy source <Install DVD>:\fw\Windows\Tools\sql_rupdate Copy destination <Install folder>\fw\manager\sql_rupdate 3. Execute the following command to updating the database. > cd <Install folder>\fw\manager\sql_rupdate\sqlserver > WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance Name> <Database Driver Name> Tip Do not insert a line feed in the command. If a space is included in the value, enclose it in double quotation marks ("). Confirm the value of DATABASE_NAME, SERVER_NAME, SQL_INSTANCE_NAME and DATABASE_DRIVER where the <Database Name>, <Server Name>, <Instance Name> and <Database Driver Name> was indicated on following file. <Install folder>\fw\manager\sg\wfdbmgr\wfdb.ini 4. When the execution log is output to the execution folder after the command is executed, make sure that there is no error. (Any error indicating that the user, role, database, or schema already exists is not a problem.) [Standby] Upgrading the VM monitoring server Upgrade the VM monitoring server in the standby system. Perform the same procedure as the upgrading the active system Upgrading the VM Monitoring Server in the Virtual DataCenter Automation Installation Guide [Standby] Stopping the service Stop the service below manually. MasterScope UMF Operations Web Service vdcrmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Active] Starting the service Start the following services. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_103 MasterScope UMF Operations Web Service vdcrmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment Resuming the cluster 1. From EXPRESSCLUSTER WebManager, resume the cluster. 86

103 Chapter 9. Upgrading the Cluster Environment 2. After starting, move the failover group to verify that neither the active nor standby system causes any error. 9.4 Upgrading the ID Management Server This section describes the upgrading procedure for the ID management server MasterScope Identity Manager in the cluster environment. The procedure in this section assumes the cluster environment of the ID management server is built according to the procedure in "Chapter 6. Cluster Configuration for an ID Management Server (page 62)". Upgrading of the ID management server MasterScope Identity Manager does not support installation by overwriting. Extraction of the existing data, uninstallation of the current version ID management server, installation of the new version ID management server, and reflection of the existing data are performed in this order [Active] Extracting the existing data Perform the procedure of Extracting the existing data in the Virtual DataCenter Automation Installation Guide in the active system Uninstalling MasterScope Identity Manager on the ID Management Server 1. Stop the failover group in the active system. From EXPRESSCLUSTER WebManager, perform operations to stop the failover group. 2. Deleting the Monitor Resources From EXPRESSCLUSTER WebManager, delete the script resources registered in "6.11 Setting Up the Monitor Resources (page 68)". 3. Deleting the Service Resources From EXPRESSCLUSTER WebManager, delete the script resources registered in "6.10 Setting Up Service Resources (page 68)". 4. Deleting the Script Resources 87

104 From EXPRESSCLUSTER WebManager, delete the script resources registered in "6.9 Setting Up the Script Resources (page 67)". 5. Deleting the Registry Synchronous Resources From EXPRESSCLUSTER WebManager, delete the script resources registered in "6.8 Setting Up the Registry Synchronous Resources (page 67)". 6. Saving and Uploading Cluster Information Chapter 9. Upgrading the Cluster Environment From EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, no configuration information is applied to the active or standby system. 7. [Standby] Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the standby system. a. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standby system on the "Select Server" dialog. b. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the standby system on the "Select Server" dialog. 8. [Standby] Uninstalling MasterScope Identity Manager on the ID Management Server Perform the procedure in Uninstalling the components of ID Management Server in the Virtual DataCenter Automation Installation Guide in the standby system. 9. [Standby] Stopping the disk resource and floating IP resource Stop the disk resource and floating IP resource in the standby system. a. From EXPRESSCLUSTER WebManager, stop the disk resource. Select the standby system on the "Select Server" dialog. b. From EXPRESSCLUSTER WebManager, stop the floating IP resource. Select the standby system on the "Select Server" dialog. 10. [Active] Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the active system. a. From EXPRESSCLUSTER WebManager, start the disk resource. Select the active system on the "Select Server" dialog. b. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the active system on the "Select Server" dialog. 11. [Active] Uninstalling MasterScope Identity Manager on the ID Management Server Perform the procedure in Uninstalling ID Management Server in the Virtual DataCenter Automation Installation Guide in the active system. 12. Deleting the Shared Disk Data 88

105 Delete the shared disk directories created in "6.3.1 Changing the Database Directory and Log Directory (page 64)" in the active system. If the shared disk is the S drive, the directories are as follows. S:\SECUREMASTER 13. [Active] Stopping the disk resource and floating IP resource Stop the disk resource and floating IP resource in the active system. a. From EXPRESSCLUSTER WebManager, stop the disk resource. Select the active system on the "Select Server" dialog. b. From EXPRESSCLUSTER WebManager, stop the floating IP resource. Select the active system on the "Select Server" dialog. 14. Rebooting the Cluster From EXPRESSCLUSTER WebManager, reboot the cluster. Chapter 9. Upgrading the Cluster Environment Cluster configuration for an ID management server Perform the procedure described in "Chapter 6. Cluster Configuration for an ID Management Server (page 62)" [Active] Reflecting the existing data Perform the procedure of Reflecting the existing Data in the Virtual DataCenter Automation Installation Guide in the active system. After starting, move the failover group to verify that neither the active nor standby system causes any error. 9.5 Upgrading the Management Agent Stopping the failover group Stop the failover group in the active system. 1. From EXPRESSCLUSTER WebManager, perform operations to stop the failover group Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the active system. 89

106 1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the active system on the "Select Server" dialog. 2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the active system on the "Select Server" dialog [Active] Stopping the service Stop the service below manually. MasterScope UMF Operations Agent_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Active] Upgrading the management agent Perform the procedure described in "7.2 Installing the Management Agent (page 72)". No input of setting values is required. On the "Product Installation Setting" screen, check that [Up] is assigned to the selected product name when installing [Active] Starting the service Start the service below manually. MasterScope UMF Operations Agent_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment Stopping the disk resource and floating IP resource Stop the disk resource in the active system. 1. From EXPRESSCLUSTER WebManager, stop the disk resource. 2. From EXPRESSCLUSTER WebManager, stop the floating IP resource Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the standby system. 1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standby system on the "Select Server" dialog. 2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the standby system on the "Select Server" dialog [Standby] Stopping the service Stop the service below manually. MasterScope UMF Operations Agent_n Chapter 9. Upgrading the Cluster Environment 90

107 The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Standby] Upgrading the management agent Perform the procedure described in "7.2 Installing the Management Agent (page 72)". No input of setting values is required. On the "Product Installation Setting" screen, check that [Up] is assigned to the selected product name when installing [Standby] Starting the service Start the service below manually. MasterScope UMF Operations Agent_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment Stopping the disk resource and floating IP resource Stop the disk resource in the standby system. 1. From EXPRESSCLUSTER WebManager, stop the disk resource. 2. From EXPRESSCLUSTER WebManager, stop the floating IP resource Starting the failover group Chapter 9. Upgrading the Cluster Environment From EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select the active system on the "Select Server" dialog. 91

108 Chapter 10. Rolling update in the cluster environment Chapter 10. Rolling update in the cluster environment This chapter describes the rolling update procedure in the cluster environment. In the following sections, it is assumed that the cluster is operating in the active system. Contents 10.1 Rolling update the Global Management Server

109 Rolling update is a method of upgrading the cluster configuration. The standby node is upgraded while the cluster package is working. The cluster package is moved to the standby node after the completion of the upgrade. The shared disk is updated at service startup in the original standby node that has switched to the active node. Automation of the shared disk update allows upgrade with the minimum stop of the cluster package. A rolling update can be used to update the version of the global management server Rolling update the Global Management Server After rolling update the global management server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 4.2 Upgrading the Global Management Server Console in the Virtual DataCenter Automation Installation Guide. <Install folder> is the installation destination folder of Global Management Server. The default value of the installation folder is "C:\Program Files (x86)\nec\vdca\gm" [Active] Updating the database 1. Insert the vdca/nwa install DVD into the DVD drive. 2. Copy the database configuration script. Chapter 10. Rolling update in the cluster environment Copy source <Install DVD>:\fw\Windows\Tools\sql_rupdate Copy destination <Install folder>\fw\manager\sql_rupdate 3. Execute the following command to updating the database. > cd <Install folder>\fw\manager\sql_rupdate\sqlserver > WfdbCmdbSetup.bat <Database Name> <Server Name> <Instance Name> <Database Driver Name> Tip Do not insert a line feed in the command. If a space is included in the value, enclose it in double quotation marks ("). Confirm the value of DATABASE_NAME, SERVER_NAME, SQL_INSTANCE_NAME and DATABASE_DRIVER where the <Database Name>, <Server Name>, <Instance Name> and <Database Driver Name> was indicated on following file. <Install folder>\fw\manager\sg\wfdbmgr\wfdb.ini 4. When the execution log is output to the execution folder after the command is executed, make sure that there is no error. (Any error indicating that the user, role, database, or schema already exists is not a problem.) [Active] Backup of the service governor This step is not necessary when updating the version from Version 2.2 or later. Back up the configuration file. Back up the following file in any location. For non-cluster: 93

110 - <Install folder>\fw\webotx\domains\domain1\config\vdcplugins - <Install folder>\fw\webotx\domains\domain1\config\vdcapi.properties - <Install folder>\fw\webotx\domains\domain1\vdcapikey.jks For cluster: - S:\vDCA\domains\domain1\config\vdcplugins - S:\vDCA\domains\domain1\config\vdcapi.properties - S:\vDCA\domains\domain1\vDCApiKey.jks [Standby] Upgrading the global management server Upgrade the global management server in the standby system. Perform the same procedure as the upgrading the active system Upgrading the global management server in the Virtual DataCenter Automation Installation Guide, except as follows. Set the [Update the Data Directory at startup] setting to [Yes] [Standby] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor [Standby] Switching back the Service Governor Setup Overwrite the files that were backed up in any location in the procedure in " [Active] Backup of the service governor (page 93)". <Install folder>\fw\tomcat\conf\vdcplugins <Install folder>\fw\tomcat\conf\vdcapi.properties <Install folder>\fw\tomcat\vdcapikey.jks Stopping the failover group Stop the failover group in the active system. Chapter 10. Rolling update in the cluster environment 1. From EXPRESSCLUSTER WebManager, perform operations to stop the failover group. 94

111 Setting up the Script Resource This step is not necessary when updating the version from Version 2.2 or later. Chapter 10. Rolling update in the cluster environment 1. Change into the setting mode from EXPRESSCLUSTER WebManager, click the failover group name, select [script] from the [Resources] tab, and then select [Property] from the [Edit] menu. 2. Select [start.bat] from the displayed dialog box, and then select [Edit]. call otxadmin start-domain WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armload service_bundleapserver /S /WAIT 180 /M /FOV "ServiceGovernor" 3. Select [stop.bat] from the displayed dialog box, and then select [Edit]. call otxadmin stop-domain --force --wait_timeout 180 domain1 call otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armkill service_bundleapserver 95

112 After changing the settings, click [Apply] and then click [OK] Saving and Uploading Cluster Information This step is not necessary when updating the version from Version 2.2 or later. Chapter 10. Rolling update in the cluster environment From EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, no configuration information is applied to the active or standby system Starting the failover group Stop the following service in the standby system. SQL Server Browser From EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select the standby system on the "Select Server" dialog. Check that no error occurred when the shared disk update command updated the version of the standby system. The path of the shared disk update command log file is <Install folder>\fw\manager\log \RupInstCmd.log. The value of ExitCode at the end of the log file of the shared disk update command indicates the exit code. In the following example, the exit code is /04/26 12:32:48.356,4144,INF,RupInstCmd_Main,----- Rolling Update Start /04/26 12:32:48.356,4144,INF,RupInstCmd_Main,UpdateData path=c:\progra m Files (x86)\nec\vdca\gm\fw\manager\updatedata 2016/04/26 12:32:48.396,4144,INF,RollingUpdateLoop,Total target product num =4 2016/04/26 12:32:48.396,4144,INF,RollingUpdateLoop,RollingUpdate loop 1. Ta rget path=c:\program Files (x86)\nec\vdca\gm\fw\manager\updatedata/product1 : (Snip) 2016/04/26 12:32:52.332,4144,INF,UpdateImage,UpdateImage From=C:\Program Fi les (x86)\nec\vdca\gm\fw\manager\updatedata/product4\product, To=S:\vDCA\GM \FW\Manager 2016/04/26 12:32:52.333,4144,INF,UpdateImage,Backup path=c:\program Files ( 96

113 x86)\nec\vdca\gm\fw\manager\updatedata/product4\product\backup 2016/04/26 12:32:52.478,4144,INF,CommandLoop,Phase= /04/26 12:32:52.478,4144,INF,CommandLoop,Phase= /04/26 12:32:52.479,4144,INF,RollingUpdateLoop,RollingUpdate loop 4. Re tcode=0 2016/04/26 12:32:53.548,4144,INF,RupInstCmd_Main,----- Rolling Update End ExitCode=0 Exit code of 1 to 127 The shared disk update command terminated abnormally and the shared disk recovery process succeeded. Exit code of 128 or higher The shared disk update command terminated abnormally and the shared disk recovery process failed Applying the standard workflow template Workflow templates are not updated in overwrite installation. Import workflow templates by referring to Applying the standard workflow template in the Virtual DataCenter Automation Installation Guide [Active] Upgrading the global management server Upgrade the global management server in the active system. Perform the same procedure as the upgrading the standby system Upgrading the global management server in the Virtual DataCenter Automation Installation Guide, except as follows. Set the [Update the Data Directory at startup] setting to [No] [Active] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor [Active] Switching back the Service Governor Setup Overwrite the files that were backed up in any location in the procedure in " [Active] Backup of the service governor (page 93)". <Install folder>\fw\tomcat\conf\vdcplugins <Install folder>\fw\tomcat\conf\vdcapi.properties <Install folder>\fw\tomcat\vdcapikey.jks Moving to the Active System Start the following service in the active system. Chapter 10. Rolling update in the cluster environment 97

114 SQL Server Browser Chapter 10. Rolling update in the cluster environment In the EXPRESSCLUSTER WebManager window, right-click the failover group and select [Move] to move to the active system. Move the failover group to verify that neither the active nor standby system causes any error. This concludes rolling update of the Virtual DataCenter Automation general management server cluster system. 98

115 Chapter 11. Upgrading from NW Automation on the Cluster Environment Chapter 11. Upgrading from NW Automation on the Cluster Environment This chapter describes the upgrade procedures from Network Automation to Virtual DataCenter Automation in the cluster environment. In the following sections, it is assumed that the cluster is operating in the active system. Contents 11.1 Upgrading the Global Management Server Upgrading the Management Server Upgrading the ID Management Server

116 11.1 Upgrading the Global Management Server After upgrading the global management server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 5.2 Upgrading the Global Management Server Console in the Virtual DataCenter Automation Installation Guide Preparation Perform preparations required for operation of Virtual DataCenter Automation as a global management server. For details, see "Chapter 2. Preparation (page 5)". The settings that have been specified do not have to be specified again Suspending the cluster To stop process monitoring that is running, suspend the cluster. Chapter 11. Upgrading from NW Automation on the Cluster Environment 1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster [Active] Stopping the service Stop the following services. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. In a version earlier than Version 2.2, execute the following command. > otxadmin stop-domain --force --wait_timeout 180 domain1 > otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin In Version 2.2 or later, stop the following service. You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. Apache Tomcat 8.0 ServiceGovernor [Active] Upgrading the global management server Upgrade the global management server by overwriting the old version by using the Virtual DataCenter Automation Integrated Installer after updating the version of each component with the Network Automation Integrated Installer. 100

117 For details, refer to 5.1. Upgrading the Global Management Server in the Virtual DataCenter Automation Installation Guide [Active] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. If registered the EXPRESSCLUSTER task manager, You can prevent the warning messages being displayed in the alert view in EXPRESSCLUSTER WebManager by stopping the services from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor [Standby] Upgrading the global management server Upgrade the global management server by overwriting the old version by using the Virtual DataCenter Automation Integrated Installer after updating the version of each component with the Network Automation Integrated Installer. For details, refer to 5.1. Upgrading the Global Management Server in the Virtual DataCenter Automation Installation Guide. Perform the same procedure as the upgrading the global management server, except as follows. Set the [Update the Data Directory at startup] setting to [No] [Standby] Changing the Procedure of Starting a service governor and stopping the services Stop the following services, and change the [Startup type] to [Manual]. MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. Apache Tomcat 8.0 ServiceGovernor Setting up the Script Resource Chapter 11. Upgrading from NW Automation on the Cluster Environment This step is not necessary when updating the version from Version 2.2 or later. 1. Change into the setting mode from EXPRESSCLUSTER WebManager, click the failover group name, select [script] from the [Resources] tab, and then select [Property] from the [Edit] menu. 101

118 Chapter 11. Upgrading from NW Automation on the Cluster Environment 2. Select [start.bat] from the displayed dialog box, and then select [Edit]. call otxadmin start-domain WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armload service_bundleapserver /S /WAIT 180 /M /FOV "ServiceGovernor" 3. Select [stop.bat] from the displayed dialog box, and then select [Edit]. call otxadmin stop-domain --force --wait_timeout 180 domain1 call otxadmin stop-domain --force --wait_timeout 180 WebOTXAdmin Overwrite the settings described above with the settings described below: * There are two locations that must be corrected. Overwrite them separately. armkill service_bundleapserver After changing the settings, click [Apply] and then click [OK] Saving and Uploading Cluster Information This step is not necessary when updating the version from Version 2.2 or later. From EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. 102

119 Chapter 11. Upgrading from NW Automation on the Cluster Environment If the upload is skipped, no configuration information is applied to the active or standby system [Active] Starting the service Start the following services. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. MasterScope UMF Operations Manager_101 MasterScope UMF Operations Web Service vdcgmproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment. In a version earlier than Version 2.2, execute the following command. > armload service_bundleapserver /S /WAIT 180 /M /FOV "ServiceGovernor" In Version 2.2 or later, start the following service. Start the services by using [Start Monitoring] if you stopped them from the EXPRESSCLUSTER task manager. Apache Tomcat 8.0 ServiceGovernor Setting up the global management server Set up the global management server. License registration is performed after upgrading and installing the global management server monitoring terminal. Perform the procedure described in 5.2 Upgrading the Global Management Server Console in the Virtual DataCenter Automation Installation Guide. Perform the procedure described in Setting up the Property File for the Service Governor in the Virtual DataCenter Automation Installation Guide Resuming the cluster 1. From EXPRESSCLUSTER WebManager, resume the cluster. 2. After starting, move the failover group to verify that neither the active nor standby system causes any error. 103

120 11.2 Upgrading the Management Server After upgrading the management server, make sure to upgrade the corresponding monitoring terminals. For details, refer to 5.4 Upgrading the Management Server Console in the Virtual DataCenter Automation Installation Guide Preparation Perform preparations required for operation of Virtual DataCenter Automation as a global management server. For details, see "Chapter 2. Preparation (page 5)". The settings that have been specified do not have to be specified again Stopping the failover group Stop the failover group in the active system. Chapter 11. Upgrading from NW Automation on the Cluster Environment 1. From EXPRESSCLUSTER WebManager, perform operations to stop the failover group Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the active system. 1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the active system on the "Select Server" dialog. 2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the active system on the "Select Server" dialog [Active] Starting the SQL server Start the following services. SQL Server (FWCMDB) SQL Server Browser SQL Server (DPMDBI) SQL Server (SSCCMDB) [Active] Attaching the databases Perform the procedure described in "4.9.4 Attaching the Databases (page 32)" [Active] Re-creating database users Perform the procedure described in "4.9.5 Re-Creating Database Users (page 32)". 104

121 [Active] Upgrading the management server Upgrade the management server by overwriting the old version by using the Virtual DataCenter Automation Integrated Installer after updating the version of each component with the Network Automation Integrated Installer. For details, refer to 5.3. Upgrading the Management Server in the Virtual DataCenter Automation Installation Guide [Active] Setting up the SigmaSystemCenter Perform the following procedure. From "4.3 [Active] Setting Up the SigmaSystemCenter Services (page 26)" to "4.6 [Active] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database (page 29)". In "4.9.1 Positioning and Modifying the SQL Scripts (page 30)". Perform the procedure following files. Script Description 8 C:\MSSQL\attach_d.sql Used to attach a dpm database file. 9 C:\MSSQL\attach_p.sql Used to attach a pvm database file. 10 C:\MSSQL\detach_d.sql Used to detach a dpm database file. 11 C:\MSSQL\dettach_p.sql Used to detach a pvm database file. From "4.10 [Active] Copying a SigmaSystemCenter Database File (page 33)" to "4.17 [Active] Revising the SigmaSystemCenter Related Registry (page 37)" [Active] Stopping the service Stop the services below manually. FTBase service MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Active] Detaching the databases Perform the procedure described in " Detaching the Database (page 42)" [Active] Stopping the SQL server Stop the following services. SQL Server (FWCMDB) SQL Server Browser SQL Server (DPMDBI) SQL Server (SSCCMDB) Chapter 11. Upgrading from NW Automation on the Cluster Environment 105

122 Stopping the disk resource and floating IP resource Stop the disk resource in the active system. 1. From EXPRESSCLUSTER WebManager, stop the disk resource. 2. From EXPRESSCLUSTER WebManager, stop the floating IP resource Starting the disk resource and floating IP resource Start the disk resource and floating IP resource in the standby system. 1. From EXPRESSCLUSTER WebManager, start the disk resource. Select the standby system on the "Select Server" dialog. 2. From EXPRESSCLUSTER WebManager, start the floating IP resource. Select the standby system on the "Select Server" dialog [Standby] Starting the SQL server Start the following services. SQL Server (FWCMDB) SQL Server Browser SQL Server (DPMDBI) SQL Server (SSCCMDB) [Standby] Attaching the databases Perform the procedure described in "4.9.4 Attaching the Databases (page 32)" [Standby] Re-creating database users Perform the procedure described in "4.9.5 Re-Creating Database Users (page 32)" [Standby] Upgrading the management server Upgrade the management server by overwriting the old version by using the Virtual DataCenter Automation Integrated Installer after updating the version of each component with the Network Automation Integrated Installer. For details, refer to 5.3. Upgrading the Management Server in the Virtual DataCenter Automation Installation Guide [Standby] Setting up the SigmaSystemCenter Perform the following procedure. From "4.23 [Standby] Setting Up the SigmaSystemCenter Services (page 40)" to "4.26 [Standby] Stopping a Database Instance and Changing the Startup Settings of the SigmaSystemCenter Database (page 40)". In "4.28 [Standby] Copying Data from the Active System (page 41)". Perform the procedure following files. Chapter 11. Upgrading from NW Automation on the Cluster Environment Copy source (active system) C:\MSSQL\attach_d.sql Same path Copy destination (standby system) 106

123 Chapter 11. Upgrading from NW Automation on the Cluster Environment Copy source (active system) C:\MSSQL\attach_p.sql C:\MSSQL\detach_d.sql C:\MSSQL\dettach_p.sql Copy destination (standby system) Same path Same path Same path "4.31 [Standby] Editing ESMPRO/ServerManager Configuration Files (page 42)" [Standby] Stopping the service Stop the services below manually. FTBase service MasterScope UMF Operations Web Service vdcmomproxy_n The "n" at the end digit should be 1 or a greater number. The number varies depending on the installation environment [Standby] Detaching the databases Perform the procedure described in " Detaching the Database (page 42)" [Standby] Stopping the SQL server Stop the following services. SQL Server (FWCMDB) SQL Server Browser SQL Server (DPMDBI) SQL Server (SSCCMDB) Stopping the disk resource and floating IP resource Stop the disk resource in the standby system. 1. From EXPRESSCLUSTER WebManager, stop the disk resource. 2. From EXPRESSCLUSTER WebManager, stop the floating IP resource Starting the failover group From EXPRESSCLUSTER WebManager, perform operations to start the failover group. Select the active system on the "Select Server" dialog. 107

124 Setting Up the registry synchronous resources Perform the procedure described in "4.33 Setting Up the Registry Synchronous Resources (page 43)" Setting up the script resources Chapter 11. Upgrading from NW Automation on the Cluster Environment From the EXPRESSCLUSTER WebManager, edit the script files included in this document as the script resources. File name <Install DVD>:\script\cluster-pro\MoM\vDCA\start.bat <Install DVD>:\script\cluster-pro\MoM\vDCA\stop.bat Service starting script Description Service stopping script Perform the following actions. 1. From EXPRESSCLUSTER WebManager, change to the Config Mode, right-click "script" in the resource list, and select Properties. 2. On the displayed dialog, select the [Details] tab, and click the [Add] button to register the script. Edit the script (*.bat) accordingly in the following cases. The path of the shared disk is different. The instance name of SQL Server is different. The number at the end of the service name of MasterScope UMF Operations Web Service is different. When being different from a default folder in an installation destination of a Management Server, please correct a installed path(2 Points) of a service script(start.bat). 108

125 Chapter 11. Upgrading from NW Automation on the Cluster Environment rem ******************* rem Set Routing rem ******************* call "C:\Program Files (x86)\nec\vdca\mom\fw\manager\bin\nwautomation \nwa_routerestore.bat" Saving and Uploading Cluster Information From the EXPRESSCLUSTER WebManager, save the cluster configuration information and upload the information files. If the upload is skipped, the cluster will not operate normally because no configuration information is reflected to the active or standby system Suspending the cluster To stop process monitoring that is running, suspend the cluster. 1. From EXPRESSCLUSTER WebManager, perform the operation to suspend the cluster. 2. Open the EXPRESSCLUSTER task manager, and stop monitoring all the active services Registering and setting up the management server Perform license registration and setting of the management server. License registration is performed after upgrading and installing the management server monitoring terminal. Perform the procedure described in 5.4 Upgrading the Management Server Console in the Virtual DataCenter Automation Installation Guide. 1. Perform license registration only for the SigmaSystemCenter function. Perform setting of the SigmaSystemCenter function. From "4.37 [Active] Moving the DPM Backup Image Storage Folder / Image Storage Folder (page 46)" to "4.38 [Active] Registering the License in SigmaSystemCenter (page 47)". From "4.41 [Active] Registering a Subsystem in SigmaSystemCenter (page 48)" to "4.43 [Active] Initializing the Operation Management Functions (page 48)". "4.47 [Active] Changing the Environment Configuration of SystemMonitor Performance Monitoring (page 49)". 109

126 Resuming the Cluster From EXPRESSCLUSTER WebManager, resume the cluster. Chapter 11. Upgrading from NW Automation on the Cluster Environment Rebooting the cluster From EXPRESSCLUSTER WebManager, reboot the cluster. After rebooting the cluster, move the failover group to verify that neither the active nor standby system causes any error Upgrading the ID Management Server Changing the registry In each of the active and standby systems, change the value of InstType of the following registry key from NWA to VDCA. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\vDCAInst\SecureMaster This concludes upgrading of the Virtual DataCenter Automation ID management server cluster system. 110