HP XP7 Replication Manager Configuration Guide Part number: TK981-96012 First edition: April 2014
Legal and notice information © Copyright 2014 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 ..............................
Mainframe systems environment ........................................................................................... Application replica environment ........................................................................................... Adding a link menu to the GUI display ....................................................................................... hcmds64link command options ............................................................................................
About Replication Manager log output ........................................................................... 95 serverstorageif.properties .................................................................................................... 96 bcmif.properties ................................................................................................................. 97 agentif.properties ...............................................................................................................
Disk status remains online after replica operation is complete ................................................. 135 7 Support and other resources ............................................................ 137 Contacting HP ........................................................................................................................ HP technical support ......................................................................................................... Subscription service ................
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 Items specified in the user-defined application file ........................................................ 56 30 Server hardware requirements .................................................................................. 59 31 Supported database and backup server combinations (Microsoft Exchange Server) ......... 59 32 Supported database and backup server combinations (Microsoft SQL Server) .................
64 Product reference conventions ................................................................................. 138 65 Restrictions when Replication Manager and Device Manager versions differ ................. 141 66 Restrictions when Replication Manager and HP XP7 Business Continuity Manager versions differ ................................................................................................................... 142 67 Items required to execute Device Manager CLI ...............................
Preface This document describes the installation and configuration process for HP XP7 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 XP7 Replication Manager User Guide. The following tables list and describe system components for each type of system and provide an overview of the software components.
System components Software included in system components Description A management server provides management information in response to requests from management clients. Replication Manager and Device Manager server (a prerequisite program of Replication Manager) are installed on the management server. 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 RAID Manager supports your storage system.) RAID Manager Replication Manager uses the 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 RAID Manager.
Figure 5 Mainframe configuration using HP XP7 Business Continuity Manager (BCM) Figure 6 Mainframe configuration using Device Manager server only or XP7 mainframe agent Configuration Guide 21
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. Replication Manager runs on the management server.
System components Software included in system components Description Microprograms Storage system Note: If necessary, register licenses for products (such as for Continuous Access Synchronous or Continuous Access Journal). A storage system is used to store data accessed by hosts. Table 4 Overview of mandatory software for mainframe management Software Description Used to centrally manage the replication of storage system volumes in large-scale system configurations.
Software Description Used to collect information about hosts and storage systems. XP7 mainframe agent In conjunction with XP7 mainframe agent, Replication Manager monitors information about configurations and statuses of copy pairs created by Peer to Peer Remote Copy (PPRC). For details about XP7 mainframe agent, see the HP XP7 Command View Advanced Edition Mainframe Agent Installation and Configuration Guide.
Prerequisites for data migration using virtual IDs (HP P9500) If a volume is an HP P9500 storage system and belongs to a resource group used for a data migration function that uses virtual IDs, Replication Manager can display the physical IDs and define pair configurations specifying the physical IDs.
For remote copy: • A copy pair consisting of volumes in one virtual storage machine configured in multiple physical storage machines. • A copy pair consisting of volumes in multiple virtual storage machines with each virtual storage machine configured in different physical storage machines (This configuration is supported only when both storage systems are HP XP7). CAUTION: Take note of the following: • If you migrate data using a virtual storage machine, any existing backup catalogs are no longer valid.
Configurations for replica management The following figure depicts a composite configuration where copy pairs and application replicas are managed. The system components (hosts) are labeled with both the pair management terms (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 Prerequisite programs Windows operating system Windows Server 2008 R2 SP1 • 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.
The following table lists the server specifications required for a Linux environment. Table 8 Linux OS and programs for a management server Linux operating system Prerequisite programs Red Hat Enterprise Linux 5.8 Supports IPv4 and IPv6 connections Red Hat Enterprise Linux 5.9 Supports IPv4 and IPv6 connections Red Hat Enterprise Linux 5.10 Supports IPv4 and IPv6 connections Red Hat Enterprise Linux 6.0 Supports IPv4 and IPv6 connections The following RPM packages must be applied to this OS: • kernel-2.6.
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 2008 R2 SP1 Windows Server 2012 no SP Windows Windows Server 2012 R2 The following table lists the server specifications required for a cluster environment.
For details on the latest virtual memory requirements, see the documentation for each product. Table 12 Virtual memory requirements for each product Product Virtual memory capacity (MB) Common Component (for x64) XP7 Command View AE1 • Device Manager • Tiered Storage Manager • Replication Manager • Host Data Collector 2501 Small memory heap size 6700 Medium memory heap size 7200 Large memory heap size 8200 Notes: 1.
NOTE: If you are using a Windows 32-bit environment, you cannot set “Large” as a memory heap size. For details about how to increase the memory heap size, see the HP XP7 Command View Advanced Edition Installation and Configuration Guide. This section discusses the following: • Maximum number of copy pairs, page 35 • Maximum number of LDEVs, page 36 • Log data and number of copy pairs, page 37 NOTE: Mainframe system resources managed by RAID Manager must be managed as open system resources.
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.TimeOut in the agent.properties file For details about how to edit the properties, see the chapter that describes the settings for using Replication Manager to manage copy pairs in the HP XP7 Command View Advanced Edition Administrator Guide.
1. Use this formula to determine the number of LDEVs and confirm that the number is less than or equal to the maximum: (number-of-open-LDEVs * 2) + number-of-mainframe-LDEVs Log data and number of copy pairs The amount of log data depends on the number of copy pairs to be managed. You can change the maximum number of log files and the maximum data size for each log file. For details, see “logger.properties” on page 93.
Windows operating system Windows 8 no SP Windows 8.1 no SP Web browser Internet Explorer 10.0 (only the 32-bit version is supported) Internet Explorer 11.0 (only the 32-bit version is supported) Notes: 1. Operation on Server Core is not supported. 2. Operation on Minimal Server Interface is not supported Table 17 Supported Linux OS and web browsers for a management client Linux operating system Web browser Red Hat Enterprise Linux 5.3 (32-bit) Firefox ESR 17.0.x Red Hat Enterprise Linux 5.
System requirements for hosts and pair management servers This section describes the requirements for hosts and pair management servers. Requirements for open systems The following table shows the requirements for hosts and pair management servers. For information on restrictions, see “Restrictions when Replication Manager and Device Manager versions differ” on page 141.
For best results, ensure that the version numbers of installed XP7 Command View AE products are synchronized. Requirements for mainframe systems The following table describes the requirements for hosts. For information on restrictions, see “Restrictions when Replication Manager and HP XP7 Business Continuity Manager versions differ” on page 142. Table 19 Requirements for hosts (for mainframe systems) Operating system Prerequisite programs HP XP7 Business Continuity Manager 5.
use HP XP7 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 XP7 For details, see the HP XP7 Command View Advanced Edition Administrator Guide.
• For port numbers used by Application Agent, see “Changing Application Agent port numbers” on page 83 Table 20 Port numbers to register as firewall exceptions between the management server and management clients Port number 22015/tcp 22016/tcp Originator Management client Management client Destination Description Management server This port is used to access the HBase 64 Storage Mgmt Web Service of Common Component when communicating with a management client.
1. When IHS is used to communicate with Business Continuity Manager via SSL, register the port number for IHS as a firewall exception. Table 24 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 XP7 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 XP7 Business Continuity Manager to acquire or delete copy pairs. BCM performs the operations on the storage system.
Replication Manager issues a request to HP XP7 Business Continuity Manager or XP7 mainframe agent, which acquires the status of copy pairs from the storage system. (Only BCM can change the status.) Acquiring performance information Replication Manager issues a request to HP XP7 Business Continuity Manager or XP7 mainframe agent to acquire performance information from the storage system (such as the sidefile usage rate, journal volume usage rate, pool volume usage rate, and write delay time (C/T delta)).
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 HP XP7 Command View AE 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. 2.
Before (v6.x or v7.x) Item After (v8.x) For x86: HP XP7 CVAE default installation folder %ProgramFiles%\CVXPAE For x64: %ProgramFiles%\CVXPAE %ProgramFiles(x86)%\CVXPAE HP XP7 CVAE common component default installation folder HP-XP7-CVAE-installation-folder\ Base HP-XP7-CVAE-installation-folder\ Base64 NOTE: %ProgramFiles% and %ProgramFiles(x86)% are Windows environment variables. Table 27 Command names and file paths changed after upgrade to v8.x (Linux) Item Before (v6.x or v7.x) After (v8.
Figure 12 Infrastructure configuration workflow Open systems environment To configure the required infrastructure for Replication Manager for an open system: 1. Install HP XP7 Command View Advanced Edition on the management server. For details, see the HP XP7 Command View Advanced Edition Installation Guide. 2. Add all resources (storage systems) to Device Manager. Add the resources (storage systems) that are to be managed by Replication Manager.
3. Install RAID Manager on the pair management servers. • Ensure the pair management server recognizes the command device in the target storage system. • If the pair management server is equipped with more than one NIC, the Device Manager agent and RAID Manager use the same IP address. For details, see the relevant RAID Manager manual. 4. Install Device Manager Agents on the pair management servers. After Device Manager Agents are installed, specify the information required for using them.
8. Ensure that all of the conditions below are satisfied: • The requirements (microcode and system configuration) for Business Copy or Continuous Access or other required storage system volume replication functions must be satisfied. For details about the requirements and the configuration procedures, see the storage system documentation for the applicable storage system model.
5.
4. Install Application Agent on the hosts (database server and backups server). For details, see Chapter 3 on page 57. Adding a link menu to the GUI display In the GUI, 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 the global tasks bar area. To register or delete a link, execute the hcmds64link command, as follows.
The following table describes the available options. Table 29 Items specified in the user-defined application file Item Description @TOOL-LINK Start key for the user-defined application file. This item is required. @NAME registration-key-name This information is used as the registration key. Specify a name that makes the link information unique, and use no more than 256 bytes. This item is required. @URL startup-URL Specifies the URL to be started in the GUI. Use no more than 256 bytes.
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/2013 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 Backup server OS Exchange version Windows Server 2008 R2 no SP Windows Server 2008 R2 no SP 20071 SP3 Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP1 Windows Server 2012 no SP Windows Server 2012 no SP 20101 no SP, SP1, SP2. SP3 20131 no SP 20101 SP3 2013 no SP NOTE: The same Service Pack should be applied on both the database and backup server operating systems. Notes: 1. 2. The Exchange Management Tool is required on the database server and backup server.
Database server OS Backup server OS Windows Server 2008 x64 (SP2) Windows Server 2008 x64 (SP2) Windows Server 2012 (no SP) Windows Server 2012 (no SP) SQL Server version 2012 (no SP, SP1) Notes: 1. 2. Supported only for use with the Application Agent CLI. Supported when the database server and backup server are Windows Server 2008 x64 (SP2) or Windows Server 2008 R2 (SP1).
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.
3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. LDM basic disks are supported. 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. In the cluster configuration, GPT disks are not supported. Use MBR disks when using this product to perform a backup.
Operating system IPv6 support Required programs Windows Server 2008 R2 SP13,4.5 Y1 RAID Manager12 Logical volume manager (the standard Windows LDM7,9) Windows Server 2008 R2 SP1 (IPF)3,5 Y Application Agent v 7.1 or later Device Manager Agent2 RAID Manager12 Windows Server 2012 no SP 5,11 Y 1 Logical volume manager (the standard Windows LDM7,9) Application Agent v 7.4 or later Device Manager Agent2 Notes: 1. 2. Communication using IPv6 is supported even when using FTP with the CLI.
12. The architecture of RAID Manager must match that of the OS. Table 37 Database and backup server requirements (Microsoft Exchange Server) Operating system IPv6 support Required programs Windows Server 2003 SP23,4,5,6,12 N RAID Manager13 Windows Server 2003 SP2 (64-bit)12 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.
• The version of Device Manager agent is earlier than 6.4 • The version of RAID Manager is earlier than 01-17-03/05 You must configure the following setting in the Device Manager properties (server.properties) file: server.agent.rm.optimization.userHorcmFile=true 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 XP7 Command View Advanced Edition Installation and Configuration Guide.
* 0.3 + number-of-files-or-directories-to-be-backed-up * 4.0 + number-of-paired-volumes-to-be-backed-up * 0.1) * number-of-backup-catalogs The number-of-backup-catalogs is determined as follows: • For a database server: The number of backup catalogs backed up from the P-VOLs to the S-VOLs. If a single P-VOL is defined to be paired with multiple S-VOLs, Application Agent can manage multiple backup generations. The number corresponds to the number of backups made in such a configuration.
Environment variables Do not specify HORCMINST or HORCC_MRCF in a system environment variable. Also, do not specify HORCM_CONF or HORCMPERM in a system or user environment variable. HORCM options and RAID Manager HORCM_DEV, HORCM_LDEV, or HORCM_LDEVG need to be specified in the configuration definition files of RAID Manager instances used by Application Agent.
• Business Copy (multiple generations), Continuous Access Synchronous or Continuous Access Journal configurations Dynamic recognition of secondary volumes When a secondary volume is dynamically recognized, do not use the LUN#0 disk among the physical disks that are connected to the device adapter port for the primary and secondary volumes. When the physical disk of LUN#0 is used, other physical disks might not be recognized.
Windows services Before you install Application Agent, use the Services pane in the Windows Computer Management console (for Windows Server 2003) or Server Manager console (for Windows Server 2008) to ensure that the Windows services are set to the default settings as shown in the following table.
NOTE: Application Agent for Exchange does not support Continuous Access Journal. Table 39 Volume replication functions required Storage system Volume replication function Business Copy Continuous Access Software XP12000/XP10000/SVS200 Continuous Access Synchronous XP24000/XP20000 Continuous Access Asynchronous Snapshot Continuous Access Journal Cluster support Application Agent can be linked to cluster software to increase the availability of the system.
Database server OS Cluster software Windows Server 2008 no SP/SP1, SP2 Windows Server 2008 IPF no SP/SP1, SP2 Windows Server 2008 no SP/SP1, SP2 (64-bit) Windows Server 2008 R2 no SP or SP1 Windows Server Failover Clustering Windows Server 2008 R2 IPF no SP or SP1 Windows Server 2012 no SP 4 Notes: 1. 2. 3. 4. Cluster environments are not supported for usage with GPT disks. Please use MBR disks.
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.
Required virtual memory when running Application Agent on a VMware ESX/ESXi virtual machine See Virtual memory for information on virtual memory requirements. Windows Server Hyper-V Application Agent supports a Windows environment that is run as a guest OS of Windows Server 2008 Hyper-V and Windows Server 2012 Hyper-V. The following tables list the scope of support for each Application Agent product.
7. A cluster configuration on a guest OS is not supported.
Virtual memory required for Application Agent on a virtual machine of Windows Server Hyper-V See Virtual memory for information on virtual memory requirements. Application Agent installation location By default, the Common-Agent-Component-installation-folder is defined as follows.
1. 2. Install Replication Manager on the management server. Set the value of base.refreshdginfo.exec in the base.properties file to 0. 3. Restart the Common Component service as described in “Starting Replication Manager” on page 88 NOTE: When base.refreshdginfo.exec is set to zero, Replication Manager cannot manage copy groups defined in storage (device groups). Installing Application Agent NOTE: This procedure applies to both cluster and non-cluster configurations.
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...
18. When the installation finishes, restart Windows. NOTE: If the Application Agent is installed on a host without a database application installed, Replication Manager will fail in any attempts to obtain information by refreshing the host. If this occurs, one of the following error messages is displayed: RPM-11004 - The specified SQL instance name is invalid or no SQL instance settings exist. RPM-11509 - Exchange Server has not yet been installed on this system.
• Do not use the RAID Manager command line interface while carrying out replica operations from Replication Manager. • If you use the RAID Manager command line interface to change a copy pair configuration, be sure and refresh the system from Device Manager, followed by updating the pair configuration and refreshing the hosts from Replication Manager. Protection function of RAID Manager Application Agent does not support the protection function of RAID Manager.
2. In the VBScript file, specify the recovery processing to be performed by drmjobsch.exe. At the entry point Function Online( ), specify that the following command is to be executed (where virtual-server-name is the name of a virtual server to be put online): Application-Agent-installation-directory\DRM\bin\drmjobsch.exe -recover -hostname virtual-server-name See Sample VBScript file for a completed script. In the example, Application-Agent-installation-folder is C:\Program Files\CVXPAE\DRM. 3.
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.
Property Default value (port number) Purpose server.http.localPort 24043 Port number for Common agent Web server. Note the following: • Acceptable port number values are 1-65535. • Avoid using small port numbers because such numbers might conflict with other applications. • The port numbers set in the server.properties file must be unique and cannot be shared by any other processes. • If you change the value of server.agent.
Setting error logging options for Application Agent The agent.logger.properties file is used to specify the values of log output-related properties. The file is stored in the following location: C:\XP7-Command-View-AE-Common-Agent-Component-installation-folder\agent\ config\ If a value is not specified in the agent.logger.properties file or if the specified value is outside the specifiable range, the default value is used.
Type Description ERROR Error occurred during the process execution or startup. FATAL Fatal exception occurred in the code and the execution stops.
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.
Starting Replication Manager To start Replication Manager, use the appropriate procedure below. In Windows 1. 2. Log in as a user with Administrator permissions. Perform one of the following (a or b): a. Using the Start menu: In Windows Server 2008: Select Start > All Programs > HP XP7 Command View Advanced Edition >Manage Services > Start - Command View AE.
Common-Component-installation-folder\bin\hcmds64srv /stop In Linux 1. 2. Log in as root user. Execute the following command: Common-Component-installation-directory/bin/hcmds64srv -stop This command also stops the services of other HP XP7 Command View AE products, so you should consider the operation of these products before executing this command. Checking the operation status of Replication Manager To see whether Replication Manager is running, use the appropriate procedure below. In Windows 1. 2.
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Common Service KAPM05009-I Already stopped service. service-name=Device Manager Server Service KAPM05009-I Already stopped service. service-name=Tiered Storage Manager Server Service If you execute the command as described above, you can also check whether the HiRDB service is running. If it is running, the following message appears in the execution results: KAPM06440-I The HiRDB service has already started.
NOTE: Under normal circumstances, the agentif.properties properties do not need to be changed. To change their values, you need expert knowledge of Device Manager Agent. Table 49 List of Replication Manager properties File Property Default value (unit) logger.loglevel 20 logger.sysloglevel 0 logger.MaxBackupIndex 6 (files) logger.MaxFileSize 20MB logger.DB.loglevel 20 logger.DB.MaxBackupIndex 6 logger.DB.MaxFileSize 20MB logger.RefreshConfig.enabled true logger.RefreshConfig.
File Property Default value (unit) ssif.alertTimeout 1800 (seconds) bcmif.socketTimeout 3600 (seconds) bcmif.socketConnectTimeout 5 (seconds) bcmif.ReconnectionInterval 60 (seconds) bcmif.ReconnectionCount 5 (times) 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.
File Property Default value (unit) RpMTaskCLI.MaxFileSize 20 (MB) logger.properties The logger.properties file is used to specify the values of log output-related properties. If a value is not specified in the logger.properties file, or if the specified value is outside the specifiable range, the default value will be used. The following table describes the available properties and settings. NOTE: File size values must be specified in bytes, kilobytes, or megabytes.
Property Description Threshold value for output of a database-related log file. logger.DB.loglevel Specifiable values: 0, 10, 20, and 30 (in decreasing order of importance from left to right). Default value: 20 Maximum number of backup files for a database-related log file. logger.DB.MaxBackupIndex Specifiable values: 1 to 16 (files) Default value: 9 Maximum size of a database-related log file. logger.DB.
Property Description Maximum size of a pair status update log file. logger.RefreshStatus.MaxFileSize Default value: 10 MB Maximum number of application configuration log backup files. logger.AppConfig.MaxBackupIndex Specifiable values: 1-32 (files). Default value: 3 Maximum size of the application configuration log file. logger.AppConfig.MaxFileSize Specifiable values: 1-2047 (MB). Default value: 10 Log function on/off switch for the application configuration log. logger.AppConfig.
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 51 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 XP7 Business Continuity Manager or between Replication Manager and XP7 mainframe agent. The following table describes the available properties and settings. Table 53 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 54 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 55 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 XP7 Command View Advanced Edition software) database synchronization function performs a check.
Property Description This property specifies the maximum number of requests Replication Manager can receive. You must specify this property if you use the Replication Manager CLI. A value of zero (0) sets the value to the Java default value (50). base.rmi.backlog This property is available if the value of the base.rmi.enabled property is set to true. Values that can be specified: 0-1000 Default value: 100 base.taskschedule.
Property RpMTaskCLI.MaxFileSize Description This property specifies the maximum size of a trace log file, which are created when the GetTasks or ExecuteTask command is executed.
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 XP7 Command View Advanced Edition 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 (on the host) unless IHS is used. • Between Replication Manager (on the management server) and XP7 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 XP7 Command View Advanced Edition Administrator Guide: • • • • Creating a secret key and a certificate signing request for Common Component Applying to a certificate authority for a Common Component server certificate Enabling SSL/TLS for Common Component Changing the URL for accessing XP7 Command View AE products (hcmd
Figure 15 Flow of operations for setting up secure communications between Replication Manager and the Device Manager server 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.
• • • • • • • • Creating a certificate signing request for Device Manager server Applying to a certificate authority for a Device Manager server certificate Importing a server certificate into the Device Manager server keystore 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 of HP XP7 CVAE Checking the server certificates i
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 XP7 Business Continuity Manager Installation Guide.
Audit log event categories This section describes the information output in the Replication Manager audit log for the ConfigurationAccess category. For details about the information for other audit categories, please see the HP XP7 Command View Advanced Edition Administrator Guide. Each audit event is assigned a severity level. You can filter audit log data to be output according to the severity levels of events.
Description of category Audit event Severity Message ID KAVN10001-I The pair operation task (pair create, delete, modify, or edit group name) has started. 6 KAVN10006-I KAVN10010-I KAVN10089-I The pair operation task (node addition or deletion) has started. 6 The pair operation task (node addition or deletion) was successful. 6 KAVN10085-I KAVN10087-I KAVN10086-I KAVN10088-I KAVN10002-I Copy pair operation The pair operation task (pair create, delete, modify, or edit group name) was successful.
Description of category Audit event Severity Secondary volume hiding operation started. 6 Secondary volume hiding operation completed. 6 Secondary volume hiding operation failed. 3 Canceling of a secondary volume hiding operation started. 6 Canceling of a secondary volume hiding operation completed. 6 Canceling of a secondary volume hiding operation failed.
Description of category 112 Audit event Severity Take over operation is terminated 6 Take over operation timed out. (The command execution was successful, but completion could not be confirmed.) 4 Take back operation has started. 6 Take back operation is terminated. 6 Take back operation timed out. (The command execution was successful, but completion could not be confirmed.) 4 Swap operation has started. 6 KAVN10055-I Swap operation is terminated.
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 XP7 Replication Manager 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 hcmds64dbclustersetup command at the same time.
Argument Description XP7-Command-ViewAE-product-name Specifies the name of the product from which maintenance information will be collected. If this option is omitted, information is collected from all XP7 Command View AE 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 62 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 File Server, Database Server, and Backup Server The volume is mounted or unmounted. Error VDS Basic Provider 1 Unexpected Failure. Error code: 2@01010013 Backup server A VSS backup is executed. Error VDS Basic Provider 1 Unexpected Failure. Error code: 1@01010013 Backup server A VSS backup is executed. Error Virtual Disk Service 1 Unexpected Failure.
Server on which event occurred When message is output to event log Type Source Event ID Message Passive node in a CCR env. and the SCR env. target A VSS backup is executed. Error ESE 522 Microsoft.Exchange.Cluster.ReplayService (xxxx) Log Verifier exx xxx: An attempt to open the device name "xxx" containing "xxx" failed with system error 5 (0x00000005): "Access is denied. ". The operation will fail with error -1032 (0xfffffbf8). SCR env. target A VSS backup is executed.
Server on which event occurred When message is output to event log Type Source Event ID Message Backup server A VSS backup is executed. Error DLM Manager 32790 KAPL08022-E A path error occurred. ErrorCode = xxxxxxxx PathID = xx PathName = xx DNum = xx HDevName = xx Backup server A VSS backup is executed. Error DLM Manager 32794 KAPL08026-E An error occurred on all the paths of the LU.
2. If other XP7 Command View AE products are running, you must stop the associated services (HBase 64 Storage Mgmt Web Service and HBase 64 Storage Mgmt Common Service) as described in “Stopping Replication Manager ” on page 88. 3.
2. From the Start menu, choose Settings, Control Panel, Administrative Tools, and then Cluster Administrator.
2.
4. Move the database onto the shared disk and follow all procedure as described in “Using the hcmds64dbclustersetup command” on page 128. NOTE: This step is unnecessary if other XP7 Command View AE products have been set up in a cluster configuration. Don't separate the shared disk from the active node until the hcmds64dbclustersetup 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 hcmds64dbclustersetup command If there are no XP7 Command View AE products in a cluster configuration on the same host, execute the command shown below.
NOTE: Do not execute the hcmds64dbclustersetup command more than once at the same time. Also, do not execute this command and the cvxpaegetlogs command at the same time.
NOTE: When using Device Manager Agent on VMware 4.x, it is necessary to confirm the prerequisite combination of Device manager server and Device Manager Agent.
3. If the agent is not correctly linked to the server, enter the following information in response to the command request: IP address or host name Specify the IP address or host name of the Device Manager server. • Specifying an IP address: In IPv4, specify the address in dotted-quad form. In IPv6, specify the address by using hexadecimal numbers delimited by colons. Abbreviated forms can also be used. • Specifying a host name: Specify the host name by using a string of up to 50 bytes.
Recognition of Device Manager Agent Check the items below to make sure that Device Manager server correctly recognizes Device Manager Agent on a host or pair management server that manages existing copy pairs: • Hosts or pair management servers that manage copy pairs are displayed in the host list. • A button to refresh host information is displayed in the host properties window.
• The configuration definition file for RAID Manager that exists on the pair management server • Copy groups that are defined in the RAID Manager configuration definition file • Copy pairs that configure copy groups. If the above items are not displayed correctly, refresh the configuration information for Device Manager server. For details, see the HP XP7 Replication Manager User Guide.
Restoring a replica with roll-forward fails with error message RPM-11510 When restoring a replica with the roll-forward option, if the storage group to recover has more than 1,008 transaction log files, the restore and roll-forward will complete, but the information store will not be mounted and the message RPM-11510 is output. Follow this procedure to complete the mount operation: 1. Start the event viewer for the operating system on the database server. 2.
Disk status remains online after replica operation is complete In Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 environments, the disk status of secondary volumes on the backup server change to Offline after a backup operation is performed. However, note that if the operation fails, the status of the secondary volumes on the backup server might remain Online.
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 64 to refer to HP XP7 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 • XP7 Continuous Access Synchronous 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 D
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • LUN Configuration and Security Manager XP (Virtual LVI) Open Volume Management • Open Volume Management • Security Manager XP • XP Data Shredder • XP Virtual LVI/LUN (VLL) This abbreviation is used when it is not necessary to distinguish the following products: • RAID Manager RAID Manager • RAID Manager XP • XP RAID Manager • XP7 RAID Manager This abbreviation is used when
A Version compatibility with other Command View AE products This appendix describes the compatibility between versions of Replication Manager and other Command View AE 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. The following functions are not supported on open systems: Device Manager Server or Device Manager Agent 7.4.1 or earlier • Editing the group name using the Pair Configuration Wizard • Specifying syncwait option using the Change Pair Status Wizard The following functions are not supported: Device Manager Server or Device Manager Agent 7.
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 XP7 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 and XP7 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 User customized view 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
Support for each storage system Upper row: open system Lower row: mainframe system Task License utilization monitoring and over-threshold notification XP512 / XP48 XP1024 / XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 and XP7 N N Y Y Y N N Y Y Y 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
Support for each storage system Upper row: open system Lower row: mainframe system Task Usage monitoring and overthreshold notification XP512 / XP48 XP1024 / XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 and XP7 N N N N N 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 N N ? ? N
Support for each storage system Upper row: open system Lower row: mainframe system Task Changing copy pair statuses (resynchronizing, splitting, and restoring)1 Batch recovering from site failures Changing statuses of copy pairs in copy groups defined by device groups XP512 / XP48 XP1024 / XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 and XP7 Y Y Y Y Y N N Y4 Y4 Y4 N N Y5,6 Y5,6 Y6,7 N N N N N ? ? ? ? Y ? ? ? ? n/a Legend: Y : Supported N : Not supported n/a: Not
Unsupported configuration Requirement for configuration Alternative configuration to implement requirement A copy group defined in HORCM files with a single copy group definition that includes virtual command device settings. To modify all the pairs in the copy group at once. Each pair modification must be executed separately. The number of pairs in the child group of a cascade configuration is greater than the number of pairs in the parent group. To create a backup of only some volumes. None.
Unsupported configuration Requirement for configuration Alternative configuration to implement requirement None None The following virtual storage machine-related configurations are unsupported: Local copy • A copy pair comprising volumes from different virtual storage machines. • A copy pair comprising virtual storage machine volumes and physical storage system volumes. • A copy group comprising multiple copy pairs from different virtual storage machines.
Unsupported configuration The number of pairs at the cascade source and cascade destination is different. Requirement for configuration Alternative configuration to implement requirement To create a backup of only some volumes. None To set up a BC multi-target configuration. Use different copy groups for each S-VOL if there are copy pairs using the same P-VOL in the copy group. None None The number of pairs in multi-target configurations is different. Pairs in the copy group use the same P-VOL.
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 153. 2. Follow the instructions in “Adding a storage system” on page 154.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 67 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 userid User ID for accessing the storage system arraypasswd* User password for accessing the storage system Legend: * : For XP512/XP48, specify searchcommunity (the SNMP community name of the storage system) instead of userid and arraypasswd. The default is public. Command execution example Using the information obtained by the GetServerInfo command, specify the value XP1024/128 for both family and displayfamily for the new storage system to be added.
Command format AddHost hostname=host-name wwnlist=wwn-list {ipaddress=IP-address|ipv6address=IP-address} Table 69 AddStorageArray command parameters Parameter name Description hostname Specifies the host name to be added. wwnlist Use periods (.) as delimiters. ipaddress|ipv6address Specifies the IP address of the host to be added. If you use an IPv4 address, specify the address for the parameter ipaddress. If you use an IPv6 address, specify the address for the parameter ipv6address.
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 the Device Manager CLI, read “Preparing to use Device Manager CLI” on page 153 and perform the 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 rm-vm-r has been registered. RESPONSE: An instance of Host objectID=HOST.8 name=rm-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 rm-vm-r, execute the following command: hdvmcli AddHostRefresh hostname=rm-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 70 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.
RESPONSE: An instance of Host objectID=HOST.8 name=rm-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.
: splitTime=-1 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 MSCS Microsoft Cluster Service 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
TLS Transport Layer Security UAC User Account Control URL Uniform Resource Locator VCS Veritas Cluster Server WSFC Windows Server Failover Clustering Configuration Guide 167
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).
consistency group An attribute to maintain integrity of data between copy pairs. As a general guideline, the attribute is assigned for each copy group or snapshot group. The attribute is mandatory for asynchronous remote copy, but is not mandatory for local copy. Consistency groups are used in Continuous Access or Continuous Access Journal to maintain integrity of the update order for volumes. Continuous Access Software that duplicates volumes between storage systems.
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. Device Manager Software that enables integrated management of resources and the hardware configuration of storage systems.
pair In this manual, pair means copy pair. pair status Indicates the current status of the copy pair. Replication Manager uses six status values: error, suspend, copying, sync, simplex, and unknown. A pair status is also called copy pair status. paired volume Denotes a primary and secondary volume pair linked by a volume replication functionality of a storage system. Also called a copy pair. In this manual, copy pair is sometimes written simply as pair.
S-VOL (secondary volume) The copy destination volume of two volumes that are associated in a copy pair by a storage system volume replication functionality. Snapshot Software used to duplicate volumes in a single storage system. Snapshot duplicates differential data in a data pool. The secondary volume is a virtual volume that consists of the primary volume and the differential data.
Glossary
Index A Administrator privileges (UAC), agent.logger.properties, 85 agentif.properties file, 97 Application Agent and 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, 70 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, 22, 24, 46 bcmif.
infrastructure mainframe, 53 open systems, 51 inqraid $Phys -CLI command, 135 L LDEV maximum number, 36 link menu, 55 log file log amount of data, 95 logger.
troubleshooting, 113 maintenance information, 114 resolving errors, 113 RPM-00824, 123 U UAC, 87 unsupported configurations, 148, 150 V virtual ID, 25 virtual storage machine, 25 VMware ESX/ESXi support, 74 VSS Provider log files, 118 requirements, 70 W web sites HP, 137 X XP7 Command View AE Common Component, 19, 23 XP7 mainframe agent, 24 Configuration Guide 177
