Technical white paper Backing Up and Restoring HP Insight Management 7.3 Central Management Server (Windows) HP Insight Management 7.
Technical white paper | HP Insight Management 7.3 Table of contents Abstract ........................................................................................................................................................................................... 4 Introduction .................................................................................................................................................................................... 5 Scope...........................................
Technical white paper | HP Insight Management 7.3 Appendix G: SPM resynchronization actions ......................................................................................................................... 82 Appendix H: Matrix infrastructure orchestration resynchronization ................................................................................ 85 Matrix infrastructure orchestration resynchronization limitations ..............................................................................
Technical white paper | HP Insight Management 7.3 Abstract The purpose of this white paper is to assist IT professionals in performing backup and recovery of HP Insight Management 7.3 running on a Microsoft Windows-based Central Management Server (CMS). HP Insight Management software products are designed to address the most difficult issues encountered by IT organizations: cost, time, energy, and change.
Technical white paper | HP Insight Management 7.3 Introduction If the HP Insight Management CMS has been lost or corrupted, you may need to restore the CMS from a backup copy. Note: The information in this white paper is specific to the HP Insight Management software components included on the HP Insight Management 7.3 DVD. See Scope for more details. Preparing your environment for backup describes the steps to quiesce the HP Insight Management CMS before performing a backup.
Technical white paper | HP Insight Management 7.3 HP Insight Management component Comments HP Insight managed system setup wizard HP Insight Control power management HP Insight Control performance management HP Insight Control virtual machine management (VMM) This document describes saving and restoring the VMM configuration data stored on the CMS.
Technical white paper | HP Insight Management 7.3 This configuration is also referred to as an infrastructure orchestration federated CMS. Backups and restores of CMSs in a federated CMS are not required to be synchronized. If one CMS in the federated CMS fails, it can be recovered by a restore from backup. It is not necessary to restore the other CMSs in the federated CMS. HP Insight Management can also be configured for high availability using Microsoft Failover Cluster.
Technical white paper | HP Insight Management 7.3 From the primary CMS, you can run the ioexec command from the command prompt, as shown in the following example. This command is located in \bin. See Table 7 for the default location of . You must replace with the lowercase fully qualified domain name (FQDN) of the secondary CMS to be backed up. This must be the same hostname configured on the Federated CMS Configuration page.
Technical white paper | HP Insight Management 7.3 Quiesce order HP Insight Management component (HP Matrix Operating Environment) 3. 7 HP Storage Provisioning Manager 8 HP Virtual Connect Enterprise Manager 9 HP Insight Control virtual machine management 10 HP Systems Insight Manager Stop the HP Insight Management services listed in Table 3 in the order shown in the Stop order column. You can do this from the command prompt using the mxsync-svcutil script, which is located in \mxsync\bin.
Technical white paper | HP Insight Management 7.3 Stop order HP Insight Management component Service display name connecter 4 HP Matrix Operating Environment configuration management HP Logical Server Automation 5 HP Storage Provisioning Manager HP Storage Provisioning Manager Service Note: This service stops and starts the HP SPM Storage Module Service.
Technical white paper | HP Insight Management 7.3 The following HP Insight Management services may remain running during backup. HP Insight Management component Service display name HP Systems Insight Manager OpenSSH Server WMI Mapper Pegasus WMI Mapper Indications Service WMI Mapper Pegasus WMI Mapper Comments Indications sent while the WMI Mapper or HP Systems Insight Manager services are not running may be lost.
Technical white paper | HP Insight Management 7.3 Step Action 7 Schedule a Windows task to save the HP Matrix infrastructure orchestration network definition files between backups. This step is optional, but is recommended in environments where infrastructure orchestration services are frequently created and deleted. To perform a full system backup of the CMS: 1. By default, the Windows services startup type of HP Insight Management services is set to Automatic.
Technical white paper | HP Insight Management 7.3 Note: For HA CMS cluster configurations, HP Insight Management services configured as cluster resources should remain set to Manual. The command mxsync-svcutil auto will change the startup type only for HP Insight Management services that are not configured as cluster resources. 5.
Technical white paper | HP Insight Management 7.
Technical white paper | HP Insight Management 7.3 HP Insight Management component Service display name Service name HP System Management Homepage HP System Management Homepage SysMgmtHp HP Systems Insight Manager OpenSSH Server OpenSSHd WMI Mapper Pegasus WMI Mapper Indications Service WbemConsumer WMI Mapper Pegasus WMI Mapper WMI Mapper Partial backup 1.
Technical white paper | HP Insight Management 7.3 Table 7 describes the default installation directories for HP Insight Management 7.3. Although recommended, it is not necessary to save the log directories and files marked as Optional in Table 8. Notes: • You must use a file management tool that preserves file and directory permissions, such as the Windows Server Backup tool. • For HA CMS cluster configurations, some files on the boot disk of each cluster server node must also be included in the backup.
Technical white paper | HP Insight Management 7.3 Symbol Component HP Version Control Default installation directory Repository Note: This is the default location of the HP Version Control repository. For HA CMS cluster configurations, the repository is located on the shared disk (for example, V:\Program Files\HP\Version Control Repository).
Technical white paper | HP Insight Management 7.
Technical white paper | HP Insight Management 7.3 Directory or file Optional Description \known_hosts No The public SSH keys stored in the known_hosts file Note: This file may not exist. \logs\Alc*.log Yes HP Matrix infrastructure orchestration log files Note: These files may not exist. \logs\mx.
Technical white paper | HP Insight Management 7.3 Directory or file Optional Description \tomcat\ No System Management Homepage directory containing Tomcat configuration files, log files, executables, Java-based plug-ins, and working files produced by Tomcat. Note: This directory may not exist. \webapp\ No System Management Homepage webapp integration XML files \bin\hpvmm.
Technical white paper | HP Insight Management 7.3 Directory or file Optional Description \lbin\capadcollector.properties No HP Matrix Operating Environment Capacity Advisor node list property file \lbin\CapAdWrapperVariables.conf No HP Matrix Operating Environment Capacity Advisor variables configuration file \lbin\hp_cpdata_service.conf No HP Matrix Operating Environment Capacity Advisor service configuration file \lib\cppidb.
Technical white paper | HP Insight Management 7.3 Component Database HP Matrix Operating Environment capacity planning, configuration, and workload management gwlm HP Matrix infrastructure orchestration hpio HP Matrix infrastructure orchestration oo HP Matrix infrastructure orchestration HPMOEMetering HP Matrix recovery management lsdt Comments Important: The archived files and databases contain confidential information, including credential data.
Technical white paper | HP Insight Management 7.3 Notes: • To support automatic provisioning, HP Matrix infrastructure orchestration maintains a pool of available IP addresses for each network defined in infrastructure orchestration. After the restore, IP addresses allocated after the last backup, but before the catastrophic failure, will be incorrectly marked in the restore database as available, and will need to be corrected.
Technical white paper | HP Insight Management 7.3 Preparing your environment for restore Before performing a restore, use the following procedure to quiesce the environment: 1. If your environment is operational and the configuration is a federated CMS, follow step 1 in Preparing your environment for backup. 2. If your environment is operational, follow step 2 in Preparing your environment for backup. 3.
Technical white paper | HP Insight Management 7.
Technical white paper | HP Insight Management 7.3 Restoring your environment This section describes the steps to restore your environment from backup. Table 11 provides a high-level description of the restore and recovery steps. Table 11. Overview of the restore and recovery steps Step Action Preparing your environment for restore 1 If restoring a secondary CMS in an infrastructure orchestration federated CMS configuration, the detailed instructions provide additional steps.
Technical white paper | HP Insight Management 7.3 Completing the recovery process Changes to managed resources that occur after the backup but before the failure (referred to as post-backup activity) can affect the recovery process. Examples of post-backup activity include activating or deactivating a logical server or infrastructure orchestration service, deleting an infrastructure orchestration service or logical server, and adding or deleting a recovery management recovery group.
Technical white paper | HP Insight Management 7.3 3. After all mxsync synchronization phases have completed successfully, you can start the HP Insight Management services described in Table 9 in the reverse order listed in the Stop order column (with the exception of the Insight Control server deployment services, which should be started in the order listed). You can do this by using the mxsync-svcutil script as shown in Table 10.
Technical white paper | HP Insight Management 7.3 7. for the logical server, and then select Modify Logical Server. On the Storage tab, click the Modify button for the SPE. Click the Add Volume button, and then provide the details, such as the Storage Port WWN and LUN, for each missing volume.
Technical white paper | HP Insight Management 7.3 9. add a new server to the service, or delete the service and re-provision the service if there is only one server for the service. C. If a server was removed from an infrastructure orchestration service as a post-backup activity, the aggregated service status will be “Partial.” You can manually remove the server from the service to return the service to the proper state.
Technical white paper | HP Insight Management 7.3 References For more information about the topics discussed in this white paper, see the following: For HP Insight Management product documentation, go to http://www.hp.com/go/insightmanagement/docs/. For HP Matrix Operating Environment product documentation, go to http://www.hp.com/go/matrixoe/docs. For HP Matrix infrastructure orchestration product documentation, go to http://www.hp.com/go/matrixoe/docs.
Technical white paper | HP Insight Management 7.3 Appendix A: mxsync man page This appendix contains the HP Insight Management mxsync tool man page. Appendix B: Sample mxsync.log provides sample output from the mxsync command. To run mxsync, you must be logged on to the CMS using a Windows account with Administrator privileges; it must also be a valid Systems Insight Manager Administrator account. On Microsoft Windows Server 2008/2012, you must run mxsync as Administrator.
Technical white paper | HP Insight Management 7.3 2 Update RM state with underlying Matrix infrastructure orchestration service state for RM recovery groups with HP IO services. Caution: • When run in analysis-only mode, an unresolved issue in one phase can cause subsequent analysis phases to report incomplete or incorrect results. • When run in execution mode, all issues identified in a phase must be resolved before proceeding to the next phase.
Technical white paper | HP Insight Management 7.3 Note: If you have implemented a policy automatically restarting stopped services in your environment, this policy must be temporarily disabled to avoid restarting the services during the recovery process. Caution: Although selected services are started by the mxsync tool, executing operations that change the state of managed resources should be avoided until resynchronization is complete.
Technical white paper | HP Insight Management 7.3 If, as a post-backup activity, a VC Domain was removed from a VC Domain Group and re-added to the same or a different VC Domain Group, you must manually reissue the Remove from VC Domain Group operation, remove the external manager account (see the section "Removing an external manager account" in the VCEM User Guide), and reissue the Add to VC Domain Group operation.
Technical white paper | HP Insight Management 7.3 During the third phase, the mxsync tool runs the lsmanalyzer tool to compare the definitions of the catalog-based storage pool entries with the state of the volumes in SPM and in the managed arrays. At this time, you are asked to review the results of the analysis and to perform the recommended manual actions for any issues reported.
Technical white paper | HP Insight Management 7.3 Note: To support automatic provisioning, HP infrastructure orchestration maintains a pool of available IP addresses for each network defined in infrastructure orchestration. After restore, IP addresses allocated after the last backup, but before the catastrophic failure occurred, are incorrectly marked as available and must be fixed.
Technical white paper | HP Insight Management 7.3 If the mxsync tool encounters errors during the recovery management synchronization section, the console says to see the log file for additional information. If you do not see anything in the mxsync logs, please check the recovery management log file located at \logs\lsdt.error.log.
Technical white paper | HP Insight Management 7.3 Additional notes 1. 2. 3. 4. 5. 6. If a recovery group was deleted after backup, and an up-to-date recovery management export configuration file was not available, it is necessary to re-delete the recovery group. During the analysis step, you are given the opportunity to identify any post-backup deleted recovery groups. During the execution step, these recovery groups are deleted.
Technical white paper | HP Insight Management 7.3 Appendix B: Sample mxsync.log To illustrate the behavior of the mxsync tool, this appendix contains output from a sample mxsync run. Table 14 describes the changes that were made after the backup. Table 14. Pre-backup state and post-backup activity for the sample mxsync run Type VC Names Pre-backup state Post-backup state HP IO Service: TC1 HP IO service is created and activated. HP IO service is deactivated.
Technical white paper | HP Insight Management 7.3 Type Names VMM HP IO Service Name: TC11 Pre-backup state HP IO service is created and activated. Logical server name: TC11esx-net01_ls VMM Post-backup state HP IO Service Name: TC12 HP IO service is created and deactivated. Logical server name:TC12hv-net01_ls RM Recovery Group: RG1 LS-based recovery group is created with TC9esx-net01_ls. Recovery group is modified to add TC11esx-net01_ls, and export file is created.
Technical white paper | HP Insight Management 7.3 RESOLUTION: During the execution step, you will be asked to run HP SIM discovery tasks to discover the current datacenter environment, including Onboard Administrators, hypervisor host operating systems (for example, VMware ESX servers or Microsoft Hyper-V servers), and operating systems deployed on blades, VM guests and stand-alone servers. To run HP SIM discovery, connect to HP SIM and login as Administrator. Select "Discovery...
Technical white paper | HP Insight Management 7.3 Virtual Connect Enterprise Management section During this section, the restored VCEM database is resynchronized with the state of the VC Domains managed by VCEM. During the first phase, the mxsync tool scans the VC Domains managed by VCEM. If changes occurred after the backup that might cause the VCEM product resynchronization to fail, the mxsync tool recommends making changes to the restored VCEM database to resolve the identified issues.
Technical white paper | HP Insight Management 7.3 +---------------------------------------+ | Section 2 of 5 | | Virtual Connect Enterprise Management | +---------------------------------------+ Synchronizes VCEM with the state of the underlying VC Domains. **** Analysis: Resolve conflicting resource assignments. **** **** Section 2 of 5, phase 1 of 2 **** Update or remove VCEM resources that conflict with the underlying VC Domains.
Technical white paper | HP Insight Management 7.3 Mark VC profile TC6phy-net01_13cd40b106d addresses external: 50:01:43:80:02:A3:00:31, 50:01:43:80:02:A3:00:30, 50:01:43:80:02:A3:00:3F, 50:01:43:80:02:A3:00:3E, 00-21-5A-9B-00-30, 00-21-5A-9B-00-32, 00-21-5A-9B-00-31, 00-21-5A-9B-00-33.............................................[ACTION] ISSUE: The addresses used by the VC profile are either not assigned to a corresponding VCEM profile for the same domain or the VCEM profile is unassigned.
Technical white paper | HP Insight Management 7.3 During the second phase of the Virtual Connect Enterprise Management section, mxsync issues requests to VCEM to resynchronize each VC Domain managed by VCEM. Notes: • During the analysis step of phase 2, mxsync displays an ISSUE for each VC Domain managed by VCEM, stating that the VC Domain may need to be synchronized with VCEM. This is only a potential issue.
Technical white paper | HP Insight Management 7.3 Logical servers and associated SAN-based storage section During this section, the restored Logical Server Management (LSM) and HP Storage Provisioning Manager (SPM) databases are resynchronized with the state of the Virtual Connect profiles, virtual machines, and storage volumes on the managed devices.
Technical white paper | HP Insight Management 7.3 +--------------------------------------------------+ | Section 3 of 5 | | Logical servers and associated SAN-based storage | +--------------------------------------------------+ Refresh logical servers and associated SAN-based storage. **** Analysis: HP Storage Provisioning Manager Resources **** **** Section 3 of 5, phase 1 of 3 **** Analyze and, if necessary, recommend actions for synchronizing the state of HP Storage Provisioning Manager storage volumes.
Technical white paper | HP Insight Management 7.3 **** Execution: HP Storage Provisioning Manager Resources **** **** Section 3 of 5, phase 1 of 3 **** Starting the "HP Extensible Storage & Server Adapter" Service. This may take a few minutes.. The "HP Extensible Storage & Server Adapter" Service is running..........[OK] Place the "HP Storage Provisioning Manager Service" in recovery mode by editing the file "C:\Program Files (x86)\HP\Storage Provisioning Manager\state\ApplicationConfig.
Technical white paper | HP Insight Management 7.3 For the sample run, the changes made during the SPM recovery and the recommended actions from lsmanalyzer are summarized in Table 16. Table 16. Summary of SPM recovery actions Pre-backup SPM activity Post-backup activity None Volume8 is imported to SPM. Pre-SPM recovery state Phase 1 Phase 3 SPM recovery action lsmanalyzer recommended action SPM is not aware of the volume.
Technical white paper | HP Insight Management 7.3 For the sample run, the changes performed by the logical server refresh operation are summarized in Table 17. Table 17. Summary of logical server refresh actions Post-backup activity Pre-LSM refresh state LSM refresh action Deactivate infrastructure orchestration services VC-based TC1 and TC7 (expired). The state of the logical server is active in the restored Matrix OE database, but the profile is unassigned in the updated VCEM database.
Technical white paper | HP Insight Management 7.3 **** Analysis: Logical Server Resources **** **** Section 3 of 5, phase 2 of 3 **** Automatic synchronization of physical and virtual logical servers. The "HP Extensible Storage & Server Adapter" Service is already running..................................................................[OK] The "HP Storage Provisioning Manager Service" Service is already running..................................................................
Technical white paper | HP Insight Management 7.3 During the third phase of the Logical servers and associated SAN-based storage section, the lsmanalyzer tool is executed. This tool compares the definitions of the SAN catalog storage entries with the actual state of the managed resources. The user is asked to review the results of the tool and perform the recommended manual actions. After the manual actions have been completed, the lsmanalyzer tool verifies that all reported issues have been resolved.
Technical white paper | HP Insight Management 7.3 **** Execution: Logical Server Catalog Storage Pool Entry Resources **** **** Section 3 of 5, phase 3 of 3 **** At this time, you are asked to review the analysis results and perform any recommended actions. The results of the analysis are available at "C:\Program Files\HP\Systems Insight Manager\mxsync\data\lsmAnalyzer.130215032308.txt".
Technical white paper | HP Insight Management 7.3 For the sample run, the results of the lsmanalyzer tool analysis follow: ADVISORY: The lsmAnalyzer tool may report transient inconsistencies if operations are in progress while the analysis is performed. If unexpected issues are identified, run the analysis again after the operations have completed. Started analysis of storage volumes allocated to catalog-based SPEs. Checking SPM3.........................................................
Technical white paper | HP Insight Management 7.3 RESOLUTION: Delete storage volume "\Virtual Disks\SPM\Volume4" in storage array "" from the SPM catalog. This is necessary to avoid the storage volume from being reassigned to another resource. This can occur if, as a post-backup activity the storage volume was added to a newly created SPE and the SPE was associated to a logical server.
Technical white paper | HP Insight Management 7.3 HP Matrix infrastructure orchestration section During this section, the restored Matrix infrastructure orchestration database is updated. In the first phase, the mxsync tool analyzes the scheduled, pending approval, or in-progress requests.
Technical white paper | HP Insight Management 7.3 During the second phase, you are asked to identify services that were deleted after the backup. To help with this effort, the mxsync tool creates the file \mxsync\data\InfrastructureServices.txt, which contains a list of the infrastructure orchestration services defined in the restored database. Before performing the execution step, you are asked to edit the generated file, and mark with an asterisk (*) the services that were deleted.
Technical white paper | HP Insight Management 7.3 **** Analysis: Remove deleted services. **** **** Section 4 of 5, phase 2 of 4 **** HP Matrix infrastructure orchestration services in the restored database may have been deleted after the backup was taken. If so, in this phase you can delete these services from the restored database. The following infrastructure service(s) were found: Checking TC7 AVAILABLE, Lease End: 03/15/2013 06:10:36..........................
Technical white paper | HP Insight Management 7.3 Analysis completed successfully. You can choose to execute synchronization actions now, or stop the synchronization process. If the synchronization process is stopped, it can be restarted later. >>> Would you like to perform the actions now? (Y/N): y **** Execution: Remove deleted services. **** **** Section 4 of 5, phase 2 of 4 **** Checking C:\Program Files\HP\Systems Insight Manager\mxsync\data\InfrastructureServices.
Technical white paper | HP Insight Management 7.3 For the sample run, six services were created post-backup, and IP addresses were allocated to them at that time. IP address 15.199.225.29 was allocated to service TC4. IP address 15.199.225.31 was allocated to TC5. IP address 15.199.225.32 was allocated to TC6. IP address 15.199.225.33 was allocated to TC8. DHCP addresses were allocated to services TC11 and TC12.
Technical white paper | HP Insight Management 7.3 **** Analysis: Update allocated IP Addresses. **** **** Section 4 of 5, phase 3 of 4 **** HP Matrix infrastructure orchestration maintains pools of available IP addresses for each network. IP addresses allocated after the backup was taken are marked as free in the restored database. In this phase you can mark these IP addresses as in-use. Checking BR-VM Network 1 DHCP addresses in use...........................................
Technical white paper | HP Insight Management 7.3 Synchronizing database. Adding 1 DHCP addresses to network BR-VM Network. Adding IP address 15.199.225.26 to network HPNet. Adding IP address 15.199.225.30 to network HPNet. Database synchronization...............................................[OK] Adding Adding Adding Adding Adding 2 DHCP addresses to network IP address 15.199.225.29 to IP address 15.199.225.31 to IP address 15.199.225.32 to IP address 15.199.225.33 to BR-VM Network.....................
Technical white paper | HP Insight Management 7.3 Figure 2: Contents of IPAddresses.txt file # This file lists all the IP addresses allocated (marked as in use) by HP # Matrix infrastructure orchestration. # Specify additional IP addresses to also mark as in use.
Technical white paper | HP Insight Management 7.3 **** Analysis: Start HP Matrix infrastructure orchestration Windows **** **** services. **** **** Section 4 of 5, phase 4 of 4 **** HP Matrix infrastructure orchestration Windows services can be started when the synchronization process is complete. Once the services are up, all users will have access to their infrastructure services. Checking Windows Services. HP Matrix infrastructure orchestration Service status.............
Technical white paper | HP Insight Management 7.3 backup created service is no longer managed by infrastructure orchestration, when these resources are deleted, the IP address is not automatically returned to the Usable IP Address Space.
Technical white paper | HP Insight Management 7.3 In the example shown in Figure 3, IP address 15.199.225.33 and one DHCP address are returned to the infrastructure orchestration Usable IP Address Space. The contents of the DeleteIPAddresses.txt file are shown in Figure 4. Note: The HP Matrix infrastructure orchestration service must be stopped before running the iosync -IPDeletionTask command.
Technical white paper | HP Insight Management 7.3 Figure 4: Contents of the DeleteIPAddresses.txt file 68 # This file lists the additional IP addresses marked as in use by HP # Matrix infrastructure orchestration. # Specify the addresses to now mark as free. # # # # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # Network name: BR-VM Network # # # IP addresses already in use: # # DHCP addresses in use: 1 of 6. # Enter the number of DHCP addresses to remove. BR-VM Network.
Technical white paper | HP Insight Management 7.3 Matrix recovery management section During this final section, the restored HP Matrix recovery management database is updated. To reduce the effort required to re-create the post-backup recovery management configuration changes, you have the opportunity to use an exported recovery management configuration file to replace the existing configuration in the restored database.
Technical white paper | HP Insight Management 7.3 Determining starting configuration for Matrix recovery management synchronization. This may take a few minutes... Checking Recovery Group RG1......................................[INPUT] Applying synchronized configuration.............................
Technical white paper | HP Insight Management 7.3 The activation status of a recovery group set depends on the restored database or, if an export file was used, whether the export file was created on the local or remote CMS. You can change the status of a recovery group set by uncommenting the line and specifying yes or no in the Activated at Local Site field before proceeding to the execution phase. Figure 5: Contents of the mxsync_fixup.
Technical white paper | HP Insight Management 7.3 **** Analysis: Matrix recovery management configuration sync with Matrix **** **** infrastructure orchestration **** **** Section 5 of 5, phase 2 of 2 **** Analyzes each Matrix recovery management Recovery Group to ensure that the associated IO service is present in the MatrixIO database and it has the same primary status as found in the MatrixRM database.
Technical white paper | HP Insight Management 7.3 Appendix C: HP Insight Management backup files and directories This appendix contains the directories and files that contain user-changeable state and configuration data (see Table 8). This list was created using the default installation directory settings described in Table 7. The drive letter for your CMS installation may be different. C:\Documents and Settings\Administrator\.
Technical white paper | HP Insight Management 7.3 C:\Program Files\HP\Systems Insight Manager\known_hosts C:\Program Files\HP\Systems Insight Manager\logs\Alc1_0.0.log C:\Program Files\HP\Systems Insight Manager\logs\mx.
Technical white paper | HP Insight Management 7.3 Appendix D: mxsync-svcutil man page The mxsync-svcutil script (Figure 6) can be used to start, stop, and change the startup type of the HP Insight Management services described in this white paper. This script is packaged with the mxsync tool and is located in \mxsync\bin. The mxsync-svcutil script is cluster-aware and can be used when HP Insight Management is configured in an HA CMS cluster configuration.
Technical white paper | HP Insight Management 7.3 Appendix E: VCEM resynchronization actions Some VC activities, if performed after the backup, may require manual steps in order to synchronize the state of the VC Domain with the restored VCEM database.
Technical white paper | HP Insight Management 7.3 Figure 7: Using the VCEM VC Domains tab to view the current status of the VC Domain Missing External Manager Lock 3. After phase 2 execution is complete, you have the opportunity to repeat this phase. However, before you do, you must reissue the request to remove the VC Domain from the restore VCEM database.
Technical white paper | HP Insight Management 7.3 Domains managed by VCEM. In phase 3, you are asked to identify any IP addresses that are associated with these servers. VC domain added after backup If, as a post-backup activity, a VC Domain was added to a VCDG, after the VCEM database is restored from backup, the VC Domain is not defined as a member of the VCDG in the restored VCEM database. You must manually re-add the VC Domain to the VCDG.
Technical white paper | HP Insight Management 7.3 An example of the error follows: **** Execution: Domain synchronization **** **** Section 2 of 5, phase 2 of 2 **** This may take a few minutes ... Synchronizing VC Domain Val-Encl3-Vc ........ Synchronize VC Domain Val-Encl3-Vc in VCEM........................[ERROR] ERROR: Unable to synchronize VC Domain Val-Encl3-Vc Synchronizing VC Domain Matrix-Encl4-Vc ............................... Synchronize VC Domain Matrix-Encl4-Vc in VCEM........................
Technical white paper | HP Insight Management 7.3 D. E. F. Create the VC Domain Group from VCEM using the same settings as before. Add the same VC Domains to the VC Domain Group as before. If you have VC-based logical servers and storage pool entries in the portability group associated with this VC Domain Group, you must perform an LSM refresh. Select ToolsHP Matrix OE visualization in Systems Insight Manager. In the Virtualization Manager, select ToolsLogical ServersRefresh.
Technical white paper | HP Insight Management 7.3 Appendix F: gWLM configuration changes Skip this appendix if you are not using the CMS to manage gWLM on Integrity servers. If, as a post-backup activity, changes were made to the gWLM configuration, the changes must be reissued to synchronize the restored gWLM database with the configurations deployed on the gWLM managed systems. This appendix describes the steps required to perform the resynchronization. Table 18.
Technical white paper | HP Insight Management 7.3 Appendix G: SPM resynchronization actions This appendix contains supplemental information for recovering the SPM catalog and SAN catalog storage entries. If you are not using SPM or SPM-based SAN catalog storage entries for your logical servers, you can skip this appendix. SPM supports a management signature feature designed to help the Storage Administrator recover SPM volumes after a restore. Management signatures are supported for EVA and 3PAR arrays.
Technical white paper | HP Insight Management 7.3 bringing a volume out of quarantine. Table 18 provides a list of the signature states and the manual recovery steps. See the HP Storage Provisioning Manager (SPM) User Guide for additional information. 1. 2. 3. Before moving a volume out of quarantine, the array and pool for that volume must be removed from quarantine. A. On the Arrays page, right-click the array to remove from quarantine and select Change Quarantine.
Technical white paper | HP Insight Management 7.3 Signature state after recovery Description Manual recovery steps Service activation- level mismatch The service for this volume was reactivated to change the host presentation in post-backup activity. Update the service requirements to match the actual presentation state. Rewrite the management signature on the volume by right-clicking the selected volume; then, select Rewrite Volume Signature. Take the volume out of quarantine.
Technical white paper | HP Insight Management 7.3 Appendix H: Matrix infrastructure orchestration resynchronization In some cases, infrastructure orchestration may not be able to fully recover a server definition when changes are made after the backup. Matrix infrastructure orchestration resynchronization limitations • If, as a post-backup activity, a data disk was added to a physical server, this will result in the attachment of an additional storage pool entry.
Technical white paper | HP Insight Management 7.3 Notes: • HP recommends that the HP IO Administrator keep track of the load balancers being added to, modified, or removed from the HP IO inventory. This information will facilitate restoring the load balancer inventory. • If the administrator is unable to re-enter all post-backup load balancer changes in HP IO, the HP IO inventory will be out of sync with the load balancers. This will not cause harm to HP IO or the load balancers.
Technical white paper | HP Insight Management 7.3 Appendix I: HA CMS cluster configurations This appendix provides information for making full and partial backups of your Insight Management CMS. When the CMS is in an HA cluster configuration, there are some differences that you must consider. When stopping and starting Insight Management services as part of the backup or restore process, it is important to use mxsync-svcutil or the Failover Cluster Manager for most of these operations.
Technical white paper | HP Insight Management 7.3 When restoring the server-specific Insight Management data directories and files on the server that is not hosting the Insight Management clustered service, you must restart the HP System Management Homepage service after restoring the files. Table 20.
Technical white paper | HP Insight Management 7.3 Directory or file Optional Description C:\Program Files\The Open Group\WMI Mapper\server.pem No OpenPegasus WMI Mapper server certificate C:\Program Files\The Open Group\WMI Mapper\ssl.
Technical white paper | HP Insight Management 7.3 Appendix J: Unattended backup with mxquiesce You can use the mxquiesce command to allow in-progress tasks to complete, and to block new tasks from starting for the Insight Management components listed in Table 2. To perform a clean backup of Insight Management, no jobs or tasks should be running when the Insight Management services are stopped.
Technical white paper | HP Insight Management 7.3 Appendix K: Troubleshooting The mxsync tool times out before Systems Insight Manager starts successfully. By default, mxsync waits 15 minutes for the Systems Insight Manager Windows service to start before terminating. To change the wait period, set the variable init.hpsim.wait.minutes in the \mxsync\conf\mxsync.properties file to the preferred value.
Technical white paper | HP Insight Management 7.3 If you run lsmanalyzer from the command prompt, the following error is displayed: ADVISORY: The lsmAnalyzer tool may report transient inconsistencies if operations are in progress while the analysis is performed. If unexpected issues are identified, run the analysis again after the operations have completed. Started analysis of storage volumes allocated to catalog-based SPEs. Could not communicate with HP Storage Provisioning Managerervice....
Technical white paper | HP Insight Management 7.3 For more information www.hp.com/go/insightcontrol www.hp.com/go/insightmanagement www.hp.com/go/matrixoe www.hp.com/go/hpsim Call to action HP recommends backing up the CMS after making configuration changes to the Insight Management environment. Sign up for updates hp.com/go/getupdated Share with colleagues Rate this document © Copyright 2014 Hewlett-Packard Development Company, L.P.
