HP P9000 Replication Manager Software Configuration Guide Part number: TB584-96036 Tenth edition: November 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 ............................................................................................... 48 hcmdslink command options ................................................................................................ 48 Creating a user-defined application file ................................................................................. 48 3 Setting up Application Agent ............................................................. 51 About Application Agent .......
appagentif.properties ......................................................................................................... 89 base.properties .................................................................................................................. 90 5 Security management ....................................................................... 93 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 Database server requirements for cluster environment (Exchange Server 2003, SQL Server, and file systems) ..................................................................................................... 64 32 Required memory when running Application Agent on a VMware ESX virtual machine ................................................................................................................ 66 33 Guest OS of Windows Server 2008 Hyper-V .........................................................
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 P9000 Replication Manager Software 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 P9000 Command View Advanced Edition Suite Software 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 • 32-bit architecture only • Supports IPv4 and IPv6 connections • Also runs under VMware ESX/ESXi Server 3.x and 4.
Operating system Cluster software • Microsoft Windows Server 2008 Enterprise Edition Solaris 10 • Microsoft Windows Server 2008 Enterprise Edition SP2 Microsoft Failover Cluster Solaris 10 SPARC (32-bit or 64-bit kernel mode) VERITAS Cluster Server 4.1 MP2 and 5.0 MP1 or Sun Cluster 3.1 Solaris 10 AMD64 (32-bit or 64-bit kernel mode) NOTE: There is no cluster support on Windows XP.
Usage Required disk space For backing up the Replication Monitor database (5.x upgrade only) At least 200 MB Virtual memory requirements If adequate virtual memory is not allocated on the management server, P9000 Command View AE suite products and any other installed programs might become unstable or might not start. To ensure stable operation, in addition to the virtual memory required for the OS and other programs, the information in Table 11 should be taken into account.
Type Value jsp 28,000,000 Total 47,290,000 Virtual memory 100 Disk space for Replication Monitor log files (5.x upgrade only) To determine the space required for backing up the Replication Monitor log file, use the following formula (which uses the settings in the logger.properties file) logger.MaxBackupIndex * logger.MaxFileSize For details about the logger.properties file, see “logger.properties” on page 83.
Memory heap size Environment Mainframe systems Small Medium Large 40,000 60,000 90,000 NOTE: In consideration of response time and memory usage, the maximum number of both open and mainframe pairs that can be operated on by the Pair Configuration Wizard at one time is 1,000. With respect to the number of mainframe pairs, the values in the table above are the maximum number of copy pairs that Device Manager and Business Continuity Manager can manage.
(number-of-open-LDEVs * 2) + number-of-mainframe-LDEVs For example, if the number of open LDEVs is 30,000 and the number of mainframe LDEVs is 40,000, the calculated value is 100,000 ((30,000 * 2) + 40,000). In this case, the appropriate memory heap size is Medium. Number of copy pairs on open systems If the number of copy pairs is 5,000 or more, edit the following Device Manager Agent properties on the pair management server: • server.agent.maxMemorySize in the server.properties file • agent.rm.
Operating system Linux Web browser Windows Server 2008 R2 no SP or SP1 (64bit) Internet Explorer 8.0, 9.0 Windows Server 2008 SP2 (64-bit)* Internet Explorer 7.0, 8.0, 9.0 Windows Server 2008* R2 no SP or SP1 Internet Explorer 8.0, 9.0 Windows XP SP2 (32-bit) Internet Explorer 7.0 Windows XP SP3 (32-bit) Internet Explorer 7.0 Windows Vista* no SP Internet Explorer 7.0, 8.0 Windows Vista* SP1 or SP2 Internet Explorer 7.0, 8.0 Windows 7* no SP or SP1 Internet Explorer 8.0, 9.
Requirements for open systems The following table shows the requirements for hosts and pair management servers. Table 16 Requirements for hosts and pair management servers (for open systems) Type Host Pair management server Operating system Prerequisite programs The Device Manager Agent must support the OS. Device Manager Agent. For information on agent compatibility with hosts managed by Device Manager, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide.
names. If they cannot determine each other's IP address, an error might occur during copy pair creation. • In the hosts file on the management servers or pair management servers, define the IP addresses and host names of the pair management servers to be connected. • Use a DNS server. Functional limitations when software versions do not match The version numbers of P9000 Command View AE suite products are synchronized to ensure feature compatibility. For example, the 6.
• When Replication Manager is used to distribute disk configuration definitions files to a host linked with HP StorageWorks P9000 for Business Continuity Manager 6.6.1, an error occurs (RPM00568) in Replication Manager. In either of the above cases, Replication Manager cannot be used to edit the disk configuration definition files that were created by HP StorageWorks P9000 for Business Continuity Manager 6.6.1. Instead, you must use HP StorageWorks P9000 for Business Continuity Manager 6.
Figure 10 Data collection (open systems) Acquiring configuration and license information Replication Manager acquires the following information using 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
NOTE: Replication Manager acquires configuration information from the Device Manager server at the following times: • When a configuration refresh is performed. All configuration information is acquired when a configuration refresh is performed. • When a storage system setup window is launched.
Figure 11 Data collection (mainframe systems) NOTE: Although not shown in this simplified diagram, all requests for HP StorageWorks P9000 for Business Continuity Manager from Replication Manager are handled by BCM Agent (which resides on the same host as BCM). Acquiring and deleting copy pair configuration information Replication Manager issues a request to HP StorageWorks P9000 for Business Continuity Manager to acquire or delete copy pairs. BCM performs the operations on the storage system.
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: 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 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 P9000 Command View Advanced Edition Suite Software Help or the HP 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 P9000 Command View Advanced Edition Suite Software Help or the HP 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: The same Service Pack should be applied on both the database and backup server operating systems. Notes: 1. 2. 3. 4. The Exchange Management Tool is required on the database server and backup server. For details, see the section Exchange Management Tool. The the ESEUTIL command must also be installed on the backup server; see ESEUTIL and Exchange Server 2003. Hotfix 892514 is required. This is supported only when using the Application Agent CLI.
Database server OS Windows Server 2008 SP2 Backup server OS SQL Server version Windows Server 2008 no SP 2005 SP21 Windows Server 2008 SP2 2005 SP3 Windows Server 2003 SP2 (64-bit) Windows Server 2003 SP2 (64-bit) Windows Server 2003 R2 SP2 (64bit) Windows Server 2003 R2 SP2 (64-bit) Windows Server 2008 no SP or SP1 (64-bit) Windows Server 2008 SP2 (64-bit) 2005 SP2 (64-bit)1 2005 SP3 (64-bit) 2005 SP4 (64-bit) Windows Server 2008 no SP or SP1 (64-bit) 2008 no SP1 Windows Server 2008 SP2 (64
NOTE: When executing a backup using VSS, the same Service Pack should be applied on both the database and backup server operating systems.
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. Table 25 Database and backup server requirements (file systems) Operating system IPv6 support Windows Server 2003 SP2 N Windows Server 2003 SP2 (IPF)1 N Windows Server 2003 SP2 (64-bit) N Logical Volume Manager (Windows LDM3 or Veritas Volume Manager for Windows4) Windows Server 2003 R2 SP2 Y Application Agent v 7.
4. Application Agent does not support Veritas Dynamic Multiple Pathing.
If you do not add this value, Replication Manager might not be able to acquire pair, pool, and journal information. For details on editing the properties file, see the HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide.
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 the section on SQL Server data and requirements in the HP 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.
NOTE: Application Agent for Exchange does not support Continuous Access Journal. Table 29 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, SP22 Windows Server 2008 IPF no SP/SP1, SP22 Windows Server 2008 no SP/SP1, SP2 (64-bit)2 Microsoft Failover Cluster 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.
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. • 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.
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 86. 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 79.
The following tables list the available properties, the types of information logged, and the parameters that are stored when values are logged. Table 36 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 77
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 79.
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 40 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 41 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 43 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 44 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 45 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 The 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 94 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 96. 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 97 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 97.
• 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 Successful resource group creation 6 Failed resource group creation 3 Successful resource group deletion 6 KAPM02631-I Failed resource group deletion 3 KAPM02636-E Successful resource group deletion 6 Failed resource group deletion 3 Successful resource group property editing 6 KAPM02634-I Failed resource group property editing 3 KAPM02639-E Successful resource group property editing 6 Failed resource group property editing 3 Addition o
Description of category Audit event Severity The pair operation task (pair create, delete, or modify) timed out. (The command was executed successfully, but whether the pair status was changed correctly could not be confirmed.) 4 The pair operation task has failed. 3 Failed to update the configuration definition file after deleting the pair. 4 Editing or distribution of the disk configuration definition file has started.
Description of category Audit event Severity Canceling of a secondary volume hiding operation failed. 3 Message ID KAVN10078-E KAVN10084-E KAVN10031-I KAVN10034-I Creation, editing, execution, canceling, or deletion of a task has started. 6 KAVN10037-I KAVN10040-I KAVN10043-I KAVN10032-I KAVN10035-I Creation, editing, execution, canceling, or deletion of a task has succeeded.
Description of category 102 Audit event Severity Message ID Swap operation has started. 6 KAVN10055-I Swap operation is terminated. 6 KAVN10056-I Swap operation timed out 4 KAVN10057-W Acquisition of replica information has started. 6 KAVN10067-I 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 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 P9000 Replication Manager Software User Guide. 3.
• • • • • 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 arc archive-filename Specifies the name of the archive file to be created. The archive file is output to the directory specified for the dir option. Do not specify a path for the archive file name. If you do, the command might terminate abnormally. If this option is omitted, the archive file name will be cvxpae_logs. When the archive file is output, this name is suffixed with the extension for the file type (.jar, .hdb.jar, .db.jar, or .csv.jar).
Resolving Application Agent installation and uninstallation errors Sometimes, an Application Agent installation or uninstallation might not end properly, such as when an error occurs during the installation, or the installation is canceled while files are being copied. In such cases, resolve the problem by following the same sequence used for installation of Replication Manager.
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: Common-Agent-installation-folder\ schedule all Common-Agent-installationfolder\log For virtual server:cluster path specified in sch.
Server on which event occurred When message is output to event log Type Source Event ID Message Backup server A VSS backup is executed. Warning disk 51 An error was detected on device device path during a paging operation. Warning ftdisk 57 The system failed to flush data to the transaction log. Corruption may occur. 107 Exchange Search Indexer has temporarily disabled indexing of the Mailbox Database xxxxxxxx due to an error xxxxxxxx.
Server on which event occurred When message is output to event log Type Source Event ID Message 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. Error VSS 12289 Volume Shadow Copy Service error: xxxx. 12290 Volume Shadow Copy Service warning: GetVolumeInformationW(\\?\Volume{xxxxxxxxxxxx-xxxx-xxxxxxxxxxxxxxxx}\,NULL,0,NULL,NULL,[0x00000000], , 260) == 0x00000001. hr = 0x00000000.
Transferring the database to another disk (non-cluster) If deleting unnecessary files does not free up enough disk space, data needs to be transferred from the HP StorageWorks P9000 Command View AE Common Component database onto another disk with more free space. NOTE: The HP StorageWorks P9000 Command View AE Common Component service must be running to perform this task. To transfer data from an HP StorageWorks P9000 Command View AE Common Component database: 1.
Transferring the database to another disk (Windows MSCS) The following topics describe the procedures for moving data when Microsoft Cluster Server (MSCS) is used. NOTE: Be aware of the following: • This procedure assumes that the HP StorageWorks P9000 Command View AE Common Component service is already running. • In the cluster management application, you must specify the resource name registered when setting up the cluster resource. Procedure on the executing node 1.
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 119 2. Link between Device Manager server and Device Manager Agent, page 119 3. Properties of Device Manager Agent, page 119 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 120 2. Recognition of the command device, page 120 3. Recognition of the replication configuration, page 120 For details about Device Manager web client, see the HP 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.
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.
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 Journal Continuous Access Journal • Continuous Access XP Journal • P9000 Continuous Access Journal • XP Continuous Access Journal This abbreviation is used when it is not necessary to distinguish the following products: Data Retention Utility • Data Retention Utility • LUN Security XP Extension • XP Data Retention Utility This abbreviation is used when it
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 129. 2. Follow the instructions in “Adding a storage system” on page 130.
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 129 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 143
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, 48 adding link menu to web client, 48 Administrator privileges (UAC), agent.logger.properties, 75 agentif.
HPStorageWorks P9000 for Business Continuity Manager Software (BCM), 41 hrpmap_getras command, 109 I information source, 147 infrastructure mainframe, 46 open systems, 44 inqraid $Phys -CLI command, 123 J jssecacerts truststore, 96, 98 K keytool command, 97 L LDEV maximum number, 33 log file log amount of data, 86 logger.
T technical support HP, 125 troubleshooting, 103 maintenance information, 104 resolving errors, 103 RPM-00824, 112 truststore, 96 U UAC, 79 V VMware ESX/ESXi support, 65 VSS Provider log files, 107, 108 requirements, 62 W web client, 17, 21 web sites HP, 125 Configuration Guide 153
