HP StorageWorks P9000 Replication Manager Software Configuration Guide Part number: TB584-96022 Eighth edition: April 2011
Legal and notice information © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface .............................................................................................. 11 1 Replication Manager system configurations and requirements ................ 13 Replication Manager system configurations .................................................................................. Configurations for open systems ........................................................................................... Configurations for mainframe systems ..............................
Adding a link menu to web client ............................................................................................... 46 hcmdslink command options ................................................................................................ 46 Creating a user-defined application file ................................................................................. 46 3 Setting up Application Agent ............................................................. 49 About Application Agent .......
Security management ....................................................................... 83 Network communications security ............................................................................................... Securing management server and client communications ......................................................... Securing communications within a single management server and between multiple servers ......... Server CA certificate setup ...................................................
Product references ................................................................................................................... 118 A Environment settings when using the Core CLI License ......................... 121 Overview ............................................................................................................................... Preparing to use Device Manager CLI ........................................................................................
Figures 1 Single site configuration in open systems .................................................................... 14 2 Two-site configuration in open systems ....................................................................... 15 3 Three-site configuration in open systems ..................................................................... 16 4 Mainframe configuration using HP StorageWorks P9000 for Business Continuity Manager Software (BCM) .......................................................
Tables 1 System components (for open systems) ....................................................................... 16 2 Overview of mandatory software (for open systems) .................................................... 18 3 System components (for mainframe systems) ............................................................... 20 4 Overview of mandatory software for mainframe management ...................................... 21 5 System components (for replica management) ...........................
33 Memory size and amount of output log information ..................................................... 77 34 List of properties in the serverstorageif.properties file .................................................... 77 35 List of properties in the bcmif.properties file ................................................................ 78 36 List of properties in the agentif.properties File .............................................................. 79 37 List of properties in the appagentif.
Preface This document describes the installation and configuration process for HP StorageWorks P9000 Replication Manager.
Preface
1 Replication Manager system configurations and requirements This chapter describes the system configurations, system components, and system requirements of Replication Manager. To help you understand systems that use Replication Manager, this chapter also describes the flow of control and data between programs. Replication Manager system configurations This section describes the basic system configurations for Replication Manager.
Figure 1 Single site configuration in open systems 14 Replication Manager system configurations and requirements
Figure 2 Two-site configuration in open systems Configuration Guide 15
Figure 3 Three-site configuration in open systems The following tables list and describe system components for each type of system and provide an overview of the software components. Table 1 System components (for open systems) System components Management client 16 Software included in system components Description Web browser A management client is a computer on which a Web browser is used to run web client for Replication Manager. Replication Manager runs on the management server.
System components Software included in system components Description A management server provides management information in response to requests from management clients. Replication Manager and Device Manager server (a prerequisite program of Replication Manager) are installed on the management server. Management server Replication Manager Device Manager server If multiple sites are used, a management server is required for each site.
System components Software included in system components Description Microprograms Storage system Note: If necessary, register licenses for products (such as Continuous Access Journal or Business Copy). A storage system is an external storage system connected to a host. Table 2 Overview of mandatory software (for open systems) Software Description Used to centrally manage the replication of storage system volumes in large-scale system configurations.
Figure 4 Mainframe configuration using HP StorageWorks P9000 for Business Continuity Manager Software (BCM) Configuration Guide 19
Figure 5 Mainframe configuration using Device Manager server only or P9000 mainframe agent The following tables list and describe system components for each type of system and provide an overview of the software components. Table 3 System components (for mainframe systems) System components Management client Management server Software included in system components Description Web browser A management client is a computer on which users use a Web browser to run web client for Replication Manager.
System components Software included in system components Description Usually, a host is the computer on which the application programs are installed. HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent is installed on a host. Note: If Device Manager server is not registered as an information source, or P9000 mainframe agent is being used, the information displayed by web client is limited.
Software Description Device Manager server Used to achieve integrated management of disk resources and for configuring storage system hardware. You can run and manage a system consisting of multiple storage systems. For details about Device Manager server, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Administrator Guide. Used to control copy group configurations located on storage systems from a host.
systems, without depending on mainframe host types. The minimum interval of automatic refresh for this configuration is 30 minutes. TIP: The status of FC and XRC copy pairs are not supported at this time. Configurations for replica management The following figure depicts a composite configuration where copy pairs and application replicas are managed.
Figure 7 Example system configuration managing copy pairs and application replicas (SQL Server) NOTE: Depending on the configuration, backup servers are not required for SQL Server configurations. The following tables describe the system components that are unique to replica management and the host configurations that are counterparts to pair management components.
System components Software included in system components Description Backup server Application Agent A host where the secondary volumes are located. Application Agent is also installed on the backup server. Table 6 Overview of mandatory software (for replica management) Software Description Application Agent Application Agent allows Replication Manager to perform database backup and restore operations.
Figure 8 Standby Replication Manager (multi-platform, multi-site configuration) System requirements This section describes the system requirements for management servers, management clients, pair management servers, hosts, and storage systems that make up a Replication Manager system. Each computer must be connected to a TCP/IP network and a static IP address is required for the management server.
NOTE: When using IPv6, both IPv4 and IPv6 must be enabled on the management server. You can use IPv6 addresses only if they are global addresses. Table 7 Windows OS and programs for a management server Windows operating system Prerequisite programs Windows Server 2003 x64 Edition SP2 • Runs in the 32-bit emulation mode • Also runs as a guest OS of Windows Server 2008 Hyper-V and V2 • Also runs under VMware ESX/ESXi Server 3.x and 4.
Prerequisite programs Windows operating system Windows Server 2008 x64 Edition • Runs in the 32-bit emulation mode Supports IPv4 and IPv6 connections • Also runs as a guest OS of Windows Server 2008 Hyper-V and V2 • Also runs under VMware ESX/ESXi Server 3.x and 4.
Item Minimum requirement Recommended specification Disk size 750 MB 750 MB to 6.6 GB (depends on the number of resources managed) The disk size required for operations of the (required) Device Manager server must also be taken into account. For details about the server specifications for Device Manager server, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Administrator Guide. NOTE: These requirements also apply to installing Replication Manager on a virtual system.
Product or component name Virtual memory requirement (MB) Provisioning Manager (Included in Device Manager) Tiered Storage Manager 600 Replication Manager If Application Agent is installed on the management server, you need to secure an additional 128 MB of virtual memory for Application Agent.
Maximum number of resources supported The maximum number of resources that can be managed by Replication Manager depends on the setting specified for the memory heap size (Small, Medium, or Large). Set an appropriate memory heap size, depending on the maximum number for each resource. NOTE: If you are using a Windows 32-bit environment, you cannot set “Large” as a memory heap size.
system. For mainframe systems, the maximum number of LDEVs is based on the total number of LDEVs in all managed storage systems. The following table shows the maximum number of LDEVs.
Log data and number of copy pairs The amount of log data depends on the number of copy pairs to be managed. You can change the maximum number of log files and the maximum data size for each log file. For details, see “Properties in the logger.properties file” on page 73. System requirements for the management client The following table lists the supported operating systems and Web browsers for a management client that allows you to use web client.
Required memory for management clients The minimum required memory size for a management client for all operating systems is at least 512 MB. System requirements for hosts and pair management servers This section describes the requirements for hosts and pair management servers. Requirements for open systems The following table shows the requirements for hosts and pair management servers.
Requirements for operating Replication Manager at multiple sites If you operate Replication Manager at multiple sites, you need to specify the settings so that the IP addresses of management servers and pair management servers can be determined from their host names (that is, name resolution can be performed).
NOTE: If you want to use an IPv6 connection or HTTPS (SSL) communication between RepMgr and BCM, you must set up the IBM HTTP Server (IHS). For the requirements for HP StorageWorks P9000 for Business Continuity Manager Software, see the HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide. For the requirements for P9000 mainframe agent, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Mainframe Agent Installation and Configuration Guide.
Figure 9 Data collection (open systems) Acquiring configuration and license information Replication Manager acquires the following information via Device Manager server: • Copy pair configuration information • Volume configuration information (including the command device, pool volumes, and journal volumes) • License information for the volume replication functionality Device Manager server stores information acquired from storage systems, while Replication Manager stores information acquired from Device Ma
Replication Manager issues a request to Device Manager Agent to acquire performance information (such as the sidefile usage rate, pool volume usage rate, and write delay time (C/T delta)). In turn, Device Manager Agent uses RAID Manager to obtain the data from the storage system. Creating and deleting copy pairs and changing copy pair statuses Replication Manager issues a request to Device Manager Agent to create and delete copy pairs or to change the status of copy pairs.
Replication Manager issues a request to HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent to acquire performance information from the storage system (such as the sidefile usage rate, journal volume usage rate, pool volume usage rate, and write delay time (C/T delta)). The journal volume usage rate is acquired as described in Acquiring license information.
Replication Manager system configurations and requirements
2 Setting up Replication Manager This chapter explains how to set up and configure Replication Manager. Overview This section is an overview that lists all the tasks that need to be performed to set up and configure Replication Manager. To set up and configure Replication Manager: 1. On the management server where Replication Manager is installed, prior to installation, you must back up the databases of other P9000 Command View AE suite products in use.
Figure 11 Infrastructure configuration workflow Open systems environment To configure the required infrastructure for Replication Manager for an open system: 1. Install Device Manager server on the management server. For details, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Installation Guide.
2. Add all resources (storage systems) to Device Manager. Add to Device Manager the resources (storage systems) that are to be managed by Replication Manager. For details about adding storage systems to Device Manager, see HP StorageWorks P9000 Command View Advanced Edition Suite Software Help or the HP StorageWorks P9000 Command View Advanced Edition Suite Software CLI User Guide. 3. Install RAID Manager on the pair management servers.
Mainframe systems environment To configure the required environment for Replication Manager for a mainframe system: 1. Install Device Manager server on the management servers. For details about how to install and set up Device Manager, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide. If necessary, also see the following manuals: 2.
3. After installation of HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent, you must specify the information required for linking with Replication Manager. For HP StorageWorks P9000 for Business Continuity Manager Software, you must configure BCM as follows: • • • • Allocate a dataset for a disk configuration definition file. Allocate a dataset for a copy group definition file. Set a route list (when using a remote command device).
Adding a link menu to web client In web client, you can register a link to any Web application or Web page (including links to Device Manager servers used as information sources). Registering links adds Links menu items to the Go menu in web client global tasks bar area. To register or delete a link, execute the hcmdslink command, as follows.
Item Description @URL startup-URL Specifies the URL to be started from web client. Use no more than 256 bytes. Note: In IPv6 environments, specify a host name instead of an IPv6 address. @DISPLAYNAME display-name-inlinks-dialog-box Specifies the link name to be displayed in the Links dialog box. Specify Unicode characters in the range U+10000 to U+10FFFF, using no more than 80 characters. If you do not specify this item, the value specified in the @NAME line is used as the link name.
Setting up Replication Manager
3 Setting up Application Agent This chapter describes the Replication Manager Application Agent, the system requirements it demands, and how to install the software on backup servers and database servers. About Application Agent Application Agent extends the functionality of Replication Manager to include application awareness, which allows application resources to be managed using the Replication Manager interface.
Creating and restoring database replicas Application Agent creates and restores replicas of storage groups (databases) using the volume replication function in the storage system to perform high-speed disk-copying operations. A storage group is a group containing one or more MS Exchange 2003/2007 information stores. Storage groups can be used to manage multiple information stores at the same time.
Managing generations Application Agent can associate multiple secondary volumes with a single primary volume. (These secondary volumes are referred to as generations.) When selecting a secondary volume for a backup, you can either select it manually or have Application Agent automatically rotate the volumes in the same way that tape backups are re-used (local backups only).
Host OS and database server requirements The following tables list the operating systems, backup-server combinations, and database versions supported by Application Agent.
Database server OS Windows Server 2008 no SP or SP1 (64bit) Windows Server 2008 SP2 (64-bit) SQL Server version Backup server OS Windows Server 2008 no SP or SP1 (64-bit) Windows Server 2008 SP2 (64-bit) Windows Server 2008 no SP or SP1 (64-bit) Windows Server 2008 SP2 (64-bit) Windows Server 2008 R2 no SP or SP1 Windows Server 2008 no SP or SP1 (IPF) Windows Server 2008 SP2 (IPF) Windows Server 2008 R2 no SP or SP1 Windows Server 2008 no SP or SP1 (IPF) Windows Server 2008 SP2 (IPF) Windows Server 2
NOTE: Application Agent does not support a combination of SQL Server 2008 and Windows Server 2008 (x86) (because a 64-bit OS is expected to serve as the basic environment for this combination). Server requirements The following are the requirements and precautions for the database and backup servers.
TIP: It is not necessary to perform this operation if you are using Exchange Server 2007 or later. Environment variables Do not specify HORCMINST or HORCC_MRCF in a system environment variable. Also, do not specify HORCM_CONF or HORCMPERM in a system environment variable or a user environment variable. Application Agent versions on database and backup servers The same version of Application Agent must be installed on database and backup server pairs. Do not, for example, install version 6.
When reinstalling Application Agent When Application Agent is uninstalled, configuration files might remain. Before re-installing Application Agent, you should manually delete the entire directory where Application Agent was installed. Maximum number of Application Agent instances The maximum number of Application Agent instances that can be registered is 128.
Service name Displayed name Prerequisite condition for startup COMSysApp COM+ System Application Manual or Automatic MSDTC Distributed Transaction Coordinator Manual or Automatic If you attempt to install RM Shadow Copy when these Windows services are not set to their default settings, the VSS Provider service will not be registered as a Windows service.
Virtual environments supported by Application Agent This section describes the virtual environments supported by Application Agent. VMware ESX/ESXi Server Application Agent supports a Windows environment that functions as a guest OS. If provided as a guest OS of the virtual server products, VMware ESX/ESXi Server 3.x and 4.x are also supported. The following notes apply: • Be sure to apply Update 4 when linking VMware ESX Server 3.5 or VMware ESXi Server 3.5 to Exchange Server.
Windows Server 2008 Hyper-V Application Agent supports a Windows environment that is run as a guest OS of Windows Server 2008 Hyper-V. The following tables list the scope of support for each Application Agent product.
For Windows 64-bit edition: %ProgramFiles(x86)%\HDVM\HBaseAgent\ If Device Manager Agent is pre-installed separately, Common-Agent-Component-installation-folder is defined as follows: folder-specified-by-HDvM-Agent-installer\HBaseAgent NOTE: When using Device Manager Agent on VMware 4.x, it is necessary to confirm the prerequisite combination of Device manager server and Device Manager Agent.
NOTE: When base.refreshdginfo.exec is set to zero, Replication Manager cannot manage copy groups defined in storage (device groups). Installing Application Agent NOTE: When performing installation or uninstallation, the system drive must have 100 MB or more of free disk space to allow the installer to create temporary files. To install the agent, follow this procedure: 1.
12. You will be prompted to choose a destination location in the Destination Folder field in the Choose VSS Provider Destination window. Use the Browse... button to navigate to your selection. Then click Next. 13. You will now be prompted whether you would like to register the Application Agent to the allowed program configuration of your firewall in order for the agent to work while that firewall is activated. Select the Yes or the No button in the Windows Firewall Settings window to set your choice.
1. Add the Copy Controller service to the list using this command: Application-Agent-installation-folder\DRM\bin\util\drmaddfwlist.bat 2. Add Common Agent service to the list using this command: Application-Agent-installation-folder\bin\firewall_setup.
If Device Manager Agent is not installed, you must manually start the P9000 RAID Manager instance on both the backup and database servers before carrying out replica operations. (If P9000 RAID Manager is not started, the replica operation will fail.) Starting and stopping P9000 RAID Manager Application Agent automatically starts and stops the local P9000 RAID Manager instance as needed.
Sample VBScript file NOTE: CHR(34) indicates a double quotation mark ("). When Application Agent-installation-folder does not contain any spaces, you do not need to specify CHR(34). The following is the specification when there are no spaces: "C:\drm\bin\drmjobsch.exe" & " -recover -hostname virtual-server-name" For details on the specification method, consult your VBScript documentation. 'Script-Level Global Variables Resource.
Application status log size = current file capacity + 3.8 * number-of-Application-Agent instances Changing Application Agent port numbers TIP: The port number used for communication between Application Agent instances (backup and database servers) can be changed during Application Agent setup (the default is 22300). If this port number has already been used, you must register the port number into the Windows Services file as DRMVSSServer.
The services associated with Application Agent are normally started and stopped automatically on the database or backup server where the agent is installed. Should you need to start or stop them manually, use the commands described in the sections that follow (Administrator privileges are required).
Property Description agent.logger.MaxBackupIndex The maximum number of log files created in Replication Manager. When the number of log files reaches this value, the existing files are reused, starting with the oldest file. Specifiable values: 1 to 20 (files) Default value: 10 The maximum size of a single Replication Manager log file. This value must be specified in bytes, kilobytes, or megabytes. If the specified value is not followed by KB or MB, the size is assumed to be in bytes.
4 Operating the management server This chapter describes the Replication Manager settings and the operating procedures, including how to start and stop Replication Manager and how to back up and restore the databases. About executing commands on the management server This section includes information related to the execution of commands that are required for Replication Manager operation.
Starting Replication Manager To start Replication Manager, start HP StorageWorks P9000 Command View AE Common Component by executing the following command. Select Start > All Programs > HP StorageWorks P9000 Command View AE >Device Manager > Start Server with Common Services. When you execute the command, the services of other HP StorageWorks P9000 Command View AE Suite products are also started.
KAPM06441-I The HiRDB service has already stopped. Changing settings in the properties files This section describes the settings in the properties files used by Replication Manager and how to change them. Use a text editor to alter parameters in the properties files. After making changes, you must do the following: • Restart Replication Manager. To do this, you must first stop and then start the services. For details, see “Starting and stopping Replication Manager” on page 69.
File serverstorageif.properties Property Default value (unit) logger.MaxBackupIndex 6 (files) logger.MaxFileSize 20MB logger.DB.loglevel 20 logger.DB.MaxBackupIndex 6 logger.DB.MaxFileSize 20MB logger.RefreshConfig.enabled true logger.RefreshConfig.MaxBackupIndex 3 (files) logger.RefreshConfig.MaxFileSize 10MB logger.UserOperation.enabled true logger.UserOperation.MaxBackupIndex 5 (files) logger.UserOperation.MaxFileSize 10MB logger.RefreshStatus.enabled true logger.
File Property Default value (unit) hdvmagtif.connectTimeout 30 (seconds) hdvmagtif.responseTimeout 3600 (seconds) hdvmagtif.MaxPollingCount 50 (times) hdvmagtif.PollingInterval 30 (seconds) agentif.connectTimeout 30 (seconds) agentif.responseTimeout 3600 (seconds) hdvmagtif.connectTimeout 30 (seconds) hdvmagtif.responseTimeout 3600 (seconds) hdvmagtif.MaxPollingCount 50 (times) hdvmagtif.PollingInterval 30 (seconds) appagentif.connectTimeout 30 (seconds) appagentif.
Property Description The threshold value for the output level of the OS event log that is output using Replication Manager. Messages containing values that are equal to or less than this value are output to the log file. logger.sysloglevel Specifiable values: 0, 10, 20, and 30 (in decreasing order of importance from left to right). Default value: 0 logger.MaxBackupIndex The maximum number of log files created in Replication Manager.
Property logger.RefreshConfig.MaxBackupIndex Description Maximum number of backup files for a configuration update log file. Specifiable values: 1 to 32 (files) Default value: 5 Maximum size of a configuration update log file. This value must be specified in bytes, kilobytes, or megabytes. If the specified value is not followed by KB or MB, the size is assumed to be in bytes. logger.RefreshConfig.
Property Description Maximum number of application configuration log backup files. logger.AppConfig.MaxBackupIndex Specifiable values: 1-32 (files). Default value: 3 Maximum size of the application configuration log file. logger.AppConfig.MaxFileSize Specifiable values: 1-2047 (MB). Default value: 10 Log function on/off switch for the application configuration log. logger.AppConfig.enabled Specifiable values: true or false.
NOTE: The default values in the logger.properties file assume 6,000 pairs in an open system and 40,000 pairs in a mainframe system. Table 33 Memory size and amount of output log information Amount of log data to be retained (MB) Memory heap size Transmission logs Trace log Database log Small 120 Medium Large Configuration update log User operations log Pair status update log 120 50 50 20 130 170 70 50 30 140 230 100 50 30 Properties in the serverstorageif.
Properties in the bcmif.properties file The bcmif.properties file is used to specify the values of properties related to the interface between Replication Manager and HP StorageWorks P9000 for Business Continuity Manager Software or between Replication Manager and P9000 mainframe agent. The following table describes the available properties and settings. Table 35 List of properties in the bcmif.properties file Property Description bcmif.
these values. To change the values, you need expert knowledge of Device Manager Agent. The following table describes the available properties and settings. Table 36 List of properties in the agentif.properties File Property agentif.connectTimeout Description The amount of time Replication Manager waits to connect to a Device Manager Agent when collecting copy pair statuses. If 0 is specified, Replication Manager waits until a connection is established without timing out.
these values. To change the values, you need expert knowledge of Application Agent. The following table describes the available properties and settings. Table 37 List of properties in the appagentif.properties File Property appagentif.connectTimeout Description The amount of time Replication Manager waits to connect to an Application Agent when collecting configuration statuses. If 0 is specified, Replication Manager waits until a connection is established without timing out.
Property base.taskscheck.mf.maxcount Description The maximum number of times that Replication Manager checks whether a task related to a mainframe copy pair operation has finished. If 0 is specified, there is no limit. Specifiable values: 0 to 100 (times) Default value: 0 base.repositry.synchronize.interval Interval at which the HDvM (HP StorageWorks P9000 Command View Advanced Edition software) database synchronization function performs a check.
Operating the management server
5 Security management This chapter explains security functions that can be used in Replication Manager. Network communications security To provide security for the communication routes used by Replication Manager, you can use the HTTPS protocol to encrypt communications.
Figure 12 Communication routes used by Replication Manager 84 Security management
Figure 13 Communication routes used by Replication Manager The following two types of HTTP communication routes are also used: • Between Replication Manager (on the management server) and a Device Manager Agent (on a pair management server) • Between Replication Manager (on the management server) and P9000 mainframe agent If a firewall is installed for the network, set it up to allow communication with Replication Manager.
Securing communications within a single management server and between multiple servers Replication Manager can use SSL to encrypt network transmissions between Replication Manager and BCM Agent (IBM HTTP Server) or Device Manager server. To configure the connection to use SSL, follow this procedure: 1. Determine if it is necessary to register a certificate. This process is described in “Server CA certificate setup” on page 86. 2. Set up SSL on Device Manager server or the BCM host.
Figure 14 Deciding whether a certificate requires registration The tasks outlined in the flowchart are as follows: 1. “Checking the truststores” on page 87 to determine if the certificate has already been registered. 2. If the certificate has not been registered, follow the procedure for “Importing a certificate into the jssecacerts truststore” on page 87.
• If there are multiple certificate files, specify an alias that has not been used in jssecacerts to import the certificate file. • Follow these restrictions for truststores, the truststore file name, and the password for the hcmdskeytool or keytool utility: • Do not use the following symbols in the file name: :,;*?"<>| • Specify the file name as a character string of no more than 255 bytes. • Do not include double quotation marks (") in a unique name in the truststore or in the password.
Description of category Audit event Severity Message ID SSO server stop 6 KAPM00092-I Table 40 Audit events for the Authentication category Description of category Administrator or end user authentication Automatic account lock HP SIM linkage Audit event Severity Message ID Successful login 6 KAPM01124-I Successful login (logged in to an external authentication server) 6 KAPM02450-I Failed login (incorrect user ID or password) 4 KAPM02291-W Failed login (logged in as a locked user) 4
Description of category Audit event Severity Message ID KAPM07358-E KAPM07360-E KAPM07368-W SSO authentication Failed SSO authentication KAPM07372-E 4 KAPM07376-E KAPM07377-E KAPM07423-E KAPM07424-E Table 41 Audit events for the ConfigurationAccess category Description of category Audit event Severity Message ID Successful user registration 6 KAPM07230-I Failed user registration 3 KAPM07240-E Successful user registration 6 KAPM07241-I Failed user registration 3 KAPM07242-E Successfu
Description of category Audit event Severity Message ID Successful account lock1 6 KAPM07235-I Failed account lock 3 KAPM07240-E Successful account lock release2 6 KAPM07236-I Failed account lock release 3 KAPM07240-E Successful authentication method change 6 KAPM02452-I Failed authentication method change 3 KAPM02453-E Authentication group addition (GUI) Successful addition of an authorization group 6 KAPM07247-I Authorization group addition (GUI) Failed addition of an authorizat
Description of category Audit event Severity Message ID Failed backup using the hcmdsbackups command 3 KAPM05562-E Successful full restore using the hcmdsdb command 6 KAPM05563-I Failed full restore using the hcmdsdb command 3 KAPM05564-E Successful partial restore using the hcmdsdb command 6 KAPM05565-I Failed partial restore using the hcmdsdb command 3 KAPM05566-E Successful data output using the hcmdsdbmove command 6 KAPM06543-I Failed data output using the hcmdsdbmove command 3 K
Description of category Resource group creation (GUI or CLI) Audit event Severity Message ID Successful resource group creation 6 KAPM02670-I Failed resource group creation 3 KAPM02675-E Successful resource group deletion 6 KAPM02631-I Failed resource group deletion 3 KAPM02636-E Successful resource group deletion 6 KAPM02671-I Failed resource group deletion 3 KAPM02676-E Successful resource group property editing 6 KAPM02634-I Failed resource group property editing 3 KAPM02639-E
Description of category Audit event Severity Failed to update the configuration definition file after deleting the pair. 4 Message ID KAVN10004-W KAVN10005-W KAVN10012-I Creation, editing, deletion, or distribution of the disk configuration definition file has started. 6 KAVN10015-I KAVN10018-I KAVN10021-I KAVN10013-I The disk configuration definition file was successfully created, edited, deleted, or distributed.
Description of category Audit event Severity Message ID Secondary volume hiding operation Canceling of a secondary volume hiding operation failed. 3 KAVN10078EKAVN10084-E KAVN10031-I Creation, editing, execution, canceling, or deletion of a task has started. KAVN10034-I 6 KAVN10037-I KAVN10040-I KAVN10043-I KAVN10032-I Creation, editing, execution, canceling, or deletion of a task has succeeded.
Description of category Audit event Severity Message ID Acquisition of replica information has finished. 6 KAVN10068-I Acquisition of replica information has failed. 3 KAVN10069-E Replica deletion has started. 6 KAVN10070-I Replica deletion has finished. 6 KAVN10071-I Replica deletion has failed. 3 KAVN10072-E Notes: 1. If an account is locked because the authentication method was changed for a user whose password is not set, this information is not recorded in the audit log. 2.
6 Troubleshooting This chapter describes how to handle the errors that might occur during operation of Replication Manager. Overview This chapter describes what to do if a problem occurs: • If a problem occurs with Application Agent (including installation and removal), see “Troubleshooting Application Agent operations” on page 100.
Figure 15 Sequence of actions to take if a problem occurs 1. Check the displayed messages for information about the problem and correct the error. If the message RPM-00824 or KAVN01281-E is displayed, take action as described in “Troubleshooting detailed message RPM-00824” on page 104. 2. Check the messages output to the Replication Manager event log and correct the error. For details on how to view the event log data, see the HP StorageWorks P9000 Replication Manager Software User Guide. 3.
• • • • • • • Trace log files for installation or uninstallation Version information files Properties files License command log files Files that contain license information Files related to the database Service pack log files NOTE: Observe the following precautions with commands: • Do not execute the cvxpaegetlogs command more than once at the same time. Also, do not execute this command and the hcmdsdbmove or hcmdsdbclustersetup command at the same time.
Argument Description P9000-Command-ViewAE-Suite-productname Specifies the name of the product from which maintenance information will be collected. If this option is omitted, information is collected from all P9000 Command View AE suite products installed on the management server (which may consume a great deal of disk space).
• Collecting support information with the hrpmap_getras command, page 103 TIP: When collecting event log information to diagnose a problem on the host where Application Agent is installed, be sure to collect maintenance information for the Replication Manager server as well. This will help identify problems caused by communication errors between Application Agent and the server. For more information, see “Collecting maintenance information” on page 98.
Output format The formats of data output to the trace log files are as follows: Format 1 yyyy/mm/dd hh:mm:ss Format 2 The format of Windows Installer logs Windows Installer log data is output from the Application Agent installer. An example of output log data is as follows: 2009/10/02 05:56:22 Windows Installer logging started.=== Logging started: 2009/10/02 5:56:20 ===Action start 5:56:20: INSTALL.Action start 5:56:20: AppSearch.
Collecting support information with the hrpmap_getras command The hrmap_getras command collects the Application Agent configuration and log files necessary for problem analysis. The command is located on hosts where Application Agent is installed and is invoked as follows: C:\Common-Agent-Component-installation-folder\bin\hrmap_getras data-collection-folder If you do not specify a data-collection folder, the files are placed in the working directory.
Files Description drm_output.log Location copied from drm_output.log.old Application Agent logfiles rm_pp_trace[1-16].log Application Agent trace log files drm_inst.log Application Agent installation trace log files all Dictionary map files Common-Agent-installationfolder\db Schedule-related log files For physical server: CommonAgent-installation-folder\ scheduleFor virtual server:cluster path specified in sch.
1. Use the following command to output the contents of the database into files. installation-folder-for-P9000-Command-View-AE-Common-Component\bin\hcmdsdbmove /export /datapath data-input-and-output-destination-folder NOTE: Do not execute the hcmdsdbmove command more than once at the same time. Also, do not execute this command and the cvxpaegetlogs command at the same time. 2.
NOTE: This procedure assumes that the HP StorageWorks P9000 Command View AE Common Component service is already running. Procedure on the executing node 1. On the executing node, make sure that the HP StorageWorks P9000 Command View AE Common Component service is online, and that the executing node currently owns the service and shared disk. 2. From the Start menu, choose Settings, Control Panel, Administrative Tools, and then Cluster Administrator.
6. Move the database onto the shared disk. NOTE: This step is unnecessary if other P9000 Command View AE suite products have been set up in a cluster configuration. If there are not any P9000 Command View AE suite products in a cluster configuration on the same host, execute the command shown below. This command changes the port number of the port used by HiRDB to the default port number (23032).
NOTE: Do not execute the hcmdsdbclustersetup command more than once at the same time. Also, do not execute this command and the cvxpaegetlogs command at the same time. This example shows how to execute the hcmdsdbclustersetup command: "C:\Program Files\CVXPAE\Base\bin\hcmdsdbclustersetup" /createcluster /databasepath R:\re_creating_db /exportpath C:\storing_data /auto 7.
4. Move the database to the shared disk. NOTE: This step is unnecessary if other P9000 Command View AE suite products have been set up in a cluster configuration. If there are not any P9000 Command View AE suite products in a cluster configuration on the same host, execute the command shown below. This command changes the port number of the port used by HiRDB to the default port number (23032).
Common Component and starts HiRDB. After command execution, both P9000 Command View AE Common Component and HiRDB will not be running. NOTE: Do not execute the hcmdsdbclustersetup command more than once at the same time. Also, do not execute this command and the cvxpaegetlogs command at the same time. This example shows how to execute the command: "C:\Program Files\CVXPAE\Base\bin\hcmdsdbclustersetup" /createcluster /databasepath R:\re_creating_db /exportpath C:\storing_data /auto 5. 6. 7.
Items to be checked on the pair management server This section describes how to make sure that the settings in the configuration definition files for Device Manager Agent and RAID Manager are correct: 1. Installation of Device Manager Agent, page 111 2. Link between Device Manager server and Device Manager Agent, page 111 3. Properties of Device Manager Agent, page 111 4.
Items to be checked from Device Manager web client This section describes how to check information about hosts (pair management servers) that are managed by Device Manager using Device Manager web client: 1. Recognition of Device Manager Agent, page 112 2. Recognition of the command device, page 112 3. Recognition of the replication configuration, page 112 For details about Device Manager web client, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Online Help.
If the button is not activated or the information is not displayed, refresh the storage system information. If it cannot be updated, make sure that the system configuration and specified settings in the RAID Manager configuration definition file are correct.
TIP: Even if Replication Manager appears to recognize the backup server as a pair management server, you should still confirm that the RAID Manager instance on the backup server is running if the following conditions are true: • The configuration is a cluster configuration. • The backup server contains the configuration definition file on the secondary machine, and no primary configuration file exists.
1. Execute the following command for each of the *.edb and *.stm files to be restored, and record the leftmost numeric values displayed for Last Consistent: Exchange-installation-folder\bin\eseutil /mh file-name-for-restoration 2. The minimum value among these recorded values is the Last Consistent log number. Move any transaction log with a number smaller than this value to a different folder. For example, when the Last Consistent log number is 1ab, the transaction log files E0x00001.
4. For each secondary volume whose disk status is Online, perform the following procedure: 1. Enter select disk disk-number. 2. The following message is displayed: Disk disk-number is now the selected disk. 3. Enter offline disk. The following message is displayed: DiskPart successfully offlined the selected disk. 5. To display the current status of the disks, enter list disk. Make sure that the disk statuses of the secondary volumes are Offline in the Status column. 6.
7 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Product references This manual follows the conventions shown in Table 47 to refer to HP StorageWorks P9000 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Asynchronous Continuous Access Asynchronous • Continuous Access XP Asynchronous • Continuous Access XP Extension • XP Continuous Access Asynchronous This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Journal Continuous Access Journal • Continuous Access XP Journal • P9000 Continuous Access Journal
Support and other resources
A Environment settings when using the Core CLI License In the procedure described in “Configurations for open systems” on page 13, if you are using Device Manager with the Core CLI License to add a resource (storage system) to Device Manager, you should use Device Manager CLI as described in this appendix. Overview Follow this procedure: 1. Check the necessary settings as described in “Preparing to use Device Manager CLI” on page 121. 2. Follow the instructions in “Adding a storage system” on page 122.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 48 Items required to execute Device Manager CLI Item Description The installation folder for Device Manager CLI is as follows: Installation folder for Device Manager CLI Device-Manager-installation-folder\ DeviceManager\hdvmcli The default location of Device-Manager-installation-folder is system-drive\Program Files\CVXPAE.
Command format: GetServerInfo -o file-path Specify the -o option to output the command execution results to a file. Specify the absolute or relative path of the file. A storage system will be added based on the information output to the file. Command execution results: An example of the command execution results is shown below. Use the values for arrayFamily and displayArrayFamily as arguments when registering storage system information.
Parameter name Description Array family of the storage system family Enter the value of arrayFamily shown in the execution results of the GetServerInfo command. Display name of array family for the storage system. displayfamily Enter the value of displayArrayFamily shown in the execution results of the GetServerInfo command.
Adding a host This appendix describes how to add a host to Device Manager server by using Device Manager CLI. Use the AddHost command to register host information into Device Manager server, and then make Device Manager server recognize the host. Command format: AddHost hostname=host-name wwnlist=wwn-list {ipaddress=IP-address|ipv6address=IP-address} Table 50 AddStorageArray command parameters Parameter name Description hostname Specifies the host name to be added. wwnlist Use periods (.
Environment settings when using the Core CLI License
B Checking the pair management server information managed by Device Manager server (for the Core CLI License) To check host (pair management server) information that is managed by the Device Manger server when Device Manager Core CLI License is enabled, use Device Manager CLI. This appendix describes how to use Device Manager CLI for this purpose. Overview Before using Device Manager CLI, read “Preparing to use Device Manager CLI” on page 121 and perform necessary checks and setup procedures.
2. Check the execution results. Make sure that the host name obtained by this command and the name of the host (pair management server) on which Device Manager Agent is installed are the same. An example of the command execution results is shown below. The value shown for name is the host name. In this example, you can see that the host cci-vm-r has been registered. RESPONSE: An instance of Host objectID=HOST.8 name=cci-vm-r ipAddress=10.208.176.
3. If a value is not registered to lastUpdated, execute the AddHostRefresh command. To refresh the pair management server information that is managed by Device Manager server, execute the AddHostRefresh command: AddHostRefresh hostname=host-name For host-name, specify the value for name, which was acquired by the GetHost command. To update information about the host cci-vm-r, execute the following command: hdvmcli AddHostRefresh hostname=cci-vm-r An example of the command execution results is shown below.
2. Make sure that the values output by this command are the same as the values specified in the RAID Manager configuration definition file, which is stored on the pair management server. The table below lists the values and settings to be checked. Table 51 Settings to be checked by the GetHost command Value Settings to be checked The value specified for instanceNumber in An instance of ConfigFile This value and the instance number in the configuration definition file are the same.
objectID=HOST.8 name=cci-vm-r ipAddress=10.208.176.103 capacityInKB=42,991,616 hostType=-1 List of 2 ConfigFile elements: An instance of ConfigFile objectID=CONFIGFILE.8.10 instanceNumber=10 controlledBy=Device Manager portNumber=50,010 valid=1 List of 1 ReplicationGroup elements: An instance of ReplicationGroup objectID=REPGROUP.5 replicationGroupID=5 groupName=SI-CG01-R pvolHostID=8 : copyTrackSize=-1 List of 2 ReplicationInfo elements: An instance of ReplicationInfo objectID=REPINFO.83000101.601.
List of 1 WWN elements: An instance of WWN WWN=50.00.08.70.00.30.55.04 3. If the execution results and the values specified in the RAID Manager configuration definition file do not match, execute the AddStorageArray command to refresh the storage system information. AddStorageArray ipaddress=IP-address family=array-family Specify the storage system IP address for IP-address. For XP24000/XP20000, you can use an IPv6 address.
Acronyms and Abbreviations The following acronyms and abbreviations appear in this guide.
iSCSI Internet Small Computer System Interface JDK Java Development Kit LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical DEVice LU Logical Unit LUN Logical Unit Number MCU Main Control Unit MIB Management Information Base NAS Network Attached Storage NAT Network Address Translation NIC Network Interface Card NTP Network Time Protocol OS Operating System PAP Password Authentication Protocol PPRC Peer-to-Peer Remote Copy RADIUS Remote Authenticati
UAC User Account Control URL Uniform Resource Locator Configuration Guide 135
Acronyms and Abbreviations
Glossary This glossary defines the special terms used in this document. Click the desired letter below to display the glossary entries that start with that letter. 3DC multi-target configuration A configuration in which, in addition to the local site, a connection is established between a nearby remote site and a distant remote site and Continuous Access Synchronous and Continuous Access Journal are used to copy storage system volumes among the three sites (called data centers).
cluster software Software installed on management server nodes to boost overall availability by duplicating management servers as a cluster system. Available software depends on the OS that runs on the management server. consistency group A group used as a unit in Continuous Access or Continuous Access Journal that maintains integrity of the update order for volumes. Continuous Access Software that duplicates volumes between storage systems. Continuous Access duplicates all data on the volumes.
Manager Software. Depending on the type of volume scan, volumes are assigned the local DAD, Non Gen'ed DAD, or remote DAD attribute. DAD ID A name that identifies a DAD. delta resync A status in which synchronization processing is performed by copying differential data to an Continuous Access Journal copy pair in which part of the copy pair exists on the local site and part exists on a remote site in a 3DC Multi-Target configuration.
multi-target configuration A copy pair configuration with a one-to-many relationship between the primary and secondary volumes. Information from one volume is copied to multiple volumes. Non-Gen’ed Volume A volume that is not recognized by a mainframe host. P9000 Command View AE Common Component A component that bundles common functions used by P9000 Command View AE suite products.
resides. The remote DAD attribute is assigned to the disk configuration definition file in which the discovered volumes are stored. SP-VOL (secondary-primary volume) The volume located in the middle of a cascade structure, when a cascade structure is used by the volume replication functionality of a storage system. Indicates the secondary volume in an upper level copy pair or the primary volume in a lower level copy pair.
Glossary
Index A D adding link menu, 46 adding link menu to web client, 46 Administrator privileges (UAC), 69 agent.logger.properties, 67 agentif.
HPStorageWorks P9000 for Business Continuity Manager Software (BCM), 38 hrpmap_getras command, 103 I information source, 139 infrastructure mainframe, 44 open systems, 42 inqraid $Phys -CLI command, 115 J jssecacerts truststore, 86, 88 K keytool command, 87 L LDEV maximum number, 31 log file log amount of data, 76 logger.
T technical support HP, 117 troubleshooting, 97 maintenance information, 98 resolving errors, 97 RPM-00824, 104 truststore, 86 U UAC, 69 V VMware ESX/ESXi support, 58 VSS Provider log files, 101, 102 requirements, 56 W web client, 16, 20 web sites HP, 117 Configuration Guide 145
