HP P9000 Replication Manager Software Configuration Guide Part number: TB584-96058 Thirteenth edition: November 2012
Legal and notice information © Copyright 2010, 2012 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 ..............................
Creating a user-defined application file ................................................................................. 55 3 Setting up Application Agent ............................................................. 57 About Application Agent ........................................................................................................... Application Agent functions .................................................................................................
appagentif.properties ......................................................................................................... 98 base.properties .................................................................................................................. 99 RpMCLI.properties .................................................................................................................. 100 5 Security management .....................................................................
7 Support and other resources ............................................................ 137 Contacting HP ........................................................................................................................ HP technical support ......................................................................................................... Subscription service .......................................................................................................... Documentation feedback ....
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) ............................................................... 22 4 Overview of mandatory software for mainframe management ...................................... 23 5 System components (for replica management) ...........................
29 Supported database and backup server OS combinations (when using a file system and VSS) ...................................................................................................................... 61 30 Supported database and backup server OS combinations (when using a file system but not VSS) ................................................................................................................ 62 31 Database and backup server requirements (file systems) ..............................
63 Restrictions when Replication Manager and HP StorageWorks P9000 for Business Continuity Manager Software versions differ ............................................................ 142 64 Items required to execute Device Manager CLI .......................................................... 156 65 AddStorageArray command parameters .................................................................. 157 66 AddStorageArray command parameters .................................................................
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. If multiple sites are used, a management server is required for each site. Replication Manager and Device Manager server are installed on the management server at the local site.
System components Software included in system components Description Normally, a host is a computer on which application programs are installed. Device Manager Agent is also installed on a host. A host uses storage systems as external storage systems. Host Device Manager Agent Installing Device Manager Agent is optional. If you install Device Manager Agent on a host, you can view information about that host (such as IP address and mount points) from Replication Manager.
Software Description Software that controls volume replication functions (such as Continuous Access or Business Copy), by issuing commands from a host to storage systems. (Make certain that the version of P9000 RAID Manager supports your storage system.) P9000 RAID Manager Replication Manager uses the P9000 RAID Manager configuration definition file to change a copy pair configuration and acquire configuration information. For details, see the manual for the corresponding version of P9000 RAID Manager.
Figure 5 Mainframe configuration using HP StorageWorks P9000 for Business Continuity Manager (BCM) Configuration Guide 21
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 the GUI 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 the GUI is limited. For details, see the HP P9000 Replication Manager Software User Guide.
Software Description 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. Device Manager server An instance of Device Manager server running on the same management server as Replication Manager is called an instance of "local Device Manager".
• If you are replacing an instance of P9000 mainframe agent with HP StorageWorks P9000 for Business Continuity Manager, HP recommends removing P9000 mainframe agent first. Prerequisites for managing copy pairs on mainframe systems using P9000 RAID Manager With P9500 systems, you can manage volumes and copy pairs on mainframe systems using P9000 RAID Manager. In this case, you must use the views and the copy pair definition wizard for open systems.
(example: pair management server) and the replica management counterpart (example: backup server). Figure 7 Example system configuration managing copy pairs and application replicas (Exchange) NOTE: Only Cnt Ac-S is supported for creating a remote copy.
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 4.x, and VMware ESXi Server 5.x.
Prerequisite programs Windows operating system Windows Server 2008 SP2 • 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 4.x, and VMware ESXi Server 5.x. To execute Replication Manager on the virtual server, configure the virtual server using the recommended configuration.
WARNING! Do not use a Managed Service Account if Windows Server 2008 R2 is the OS on the pair management server, database server, or backup server.
The following table lists the server specifications required for use of the Replication Manage CLI. Table 9 Requirements for using the Replication Manager CLI on a management server Operating system Edition Windows Server 2003 R2 SP2 (x86 and x64) Windows Server 2008 no SP/SP1 or SP2 (x86 and x64) Windows Windows server 2008 R2 no SP or SP1 The following table lists the server specifications required for a cluster environment.
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 12 should be taken into account.
+ 3700 ( P9000 Command View AE Command Suite) + 1000 (Allocated virtual memory) = 6480 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 92.
Maximum number of copy pairs The following table shows the maximum number of copy pairs. Table 14 Maximum number of copy pairs that can be managed Environment Number of copy pairs by memory heap size Small Medium Large Open systems only 6,000 12,000 24,000 Mainframe systems only 40,000 60,000 90,000 Combined open and mainframe1 40,000 60,000 90,000 Notes: 1.
the maximum number. In an open system environment, when the memory heap size is Small or Medium, the maximum number is the total number of LDEVs acquired from both the local and remote instances of Device Manager. When the memory heap size is Large, the maximum number differs for the LDEVs acquired from the local and remote instances of Device Manager.
NOTE: Consider the following points: • 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. • If you are using Internet Explorer 6.0, Internet Explorer 6.0 SP1, or Internet Explorer 6.0 SP2, you cannot use an IPv6 address to connect to Replication Manager. Make sure you use the host name instead.
Operating system Web browser Red Hat Enterprise Linux 5.6* (32-bit/64bit) Firefox 3.6.x and Firefox ESR 10.0.x Red Hat Enterprise Linux 5.7* (32-bit/64bit) Firefox 3.6.x and Firefox ESR 10.0.x Red Hat Enterprise Linux 5.8* (32-bit/64bit) Firefox 3.6.x and Firefox ESR 10.0.x Red Hat Enterprise Linux 6.0* (32-bit) Red Hat Enterprise Linux 6.1* (32-bit) Red Hat Enterprise Linux 6.2* (32-bit/64bit) Red Hat Enterprise Linux 6.
Requirements for open systems The following table shows the requirements for hosts and pair management servers. For information on restrictions, see “Restrictions when Replication Manager and Device Manager versions differ” on page 141. Table 17 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.
Requirements for mainframe systems The following table describes the requirements for hosts. For information on restrictions, see “Restrictions when Replication Manager and HP StorageWorks P9000 for Business Continuity Manager Software versions differ” on page 142. Table 18 Requirements for hosts (for mainframe systems) Operating system Prerequisite programs HP StorageWorks P9000 for Business Continuity Manager 5.0, or or P9000 mainframe agent 6.0 or later.
Instead, you must use HP StorageWorks P9000 for Business Continuity Manager 6.7 or later to edit the disk configuration definition files and then perform volume scan or distribution with Replication Manager). Supported storage systems Replication Manager supports all storage systems supported by Device Manager server: • • • • • XP512/XP48 XP1024/XP128 XP12000/XP10000/SVS200 XP24000/XP20000 P9500 For details, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide.
• For port numbers used by Application Agent, see “Changing Application Agent port numbers” on page 83 Table 19 Port numbers to register as firewall exceptions between the management server and management clients Port number 23015/tcp 23016/tcp Originator Management client Management client Destination Description Management server This port is used to access the HBase Storage Mgmt Web Service of Common Component when communicating with a management client.
1. When IHS is used to communicate with Business Continuity Manager Software via SSL, register the port number for IHS as a firewall exception. Table 23 Port numbers to register as firewall exceptions between the management server and the database or backup server Port number 24041/tcp 24042/tcp Originator Management server Destination • database server • backup server Description This port is used to communicate with Device Manager Agent. It represents the value of the server.agent.
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: • For a local Device Manager: The configuration management information displayed in each window is acquired from Device Manager when each source management window of Replication Manager is displayed. You need not manually refresh the system configuration information before using Replication Manager to set up a storage system or define copy pair configurations.
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 HP P9000 Command View Advanced Edition Suite 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. • Ensure the pair management server recognizes the command device in the target storage system.
6. Install Device Manager Agents on the hosts. For details, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide. NOTE: If there are resources on hosts where Device Manager Agent is not installed, manually add the resource (host). 7. If there is any host on which Device Manager Agent has not been installed, manually add the resource (host) to Device Manager.
4. You must configure BCM as follows: • • • • • • 5.
Application replica environment To configure the required infrastructure for Replication Manager for application (database) replica operations: 1. Install HP P9000 Command View Advanced Edition Suite on the management server. For details, see the HP P9000 Command View Advanced Edition Suite Software Installation Guide. 2. Install P9000 RAID Manager on the pair management servers. For details, see the relevant P9000 RAID Manager manual. 3. Install Device Manager Agents on the pair management servers.
Creating a user-defined application file In the file specified for registering the link information, specify that information in the following format: @TOOL-LINK @NAME registration-key-name @URL startup-URL @DISPLAYNAME display-name-in-links-dialog-box @DISPLAYORDER display-order-in-links-dialog-box @ICONURL icon-URL @TOOL-END The following table describes the available options.
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.
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.
Database server OS Windows Server 2008 SP2 (64-bit) Backup server OS Exchange version Windows Server 2008 SP24 20071 no SP4, SP1, SP2, SP3 Windows Server 2008 SP2 (64-bit) 20101 no SP, SP1, or SP2 Windows Server 2008 R2 no SP Windows Server 2008 R2 no SP 20071 SP3 Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP1 20101 no SP, SP1, or SP2 NOTE: The same Service Pack should be applied on both the database and backup server operating systems. Notes: 1. 2. 3. 4.
Database server OS Backup server OS SQL Server version Windows Server 2012 (no SP) Windows Server 2012 (no SP) 2012 (no SP) Notes: 1. 2. Supported only for use with the Application Agent CLI.
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 31 Database and backup server requirements (file systems) Operating system IPv6 support Windows Server 2003 SP25, 6, 7 N Windows Server 2003 SP2 (IPF)1, 5, 6, 7.
4. 5. Application Agent does not support Veritas Dynamic Multiple Pathing. Provided as a guest OS of virtual server product Windows Server 2008 Hyper-V which is also supported. To execute Application Agent (CLI) on the virtual server, configure the virtual server as the recommended configuration. 6. In the cluster configuration, GPT disks are not supported. Use MBR disks when using this product to perform a backup. 7. Provided as a guest OS of virtual server product VMware ESX/ESXi Server 4.x and 5.
Operating system IPv6 support Required programs P9000 RAID Manager Windows Server 2012 no SP Y 1 Logical volume manager (the standard Windows LDM7,9) Application Agent v 7.4 or later Device Manager Agent2 Notes: 1. Communication using IPv6 is supported even when using FTP with the CLI. For details, see the HP P9000 Replication Manager Application Agent CLI User Guide. 2.
10. Configurations including storage pools are not supported. Table 33 Database and backup server requirements (Microsoft Exchange Server) Operating system IPv6 support Required programs Windows Server 2003 SP23,4,5,6 N P9000 RAID Manager Windows Server 2003 SP2 (64-bit) N Logical volume manager (the standard Windows LDM6) or Veritas Foundation 5.07) Windows Server 2003 R2 SP23,4,5,6 Y Application Agent v 6.
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. For details about Device Manager agent versions that correspond to each OS, see the Device Manager Release Notes. 3. 4. 5. 6. 7. 8. 9. When performing a VSS backup, dynamic disks are not supported.
The account must satisfy the following conditions: • It must have OS administrator permissions. • In Security Policy, Logon as a service must be enabled and Deny logon as a service must be disabled. • It must have the following database access permissions: For backing up an Exchange database: The account used to execute Common Agent Service must belong to the Enterprise Admins group or Exchange Domain Servers group in the domain.
Remote copy type support Microsoft Exchange Server uses VSS to create replicas. Because VSS only supports Cnt Ac-S for remote copies, Replication Manager must use Cnt Ac-S to create remote replicas. (Cnt Ac-A and Cnt Ac-J remote replicas are not supported. VSS does not allow the split time to exceed 10 seconds, and these copy types cannot meet this requirement.) Because Microsoft SQL Server does not use VSS (it uses VDI), there is no limitation on the remote copy type for linkage with Microsoft SQL Server.
Maximum number of Application Agent instances The maximum number of Application Agent instances that can be registered is 128. SQL server log distribution function The SQL Server log distribution function can be used when SQL Server databases are backed up. To do this, there must be two servers; a server from which to distribute the log files and a server to which to send the log files. For this type of configuration, Application Agent must be installed on both servers.
Service name Displayed name Prerequisite condition for startup winmgmt Windows Management Instrumentation Automatic EventSystem COM+ Event System Manual or Automatic MSIServer Windows Installer Manual or Automatic VSS Volume Shadow Copy Manual or Automatic COMSysApp COM+ System Application Manual or Automatic MSDTC Distributed Transaction Coordinator Manual or Automatic If you attempt to install RM Shadow Copy when these Windows services are not set to their default settings, the VSS Pr
NOTE: Application Agent for Exchange does not support Continuous Access Journal. Table 35 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 2003 R2 SP2 (64-bit)1, 2, 3 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.
VMware ESX/ESXi Server Application Agent supports a Windows environment that functions as a guest OS. If provided as a guest OS of the virtual server products, VMware ESX/ESXi Server 4.x and 5.x are also supported. The following notes apply: • Application Agent does not support VMware FT (Fault Tolerance). • Do not run VMware live migration (VMware vMotion) and Application Agent at the same time. If you run both concurrently, execution of Application Agent might fail.
• If any of the conditions above is not satisfied, do not configure the server in a virtual environment. Table 39 Required memory when running Application Agent on a VMware ESX/ESXi virtual machine Installed program Memory Application Agent (for SQL) 128,000KB Application Agent (for Exchange) 128,000KB Application Agent (for SQL and Exchange) 192,000KB NOTE: When using Device Manager Agent on VMware 4.x, you must confirm the prerequisite combination of Device Manager server and Device Manager Agent.
2. 3. 4. 5. 6. 7. SQL Server cluster configurations are supported on the guest OS if the disk being used is directly connected using iSCSI. This is supported for SQL Server 2005 SP3 or later. The status of Windows Server 2008 HyperV support depends on the method used to connect to the guest OS. Windows Server 2008 and Windows Server 2008 R2 are supported. The SQL Server cluster configuration on multiple guest operating systems is supported by V7.1.0 or later if the following conditions are met: a.
Hyper-V Live Migration In addition to the notes provided in the Application Agent CLI and Windows Server 2008 Hyper-V documentation, please note the following points when using the Application Agent CLI under a guest OS intended for live migration: • Use a configuration where the command device is not connected directly to the database server; be sure to use a virtual command device. For details about how to set up a virtual command device, see the P9000 RAID Manager documentation.
%` • The installation path must be an absolute path consisting of 124 bytes or less (subject to program restrictions). 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. Start the installer as follows: • In the case of the integrated installer media for Windows: In the displayed window, click the Install button next to Replication Manager Application Agent. If the window is not displayed, manually execute the installer (setup.exe). The Installer is stored in drive:/AGENTS/HRPM_APP. • In the case of the integrated installer media for UNIX: Execute the installer (setup.exe). The Installer is stored in drive:/AGENTS/HRPM_APP. Proceed to step 7. 4.
16. The Replication Manager - Application Agent Setup window appears. Enter the User name and Password in the respective fields, for an account that has Administrator permissions and the “Log on as a service” permission and click Next. 17. You are asked if you wish to setup the Device Manager agent. If you choose Yes, follow the instructions for installation and configuration of the HDvM agent as described in the HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide. 18.
• Device Manager and P9000 RAID Manager, page 81 • Starting and stopping P9000 RAID Manager, page 81 Command line interface for P9000 RAID Manager Note the following precautions regarding using the P9000 RAID Manager command line interface: • Do not use the P9000 RAID Manager command line interface while carrying out replica operations from Replication Manager.
Perform the following procedure on each server that makes up the virtual server: 1. Create a VBScript file named RecoverJob.vbs in the following location: Application-Agent-installation-folder\DRM\schedule You can specify a different name and location for the VBScript file, but for maintenance reasons, HP recommends that you use the above file name and file storage location. 2. In the VBScript file, specify the recovery processing to be performed by drmjobsch.exe.
LooksAlive = 0 End Function Function IsAlive( ) IsAlive = 0 End Function Function Open( ) Open = 0 End Function Function Close( ) Close = 0 End Function Function Terminate( ) Terminate = 0 End Function 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 95.
The properties and default values are listed in the following table. Table 42 Port numbers in server.properties file Property Default value (port number) Purpose server.agent.port 24041 Port number for the Common agent daemon process (service). server.http.port 24042 Port number for the communication between the Common agent daemon process and the web server process. server.http.localPort 24043 Port number for Common agent Web server.
TIP: After installing Application Agent, if the Copy Controller service or the Common Agent Service is Disabled, change the setting to Automatic. The Common Agent Service is used by other agent programs (such as Device Manager Agent). When you stop Common Agent Service, you should determine whether or not the operation of other agents is affected. Setting error logging options for Application Agent The agent.logger.properties file is used to specify the values of log output-related properties.
Property Description The maximum size of a single Replication Manager log file. This value must be specified in bytes, kilobytes, or megabytes. If the specified value is not followed by KB or MB, the size is assumed to be in bytes. Specifiable values are determined by the specified unit as follows: agent.logger.
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.
NOTE: Device Manager must be running for Replication Manager to operate properly. Starting Replication Manager To start Replication Manager, start HP StorageWorks P9000 Command View AE Common Component as described below. In Windows: Log in as a user with Administrator permissions, and then start the services from the Start menu or the command prompt. Select Start > All Programs > HP StorageWorks P9000 Command View AE >Device Manager > Start Server with Common Services.
In Windows: Log in as a user with Administrator permissions, and then obtain the status from the Start menu or the command prompt. Select Start > All Programs > HP StorageWorks P9000 Command View AE >Device Manager > Server and Common Services Status. From the command prompt: installation-folder-for-Common-Component\bin\hcmdssrv /status In Linux: installation-folder-for-Common-Component/bin/hcmdssrv -status Example 1: Execution results if Replication Manager is running KAPM05007-I Already started service.
Properties related to Replication Manager The properties required by Replication Manager are specified in the following properties files stored on the management server: • • • • • • • logger.properties, page 92 serverstorageif.properties, page 96 bcmif.properties, page 97 agentif.properties, page 97 appagentif.properties, page 98 base.properties, page 99 RpMCLI.properties, page 100 With the exception of RpMCLI.
File serverstorageif.properties Property Default value (unit) logger.UserOperation.MaxBackupIndex 5 (files) logger.UserOperation.MaxFileSize 10MB logger.RefreshStatus.enabled true logger.RefreshStatus.MaxBackupIndex 2 (files) logger.RefreshStatus.MaxFileSize 10MB logger.AppConfig.MaxBackupIndex 3 (files) logger.AppConfig.MaxFileSize 10 (MB) logger.AppConfig.enabled true logger.AppStatus.MaxBackupIndex 6 (files) logger.AppStatus.MaxFileSize 20 (MB) logger.AppStatus.
File Property Default value (unit) hdvmagtif.PollingInterval 30 (seconds) appagentif.connectTimeout 30 (seconds) appagentif.responseTimeout 3600 (seconds) base.repositry.synchronize.polling true base.taskscheck.interval 120 (seconds) base.taskscheck.maxcount 0 (times) base.taskscheck.mf.interval 120 (seconds) base.taskscheck.mf.maxcount 0 (times) base.alert.automarking true base.refreshdginfo.exec 1 base.repositry.synchronize.interval 10 (minutes) base.repositry.synchrocheck.
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 47 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 48 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 50 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 51 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 52 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.
The following table describes the available properties and settings. Table 54 List of properties in the RpMCLI.properties File Property Description This property specifies output level of the Replication Manager CLI trace log. The values that can be specified are: ERROR, WARN, INFO, DEBUG. Default value: INFO The values are case sensitive. The meaning of each value is as follows: RpMCLI.diaglevel • ERROR: Messages that indicate an abnormal occurrence and error messages are output.
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. The following routes can be encrypted: (1) Between HP StorageWorks P9000 Command View Advanced Edition Suite Common Component on the management server and the Web browser on the management client.
Figure 13 Communication Routes Used by Replication Manager The following four 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 a Business Continuity Manager Software (on the host) unless IHS is used. • Between Replication Manager (on the management server) and P9000 mainframe agent (on the host).
Figure 14 Flow of operations for setting up secure communications between Common Component and a Web browser For more information on the procedures, see the following descriptions in the HP P9000 Command View Advanced Edition Suite Software Administrator Guide: • Creating a secret key for Common Component • Creating a certificate signing request for Common Component • Creating a secret key and a certificate signing request for Common Component (Advanced security mode) • Applying to a certificate authority f
Securing communications between Replication Manager and the Device Manager server To encrypt communications between Replication Manager on the management server and the Device Manager server (local or remote), you must create a server certificate for the Device Manager server and import it into the truststore (jssecacerts) file in Replication Manager.
• • • • • Importing a server certificate into the Device Manager server truststore Downloading a Device Manager server truststore file Exporting a Device Manager server self-signed certificate Importing a server certificate into the truststore Checking the server certificates imported into the truststore After importing the server certificate for the Device Manager server to the truststore (jssecacerts), select HTTPS as the transmission protocol in the Replication Manager GUI window for adding (or the win
Figure 16 Flow of operation for setting up secure communications between Replication Manager and BCM (IHS) If you use a well-known certificate authority (CA), its server certificate might already be in the truststore (jssecacerts). In this case, you do not need to import the CA’s server certificate again. For more information on the procedure for using BCM (IHS) as an SSL server, see the description of setting up HTTPS connections in the HP P9000 for Business Continuity Manager Software Installation Guide.
NOTE: Regarding server certificates: • If you manage multiple BCM (IHS) hosts as information sources, you must create server certificates for each server and import them into the truststore (jssecacerts) for the management server running Replication Manager. • A secure method must be used to transmit the server certificate for the IHS to the management server running Replication Manager. Audit log event categories This section describes the information output in the Replication Manager audit log.
Description of category Audit event Severity Successful resource group property editing 6 Failed resource group property editing 3 Addition of a user to a resource group (GUI) Successful user addition to a resource group 6 KAPM02632-I Failed user addition to a resource group 3 KAPM02637-E Removing of a user from a resource group (GUI) Successful user removal from a resource group 6 KAPM02633-I Failed user removal from a resource group 3 KAPM02638-E Assignment of a user to a resource gro
Description of category Audit event Severity Message ID KAVN10014-E An attempt to edit or distribute the disk configuration definition file has failed. 3 KAVN10017-E KAVN10020-E KAVN10023-E Management host change operation KAVN10024-I Editing or distribution of the copy group configuration definition file has started. 6 The copy group configuration definition file was successfully edited or distributed. 6 An attempt to edit or distribute the copy group configuration definition file has failed.
Description of category Audit event Severity Message ID KAVN10033-E KAVN10036-E Creation, editing, execution, canceling, or deletion of a task has failed. 3 KAVN10039-E KAVN10042-E KAVN10045-E 112 KAVN10046-I Mounting or unmounting has started. 6 Mounting or unmounting has succeeded. 6 Mounting or unmounting has failed. 3 Take over operation has started 6 Take over operation is terminated 6 Take over operation timed out.
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 117.
Figure 17 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 123. 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 CLI log files Executing the collection command This section describes how to use the cvxpaegetlogs command. 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).
Troubleshooting Application Agent operations This section explains how to troubleshoot problems with Application Agent, including how to collect information when calling for support: • • • • Resolving Application Agent installation and uninstallation errors, page 117 Resolving Application Agent operation errors, page 119 Collecting support information with the hrpmap_getras command, page 119 Application Agent events that can be ignored, page 120 TIP: When collecting event log information to diagnose a pro
Application Agent and VSS Provider installer trace log files The details and results of an Application Agent installation or uninstallation (including the VSS Provider) are output to installer trace log files. You can use these files to analyze the causes of errors that occurred during installation or uninstallation. Application Agent rpm_app_agt_inst.log VSS Provider vssprv_inst.
Resolving Application Agent operation errors Application Agent is set up to support application linkage on hosts (database and backup servers). If an error occurs during user operation, an error message provides information indicating the host where the error occurred, regardless of whether that host is a database or backup server. For this reason, you must collect information about the host occurred.
Files Description Location copied from Deployment descriptor file of Application Agent Common-Agent-installation-folder\mod\ hrpmap error.log service.log trace.log alet.xml Table 59 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 Virtual Disk Service 1 Unexpected Failure. Error code: 1@02000018 Backup server A VSS backup is executed. Error Virtual Disk Service 1 Unexpected Failure. Error code: 48F@02000018 Backup server A VSS backup is executed. Error VDS Dynamic Provider 10 The provider failed while storing notifications from the driver.
Server on which event occurred When message is output to event log Type Source Event ID Message SCR env. target A VSS backup is executed. Error Microsoft Exchange Repl 2104 Log file action LogCopy failed for storage group "xxx". Reason: CreateFile("xxx") = 2 Backup server Simultaneous backups are executed in a cascade configuration. Error Service Control Manager 7034 The Logical Disk Manager Administrative Service service terminated unexpectedly. It has done this xx time(s).
Troubleshooting detailed message RPM-00824 Detailed message RPM-00824 indicates that the HP StorageWorks P9000 Command View AE Common Component database memory area is insufficient. Check the amount of space available on the disk on which Replication Manager is installed.
3.
Transferring the database to a Windows Microsoft Cluster Server (MSCS) The following topics describe the procedures for moving data when Microsoft Cluster Server (MSCS) is used. Make sure that before executing a transfer, you adhere to the conditions described in “Transferring the database to a cluster server” on page 124. Procedure on the executing node 1.
7. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Move Group to switch the node to the standby node. Procedure on the standby node 1. On the standby node, make sure that the standby node currently owns the HP StorageWorks P9000 Command View AE Common Component service and the shared disk. 2.
4. Move the database onto the shared disk and follow all procedure as described in “Using the hcmdsdbclustersetup command” on page 128. NOTE: This step is unnecessary if other P9000 Command View AE suite products have been set up in a cluster configuration. Don't separate the shared disk from the active node until the hcmdsdbclustersetup command is complete.
6. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Move Group to switch the node to the executing node. 7. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Online. Using the hcmdsdbclustersetup command If there are no P9000 Command View AE suite products in a cluster configuration on the same host, execute the command shown below.
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 Troubleshooting when copy pairs are not recognized In an environment where Device Manager and P9000 RAID Manager manage copy pairs, if information about the existing copy pairs cannot be recognized after refreshing the configuration information, take the following actions to correct the problem: 1.
Installation of Device Manager Agent Make sure Device Manager Agent is installed on both pair management servers that manage a primary and secondary volume. Link between Device Manager server and Device Manager Agent Make sure Device Manager Agent links correctly with Device Manager server using the hdvmagt_account command. If the link is incorrect, execute this command on the pair management server to change the settings. 1.
Properties of Device Manager Agent Make sure Device Manager Agent properties (stored in the pair management server) are correct. For details about the properties to be specified, see “Setting up the prerequisite environment” on page 49. If you change the properties, restart Device Manager Agent.
Recognition of the replication configuration Make sure that Device Manager server correctly recognizes the replication configuration that is managed by a host or pair management server. NOTE: On copy pairs that configure remote copies, you do not need to check this item. Check the following: • On the host (pair management server) properties window, make sure that you can click the button to view the pair information managed by the host.
Replica creation fails silently If replica creation fails when there is not enough disk space to create transaction log files, there may be no error messages displayed. To delete transaction logs periodically, select Truncate Exchange transaction log files in the Execution Options of the Create Replica Wizard (2. Setup Options) page. When this option is selected, transaction log files will be automatically deleted every time a backup is performed.
4. Start Exchange System Manager and view the properties of the storage group to be recovered. Check the location of the transaction logs as well as the initial characters of the log file. The initial characters are E0n, where n is from 0 to 3. 5. Of the transaction log files in the storage group to be recovered, move those not matching the description in step 4 to a new folder. 6. From the Exchange System Manager, mount the information store to be recovered. 7.
backup server might remain Online. If this happens, perform the following procedure to change the disk status of secondary volumes on the backup server to Offline: 1. Use the P9000 RAID Manager command inqraid $Phys -CLI to check the disk numbers of all secondary volumes that are the backup destinations. The disk numbers are shown in the DEVICE_FILE column. 2. Start the diskpart command. 3. To display the current disk statuses, enter list disk.
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.
Conventions This guide follows the conventions shown in Table 61 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 Synchronous Continuous Access Synchronous • Continuous Access XP Synchronous • P9000 Continuous Access Synchronous • XP Continuous Access Synchronous 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 Version compatibility with other Command View AE Suite products This appendix describes the compatibility between versions of Replication Manager and other Command View AE Suite product versions. Restrictions when Replication Manager and Device Manager versions differ The following restrictions for configuring the Replication Manager system are dependent on the version of Device Manager that is installed on the components (management server, pair management server, and hosts).
Release Number Restriction Device Manager Server or Device Manager Agent 7.1 or earlier Mainframe system volume attributes may not display correctly.
B Supported functions and unsupported configurations This appendix provides information on functions and supported by Replication Manager.
Open Creating and deleting copy pairs Mainframe DevMgr Server DevMgr Agent BCM P9000 mainframe agent N Y Y* N Y Y N Replication operation support functionality Changing copy pair statuses N Legend * - Only the pair definition function for creating a copy group definition file is supported. The creation of copy pairs is not supported. List of tasks supported for each storage system The tasks supported by Replication Manager depend on the storage system model.
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Replication status display Acquisition of latest pair statuses Acquisition of latest remote-copy performance information Replication management logical-group creation and deletion Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Site-view-based "Site" definit
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N N N N N N Y Y Y N N N N N N N Y Y Y N N n/a n/a n/a N N Y Y Y N N n/a n/a n/a N N Y Y Y N N n/a n/a n/a N N Y Y Y N N N N N N N Y Y Y N N N N N N N Y Y Y N N N N N N N N Y Y n/a n/a n/a n/a n/a N N N Y Y n/a n/a n/a n/a n/a N N Y
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N N N N Y Y Y Y Y N N N N N N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Re
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y N N Y Y Y N N Y3,4 Y3,4 Y3,4 Y Y Y Y Y N N Y4 Y4 Y4 N N Y5,6 Y5,6 Y6,7 N N N N N Automated alert renotification Detailed monitoring and alert notification of each individual copy pai
4. 5. 6. 7. This function can be used only when BCM is used. It cannot be used with P9000 mainframe agent. Continuous Access Journal, Continuous Access, and Continuous Access Synchronous are supported. No other remote copy or local copy functions are supported. Device Manager agent 6.4.0 or later must be installed on the host. Continuous Access Journal and Continuous Access Synchronous are supported. No other remote copy or local copy functions are supported.
Secondary-side storage system Primary-side storage system HP StorageWorks P9500 Disk Array XP12000/ XP10000/ SVS200 Universal Storage Platform V/VM XP24000/ XP20000 HP StorageWorks P9500 Disk Array -- -- Y --: Cannot be combined Supported storage system combinations (Cnt Ac-S ) Secondary-side storage system Primary-side storage system XP12000/ SVS200 XP24000/ XP20000 HP StorageWorks P9500 Disk Array XP12000/ XP10000/ SVS200 Universal Storage Platform V/VM XP24000/ XP20000 HP StorageWorks P9500
Supported storage system combinations (Cnt Ac-J) Secondary-side storage system Primary-side storage system XP12000/ SVS200 XP24000/ XP20000 HP StorageWorks P9500 Disk Array XP12000/ XP10000/ SVS200 Universal Storage Platform V/VM XP24000/ XP20000 HP StorageWorks P9500 Disk Array Y Y Y Y Y Y Y Y Y --: Cannot be combined Unsupported configurations (open systems) The following is a list of unsupported open systems pair configurations.
Unsupported configuration Requirement for configuration The storage systems for the secondary volumes in the same copy group are different. Alternative configuration to implement requirement Unify the S-VOLs using the same storage system into the same CTG*. Legend: *: When primary volumes and secondary volumes in the same copy group belong to different storage systems, it is necessary to create CTGs with volumes that have the same combination of primary and secondary storage systems.
Unsupported configuration The cascade destination contains multiple copy groups. Requirement for configuration Alternative configuration to implement requirement To create a backup of only some volumes. Create CTGs in the cascade source according to the cascade destination copy groups. Pairs in the cascade source must belong to any CTG.
Supported functions and unsupported configurations
C 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 155. 2. Follow the instructions in “Adding a storage system” on page 156.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 64 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 66 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
D 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 Manager 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 155 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 67 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 169
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 Administrator privileges (UAC), agent.logger.properties, 85 agentif.properties file, 97 Application Agent and P9000 RAID Manager, 80 cluster configuration, 71 - 72, 81 described, 57 error log options, 85 installing, 78 log files, 83, 118 maximum number, 70 port numbers, 83 reinstalling, 69 requirements, 58, 71 service, 84 troubleshooting, 117 audit event, 109 audit log event categories, 109 B base.properties file, 99 base.repositry.synchronize.polling, 99 BCM Agent, 23 - 24, 47 bcmif.
I information source, 173 infrastructure mainframe, 52 open systems, 50 inqraid $Phys -CLI command, 135 L LDEV maximum number, 36 link menu, 54 log file log amount of data, 95 logger.
T technical support HP, 137 troubleshooting, 113 maintenance information, 114 resolving errors, 113 RPM-00824, 123 U UAC, 87 unsupported configurations, 151 - 152 V VMware ESX/ESXi support, 74 VSS Provider log files, 118 requirements, 70 W web sites HP, 137 Configuration Guide 179
