White paper Installing and upgrading HP Insight Management 7.2 on Windows Server 2012 Failover Clusters HP Insight Management 7.
White paper | HP Insight Management 7.2 Table of Contents Revision history .................................................................................................................................. 6 Abstract ............................................................................................................................................... 7 Introduction ......................................................................................................................................
White paper | HP Insight Management 7.2 Installing Microsoft SQL Server 2012 Enterprise .......................................................................24 Installing Microsoft Distributed Transaction Coordinator as a clustered service ......25 Installing Microsoft SQL Server 2012 Enterprise as a clustered service ....................26 Alternative method for launching the SQL Server 2012 installer ...............................................................................................
White paper | HP Insight Management 7.2 Creating the generic service resource: HP Agentless Data Collector Service ............................................................................ 46 Creating the generic service resource: HP Capacity Advisor Data Service (formerly known as “HP Agentless Collection for Linux Systems”) .........................................................................................................................................................
White paper | HP Insight Management 7.2 Upgrading in a federated CMS environment ................................................................... 70 Upgrade steps ...................................................................................................................... 70 Appendix C: Applying Insight Management Incremental Updates ..........................................81 Option 1: Installing an Incremental Update during a fresh install ...............................
White paper | HP Insight Management 7.2 Revision history 6 | March 2013 Version Date Description of Revision 1.0 March 2013 First release of this white paper 1.
White paper | HP Insight Management 7.2 Abstract Using Failover Clustering with HP Insight Management is a simple way of achieving redundancy, availability, load balancing, and failover capability for this powerful management software. This white paper is intended to assist IT professionals with one or more of the following: 1. Install Insight Management 7.2 for ProLiant from its DVD distribution onto a Microsoft Windows-based Central Management Server (CMS) to create a highly available environment.
White paper | HP Insight Management 7.2 Introduction The HP Insight Management media set provides an installer to quickly and accurately deploy, configure, integrate, and update HP Insight Management products. For more information about the individual components delivered with HP Insight Management, visit http://www.hp.com/go/insightmanagement/docs.
White paper | HP Insight Management 7.2 o All system components (server, storage, HBA, MPIO, etc.) have been certified under the Windows Server Logo Program for Windows Server 2012. See the following Microsoft website: http://www.windowsservercatalog.com/ o The fully configured solution must pass the Validate test in the Failover Cluster Manager. Using a CMS cluster as part of a federated CMS environment A federated CMS environment relates specifically to HP Matrix infrastructure orchestration.
White paper | HP Insight Management 7.
White paper | HP Insight Management 7.2 1 By using the Insight Installer’s Customize button, components from this table can be selected for installation. 2 This component may require special configuration to run in a CMS cluster as described later in this whitepaper.
White paper | HP Insight Management 7.2 • Because the Microsoft SQL Server instance used by Insight Management is also a clustered service, Insight Management connects to it via the instance’s own client access point. • The databases used by the Insight Management reside on a shared disk managed by Microsoft SQL Server. Other CMS data are stored on a shared disk owned by Insight Management.
White paper | HP Insight Management 7.2 Getting started This white paper documents how to install Insight Management on a new two-node Microsoft Failover Cluster.
White paper | HP Insight Management 7.2 If the servers are ProLiant Server Blades, it is a best practice to locate them in separate enclosures that will not be managed by the Insight Management software that runs on them. Software The following software is needed: • Microsoft Windows Server 2012 Standard, which includes: o Failover Clustering o Microsoft Distributed Transaction Coordinator (DTC) • Microsoft SQL Server 2012 Enterprise or Standard • HP Insight Management 7.
White paper | HP Insight Management 7.2 Create the shared disks W:, T:, S:, and V: on the SAN and present them to the cluster nodes, but do not “online,” “initialize,” or “create” a volume for any disk until instructed to do so in Creating the Failover Cluster. Supporting Systems It is assumed that an existing Active Directory domain infrastructure and DNS services suitable for hosting the cluster are available. Multi-site clusters are not supported.
White paper | HP Insight Management 7.2 5. Failover Cluster primary system IP address and name Function: To serve as the TCP/IP address and name of the specific Microsoft Windows server host Suggested action: Any software that references system-specific functions uses this address to connect to this system. In the examples discussed in this white paper, the IP address is 15.199.242.157 and the name is CMS-C16-N1. 6.
White paper | HP Insight Management 7.2 Setting up the failover environment This section covers setting up the cluster environment in preparation for installing SQL Server 2012 and Insight Management.
White paper | HP Insight Management 7.2 On each system: 1. Select Start Administrative Tools Server Manager. 2. If Application Server is listed in the left pane, select it, and then in the right pane ensure that all the Role and Feature Services listed Figure 2: Application Server Role Services from Server Manager are installed. If so, exit Server Manager and go to the next section, Setting the SNMP service community name and security.
White paper | HP Insight Management 7.2 1. Select Start Administrative Tools Server Manager. 2. In the left pane, click All Servers. • If SNMP Service is listed with the installed features in the middle pane under ROLES AND FEATURES, exit Server Manager and continue with Setting the SNMP service community name and security. 3. Run the Add Roles and Features Wizard. Navigate to the Select features screen. 4. Select SNMP Service.
White paper | HP Insight Management 7.2 2. On the View by: menu, select Small icons. 3. Click HP Management Agents. 4. Click the Services tab. 5. Ensure that Clustering information is either present in or added to the list of Active agents. 6. Click OK to apply the update and Yes to restart the management agents. Matrix pre-requisites If you are installing Matrix in a high availability configuration, add any additional Windows features or tools required for Matrix at this point.
White paper | HP Insight Management 7.2 Step # Step Description Notes 3 Connect networks and storage: Important: Use the Microsoft Disk Management snap-in described to Online, Initialize, and then create a New Simple Volume… for only disk W:, the witness disk. The volume type for shared disks must be Basic. MBR or GPT partitions can be used. When the cluster is created in step 5, there is no user control of which disk is selected to be the witness disk.
White paper | HP Insight Management 7.2 After the cluster has been successfully formed, continue under the same account and with both cluster nodes online to complete the following steps: 22 | March 2013 1. Click Start Administrative Tools Computer Management Disk Management. Select Online, then Initialize, and finally create New Simple Volumes… for the remaining three shared disks. The volume type for shared disks must be Basic. MBR or GPT partitions may be used. 2.
White paper | HP Insight Management 7.2 At this point a two-node Failover Cluster has been created, and no clustered services or applications are yet configured. All relevant Microsoft operating system updates should have been applied to both cluster nodes. Failover Cluster Manager should produce a display similar to one shown in Figure 4.
White paper | HP Insight Management 7.2 Installing Microsoft SQL Server 2012 Enterprise A clustered instance of Microsoft SQL Server 2012 Enterprise or Standard is required for Insight Management components to become highly available. If you already have installed a suitable named instance of Microsoft SQL Server 2012, you can skip to Installing Insight Management components on the cluster and specify this instance when prompted.
White paper | HP Insight Management 7.2 Installing Microsoft Distributed Transaction Coordinator as a clustered service MSDTC coordinates distributed transactions across a Windows Failover Cluster. SQL Server functionality can be adversely impacted if MSDTC is not installed. In an active-active cluster MSDTC must be installed as a clustered service. The following implementation installs one instance of MSDTC as a clustered service in its own group.
White paper | HP Insight Management 7.2 4. Upon completion, you should see a screen similar to Figure 6. Figure 6: Microsoft Distributed Transaction Coordinator service in Failover Cluster Manager For additional information on DTC, see: • Requirements for Creating an MS DTC Resource in a Failover Cluster, http://technet.microsoft.com/en-us/library/cc770748(WS.10).aspx • Understanding MS DTC Resources in Windows Server Failover Clusters, http://technet.microsoft.com/en-us/library/cc730992(WS.10).
White paper | HP Insight Management 7.2 If this occurs in your installation, the workaround is to invoke the SQL Server 2012 installer from the command prompt as described here. Navigate to the directory that contains setup.exe for the SQL Server 2012. Then use one of the following commands to start the installer.
White paper | HP Insight Management 7.2 If the cluster’s domain controllers are on the private network, the network binding order should remain public first, then private. However, this will produce a warning for the Network binding order test. This is just a warning and it is acceptable to proceed. 7. Product Key: Enter your product key and click Next. 8. License Terms: If you accept the license terms, select the acceptance box and click Next. 9. Setup Role: Select “SQL Server Feature Installation”.
White paper | HP Insight Management 7.2 entry. Either keep the default name shown, select another name from the drop-down (if another choice exists), or enter a name. This white paper kept the default selection, SQL Server (cms_c16_instance). On the screen, the names with a red symbol in the Qualified column are not eligible. Click Next. 15. Cluster Disk Selection: Select the box for each available shared disk you want SQL Server to use for data storage.
White paper | HP Insight Management 7.2 20. Reporting Services Configuration: If you selected the Reporting Services feature, make selections as done for Analysis Services Configuration. 21. Error Reporting: Specify the preferred types of reporting services, and then click Next. 22. Cluster Installation Rules runs tests and produces a results display. Verify that no tests are failed, and then click Next. 23. Ready to Install: Verify the configuration presented, and then click Install. 24.
White paper | HP Insight Management 7.2 6. Product Key: Enter your product key and click Next. 7. License Terms: Select the accept box and click Next. 8. Cluster Node Configuration: Verify that the SQL Server instance name shown is correct. If not, select the correct instance to be installed from the list on the screen. Click Next. 9. Cluster Network Configuration: Review and click Next. 10. Service Accounts: Enter the account password for each Service where the Password field is white. Click Next.
White paper | HP Insight Management 7.2 such as security issues, are packaged into General Distribution Releases and distributed through Microsoft Update, Windows Update, or both. Other hotfixes are released periodically as cumulative updates. These updates must be requested. See The SQL Server 2012 builds that were released after SQL Server 2012 at http://support.microsoft.com/kb/2772858 and Cumulative update package 5 for SQL Server 2012 is available at http://support.microsoft.com/kb/2777772.
White paper | HP Insight Management 7.2 Installing Insight Management components in the cluster By following the previous instructions in this white paper, you now have a two-node Failover Cluster with Microsoft Distributed Transaction Coordinator and an instance of Microsoft SQL Server 2012 Enterprise installed as clustered services. The resources needed to create a clustered service for Insight Management 7.2 have been provisioned. Both cluster nodes are running.
White paper | HP Insight Management 7.2 8. At this point the cluster group for Systems Insight Manager and Insight Management has been created, the client access point resource is defined and is online, and disk resource is defined and online as shown in Figure 7.
White paper | HP Insight Management 7.2 a. b. Simplest: if you wish to allow SQL Server to listen to all the IP addresses bound to network cards on the system through a single static port (the SQL Server default), then: i. On the Protocol tab, ensure that Enabled is set to Yes and Listen All is set to Yes. ii. Click the IP Addresses tab. Navigate to the IP All entry at the bottom of the list. Set its TCP Dynamic Ports parameter to blank and its TCP Port parameter to your selected static port number.
White paper | HP Insight Management 7.2 3. b. Select only the components you will be installing. c. Select Include Pre-Install Tests. d. Click OK and Run Now. Review the results. Correct any material deficiencies noted, such as installing any missing software. Important: Be sure .NET 3.5.1 or later software is installed BEFORE continuing with the HP Insight Management installation. Microsoft SQL Server 2012 requires .NET 3.
White paper | HP Insight Management 7.2 In the following two sections, the notation, [ICG: Step n], indicates that the step number below aligns to Step n in Section 2 of the ICG. Important: If the steps in the following sections differ from the ICG, follow the steps in this white paper.
White paper | HP Insight Management 7.2 you are installing a CMS cluster that will be part of a federated CMS environment, see the Primary CMS and Secondary CMS columns. After verifying the components for installation, the process for installing a federated or non-federated CMS cluster is the same. 6. [ICG: Step 5] The Insight Management DVD #2 Selection screen appears when you are installing or upgrading components or suites that reside on DVD #2. The items to be installed from this DVD appear onscreen.
White paper | HP Insight Management 7.2 14. [ICG: Step 23] Follow the Insight Management installation instructions to complete the installation. You have successfully completed the installation if each component is marked successfully installed or successfully upgraded and Product Configuration is marked successfully completed.
White paper | HP Insight Management 7.2 Installing Insight Management components on the secondary system To have a clustered installation of HP Insight Management, you must complete the installation process on the secondary system as well, with a few differences in the procedure to account for the existing program files on the cluster disk. Installing Insight Management 7.2 Important: Be sure to specify the same user credentials and path information that you used on the primary system. 1.
White paper | HP Insight Management 7.2 If these entries appear, which suggests that the PMP configuration has not completed, then copy the *.xml and *.properties files from the PMP installation directory to the Systems Insight Manager setup folder. 7. Open the ~\Systems Insight Manager\config\database.props file (for example, using Notepad) and record the database name corresponding to the hp.Database.databaseName keyword. Optional: Installing an Insight Management 7.
White paper | HP Insight Management 7.2 Adding the Insight Management cluster resources To complete the installation of HP Insight Management to the cluster, several cluster resources must be created using Failover Cluster Manager. 1. If the secondary system is powered on, shut it down and wait for it to complete. 2. If the primary system is powered off, power it on and wait for it to complete. 3. Log in to Windows on the primary system as SQL/IM Administrator. 4. Power on the secondary system. 5.
White paper | HP Insight Management 7.2 Using Failover Cluster Manager to create resources for the Insight Management clustered service This section describes the process for creating the Systems Insight Manager cluster resources. The actual creation of the resources is done in the sections following this one. The same process is repeated to create each needed cluster resource.
White paper | HP Insight Management 7.2 In the center pane of Failover Cluster Manager under Roles in the Resources tab, right-click the resource just created and click Properties. The Properties screen appears. 1. Click the Advanced Policies tab. Under Possible Owners ensure that each cluster node has a check in its box. 2. Click the Dependencies tab. At the top of the white area click Click here to add a dependency. 3.
White paper | HP Insight Management 7.2 a. Select the HP Systems Insight Manager service. b. The Confirmation screen shows Service: HP Systems Insight Manager (HP Systems Insight Manager). 2. Add the following dependency to the new resource’s properties: Pegasus WMI Mapper. 3. On the Policies tab, set the “Pending timeout” value to 15:00. Creating the generic service resource: OpenSSH Server 1. Use the New Resource Wizard to create a generic service: 2. a. Select the OpenSSH Server service. b.
White paper | HP Insight Management 7.2 Creating the generic service resource: HP Insight Control virtual machine management 1. Use the New Resource Wizard to create a generic service: 2. a. Select the HP Insight Control virtual machine management service. b. The Confirmation screen shows Service: HP Insight Control virtual machine management (hpvmmsvc). Add the following dependency to the new resource’s properties: HP Systems Insight Manager.
White paper | HP Insight Management 7.2 b. 2. The Confirmation screen shows Service: HP Capacity Advisor Data Service (HP Capacity Advisor Data Service). Add the following dependencies to the new resource’s properties: HP Global Workload Manager Central Management Server and HP Systems Insight Manager. Creating the generic service resource: HP Extensible Storage & Server Adapter 1. Use the New Resource Wizard to create a generic service: 2. a.
White paper | HP Insight Management 7.2 2. a. Select the RSJRAS service. b. The Confirmation screen shows Service: RSJRAS (RSJRAS). Add the following dependency to the new resource’s properties: HP SIM Disk and HP SIM Network Name. Creating the generic service resource: RSCentral 1. Use the New Resource Wizard to create a generic service: 2. a. Select the RSCentral service. b. The Confirmation screen shows Service: RSCentral (RSCentral).
White paper | HP Insight Management 7.2 a. 3. On the Services console, change the startup type for the HP Matrix infrastructure bursting connecter service from Disabled to Manual. Use the New Resource Wizard to create a generic service: a. Select the HP Matrix infrastructure bursting connecter service. The Confirmation screen shows Service: HP Matrix infrastructure bursting connecter (hpio-connecter). 4.
White paper | HP Insight Management 7.2 com.hp.gwlm.security.virtualLocalHostName= Where is the virtual server IP address of Systems Insight Manager. HP Matrix infrastructure orchestration 1. Edit the hpio property file found in ~\Matrix infrastructure orchestration\hpio.conf. In the following line, starting with #wrapper, delete the “#” and replace [FQDN] with the FQDN of the HPSIM virtual server: … #Uncomment this line for a clustered HA environment. #wrapper.
White paper | HP Insight Management 7.2 Bringing online the Insight Management clustered service In the center pane of Failover Cluster Manager, right-click the HP SIM Group, in this white paper cms-c16-matrix, and select Start Role. If configured properly, all resources should come online, as shown in Figure 9.
White paper | HP Insight Management 7.2 Always use Failover Cluster Manager to stop a service. Right-click the service’s resource in the center pane and then click Stop Role. The resource and any other resources that have a dependency on it are taken offline. To start the same service, right-click it, then click bring this resource online. The resource and any others on which it is dependent are brought online. Note the asymmetry of operation.
White paper | HP Insight Management 7.2 Completing and validating the installation At this time both nodes of the cluster remain online, Insight Management services are online, and you are logged into Windows on the primary system with the SQL/IM Administrator account. Configuring Systems Insight Manager and validating the cluster It is important to complete the following Systems Insight Manager configuration steps on first login. 1.
White paper | HP Insight Management 7.2 than the name of the server that owns the virtual group, a security certificate for Systems Insight Manager is sent to your browser. If your browser is configured to warn about invalid site certificates, a security alert displays when connecting to the Systems Insight Manager virtual server (which was created earlier in this white paper). This alert indicates that the server name to which you have connected does not match the name on the certificate.
White paper | HP Insight Management 7.2 9. b. Under Sign-in Credentials, enter the SQL/IM Administrator account credentials (for example, domain\username and password). Click Add. c. Ensure that under SNMP Credentials the SNMP Community String is set to public. d. Click OK. Navigate to Options Discovery. The Systems Insight Manager discovery page appears. a. Click the link for Configure general settings under For all automatic discoveries. b.
White paper | HP Insight Management 7.2 g. The Sign-in tab is selected. Under Use these credentials, enter the SQL/IM Administrator account credentials (for example, domain\username and password). h. Clear the If these credentials fail box. i. Click the SNMP tab and ensure the community string is set to public or the preferred string is configured. j. Click OK. k. Click Save to complete. 12. Run the discovery task just created. a.
White paper | HP Insight Management 7.2 g. The Sign-in tab is selected. Under Use these credentials, enter the SQL/IM Administrator account credentials (for example, domain\username and password). h. Clear the If these credentials fail box. i. Click the SNMP tab and ensure the community string is set to public or the preferred string is configured. j. Click OK. k. Click Save to complete. 16. Run the discovery task just created. a.
White paper | HP Insight Management 7.2 b. Click the Tools & Links tab. c. Click the link to Edit System Properties. When the page appears: d. i. Ensure the box labeled Prevent the Discovery process from changing this system name is selected. ii. Ensure the box labeled Prevent the Discovery process from changing this system’s primary IP address is selected. iii.
White paper | HP Insight Management 7.2 i. WMI Mapper Proxy (Step 7) ii. SNMP community name and credentials (Steps 8, 11.i, and 15.i) iii. Ping exclusion ranges (Step 9) iv. Discovery tasks edited and created (Steps 10, 11, 13, and 15) d. Verify consistency of the All Systems and Cluster Monitor displays (Steps 17 and 18). 22. Systems Insight Manager Group resources are now owned by the secondary system.
White paper | HP Insight Management 7.2 secondary system. Next repeat these steps for the secondary system. Lastly move the Systems Insight Manager Group back to the primary system. a. Browse to VCRM using the Systems Insight Manager virtual network name and port 2381 (for example, https://cms-hpsim.fqdn:2381). Log in with the same credentials used in Step 1. b. On the bottom of the SMH home page, click Version Control Repository Manager. The Version Control Repository Manager home page appears. c.
White paper | HP Insight Management 7.2 4. g. Enter the fully qualified Systems Insight Manager virtual server name or the Systems Insight Manager virtual server IP address in the Property Value field. h. Check in the property by clicking the padlock. i. Enter a comment and click OK. Update the RAS_Operator_Path property to include the fully qualified Systems Insight Manager virtual server name. a.
White paper | HP Insight Management 7.2 e. Click Finish.
White paper | HP Insight Management 7.2 Configuring the cluster for operations To implement the Insight Management high availability configuration described in Figure 1 with Systems Insight Manager and Microsoft SQL Server running on different nodes, HP recommends you use the cluster resource ownership arrangement shown in Figure 12. Use Failover Cluster Manager to move the Resource Groups as needed. If a node were to fail, its resources would fail over to the other node.
White paper | HP Insight Management 7.2 Using the Cluster Validation Wizard to verify the storage configuration The Cluster Validation Wizard runs a comprehensive suite of tests on your cluster, including its storage configuration. The wizard should be run whenever you change the configuration of the cluster or replace a hardware component. Successful completion of the wizard ensures that your cluster is properly configured and is a requirement for cluster support.
White paper | HP Insight Management 7.2 Appendix A: Summary of Insight Management cluster resources Table 3. Summary of Insight Management cluster resources Resource Name Resource Type Dependencies Service name Notes cms-c16-matrix Group N/A N/A Group “container” for cluster resources c16_insight Physical Disk None N/A Disk V: IP Address 15.199.242.164 IP Address None N/A Virtual IP used to connect to SIM Network Name IP Address: N/A 15.199.242.
White paper | HP Insight Management 7.
White paper | HP Insight Management 7.
White paper | HP Insight Management 7.2 Appendix B: Upgrading clustered Insight Management This appendix describes how to upgrade Insight Management in a cluster environment. The upgrade procedure can be used to do the following: 1. Upgrade from Insight Software 6.2 or a succeeding release to Insight Management 7.2. 2. Add new products to an existing installation of Insight Management 7.2. 3. Apply an Insight Management 7.2 incremental update to Insight Management 7.2. 4.
White paper | HP Insight Management 7.2 c. Upgrade Insight Management on the secondary system. You can upgrade to a new major release, install new products, and/or apply an incremental update. d. Stop the Insight Management services on the secondary system. 6. Use Failover Cluster Manager to update cluster resources for the new software. 7. Start Systems Insight Manager on the primary system. 8. Perform validation and final configuration steps.
White paper | HP Insight Management 7.2 Upgrading in a federated CMS environment A CMS federation includes a primary and one or more secondary CMSs. The following rules for upgrading in a federation apply to both standalone and clustered CMSs: • The primary must be the first CMS to be upgraded. • After the primary is upgraded, the secondary CMSs may be upgraded in any order. • The secondary CMSs may be upgraded serially or in parallel.
White paper | HP Insight Management 7.2 3. Upgrade the primary system. a. Make sure the primary system is running and the secondary system is shut down. b. Log into the primary system with the same administrator credentials that you configured for the Insight Management service account credentials. c. Use Failover Cluster Manager to take the Insight Management service offline. In this paper, the Insight Management service is called cms-c16-matrix. d.
White paper | HP Insight Management 7.2 xx. RSJRAS xxi. RSCentral xxii. HP Matrix Infrastructure Orchestration xxiii. HP Matrix Infrastructure chargeback g. Verify that Systems Insight Manager has completed its startup by logging into the Systems Insight Manager service through a client Web browser. Use the network name specified for the Systems Insight Manager network name cluster resource. Then log out. h. Install the new Insight Management release or products.
White paper | HP Insight Management 7.2 j. Run Insight Management Advisor… to confirm that all the installation requirements are met. Select Filter, and then Customize. Select those products that you want to upgrade or install. Only select products which are supported in a highly available environment. See Table 1 for the list of Components supported in a highly available environment. Click OK and Run Now.
White paper | HP Insight Management 7.2 Install Insight Management 7.2 Incremental Update and Insight Management Software Patches on the Primary System (Optional) 4. u. You can choose to install an Insight Management 7.2 incremental update on the primary. See Appendix C: Applying Insight Management Incremental Updates for more information about installing an incremental update. See How to run the Incremental Update Installer in Appendix C for details about running the incremental installer. v.
White paper | HP Insight Management 7.2 xi. HP Agentless Collection for Linux Systems xii. HP Capacity Advisor Data Service xiii. HP Extensible Storage & Server Adapter xiv. HP SPM Storage Module J2EE Service xv. HP SPM Storage Module Service xvi. HP Storage Provisioning Manager xvii. HP Storage Provisioning Manager Service xviii. HP Logical Server Automation xix. RSScheduler xx. RSJRAS xxi. RSCentral xxii. HP Matrix Infrastructure Orchestration xxiii.
White paper | HP Insight Management 7.2 • Upgrade directly from Insight Software 6.2 or a succeeding release to Insight Management 7.2. Complete the steps under Install Insight Management 7.2 Release on the Secondary System followed by the steps under Install Insight Management 7.2 Incremental Update and Insight Management Software Patches on the Secondary System. Install Insight Management 7.2 Release on the Secondary System. h. Insert HP Insight Management DVD #1 into the DVD drive.
White paper | HP Insight Management 7.2 6. Use Failover Cluster Manager to update the cluster resources for the new software. The specific modifications needed for the cluster resources vary, depending on your Insight Management source and target release numbers. Identify the “Change Set” number from Table 4 that corresponds to upgrade that you are performing. Then execute each following step that is prefaced with your Change Set number. For example, if you are upgrading from 6.2 to 7.
White paper | HP Insight Management 7.2 To recreate this cluster resource, follow these steps: e. f. i. In Failover Cluster Manager, in the center pane, delete the existing resource HP Storage Provisioning Manager. ii. Add the new resource named HP Storage Provisioning Manager Service and its dependencies, as described in Creating resources for HP Matrix components. [2]: If HP Matrix Operating Environment is installed, edit the dependencies for the HP Storage Provisioning Manager Service resource.
White paper | HP Insight Management 7.2 n. 7. [4]: If you have installed a new Insight Management 7.2 product, add its cluster resources. See Adding the Insight Management cluster resources for directions on how to add cluster resources. Start Systems Insight Manager clustered service. a. b. c. d. On the secondary system, edit or confirm the property file settings following instructions in Updating properties .
White paper | HP Insight Management 7.2 g. 8. 80 | March 2013 Use Failover Cluster Manager to move the Insight Management clustered service to the primary system. Bring the service online. In this paper, the Insight Management service is called cms-c16-matrix. Perform validation and final configuration steps. a.
White paper | HP Insight Management 7.2 Appendix C: Applying Insight Management Incremental Updates This appendix describes how to apply an Insight Management incremental update (patch) to Insight Management in a Failover Cluster. An Insight Management incremental update is a patch that is applied to a major release. For example, an Insight Management 7.2 update is a patch for Insight Management 7.2. Insight Management 7.2 must already be installed before installing an Insight Management 7.2 update.
White paper | HP Insight Management 7.2 4. Add cluster resources for Insight Management, complete the Insight Management configuration, and validate the installation. Option 2: Installing an Incremental Update during an upgrade to a major release Appendix B: Upgrading clustered Insight Management describes upgrading Insight Management in a cluster. It also discusses installing an incremental update during an upgrade to a new major release of Insight Management.
White paper | HP Insight Management 7.2 8. Perform validation and final configuration steps. How to run the Incremental Update Installer This section describes the steps for running the incremental update installer. 1. If you are installing on the primary system, make sure the secondary system is shut down. Alternately, if you are installing on the secondary system, make sure the primary system is shut down. 2.
White paper | HP Insight Management 7.2 Appendix D: Applying Insight Management Software Patches This appendix provides an overview of the steps to apply Insight Management Software patches during or after an upgrade to a major release. Before applying the patch, the Insight Management software should be installed on the system. To install an Insight Management Software Patch, follow the instructions provided with the patch.
White paper | HP Insight Management 7.2 Appendix B: Upgrading clustered Insight Management describes upgrading Insight Management in a cluster. It also discusses installing an incremental update, if applicable, followed by any applicable Insight Management Software Patches during an upgrade to a new major release of Insight Management. The steps from Appendix B: Upgrading clustered Insight Management are summarized as follows: 1.
White paper | HP Insight Management 7.2 7. After the patch installation is completed on the primary system, move the Insight Management resources over to the secondary system. Wait for the HP SIM group resources to come online. 8. Install the Insight Management Software Patches on the secondary system if the Insight Management Software patches have been installed on the primary system.
White paper | HP Insight Management 7.2 Appendix E: Migrating an Insight Management 7.2 Windows 2012 Cluster or a 7.2 Windows 2012 Standalone Server to a Windows 2012 Cluster This appendix provides an overview of the steps to migrate an Insight Management 7.2 Windows 2012 Cluster or a 7.2 Windows 2012 Standalone Server, called the Source system, to a new Windows 2012 cluster, called the Target system. The source standalone server may be in a domain or in a workgroup.
White paper | HP Insight Management 7.2 2. On the source cluster or Standalone Server, follow the instructions in the Data Migration of an existing Microsoft Windows CMS to a new Insight Management 7.2 system White Paper to perform the following: a. Prepare the source CMS and run the export utility on one of the nodes in the Windows 2012 cluster or on the Standalone Server. b.
White paper | HP Insight Management 7.2 References See the following for more information regarding the topics discussed in this white paper. HP white papers from previous Insight Management releases Table 6 White papers for previous Insight Management releases Operation Release Title with link to document Install, upgrade 7.1 Installing and upgrading HP Insight Management 7.1 on Windows Server 2008 R2 Failover Clusters Backup, restore 7.1 Backing up and restoring HP Insight Management 7.
White paper | HP Insight Management 7.2 HP infrastructure software, servers, and storage • All documentation for Insight Management, including HP Systems Insight Manager, Insight Control, and Matrix, can be found through the following link: http://www.hp.com/go/insightmanagement/docs Also, the following white papers can be found on this website: o Backing up and restoring HP Insight Management 7.
White paper | HP Insight Management 7.2 Microsoft Distributed Transaction Coordinator (MS DTC) • Distributed Transaction Support for Application Server, http://technet.microsoft.com/enus/library/cc772014.aspx • Requirements for Creating an MS DTC Resource in a Failover Cluster, http://technet.microsoft.com/en-us/library/cc770748(WS.10).aspx • Understanding MS DTC Resources in Failover Clusters, http://technet.microsoft.com/enus/library/cc755269(v=ws.10).
White paper | HP Insight Management 7.2 For more information Learn more at www.hp.com/go/matrixoe www.hp.com/go/matrixoe www.hp.com/go/insightcontrol www.hp.com/go/vse www.hp.com/go/hpsim Sign up for updates hp.com/go/getupdated Share with colleagues Rate this document © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
