HP P9000 Replication Manager Software Configuration Guide Part number: TB584-96052 Twelfth edition: October 2012
Legal and notice information © Copyright 2010, 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface .............................................................................................. 11 1 Replication Manager system configurations and requirements ................ 13 Replication Manager system configurations .................................................................................. Configurations for open systems ........................................................................................... Configurations for mainframe systems ..............................
3 Setting up Application Agent ............................................................. 55 About Application Agent ........................................................................................................... Application Agent functions ................................................................................................. System requirements and supported environments .........................................................................
Security management ....................................................................... 97 Network communications security ............................................................................................... 97 Securing communications between HP StorageWorks P9000 Command View Advanced Edition Suite Common Component and Web browsers ...................................................................... 98 Securing communications between Replication Manager and the Device Manager server ....
Related information ................................................................................................................. 131 Conventions ........................................................................................................................... 132 A Version compatibility with other Command View AE Suite products ...... 135 Restrictions when Replication Manager and Device Manager versions differ ...................................
Figures 1 Single site configuration in open systems .................................................................... 14 2 Two-site configuration in open systems ....................................................................... 15 3 Three-site configuration in open systems ..................................................................... 16 4 Redundant pair management server configuration in open systems ................................
Tables 1 System components (for open systems) ....................................................................... 17 2 Overview of mandatory software (for open systems) .................................................... 19 3 System components (for mainframe systems) ............................................................... 22 4 Overview of mandatory software for mainframe management ...................................... 23 5 System components (for replica management) ...........................
29 Supported database and backup server OS combinations (when using a file system but not VSS) ................................................................................................................ 60 30 Database and backup server requirements (file systems) ............................................... 60 31 Database and backup server requirements (Microsoft SQL Server) ................................. 62 32 Database and backup server requirements (Microsoft Exchange Server) ..................
63 AddStorageArray command parameters .................................................................. 147 64 AddStorageArray command parameters .................................................................. 149 65 Settings to be checked by the GetHost command ......................................................
Preface This document describes the installation and configuration process for HP StorageWorks P9000 Replication Manager.
Preface
1 Replication Manager system configurations and requirements This chapter describes the system configurations, system components, and system requirements of Replication Manager. To help you understand systems that use Replication Manager, this chapter also describes the flow of control and data between programs. Replication Manager system configurations This section describes the basic system configurations for Replication Manager.
Figure 1 Single site configuration in open systems 14 Replication Manager system configurations and requirements
Figure 2 Two-site configuration in open systems Configuration Guide 15
Figure 3 Three-site configuration in open systems 16 Replication Manager system configurations and requirements
Figure 4 Redundant pair management server configuration in open systems For more information on redundant configurations, see the HP P9000 Replication Manager Software User Guide. The following tables list and describe system components for each type of system and provide an overview of the software components.
System components Software included in system components Description A management server provides management information in response to requests from management clients. Replication Manager and Device Manager server (a prerequisite program of Replication Manager) are installed on the management server. If multiple sites are used, a management server is required for each site. Replication Manager and Device Manager server are installed on the management server at the local site.
System components Software included in system components Description Normally, a host is a computer on which application programs are installed. Device Manager Agent is also installed on a host. A host uses storage systems as external storage systems. Host Device Manager Agent Installing Device Manager Agent is optional. If you install Device Manager Agent on a host, you can view information about that host (such as IP address and mount points) from Replication Manager.
Software Description Software that controls volume replication functions (such as Continuous Access or Business Copy), by issuing commands from a host to storage systems. P9000 RAID Manager Replication Manager uses the P9000 RAID Manager configuration definition file to change a copy pair configuration and acquire configuration information. For details, see the manual for the corresponding version of P9000 RAID Manager.
Figure 5 Mainframe configuration using HP StorageWorks P9000 for Business Continuity Manager (BCM) Configuration Guide 21
Figure 6 Mainframe configuration using Device Manager server only or P9000 mainframe agent The following tables list and describe system components for each type of system and provide an overview of the software components. Table 3 System components (for mainframe systems) System components Management client Management server Software included in system components Description Web browser A management client is a computer on which users use a Web browser to run the GUI for Replication Manager.
System components Software included in system components Description Usually, a host is the computer on which the application programs are installed. HP StorageWorks P9000 for Business Continuity Manager or P9000 mainframe agent is installed on a host. Note: If Device Manager server is not registered as an information source, or P9000 mainframe agent is being used, the information displayed by the GUI is limited. For details, see the HP P9000 Replication Manager Software User Guide.
Software Description Used to achieve integrated management of disk resources and for configuring storage system hardware. You can run and manage a system consisting of multiple storage systems. Device Manager server An instance of Device Manager server running on the same management server as Replication Manager is called an instance of "local Device Manager".
• If you are replacing an instance of P9000 mainframe agent with HP StorageWorks P9000 for Business Continuity Manager, HP recommends removing P9000 mainframe agent first. Configurations for mainframe monitoring As of release 6.3, Replication Manager supports monitoring of IBM environments (z/OS, z/VM, z/VSE and z/Linux) and non-IBM environments using only Device Manager (without HP StorageWorks P9000 for Business Continuity Manager or P9000 mainframe agent installed).
Figure 7 Example system configuration managing copy pairs and application replicas (Exchange) NOTE: Only Cnt Ac-S is supported for creating a remote copy.
Figure 8 Example system configuration managing copy pairs and application replicas (SQL Server) NOTE: Depending on the configuration, backup servers are not required for SQL Server configurations. The following tables describe the system components that are unique to replica management and the host configurations that are counterparts to pair management components.
System components Software included in system components Description Backup server Application Agent A host where the secondary volumes are located. Application Agent is also installed on the backup server. Table 6 Overview of mandatory software (for replica management) Software Description Application Agent Allows Replication Manager to perform database backup and restore operations.
Figure 9 Standby Replication Manager (multi-platform, multi-site configuration) System requirements This section describes the system requirements for management servers, management clients, pair management servers, hosts, and storage systems that make up a Replication Manager system. Each computer must be connected to a TCP/IP network and a static IP address is required for the management server.
NOTE: When using IPv6, both IPv4 and IPv6 must be enabled on the management server. You can use IPv6 addresses only if they are global addresses. Table 7 Windows OS and programs for a management server Windows operating system Prerequisite programs Windows Server 2003 R2 SP2 • Runs as a guest OS of Windows Server 2008 Hyper-V and V2 • Supports IPv4 and IPv6 connections • Also runs under VMware ESX/ESXi Server 4.x, and VMware ESXi Server 5.x.
Prerequisite programs Windows operating system Windows Server 2008 SP2 • Supports IPv4 and IPv6 connections • Also runs as a guest OS of Windows Server 2008 Hyper-V and V2 • Also runs under VMware ESX/ESXi Server 4.x, and VMware ESXi Server 5.x. To execute the Hitachi Replication Manager Software on the virtual server, configure the virtual server using the recommended configuration aswritten in the manual.
WARNING! Do not use a Managed Service Account if Windows Server 2008 R2 is the OS on the pair management server, database server, or backup server.
The following table lists the server specifications required for a cluster environment. Table 9 Requirements for a cluster environment Operating system Windows1, 2 Cluster software • Microsoft Windows Server 2003 R2, Enterprise Edition SP2 Microsoft Cluster Service • Microsoft Windows Server 2008 R2 Microsoft Cluster Service • Microsoft Windows Server 2008 Enterprise Edition Microsoft Failover Cluster Notes: 1. There is no cluster support on Windows XP. 2.
For details on the latest virtual memory requirements, see the documentation for each product.
logger.MaxBackupIndex * logger.MaxFileSize For details about the logger.properties file, see “logger.properties” on page 88. NOTE: The configuration must always be refreshed when Replication Monitor is upgraded from v5.x to v7.x Resource Limits The maximum number of resources that can be managed by Replication Manager depends on the memory heap size (Small, Medium, or Large). Set an appropriate memory heap size, depending on the maximum number for each resource.
NOTE: In consideration of response time and memory usage, the maximum number of both open and mainframe pairs that can be operated on by the Pair Configuration Wizard at one time is 1,000. In the case of a mainframe system, when operating a copy group or consistency group that includes 25,000 or more copy pairs, specify Medium or Large for the memory size.
Number of LDEVs by memory heap size Environment Small Medium The LDEV information acquisition source is a local Device Manager on the open system Combined open and maniframe The LDEV information acquisition source is a remote Device Manager on the open system Large 1,000,000 80,0001 120,0001 For the mainframe system 153,000 200,000 Note: 1.
Operating system Linux Windows Server 2008 no SP or SP1 (64bit)* Internet Explorer 7.0, 8.0 Windows Server 2008 R2 no SP or SP1 (64bit) Internet Explorer 8.0, 9.0 Windows Server 2008 SP2 (64-bit)* Internet Explorer 7.0, 8.0, 9.0 Windows Server 2008* R2 no SP or SP1 Internet Explorer 8.0, 9.0 Windows XP SP2 (32-bit) Internet Explorer 7.0 Windows XP SP3 (32-bit) Internet Explorer 7.0 Windows Vista* no SP Internet Explorer 7.0, 8.0 Windows Vista* SP1 or SP2 Internet Explorer 7.0, 8.
NOTE: Replication Manager supports Mozilla provided by Hewlett-Packard Development Company, L.P. Required memory for management clients The minimum required memory size for a management client for all operating systems is at least 512 MB. 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.
P9000 RAID Manager version and consistency group support To create remote pairs with the CTG option, P9000 RAID Manager 01.21.03 or later must be installed on the pair management server. If an earlier version is installed, pairs can be created successfully, but they are not members of a CT group (because the CTG option is ignored). Functional limitations when software versions do not match The version numbers of P9000 Command View AE suite products are synchronized to ensure feature compatibility.
NOTE: When attempting to delete copy pairs from a Cnt Ac-J x Cnt Ac-J configuration for a mainframe system, switch the status of all the copy pairs in the concatenated copy groups of the two instances to Suspend, and then delete the copy pairs. Restrictions on using HP StorageWorks P9000 for Business Continuity Manager Software 6.6.1 The following operations are not supported if you are using HP StorageWorks P9000 for Business Continuity Manager 6.6.
Firewall exceptions If a firewall is present, the port number for transmissions to and from Replication Manager must be registered as an exception. The tables that follow describe the port numbers associated with each type of configuration: • • • • • Table Table Table Table Table 18 19 20 21 22 The number of each port can be changed.
Port number Originator Replication Manager management server 2443/tcp Destination Description Remote Device Manager management server This port is used to communicate with Device Manager Server via SSL. It represents the value of the server.https.port property in the server.properties file for Device Manager Server. This port is required for SSL connections.
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 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 20101 no SP, SP1, or SP2 NOTE: The same Service Pack should be applied on both the database and backup server operating systems. Notes: 1. 2. 3. 4. The Exchange Management Tool is required on the database server and backup server. For details, see the section Exchange Management Tool.
2. Application Agent supports Microsoft SQL Server, but does not support new Microsoft SQL Server 2012 functionality or configurations that include the following: • AlwaysOn Availability Groups • Server Core support • (Application Agent CLI only) AlwaysOn SQL server All existing limitations for SQL Server 2008 also apply to SQL Server 2012. 3. 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.
Operating system IPv6 support Windows Server 2003 R2 SP25, 6, 7 Y Windows Server 2003 R2 SP2 (64-bit)5, 6 , 7, 9 Y Windows Server 2008 no SP or SP15, 7, 8 Y Windows Server 2008 SP25, 7, 8 Y Windows Server 2008 IPF no SP or SP18, 9, 10 Y Windows Server 2008 IPF SP28, 9, 10 Y Windows Server 2008 no SP or SP1 (64-bit)5, 7, 8, 9 Y 5, 7, 8, 9 Required programs P9000 RAID Manager Windows Server 2008 SP2 (64-bit) Y Windows Server 2008 R2 no SP8 Y2 Windows Server 2008 R2 IPF no SP1, 5, 7 Y
10. Dynamic disks are not supported.
5. 6. 7. 8. The Server Core feature is not supported. Provided as a guest OS of virtual server product VMware ESX/ESXi Server 4.x and 5 are also supported. However, VMware FT is not supported. To execute Application Agent on the virtual server, configure the virtual server as the recommended configuration written in the manual. LDM basic structure is supported. This is supported when using the Application Agent CLI. Application Agent does not support the Veritas Dynamic Multiple Pathing function.
• 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.
Account for Application Agent Services Before installing Application Agent, you must create an account that will be used to execute the Application Agent Services (a collective term for the Copy Controller service and the Common Agent Service). The account must satisfy the following conditions: • It must have OS administrator permissions. • In Security Policy, Logon as a service must be enabled and Deny logon as a service must be disabled.
Application Agent versions on database and backup servers The same version of Application Agent must be installed on database and backup server pairs. Do not, for example, install version 6.3 on the database server and 6.4 on the corresponding backup server. Remote copy type support Microsoft Exchange Server uses VSS to create replicas. Because VSS only supports Cnt Ac-S for remote copies, Replication Manager must use Cnt Ac-S to create remote replicas.
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. When reinstalling Application Agent When Application Agent is uninstalled, configuration files might remain.
Service name Displayed name Prerequisite condition for startup DcomLaunch DCOM Server Process Launcher Automatic SamSs Security Accounts Manager Automatic winmgmt Windows Management Instrumentation Automatic EventSystem COM+ Event System Manual or Automatic MSIServer Windows Installer Manual or Automatic VSS Volume Shadow Copy Manual or Automatic COMSysApp COM+ System Application Manual or Automatic MSDTC Distributed Transaction Coordinator Manual or Automatic If you attempt to in
Cluster support Application Agent can be linked to cluster software to increase the availability of the system. The following tables summarize the cluster software configurations that can be used with Application Agent. Table 35 Database server requirements for cluster environment (Exchange Server 2007) Database server OS Cluster software Windows Server 2003 SP2 (64-bit)1 Microsoft Cluster Service 1 Windows Server 2003 R2 SP2 (64-bit) Veritas Storage Foundation HA for Windows 5.
3. 4. To perform restore when a cluster source is online, the Microsoft Cluster Service correction module (Hotfix 903650) is required. Windows Server 2003 with Service Pack 1 or Windows Server 2003 R2 is the prerequisite OS, This is supported only when using the Application Agent CLI.
• Depending on the connection method used by the guest OS, the VMware ESX support status varies.
NOTE: When using Device Manager Agent on VMware 4.x, you must confirm the prerequisite combination of Device Manager server and Device Manager Agent. Even if you confirm the combination, note the following: • If the target volume is set as a command device on the virtual machine, by using Add CMD Devices, the virtualization server needs to be restarted to recognize the command device.
SQL Server 2008 SQL Server 2008 R2 SQL Server 2012 Table 40 Windows Server 2008 Hyper-V support based on the guest OS connection method Physical connection Guest OS connection method Host OS Guest OS Supported Pass through RAID (offline) RAID Y VHD (variable/fixed) RAID Non-RAID N Pass through RAID (offline) RAID Y VHD (variable/fixed) RAID Non-RAID N Direct connection - RAID Y Fibre Channel iSCSI NOTE: The following restrictions apply: • SQL Server cluster configurations are not
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.
NOTE: When performing installation or uninstallation, the system drive must have 100 MB or more of free disk space to allow the installer to create temporary files. To install the agent, follow this procedure: 1. Log on to Windows as a member of the Administrators group on each of the database and backup servers where you plan to install Application Agent. 2. If you are installing from the integrated installer, insert the media. If you are installing from the GUI, proceed to step 4. 3.
15. The Setup Status window appears, displaying the progress of the operation. 16. The Replication Manager - Application Agent Setup window appears. Enter the User name and Password in the respective fields, for an account that has Administrator permissions and the “Log on as a service” permission and click Next. 17. You are asked if you wish to setup the Device Manager agent.
• Using P9000 RAID Manager to configure pair volumes, page 77 • Device Manager and P9000 RAID Manager, page 77 • Starting and stopping P9000 RAID Manager, page 77 Command line interface for P9000 RAID Manager Note the following precautions regarding using the P9000 RAID Manager command line interface: • Do not use the P9000 RAID Manager command line interface while carrying out replica operations from Replication Manager.
Perform the following procedure on each server that makes up the virtual server: 1. Create a VBScript file named RecoverJob.vbs in the following location: Application-Agent-installation-folder\DRM\schedule You can specify a different name and location for the VBScript file, but for maintenance reasons, HP recommends that you use the above file name and file storage location. 2. In the VBScript file, specify the recovery processing to be performed by drmjobsch.exe.
LooksAlive = 0 End Function Function IsAlive( ) IsAlive = 0 End Function Function Open( ) Open = 0 End Function Function Close( ) Close = 0 End Function Function Terminate( ) Terminate = 0 End Function Application Agent and Replication Manager log output The number of Application Agent instances in your storage configuration must be considered when configuring the amount of log output, as described in “About Replication Manager log output” on page 91.
The properties and default values are listed in the following table. Table 41 Port numbers in server.properties file Property Default value (port number) Purpose server.agent.port 24041 Port number for the Common agent daemon process (service). server.http.port 24042 Port number for the communication between the Common agent daemon process and the web server process. server.http.localPort 24043 Port number for Common agent Web server.
TIP: After installing Application Agent, if the Copy Controller service or the Common Agent Service is Disabled, change the setting to Automatic. The Common Agent Service is used by other agent programs (such as Device Manager Agent). When you stop Common Agent Service, you should determine whether or not the operation of other agents is affected. Setting error logging options for Application Agent The agent.logger.properties file is used to specify the values of log output-related properties.
Property Description The maximum size of a single Replication Manager log file. This value must be specified in bytes, kilobytes, or megabytes. If the specified value is not followed by KB or MB, the size is assumed to be in bytes. Specifiable values are determined by the specified unit as follows: agent.logger.
4 Operating the management server This chapter describes the Replication Manager settings and operating procedures, including how to start and stop Replication Manager and how to back up and restore the databases. About executing commands on the management server This section includes information related to the execution of commands that are required for Replication Manager operation.
NOTE: Device Manager must be running for Replication Manager to operate properly. Starting Replication Manager To start Replication Manager, start HP StorageWorks P9000 Command View AE Common Component as described below. In Windows: Log in as a user with Administrator permissions, and then start the services from the Start menu or the command prompt. Select Start > All Programs > HP StorageWorks P9000 Command View AE >Device Manager > Start Server with Common Services.
In Windows: Log in as a user with Administrator permissions, and then obtain the status from the Start menu or the command prompt. Select Start > All Programs > HP StorageWorks P9000 Command View AE >Device Manager > Server and Common Services Status. From the command prompt: installation-folder-for-Common-Component\bin\hcmdssrv /status In Linux: installation-folder-for-Common-Component/bin/hcmdssrv -status Example 1: Execution results if Replication Manager is running KAPM05007-I Already started service.
Properties related to Replication Manager The properties required by Replication Manager are specified in the following properties files stored on the management server: • • • • • • logger.properties, page 88 serverstorageif.properties, page 91 bcmif.properties, page 92 agentif.properties, page 93 appagentif.properties, page 94 base.
File serverstorageif.properties Property Default value (unit) logger.UserOperation.MaxFileSize 10MB logger.RefreshStatus.enabled true logger.RefreshStatus.MaxBackupIndex 2 (files) logger.RefreshStatus.MaxFileSize 10MB logger.AppConfig.MaxBackupIndex 3 (files) logger.AppConfig.MaxFileSize 10 (MB) logger.AppConfig.enabled true logger.AppStatus.MaxBackupIndex 6 (files) logger.AppStatus.MaxFileSize 20 (MB) logger.AppStatus.enabled true ssif.socketTimeout 3600 (seconds) ssif.
File Property Default value (unit) appagentif.connectTimeout 30 (seconds) appagentif.responseTimeout 3600 (seconds) base.repositry.synchronize.polling true base.taskscheck.interval 120 (seconds) base.taskscheck.maxcount 0 (times) base.taskscheck.mf.interval 120 (seconds) base.taskscheck.mf.maxcount 0 (times) base.alert.automarking true base.refreshdginfo.exec 1 base.repositry.synchronize.interval 10 (minutes) base.repositry.synchrocheck.interval 10 (minutes) appagentif.
Property Description logger.sysloglevel The threshold value for the output level of the OS event log that is output using Replication Manager. Messages containing values that are equal to or less than this value are output to the log file. Specifiable values: 0, 10, 20, and 30 (in decreasing order of importance from left to right). Default value: 0 logger.MaxBackupIndex The maximum number of log files created in Replication Manager.
Property Description Maximum number of backup files for a user operation log file. logger.UserOperation.MaxBackupIndex Specifiable values: 1 to 32 (files) Default value: 5 Maximum size of a user operation log file. logger.UserOperation.MaxFileSize Default value: 10 MB 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.
The following are the output levels of log files and the contents of output messages: 0: Critical error, high-priority information 10: Non-critical error, medium-priority information 20: Warning 30: All debug information 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.
Property ssif.socketConnectTimeout Description The amount of time Replication Manager waits to connect to Device Manager server. If 0 is specified, Replication Manager waits until a connection is established without timing out. Specifiable values: 0 to 3600 (seconds) Default value: 5 The amount of time Replication Manager waits to issue an alert message query to Device Manager server. Specifiable values: 1 to 3600 (seconds) ssif.
Property Description bcmif.ReconnectionCount The number of retries attempted when Replication Manager cannot establish a connection with HP StorageWorks P9000 for Business Continuity Manager Software or P9000 mainframe agent. If 0 is specified, the number of retries is unlimited. Specifiable values: 0 to 100 (times) Default value: 5 agentif.properties The agentif.
Property hdvmagtif.MaxPollingCount Description The maximum number of times that Replication Manager checks the processing status of a Device Manager Agent when Device Manager Agent takes an indefinite period of time to collect configuration information or to perform copy pair operations. If 0 is specified, there is no limit on the number of retries. Specifiable values: 0 to 100 (times) Default value: 50 hdvmagtif.
base.properties The base.properties file is used to specify the values of properties necessary for the internal processing of Replication Manager. The following table describes the available properties and settings. Table 52 List of properties in the base.properties File Property base.repositry.synchronize.polling Description Specifies whether Replication Manager automatically synchronizes with a Device Manager database.
Property Description This property specifies whether to acquire definition information of copy pairs defined in device groups. base.refreshdginfo.exec To acquire definition information, specify 1. To not acquire definition information, specify 0. Values that can be specified: 0 or 1 Default value: 1 base.alert.
5 Security management This chapter explains security functions that can be used in Replication Manager. Network communications security To provide security for the communication routes used by Replication Manager, you can use the HTTPS protocol to encrypt communications. The following routes can be encrypted: (1) Between HP StorageWorks P9000 Command View Advanced Edition Suite Common Component on the management server and the Web browser on the management client.
Figure 13 Communication Routes Used by Replication Manager The following four types of HTTP communication routes are also used: • Between Replication Manager (on the management server) and a Device Manager Agent (on a pair management server) • Between Replication Manager (on the management server) and a Business Continuity Manager Software (on the host) unless IHS is used. • Between Replication Manager (on the management server) and P9000 mainframe agent (on the host).
Figure 14 Flow of operations for setting up secure communications between Common Component and a Web browser For more information on the procedures, see the following descriptions in the HP P9000 Command View Advanced Edition Suite Software Administrator Guide: • Creating a secret key for Common Component • Creating a certificate signing request for Common Component • Creating a secret key and a certificate signing request for Common Component (Advanced security mode) • Applying to a certificate authority f
Securing communications between Replication Manager and the Device Manager server To encrypt communications between Replication Manager on the management server and the Device Manager server (local or remote), you must create a server certificate for the Device Manager server and import it into the truststore (jssecacerts) file in Replication Manager.
• • • • • Importing a server certificate into the Device Manager server truststore Downloading a Device Manager server truststore file Exporting a Device Manager server self-signed certificate Importing a server certificate into the truststore Checking the server certificates imported into the truststore After importing the server certificate for the Device Manager server to the truststore (jssecacerts), select HTTPS as the transmission protocol in the Replication Manager GUI window for adding (or the win
Figure 16 Flow of operation for setting up secure communications between Replication Manager and BCM (IHS) If you use a well-known certificate authority (CA), its server certificate might already be in the truststore (jssecacerts). In this case, you do not need to import the CA’s server certificate again. For more information on the procedure for using BCM (IHS) as an SSL server, see the description of setting up HTTPS connections in the HP P9000 for Business Continuity Manager Software Installation Guide.
NOTE: Regarding server certificates: • If you manage multiple BCM (IHS) hosts as information sources, you must create server certificates for each server and import them into the truststore (jssecacerts) for the management server running Replication Manager. • A secure method must be used to transmit the server certificate for the IHS to the management server running Replication Manager. Audit log event categories This section describes the information output in the Replication Manager audit log.
Description of category Audit event Severity Successful resource group property editing 6 Failed resource group property editing 3 Addition of a user to a resource group (GUI) Successful user addition to a resource group 6 KAPM02632-I Failed user addition to a resource group 3 KAPM02637-E Removing of a user from a resource group (GUI) Successful user removal from a resource group 6 KAPM02633-I Failed user removal from a resource group 3 KAPM02638-E Assignment of a user to a resource gro
Description of category Audit event Severity Message ID KAVN10014-E An attempt to edit or distribute the disk configuration definition file has failed. 3 KAVN10017-E KAVN10020-E KAVN10023-E Management host change operation KAVN10024-I Editing or distribution of the copy group configuration definition file has started. 6 The copy group configuration definition file was successfully edited or distributed. 6 An attempt to edit or distribute the copy group configuration definition file has failed.
Description of category Audit event Severity Message ID KAVN10033-E KAVN10036-E Creation, editing, execution, canceling, or deletion of a task has failed. 3 KAVN10039-E KAVN10042-E KAVN10045-E 106 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 111.
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 117. 2. Check the messages output to the Replication Manager event log and correct the error. For details on how to view the event log data, see the HP P9000 Replication Manager Software User Guide. 3.
• • • • • Properties files License command log files Files that contain license information Files related to the database Service pack log files NOTE: Observe the following precautions with commands: • Do not execute the cvxpaegetlogs command more than once at the same time. Also, do not execute this command and the hcmdsdbmove or hcmdsdbclustersetup command at the same time.
Argument Description 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 111 Resolving Application Agent operation errors, page 113 Collecting support information with the hrpmap_getras command, page 113 Application Agent events that can be ignored, page 114 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 57 List of files collected in the drminfo folder Files Description Location copied from .version* Application Agent version information file Common-Agent-installationfolder\ all Files for each type of Application Agent environment setting Common-Agent-installationfolder\conf drm_output.log drm_output.log.
Server on which event occurred When message is output to event log Type Source Event ID Message Backup server A VSS backup is executed. Error Virtual Disk Service 1 Unexpected Failure. Error code: 1@02000018 Backup server A VSS backup is executed. Error Virtual Disk Service 1 Unexpected Failure. Error code: 48F@02000018 Backup server A VSS backup is executed. Error VDS Dynamic Provider 10 The provider failed while storing notifications from the driver.
Server on which event occurred When message is output to event log Type Source Event ID Message SCR env. target A VSS backup is executed. Error Microsoft Exchange Repl 2104 Log file action LogCopy failed for storage group "xxx". Reason: CreateFile("xxx") = 2 Backup server Simultaneous backups are executed in a cascade configuration. Error Service Control Manager 7034 The Logical Disk Manager Administrative Service service terminated unexpectedly. It has done this xx time(s).
Troubleshooting detailed message RPM-00824 Detailed message RPM-00824 indicates that the HP StorageWorks P9000 Command View AE Common Component database memory area is insufficient. Check the amount of space available on the disk on which Replication Manager is installed.
3.
Transferring the database to a Windows Microsoft Cluster Server (MSCS) The following topics describe the procedures for moving data when Microsoft Cluster Server (MSCS) is used. Make sure that before executing a transfer, you adhere to the conditions described in “Transferring the database to a cluster server” on page 118. Procedure on the executing node 1.
7. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Move Group to switch the node to the standby node. Procedure on the standby node 1. On the standby node, make sure that the standby node currently owns the HP StorageWorks P9000 Command View AE Common Component service and the shared disk. 2.
4. Move the database onto the shared disk and follow all procedure as described in “Using the hcmdsdbclustersetup command” on page 122. NOTE: This step is unnecessary if other P9000 Command View AE suite products have been set up in a cluster configuration. Don't separate the shared disk from the active node until the hcmdsdbclustersetup command is complete.
6. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Move Group to switch the node to the executing node. 7. In the Cluster Administrator window, right-click the group in which the HDvM service (DeviceManagerServer) is registered, and choose Online. Using the hcmdsdbclustersetup command If there are no P9000 Command View AE suite products in a cluster configuration on the same host, execute the command shown below.
This example shows how to execute the hcmdsdbclustersetup command: "C:\Program Files\CVXPAE\Base\bin\hcmdsdbclustersetup" /createcluster / databasepath R:\re_creating_db /exportpath C:\storing_data /auto Troubleshooting when copy pairs are not recognized In an environment where Device Manager and P9000 RAID Manager manage copy pairs, if information about the existing copy pairs cannot be recognized after refreshing the configuration information, take the following actions to correct the problem: 1.
Installation of Device Manager Agent Make sure Device Manager Agent is installed on both pair management servers that manage a primary and secondary volume. Link between Device Manager server and Device Manager Agent Make sure Device Manager Agent links correctly with Device Manager server using the hdvmagt_account command. If the link is incorrect, execute this command on the pair management server to change the settings. 1.
Properties of Device Manager Agent Make sure Device Manager Agent properties (stored in the pair management server) are correct. For details about the properties to be specified, see “Setting up the prerequisite environment” on page 47. If you change the properties, restart Device Manager Agent.
NOTE: On copy pairs that configure remote copies, you do not need to check this item. Check the following: • On the host (pair management server) properties window, make sure that you can click the button to view the pair information managed by the host. • On the window displayed by clicking the button to view the pair information, make sure that existing copy group names and copy pair names are displayed.
Backup server is not recognized as a pair management server If Replication Manager does not recognize the backup server as a pair management server, make sure that the P9000 RAID Manager instance on the backup server is running before performing the following operations: • Executing Setup Agent or Refresh Hosts • Executing Mount Replica or Unmount Replica.
Restoring a replica fails with event ID 454 If you have applied Exchange Server 2003 Service Pack 1 to a database server and end up with a mixture of transaction logs from before and after the service pack installation, a restore operation on the data may fail. In such a case, an event log with an event ID of 454 will be output. Follow this procedure for the restore: 1. Execute the following command for each of the *.edb and *.
3. To display the current disk statuses, enter list disk. A list of disks that are currently connected to the server will be displayed. The disk numbers are shown in the Disk ### column. Make sure that in the Status column, statuses of disks whose disk numbers correspond to the disk numbers on the secondary volumes are Online. 4. For each secondary volume whose disk status is Online, perform the following procedure: 1. Enter select disk disk-number. 2.
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 59 to refer to HP StorageWorks P9000 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Synchronous Continuous Access Synchronous • Continuous Access XP Synchronous • P9000 Continuous Access Synchronous • XP Continuous Access Synchronous This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Journal Continuous Access Journal • Continuous Access XP Journal • P9000 Continuous Access Journal
Support and other resources
A Version compatibility with other Command View AE Suite products This appendix describes the compatibility between versions of Replication Manager and other Command View AE Suite product versions. Restrictions when Replication Manager and Device Manager versions differ The following restrictions for configuring the Replication Manager system are dependent on the version of Device Manager that is installed on the components (management server, pair management server, and hosts).
Release Number Restriction Device Manager Server or Device Manager Agent 7.1 or earlier Mainframe system volume attributes may not display correctly.
B Supported functions and unsupported configurations This appendix provides information on functions and supported by Replication Manager.
Open Creating and deleting copy pairs Mainframe DevMgr Server DevMgr Agent BCM P9000 mainframe agent N Y Y* N Y Y N Replication operation support functionality Changing copy pair statuses N Legend * - Only the pair definition function for creating a copy group definition file is supported. The creation of copy pairs is not supported. List of tasks supported for each storage system The tasks supported by Replication Manager depend on the storage system model.
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Replication status display Acquisition of latest pair statuses Acquisition of latest remote-copy performance information Replication management logical-group creation and deletion Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Site-view-based "Site" definit
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N N N N N N Y Y Y N N N N N N N Y Y Y N N n/a n/a n/a N N Y Y Y N N n/a n/a n/a N N Y Y Y N N n/a n/a n/a N N Y Y Y N N N N N N N Y Y Y N N N N N N N Y Y Y N N N N N N N N Y Y n/a n/a n/a n/a n/a N N N Y Y n/a n/a n/a n/a n/a N N Y
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N N Y Y Y N N N N N Y Y Y Y Y N N N N N N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 N N Y Y Y N N Y2,4 Y2,4 Y2,4 Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Re
Support for each storage system Upper row: open system Lower row: mainframe system Task XP512/XP48 XP1024/XP128 XP12000/ XP10000/ SVS200 XP24000/ XP20000 P9500 N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y N Y Y Y Y N N Y Y Y N N Y3,4 Y3,4 Y3,4 Y Y Y Y Y N N Y4 Y4 Y4 N N Y5,6 Y5,6 Y6,7 N N N N N Automated alert renotification Detailed monitoring and alert notification of each individual copy pai
4. 5. 6. 7. This function can be used only when BCM is used. It cannot be used with P9000 mainframe agent. Continuous Access Journal, Continuous Access, and Continuous Access Synchronous are supported. No other remote copy or local copy functions are supported. Device Manager agent 6.4.0 or later must be installed on the host. Continuous Access Journal and Continuous Access Synchronous are supported. No other remote copy or local copy functions are supported.
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 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 145. 2. Follow the instructions in “Adding a storage system” on page 146.
Checking the items required to execute Device Manager CLI You need to check the following items to execute Device Manager CLI. Table 62 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 64 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 145 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 65 Settings to be checked by the GetHost command Value Settings to be checked The value specified for instanceNumber in An instance of ConfigFile This value and the instance number in the configuration definition file are the same.
objectID=HOST.8 name=cci-vm-r ipAddress=10.208.176.103 capacityInKB=42,991,616 hostType=-1 List of 2 ConfigFile elements: An instance of ConfigFile objectID=CONFIGFILE.8.10 instanceNumber=10 controlledBy=Device Manager portNumber=50,010 valid=1 List of 1 ReplicationGroup elements: An instance of ReplicationGroup objectID=REPGROUP.5 replicationGroupID=5 groupName=SI-CG01-R pvolHostID=8 : copyTrackSize=-1 List of 2 ReplicationInfo elements: An instance of ReplicationInfo objectID=REPINFO.83000101.601.
List of 1 WWN elements: An instance of WWN WWN=50.00.08.70.00.30.55.04 3. If the execution results and the values specified in the RAID Manager configuration definition file do not match, execute the AddStorageArray command to refresh the storage system information. AddStorageArray ipaddress=IP-address family=array-family Specify the storage system IP address for IP-address. For XP24000/XP20000, you can use an IPv6 address.
Acronyms and Abbreviations The following acronyms and abbreviations appear in this guide.
iSCSI Internet Small Computer System Interface JDK Java Development Kit LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical DEVice LU Logical Unit LUN Logical Unit Number MCU Main Control Unit MIB Management Information Base NAS Network Attached Storage NAT Network Address Translation NIC Network Interface Card NTP Network Time Protocol OS Operating System PAP Password Authentication Protocol PPRC Peer-to-Peer Remote Copy RADIUS Remote Authenticati
UAC User Account Control URL Uniform Resource Locator Configuration Guide 159
Acronyms and Abbreviations
Glossary This glossary defines the special terms used in this document. Click the desired letter below to display the glossary entries that start with that letter. 3DC multi-target configuration A configuration in which, in addition to the local site, a connection is established between a nearby remote site and a distant remote site and Continuous Access Synchronous and Continuous Access Journal are used to copy storage system volumes among the three sites (called data centers).
cluster software Software installed on management server nodes to boost overall availability by duplicating management servers as a cluster system. Available software depends on the OS that runs on the management server. consistency group A group used as a unit in Continuous Access or Continuous Access Journal that maintains integrity of the update order for volumes. Continuous Access Software that duplicates volumes between storage systems. Continuous Access duplicates all data on the volumes.
Manager Software. Depending on the type of volume scan, volumes are assigned the local DAD, Non Gen'ed DAD, or remote DAD attribute. DAD ID A name that identifies a DAD. delta resync A status in which synchronization processing is performed by copying differential data to an Continuous Access Journal copy pair in which part of the copy pair exists on the local site and part exists on a remote site in a 3DC Multi-Target configuration.
multi-target configuration A copy pair configuration with a one-to-many relationship between the primary and secondary volumes. Information from one volume is copied to multiple volumes. Non-Gen’ed Volume A volume that is not recognized by a mainframe host. P9000 Command View AE Common Component A component that bundles common functions used by P9000 Command View AE suite products.
Remote Scan A volume scan that can be performed on Non Gen'ed volumes outside the site where HP StorageWorks P9000 for Business Continuity Manager Software resides. The remote DAD attribute is assigned to the disk configuration definition file in which the discovered volumes are stored. SP-VOL (secondary-primary volume) The volume located in the middle of a cascade structure, when a cascade structure is used by the volume replication functionality of a storage system.
Glossary
Index A Administrator privileges (UAC), agent.logger.properties, 81 agentif.properties file, 93 Application Agent and P9000 RAID Manager, 76 cluster configuration, 68 - 69, 77 described, 55 error log options, 81 installing, 74 log files, 79, 112 maximum number, 67 port numbers, 79 reinstalling, 67 requirements, 56, 68 service, 80 troubleshooting, 111 audit event, 103 audit log event categories, 103 B base.properties file, 95 base.repositry.synchronize.polling, 95 BCM Agent, 23 - 24, 46 bcmif.
I information source, 163 infrastructure mainframe, 50 open systems, 48 inqraid $Phys -CLI command, 128 L LDEV maximum number, 36 link menu, 52 log file log amount of data, 91 logger.
troubleshooting, 107 maintenance information, 108 resolving errors, 107 RPM-00824, 117 U UAC, 83 unsupported configurations, 143 - 144 V VMware ESX/ESXi support, 70 VSS Provider log files, 112 requirements, 67 W web sites HP, 131 Configuration Guide 169
