HP StorageWorks P9000 Replication Manager Software Configuration Guide Part number: TB584-96029 Ninth edition: August 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 .......
appagentif.properties ......................................................................................................... 85 base.properties .................................................................................................................. 86 5 Security management ....................................................................... 89 Network communications security ...............................................................................................
HP technical support ......................................................................................................... Subscription service .......................................................................................................... Documentation feedback ................................................................................................... Related information .................................................................................................................
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 Redundant pair management server configuration in open systems ................................
Tables 1 System components (for open systems) ....................................................................... 17 2 Overview of mandatory software (for open systems) .................................................... 19 3 System components (for mainframe systems) ............................................................... 21 4 Overview of mandatory software for mainframe management ...................................... 22 5 System components (for replica management) ...........................
31 Guest OS of Windows Server 2008 Hyper-V .............................................................. 63 32 Windows Server 2008 Hyper-V support based on the guest OS connection method ........ 63 33 Port numbers in server.properties file .......................................................................... 70 34 List of properties in the agent.logger.properties file ...................................................... 72 35 Error values and descriptions ...........................................
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 16 Replication Manager system configurations and requirements
Figure 4 Redundant pair management server configuration in open systems For more information on redundant configurations, see the HP StorageWorks P9000 Replication Manager User Guide. The following tables list and describe system components for each type of system and provide an overview of the software components.
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 5 Mainframe configuration using HP StorageWorks P9000 for Business Continuity Manager (BCM) 20 Replication Manager system configurations and requirements
Figure 6 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 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 Administrator Guide. Used to control copy group configurations located on storage systems from a host.
retrieves the status of Cnt Ac-S/Cnt-Ac-A/BC and Cnt Ac-J copy pairs directly from storage 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 8 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 Allows Replication Manager to perform database backup and restore operations.
Figure 9 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 R2 SP2 • Runs as a guest OS of Windows Server 2008 Hyper-V and V2 • Supports IPv4 and IPv6 connections • Also runs under VMware ESX/ESXi Server 3.x and 4.
Windows operating system Prerequisite programs Windows Server 2008 R2 no SP or SP1 • 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.x • Operation on Server Core is not supported Windows 7 no SP or SP1 • x86 architecture only • Supports IPv4 and IPv6 connections • Also runs under VMware ESX/ESXi Server 3.x and 4.
Server specifications The following table lists the server specifications required for a management server to run Replication Manager. Table 9 Required server specifications for a management server Item Minimum requirement Recommended specification CPU clock speed 1 GHz 2 GHz or higher Memory size 1 GB 2 GB or more Disk size 750 MB 750 MB to 6.
For details on the latest virtual memory requirements, see the documentation for each product. Table 11 Virtual memory requirements for each product Virtual memory requirement (MB) Product or component name Device Manager For details on virtual memory requirements and allocating virtual memory, see the description of the server.agent.maxMemorySize property in the HP StorageWorks P9000 Command View Advanced Edition Suite Administrator Guide.
NOTE: The configuration must always be refreshed when Replication Monitor is upgraded from v5.x to v7.x Resource Limits The maximum number of resources that can be managed by Replication Manager depends on 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.
mainframe systems. For open systems, the maximum number of LDEVs is already set per storage 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 “logger.properties” on page 79. 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.
Operating system Web browser Red Hat Enterprise Linux 5.6* (x86/x64) Firefox 3.6.x SUSE Linux Enterprise Server 11* noSP/SP1 (x86/x64) Firefox 3.6.x, 4.0.x NOTE: Replication Manager supports Mozilla provided by Hewlett-Packard Development Company, L.P. Required memory for management clients The minimum required memory size for a management client for all operating systems is at least 512 MB.
P9000 RAID Manager version and consistency group support To create remote pairs with the CTG option, P9000 RAID Manager 01.21.03 or later must be installed on the pair management server. If an earlier version is installed, pairs can be created successfully, but they are not members of a CT group (because the CTG option is ignored).
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 HP StorageWorks P9000 for Business Continuity Manager requirements, see the HP StorageWorks P9000 for Business Continuity Manager Installation Guide. For the requirements for P9000 mainframe agent, see the HP StorageWorks P9000 Command View Advanced Edition Suite Mainframe Agent Installation and Configuration Guide.
Data collection in open systems This section describes the data collection and flow of processing between programs in open systems.
For a copy pair defined by the storage system (such as Remote Web Console ), the status is acquired from Device Manager server because the P9000 RAID Manager configuration definition file is not available. Acquiring performance information 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)).
Acquiring and changing copy pair statuses Replication Manager issues a request to HP StorageWorks P9000 for Business Continuity Manager or P9000 mainframe agent, which acquires the status of copy pairs from the storage system. (Only BCM can change the status.
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: 1. Before installing Replication Manager, you must back up the databases of other P9000 Command View AE suite products in use, on the management server where Replication Manager is installed. For details about how to back up databases, see the application product manuals.
Figure 12 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 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 P9000 RAID Manager on the pair management servers. For details, see the relevant P9000 RAID Manager manual. 4.
7. If there is any host on which Device Manager Agent has not been installed, manually add the resource (host) to Device Manager. For details about how to add hosts in 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. Mainframe systems environment To configure Replication Manager for a mainframe environment: 1. Install Device Manager server on the management servers.
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, 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.
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. NOTE: Exchange 2010 does not use storage groups. MS Exchange databases contain the following two types of information stores: • Mailbox stores for saving received email messages, attachments, folders, documents, etc. • Public folder stores for saving information shared among users (email messages, documents, MS Outlook custom forms, etc.
NOTE: Replication Manager identifies the database application running on each host according to the version of the Application Agent installed (Exchange or SQL Server). Therefore, do not install a version of Application Agent on a host that does not have the corresponding database application installed. If an inappropriate version of Application Agent is installed on a server, Replication Manager will fail to collect information during Refresh Host processing and display an error message.
NOTE: Application Agent is not supported on Windows Server 2008 (32-bit version).
Database and backup server requirements This section describes database and backup server requirements. File systems are only supported using the Application Agent CLI. NOTE: When using IPv6, both IPv4 and IPv6 must be enabled on the database and backup servers. You can use IPv6 addresses only if they are global addresses.
4. Application Agent does not support Veritas Dynamic Multiple Pathing.
For details, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide. Table 25 Database and backup server requirements (Microsoft Exchange Server) Operating system IPv6 support Required programs Windows Server 2003 SP2 N Windows Server 2003 SP2 (64-bit) N Windows Server 2003 R2 SP2 Y Application Agent v 6.3 or later Windows Server 2003 R2 SP2 (64-bit) Y RM Shadow Copy Provider (VSS Provider) 01-02-03/05.
CAUTION: If you execute a VSS backup for a GPT disk, registry keys related to the backup server GPT disk are added. If the VSS backup is repeated and too many device entries have accumulated in the registry, the backup might fail. Therefore, HP does not recommend using Application Agent in an environment that uses GPT disks.
Exchange Management Tool The same version of Exchange Management Tool must be installed on the database and backup servers. ESEUTIL and Exchange Server 2003 To back up an Exchange database, the Exchange management tools must be installed on both the database server and the backup server. For Exchange Server 2003, the ESEUTIL command must also be installed. The ESEUTIL command does not need to be installed for any other versions of Exchange Server.
Replica operations for Microsoft SQL server The following features of SQL Server 2008 and SQL Server 2008 R2 are not supported: • • • • • • FILESTREAM Data Change Data Capture Change Tracking Backup Compression (Database) Backup Compression (Transaction Log) Shrinking a Database For other notes about replica operations for Microsoft SQL Server, see "SQL Server data and requirements" in the HP StorageWorks P9000 Replication Manager Software User Guide.
When using a VSS Provider not bundled with Application Agent Beginning with 7.1, the VSS Provider bundled with Application Agent is named P9000 RM Shadow Copy. When Application Agent is upgraded, the VSS Provider is automatically upgraded as well. However, if the currently installed VSS Provider was not originally bundled with Application Agent, you must remove it manually and use Application Agent to install P9000 RM Shadow Copy.
The volume replication functions required to use Application Agent with the storage systems are listed in the following table. Table 27 Volume replication functions required Storage system Volume replication function Business Copy Continuous Access Software XP12000/XP10000/SVS200 Continuous Access Synchronous XP24000/XP20000 Continuous Access Asynchronous Snapshot Continuous Access Journal Cluster support Application Agent can be linked to cluster software to increase the availability of the system.
Database server OS Cluster software Windows Server 2008 no SP/SP1, SP2 (64-bit)2 Windows Server 2008 R2 no SP or SP12 Windows Server 2008 R2 IPF no SP or SP12 Notes: 1. 2. 3. 4. Cluster environments are not supported for usage with GPT disks. Please use MBR disks. Exchange Server 2003 is not supported. To perform restore when a cluster source is online, the Microsoft Cluster Service correction module (Hotfix 903650) is required. This is supported only when using the CLI.
• Under VMware ESX/ESXi Server 4.0 or 4.1, database servers that are configured on a guest OS are supported. Backup servers that are configured on a guest OS are supported if all of the following conditions are satisfied: • The backup target is a file system or SQL Server. • The secondary volume is a single generation. • The configuration does not recognize the second volume dynamically. • The backup is not made with VSS.
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.
NOTE: The following restrictions apply: • SQL Server cluster configurations are not supported on guest operating systems, except for a limited subset of configurations between guest operating systems, which are supported only in Replication Manager version 7.1 and later. However, note that in these configurations, you must use disks that are directly connected to iSCSI, and the SQL version must be one of the following: SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2.
If you plan to install Application Agent on the management server If you plan to install Application Agent on the management server, you must first do the following: If Replication Manager is already installed on the management server: 1. Set the value of base.refreshdginfo.exec in the base.properties file to 0. 2. 3. Refresh the configuration. Install Application Agent on the management server. If Application Agent is already installed on the management server: 1. 2.
6. After the download completes, execute the Application Agent installation file and activate the Installshield Wizard. 7. In the Welcome… dialog box, click Next. The Start Copying Files dialog box appears. 8. Enter the appropriate customer information in the User Name and Company Name fields of the Customer Information window. Then click Next. 9. You will be prompted to choose a destination location in the Destination Location field in the next window. Use the Browse...
Adding Application Agent to the Windows Firewall Exception list NOTE: As of 7.1, automatic Windows Firewall Exception registration is supported. The following procedure is not required unless the process failed or you elected not to add the exceptions when prompted during the Application Agent installation.
Using P9000 RAID Manager to configure pair volumes Within a copy group, only include the pair volumes for one application. If the pair volumes of multiple applications are mixed together in one copy group, unintended backups and restorations might occur. Device Manager and P9000 RAID Manager For P9000 RAID Manager to be started on the database and/or backup servers automatically, Device Manager Agent needs to be installed on both servers.
3. Use the Cluster Administrator wizard to add the new resource to the cluster resource group with the name virtual-server-name (such as a cluster resource group for Exchange Server). Resource type: Generic script Script file path: Path name of the created VBScript file If the VBScript file is stored on a shared disk for nodes, be sure and register this shared disk as a physical disk resource in the Resource dependencies field in the Dependencies dialog box.
Application Agent and Replication Manager log output The number of Application Agent instances in your storage configuration must be considered when configuring the amount of log output, as described in “About Replication Manager log output” on page 82. If the number of target Application Agent instances exceeds 30, you need to tune the file capacity and number of files as follows: Trace log size = current-file-capacity + 2.
• The port numbers set in the server.properties file must be unique and cannot be shared by any other processes. • After changing these values, the Common Agent Service must be restarted. Starting and stopping the Application Agent Services To use Replication Manager to perform a backup, the Application Agent Services must be running on both the database server and the backup server. For details, see “Starting and stopping Replication Manager” on page 75.
The following tables list the available properties, the types of information logged, and the parameters that are stored when values are logged. Table 34 List of properties in the agent.logger.properties file Property Description The output level of the Replication Manager log file. Messages matching the type are output to the log file. Specifiable values: One of the three following scenarios: DEBUG and INFO, WARN, or ERROR and FATAL. agent.logger.
Values Logged INFO DEBUG WARN WARN X X ERROR X X X FATAL X X X ERROR FATAL X Configuration Guide 73
Setting up Application Agent
4 Operating the management server This chapter describes the Replication Manager settings and 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.
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. However, if HP StorageWorks P9000 Command View AE Common Component services are already running, the services of P9000 Command View AE suite products are not automatically started, and you must start them manually.
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 75.
File serverstorageif.properties Property Default value (unit) 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.RefreshStatus.
File Property Default value (unit) 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.responseTimeout 3600 (seconds) base.repositry.
NOTE: File size values 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. Specifiable values are determined by the specified unit as follows: Bytes: 4096 to 2147483647 KB: 4 KB to 2097151 KB MB: 1 MB to 2047 MB Table 38 List of properties in the logger.properties file Property Description logger.loglevel The threshold value for the output level of the Replication Manager log files.
Property Description Maximum size of a database-related log file. logger.DB.MaxFileSize Default value: 20 MB Enabling or disabling of the configuration update logging function. logger.RefreshConfig.enabled Specifiable values: true or false Default value: true Maximum number of backup files for a configuration update log file. logger.RefreshConfig.MaxBackupIndex Specifiable values: 1 to 32 (files) Default value: 5 Maximum size of a configuration update log file. logger.RefreshConfig.
Property Description 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. Default value: true Maximum number of the application status log backup files. logger.AppStatus.MaxBackupIndex Specifiable values: 1-32 (files). Default value: 6 Maximum size of the application status log file logger.
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 39 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 serverstorageif.properties The serverstorageif.
bcmif.properties 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 41 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 42 List of properties in the agentif.properties File Property Description agentif.connectTimeout 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 43 List of properties in the appagentif.properties File Property Description appagentif.connectTimeout 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 13 Communication routes used by Replication Manager 90 Security management
Figure 14 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 92. 2. Set up SSL on Device Manager server or the BCM host.
Figure 15 Deciding whether a certificate requires registration The tasks outlined in the flowchart are as follows: 1. “Checking the truststores” on page 93 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 93.
• 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 46 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 47 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 issues arise with Application Agent (including installation and removal), see “Troubleshooting Application Agent operations” on page 106.
Figure 16 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 112. 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.
• • • • • • 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 109 • Application Agent events that can be ignored, page 110 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.
VSS Provider vssprv_inst.log Output folder The output folder of the Application Agent and VSS Provider trace log files differ depending on whether the installation-folder-for-Application-Agent\DRM\log folder exists. If this folder does not exist, the log files are placed on the desktop.
• On hosts where both Device Manager Agent and Application Agent are installed, run both the cvxpaegetlogs command on the management server and hrmap_getras command on the host where Application Agent is installed. • On hosts where only Application Agent is installed, you need only run the hrmap_getras command. For more information, see “Collecting support information with the hrpmap_getras command” on page 109 and “Collecting maintenance information” on page 104.
Files Description Location copied from alet.xml Deployment descriptor file of Application Agent Common-Agent-installation-folder\mod\ hrpmap Table 51 List of files collected in the drminfo folder Files Description Location copied from .version* Application Agent version information file Common-Agent-installationfolder\ all Files for each type of Application Agent environment setting Common-Agent-installationfolder\conf drm_output.log drm_output.log.
Server on which event occurred When message is output to event log Type Source Event ID Message Backup server A VSS backup is executed. Error VDS Dynamic Provider 10 The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505 Backup server A VSS backup is executed. Error PlugPlayManager 12 The device "xxxxxxxx" disappeared from the system without first being prepared for removal. Backup server A VSS backup is executed.
Server on which event occurred When message is output to event log Type Source Event ID Message Backup server A VSS backup is executed. Error Service Control Manager 7034 The Virtual Disk Service service terminated unexpectedly. It has done this xx time(s). Backup server The OS is Windows Server 2008 and during a VSS import, COPY/COPY or PAIR/PAIR volumes other than the volumes to be processed exist.
Checking disk space Check the amount of space available on the disk on which Replication Manager is installed.
3. Execute the following command to re-create a database system on the disk: installation-folder-for-P9000-Command-View-AE-Common-Component\bin\hcmdsdbremake /databasepath new-database-recreation-destination-folder NOTE: Observe the following restrictions for folders/directories: • Specify an absolute path for database-recreation-destination-folder of no more than 63 bytes. • If you use a path delimiter as the last character of the destination name, the command will fail.
2. From the Start menu, choose Settings, Control Panel, Administrative Tools, and then Cluster Administrator. In the Cluster Administrator window that opens, place the following services offline: • DeviceManagerServer • HBase Storage Mgmt Web Service • HBase Storage Mgmt Common Service NOTE: Do not place the shared disk resource offline, or migration of the database will fail. 3.
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 no 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 P9000 RAID Manager are correct: 1. Installation of Device Manager Agent, page 120 2. Link between Device Manager server and Device Manager Agent, page 120 3. Properties of Device Manager Agent, page 120 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 121 2. Recognition of the command device, page 121 3. Recognition of the replication configuration, page 121 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 P9000 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 P9000 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.
Troubleshooting
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.
• http://www.hp.com/support/cvae/manuals • http://www.hp.com/storage/spock Conventions This guide follows the conventions shown in Table 53 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 131. 2. Follow the instructions in “Adding a storage system” on page 132.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 54 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 56 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 131 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 57 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 145
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.
Remote Scan A volume scan that can be performed on Non Gen'ed volumes outside the site where HP StorageWorks P9000 for Business Continuity Manager Software 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.
Glossary
Index A D adding link menu, 46 adding link menu to web client, 46 Administrator privileges (UAC), agent.logger.properties, 71 agentif.
HPStorageWorks P9000 for Business Continuity Manager Software (BCM), 39 hrpmap_getras command, 109 I information source, 149 infrastructure mainframe, 44 open systems, 42 inqraid $Phys -CLI command, 124 J jssecacerts truststore, 92, 94 K keytool command, 93 L LDEV maximum number, 32 log file log amount of data, 82 logger.
T technical support HP, 127 troubleshooting, 103 maintenance information, 104 resolving errors, 103 RPM-00824, 112 truststore, 92 U UAC, 75 V VMware ESX/ESXi support, 61 VSS Provider log files, 107, 108 requirements, 58 W web client, 17, 21 web sites HP, 127 Configuration Guide 155
