HP P9000 Replication Manager Software Configuration Guide Part number: TB584-96091 Seventeenth edition: January 2014
Legal and notice information © Copyright 2010, 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.
Date Version Edition Description October 2013 7.6-00 Sixteenth Added information for new and changed features. January 2014 7.6.1-00 Seventeenth Added information for new and changed features.
Contents Preface .............................................................................................. 13 1 Replication Manager system configurations and requirements ................ 15 Replication Manager system configurations .................................................................................. Configurations for open systems ........................................................................................... Configurations for mainframe systems ..............................
Adding a link menu to the GUI display ....................................................................................... 58 hcmdslink command options ................................................................................................ 58 Creating a user-defined application file ................................................................................. 59 3 Setting up Application Agent ............................................................. 61 About Application Agent ..........
bcmif.properties ............................................................................................................... agentif.properties ............................................................................................................. appagentif.properties ....................................................................................................... base.properties ................................................................................................................
7 Support and other resources ............................................................ 143 Contacting HP ........................................................................................................................ HP technical support ......................................................................................................... Subscription service .......................................................................................................... Documentation feedback ....
Figures 1 Single site configuration in open systems .................................................................... 16 2 Two-site configuration in open systems ....................................................................... 17 3 Three-site configuration in open systems ..................................................................... 18 4 Redundant pair management server configuration in open systems ................................
Tables 1 System components (for open systems) ....................................................................... 19 2 Overview of mandatory software (for open systems) .................................................... 21 3 System components (for mainframe systems) ............................................................... 24 4 Overview of mandatory software for mainframe management ...................................... 25 5 System components (for replica management) ...........................
29 Server hardware requirements .................................................................................. 63 30 Supported database and backup server combinations (Microsoft Exchange Server) ......... 63 31 Supported database and backup server combinations (Microsoft SQL Server) ................. 64 32 Supported database and backup server OS combinations (when using a file system and VSS) ................................................................................................................
64 Restrictions when Replication Manager and Device Manager versions differ ................. 147 65 Restrictions when Replication Manager and HP StorageWorks P9000 for Business Continuity Manager Software versions differ ............................................................ 148 66 Items required to execute Device Manager CLI .......................................................... 158 67 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 16 Replication Manager system configurations and requirements
Figure 2 Two-site configuration in open systems Configuration Guide 17
Figure 3 Three-site configuration in open systems 18 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 23
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.
Prerequisites for managing copy pairs using snapshot groups If a volume is an HP P9500, Replication Manager can manage copy pairs using snapshot groups. However, the following functions are not available: • Setting alert (pool usage monitoring function for Thin Image is available) • Managing My Copy Groups • Managing replicas The prerequisites for managing copy pairs using snapshot groups are as follows: • Authentication mode of the command device is enabled.
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 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.
Windows operating system Prerequisite programs 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.
Linux operating system Prerequisite programs Red Hat Enterprise Linux 6.1 (64-bit) • Supports IPv4 and IPv6 connections • Required RPM packages: kernel-2.6.32-220.4.2.el6.x86_64.rpm or later kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm or later Red Hat Enterprise Linux 6.2 (32-bit) • Supports IPv4 and IPv6 connections • Required RPM packages: kernel-2.6.32-220.4.2.el6.i686.rpm or later kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm or later Red Hat Enterprise Linux 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 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 Windows Server 2012 no SP RedHat Enterprise Linux 6.1 (32-bit), 6.2 (32-bit) • Required RPM packages: kernel-2.6.32-220.4.2.el6.i686.rpm or later kernel-firmware-2.6.
Server specifications The following table lists the server specifications required for a management server to run Replication Manager. Table 11 Required server specifications for a management server Item Minimum requirement Recommended specification CPU clock speed 1 GHz 2 GHz or higher Memory size 3 GB 6 GB or more Disk size 750 MB 750 MB to 6.
1. Device Manager, Tiered Storage Manager, Replication Manager, and Host Data Collector are always installed at the same time. Table 13 Agent virtual memory requirements Agent Requirement Device Manager Specify the virtual memory size values using the server.agent.maxMemorySize property. (See the HP P9000 Command View Advanced Edition Suite Software Administrator Guide for more information.
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 P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide.
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 P9000 Command View Advanced Edition Suite Software 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 99.
Windows operating system Web browser Windows XP SP2 (32-bit) Internet Explorer 7.0, 8.0 Windows XP SP3 (32-bit) Internet Explorer 7.0, 8.0 Windows Vista no SP or SP1 Windows Vista SP2 Windows 7 no SP1 Windows 7 SP1 Windows 8 no SP Windows 8.1 Internet Explorer 7.0, 8.0 (only the 32 bit version is supported) Internet Explorer 7.0, 8.0, 9.0 (only the 32 bit version is supported) Internet Explorer 8.0, 9.0 (only the 32 bit version is supported) Internet Explorer 8.0, 9.0, 11.
Linux operating system Red Hat Enterprise Linux 5.5 (64-bit) Red Hat Enterprise Linux 5.6 (32-bit) Red Hat Enterprise Linux 5.6 (64-bit) Red Hat Enterprise Linux 5.7 (32-bit) Red Hat Enterprise Linux 5.7 (64-bit) Red Hat Enterprise Linux 5.8 (32-bit) Red Hat Enterprise Linux 5.8 (64-bit) Web browser Firefox 3.6.x (only the 32 bit version is supported) Firefox 3.6.x, Firefox ESR 10.0.x, Firefox ESR 17.0.x Firefox 3.6.x (only the 32 bit version is supported) Firefox 3.6.x, Firefox ESR 10.0.x, Firefox ESR 17.
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 147.
For best results, ensure that the version numbers of installed P9000 Command View AE suite 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 StorageWorks P9000 for Business Continuity Manager Software versions differ” on page 148.
In either of the above cases, Replication Manager cannot be used to edit the disk configuration definition files that were created by HP StorageWorks P9000 for Business Continuity Manager 6.6.1. Instead, you must use HP StorageWorks P9000 for Business Continuity Manager 6.7 or later to edit the disk configuration definition files and then perform volume scan or distribution with Replication Manager).
• For port numbers used by Application Agent, see “Changing Application Agent port numbers” on page 88 Table 21 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 25 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.
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/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 Windows Server 2008 SP2 Windows Server 2008 SP2 (64-bit) Windows Server 2008 R2 no SP Exchange version 20071 no SP4, SP1, SP2, SP3 4 Windows Server 2008 SP2 (64-bit) 20101 no SP, SP1, SP2. SP3 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.
Database server OS Backup server OS SQL Server version Windows Server 2003 x64 (SP2) Windows Server 2003 x64 (SP2) 2005 (SP21, SP3, SP4) Windows Server 2003 R2 x64 (SP2) Windows Server 2003 R2 x64 (SP2) 2005 x64 (SP21, SP3, SP4) Windows Server 2008 x64 (no SP/SP1) Windows Server 2008 x64 (no SP/SP1) Windows Server 2008 x64 (SP2) Windows Server 2008 R2 (no SP) Windows Server 2008 R2 (SP1) Windows Server 2008 x64 (SP2) 2008 (no SP1, SP1, SP2, SP3) 2008 x64 (no SP1, SP1, SP2, SP3) 2008 R2 (no SP,
Database server OS Backup server OS File system type Windows Server 2008 x86 (no SP, SP1, SP2) Windows Server 2012 (no SP) Windows Server 2008 x64 (no SP, SP1, SP2) Windows Server 2008 R2 (no SP, SP1) Windows Server 2012 (no SP) 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.
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.
IPv6 support Operating system Required programs P9000 RAID Manager 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. For details, see the HP P9000 Replication Manager Application Agent CLI User Guide.
11. Operation on Minimal Server Interface is not supported. Table 36 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.
• The version of Device Manager agent is earlier than 6.4 • The version of P9000 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 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. • For a backup server: The number of backup catalogs backed up from the S-VOL to a tape.
also be installed. The ESEUTIL command does not need to be installed for any other versions of Exchange Server. The ESEUTIL command must be copied into the Application Agent installation folder. Copy the following files from Exchange-installation-directory\bin to Application-Agent-installation-directory\DRM\bin\util: • ESE.dll • ESEUTIL.exe • EXCHMEM.dll • EXOSAL.dll TIP: It is not necessary to perform this operation if you are using Exchange Server 2007 or later.
Replica operations between storage systems Application Agent is compatible with Continuous Access Synchronous and Continuous Access Journal backups to (and restorations from) remote site storage systems, for when a failure occurs on a local site storage system.
After a VSS backup, a disk containing a backup server's secondary volume is taken offline. However, if the backup fails, the disk might be put online. In such a case, follow the procedure described in “Disk status remains online after replica operation is complete” on page 141. Host Bus Adapter (HBA) Make sure that both the HBA and HBA driver support VSS. Application Agent does not support Emulex Full Port drivers. When using a VSS Provider not bundled with Application Agent Beginning with 7.
• • • • XP512/XP48 XP12000/XP10000/SVS200 XP24000/XP20000 HP9500 NOTE: If the backup or database server operating system is Windows Server 2012, Application Agent only supports the HP P9500. The volume replication functions required to use Application Agent with the storage systems are listed in the following table. NOTE: Application Agent for Exchange does not support Continuous Access Journal.
3. VERITAS Storage Foundation HA for Windows Table 40 Database server requirements for cluster environment (Exchange Server 2003, SQL Server, and file systems) Database server OS Cluster software Windows Server 2003 SP21 Windows Server 2003 SP2 IPF1, 2, 3 Microsoft Cluster Service 1, 2, 3 Windows Server 2003 SP2 (64-bit) Veritas Storage Foundation HA for Windows 5.
the database services offline. However, for a restore operation in which the cluster resources are currently online, you only need to take the databases offline that are involved in the restore operation. • You can put together a cluster configuration using only database servers. You cannot allocate one cluster server to a database server and the other cluster server to a backup server.
Notes: 1. Database servers that are configured on a guest OS are supported. Backup servers that are configured on a guest OS are supported if all of the following conditions are satisfied: • The backup target is a file system or SQL Server. • The secondary volume is a single generation. • The backup is not made with VSS.
Guest OS Application Agent product File systems Windows Server 2003 SP2 (32-bit and 64-bit) Windows Server 2003 R2 SP2 (32-bit and 64bit) Windows Server 2008 (32-bit) Windows Server 2008 (64-bit) Windows Server 2008 R2 (64-bit) Windows Server 2012 (64-bit) Y Y Y Y Y Y Notes: 1. 2. 3. 4. 5. 6. 7. See “Hyper-V Live Migration” on page 81 for additional information. SQL Server cluster configurations are supported on the guest OS if the disk being used is directly connected using iSCSI.
NOTE: The following restrictions apply: • SQL Server cluster configurations are not supported on guest operating systems, except for a limited subset of configurations between guest operating systems, which are supported only in Replication Manager version 7.1 and later. However, note that in these configurations, you must use disks that are directly connected to iSCSI, and the SQL version must be one of the following: SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012.
Application Agent installation path restrictions Make sure the paths used in the installation of Application Agent meet the following requirements: • For the download destination path, the installation path for Application Agent, and the path specified in the environment variable %TMP%, do not use a directory name that starts or ends with one or more spaces.
Before starting the installation, stop all running programs. For example, Exchange Server 2013 includes services such as the Microsoft Exchange Health Manager service. You must stop all services associated with Microsoft Exchange Server or SQL Server prior to installing Application Agent.
10. After selecting a destination, you are prompted to select the components to install or uninstall using Select Features. The choices are Component for SQL and Component for Exchange. NOTE: When installing on Windows Server 2008 (32-bit) and Windows Server 2012, the option to install the Component for Exchange may not be displayed. If you plan to perform VSS backups, you must select to install the Component for SQL instead and then install the Shadow Copy Provider manually.
Adding Application Agent to the Windows Firewall Exception list NOTE: This procedure is not required unless: • You selected not to add the exceptions when prompted during the Application Agent installation (or the process of adding the exceptions failed). • You enabled the firewall after installing Application Agent. • You migrated Protection Manager to Application Agent. The Application Agent service services are as follows: • Copy Controller • Common Agent To configure these services as exceptions: 1.
Using P9000 RAID Manager to configure pair volumes Within a copy group, only include the pair volumes for one application. If the pair volumes of multiple applications are mixed together in one copy group, unintended backups and restorations might occur. Device Manager and P9000 RAID Manager For P9000 RAID Manager to be started on the database and/or backup servers automatically, Device Manager Agent needs to be installed on both servers.
3. Use the Cluster Administrator wizard to add the new resource to the cluster resource group with the name virtual-server-name (such as a cluster resource group for Exchange Server). Resource type: Generic script Script file path: Path name of the created VBScript file If the VBScript file is stored on a shared disk for nodes, be sure and register this shared disk as a physical disk resource in the Resource dependencies field in the Dependencies dialog box.
Application Agent and Replication Manager log output The number of Application Agent instances in your storage configuration must be considered when configuring the amount of log output, as described in “About Replication Manager log output” on page 102. If the number of target Application Agent instances exceeds 30, you need to tune the file capacity and number of files as follows: Trace log size = current-file-capacity + 2.
• The port numbers set in the server.properties file must be unique and cannot be shared by any other processes. • If you change the value of server.agent.port, you must also change the port number for Application Agents registered as information sources. • After changing these values, the Common Agent Service must be restarted.
The following tables list the available properties, the types of information logged, and the parameters that are stored when values are logged. Table 45 List of properties in the agent.logger.properties file Property Description The output level of the Replication Manager log file. Messages matching the type are output to the log file. Specifiable values: One of the three following scenarios: DEBUG and INFO, WARN, or ERROR and FATAL. agent.logger.
Values Logged INFO DEBUG WARN WARN X X ERROR X X X FATAL X X X ERROR FATAL X Configuration Guide 91
Setting up Application Agent
4 Operating the management server This chapter describes the Replication Manager settings and operating procedures, including how to start and stop Replication Manager and how to back up and restore the databases. About executing commands on the management server This section includes information related to the execution of commands that are required for Replication Manager operation.
NOTE: Device Manager must be running for Replication Manager to operate properly. 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 XP, Windows Server 2003, Windows Vista, Windows 7 or Windows Server 2008: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite >Start Command View AE Suite.
In Windows XP, Windows Server 2003, Windows Vista, Windows 7 or Windows Server 2008: Select Start > All Programs > HP StorageWorks P9000 Command View AE >Manage Services > Stop - CVXPAE. In Windows Server 2012: Select All Apps from the Start menu, then select HP P9000 Command View Advanced Edition Suite > Stop - Command View AE Suite. b. Using the command line: Common-Component-installation-folder\bin\hcmdssrv /stop In Linux 1. 2. Log in as root user.
KAPM05007-I Already started service. service-name=HBase Storage Mgmt Common Service Example 2: Execution results if Replication Manager has stopped KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service If you execute the command as described above, you can also check whether the HiRDB service is running.
Replication-Manager-server-installation-folder\conf In Linux: Replication-Manager-server-installation-directory/conf The RpMCLI.properties file is located in the RpMCLI folder/directory (not conf). The following table lists the properties and default values for each file. 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.
File serverstorageif.properties Property Default value (unit) logger.AppStatus.MaxFileSize 20 (MB) logger.AppStatus.enabled true ssif.socketTimeout 3600 (seconds) ssif.socketConnectTimeout 5 (seconds) 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.
File RpMCLI.properties Property Default value (unit) base.taskschedule.threadmax 10 base.refreshstorage.polling.timeout 60 minutes RpMCLI.diaglevel INFO RpMTaskCLI.MaxBackupIndex 6 (files) 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.
Property Description logger.MaxBackupIndex The maximum number of log files created in Replication Manager. When the number of log files reaches this value, the existing files are reused, starting with the oldest file. Specifiable values: 1 to 16 (files) Default value: 6 logger.MaxFileSize The maximum size of a single Replication Manager log file. Default value: 20MB Threshold value for output of a database-related log file. logger.DB.
Property Description Enabling or disabling of the pair status update logging function. logger.RefreshStatus.enabled Specifiable values: true or false Default value: true Maximum number of backup files for a pair status update log file. logger.RefreshStatus.MaxBackupIndex Specifiable values: 1 to 32 (files) Default value: 2 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.
About Replication Manager log output The amount of information output to the Replication Manager log files depends on the memory heap size of the system. Therefore, you must change the values of the xxxx.MaxBackupIndex and xxxx.MaxFileSize parameters in the logger.properties file to appropriate values for the memory heap size. The following table shows the recommended amount of log data to be retained. NOTE: The default values in the logger.
Property Description The amount of time Replication Manager waits to issue an alert message query to Device Manager server. Specifiable values: 1 to 3600 (seconds) ssif.alertTimeout Default value: 1800 Note: When you change this value, do not specify a value greater than the value specified for ssif.socketTimeout (except zero). If you specify a greater value, alerts might not be received immediately. bcmif.properties The bcmif.
agentif.properties The agentif.properties file is used to specify the values of properties necessary for the interface between Replication Manager and a Device Manager Agent. Normally, you do not need to change these values. To change the values, you need expert knowledge of Device Manager Agent. The following table describes the available properties and settings. Table 53 List of properties in the agentif.properties File Property Description agentif.
appagentif.properties The appagentif.properties file is used to specify the values of properties necessary for the interface between Replication Manager and Application Agent. Normally, you do not need to change these values. To change the values, you need expert knowledge of Application Agent. The following table describes the available properties and settings. Table 54 List of properties in the appagentif.properties File Property Description appagentif.
Property base.taskscheck.mf.interval Description The interval at which Replication Manager checks whether a task related to a mainframe copy pair operation has finished. Specifiable values: 30 to 3600 (seconds) Default value: 120 base.taskscheck.mf.maxcount 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.
Property Description This property specifies whether the RMI registry is started. You must specify this property if you use the Replication Manager CLI. base.rmi.enabled Specifiable values: true or false Default value: false 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.
Property Description RpMTaskCLI.MaxBackupIndex This property specifies the maximum number of trace log files (RpMTaskCLIn.log), which are created when the GetTasks or ExecuteTask command is executed. If a new log file is required when the number of log files has been reached this value, the oldest log file is overwritten. Values that can be specified: 1-16 (files) Default value: 6 RpMTaskCLI.
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 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 P9000 Command
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.
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 window for editing) the information source, and specify the port number for HTTPS communications. For more information on how to add or edit the information source, see the online Help.
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 118 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 123.
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 129. 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 123 Resolving Application Agent operation errors, page 125 Collecting support information with the hrpmap_getras command, page 125 Application Agent events that can be ignored, page 126 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 61 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.
3. Execute the following command to re-create a database system on the disk: In Windows: Common-Component-installation-folder\bin\hcmdsdbremake /databasepath new-database-recreation-destination-folder In Linux: Common-Component-installation-directory/bin/hcmdsdbremake -databasepath new-database-recreation-destination-directory NOTE: Observe the following restrictions for folders/directories: • Specify an absolute path for database-recreation-destination-folder of no more than 63 bytes.
Procedure on the executing node 1. On the executing node, make sure that the HP StorageWorks P9000 Command View AE Common Component service is online, and that the executing node currently owns the service and shared disk. 2. From the Start menu, choose Settings, Control Panel, Administrative Tools, and then Cluster Administrator.
2.
4. Move the database onto the shared disk and follow all procedure as described in “Using the hcmdsdbclustersetup command” on page 134. 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.
NOTE: Do not execute the hcmdsdbclustersetup command more than once at the same time. Also, do not execute this command and the cvxpaegetlogs command at the same time.
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 P9000 RAID Manager that exists on the pair management server • Copy groups that are defined in the P9000 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 P9000 Replication Manager Software 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.
Creating a replica fails with error message RPM-10006 If different logical volumes are mounted at mount points in a hierarchical relationship, such as M:\ and M:\MNT, any mount points that hold a lower-level directory mount point (in this case, M:\) cannot be specified for backup. If specified, the backup will fail, and an error message (RPM-10006 and RPM-20062) will be output.
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 63 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. 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 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.
Unsupported configurations (mainframe systems) The following are a list of unsupported mainframe pair configurations. The Pair Configuration Wizard cannot be initiated to perform operations to modify these configurations. The copy group definition file should be edited directly because it is impossible to recover from these configurations using Replication Manager. Unsupported configuration The number of pairs at the cascade source and cascade destination is different.
C Environment settings when using the Core CLI License In the procedure described in “Configurations for open systems” on page 15, 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 157. 2. Follow the instructions in “Adding a storage system” on page 158.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 66 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 68 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 157 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 69 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 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 171
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 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.
DAD (Device Address Domain) A DAD is a group of volumes that is managed by HP StorageWorks P9000 for Business Continuity Manager Software. Volumes are registered in a DAD during a volume scan (discovery) by HP StorageWorks P9000 for Business Continuity 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.
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. RMI Remote Method Invocation. 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, 89 agentif.properties file, 104 Application Agent and P9000 RAID Manager, 85 cluster configuration, 75, 76, 86 described, 61 error log options, 89 installing, 82 log files, 88, 124 maximum number, 74 port numbers, 88 reinstalling, 74 requirements, 62, 75 service, 89 troubleshooting, 123 audit event, 115 audit log event categories, 115 B base.properties file, 105 base.repositry.synchronize.polling, 105 BCM Agent, 25, 26, 52 bcmif.
I information source, 175 infrastructure mainframe, 56 open systems, 54 inqraid $Phys -CLI command, 141 L LDEV maximum number, 41 link menu, 58 log file log amount of data, 102 logger.
T technical support HP, 143 troubleshooting, 119 maintenance information, 120 resolving errors, 119 RPM-00824, 129 U UAC, 93 unsupported configurations, 155, 156 V VMware ESX/ESXi support, 78 VSS Provider log files, 124 requirements, 74 W web sites HP, 143 Configuration Guide 181
