Hitachi Command Suite Replication Manager

Hitachi Command SuiteReplication Manager8.6

Configuration Guide

This document describes how to configure the Replication Manager software.

MK-98HC151-30

May 2018

© 2014, 2018 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechanical, including copying and recording, or stored in a database or retrievalsystem for commercial purposes without the express written permission of Hitachi, Ltd., or HitachiVantara Corporation (collectively "Hitachi"). Licensee may make copies of the Materials providedthat any such copy is: (i) created as an essential step in utilization of the Software as licensed andis used in no other manner; or (ii) used for archival purposes. Licensee may not make any othercopies of the Materials. "Materials" mean text, data, photographs, graphics, audio, video anddocuments.

Hitachi reserves the right to make changes to this Material at any time without notice and assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Vantara Corporation at https://support.hitachivantara.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi Vantara Corporation.

By using this software, you agree that you are responsible for:

1) Acquiring the relevant consents as may be required under local privacy laws or otherwise fromauthorized employees and other individuals; and

2) Verifying that your data continues to be held, retrieved, deleted, or otherwise processed inaccordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and WindowsVista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screenshots are reprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website areproperties of their respective owners.

iiHitachi Replication Manager Configuration Guide

https://support.hitachivantara.com/en_us/contact-us.html

Contents

Preface................................................................................................. viiIntended audience...................................................................................................viiiProduct version....................................................................................................... viiiRelease notes..........................................................................................................viiiDocument organization............................................................................................ viiiReferenced documents.............................................................................................. ixDocument conventions............................................................................................... xConvention for storage capacity values....................................................................... xiAccessing product documentation..............................................................................xiiGetting help............................................................................................................. xiiComments............................................................................................................... xii

1 Overview of Replication Manager........................................................... 1-1About Replication Manager...................................................................................... 1-2

Features.......................................................................................................... 1-3Replication Manager operations roadmap................................................................. 1-4

2 Replication Manager system configurations and requirements.................. 2-1Replication Manager system configurations...............................................................2-2

Configurations for open systems........................................................................2-2Open system components........................................................................2-9

Configurations for mainframe systems..............................................................2-13Mainframe system components.............................................................. 2-15Mainframe Agent versus BCM Agent....................................................... 2-18

Prerequisites for managing copy pairs on mainframe systems using CCI............. 2-18Prerequisites for data migration using virtual IDs (VSP and HUS VM)..................2-19Prerequisites for nondisruptive migration (VSP G1000, VSP G1500, VSP F1500, VSPGx00 models, or VSP Fx00 models)..................................................................2-19Prerequisites for managing global-active device copy pairs.................................2-21Prerequisites for managing copy pairs using snapshot groups............................ 2-22Mainframe pairs and Device Manager Agent..................................................... 2-22Configurations for mainframe monitoring..........................................................2-23Virtual command device requirements for managing copy pairs..........................2-23

Specifying port numbers for pair management servers............................. 2-25Configurations for replica management............................................................ 2-25

iiiHitachi Replication Manager Configuration Guide

Components for replica management......................................................2-27Replication Manager in standby configuration................................................... 2-28

System limits........................................................................................................ 2-29Resource Limits.............................................................................................. 2-29Maximum number of copy pairs....................................................................... 2-30Maximum number of LDEVs.............................................................................2-31Log data and number of copy pairs.................................................................. 2-31

Firewall exceptions................................................................................................2-32How Replication Manager collects data................................................................... 2-34

Data collection in open systems....................................................................... 2-34Data collection in mainframe systems...............................................................2-36

3 Setting up Replication Manager..............................................................3-1Overview................................................................................................................3-2Concerning upgrade installations..............................................................................3-2

Items to be checked after upgrading Replication Manager................................... 3-2Setting up the prerequisite environment................................................................... 3-3

Open systems environment............................................................................... 3-5Mainframe systems environment........................................................................3-6Application replica environment......................................................................... 3-8

Adding a link menu to the GUI display .....................................................................3-8hcmds64link command options..........................................................................3-9Creating a user-defined application file...............................................................3-9

4 Setting up Application Agent..................................................................4-1About Application Agent.......................................................................................... 4-2

Application Agent functions............................................................................... 4-2Application Agent installation location.......................................................................4-8

Application Agent installation path restrictions.................................................... 4-8If you plan to install Application Agent on the management server.......................4-9

Application Agent and OS upgrades..........................................................................4-9Installing Application Agent....................................................................................4-10Adding Application Agent to the Windows Firewall Exception list...............................4-12Application Agent and CCI..................................................................................... 4-12

Command line interface for CCI....................................................................... 4-12Protection function of CCI................................................................................4-13Using CCI to configure pair volumes.................................................................4-13Device Manager and CCI................................................................................. 4-13Starting and stopping CCI instances................................................................. 4-13Configuring a system to back up an SQL Server database..................................4-13Configuring a system to create Exchange Server database replicas.....................4-14

Settings for Application Agent in a cluster configuration........................................... 4-14Unsupported cluster configuration....................................................................4-16Creating SQL Server replicas in a cluster configuration.......................................4-16Creating Exchange Server replicas in a cluster configuration.............................. 4-16Exchange Server 2007 in Windows Server Failover Clustering............................ 4-17

Requirements and precautions for volume configurations.........................................4-17Volume configurations usable by Application Agent........................................... 4-17Requirements for unmounting and mounting volumes....................................... 4-18Requirements for backing up and restoring volumes..........................................4-19Precautions when changing a volume configuration...........................................4-19

ivHitachi Replication Manager Configuration Guide

Precautions for disk partition styles.................................................................. 4-20Application Agent and Replication Manager log output............................................. 4-20Changing Application Agent port numbers...............................................................4-21Creating file system replicas...................................................................................4-22Starting and stopping the Application Agent Services...............................................4-22

Copy Controller service....................................................................................4-22Common Agent service....................................................................................4-22

Setting error logging options for Application Agent.................................................. 4-23

5 Operating the management server.........................................................5-1About executing commands on the management server............................................ 5-2

User permissions.............................................................................................. 5-2Setting up the PATH environment variable in Linux............................................. 5-2

Starting and stopping Replication Manager............................................................... 5-2Starting Replication Manager.............................................................................5-2Stopping Replication Manager ...........................................................................5-3Checking the operation status of Replication Manager ........................................ 5-4

Changing settings in the properties files................................................................... 5-5Properties related to Replication Manager...........................................................5-5logger.properties.............................................................................................. 5-8

About Replication Manager log output.....................................................5-11serverstorageif.properties................................................................................5-12bcmif.properties..............................................................................................5-12agentif.properties........................................................................................... 5-13appagentif.properties...................................................................................... 5-14base.properties...............................................................................................5-15RpMCLI.properties.......................................................................................... 5-18

6 Security management........................................................................... 6-1Network communications security............................................................................ 6-2

Securing communications between Hitachi Command Suite Common Component andWeb browsers.................................................................................................. 6-4Securing communications between Replication Manager and the Device Managerserver..............................................................................................................6-5Securing communications between Replication Manager and Business ContinuityManager (IHS)................................................................................................. 6-7

Collecting audit logs ...............................................................................................6-9

7 Troubleshooting....................................................................................7-1Overview................................................................................................................7-2General problem resolution......................................................................................7-2Collecting maintenance information..........................................................................7-3

Executing the collection command..................................................................... 7-3Examples of collection commands............................................................ 7-5

Troubleshooting Application Agent operations...........................................................7-5Resolving Application Agent installation and removal errors................................. 7-6

Application Agent and VSS Provider installer trace log files......................... 7-6Resolving Application Agent operation errors...................................................... 7-8About collecting support information..................................................................7-8Collecting support information with the hrpmap_getras command........................7-8

vHitachi Replication Manager Configuration Guide

Application Agent events that can be ignored....................................................7-10Troubleshooting when copy pairs are not recognized...............................................7-15

Items to be checked on the pair management server........................................ 7-15Installation of Device Manager Agent......................................................7-16Link between Device Manager server and Device Manager Agent..............7-16Properties of Device Manager Agent....................................................... 7-16Settings in the CCI configuration definition file.........................................7-16

Items to be checked from Device Manager GUI.................................................7-16Recognition of Device Manager Agent..................................................... 7-17Recognition of the command device........................................................7-17Recognition of the replication configuration............................................. 7-17Recognition of storage systems.............................................................. 7-18

Items to be checked from Replication Manager GUI.......................................... 7-18Creation of TrueCopy Extended Distance or COW Snapshot copy pairs fails (HUS100Series)................................................................................................................. 7-18Troubleshooting replica operations......................................................................... 7-19

Replica creation fails silently............................................................................ 7-20Backup server is not recognized as a pair management server........................... 7-20Restoring a replica with roll-forward fails with error message RPM-11510........... 7-20Creating a replica fails with error message RPM-10006...................................... 7-21Creating a replica fails with event IDs 17, 1 and 10010......................................7-21Disk status remains online after replica operation is complete............................ 7-21

A Version compatibility with other HCS products........................................A-1Restrictions when Replication Manager and Device Manager versions differ................ A-2Restrictions when Replication Manager and Business Continuity Manager versions differ.............................................................................................................................A-3

B Supported functions and unsupported configurations.............................. B-1Supported paths for acquiring information and performing processing........................ B-2List of tasks supported for each storage system........................................................B-3Unsupported configurations (open systems)............................................................. B-9Unsupported configurations (mainframe systems)................................................... B-12

Acronyms and Abbreviations

Glossary

Index

viHitachi Replication Manager Configuration Guide

Preface

This document describes the installation and configuration process for HitachiReplication Manager.

This preface includes the following information:

□ Intended audience

□ Product version

□ Release notes

□ Document organization

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface viiHitachi Replication Manager Configuration Guide

Intended audienceThis manual is intended for the following system administrators who useReplication Manager to operate and manage their systems:

• Those who design systems that use Replication Manager• Those who want to learn how to install or remove Replication Manager

and how to set up its environment• Those who operate and maintain a system in which Replication Manager is

installed

The manual assumes that the reader has the following types of knowledge:

Knowledge of storage systems and related software

• A basic knowledge of Storage Area Networks (SANs) and managementsoftware used to operate storage systems

• Knowledge of storage system volume replication functionality (such asShadowImage or TrueCopy )

Knowledge of prerequisite products

• Ability to use a prerequisite operating system and a Web browser• A basic knowledge of Device Manager• A basic knowledge of Business Continuity Manager or Mainframe Agent (if

managing a mainframe system)

Product versionThis document revision applies to Replication Manager v8.6.0 or later.

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document. Release notes areavailable on Hitachi Data Systems Support Connect: https://support.hitachivantara.com/en_us/documents.html

Document organizationThe following table provides an overview of the contents and organization ofthis document. Click the chapter title in the left column to go to that chapter.The first page of each chapter provides links to the sections in that chapter.

viii PrefaceHitachi Replication Manager Configuration Guide

https://support.hitachivantara.com/en_us/documents.html


Chapter Description

Chapter 1, Overview ofReplication Manager onpage 1-1

Provides a functional overview of Replication Manager andexplains its characteristics and its terminology.

Chapter 2, ReplicationManager systemconfigurations andrequirements on page2-1

Describes the system configurations, system components,and limits that apply to Replication Manager.

Chapter 3, Setting upReplication Manager onpage 3-1

Describes how to set up the necessary environment forReplication Manager.

Chapter 4, Setting upApplication Agent onpage 4-1

Describes how to set up the necessary environment andinstall Application Agent.

Chapter 5, Operating themanagement server onpage 5-1

Describes Replication Manager settings, including those forstarting and stopping services, how to back up and restoredatabases, and how to edit the properties file.

Chapter 6, Securitymanagement on page6-1

Describes the security functions available for ReplicationManager.

Chapter 7,Troubleshooting on page7-1

Describes what to do if problems occur during ReplicationManager operation.

Appendix A, Versioncompatibility with otherHCS products on pageA-1

Describes the compatibility between versions of ReplicationManager and other Hitachi Command Suite product versions.

Appendix B, Supportedfunctions andunsupportedconfigurations on pageB-1

Contains tables that summarize supported functions andconfigurations that are not supported.

Referenced documentsThe following referenced documents can be found on Hitachi Vantara SupportConnect: (https://support.hitachivantara.com/en_us/documents.html):

• Hitachi Command Suite Installation and Configuration Guide,MK-90HC173

• Hitachi Replication Manager User Guide, MK-99HC166• Hitachi Command Suite Administrator Guide, MK-90HC175• Hitachi Command Suite CLI Reference Guide, MK-90HC176• Hitachi Command Suite Messages, MK-90HC178• Hitachi Command Suite Business Continuity Manager User Guide,

MK-94RD247

Preface ixHitachi Replication Manager Configuration Guide


• Hitachi Command Suite Business Continuity Manager Installation UserGuide, MK-95HC104

• Hitachi Command Suite Mainframe Agent Installation and ConfigurationGuide, MK-96HC130

• Hitachi Command Suite Replication Manager Application Agent CLIReference Guide, MK-90HC181

• Hitachi Command Suite Replication Manager Application Agent CLI UserGuide, MK-90HC189

Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold • Indicates text in a window, including window titles, menus, menuoptions, buttons, fields, and labels. Example:Click OK.

• Indicates a emphasized words in list items.

Italic • Indicates a document title or emphasized words in text.• Indicates a variable, which is a placeholder for actual text

provided by the user or for output by the system. Example:pairdisplay -g group(For exceptions to this convention for variables, see the entry forangle brackets.)

Monospace Indicates text that is displayed on screen or entered by the user.Example:pairdisplay -g oradb

< > angledbrackets

Indicates a variable in the following scenarios:• Variables are not clearly separated from the surrounding text or

from other variables. Example:Status-<report-name><file-version>.csv

• Variables in headings.

[ ] squarebrackets

Indicates optional values. Example: [ a | b ] indicates that you canchoose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicatesthat you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options orarguments. Examples:[ a | b ] indicates that you can choose a, b, or nothing.{ a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

x PrefaceHitachi Replication Manager Configuration Guide

Icon Label Description

Note Calls attention to important or additional information.

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Caution Warns the user of adverse conditions or consequences (forexample, disruptive operations).

WARNING Warns the user of severe conditions or consequences (forexample, destructive operations).

Convention for storage capacity valuesPhysical storage capacity values (for example, drive capacity) are calculatedbased on the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity values (for example, logical device capacity, cache memorycapacity) are calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KBOpen-systems:• OPEN-V: 960 KB• Others: 720 KB

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

Preface xiHitachi Replication Manager Configuration Guide

Logical capacity unit Value

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentationProduct documentation is available on Hitachi Vantara Support Connect:https://support.hitachivantara.com/en_us/documents.html. Check this sitefor the most current documentation, including important updates that mayhave been made after the release of the product.

Getting helpHitachi Vantara Support Connect is the destination for technical support ofproducts and solutions sold by Hitachi Vantara. To contact technical support,log on to Hitachi Vantara Support Connect for contact information: https://support.hitachivantara.com/en_us/contact-us.html.

Hitachi Vantara Community is a global online community for HDS customers,partners, independent software vendors, employees, and prospects. It is thedestination to get answers, discover insights, and make connections. Jointhe conversation today! Go to community.hitachivantara.com, register,and complete your profile.

CommentsPlease send us your comments on this document [email protected]. Include the document title, and number,including the revision level (for example, -07), and refer to specific sectionsand paragraphs whenever possible. All comments become the property ofHitachi Vantara Corporation.

Thank you!

xii PrefaceHitachi Replication Manager Configuration Guide




https://community.hitachivantara.com/welcome

1Overview of Replication Manager

This chapter provides information that you will need to understand beforerunning a system that incorporates Replication Manager. This informationalso includes an overview of the system.

□ About Replication Manager

□ Replication Manager operations roadmap

Overview of Replication Manager 1-1Hitachi Replication Manager Configuration Guide

About Replication ManagerReplication Manager allows you to manage the replication of storage systemvolumes in large-scale system configurations.

To prevent data loss or disruption of work services due to unforeseenaccidents or disasters, a replication environment that is designed withdisaster recovery already taken into account is required. Replication Manageruses the volume replication functionality of Hitachi storage systems to reducethe workload involved in management tasks such as protecting and restoringsystem data. The following figure illustrates an example of a replicationenvironment designed for disaster recovery, in which a number of separatesites are linked together.

Figure 1-1 Example of a replication environment

Volume replication indicates the replication of volumes within a specificstorage system (local copying) or across multiple storage systems (remotecopying). You can improve system reliability by using a combination of localcopying and remote copying, to back up and manage important work data.For example, local and remote copying enables you to respond efficiently todisruptions caused by hardware failures. Also, by using remote copying tocopy data to distant locations, you can recover and continue businessoperation if a disaster occurs.

1-2 Overview of Replication ManagerHitachi Replication Manager Configuration Guide

FeaturesReplication Manager provides the following features to assist storageadministrators.

Centralized management of the replication environment

Replication Manager can be used to manage storage systems (such asUniversal Storage Platform V/VM, or Hitachi AMS2000) and hosts (such asWindows, Linux, or mainframes) that are at a number of different sites. Asingle instance of Replication Manager can manage up to 24,000 open copypairs. The status of the large number of copy pairs in these systems, theprogress of copy operations, and performance information (such as datatransfer delays between copy pairs and buffer usage when copying volumes)can be centrally managed from a single console.

Integrated database backup management

Replication Manager supports creating backups of Exchange Server and SQLServer databases. Known as application replicas, these backup snapshots aremanaged as a series of secondary volumes that are rotated on a scheduledbasis. Replication Manager manages the relationships between backupobjects and their associated logical units within storage systems, therelationships between primary and secondary volumes, and the backuphistory. Replicas can be mounted and dumped to tape, using scripts that areexecuted through Replication Manager.

Visual representation of replication structures

Administrators can visually check the structure of copy pairs that areconfigured across multiple storage systems by examining the structure fromthe perspective of a host, a storage system, an application, or a copy pairconfiguration definition. Copy pairs in complex configurations can be viewedas lists. Complex configurations include multi-target configurations in whichone volume is copied to multiple volumes; and cascade configurations inwhich primary and secondary volume relationships occur consecutively (sothat, for example, the secondary volume of one copy pair becomes theprimary volume of another copy pair).

Immediate notification of error information

To enable prompt error detection and resolution, the environment mustsupport error notification from the source of the problem, enabling theadministrator to identify the location of the error. In Replication Manager, youcan specify monitoring conditions for designated copy pairs and sidefiles, andalerts will be automatically generated when the conditions are satisfied. Suchmeasures allow you to work out strategies to prevent possible problems fromoccurring. For example, you can develop strategies to prevent transferperformance deterioration due to insufficient network capacity, or to preventpairs from being blocked due to a buffer overflow. The status of applicationreplicas is tracked and reflected in summary form so that the administratorknows to what extent the application databases are protected.


You can continue monitoring the system even when not logged in toReplication Manager, because alerts can be reported in the form of emailmessages or SNMP traps.

Modification of replication structures

You can configure additional copy pairs as business operations expand, andimprove performance by expanding buffer space for copying volumes. Youcan also change pair states manually after error recovery. Using GUI-basedwizards, you can set up pairs while visually keeping track of complexreplication structures.

Monitoring and analyzing remote copy performance (write delaytime)

When using Universal Replicator, you can check copy performance visuallyusing the Replication tab of the Device Manager GUI.

Note: Use of the Replication tab requires licenses for Device Manager andTuning Manager.

When a drop in performance occurs, you can analyze the cause by checkingthe detailed information provided by the Replication tab. For moreinformation, see the Hitachi Command Suite User Guide.

Replication Manager operations roadmapThe following figure shows the roadmap for system configuration, operation,and maintenance, using Replication Manager.


Figure 1-2 Replication Manager operations roadmap

The chapters in this manual cover the tasks labeled “System configuration”and “Maintenance” in Figure 1-2 Replication Manager operations roadmap onpage 1-5. For detailed information about operation, see the HitachiReplication Manager User Guide.



2Replication Manager system

configurations and requirements

This chapter describes the system configurations, system components, andsystem requirements of Replication Manager. Please refer to the HitachiCommand Suite System Requirements for detailed system requirementsassociated with each component of Replication Manager.

To help you understand systems that use Replication Manager, this chapteralso describes the flow of control and data between programs.

□ Replication Manager system configurations

□ System limits

□ Firewall exceptions

□ How Replication Manager collects data

Replication Manager system configurations and requirements 2-1Hitachi Replication Manager Configuration Guide

Replication Manager system configurationsThis section describes the basic system configurations for ReplicationManager. Although the following descriptions treat open systems andmainframe systems separately, Replication Manager also supportsenvironments that contain both.

Configurations for open systemsThis section describes basic system configurations for open systems. Thefollowing figures show examples of site configurations:

• Figure 2-1 Single site configuration in open systems on page 2-3• Figure 2-2 Two-site configuration in open systems on page 2-4• Figure 2-3 Three-site configuration in open systems on page 2-5• Figure 2-5 Redundant pair management server configuration in open

systems on page 2-7• Figure 2-4 Pair managenment using a file server or NAS module on page

2-6• Figure 2-6 Example GAD configuration on page 2-9

2-2 Replication Manager system configurations and requirementsHitachi Replication Manager Configuration Guide

Figure 2-1 Single site configuration in open systems


Figure 2-2 Two-site configuration in open systems


Figure 2-3 Three-site configuration in open systems

You can use the central management method to manage copy pairs ofvolumes that are assigned to a file server or NAS module (instead of beingconnected to a host). For details about the central management method andthe configuration definition file, see the Hitachi Command Suite AdministratorGuide.


Figure 2-4 Pair managenment using a file server or NAS module


Figure 2-5 Redundant pair management server configuration in opensystems

For more information on redundant configurations, see the Hitachi ReplicationManager User Guide.

Global-active device configurations

This guide does not include detailed information on global-active device(GAD) configurations. For complete setup requirements and managementprocedures, see:

• Global-Active Device User Guide• Hitachi Command Suite User Guide


Note: The following conditions apply:

• GAD configurations are only supported on VSP G1000, VSP G1500, VSPF1500, VSP Gx00 models, or Fx00 models storage systems.

• Application Agent does not support replica management using GAD copypairs.


Figure 2-6 Example GAD configuration

Open system components

The following tables list and describe system components for each type ofsystem and provide an overview of the software components:


• Table 2-1 System components (for open systems) on page 2-10• Table 2-2 Overview of mandatory software (for open systems) on page

2-12

Table 2-1 System components (for open systems)

System components Software included insystem components Description

Management client Web browser A management client is a computer onwhich a Web browser is used to run theGUI for Device Manager and ReplicationManager. Replication Manager runs onthe management server.

Management server Replication ManagerDevice Manager server

A management server providesmanagement information in response torequests from management clients.Replication Manager and DeviceManager server (a prerequisite programof Replication Manager) are installed onthe management server.If multiple sites are used, amanagement server is required for eachsite. Replication Manager and DeviceManager server are installed on themanagement server at the local site.Device Manager server is installed onthe management server at the remotesite.Note: When a remote copy isperformed between sites, theinformation displayed by the GUI islimited dependent upon the storagesystem model. For details about howthe system configuration limitsdisplayed information, see the HitachiReplication Manager User Guide.For communication between amanagement server and pairmanagement server, ensure that eachcan resolve the others’ IP address fromtheir host names. If the settings arespecified so that address conversion isperformed between the sites (such asfor a private address and NAT),Replication Manager might not correctlyconnect to Device Manager Agents atother sites.

Pair managementserver

CCIDevice Manager Agent

A pair management server collectsmanagement information, includingcopy pair statuses and performanceinformation for remote copying. CCI(Command Control Interface) andDevice Manager Agent are installed oneach pair management server.



By installing CCI and Device ManagerAgent, you can manipulate copy pairsfrom Replication Manager. The pairmanagement server must recognize thecommand device in the target storagesystem.If multiple sites are used, at least onepair management server is required foreach site. Multiple pair managementservers can be set up at each site.A pair management server can also beused as a host. When determiningwhether to set up pair managementservers to be independent of hosts,consider security and the loads on thehosts.For communication between pairmanagement servers; if you perform aremote copy using multiple pairmanagement servers, ensure that thepair management server at the primarysite and the pair management server atthe secondary site can determine the IPaddress from their respective hostnames. If they cannot, an error mightoccur during copy pair creation.Note: Pair management servers mustbe connected to an SVP, a server thatprovides functions of storage systemmanagement, or a virtual commanddevice server through UDP.

Host Device Manager Agent Normally, a host is a computer on whichapplication programs are installed.Device Manager Agent is also installedon a host. A host uses storage systemsas external storage systems.Installing Device Manager Agent isoptional. If you install Device ManagerAgent on a host, you can viewinformation about that host (such as IPaddress and mount points) fromReplication Manager.

Storage system MicroprogramsNote: If necessary,register licenses forproducts (such asUniversal Replicator orShadowImage).

A storage system is an external storagesystem connected to a host.


Table 2-2 Overview of mandatory software (for open systems)

Software Description

Replication Manager Used to centrally manage the replication of storage systemvolumes in large-scale system configurations.Replication Manager includes Hitachi Command Suite CommonComponent, a collection of functions that are shared by HitachiCommand Suite products. Common Component is installed as acomponent of the Hitachi Command Suite server products and isupgraded with the latest version during installation.

Device Managerserver

Used for integrated management of resources and for configuringstorage system hardware. You can run and manage a systemthat consists of multiple storage systems.An instance of Device Manager server running on the samemanagement server as Replication Manager is called an instanceof "local Device Manager." Instances of Device Manager runningon the a management server different from the managementserver on which Replication Manager is running are calledinstances of "remote Device Manager."Note that even when the instance of Device Manager server isrunning on a primary site, if Replication Manager is running on adifferent management server, the instance of Device Managerserver on the primary site is still called "remote Device Manager.”Replication Manager performs copy pair operations and otheroperations on volumes of storage systems that are managed byDevice Manager server. For details about this server, see theHitachi Command Suite Administrator Guide.

Device Manageragent

Device Manager agents instruct CCI to perform copy pairoperations in response to requests from Replication Manager andprovide Device Manager server with host information.If you plan to manage copy groups defined by device group, anappropriate Device Manager agent version, which depends on thestorage system as follows, must be installed:• For VSP G350, G370, G700, G900 or VSP F350, F370, F700,

F900: v8.5.0-08 or later• For VSP G1000: v8.0 or later• For VSP G1500, F1500: v8.5 or later• For Virtual Storage Platform: v7.1 or later• For HUS VM: v7.3.1 or later• For VSP G200, G400, G600: v8.1.3 or later• For VSP G800: v8.2 or later• For VSP F400, F600, F800: v8.2.1 or laterFor details about these agents, see the Hitachi Command SuiteAdministrator Guide.

CCI Software that controls volume replication functions (such asTrueCopy or ShadowImage), by issuing commands from a host tostorage systems. (Make certain that the version of CCI supportsyour storage system.)Replication Manager uses the CCI configuration definition file tochange a copy pair configuration and acquire configuration



information. For details, see the manual for the correspondingversion of CCI.Replication Manager manages the configuration definition fileusing Device Manager Agent. For details, refer to the HitachiCommand Suite Administrator Guide.

Configurations for mainframe systemsThis section describes the basic system configurations in use when the host isa mainframe system host. Mainframe system configurations use eitherBusiness Continuity Manager or Mainframe Agent. The following figures showexamples of configurations depending on the software program:

• Figure 2-7 Mainframe configuration using Business Continuity Manager(BCM) on page 2-14

• Figure 2-8 Mainframe configuration using Device Manager server andMainframe Agent on page 2-15


Figure 2-7 Mainframe configuration using Business Continuity Manager(BCM)


Figure 2-8 Mainframe configuration using Device Manager server andMainframe Agent

Mainframe system components

The following tables describe system components for each type of system andprovide an overview of the software components:

• Table 2-3 System components (for mainframe systems) on page 2-15• Table 2-4 Overview of mandatory software for mainframe management

on page 2-17

Table 2-3 System components (for mainframe systems)


Management client Web browser A management client is a computer onwhich users use a Web browser to runthe GUI for Replication Manager.Replication Manager runs on themanagement server.

Management server Replication ManagerDevice Manager server

A management server providesmanagement information in response torequests from management clients.Replication Manager and DeviceManager server (a prerequisite program



of Replication Manager) are installed onthe management server.If multiple sites are used, amanagement server is required for thelocal site.

Host (pairmanagement server)

Business ContinuityManager or MainframeAgent

Usually, a host is the computer onwhich the application programs areinstalled. Business Continuity Manageror Mainframe Agent is installed on ahost.Note: If Device Manager server is notregistered as an information source, orMainframe Agent is being used, theinformation displayed by the GUI islimited. For details, see the HitachiReplication Manager User Guide.By installing Business ContinuityManager (6.2 or later), you can managecopy pairs from Replication Manager.BCM Agent (installed as part ofBusiness Continuity Manager) handlesrequests from Replication Manager. Formore information, see Mainframe Agentversus BCM Agent on page 2-18.If you use the remote scan function ofBusiness Continuity Manager, there isno need to install a host (pairmanagement server) at the remote site.Note: You must set up an environmentprior to performing remote scans orusing pair management functions. Fordetails, see the Hitachi BusinessContinuity Manager User Guide.Like a pair management server in anopen system, a mainframe system hostcollects management information,including copy pair statuses andperformance information for remotecopying. Therefore, a mainframesystem host is sometimes called a pairmanagement server.

Storage system MicroprogramsNote: If necessary,register licenses forproducts (such as forTrueCopy Sync orUniversal Replicator).

A storage system is used to store dataaccessed by hosts.


Table 2-4 Overview of mandatory software for mainframe management


Replication Manager Used to centrally manage the replication of storage systemvolumes in large-scale system configurations.Replication Manager includes Hitachi Command Suite CommonComponent, a collection of functions shared by HitachiCommand Suite products. Common Component is installed as acomponent of the Hitachi Command Suite server products and isupgraded to the latest version during installation.

Device Manager server Used to achieve integrated management of disk resources andfor configuring storage system hardware. You can run andmanage a system consisting of multiple storage systems.An instance of Device Manager server running on the samemanagement server as Replication Manager is called an instanceof "local Device Manager." Instances of Device Manager runningon the a management server different from the managementserver on which Replication Manager is running are calledinstances of "remote Device Manager."Note that even when the instance of Device Manager server isrunning on a primary site, if Replication Manager is running on adifferent management server, the instance of Device Managerserver on the primary site is still called "remote DeviceManager."For details about Device Manager server, see the HitachiCommand Suite Administrator Guide.

Business ContinuityManager and BCMAgent

Used to control copy group configurations located on storagesystems from a host.Via BCM Agent, Replication Manager monitors and performscopy pair operations on storage systems managed by BusinessContinuity Manager. For details about Business ContinuityManager, see the Hitachi Business Continuity Manager UserGuide.Note: Pair management using Replication Manager requires theuse of Business Continuity Manager 6.2 or later - earlier releasesonly support data collection.If you manage copy pairs using the HyperSwap function, ordefine a consistency group consisting of one copy group andanother created using CCI, the following hardware/softwareversions are required:• VSP G1000: v8.0.0 or later• VSP G1500, VSP F1500: v8.5 or later• VSP: v6.1.1 or later• USP V/VM: v6.3 or later

Mainframe Agent Used to collect information about hosts and storage systems.In conjunction with Mainframe Agent, Replication Managermonitors information about configurations and statuses of copypairs created by Peer to Peer Remote Copy (PPRC). For detailsabout Mainframe Agent, see the Hitachi Command SuiteMainframe Agent Installation and Configuration Guide.


Note: Do not perform concurrent operations from other applications(including Business Continuity Manager) on volumes, copy groups, or copypairs that are the target of running (or scheduled) tasks. Doing so mightresult in an error.

Mainframe Agent versus BCM Agent

Mainframe Agent is installed on a pair management server and allowsReplication Manager to monitor mainframe pairs. BCM Agent is installed aspart of Business Continuity Manager and enables Replication Manager tomanage mainframe pairs. In effect, Business Continuity Manager replacesMainframe Agent, with BCM Agent acting as a link with Replication Manager.

• If you are adding Business Continuity Manager to your storageconfiguration, and instances of Mainframe Agent are already configured, itis not necessary to remove them.

• If you are setting up a new configuration with Business ContinuityManager and Replication Manager, there is no need to install MainframeAgent.

• If you are replacing an instance of Mainframe Agent with BusinessContinuity Manager, we recommend removing the Mainframe Agent first.

Prerequisites for managing copy pairs on mainframe systems usingCCI

With Hitachi VSP, VSP G1000, VSP G1500, and VSP F1500 systems, you canmanage volumes and copy pairs on mainframe systems using CCI. In thiscase, you must use the views and the Pair Configuration wizard for opensystems. The prerequisites are as follows:

• The copy pair must consist of TrueCopy Sync or Universal Replicator.• Multi-target and cascade configurations cannot be used.• Neither a virtual command device nor a device group is used.• The copy pair is not simultaneously managed by CCI and Business

Continuity Manager. That is:

¢ A copy pair managed by Business Continuity Manager is not defined inthe configuration definition file of CCI.

¢ No volumes that consist of a copy pair in a mainframe systemmanaged by CCI are scanned by Business Continuity Manager, andBusiness Continuity Manager is not aware of LDEVs that comprise thesame copy pair.

¢ The value of server.agent.rm.centralizePairConfiguration in theserver.properties file of Device Manager Agent must be set toenable. For details, see the Hitachi Command Suite AdministratorGuide.


Prerequisites for data migration using virtual IDs (VSP and HUS VM)If a volume is a VSP or HUS VM storage system and belongs to a resourcegroup used for a data migration function that uses virtual IDs, ReplicationManager can display the physical IDs and define pair configurations byspecifying the physical IDs. However, the following functions are notavailable:

• Displaying virtual ID• Settings of storage system (command device, pool volume, and journal

group)• Managing replicas

The prerequisites for defining or managing such a configuration are asfollows:

• Copy pairs must be configured in such a way that they are managed withthe central management method.

• The configuration definition file must be re-created to match the migratedenvironment.

• Authentication mode is e/nabled for the command device assigned to apair management server.

• Fulfill the requirements described in Device Manager Agent and userauthentication on page 2-20.

For details about the central management method and the configurationdefinition file, see the Hitachi Command Suite Administrator Guide.

Prerequisites for nondisruptive migration (VSP G1000, VSP G1500,VSP F1500, VSP Gx00 models, or VSP Fx00 models)

The prerequisites for defining or managing such a configuration are asfollows:

• If you are using physical IDs, copy pairs must be configured in such away that they are managed with the central management method.

• A volume migrated using nondisruptive migration should be managedusing a virtual ID.

• The configuration definition file from the old storage system must be re-created to match the environment to which you are migrating. When themigration is complete and the copy pairs are functional, do not makefurther changes to the configuration definition file.

• If you are using physical IDs, authentication mode must be enabled forthe command device assigned to the pair management server.

• Check the conditions described in Device Manager Agent and userauthentication on page 2-20.

WARNING: Do not attempt to create a copy pair if all the followingconditions are true:

• The Device Manager Agent version is v8.0.0.


• The CCI version is earlier than 01-32-03/xx.• The physical and virtual storage machines that share the same serial

numbers and LDEV IDs coexist and the storage machines do not coexistin one LDEV.

Virtual ID and resource group limitations

If the storage system is VSP G1000, VSP G1500, VSP F1500, VSP Gx00models, or VSP Fx00 models and the volume belongs to a resource groupmigrated using virtual IDs, then Replication Manager can display the physicaland virtual IDs and define copy pair configurations. However, the followingfunctions are not available:

• storage system settings

¢ command device¢ pool volume¢ journal group setting¢ remote path

• CTGID• snapshot group• device group

Device Manager Agent and user authentication

User authentication is automatically performed if all the following conditionsare satisfied:

• The Device Manager Agent version is v8.0.1 or later.• SSL communication is established between the Device Manager server

and Device Manager Agent.

If these conditions are not satisfied, perform the user authenticationmanually:

1. If the pair management server OS is Windows, change the log on accountof the Device Manager Agent service to an Administrators group account.

2. If the pair management server OS is Windows, log on as the log onaccount of the Device Manager Agent service. If the pair managementserver OS is Linux, log in as a root user.

3. Use the CCI command (raidcom –login) to perform user authentication.

Virtual IDs and Device Manager Agent and CCI versions

We recommend using the following software versions if you plan to usevirtual IDs:

• Device Manager Agent v8.0.1 or later• CCI 01-32-03/xx or later


If the CCI version is 01-32-03/xx or later, the following conditions apply:

• The virtual ID needs to be specified for HORCM_VCMD. If a commanddevice is defined in HORCM_CMD, you need to review the configurationdefinition file whenever you upgrade CCI.

• If you plan to use both physical and virtual IDs, create separateconfiguration definition files for each.

Application Agent support for virtual IDs and virtual storagemachines

Application Agent supports the following configurations using virtual IDs andvirtual storage machines.

For local copy: A copy pair consisting of volumes in one virtual storagemachine configured in one physical storage machine.

For remote copy:

• A copy pair consisting of volumes in one virtual storage machineconfigured in multiple physical storage machines.

• A copy pair consisting of a physical storage machine and a virtual storagemachine configured in another physical storage machine (for storagesystems supporting virtual storage machines).

Caution: Take note of the following:

• If you migrate data using nondisruptive migration, any existing backupcatalogs are no longer valid. After the migration is complete, re-createthe dictionary map file as described in the Hitachi Command SuiteReplication Manager Application Agent CLI User Guide and run a newbackup.

• If an LU that is a target of Application Agent commands is recognizedusing a virtual ID by the host, and the LU is defined in the configurationdefinition file of CCI using a physical ID, the Application Agent commandsmight terminate abnormally.

Prerequisites for managing global-active device copy pairsThe following table describes prerequisites and precautions for GAD copypairs.

Settings Requirements

Storage system • The physical storage system is VSP Gx00 models, VSPG1000, VSP G1500, VSP Fx00 models, or VSP F1500.

• Remote paths are set in both directions.• A quorum storage system that has a common Quorum Disk

ID is connected externally to both primary and secondarystorage systems.

• Check the conditions described in Virtual IDs and DeviceManager Agent and CCI versions on page 2-20.


Settings Requirements

• Check the conditions described in About adding a copygroup to an existing GAD pair on page 2-22.

About adding a copy group to an existing GAD pair

When you add a copy group to an existing copy pair, it is known as a multi-target configuration when created on the primary side and a cascade on thesecondary.

If you are adding a copy group to an existing global-active device copy pair,the following conditions must be met:

• The copy type is ShadowImage or Thin Image.• If primary and secondary storage systems used by a global-active device

pair are managed by one pair management server, you cannot use thevirtual IDs of the virtual storage machine. To use virtual IDs, you mustconfigure a separate pair management server for each storage system.

WARNING: Application Agent does not support multi-target and cascadeglobal-active device configurations.

Prerequisites for managing copy pairs using snapshot groupsIf a volume is a VSP, VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models,VSP Fx00 models, or HUS VM, Replication Manager can manage copy pairsusing 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 asfollows:

• Authentication mode is enabled for the command device assigned to apair management server.

• Check the conditions described in Device Manager Agent and userauthentication on page 2-20.

Mainframe pairs and Device Manager AgentBeginning with v7.4.0, Replication Manager supports configurations in whichmainframe system pairs are managed by Device Manager Agent. As withopen system pairs, the status of a pair managed through Device ManagerAgent is acquired from the Replication Manager Agent instance on therelevant pair management server. The information that can be acquired is thesame as for open system pairs.


Configurations for mainframe monitoringAs of release 6.3, Replication Manager supports monitoring of IBMenvironments (z/OS, z/VM, z/VSE and z/Linux) and non-IBM environmentsusing only Device Manager (without Business Continuity Manager orMainframe Agent installed). Replication Manager retrieves the status ofTCS/TCA/SI, as well as UR copy pairs directly from storage systems, withoutdepending on mainframe host types. The minimum interval of automaticrefresh for this configuration is 30 minutes.

Tip: The status of FC and XRC copy pairs are not supported at this time.

Virtual command device requirements for managing copy pairsThe requirements are as follows:

• The configuration information is being updated using the same HORCMfile that was used to set up the virtual command device.

• If you plan to use a virtual command device server as a virtual commanddevice, you must start a transition instance of CCI on the server.

• User authentication of the command device is either disabled, or enabled(and performed manually if necessary).

• If you plan to specify the HORCM_ALLOW_INST parameter in theconfiguration definition file on the virtual command device server, thefollowing conditions apply:

¢ The default port must be used as the CCI initiator port of the pairmanagement server.

¢ The port number must be specified for each pair management serveras described in Specifying port numbers for pair management serverson page 2-25

The following related considerations apply to using virtual command devicesto manage copy pairs:

• User authentication for virtual command devices on page 2-23• Monitoring volume or journal usage rates on page 2-24• CCI command response time on page 2-24

User authentication for virtual command devices

If the following conditions are true, user authentication needs to becompleted using 01-25-03/01 or later version of CCI prior to startingoperation:

• The storage system is VSP G1000, VSP G1500, VSP F1500, VirtualStorage Platform, or HUS VM and an SVP is used as a virtual commanddevice.


• The storage system is VSP Gx00 models, or VSP Fx00 models and aserver that provides functions of storage system management is used asa virtual command device.

• User authentication is enabled for the device.

User authentication is automatic when these two conditions are satisfied:

• The Device Manager Agent version is v8.0.1 or later.• SSL communication is established between the Device Manager server

and Device Manager Agent.

When the above conditions are not satisfied, you must perform userauthentication manually as follows:

1. If the pair management server OS is Windows, change the log on accountof the Device Manager Agent service to an Administrators group account,and then log on.If the pair management server OS is Linux, log in as a root user.

2. Use the CCI command (raidcom -login) to perform user authentication.

Monitoring volume or journal usage rates

If plan to monitor journal volume usage rate or pool volume usage rate ofVSP G1000, VSP Gx00, VSP Fx00, VSP, USP V/VM, or HUS VM storagesystems, one of the following conditions must be satisfied:

• The host or virtual command device server connected to the commanddevice of the storage system is recognized by Replication Manager.

• The system is configured for managing device groups.

Note: The configuration information is not updated even if adding orchanging a configuration definition file updates information of a newly addedstorage system.

CCI command response time

When you manage copy pairs using a virtual command device, the CCIcommand takes longer to respond than with a physical command device.

To prevent possible timeout errors from Device Manager Agent, werecommend the following property file settings:

Device Manager Agent

• Set the server.atent.rm.moduleTimeOut property in theserver.properties file to 1800 or greater.

• Set the agent.rm.TimeOut property in the agent.properties file to1800 or greater.

Replication Manager

• Set the hdvmagtif.MaxPollingCount property in theagentif.properties file to 100.


• Set the hdvmagtif.PollingInterval property in theagentif.properties file to 60 or greater.

For details about editing property files, see Properties related to ReplicationManager on page 5-5. After changing property files, you must restartReplication Manager as described in Starting and stopping ReplicationManager on page 5-2.

Specifying port numbers for pair management servers

The port numbers that depend on Device Manager Agent version and CCIversion must be specified for each pair management server as shown in thetable below.

For details on instance numbers of HORCM files for monitoring, see theHitachi Command Suite Administrator Guide.

Condition Port numbers for each pair management server

Device ManagerAgent version CCI version Port numbers Default values

v8.1.0 or later 01-32-03/xx orlater

instance-number to instance-number - (range -1)Where:• instance-number is the value specified for

the Device Manager Agent propertyserver.agent.temporaryInstance(default value: 2047).

• range is the value specified for the DeviceManager Agent propertyagent.rm.horcmRange (default value: 100).

Note: You do not need to set any instancenumbers you want to reject.

1948 to 2047

Earlier than01-32-03/xx

instance-number and instance-number -1Where instance-number is the value specifiedfor the Device Manager Agent propertyserver.agent.temporaryInstance (defaultvalue: 4094).

4094 and 4093

v8.0.1 01-32-03/xx orlater

Earlier than01-32-03/xx

instance-numberWhere instance-number is the value specifiedfor the Device Manager Agent propertyserver.agent.temporaryInstance (defaultvalue: 4094).

4094

v8.0.0 All versions

Configurations for replica managementThe following figures depicts composite configuration where copy pairs andapplication replicas are managed. The system components (hosts) are labeledwith both the pair management terms (example: pair management server)and the replica management counterpart (example: backup server):


• Figure 2-9 Example system configuration managing copy pairs andapplication replicas (Exchange) on page 2-26

• Figure 2-10 Example system configuration managing copy pairs andapplication replicas (SQL Server) on page 2-27

Note: In this document, creating a replica or backup refers to creating areplica using Application Agent.

Figure 2-9 Example system configuration managing copy pairs andapplication replicas (Exchange)


Note: Only TCS is supported for creating a remote copy.

Figure 2-10 Example system configuration managing copy pairs andapplication replicas (SQL Server)

Note: Depending on the configuration, backup servers are not required forSQL Server configurations.

Components for replica management

The following tables describe the system components that are unique toreplica management and their counterparts to pair management:

• Table 2-5 System components (for replica management) on page 2-28


• Table 2-6 Overview of mandatory software (for replica management) onpage 2-28

Table 2-5 System components (for replica management)


Database server Application Agent A host where Exchange or SQL Serveris installed. Application Agent isinstalled on the database server.

Backup server Application Agent A host where the secondary volumesare located. Application Agent is alsoinstalled on the backup server.

Table 2-6 Overview of mandatory software (for replica management)


Application Agent Allows Replication Manager to perform database backup andrestore operations. The agent internally manages therelationships between backup objects and their associatedlogical units within the storage systems, the relationshipsbetween primary and secondary volumes, and the backuphistory.

VSS provider:RM Shadow Copy(Exchange only)

Installed as part of Application Agent, VSS is used to create,restore, and verify Exchange database replicas (snapshots).Application Agent requires two servers (one database server andone backup server) to back up Exchange data. The databaseserver can manage the primary volumes. The backup serverimports VSS snapshots and verifies the Exchange database.

Replication Manager in standby configurationTo prepare for disaster recovery, you can install Replication Manager on amanagement server at the standby site and leave it operating in maintenancemode. Should the primary server fail, the standby server can be brought intoservice by taking it out of maintenance mode. For details about how to setmaintenance mode, see the Hitachi Replication Manager User Guide.


Figure 2-11 Standby Replication Manager (multi-platform, multi-siteconfiguration)

System limitsThis section describes limits that apply to the clients, hosts, and servers thatcomprise a Replication Manager system.

Resource LimitsThe maximum number of resources that can be managed by ReplicationManager depends on the memory heap size (Small, Medium, or Large). Setan appropriate memory heap size, depending on the maximum number foreach resource.

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 HitachiCommand Suite Installation and Configuration Guide.

This section discusses the following:

• Maximum number of copy pairs on page 2-30• Maximum number of LDEVs on page 2-31• Log data and number of copy pairs on page 2-31


Note: Mainframe system resources managed by CCI must be managed asopen system resources. See Prerequisites for managing copy pairs onmainframe systems using CCI on page 2-18 for more information.

Maximum number of copy pairsThe following table shows the maximum number of copy pairs.

Table 2-7 Maximum number of copy pairs that can be managed

EnvironmentNumber of copy pairsby memory heap size

Small Medium Large

Open systems only 6,000 12,000 24,000

Mainframe systems only 40,000 60,000 90,000

Combined open and mainframe1 40,000 60,000 90,000

Notes:

1. Use this formula to determine the number of copy pairs:(number-of-copy-pairs-for-open-systems * 6) + number-of-copy-pairs-for-mainframe-systems

Note: In consideration of response time and memory usage, the maximumnumber of both open and mainframe pairs that can be operated on by thePair Configuration Wizard at one time is 1,000. In the case of a mainframesystem, when operating a copy group or consistency group that includes25,000 or more copy pairs, specify Medium or Large for the memory size.

Number of copy pairs on open systems

If the number of copy pairs is 5,000 or more, edit the following DeviceManager 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 “Managing copy pairs”chapter in the Hitachi Command Suite Administrator Guide.

Number of copy pairs on mainframe systems

Among the number of copy pairs managed by Device Manager server and thenumber of copy pairs managed by Business Continuity Manager, confirm thatthe larger number of copy pairs is less than or equal to the value shown inTable 2-7 Maximum number of copy pairs that can be managed on page2-30.


Maximum number of LDEVsThe maximum number of manageable LDEVs is based on the total number ofLDEVs in all managed storage systems. The following table shows themaximum number of LDEVs.

In an environment where there are multiple sources for LDEV informationacquisition, confirm that the total number of LDEVs acquired from eachinformation acquisition source is less than or equal to than the maximumnumber. In an open system environment, when the memory heap size isSmall or Medium, the maximum number is the total number of LDEVsacquired from both the local and remote instances of Device Manager. Whenthe memory heap size is Large, the maximum number differs for the LDEVsacquired from the local and remote instances of Device Manager.

Table 2-8 Maximum number of LDEVs that can be managed

EnvironmentNumber of LDEVs bymemory heap size

Small Medium Large

Open systemsonly

The LDEV informationacquisition source is alocal Device Manager

50,000 80,000 1,000,000

The LDEV informationacquisition source is aremote Device Manager

256,000

Mainframe systems only 80,000 120,000 200,000

Combined openand mainframe

The LDEV informationacquisition source is alocal Device Manager onthe open system

80,0001 120,0001 1,000,000

The LDEV informationacquisition source is aremote Device Manageron the open system

153,000

For the mainframe system 200,000

Note:

1. Use this formula to determine the number of LDEVs and confirm that thenumber is less than or equal to the maximum:(number-of-open-LDEVs * 2) + number-of-mainframe-LDEVs

Log data and number of copy pairsThe 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 sizefor each log file. For details, see logger.properties on page 5-8.


Firewall exceptionsIf a firewall is present, the port number for transmissions to and fromReplication Manager must be registered as an exception. The tables thatfollow describe the port numbers associated with each type of configuration:

• Table 2-9 Port numbers to register as firewall exceptions between themanagement server and management clients on page 2-32

• Table 2-10 Port numbers to register as firewall exceptions between theReplication Manager management server and remote Device Managermanagement server on page 2-33

• Table 2-11 Port numbers to register as firewall exceptions between themanagement server and the pair management server, or the host (opensystem) on page 2-33

• Table 2-12 Port numbers to register as firewall exceptions between themanagement server and the host (mainframe system) on page 2-33

• Table 2-13 Port numbers to register as firewall exceptions between themanagement server and the database or backup server on page 2-34

The number of each port can be changed. For details about how to changethe port numbers, see the following manuals:

• For port numbers used by Common Component, Device Manager server,and Device Manager agent: Hitachi Command Suite Administrator Guide

• For port numbers used by Business Continuity Manager: Hitachi BusinessContinuity Manager Installation Guide

• For port numbers used by Mainframe Agent: Hitachi Command SuiteMainframe Agent Installation and Configuration Guide

• For port numbers used by Application Agent, see Changing ApplicationAgent port numbers on page 4-21

Table 2-9 Port numbers to register as firewall exceptions between the managementserver and management clients

Port number Originator Destination Description

22015/tcp Management client Management server This port is used to access the HBase 64Storage Mgmt Web Service of CommonComponent when communicating with amanagement client. This port is requiredfor non-SSL connections.

22016/tcp Management client Management server This port is used to access the HBase 64Storage Mgmt Web Service of CommonComponent when communicating with amanagement client via SSL. This port isrequired for SSL connections.


Table 2-10 Port numbers to register as firewall exceptions between the ReplicationManager management server and remote Device Manager management server


2001/tcp ReplicationManagermanagementserver

Remote DeviceManagermanagementserver

This port is used to communicate withDevice Manager Server. It represents thevalue of the server.http.port propertycoded in the server.properties file forDevice Manager Server. This port is requiredfor non-SSL connections.

2443/tcp ReplicationManagermanagementserver

Remote DeviceManagermanagementserver

This port is used to communicate withDevice Manager Server via SSL. Itrepresents the value of theserver.https.port property in theserver.properties file for Device ManagerServer. This port is required for SSLconnections.

Table 2-11 Port numbers to register as firewall exceptions between the managementserver and the pair management server, or the host (open system)


24041/tcp24042/tcp

Management server • Pair managementserver

• Host (opensystem)

This port is used to communicate withDevice Manager Agent. It represents thevalue of the server.agent.portproperty in the server.properties filefor Device Manager Agent.

Table 2-12 Port numbers to register as firewall exceptions between the managementserver and the host (mainframe system)


24042/tcp Management server Host (mainframesystem)

This port is used to communicate withBusiness Continuity Manager (when IHSis not being used1), or Mainframe Agent.It represents the value in the TCP/IPenvironment settings file(PROFILE.TCPIP profile) for a mainframesystem.

Notes:

1. When IHS is used to communicate with Business Continuity Manager viaSSL, register the port number for IHS as a firewall exception.


Table 2-13 Port numbers to register as firewall exceptions between the managementserver and the database or backup server


24041/tcp24042/tcp

Management server • database server• backup server

This port is used to communicate withDevice Manager Agent. It represents thevalue of the server.agent.portproperty in the server.properties filefor Common Agent Component.

Table 2-14 Port numbers to register as firewall exceptions between the database serverand the backup server


22300/tcp • databaseserver

• backup server

• database server• backup server

This port is used to communicatebetween Application Agents. This is thevalue registered as DRMVSSServer in theWindows services file.

How Replication Manager collects dataThis section describes how data is acquired and the flow of processingbetween individual programs. The elements of the following diagram areexplained in the text that follows.

Data collection in open systemsThis section describes the data collection and flow of processing betweenprograms in open systems.


Figure 2-12 Data collection (open systems)

Acquiring configuration and license informationReplication Manager acquires the following information using DeviceManager 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 storagesystems, while Replication Manager stores information acquired fromDevice Manager server.Information for performing remote copy between multiple sites (inwhich a copy pair is defined between multiple Device Managerservers) is acquired using Device Manager Agent because thisinformation cannot be retained by Device Manager server.


Note: Replication Manager acquires configuration information fromthe Device Manager server at the following times:

• For a local Device Manager:The configuration management information displayed in eachwindow is acquired from Device Manager when each sourcemanagement window of Replication Manager is displayed. Youneed not manually refresh the system configuration informationbefore using Replication Manager to set up a storage system ordefine copy pair configurations.

• For a remote Device Manager, all configuration information isacquired when a configuration refresh is performed.

Acquiring copy pair statusesReplication Manager sends a request to Device Manager Agent, which inturn uses CCI to collect the status of copy pairs from the storage system.For a copy pair defined by the storage system (such as Storage Navigatorand Storage Navigator Modular), the status is acquired from DeviceManager server because the CCI configuration definition file is notavailable.

Acquiring performance informationReplication Manager issues a request to Device Manager Agent to acquireperformance information (such as the sidefile usage rate, pool volumeusage rate, and write delay time (C/T delta)). In turn, Device ManagerAgent uses CCI to obtain the data from the storage system.

Creating and deleting copy pairs and changing copy pair statusesReplication Manager issues a request to Device Manager Agent to createand delete copy pairs or to change the status of copy pairs. The DeviceManager Agent uses CCI to perform the operations on the storagesystem.

Data collection in mainframe systemsThis section describes the data collection and flow of processing betweenprograms in mainframe systems.


Figure 2-13 Data collection (mainframe systems)

Note: Although not shown in this simplified diagram, all requests forBusiness Continuity Manager from Replication Manager are handled by BCMAgent (which resides on the same host as BCM).

Acquiring and deleting copy pair configuration informationReplication Manager issues a request to Business Continuity Manager toacquire or delete copy pairs. BCM performs the operations on the storagesystem.

Acquiring and changing copy pair statusesReplication Manager issues a request to Business Continuity Manager orMainframe Agent, which acquires the status of copy pairs from thestorage system. (Only BCM can change the status.)

Acquiring performance informationReplication Manager issues a request to Business Continuity Manager orMainframe Agent to acquire performance information from the storagesystem (such as the sidefile usage rate, journal volume usage rate, poolvolume usage rate, and write delay time (C/T delta)). The journal volumeusage rate is acquired as described below.

Acquiring license information


To acquire license information for the volume replication functionality inmainframe systems, Device Manager server must be registered as aninformation acquisition source.Replication Manager obtains this license information from the DeviceManager database (acquired from the storage system).


3Setting up Replication Manager

This chapter explains how to set up and configure Replication Manager.

□ Overview

□ Concerning upgrade installations

□ Setting up the prerequisite environment

□ Adding a link menu to the GUI display

Setting up Replication Manager 3-1Hitachi Replication Manager Configuration Guide

OverviewThis 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 ofother Hitachi Command Suite products in use, on the management serverwhere Replication Manager is installed. For details about how to back updatabases, see the application product manuals.

2. Set up the necessary infrastructure as described in Setting up theprerequisite environment on page 3-3.

3. For a cluster environment, follow the appropriate procedure in the HitachiCommand Suite Installation and Configuration Guide before installingReplication Manager.

Note: After installing or updating Replication Manager, you must back up thenew configuration data.

Concerning upgrade installationsIf you are currently using Replication Manager v6.x or v7.x, you can upgradeto v8.x. For details about the upgrade installation procedure, see the HitachiCommand Suite Installation Guide. When the upgrade is complete, consultthe items that follow.

Items to be checked after upgrading Replication ManagerThe upgrade changes certain command names and default installationfolders. If you created any scripts that use the command names or file pathsshown in Table 3-1 Command names and file paths changed after upgrade tov8.x (Windows) on page 3-2 or Table 3-2 Command names and file pathschanged after upgrade to v8.x (Linux) on page 3-3, you should make thechanges indicated.

Table 3-1 Command names and file paths changed after upgrade to v8.x (Windows)

Item Before(v6.x or v7.x)

After(v8.x)

Hitachi Command Suite commoncomponent command names

hcmdsxxxx hcmds64xxxx

Hitachi Command Suite defaultinstallation folder

For x86:%ProgramFiles%\HiCommandFor x64:%ProgramFiles(x86)%\HiCommand

%ProgramFiles%\HiCommand

3-2 Setting up Replication ManagerHitachi Replication Manager Configuration Guide


After(v8.x)

Hitachi Command Suite commoncomponent default installationfolder

Hitachi-Command-Suite-installation-folder\Base

Hitachi-Command-Suite-installation-folder\Base64

Note: %ProgramFiles% and %ProgramFiles(x86)% are Windows environmentvariables.

Table 3-2 Command names and file paths changed after upgrade to v8.x (Linux)


After(v8.x)

Hitachi Command Suite commoncomponent command names

hcmdsxxxx hcmds64xxxx

Hitachi Command Suite commoncomponent default installationdirectory

Hitachi-Command-Suite-installation-folder/Base

Hitachi-Command-Suite-installation-folder/Base64

Note: For Linux, the upgrade process does not change the Hitachi CommandSuite default installation folder.

Setting up the prerequisite environmentThis section describes how to set up the necessary infrastructure forReplication Manager. You can follow the workflow figures or the detailedprocedures. Skip any task that has already been completed.

• Open systems environment on page 3-5• Mainframe systems environment on page 3-6• Application replica environment on page 3-8

The following figure is an overview of the configuration procedure for bothmainframe and open systems.


Figure 3-1 Infrastructure configuration workflow


Open systems environmentTo configure the required infrastructure for Replication Manager for an opensystem:

1. Install Hitachi Command Suite on the management server.For details, see the Hitachi Command Suite Server Installation Guide.

2. Add all resources (storage systems) to Device Manager that are to bemanaged by Device Manager and Replication Manager.For details about adding storage systems to Device Manager, see HitachiCommand Suite Help or the Hitachi Command Suite CLI Reference Guide.

3. Install CCI on the pair management servers.

¢ Ensure the pair management server recognizes the command devicein the target storage system.

¢ If the pair management server is equipped with more than one NIC,the Device Manager agent and CCI use the same IP address.

For details, see the relevant CCI manual.4. Install Device Manager Agents on the pair management servers.

After Device Manager Agents are installed, specify the informationrequired for using them. The setup procedure involves the specification ofCCI-related information (such as where to install Device Manager Agentor whether to use the central management method). Specify settingsappropriate to the environment. For details about how to install and setup Device Manager Agents, see the Hitachi Command Suite AdministratorGuide.

5. Configure Device Manager Agents by editing the properties file(s) that arestored on the pair management servers.

Note: If you have specified settings for CCI in step 4, you can skip step5.You need to modify the specific files as directed if any of the conditionslisted below apply to your configuration:

¢ CCI has been installed at a location other than the default location, or(when Windows is used) multiple instances of CCI and DeviceManager Agents have been installed on different drives.In the server.properties file, specify the CCI installation target inthe server.agent.rm.location property.

¢ The central management method is used for management of copypairs.In the server.properties file, specify enable in theserver.agent.rm.centralizePairConfiguration property.For details about the central management method, see the HitachiCommand Suite Administrator Guide.

After you edit the properties file, restart Device Manager Agents. Fordetails about how to edit the properties file, the specification rules, andhow to restart Device Manager Agents, see the Hitachi Command SuiteAdministrator Guide.


6. Install Device Manager Agents on the hosts.For details, see the Hitachi Command Suite Administrator Guide.

Note: Hosts can be added manually or by the Host Data Collector (HDC)

7. If there is any host on which Device Manager Agent has not beeninstalled, manually add the resource (host) to Device Manager.For details about how to add hosts in Device Manager, see HitachiCommand Suite Help or the Hitachi Device Manager Command LineInterface (CLI) User Guide.

8. Ensure that all of the conditions below are satisfied:

¢ The requirements (microcode and system configuration) forShadowImage or TrueCopy or other required storage system volumereplication functions must be satisfied. For details about therequirements and the configuration procedures, see the storagesystem documentation for the applicable storage system model.

¢ The storage systems to which the primary and secondary volumesbelong are registered as management targets of Device Manager, andthe applicable Device Manager server is registered as a ReplicationManager information source.

¢ The pair management server recognizes the command device in thetarget storage system.

¢ The primary and secondary volumes are recognized individually fromthe hosts.

¢ The serial numbers for all storage systems managed by DeviceManager are unique.

Mainframe systems environmentTo configure Replication Manager for a mainframe environment:

1. Install Hitachi Command Suite on the management servers.For details, see the Hitachi Command Suite Server Installation Guide. Ifnecessary, also see the following manuals:

¢ Hitachi Command Suite Administrator Guide¢ Hitachi Command Suite Help¢ Hitachi Command Suite CLI Reference Guide

2. Install Business Continuity Manager or Mainframe Agent on the hosts.

Note: Mainframe pair configuration requires Business Continuity Manager6.2 or later. Earlier releases only support monitoring functions.

3. After installation of Business Continuity Manager or Mainframe Agent, youmust specify the information required for linking with ReplicationManager.

4. You must configure BCM as follows:


¢ Set up RACF for user authentication¢ Specify the prefix and allocate datasets as follows for the definition

files:¢ For disk configuration definition files, allocate datasets whose name

includes a DADID¢ For copy group definition files, allocate datasets whose names include

a copy group name¢ If replicating datasets between sites, allocate the same name of the

datasets to these sites¢ If route lists and command devices are managed with BCM, allocate

datasets of BCM configuration files5. The following BCM setup operations need to be performed:

¢ Identify DADIDs and prefixes used by Replication Manager and specifythem as initialization parameters for BCM Agent

¢ Set up route lists and command devices to achieve either of thefollowing:(a) To retrieve or monitor C/T Delta with Replication Manager / BCM(b) To discover volumes or perform pair operation on remote DKCsusing local instances of BCM (when no BCM exists on the secondarysite)

¢ For the MODE initialization parameter of BCM Agent, specify EDIT (theinitial value is MONITOR). This allows the management of copy groupsfrom Replication Manager. (If a function that updates a definition orchanges a status is used when the startup mode is MONITOR, anYKY727E error occurs in BCM Agent.)

¢ The LOCK initialization parameter can also be set to manage conflictsbetween operations performed by Replication Manager and BusinessContinuity Manager.

Note: If you want to use an IPv6 connection or HTTPS (SSL)communication between HRpM and BCM, you must set up the IBM HTTPServer (IHS).

Note: Replication Manager does not support the multiple subchannel setsfunction. Prefixes that contain a definition file corresponding to one of thefollowing conditions cannot be managed:

• Copy group definition file with a setting for a subchannel set ID• Disk configuration definition file that includes a volume with a setting

for a subchannel set ID• Disk configuration definition file that includes a volume to which a

dummy DEVN has not been assigned (in the case of a Non Gen'edscan or a remote scan)

6. Ensure that all of the conditions below are satisfied:

¢ The requirements (microcode and system configuration) of thestorage system volume replication functionality (such as


ShadowImage or TrueCopy) are satisfied. For details about therequirements and the configuration procedures, see the storagesystem documentation for the applicable storage system model.

¢ The storage systems to which the primary and secondary volumesbelong are registered as management targets of Device Manager, andthe applicable Device Manager server is registered as a ReplicationManager information source.

¢ The primary and secondary volumes are recognized individually fromthe hosts.

¢ The serial numbers for all storage systems managed by DeviceManager are unique.

For complete information, see the Hitachi Business Continuity ManagerInstallation Guide and the Hitachi Business Continuity Manager User Guide,which include respective chapters on setting up and using the BCM withReplication Manager.

For Mainframe Agent, refer to the Hitachi Command Suite Mainframe AgentInstallation and Configuration Guide.

Application replica environmentTo configure the required infrastructure for Replication Manager forapplication (database) replica operations:

1. Install Hitachi Command Suite on the management server.For details, see the Hitachi Command Suite Server Installation Guide.

2. Install CCI on the pair management servers.For details, see the relevant CCI manual.

3. Install Device Manager Agents on the pair management servers.For details about how to install and set up Device Manager Agents, seethe Hitachi Command Suite Administrator Guide.

4. Install Application Agent on the hosts (database server and backupsserver).For details, see Chapter 4, Setting up Application Agent on page 4-1.

Adding a link menu to the GUI display In the GUI, you can register a link to any Web application or Web page(including links to Device Manager servers used as information sources).Registering links adds Links menu items to the Go menu in the global tasksbar area. To register or delete a link, execute the hcmds64link command, asfollows.

In Windows:Common-Component-installation-folder\bin\hcmds64link {/add|/delete} /file user-defined-application-file /user user-ID /pass password


In Linux:Common-Component-installation-directory/bin/hcmds64link {-add|-delete} -file user-defined-application-file -user user-ID-pass password

hcmds64link command optionsThe options for the command are shown in the following table.

Table 3-3 hcmds64link command options

Item Description

add Specify this option to add a link.

delete Specify this option to delete a link.

file user-defined-application-file

Specify the file (the user-defined application file) used toregister the link information.

user user-ID passpassword

Specify the user ID and password for logging in to ReplicationManager. Specify the user ID of a user who has the Admin(Replication Manager management) permission.

Creating a user-defined application fileIn the file specified for registering the link information, specify thatinformation 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-ENDThe following table describes the available options.

Table 3-4 Items specified in the user-defined application file

Item Description

@TOOL-LINK Start key for the user-defined application file. Thisitem is required.

@NAME registration-key-name This information is used as the registration key.Specify a name that makes the link informationunique, and use no more than 256 bytes. This itemis required.

@URL startup-URL Specifies the URL to be started in the GUI. Use nomore than 256 bytes. Note: In IPv6 environments,specify a host name instead of an IPv6 address.

@DISPLAYNAME display-name-in-links-dialog-box

Specifies the link name to be displayed in the Linksdialog box. Specify Unicode characters in the rangeU+10000 to U+10FFFF, using no more than 80


Item Description

characters. If you do not specify this item, the valuespecified in the @NAME line is used as the link name.

@DISPLAYORDER display-order-in-links-dialog-box

Specifies the order of values to be displayed in theLinks dialog box. Specify a value from -2147483648to 2147483647. Values specified here are displayedin ascending order in the Links dialog box.

@ICONURL icon-URL Specifies the location of the icon displayed besidethe link. Use no more than 256 bytes. In IPv6environments, specify a host name instead of anIPv6 address.

@TOOL-END Termination key of the user-defined application file.This item is required.

The user-defined application file is created in ASCII format. The only availablecontrol characters are CR and LF.

The following example shows the contents of a user-defined application file.@TOOL-LINK@NAME SampleApp@URL http://SampleApp/index.html@DISPLAYNAME SampleApplication@DISPLAYORDER 10@ICONURL http://SampleApp/graphic/icon.gif@TOOL-END


4Setting up Application Agent

This chapter describes the Replication Manager Application Agent, the systemrequirements, and how to install the software on backup servers anddatabase servers.

□ About Application Agent

□ Application Agent installation location

□ Application Agent and OS upgrades

□ Installing Application Agent

□ Adding Application Agent to the Windows Firewall Exception list

□ Application Agent and CCI

□ Settings for Application Agent in a cluster configuration

□ Requirements and precautions for volume configurations

□ Application Agent and Replication Manager log output

□ Changing Application Agent port numbers

□ Creating file system replicas

□ Starting and stopping the Application Agent Services

□ Setting error logging options for Application Agent

Setting up Application Agent 4-1Hitachi Replication Manager Configuration Guide

About Application AgentApplication Agent extends the functionality of Replication Manager to includeapplication awareness, which allows application resources to be managedusing the Replication Manager interface. Specifically, Application Agent allowsReplication Manager to create and restore replicas of MS Exchange and SQLServer databases. By linking Application Agent with DBMS products onapplication servers, the databases can be backed up and restored.

Application Agent internally manages the relationships between these backupobjects and their associated logical units within storage systems, therelationships between primary and secondary volumes, and the backuphistory. Application Agent also provides information to Replication Managerwhenever necessary.

The following describes how Application Agent controls other softwarecomponents:

• Application Agent pauses databases in storage systems to ensure reliablebackup operations.

• Using CCI, Application Agent backs up or restores volumes that havealready been operated on using the functions built into the storagesystems.

• Application Agent operates in conjunction with other backup managementproducts to perform tape backup and restore operations, such asNetBackup and Backup Exec.

Tip: Application Agent uses a command line interface (CLI) to communicatewith CCI, the Logical Volume Manager (Windows standard LDM), and otherbackup management products. Such products must be installed before usingApplication Agent.

Application Agent functionsApplication Agent has the following functions:

• Creating and restoring database replicas on page 4-2• Data management across storage systems on page 4-3• Managing generations on page 4-3

Creating and restoring database replicas

Application Agent creates and restores replicas of storage groups (databases)using the volume replication function in the storage system to perform high-speed disk-copying operations. A storage group is a group containing one ormore MS Exchange 2007 information stores. Storage groups can be used tomanage multiple information stores at the same time.

Note: Exchange 2010/2013/2016 does not use storage groups.

4-2 Setting up Application AgentHitachi Replication Manager Configuration Guide

MS Exchange databases contain the following two types of informationstores:

• Mailbox stores for saving received email messages, attachments, folders,documents, etc.

• Public folder stores for saving information shared among users (emailmessages, documents, MS Outlook custom forms, etc.)

Data management across storage systems

Application Agent allows you to back up and restore secondary volumes toand from a local site (the storage system where the primary volume resides)and a remote site (a storage system different from that of the primaryvolume).

Replication Manager can perform the following operations on a remote siteusing Application Agent:

• Back up and restore data• Re-synchronize a copy pair• Display resource information• Lock a copy pair• Mount or unmount a secondary volume

Managing generations

Application Agent can associate multiple secondary volumes with a singleprimary volume. (These secondary volumes are referred to as generations.)When selecting a secondary volume for a backup, you can either select itmanually or have Application Agent automatically rotate the volumes in thesame way that tape backups are re-used (local backups only). At the sametime, Application Agent allows you to lock the contents of certain secondaryvolumes and only use other (unlocked) secondary volumes for backups. Formore information, see the Hitachi Replication Manager User Guide.

Note: The number of generations supported by Application Agent depends onthe volume replication function used, but the procedures are the same.

User authorization for command execution

The following authorizations are required to execute Application Agentcommands:

• OS administrator permissions and administrator privilegesA user executing an Application Agent command must have localAdministrator authorization on the server on which the command is to beexecuted. In a Windows Server 2008 operating environment, the usermust also have OS administrator privileges. If the user does not have OSadministrator privileges, an error message appears, and commandexecution fails.

• Database access authorization


¢ When backing up an SQL Server database: When a user executes anApplication Agent command, Windows must first authenticate the userbefore gaining access to the SQL Server. A user must have sysadminauthorization to execute Application Agent commands for an SQLserver.

¢ When backing up an Exchange database: A user must be assigned tothe Enterprise Admins group or the Exchange Domain Servers groupof a domain to execute Application Agent commands.

WARNING: Do not use a Managed Service Account if Windows Server 2008R2 is the OS on the pair management server, database server, or backupserver. If a Managed Service Account is specified for one of the followingservices, errors might occur when Replication Manager operations are beingperformed:

• Application Agent Services (Protection Manager Service, HBsA Service)• SQL Server, SQL Server Agent, and other SQL Server-related services

(when running a service to create a replica for an SQL Server database)

Account for Application Agent Services

Before installing Application Agent, you must create an account that will beused to execute the Application Agent Services (a collective term for the CopyController 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.• It must have the following database access permissions:

For backing up an Exchange database: The account used to executeCommon Agent Service must belong to the Enterprise Admins group orExchange Domain Servers group in the domain.For backing up a SQL Server database: Application Agent accesses SQLServer using Windows authentication. Therefore, the account used toexecute the Common Agent Service must be registered as a member thathas a sysadmin fixed server role for SQL Server.

WARNING: Do not use a Managed Service Account if Windows Server 2008R2 is the OS on the pair management server, database server, or backupserver. If a Managed Service Account is specified for one of the followingservices, errors might occur when Replication Manager operations are beingperformed:

• Application Agent Services (Protection Manager Service, HBsA Service)• SQL Server, SQL Server Agent, and other SQL Server-related services

(when running a service to create a replica for an SQL Server database)


Environment variables

Do not specify HORCMINST or HORCC_MRCF in a system environment variable.Also, do not specify HORCM_CONF or HORCMPERM in a system or userenvironment variable.

HORCM options and CCI

HORCM_DEV, HORCM_LDEV, or HORCM_LDEVG need to be specified in theconfiguration definition files of CCI instances used by Application Agent.

If you are going to manage a copy group defined by device group,HORCM_LDEVG needs to be specified in both the P-VOL and S-VOLconfiguration definition files. (If you omit HORCM_LDEVG, the P-VOL might bedisconnected from the database server when you perform an ApplicationAgent operation.)

Make sure that there are no copy pairs consisting of disks that are notconnected to the server in the database server and the file server.

Copy pairs and backup/restore operations

A copy pair that is a target of backup and restore operation cannot beassigned as a network drive. The P-VOL of a file system that is a target ofbackup and restore operations needs to be mounted. For additional notesregarding pair configuration, refer to the requirements when using CCI toconfigure a pair volume documented in the Hitachi Command SuiteReplication Manager Application Agent CLI User Guide.

Application Agent versions on database and backup servers

The same version of Application Agent must be installed on database andbackup server pairs. Do not, for example, install version 6.3 on the databaseserver and 6.4 on the corresponding backup server.

Remote copy type support

Microsoft Exchange Server uses VSS to create replicas. Because VSS onlysupports TCS for remote copies, Replication Manager must use TCS to createremote replicas. (TCA and UR remote replicas are not supported. VSS doesnot allow the split time to exceed 10 seconds, and these copy types cannotmeet this requirement.)

Because Microsoft SQL Server does not use VSS (it uses VDI), there is nolimitation on the remote copy type for linkage with Microsoft SQL Server.TCS, TCA, and UR are also supported.

Replica operations between storage systems

Application Agent is compatible with TrueCopy and Universal Replicatorbackups to (and restorations from) remote site storage systems, for when afailure occurs on a local site storage system. Depending on the DBMS productlinked to, different volume replication functions can be used:


• Exchange Server: TrueCopy Sync• SQL Server: TrueCopy and Universal Replicator

For additional information, refer to the precautions on backing up andrestoring data between storage systems documented in the Hitachi CommandSuite Replication Manager Application Agent CLI User Guide.

Copy types supported for replica operation

The following system configurations can be used to perform backups andrestorations between storage systems:

• TrueCopy or Universal Replicator configurations (basic)• ShadowImage and TrueCopy multi-target configurations• ShadowImage and Universal Replicator multi-target configurations• TrueCopy and Universal Replicator multi-target configurations• ShadowImage (multiple generations), TrueCopy, or Universal Replicator

configurations

Dynamic recognition of secondary volumes

When a secondary volume is dynamically recognized, do not use the LUN#0disk among the physical disks that are connected to the device adapter portfor the primary and secondary volumes. When the physical disk of LUN#0 isused, other physical disks might not be recognized.

When reinstalling Application Agent

When Application Agent is removed, configuration files might remain. Beforere-installing Application Agent, you should manually delete the entiredirectory where Application Agent was installed.

Maximum number of Application Agent instances

The maximum number of Application Agent instances that can be registeredis 128.

SQL server log distribution function

The SQL Server log distribution function can be used when SQL Serverdatabases are backed up. To do this, there must be two servers; a serverfrom which to distribute the log files and a server to which to send the logfiles.

For this type of configuration, Application Agent must be installed on bothservers.


Windows services

Before you install Application Agent, use the Services pane in the ServerManager console to ensure that the Windows services are set to the defaultsettings as shown in the following table.

Table 4-1 Services and settings required for installation of VSS Provider

Service name Displayed name Prerequisite condition forstartup

RpcSs Remote Procedure Call (RPC) Automatic

EventLog Event Log Automatic

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 install RM Shadow Copy when these Windows services arenot set to their default settings, the VSS Provider service will not beregistered as a Windows service.

Cluster considerations

The following considerations apply to cluster support and operations:

• Application Agent supports both mutual standby cluster configurations(Active-Active) and operational standby cluster configurations (Active-Passive). However, For the cluster configuration, Replication Manager(Server) supports the “Active - Passive” configuration only.

• To restore backup data, the database must be taken offline. If a databaseis taken offline while the cluster resources that are monitoring thedatabase are still online, a failover will occur. This usually requirescontrolling control cluster resources manually. With Application Agent,cluster resources that monitor the database are automatically taken downand brought back online whenever Application Agent is used to perform abackup or restore operation for data.

• In a cluster environment using WSFC, you can choose whether to performa restore operation while the cluster resources that monitor the databaseare online or offline. For a restore operation in which the cluster resourcesare offline, you need to take all the databases that are using the databaseservices offline. However, for a restore operation in which the clusterresources are currently online, you only need to take the databases offlinethat 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 othercluster server to a backup server.

• Depending on the storage system type and features of the operatingsystem, you might not be able to perform a restore operation while thecluster is online.

Application Agent installation locationBy default, the Application-Agent-installation-folder is defined asfollows.

For Windows 32-bit edition:

%ProgramFiles%\HDVM\HBaseAgent\For Windows 64-bit edition:

%ProgramFiles(x86)%\HDVM\HBaseAgent\If Device Manager Agent is pre-installed separately, Application-Agent-installation-folder is defined as follows:

folder-specified-by-HDvM-Agent-installer\HBaseAgent

Caution: If Hitachi Command Suite Common agent component and DeviceManager agent are not installed on the computer when you start theApplication Agent installation, they are automatically installed as follows:

• The Common agent component is installed in the same location asdocumented for Application Agent

• The Device Manager Agent is installed in this location:Common-agent-component-installation-folder\mod\hdvm

If you want to specify an arbitrary folder for these installation folders, installthe components before you start the Application Agent installation.

Application Agent installation path restrictionsMake sure the paths used in the installation of Application Agent meet thefollowing requirements:

• For the download destination path, the installation path for ApplicationAgent, and the path specified in the environment variable %TMP%, do notuse a directory name that starts or ends with one or more spaces.

• For the path specified in the environment variable %TMP%, do not use adirectory name that includes the following characters:% ` & ^ ;

• For the download destination path for Application Agent, do not use adirectory name that includes the following characters:% `


• The installation path must be an absolute path consisting of 124 bytes orless (subject to program restrictions).

• Create a download-destination folder with access limited to users in theAdministrators group.

• The Application Agent installation file must be extracted to a new folderwith access limited to users in the Administrators group.

If you plan to install Application Agent on the management serverIf you plan to install Application Agent on the management server, you mustfirst do the following:

If Replication Manager is already installed on the managementserver:

1. Set the value of base.refreshdginfo.exec in the base.properties fileto 0.

2. Restart the Common Component service as described in StartingReplication Manager on page 5-2

3. Select all the remote Device Manager instances and execute RefreshConfiguration

4. Select all of the storage devices managed by the local Device Managerinstance and execute Refresh Storage System Information.

5. Install Application Agent on the management server.

If Application Agent is already installed on the management server:

1. Install Replication Manager on the management server.2. Set the value of base.refreshdginfo.exec in the base.properties file

to 0.3. Restart the Common Component service as described in Starting

Replication Manager on page 5-2.

Note: When base.refreshdginfo.exec is set to zero, Replication Managercannot manage copy groups defined in storage (device groups).

Application Agent and OS upgradesIf you plan to upgrade the OS, be sure to uninstall Application Agent first.After the upgrade is complete, be sure and install the version of ApplicationAgent that matches your upgraded OS. After installation is complete, create areplica (backup data) immediately. (Restoration of replicas created prior tothe OS upgrade might not work properly.)


Installing Application Agent

Note: Please refer to the Hitachi Command Suite System Requirements fordetailed system requirements for Application Agent.This procedure applies to both cluster and non-cluster configurations.

Before starting the installation, stop all running programs. For example,Exchange Server 2013/2016 includes services such as the Microsoft ExchangeHealth Manager service. You must stop all services associated with MicrosoftExchange Server or SQL Server prior to installing Application Agent.

Caution: Observe the following precautions regarding upgrades:

• After performing an upgrade installation of Application Agent, you shouldimmediately create a replica (backup) of your data. (Restoring a replicathat was created prior to the upgrade might fail.)

• If you perform an upgrade or overwrite installation of Application Agent,the existing setting of the Application Agent service is preserved, but thelogin account of the common agent component service (HBsA) might bereset to the default local system account. In this case, when theinstallation is completed, select HBsA Service from the WindowsServices dialog and then set the logon account of the service to anAdministrators group user.

To install the agent, follow this procedure:

1. Log on to Windows as a member of the Administrators group on each ofthe database and backup servers where you plan to install ApplicationAgent.

2. If you are installing from the integrated installer, insert the media.If you are installing from the GUI, proceed to step 4.

3. In the displayed window, click the Install button next to ReplicationManager Application Agent.If the window is not displayed, manually execute the installer(setup.exe). The Installer is stored in drive:/AGENTS/HRPM_APP.Proceed to step 7.

4. Open Replication Manager in a browser.5. Select Go - Download from the Global Tasks bar area and choose

Application Agent.6. After the download completes, execute the Application Agent installation

file and activate the Installshield Wizard.7. In the Welcome… dialog box, click Next.

The Start Copying Files dialog box appears.8. Enter the appropriate customer information in the User Name and

Company Name fields of the Customer Information window. Thenclick Next.

9. You will be prompted to choose a destination location in the DestinationLocation field in the next window. Use the Browse... button to navigateto your selection. Then click Next.


10. After selecting a destination, you are prompted to select the componentsto install or remove using Select Features. The choices are Componentfor SQL and Component for Exchange.

Note: If you plan to perform VSS backups, select to install theComponent for Exchange to install the Shadow Copy Provider. If theoption to install the Component for Exchange is not displayed, select toinstall the Component for SQL instead and then install the Shadow CopyProvider manually. (The Shadow Copy provider is bundled with theComponent for Exchange.) For information on installing the ShadowCopy Provider, see the CCI documentation.

11. Confirm your installation choices and click Next.12. You will be prompted to choose a destination location in the Destination

Folder field in the Choose VSS Provider Destination window. Use theBrowse... button to navigate to your selection. Then click Next.

13. You will now be prompted whether you would like to register theApplication Agent to the allowed program configuration of your firewall inorder for the agent to work while that firewall is activated. Select the Yesor the No button in the Windows Firewall Settings window to set yourchoice. Then click Next.

14. The Start Copying Files window appears, allowing you to review yoursettings before proceeding with the file copying. Review the settings. Ifyou wish to change any, use the Back button. If you are satisfied withthe settings, click Next to begin copying files.

15. The Setup Status window appears, displaying the progress of theoperation.

16. The Replication Manager - Application Agent Setup window appears.Enter the User name and Password in the respective fields, for anaccount that has Administrator permissions and the “Log on as a service”permission and click Next.

17. You are asked if you wish to setup the Device Manager agent. If youchoose Yes, follow the instructions for installation and configuration ofthe HDvM agent as described in the Hitachi Command Suite Installationand Configuration Guide.

18. When the installation finishes, restart Windows.

Note:

• If the Application Agent is installed on a host without a databaseapplication installed, Replication Manager will fail in any attempts toobtain information by refreshing the host. If this occurs, one of thefollowing error messages is displayed:RPM-11004 - The specified SQL instance name is invalid orno SQL instance settings exist.RPM-11509 - Exchange Server has not yet been installed onthis system.

• Replication Manager identifies the database application running oneach 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 correspondingdatabase application installed.

• If an inappropriate version of Application Agent is installed on aserver, Replication Manager will fail to collect information duringRefresh Host processing and display an error message.

Adding Application Agent to the Windows Firewall Exceptionlist

Note: This procedure is not required unless:

• You selected not to add the exceptions when prompted during theApplication Agent installation (or the process of adding the exceptionsfailed).

• 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. Add the Copy Controller service to the list using this command:Application-Agent-installation-folder\DRM\bin\util\drmaddfwlist.bat

2. Add the Common Agent service to the list using this command:Application-Agent-installation-folder\bin\firewall_setup.bat -set

Application Agent and CCIThe following sections concern the interaction of Application Agent and CCI:

• Command line interface for CCI on page 4-12• Protection function of CCI on page 4-13• Using CCI to configure pair volumes on page 4-13• Device Manager and CCI on page 4-13• Starting and stopping CCI instances on page 4-13

Command line interface for CCINote the following precautions regarding using the CCI command lineinterface:


• Do not use the CCI command line interface while carrying out replicaoperations from Replication Manager.

• If you use the CCI command line interface to change a copy pairconfiguration, be sure and refresh the system from Device Manager,followed by updating the pair configuration and refreshing the hosts fromReplication Manager.

Protection function of CCIApplication Agent does not support the protection function of CCI. Thisfunction should be disabled on servers where Application Agent is installed.

Using CCI to configure pair volumesWithin a copy group, only include the pair volumes for one application. If thepair volumes of multiple applications are mixed together in one copy group,unintended backups and restorations might occur.

Device Manager and CCIFor CCI to be started on the database and/or backup servers automatically,Device Manager Agent needs to be installed on both servers.

If Device Manager Agent is not installed, you must manually start the CCIinstance on both the backup and database servers before carrying out replicaoperations. (If CCI is not started, the replica operation will fail.)

Starting and stopping CCI instancesCCI instances are necessary to execute Application Agent commands. Werecommend that you manually start both the CCI instance that manages theprimary volume and the instance that manages the secondary volume, priorto executing an Application Agent command.

Application Agent automatically starts and stops the instance only on the hostwhere you execute the command. If the instances are on different servers,you must start the following CCI instances manually prior to executing anApplication Agent command:

• When you execute the command on the database server or file server,start the CCI instance that manages the secondary volume

• When you execute the command on the backup server, start the CCIinstance that manages the primary volume

For more information, see the CCI documentation.

Configuring a system to back up an SQL Server databaseThe following items need to be considered to design a system to back up SQLServer database using Application Agent:


• All databases that coexist on a volume must be backed upsimultaneously. Store each database in an appropriate volume to meetyour backup plan.

• Due to the VDI quiesce operation, the drmsqlbackup command can onlyback up 64 databases in a single invocation. Use the drmsqlbackupcommand multiple times if you need to back up more than 64 databases.

For information on requirements and precautions for backing up SQL Serverdatabases or restoring an SQL Server database to an alternate location, seethe Hitachi Command Suite Replication Manager Application Agent CLI UserGuide.

Configuring a system to create Exchange Server database replicasThis section includes important information on creating Exchange Serverdatabase replicas using Application Agent. For additional information, see therequirements and precautions for backing up Exchange databases in theHitachi Command Suite Replication Manager Application Agent CLI UserGuide.

Installing the Exchange management tool

Install the Exchange management tool on the database and backup servers.(Ensure the same version is installed on both servers.) Refer to the ExchangeServer documentation for more details.

Using the ESEUTIL command

If you perform either of the following operations using the ESEUTILcommand, the electronic signature of the database is changed:

• Restoration of information store (ESEUTIL /p)• Defragmentation (ESEUTIL /d)

As a result, roll forward restoration is not available for replicas that createdbefore the operation. To correct this problem, you must recreate theExchange database replica using the Create Replica Wizard.

Settings for Application Agent in a cluster configurationThis section describes the steps necessary to configure replica operationsproperly in a cluster configuration. Application Agent provides a dedicatedcommand (drmjobsch.exe) for switching the target node. You must set upthis command in the cluster software so that it runs automatically when afailover occurs.

Verify the following before performing the appropriate procedure for thecluster software you are using:

• Application Agent and the cluster software have been installedsuccessfully.


• You have logged in as a member of the Administrators group.

Perform the following procedure on each server that makes up thevirtual server:

1. Create a VBScript file named RecoverJob.vbs in the following location:Application-Agent-installation-folder\DRM\scheduleYou can specify a different name and location for the VBScript file, but formaintenance reasons, we recommend that you use the above file nameand file storage location.

2. In the VBScript file, specify the recovery processing to be performed bydrmjobsch.exe. At the entry point Function Online( ), specify that thefollowing command is to be executed (where virtual-server-name is thename of a virtual server to be put online):Application-Agent-installation-directory\DRM\bin\drmjobsch.exe-recover -hostname virtual-server-nameSee Sample VBScript file on page 4-15 for a completed script. In theexample, Application-Agent-installation-folder is C:\ProgramFiles\HITACHI\DRM.

3. Use the Failover Cluster Management wizard to add the new resource tothe cluster resource group with the name virtual-server-name (such asa cluster resource group for Exchange Server).Resource type: Generic scriptScript file path: Path name of the created VBScript fileIf the VBScript file is stored on a shared disk for nodes, be sure andregister this shared disk as a physical disk resource in the Resourcedependencies field in the Dependencies dialog box.

Sample VBScript file

Note: CHR(34) indicates a double quotation mark ("). When ApplicationAgent-installation-folder does not contain any spaces, you do not needto specify CHR(34). The following is the specification when there are nospaces:"C:\drm\bin\drmjobsch.exe" & " -recover -hostname virtual-server-name"For details on the specification method, consult your VBScript documentation.'Script-Level Global VariablesResource.LogInformation("Script-wide code begins execution")Dim WshShell, oExecSet WshShell = CreateObject("WScript.Shell")Function Online( )Online = 0Resource.LogInformation "Entering Online"Set oExec = WshShell.Exec (CHR(34) & "C:\Program Files\HITACHI\drm\bin\drmjobsch.exe" & CHR(34) & " -recover -hostname virtual-server-name")Do While oExec.Status = 0Set oWait = WshShell.Exec("timeout /t 1")LoopResource.LogInformation "Exiting Online"


End FunctionFunction Offline( )Offline = 0End FunctionFunction LooksAlive( )LooksAlive = 0End FunctionFunction IsAlive( )IsAlive = 0End FunctionFunction Open( )Open = 0End FunctionFunction Close( )Close = 0End FunctionFunction Terminate( )Terminate = 0End Function

Unsupported cluster configurationApplication Agent supports operation-standby or mutual-standby clusterconfigurations. However, the following configuration is not available:

One node of the cluster configuration is assigned as file server or databaseserver, and the other node is assigned as backup server.

For details about operation-standby or mutual-standby cluster configurations,refer to the Hitachi Command Suite Replication Manager Application AgentCLI User Guide.

Creating SQL Server replicas in a cluster configurationNote the following:

• Do not register multiple resources of SQL Server instances in a clustergroup.

• In a cluster configuration, the owner of backup target database must be adomain user that is recognized by both nodes. A local user of a node isnot handled the same as a user of another node (even if the user nameand password are identical). If the cluster system fails over to a node thatdoes not recognize the owner, the database backup fails.

• Install the SQL Server instance as a failover cluster.

Creating Exchange Server replicas in a cluster configurationNote the following:

• Do not register multiple instances of Exchange resources in a clustergroup.

• If you restore a backup to a node other than the one where it wascreated, the Exchange virtual server that uses the same shared drivemust be running.


Exchange Server 2007 in Windows Server Failover ClusteringWhen you back up the database, all Exchange System Attendant andExchange Information Store resources belonging to the cluster resourcegroup must be online. If the resources are offline, the drmexgbackup orEX_DRM_EXG_BACKUP commands will terminate with an error. Do not apply asetting that takes an Exchange Information Store resource offline when therelevant cluster resource goes offline.

Requirements and precautions for volume configurationsThis module describes the requirements and precautions for volumeconfigurations when Application Agent is used:

• Volume configurations usable by Application Agent on page 4-17• Requirements for unmounting and mounting volumes on page 4-18• Requirements for backing up and restoring volumes on page 4-19• Precautions when changing a volume configuration on page 4-19• Precautions for disk partition styles on page 4-20

Volume configurations usable by Application AgentThe table below describes volume configurations that Application Agent canback up and restore. Application Agent supports only configurations whereone logical volume (partition) consists of one physical disk.

Table 4-2 Supported volume configurations

Logicalvolume

manager

Diskmanagement

method

Volume-configurationunit supported for back

up and restore

Location of database orfile to be backed up and

restored

LDM Basic disk(GPT)

Physical disk File system on a diskpartition

Note: Before using Application Agent, you must disable Automatic mountingof the new volume on the database server and the backup server. Performthe following procedure to check the current status and (if Automaticmounting of new volume is enabled) disable it:

1. Execute the diskpart command at the command prompt.2. Enter automount to display the current status.3. If Automatic mounting of new volumes enabled is displayed, enter

automount disable to disable the setting.4. Type exit to close diskpart.


Requirements for unmounting and mounting volumes• When executing backup and restoration of file systems and databases,

Application Agent mounts and unmounts the necessary volumes. Themount point directory name and path are dependent on the limitation forthe CCI mount or unmount functionality:

¢ When performing a disk backup: The limitation applies to the lengthof the path where the primary volume has been mounted (for whichcold backup operations are to be performed).

¢ When backing up to tape: The limitation applies to the length of thepath for the mounted volume. (This limitation also applies to thelength of the path for the secondary volume.)

• The limitations on folder names are the same as for Windows (no nullcharacters).

• One mount point can be specified for each logical volume.• Do not define the following as copy groups, and do not specify them as

backup targets: directories at a directory mount point, or volumesmounted to a drive.

• We recommend that you create directory mount points for backup targetson the same directory level (to make them easier to manage).The following shows a configuration example of a mounted directory thatis a suitable backup target. Data files and log files are mounted to adirectory and specified as backup targets.

Figure 4-1 Example of a suitable backup target (mounted directory)

The following shows a configuration example of a mounted directory that isnot a suitable backup target. When the configuration places a mount pointdirectory on a directory below a volume, higher-level volumes that containmounted volumes cannot be specified as a backup target.


Figure 4-2 Example of an unsuitable backup target

Requirements for backing up and restoring volumes• Do not use any functions for expanding or reducing the capacity of a

logical volume. If you use such functions, Application Agent will notperform backup and restoration correctly. This is because the number ofphysical volumes that make up the logical volume changes according tothe change in capacity of the logical volume. Application Agent checkswhether the configuration of logical volumes has been changed and, ifchanged, restoration terminates with an error.

• If the volumes to be processed by Application Agent contain an LDEV forwhich a mode other than the normal mode is specified for the access levelby using Data Retention Utility, neither a backup nor a restoration can beperformed.

• Do not perform a backup to the primary volume for which the shadowcopy functionality for the Windows shared folder is enabled or to theprimary volume that was specified as a storage area for shadow copy. Ifbackup is performed to these volumes, data consistency cannot beguaranteed.

• Allocate database files and file systems that are not subject to backup andrestoration so that they are not included on the same disk as those thatare subject to backup and restoration.

• Allocate database files and file systems that are backed up simultaneouslybut can be restored separately so that they are not included on the samedisk as those that are subject to backup and restoration.

Precautions when changing a volume configuration• If the following operations or changes are performed on a logical volume

manager that is a backup operation target, or on a file system or CCIconfiguration definition file (horcmn.conf), then update the dictionarymap files before executing the backup:

¢ A new file system was mounted on a directory under the file system.


¢ A file system was unmounted.¢ A file system was moved to another directory and mounted.¢ A change was made in the CCI configuration definition file

(horcmn.conf), such as adding or deleting a pair volume.

Note: If you execute backup without updating the dictionary mapfiles, a system inconsistency might occur. To update the dictionarymap files, use the drmfsdisplay, drmsqldisplay, or drmexgdisplaycommands. For details about how to use these commands, see theHitachi Command Suite Replication Manager Application Agent CLIUser Guide.

• If you made changes to a configuration involving an update of thedictionary map files, to restore the data backed up before the change to afile server or database server, first restore the configuration for the logicalvolume manager and file system to the state that was in place at the timethe backup was created, and then perform restoration. If you performrestoration incorrectly, a system inconsistency might occur. To review theconfiguration that was in place at the time the backup was created, usethe drmfscat, drmsqlcat, or drmexgcat command. For details about howto use these commands, see Hitachi Command Suite Replication ManagerApplication Agent CLI User Guide. For details about restoration when aphysical volume is replaced, see the section that mentions aboutreplacing primary and secondary volume disks while Application Agent isrunning in the Hitachi Command Suite Replication Manager ApplicationAgent CLI User Guide.

Precautions for disk partition styles• After performing a backup, disk partition styles cannot be modified. When

replacing a disk, the new disk must have the same partition style as whenthe backup was performed.

• If the partition style was changed after the backup was performed, andyou execute the restore command (drmfsrestore, drmsqlrestore, ordrmexgrestore), or you execute the drmdevctl command with either the-sigview or -sigset option, the operation might end with an error. Inthis case, change the partition style to the one in use when the backupwas performed.

• When the backup target is being managed in a cluster configuration, thedisk signatures for the primary and secondary volumes must be the sameas when the backup was performed. To view the original backupsignatures, execute the drmdevctl command with the proper backup IDand the -sigview option.

Application Agent and Replication Manager log outputThe number of Application Agent instances in your storage configuration mustbe considered when configuring the amount of log output, as described inAbout Replication Manager log output on page 5-11.


If the number of target Application Agent instances exceeds 30, you need totune the file capacity and number of files as follows:

Trace log size = current-file-capacity + 2.6 * number-of-Application-Agentinstances

Database log size = current-file-capacity + 0.5 * number-of-Application-Agent instances

Application status log size = current-file-capacity + 3.8 * number-of-Application-Agent instances

Changing Application Agent port numbers

Tip: The port number used for communication between Application Agentinstances (backup and database servers) can be changed during ApplicationAgent setup (the default is 22300). If this port number has already beenused, you must register the port number into the Windows Services file asDRMVSSServer.

You can change the port numbers used by the Agent daemon, the APIresponse process, and communication with the API response process, byediting the server.properties file on the backup and database servers. Thefile is stored in the following location.

For 32-bit Windows:%ProgramFiles%\HDVM\HBaseAgent\config\server.properties

For 64-bit Windows:%ProgramFiles(x86)%\HDVM\HBaseAgent\config\server.properties

The properties and default values are listed in the following table.

Table 4-3 Port numbers in server.properties file

Property Default value (portnumber) Purpose

server.agent.port 24041 Port number for theCommon agent daemonprocess (service).

server.http.port 24042 Port number for thecommunication between theCommon agent daemonprocess and the web serverprocess.

server.http.localPort 24043 Port number for Commonagent Web server.

Note the following:

• Acceptable port number values are 1-65535.


• Avoid using small port numbers because such numbers might conflict withother applications.

• The port numbers set in the server.properties file must be unique andcannot be shared by any other processes.

• If you change the value of server.agent.port, you must also change theport number for Application Agents registered as information sources.

• After changing these values, the Common Agent Service must berestarted.

Creating file system replicasFor important information on creating file system replicas using ApplicationAgent, see the requirements and precautions for backing up file systems inHitachi Command Suite Replication Manager Application Agent CLI UserGuide.

Starting and stopping the Application Agent ServicesTo use Replication Manager to perform a backup, the Application AgentServices must be running on both the database server and the backup server.For details, see Starting and stopping Replication Manager on page 5-2.

The services associated with Application Agent are normally started andstopped automatically on the database or backup server where the agent isinstalled. Should you need to start or stop them manually, use the commandsdescribed in the sections that follow (Administrator privileges are required).

Copy Controller serviceTo start or stop the Copy Controller service, launch the service screen ofServer Manager and start or stop the Protection Manager Service.

Common Agent serviceTo stop and start the Common Agent Service, use the following commands:

Hitachi-Command-Suite-Common-Agent-Component-installation-folder\bin\hbsasrv.exe stopHitachi-Command-Suite-Common-Agent-Component-installation-folder\bin\hbsasrv.exe start

Tip: After installing Application Agent, if the Copy Controller service or theCommon Agent Service is Disabled, change the setting to Automatic.The Common Agent Service is used by other agent programs (such as DeviceManager Agent). When you stop Common Agent Service, you shoulddetermine whether or not the operation of other agents is affected.


Setting error logging options for Application AgentThe agent.logger.properties file is used to specify the values of logoutput-related properties. The file is stored in the following location:

C:\Hitachi-Command-Suite-Agent Component-installation-folder\agent\config\If a value is not specified in the agent.logger.properties file or if thespecified value is outside the specifiable range, the default value is used.

The following tables list the available properties, the types of informationlogged, and the parameters that are stored when values are logged.

Table 4-4 List of properties in the agent.logger.properties file

Property Description

agent.logger.loglevel The output level of the Replication Manager log file.Messages matching the type are output to the logfile.Specifiable values: One of the three followingscenarios: DEBUG and INFO, WARN,or ERROR and FATAL.See Table 4-5 Error values and descriptions on page4-24 for a description of the types and Table 4-6Logged values on page 4-24 for a list of typeslogged for each level. These values can be entered inany combination of upper and lower case.Default value: INFO

agent.logger.MaxBackupIndex The maximum number of log files created inReplication Manager. When the number of log filesreaches this value, the existing files are reused,starting with the oldest file.Specifiable values: 1 to 20 (files)Default value: 10

agent.logger.MaxFileSize The maximum size of a single Replication Managerlog file. This value must be specified in bytes,kilobytes, or megabytes. If the specified value is notfollowed by KB or MB, the size is assumed to be inbytes.Specifiable values are determined by the specifiedunit as follows:Bytes: 524288 to 33554432KB: 512K B to 32768 KBMB: 1 MB to 32 MBDefault value: 5 MB


Table 4-5 Error values and descriptions

Type Description

DEBUG Detailed information for the purpose of debugging.

INFO Information for the purpose of tracing the process flow.

WARN Messages that are raised when there are some limitations but theprocess execution continues.

ERROR Error occurred during the process execution or startup.

FATAL Fatal exception occurred in the code and the execution stops.

Table 4-6 Logged values

ValuesLogged INFO DEBUG WARN ERROR FATAL

DEBUG X

INFO

WARN X X

ERROR X X X

FATAL X X X X


5Operating the management server

This chapter describes the Replication Manager settings and operatingprocedures, including how to start and stop Replication Manager and how toback up and restore the databases.

□ About executing commands on the management server

□ Starting and stopping Replication Manager

□ Changing settings in the properties files

Operating the management server 5-1Hitachi Replication Manager Configuration Guide

About executing commands on the management serverThis section includes information related to the execution of commands thatare required for Replication Manager operation.

User permissionsTo execute the commands described in this manual, you must log in as amember of the Administrators group in Windows or as a root user in Linux.

If the User Account Control (UAC) feature is enabled, you might be asked toelevate your current privileges to the Administrator level. Because somecommands necessary to operate a management server require just suchprivileges, you should do so (unless specifically instructed otherwise).

To elevate your privileges to the Administrator level for executing acommand:

1. Right-click the Command Prompt icon.2. From the list of context menu items, choose Run as administrator. The

elevated command prompt window opens.

Setting up the PATH environment variable in LinuxThe directories for basic OS commands must be specified as the first entriesin the PATH environment variable. If an error occurs when you execute acommand because a command was not found or because another utilityexists in a path with the same name, edit the PATH environment variable sothat the directories for basic OS commands are specified first.

Starting and stopping Replication ManagerThis section describes how to start and stop Replication Manager.

Replication Manager operates as part of HBase 64 Storage Mgmt Web Service(which is a service of Hitachi Command Suite Common Component). Thismeans that you start and stop Replication Manager by starting or stoppingthe Hitachi Command Suite Common Component services.

For more information see Starting and stopping the Application AgentServices on page 4-22.

Note: Device Manager must be running for Replication Manager to operateproperly.

Starting Replication ManagerTo start Replication Manager, use the appropriate procedure below.

5-2 Operating the management serverHitachi Replication Manager Configuration Guide

In Windows

1. Log in as a user with Administrator permissions.2. Perform one of the following (a or b):

a. Using the Start menu:In Windows Server 2008:Select Start > All Programs > Hitachi Command Suite > ManageServices > Start - HCS.In Windows Server 2012:Select All Apps from the Start menu, then select Hitachi CommandSuite > Manage Services > Start - HCS.

b. Using the command line:Common-Component-installation-folder\bin\hcmds64srv /start

In Linux

1. Log in as root user.2. Execute the following command:

Common-Component-installation-directory/bin/hcmds64srv -startWhen you execute the command, the services of other Hitachi CommandSuite products are also started. However, if Hitachi Command Suite CommonComponent services are already running, the services of Hitachi CommandSuite products are not automatically started, and you must start themmanually. Because Device Manager must be running for Replication Managerto operate properly, start the Device Manager service first. For details abouthow to start this service, see the Hitachi Command Suite AdministratorGuide. For details about how to start the services of other Hitachi CommandSuite products, see the manuals for each product.

Stopping Replication Manager To stop Replication Manager, use the appropriate procedure below.

In Windows


a. Using the Start menu:In Windows Server 2008:Select Start > All Programs > Hitachi Command Suite > ManageServices > Stop - HCS.In Windows Server 2012:Select All Apps from the Start menu, then select Hitachi CommandSuite > Manage Services > Stop - HCS.

b. Using the command line:Common-Component-installation-folder\bin\hcmds64srv /stop


In Linux


Common-Component-installation-directory/bin/hcmds64srv -stopThis command also stops the services of other Hitachi Command Suiteproducts, so you should consider the operation of these products beforeexecuting this command.

Checking the operation status of Replication Manager To see whether Replication Manager is running, use the appropriateprocedure below.

In Windows


a. Using the Start menu:In Windows Server 2008:Select Start > All Programs > Hitachi Command Suite > ManageServices > Status - HCS.In Windows Server 2012:Select All Apps from the Start menu, then select Hitachi CommandSuite > Manage Services > Status - HCS.

b. Using the command line:Common-Component-installation-folder\bin\hcmds64srv /status

In Linux


Common-Component-installation-directory/bin/hcmds64srv -status

Example 1: Execution results if Replication Manager is runningKAPM05007-I Already started service. service-name=HBase 64 Storage Mgmt Web ServiceKAPM05007-I Already started service. service-name=HBase 64 Storage Mgmt Web SSO ServiceKAPM05007-I Already started service. service-name=HBase 64 Storage Mgmt SSO ServiceKAPM05007-I Already started service. service-name=HCS Device Manager Web ServiceKAPM05007-I Already started service. service-name=HBase 64 Storage Mgmt Common ServiceKAPM05007-I Already started service. service-name=Device Manager Server ServiceKAPM05007-I Already started service. service-name=Tiered Storage Manager Server Service


Example 2: Execution results if Replication Manager has stoppedKAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web ServiceKAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web SSO ServiceKAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt SSO ServiceKAPM05009-I Already stopped service. service-name=HCS Device Manager Web ServiceKAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Common ServiceKAPM05009-I Already stopped service. service-name=Device Manager Server ServiceKAPM05009-I Already stopped service. service-name=Tiered Storage Manager Server ServiceIf you execute the command as described above, you can also check whetherthe HiRDB service is running. If it is running, the following message appearsin the execution results:

KAPM06440-I The HiRDB service has already started.The following message appears if the service is not running:

KAPM06441-I The HiRDB service has already stopped.

Changing settings in the properties filesThis section describes the settings in the properties files used by ReplicationManager and how to change them.

Use a text editor to alter parameters in the properties files. After makingchanges, you must do the following:

• Restart Replication Manager. To do this, you must first stop and thenstart the services. For details, see Starting and stopping ReplicationManager on page 5-2.

• In a cluster environment, the values in the properties files of theexecuting and standby nodes must match. (If you change a properties fileon the executing node, you must do the same for the standby node.)

Note: Inappropriate changes to properties files can have unexpectedresults. We recommend that you use the default values unless they causeproblems.

Properties related to Replication ManagerThe properties required by Replication Manager are specified in the followingproperties files stored on the management server:

• logger.properties on page 5-8• serverstorageif.properties on page 5-12• bcmif.properties on page 5-12


• agentif.properties on page 5-13• appagentif.properties on page 5-14• base.properties on page 5-15• RpMCLI.properties on page 5-18

With the exception of RpMCLI.properties, these files are in the followingdirectories/folders:

In Windows: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 (notconf).

The following table lists the properties and default values for each file.

Note: Under normal circumstances, the agentif.properties properties donot need to be changed. To change their values, you need expert knowledgeof Device Manager Agent.

Table 5-1 List of Replication Manager properties

File Property Defaultvalue (unit)

logger.properties logger.loglevel 20

logger.sysloglevel 0

logger.MaxBackupIndex 6 (files)

logger.MaxFileSize 20MB

logger.DB.loglevel 20

logger.DB.MaxBackupIndex 6

logger.DB.MaxFileSize 20MB

logger.RefreshConfig.enabled true

logger.RefreshConfig.MaxBackupIndex 3 (files)

logger.RefreshConfig.MaxFileSize 10MB

logger.UserOperation.enabled true

logger.UserOperation.MaxBackupIndex 5 (files)

logger.UserOperation.MaxFileSize 10MB

logger.RefreshStatus.enabled true

logger.RefreshStatus.MaxBackupIndex 2 (files)

logger.RefreshStatus.MaxFileSize 10MBlogger.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

serverstorageif.properties

ssif.socketTimeout 3600(seconds)

ssif.socketConnectTimeout 5 (seconds)

ssif.alertTimeout 1800(seconds)

bcmif.properties bcmif.socketTimeout 3600(seconds)

bcmif.socketConnectTimeout 5 (seconds)

bcmif.ReconnectionInterval 60 (seconds)

bcmif.ReconnectionCount 5 (times)

agentif.properties agentif.connectTimeout 30 (seconds)

agentif.responseTimeout 3600(seconds)

hdvmagtif.connectTimeout 30 (seconds)

hdvmagtif.responseTimeout 3600(seconds)

hdvmagtif.MaxPollingCount 50 (times)

hdvmagtif.PollingInterval 30 (seconds)

appagentif.properties appagentif.connectTimeout 30 (seconds)

appagentif.responseTimeout 3600(seconds)

base.properties base.operationmode.forcemaintenancemode

false

base.pair.udpport.startnumber 35301base.repositry.synchronize.polling truebase.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)

base.rmi.port 25200

base.rmi.backlog 100

base.taskschedule.threadmax 10

base.refreshstorage.polling.timeout 60 minutes

base.pair.performance.interval 1 minute

base.pair.performance.aggregate 5

base.vmhost.enabled trueRpMCLI.properties RpMCLI.diaglevel INFO

RpMTaskCLI.MaxBackupIndex 6 (files)

RpMTaskCLI.MaxFileSize 20 (MB)

logger.propertiesThe logger.properties file is used to specify the values of log output-related properties.

For the following log files, specify the properties in the filelogger.properties file (where n is an integral number):

Table 5-2 Log file type and file name

Type File name

Trace log files HRpMTracen.log

DB trace log files HRpMDBTracen.log

Application status logfiles

HRpMIFAppStatusn.log

Application configurationlog files

HRpMIFAppConfign.log

Pair status updating logfiles

HRpMIFRefreshStatusn.log

User operation log files HRpMIFUserOperationn.log

Configuration updatinglog files

HRpMIFRefreshConfign.log

If a value is not specified in the logger.properties file, or if the specifiedvalue is outside the specifiable range, the default value will be used. Thefollowing table describes the available properties and settings.


Note: File size values must be specified in bytes, kilobytes, or megabytes. Ifthe specified value is not followed by KB or MB, the size is assumed to be inbytes. Specifiable values are determined by the specified unit as follows:Bytes: 4096 to 2147483647KB: 4 KB to 2097151 KBMB: 1 MB to 2047 MB

Table 5-3 List of properties in the logger.properties file


logger.loglevel The threshold value for the output level ofthe Replication Manager log files.Messages containing values that are equalto or less than this value are output to thelog file.Specifiable values: 0, 10, 20, 30 (indecreasing order of importance from leftto right).Default value: 20

logger.sysloglevel The threshold value for the output level ofthe OS event log or syslog that is outputusing Replication Manager. Messagescontaining values that are equal to or lessthan this value are output to the log file.Specifiable values: 0, 10, 20, and 30 (indecreasing order of importance from leftto right).Default value: 0

logger.MaxBackupIndex The maximum number of log files createdin Replication Manager. When the numberof log files reaches this value, the existingfiles are reused, starting with the oldestfile.Specifiable values: 1 to 16 (files)Default value: 6

logger.MaxFileSize The maximum size of a single ReplicationManager log file.Default value: 20MB

logger.DB.loglevel Threshold value for output of a database-related log file.Specifiable values: 0, 10, 20, and 30 (indecreasing order of importance from leftto right).Default value: 20

logger.DB.MaxBackupIndex Maximum number of backup files for adatabase-related log file.Specifiable values: 1 to 16 (files)Default value: 9



logger.DB.MaxFileSize Maximum size of a database-related logfile.Default value: 20 MB

logger.RefreshConfig.enabled Enabling or disabling of the configurationupdate logging function.Specifiable values: true or falseDefault value: true

logger.RefreshConfig.MaxBackupIndex Maximum number of backup files for aconfiguration update log file.Specifiable values: 1 to 32 (files)Default value: 5

logger.RefreshConfig.MaxFileSize Maximum size of a configuration updatelog file.Default value: 10 MB

logger.UserOperation.enabled Enabling or disabling of the user operationlogging function.Specifiable values: true or falseDefault value: true

logger.UserOperation.MaxBackupIndex Maximum number of backup files for auser operation log file.Specifiable values: 1 to 32 (files)Default value: 5

logger.UserOperation.MaxFileSize Maximum size of a user operation log file.Default value: 10 MB

logger.RefreshStatus.enabled Enabling or disabling of the pair statusupdate logging function.Specifiable values: true or falseDefault value: true

logger.RefreshStatus.MaxBackupIndex Maximum number of backup files for a pairstatus update log file.Specifiable values: 1 to 32 (files)Default value: 2

logger.RefreshStatus.MaxFileSize Maximum size of a pair status update logfile.Default value: 10 MB

logger.AppConfig.MaxBackupIndex Maximum number of applicationconfiguration log backup files.Specifiable values: 1-32 (files).Default value: 3

logger.AppConfig.MaxFileSize Maximum size of the applicationconfiguration log file.Specifiable values: 1-2047 (MB).



Default value: 10

logger.AppConfig.enabled Log function on/off switch for theapplication configuration log.Specifiable values: true or false.

Default value: truelogger.AppStatus.MaxBackupIndex Maximum number of the application status

log backup files.Specifiable values: 1-32 (files).Default value: 6

logger.AppStatus.MaxFileSize Maximum size of the application status logfileSpecifiable values: 1 to 2047 (MB).Default value: 20

logger.AppStatus.enabled Log function on/off switch for theapplication status log.Specifiable values: true or false.

Default value: true

The following are the output levels of log files and the contents of outputmessages:

0: Critical error, high-priority information10: Non-critical error, medium-priority information20: Warning30: All debug information

About Replication Manager log output

The amount of information output to the Replication Manager log filesdepends on the memory heap size of the system. Therefore, you mustchange the values of the xxxx.MaxBackupIndex and xxxx.MaxFileSizeparameters in the logger.properties file to appropriate values for thememory heap size. The following table shows the recommended amount oflog data to be retained.

Note: The default values in the logger.properties file assume 6,000 pairsin an open system and 40,000 pairs in a mainframe system.


Table 5-4 Memory size and amount of output log information

Memoryheap size

Amount of log data to be retained (MB)

Tracelog Database log

Transmission logs

Configurationupdate log

Useroperations

log

Pair statusupdate log

Small 120 120 50 50 20

Medium 130 170 70 50 30

Large 140 230 100 50 30

serverstorageif.propertiesThe serverstorageif.properties file is used to specify the values ofproperties related to the interface between Replication Manager and DeviceManager server. The following table describes the available properties andsettings.

Table 5-5 List of properties in the serverstorageif.properties file


ssif.socketTimeout The amount of time Replication Manager waits to read datafrom Device Manager server. If 0 is specified, ReplicationManager waits until all data is read without timing out.Specifiable values: 0 to 86400 (seconds)Default value: 3600

ssif.socketConnectTimeout

The amount of time Replication Manager waits to connect toDevice Manager server. If 0 is specified, Replication Managerwaits until a connection is established without timing out.Specifiable values: 0 to 3600 (seconds)Default value: 5

ssif.alertTimeout The amount of time Replication Manager waits to issue analert message query to Device Manager server.Specifiable values: 1 to 3600 (seconds)Default value: 1800Note: When you change this value, do not specify a valuegreater than the value specified for ssif.socketTimeout(except zero). If you specify a greater value, alerts might notbe received immediately.

bcmif.propertiesThe bcmif.properties file is used to specify the values of properties relatedto the interface between Replication Manager and Business Continuity


Manager or between Replication Manager and Mainframe Agent. The followingtable describes the available properties and settings.

Table 5-6 List of properties in the bcmif.properties file


bcmif.socketTimeout The amount of time Replication Manager waits toread data from Business Continuity Manager orMainframe Agent. If 0 is specified, ReplicationManager waits until all data is read without timingout.Specifiable values: 0 to 86400 (seconds)Default value: 3600

bcmif.socketConnectTimeout The amount of time Replication Manager waits toconnect to Business Continuity Manager or MainframeAgent. If 0 is specified, Replication Manager waitsuntil a connection is established without timing out.Specifiable values: 0 to 3600 (seconds)Default value: 5

bcmif.ReconnectionInterval The retry interval when Replication Manager cannotestablish a connection with Business ContinuityManager or Mainframe Agent. If 0 is specified,Replication Manager continually attempts to establisha connection.Specifiable values: 0 to 1800 (seconds)Default value: 60

bcmif.ReconnectionCount The number of retries attempted when ReplicationManager cannot establish a connection with BusinessContinuity Manager or Mainframe Agent. If 0 isspecified, the number of retries is unlimited.Specifiable values: 0 to 100 (times)Default value: 5

agentif.propertiesThe agentif.properties file is used to specify the values of propertiesnecessary for the interface between Replication Manager and a DeviceManager Agent. Normally, you do not need to change these values. Tochange the values, you need expert knowledge of Device Manager Agent. Thefollowing table describes the available properties and settings.

Table 5-7 List of properties in the agentif.properties File


agentif.connectTimeout The amount of time Replication Manager waits toconnect to a Device Manager Agent when collectingcopy pair statuses. If 0 is specified, ReplicationManager waits until a connection is established withouttiming out.Specifiable values: 0 to 3600 (seconds)



Default value: 30

agentif.responseTimeout The amount of time Replication Manager waits toreceive a response from a Device Manager Agent whencollecting copy pair statuses. If 0 is specified,Replication Manager waits for a response is withouttiming out.Specifiable values: 0 to 86400 (seconds)Default value: 3600

hdvmagtif.connectTimeout The amount of time Replication Manager waits toconnect to a Device Manager Agent when collectingconfiguration information or performing copy pairoperations. If 0 is specified, Replication Manager waitsuntil a connection is established without timing out.Specifiable values: 0 to 3600 (seconds)Default value: 30

hdvmagtif.responseTimeout The amount of time Replication Manager waits toreceive a response from a Device Manager Agent whencollecting configuration information or performing copypair operations. If 0 is specified, Replication Managerwaits for a response without timing out.Specifiable values: 0 to 86400 (seconds)Default value: 3600

hdvmagtif.MaxPollingCount The maximum number of times that ReplicationManager checks the processing status of a DeviceManager Agent when Device Manager Agent takes anindefinite period of time to collect configurationinformation or to perform copy pair operations. If 0 isspecified, there is no limit on the number of retries.Specifiable values: 0 to 100 (times)Default value: 50

hdvmagtif.PollingInterval The interval at which Replication Manager checks theprocessing status of a Device Manager Agent whenDevice Manager Agent takes an indefinite period oftime to collect configuration information or to performcopy pair operations.Specifiable values: 5 to 1200 (seconds)Default value: 30

appagentif.propertiesThe appagentif.properties file is used to specify the values of propertiesnecessary for the interface between Replication Manager and ApplicationAgent. Normally, you do not need to change these values. To change thevalues, you need expert knowledge of Application Agent. The following tabledescribes the available properties and settings.


Table 5-8 List of properties in the appagentif.properties File


appagentif.connectTimeout The amount of time Replication Manager waits toconnect to an Application Agent when collectingconfiguration statuses. If 0 is specified, ReplicationManager waits until a connection is establishedwithout timing out.Specifiable values: 0 to 3600 (seconds)Default value: 30

appagentif.responseTimeout The amount of time Replication Manager waits toreceive a response from an Application Agent whencollecting configuration statuses. If 0 is specified,Replication Manager waits for a response withouttiming out. If the specified value exceeds themaximum, the default value is used.Specifiable values: 0 to 86400 (seconds)Default value: 3600

base.propertiesThe base.properties file is used to specify the values of propertiesnecessary for the internal processing of Replication Manager. The followingtable describes the available properties and settings.

Table 5-9 List of properties in the base.properties file


base.operationmode.forcemaintenancemode

Specifies to start Replication Manager inmaintenance mode regardless of the currentoperation mode. If true is specified, ReplicationManager starts with maintenance mode when theserver services are started or restarted. If false,Replication Manager starts with the currentoperation mode when the server services arestarted or restarted.Specifiable values: true or falseDefault value: false

base.pair.udpport.startnumber The starting UDP port number used forcommunication between CCI instances.Specifiable values: 0 to 65535Default value: 35301

base.repositry.synchronize.polling

Specifies whether Replication Manager automaticallysynchronizes with a Device Manager database. Avalue of true means that automatic synchronizationoccurs, and a value of false means that it does not.

Specifiable values: true or falseDefault value: true



base.taskscheck.interval The interval at which Replication Manager checkswhether a task related to a copy pair operation hasfinished.Specifiable values: 30 to 3600 (seconds)Default value: 120

base.taskscheck.maxcount The maximum number of times that ReplicationManager checks whether a task related to a copypair operation has finished. If 0 is specified, there isno limit.Specifiable values: 0 to 100 (times)Default value: 0

base.taskscheck.mf.interval The interval at which Replication Manager checkswhether a task related to a mainframe copy pairoperation has finished.Specifiable values: 30 to 3600 (seconds)Default value: 120

base.taskscheck.mf.maxcount The maximum number of times that ReplicationManager checks whether a task related to amainframe copy pair operation has finished. If 0 isspecified, there is no limit.Specifiable values: 0 to 100 (times)Default value: 0

base.repositry.synchronize.interval

The interval at which the database synchronizationfunction performs a check.Specifiable values: 10 to 1440 (minutes)Default value: 10

base.repositry.synchrocheck.interval

The interval at which Replication Managerautomatically checks the Device Manager databaseto see if it has been updated. If 0 is specified, theautomatic checking is disabled.This property is only enabled when the informationsource is a remote Device Manager.Specifiable values: 0 to 1440 (minutes)Default value: 10

base.refreshdginfo.exec This property specifies whether to acquire definitioninformation of copy pairs defined in device groups.To acquire definition information, specify 1.To not acquire definition information, specify 0.Values that can be specified: 0 or 1Default value: 1

base.alert.automarking This property specifies whether Replication Managerautomatically controls the transition of alerts fromNot Completed to Completed status and whetherdetection of transitions in copy pair status in copygroups is performed for each copy group.



To specify that control and detection are to beperformed, specify true.

To specify that control and detection not beperformed, specify false.

Values that can be specified: true or falseDefault value: true

base.rmi.port This property specifies the RMI registry port numberused by Replication Manager for receiving requests.You must specify this property if you use theReplication Manager CLI, the Replication tab ofDevice Manager, or you manage tasks created byAutomation Director using Replication Manager. Ifyou use the Replication tab, you must set therpmlib.rpm.port property in therpmlib.properties file on the Device Managerserver. For details, see the Hitachi Command SuiteAdministrator Guide or the Automation DirectorInstallation and Configuration Guide.Values that can be specified: 1-65535Default value: 25200

base.rmi.enabled • If Replication Manager version is earlier thanv8.2.1:This property specifies whether the RMI registryis started. You must set this property to true ifyou use the Replication tab of Device Manageror you manage tasks created by AutomationDirector using Replication Manager.Specifiable values: true or falseDefault value: true

• If Replication Manager version is v8.2.1 orlater:This property is disabled. The RMI registry isalways started regardless of the value of thisproperty.

base.rmi.backlog This property specifies the maximum number ofrequests Replication Manager can receive. You mustspecify this property if you use the ReplicationManager CLI, the Replication tab of DeviceManager, or you manage tasks created byAutomation Director using Replication Manager.A value of zero (0) sets the value to the Javadefault value (50).Values that can be specified: 0-1000Default value: 100

base.taskschedule.threadmax This property specifies the maximum number oftasks Replication Manager can execute concurrently.Values that can be specified: 10-100Default value: 10



base.refreshstorage.polling.timeout

This property specifies the length of time ReplicationManager waits for a Device Manager server refreshof storage system information.Values that can be specified: 60-1440Default value: 60

base.pair.performance.interval

This property specifies the interval of copy pairperformance information (C/T delta) acquisitionfrom Device Manager agent. If 0 is specified, theacquisition is not performed.Value that can be specified: 0-60 (0 and measuresof 60)Default value: 1

base.pair.performance.aggregate

This property specifies the aggregate value of C/Tdelta.Values that can be specified: 1-60Default value: 5

base.vmhost.enabled The property specifies whether the Hosts view listsvirtualization servers. If some virtualization serversare managed by a remote Device Manager, refreshthe configuration information after you change thevalue of this property.Specifiable values: true or falseDefault value: true

RpMCLI.propertiesThe RpMCLI.properties file is used to specify the values of propertiesnecessary for the Replication Manager CLI.

The following table describes the available properties and settings.

Table 5-10 List of properties in the RpMCLI.properties File


RpMCLI.diaglevel This property specifies output level of the Replication ManagerCLI trace log. The values that can be specified are: ERROR, WARN,INFO, DEBUG.

Default value: INFOThe values are case sensitive. The meaning of each value is asfollows:• ERROR: Messages that indicate an abnormal occurrence and

error messages are output.• WARN: In addition to ERROR messages, warning messages

are output.• INFO: In addition to the ERROR and WARN messages,

information messages are output



• DEBUG: All messages are output.

RpMTaskCLI.MaxBackupIndex

This property specifies the maximum number of trace log files(RpMTaskCLIn.log), which are created when the GetTasks orExecuteTask command is executed. If a new log file is requiredwhen the number of log files has been reached this value, theoldest log file is overwritten.Values that can be specified: 1-16 (files)Default value: 6

RpMTaskCLI.MaxFileSize

This property specifies the maximum size of a trace log file,which are created when the GetTasks or ExecuteTask commandis executed.Values that can be specified: 1-20 (MB)Default value: 20



6Security management

This chapter explains security functions that can be used in ReplicationManager.

□ Network communications security

□ Collecting audit logs

Security management 6-1Hitachi Replication Manager Configuration Guide

Network communications securityTo provide security for the communication routes used by ReplicationManager, you can use the HTTPS protocol to encrypt communications. Thefollowing routes can be encrypted:

(1) Between Hitachi Command Suite Common Component on themanagement server and the Web browser on the management client.

(2) Between Replication Manager on one management server and DeviceManager server on another management server (local or remote).

(3) Between Replication Manager (on the management server) and BusinessContinuity Manager (on a host) using IHS.

The numbers (1), (2), and (3) correspond to the diagram that follows.

6-2 Security managementHitachi Replication Manager Configuration Guide

Figure 6-1 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 DeviceManager Agent (on a pair management server)

• Between Replication Manager (on the management server) and aBusiness Continuity Manager (on the host) unless IHS is used.

• Between Replication Manager (on the management server) andMainframe Agent (on the host).

• Between Replication Manager (on the management server) andApplication Agent (on the database server or backup server).


Securing communications between Hitachi Command Suite CommonComponent and Web browsers

To encrypt communications between Hitachi Command Suite CommonComponent on the management server and the Web browser on themanagement client, you must create a server certificate for CommonComponent on the management server and import it into the Web browser onthe management client.

Figure 6-2 Flow of operations for setting up secure communicationsbetween Common Component and a Web browser

For more information on the procedures, see the following descriptions in theHitachi Command Suite Administrator Guide:

• Creating a secret key and a certificate signing request for CommonComponent

• Applying to a certificate authority for a Common Component servercertificate

• Enabling SSL/TLS for Common Component• Changing the URL for accessing Hitachi Command Suite products

(hcmds64chgurl command)• Importing a server certificate into a Web browser• Changing pop-up blocker settings


Note: A secure method must be used to transmit the server certificate forHitachi Command Suite Common Component to management clients.

Securing communications between Replication Manager and theDevice Manager server

To encrypt communications between Replication Manager on themanagement server and the Device Manager server (local or remote), youmust create a server certificate for the Device Manager server and import itinto the truststore (jssecacerts) file in Replication Manager.


Figure 6-3 Flow of operations for setting up secure communicationsbetween Replication Manager and the Device Manager server

If you use a well-known certificate authority (CA), its server certificate mightalready be in the truststore (jssecacerts). In this case, you do not need toimport the CA’s server certificate again.

Note: Regarding server certificates:

• If you manage multiple Device Manager servers as information sources,you must create server certificates for each server and import them intothe truststore (jssecacerts) for the management server runningReplication Manager.


• A secure method must be used to transmit the server certificate for theremote Device Manager to the management server running ReplicationManager.

For more information on the procedures for the Device Manager server andCommon Component, and information on the truststore, see the followingdescriptions in the Hitachi Command Suite Administrator Guide:

• Creating a key pair and a self-signed certificate for Device Manager server• Enabling SSL/TLS for the Device Manager server• Creating a certificate signing request for Device Manager server• Applying to a certificate authority for a Device Manager server certificate• Importing a server certificate into the Device Manager server keystore• Importing a server certificate into the Device Manager server truststore• Downloading a Device Manager server truststore file• Exporting a Device Manager server self-signed certificate• Importing a server certificate into the truststore of Hitachi Command

Suite• Checking the server certificates imported into the truststore of Hitachi

Command Suite

After importing the server certificate for the Device Manager server to thetruststore (jssecacerts), select HTTPS as the transmission protocol in theReplication Manager GUI window for adding (or the window for editing) theinformation source, and specify the port number for HTTPS communications.For more information on how to add or edit the information source, see theonline Help.

Note: If you want to restrict which cipher suites are used for SSL/TLScommunication, change the value of theserver.https.enabledCipherSuites property in the server.propertiesfile of the Device Manager server. See the Hitachi Command SuiteAdministrator Guide for more information.

Securing communications between Replication Manager andBusiness Continuity Manager (IHS)

To encrypt communications between Replication Manager on themanagement server and BCM on the host, you must set IHS as the reverseproxy server and import the IHS server certificate into the truststore(jssecacerts) of Replication Manager.


Figure 6-4 Flow of operation for setting up secure communicationsbetween Replication Manager and BCM (IHS)

If you use a well-known certificate authority (CA), its server certificate mightalready be in the truststore (jssecacerts). In this case, you do not need toimport 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 Hitachi BusinessContinuity Manager Installation Guide.

For more information on the procedures for Common Component andinformation on the truststore, see the following descriptions in the HitachiCommand Suite Administrator Guide:

• Importing a server certificate into the truststore of Hitachi CommandSuite

• Checking the server certificates imported into the truststore of HitachiCommand Suite


After importing the server certificate for the IHS to the truststore(jssecacerts), select HTTPS as the transmission protocol in the ReplicationManager GUI window for adding (or the window for editing) the informationsource, and specify the port number for HTTPS communications. For moreinformation on how to add or edit the information source, see the online Help.

Note: Regarding server certificates:

• If you manage multiple BCM (IHS) hosts as information sources, youmust create server certificates for each server and import them into thetruststore (jssecacerts) for the management server running ReplicationManager.

• A secure method must be used to transmit the server certificate for theIHS to the management server running Replication Manager.

Collecting audit logs This section describes the information output in the Replication Manager auditlog for the ConfigurationAccess category. For details about the informationfor other audit categories, please see the Hitachi Command SuiteAdministrator Guide.

Each audit event is assigned a severity level. You can filter audit log data tobe output according to the severity levels of events.

Table 6-1 Audit events for the ConfigurationAccess category

Descriptionof category Audit event Severity Message ID

Resource groupcreation (GUI)

Successful resource group creation 6 KAPM02630-I

Failed resource group creation 3 KAPM02635-E

Resource groupcreation (GUI orCLI)

Successful resource group creation 6 KAPM02670-IKAPM07257-I

Failed resource group creation 3 KAPM02675-EKAPM07258-E

Resource groupdeletion (GUI)

Successful resource group deletion 6 KAPM02631-I

Failed resource group deletion 3 KAPM02636-E

Resource groupdeletion (GUI orCLI)

Successful resource group deletion 6 KAPM02671-IKAPM07259-I

Failed resource group deletion 3 KAPM02676-EKAPM07260-E

Editing ofresource groupproperties (GUI)

Successful resource group property editing 6 KAPM02634-I

Failed resource group property editing 3 KAPM02639-E

Editing ofresource group

Successful resource group property editing 6 KAPM02674-IKAPM07261-I



properties (GUIor CLI)

Failed resource group property editing 3 KAPM02679-EKAPM07262-E

Addition of auser to aresource group(GUI)

Successful user addition to a resource group 6 KAPM02632-I

Failed user addition to a resource group 3 KAPM02637-E

Removing of auser from aresource group(GUI)

Successful user removal from a resource group 6 KAPM02633-I

Failed user removal from a resource group 3 KAPM02638-E

Assignment of auser to aresource group(GUI or CLI)

Successful user assignment to a resource group 6 KAPM02672-I

Failed user assignment to a resource group 3 KAPM02677-E

Copy pairoperation

The pair operation task (pair create, delete, modify, oredit group name) has started.

6 KAVN10001-IKAVN10006-IKAVN10010-IKAVN10089-I

The pair operation task (node addition or deletion) hasstarted.

6 KAVN10085-IKAVN10087-I

The pair operation task (node addition or deletion) wassuccessful.


The pair operation task (pair create, delete, modify, oredit group name) was successful.

6 KAVN10002-IKAVN10007-IKAVN10011-IKAVN10090-I

The pair operation task (pair create, delete, or modify)timed out. (The command was executed successfully, butwhether the pair status was changed correctly could notbe confirmed.)

4 KAVN10003-WKAVN10008-WKAVN10030-W

The pair operation task has failed. 3 KAVN10009-E

Failed to update the configuration definition file afterdeleting the pair.

4 KAVN10004-WKAVN10005-W

Editing or distribution of the disk configuration definitionfile has started.


The disk configuration definition file was successfullyedited or distributed.


An attempt to edit or distribute the disk configurationdefinition file has failed.

3 KAVN10014-EKAVN10017-EKAVN10020-EKAVN10023-E



Editing or distribution of the copy group configurationdefinition file has started.


The copy group configuration definition file wassuccessfully edited or distributed.


An attempt to edit or distribute the copy groupconfiguration definition file has failed.

3 KAVN10009-E

Managementhost changeoperation

Changing of the management host has started. 6 KAVN10026-I

Changing of the management host has finished. 6 KAVN10027-I

An attempt to change the management host has failed. 3 KAVN10009-E

Secondaryvolume hidingoperation

Secondary volume hiding operation started. 6 KAVN10073-IKAVN10079-I

Secondary volume hiding operation completed. 6 KAVN10074-IKAVN10080-I

Secondary volume hiding operation failed. 3 KAVN10075-EKAVN10081-E

Canceling of a secondary volume hiding operationstarted.


Canceling of a secondary volume hiding operationcompleted.


Canceling of a secondary volume hiding operation failed. 3 KAVN10078-EKAVN10084-E

Replicaoperation

Creation, editing, execution, canceling, or deletion of atask has started.

6 KAVN10031-IKAVN10034-IKAVN10037-IKAVN10040-IKAVN10043-I

Creation, editing, execution, canceling, or deletion of atask has succeeded.

6 KAVN10032-IKAVN10035-IKAVN10038-IKAVN10041-IKAVN10044-I

Creation, editing, execution, canceling, or deletion of atask has failed.

3 KAVN10033-EKAVN10036-EKAVN10039-EKAVN10042-EKAVN10045-E

Mounting or unmounting has started. 6 KAVN10046-IKAVN10049-I



Mounting or unmounting has succeeded. 6 KAVN10047-IKAVN10050-I

Mounting or unmounting has failed. 3 KAVN10048-EKAVN10051-E

Take over operation has started 6 KAVN10052-IKAVN10064-I

Take over operation is terminated 6 KAVN10053-IKAVN10065-I

Take over operation timed out. (The command executionwas successful, but completion could not be confirmed.)


Take back operation has started. 6 KAVN10058-IKAVN10061-I

Take back operation is terminated. 6 KAVN10059-IKAVN10062-I

Take back operation timed out. (The command executionwas successful, but completion could not be confirmed.)


Swap operation has started. 6 KAVN10055-I

Swap operation is terminated. 6 KAVN10056-I

Swap operation timed out 4 KAVN10057-W

Acquisition of replica information has started. 6 KAVN10067-I

Acquisition of replica information has finished. 6 KAVN10068-I

Acquisition of replica information has failed. 3 KAVN10069-E

Replica deletion has started. 6 KAVN10070-I

Replica deletion has finished. 6 KAVN10071-I

Replica deletion has failed. 3 KAVN10072-E


7Troubleshooting

This chapter describes how to handle the errors that might occur duringoperation of Replication Manager.

If you need technical support, see Getting help on page xii.

□ Overview

□ General problem resolution

□ Collecting maintenance information

□ Troubleshooting Application Agent operations

□ Troubleshooting when copy pairs are not recognized

□ Creation of TrueCopy Extended Distance or COW Snapshot copy pairs fails(HUS100 Series)

□ Troubleshooting replica operations

Troubleshooting 7-1Hitachi Replication Manager Configuration Guide

OverviewThis 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 7-5.

• When installing Replication Manager in an environment where DeviceManager and CCI manage copy pairs, if you cannot acquire the currentcopy pair information after refreshing the configuration information, seeTroubleshooting when copy pairs are not recognized on page 7-15 tosolve the problem.

• If the problem is not related to installation or removal, take actionaccording to General problem resolution on page 7-2.

General problem resolutionThis section describes how to deal with a problem that is not explicitlydescribed in this chapter. Follow the general procedure in the flowchart seenbelow.

Figure 7-1 Sequence of actions to take if a problem occurs

7-2 TroubleshootingHitachi Replication Manager Configuration Guide

1. Check the displayed messages for information about the problem andcorrect the error. For details about the actions to take for each message,see the Hitachi Command Suite Messages.

2. Check the messages output to the Replication Manager event log andcorrect the error. For details on how to view the event log data, see theHitachi Replication Manager User Guide.

3. If you cannot correct the error, execute the hcmds64getlogs command toobtain the maintenance information and contact the Support Center.

Send all the information to the Support Center . For details on how to executespecific maintenance commands, see Collecting maintenance information onpage 7-3.

If the error occurred on a host or pair management server, also obtainmaintenance information from Device Manager Agent. For details, see theHitachi Command Suite Installation and Configuration Guide.

Collecting maintenance informationThe hcmds64getlogs command allows you to collect maintenance informationabout Replication Manager and other Hitachi Command Suite productsinstalled on the same host. All the necessary information is collected by abatch process and output to an archive file.

You can collect the following files:

• Communication logs for refresh and user operations• Trace log files• Trace log files for installation or removal• Version information files• 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 commandThis section describes how to use the hcmds64getlogs command.

Note: Observe the following precautions with commands:

• Do not execute the hcmds64getlogs command more than once at thesame time. Also, do not execute this command and the hcmdsdbmove orhcmds64dbclustersetup command at the same time.

• If no message is displayed indicating that the hcmds64getlogs commandsucceeded or failed (KAPM05318-I or KAPM05319-E), it means the


command was interrupted due to insufficient disk space in the specifieddirectory (dir option). Allocate sufficient space in the output destinationand re-execute the command.

In Windows:Common-Component-installation-folder\bin\hcmds64getlogs /dirdirectory-name[/types Hitachi-Command-Suite-product-name][/arc archive-file-name][/logtypes logfile-types]

In Linux:Common-Component-installation-directory/bin/hcmds64getlogs -dir directory-name[-types Hitachi-Command-Suite-product-name][-arc archive-file-name][-logtypes logfile-types]

The arguments are shown in this table.

Table 7-1 hcmds64getlogs arguments

Argument Description

dir directory-name Specifies the name of the directory on the local disk in which thecollected maintenance information is to be stored. You need tocreate a new directory or specify an existing empty directory.The maximum length allowed for a directory name is 41 bytes ifno value is specified for the type option, and 35 bytes ifReplication Manager is specified as the type. For details about themaximum directory name length for products other thanReplication Manager, see the manual for the applicable product.

types Hitachi-Command-Suite-product-name

Specifies the name of the product from which maintenanceinformation will be collected. If this option is omitted, informationis collected from all Hitachi Command Suite products installed onthe management server (which may consume a great deal of diskspace). Use the batch collection command for maintenanceinformation twice to collect the maintenance information fromReplication Manager and Device Manager separately, or omit thetype option to collect the maintenance information from everyHitachi Command Suite product. For details about DeviceManager maintenance information, see the Hitachi CommandSuite Administrator Guide.

arc archive-file-name

Specifies the name of the archive file to be created. The archivefile is output to the directory specified for the dir option. Do notspecify a path for the archive file name. If you do, the commandmight terminate abnormally. If this option is omitted, the archivefile name will be HiCommand_log. When the archive file is output,this name is suffixed with the extension for the file type(.jar, .hdb.jar, .db.jar, or .csv.jar).

logtypes logfile-types

Specifies the types of the log files to be collected if only specifictypes of log files can be collected for some reason (such as afailure):


Argument Description

• log (.jar and .hdb.jar)

• db (.db.jar)

• csv (.csv.jar)

When specifying multiple types, separate the types with a space.If the logtypes option is not specified, all types of log files arecollected.If you specify both the types option and the logtypes option,always specify log in the logtypes option.

The characters that can be used for specifying arguments are as follows:

A to Z a to z 0 to 9 ! # ' ( ) - . = @ [ ] _ ` { } ~In Windows, you can use backslashes (\), forward slashes (/), and colons (:)as path delimiters. In Linux, you can use forward slashes as path delimiters.Note that you cannot specify spaces in a path in Linux.

Examples of collection commands

To collect only the maintenance information for Replication Manager:

In Windows:"C:\Program Files\HiCommand\Base64\bin\hcmds64getlogs" /dir C:\logfile /types ReplicationManager

In Linux:/opt/HiCommand/Base64/bin/hcmds64getlogs -dir /logfile -typesReplicationManager

To collect all the maintenance information for Hitachi Command Suiteproducts and output it to the Hitachi_log output archive file:

In Windows:"C:\Program Files\HiCommand\Base64\bin\hcmds64getlogs" /dir"C:\Program Files\HiCommand\log" /arc Hitachi_log

In Linux:/opt/HiCommand/Base64/bin/hcmds64getlogs -dir /opt/HiCommand/log -arc Hitachi_log

Troubleshooting Application Agent operationsThis section explains how to troubleshoot problems with Application Agent,including how to collect information when calling for support:

• Resolving Application Agent installation and removal errors on page 7-6• Resolving Application Agent operation errors on page 7-8• Collecting support information with the hrpmap_getras command on page

7-8


• Application Agent events that can be ignored on page 7-10

Tip: When collecting event log information to diagnose a problem on the hostwhere Application Agent is installed, be sure to collect maintenanceinformation for the Replication Manager server as well. This will help identifyproblems caused by communication errors between Application Agent and theserver. For more information, see Collecting maintenance information onpage 7-3.

Resolving Application Agent installation and removal errorsSometimes, an Application Agent installation or removal might not endproperly, such as when an error occurs during the installation, or theinstallation is canceled while files are being copied. In such cases, resolve theproblem by following the same sequence used for installation of ReplicationManager.

Note: After the RM Shadow Copy (VSS Provider) window has been started, ifthe installation fails or the Cancel button is used to stop the installation, youhave to use the Application Agent installer to re-install RM Shadow Copy.Note that before attempting to re-install RM Shadow Copy, first open Add/Remove Programs to make sure that it is removed. If it is still installed,remove it using Add/Remove Programs, and then re-install using theApplication Agent installer.

To resolve Application Agent installation or removal errors:

1. Check the displayed messages for information about the problem, andthen try to resolve it.

2. Check the trace log files that were output during the installation orremoval, and then try to resolve the problem.For details, see Application Agent and VSS Provider installer trace log fileson page 7-6.

3. If you cannot resolve the problem, collect the trace log files and contactthe Support Center.Send all of the collected information to the Support Center. For details,see Collecting maintenance information on page 7-3.

Note: Check the table contained in the section Application Agent events thatcan be ignored on page 7-10, to determine whether the displayed messagecan safely be ignored.

Application Agent and VSS Provider installer trace log files

The details and results of an Application Agent installation or removal(including the VSS Provider) are output to installer trace log files. You canuse these files to analyze the causes of errors that occurred duringinstallation or removal.

Application Agentrpm_app_agt_inst.log


VSS Providervssprv_inst.log

Output folder

The output folder of the Application Agent and VSS Provider trace log filesdiffer depending on whether the installation-folder-for-Application-Agent\DRM\log folder exists. If this folder does not exist, the log files areplaced on the desktop.

Output format

The formats of data output to the trace log files are as follows:

Format 1yyyy/mm/dd hh:mm:ss

Format 2The format of Windows Installer logs

Windows Installer log data is output from the Application Agent installer. Anexample of output log data is as follows:

2009/10/02 05:56:22 Windows Installer logging started.=== Loggingstarted: 2009/10/02 5:56:20 === Action start 5:56:20:INSTALL.Action start 5:56:20: AppSearch.…=== Logging stopped:2009/10/02 5:56:22 === 2009/10/02 05:56:22 Windows Installerlogging ended.

Application Agent log entries related to VSS Provider

In the Application Agent installer log file, check whether the following datahas been output to the log. If the data has been output, an error occurredduring a VSS Provider installation or removal. If that is the case, check theVSS Provider installer log file to view the details of the error.

The following are examples of data output to the log when an error occurredduring a VSS Provider operation.

Installation log entry2009/10/02 11:25:51 G:\WINDOWS\SysWOW64\cmd.exe /c ""G:\Program Files (x86)\HITACHI\DRM\VSS_Provider\vssprv.bat" -install "RMVSSPRV" "..\rpm\log""2009/10/02 11:26:53 Problem:An installation error occurred. The installation will nowstop.

Removal log entry2009/10/02 11:27:51 G:\WINDOWS\SysWOW64\cmd.exe /c ""G:\Program Files (x86)\HITACHI\DRM\VSS_Provider\vssprv.bat" -uninstall "RMVSSPRV" "...\rpm\log""2009/10/02 11:28:53Problem: An installation error occurred. The installation willnow stop.


Resolving Application Agent operation errorsApplication Agent is set up to support application linkage on hosts (databaseand backup servers). If an error occurs during user operation, an errormessage provides information indicating the host where the error occurred,regardless of whether that host is a database or backup server. For thisreason, you must collect information about the host occurred. When multipleagents are installed (such as Device Manager Agent), it is necessary to collectinformation about other agents that are stored on the management server(for use by Replication Manager) as follows:

• On hosts where both Device Manager Agent and Application Agent areinstalled, run both the hcmds64getlogs command on the managementserver and hrmap_getras command on the host where Application Agentis installed.

• On hosts where only Application Agent is installed, you need only run thehrmap_getras command.

For more information, see Collecting support information with thehrpmap_getras command on page 7-8 and Collecting maintenanceinformation on page 7-3.

About collecting support informationThe method used to collect Application Agent support information in databaseserver or backup server differs depending on the version of the DeviceManager agent.

Note: In a 64-bit environment, the command to collect support informationmust be executed as a 64-bit process.

If Device Manager Agent version is v6.3 or later

Execute the TIC command on the database or backup server. For details, seethe Hitachi Command Suite Administrator Guide.

If Device Manager Agent version is earlier than v6.3 or DeviceManager agent is not installed

Execute the hrpmap_getras command on the database or backup server. IfDevice Manager Agent is not installed, execute the TIC command on thedatabase or backup server.

Collecting support information with the hrpmap_getras commandThe hrmap_getras command collects the Application Agent configuration andlog files necessary for problem analysis. The command is located on hostswhere Application Agent is installed and is invoked as follows:

C:\Common-Agent-installation-folder\bin\hrmap_getras data-collection-folder


If you do not specify a data-collection-folder, the files are placed in theworking directory.

The collected information is described in the tables that follow.

Table 7-2 List of files collected in the hrpmap_getras folder

Files Description Location copied from

logger.properties Configuration file for ApplicationAgent logs

Common-Agent-installation-folder\mod\hrpmap\config\

agent.properties Configuration file for ApplicationAgent

trace.log[1-n] Trace log of Application Agent Common-Agent-installation-folder\mod\hrpmap\log\

SET_EXPORT_CATALOG_PATH.bat Batch file for setting exportcatalog path

Common-Agent-installation-folder\mod\hrpmap\bin\

Table 7-3 List of files collected in the hbsainfo folder


logger.properties Application Agent logconfiguration file

Common-Agent-installation-folder\agent\config

server.properties Application Agentconfiguration file

access.log Application Agent log files Common-Agent-installation-folder\agent\logs

error.logservice.logtrace.logalet.xml Deployment descriptor file

of Application AgentCommon-Agent-installation-folder\mod\hrpmap

Table 7-4 List of files collected in the drminfo folder


.version* Application Agent versioninformation file

Common-Agent-installation-folder\

all Files for each type of ApplicationAgent environment setting

Common-Agent-installation-folder\conf

drm_output.logdrm_output.log.old

Application Agent logfiles Common-Agent-installation-folder\log

rm_pp_trace[1-16].log Application Agent trace log files

drm_inst.log Application Agent installationtrace log files



all Dictionary map files Common-Agent-installation-folder\db

all Schedule-related log files For physical server:Common-Agent-installation-folder\scheduleFor virtual server:cluster path specified in sch.conf

Table 7-5 List of files collected in the ExportCatalog folder


all Catalog information files Path set for%EXPORT_CATALOG_PATH%

Application Agent events that can be ignoredSometimes events (error messages) are logged to the Windows event logthat have no effect on Application Agent operation. The following table liststhese events.

Server onwhichevent

occurred

When messageis output toevent log

Type Source EventID Message Log type

File Server,DatabaseServer, andBackupServer

The volume ismounted orunmounted.

Error VDS BasicProvider

1 Unexpected Failure.Error code:2@01010013

System log

Backupserver

A VSS backup isexecuted.

Error VDS BasicProvider


System log

Backupserver


Error VirtualDiskService


System log

Backupserver



1 Unexpected Failure.Error code:48F@02000018

System log

Backupserver



9 Unexpected providerfailure. Restarting theservice may fix theproblem. Errorcode:XXXXXXXX@YYYYYYYY

System log


Server onwhichevent

occurred



Backupserver


Error VDSDynamicProvider

10 The provider failedwhile storingnotifications from thedriver. The Virtual DiskService should berestarted.hr=80042505

System log

Backupserver


Error PlugPlayManager

12 The device "xxxxxxxx"disappeared from thesystem without firstbeing prepared forremoval.

System log

Backupserver


Error Disk 15 The device, xxxxxxxx,is not ready for accessyet.

System log

Backupserver


Warning ntfs 50 {Delayed Write Failed}Windows was unable tosave all the data for thefile. The data has beenlost.

System log

Backupserver


Warning disk 51 An error was detectedon device device pathduring a pagingoperation.

System log

Databaseserver andbackupserver

• A VSS backupis executed.

• A volume isplaced offlineafter a VSSbackup hasbeencompleted.

• The volume isunmountedduring a VSSrestoration.

Warning ftdisk 57 The system failed toflush data to thetransaction log.Corruption may occur.

System log

Databaseserver

A VSS restorationis performed.

Warning MicrosoftExchangeSearchIndexer

107 Exchange SearchIndexer has temporarilydisabled indexing of theMailbox Databasexxxxxxxx due to anerror xxxxxxxx.

Applicationlog

Backupserver


• Dynamicrecognition ofsecondaryvolumes is

Warning disk 157 Disk # has beensurprise removed

System log


Server onwhichevent

occurred



enabled, anda secondaryvolume isunmounted.

• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isconcealed.

Backupserver

Simultaneousbackups areexecuted in acascadeconfiguration.

Warning PlugPlayManager

257 Timed out sendingnotification of targetdevice change towindow of "VDSNotification ThreadHidden Window{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}"

System log

Backupserver


• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isunmounted.

• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isconcealed.

Warning disk 257 Disk # has beensurprise removed

System log

Backupserver


Warning PlugPlayManager

257 Timed out sendingnotification of targetdevice change towindow of "VDSNotification ThreadHidden Window{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}"

System log

Passivenode in aCCR env.


Error ESE 522 Microsoft.Exchange.Cluster.ReplayService(xxxx) Log Verifier exxxxx: An attempt to

Applicationlog


Server onwhichevent

occurred



and theSCR env.target

open the device name"xxx" containing "xxx"failed with system error5 (0x00000005):"Access is denied. ".The operation will failwith error -1032(0xfffffbf8).

SCR env.target


Error MicrosoftExchangeRepl

2104 Log file action LogCopyfailed for storage group"xxx". Reason:CreateFile("xxx") = 2

Applicationlog

Backupserver


Error ServiceControlManager

7034 The Logical DiskManager AdministrativeService serviceterminatedunexpectedly. It hasdone this xx time(s).

System log

Backupserver


Error ServiceControlManager

7034 The Virtual Disk Serviceservice terminatedunexpectedly. It hasdone this xx time(s).

System log

Backupserver

The OS isWindows Server2008 or 2012 andduring a VSSimport, COPY/COPY or PAIR/PAIR volumesother than thevolumes to beprocessed exist.

Error VSS 8193 Volume Shadow CopyService error:Unexpected errorcalling routine xxxx

Applicationlog

Backupserver

The OS isWindows Server2008 and 2012and during a VSSimport, COPY/COPY or PAIR/PAIR volumesother than thevolumes to beprocessed exist.

Error VSS 12289 Volume Shadow CopyService error: xxxx.

Applicationlog

Backupserver


Error VSS 12290 Volume Shadow CopyService warning:GetVolumeInformationW(\\?\Volume{ xxxxxxxx-xxxx-xxxxxxxx-xxxxxxxxxxxx}

Applicationlog


Server onwhichevent

occurred



\,NULL,0,NULL,NULL,[0x00000000], , 260)== 0x00000001. hr =0x00000000.

Backupserver


Error VSS 12290 Volume Shadow CopyService warning:GetVolumeInformationW(\\?\Volume{ xxxxxxxx-xxxx-xxxxxxxx-xxxxxxxxxxxx}\,NULL,0,NULL,NULL,[0x00000000], , 260)== 0x00000057. hr =0x00000000.

Applicationlog

Databaseserver andbackupserver


Warning VSS 12333 Volume Shadow CopyWarning: The providerhas reported a storageidentifier that is notsupported by VSS

Applicationlog

Backupserver

• A VSS backupis executed

• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isunmounted

• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isconcealed

Error DLMManager

32787 KAPL08019-E The path(xxxxxxxxx) detectedan error (0x00000000).(0x00000001)

Applicationlog

Backupserver



• Dynamicrecognition of

Error DLMManager

32790 KAPL08022-E A patherror occurred.ErrorCode = xxxxxxxxPathID = xx PathName= xx DNum = xxHDevName = xx

Applicationlog


Server onwhichevent

occurred



secondaryvolumes isenabled, anda secondaryvolume isconcealed

Backupserver



• Dynamicrecognition ofsecondaryvolumes isenabled, anda secondaryvolume isconcealed

Error DLMManager

32794 KAPL08026-E An erroroccurred on all thepaths of the LU. PathID= xx

Applicationlog

Troubleshooting when copy pairs are not recognizedIn an environment where Device Manager and CCI manage copy pairs, ifinformation about the existing copy pairs cannot be recognized afterrefreshing the configuration information, take the following actions to correctthe problem:

1. Go to Items to be checked on the pair management server on page7-15, to make sure that the configuration definition files for DeviceManager Agent and CCI are correct.

2. Go to Items to be checked from Device Manager GUI on page 7-16, tomake sure that information about hosts or pair management servers thatare managed by Device Manager server is correct.

3. Go to Items to be checked from Replication Manager GUI on page 7-18,to make sure that information about hosts that are managed by theReplication Manager server is correct.

Items to be checked on the pair management serverThis section describes how to make sure that the settings in the configurationdefinition files for Device Manager Agent and CCI are correct:


1. Installation of Device Manager Agent on page 7-162. Link between Device Manager server and Device Manager Agent on page

7-163. Properties of Device Manager Agent on page 7-164. Settings in the CCI configuration definition file on page 7-16

For details about commands to be executed on the pair management server,how to operate Device Manager Agent, and how to specify configurationdefinition files that are supported by Device Manager, see the HitachiCommand Suite Administrator Guide.

Installation of Device Manager Agent

Make sure Device Manager Agent is installed on both pair managementservers 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 serverusing the hdvmagt_setting command on the pair management server. Thiscommand displays information about the configured Device Manager server.If the link is incorrect, change the settings.

Properties of Device Manager Agent

Make sure Device Manager Agent properties (stored in the pair managementserver) are correct. For details about the properties to be specified, seeSetting up the prerequisite environment on page 3-3. If you change theproperties, restart Device Manager Agent.

Settings in the CCI configuration definition file

Make sure that the specified settings in the CCI configuration definition filesare correct, and the HORCM instances that correspond to these files can startwithout any problems. Also, make sure that parameter formats and specifiedsettings in the configuration definition files are supported by Device Manager.

Items to be checked from Device Manager GUIThis section describes how to check information about hosts (pairmanagement servers) that are managed by Device Manager using the DeviceManager GUI:

1. Recognition of Device Manager Agent on page 7-172. Recognition of the command device on page 7-173. Recognition of the replication configuration on page 7-174. Recognition of storage systems on page 7-18

For details about Device Manager GUI, see the Hitachi Command Suite Help.


Recognition of Device Manager Agent

Check the items below to make sure that Device Manager server correctlyrecognizes Device Manager Agent on a host or pair management server thatmanages existing copy pairs:

• Hosts or pair management servers that manage copy pairs are displayedin the host list.

• A button to refresh host information is displayed in the host propertieswindow.

If the above items are not displayed, Device Manager Agent and theconnection-target Device Manager server are not linked correctly. See Linkbetween Device Manager server and Device Manager Agent on page 7-16 tocorrect the problem.

Recognition of the command device

Check the following to make sure Device Manager server correctly recognizesthe command device that is allocated to the host or pair management server:

• In the host properties window, make sure that the last updated date andtime of LUs that correspond to the command device are displayed. If not,refresh the host information.

• If the last updated date and time are not changed, check the OS diskinformation on the pair management server to make sure that LUs thatcorrespond to the command device are correctly recognized by the OS.

Recognition of the replication configuration

Make sure that Device Manager server correctly recognizes the replicationconfiguration that is managed by a host or pair management server.

Note: On copy pairs that configure remote copies, you do not need to checkthis item.

Check the following:

• On the host (pair management server) properties window, make sure thatyou can click the button to view the pair information managed by thehost.

• On the window displayed by clicking the button to view the pairinformation, make sure that existing copy group names and copy pairnames are displayed.

If the button is not activated or the information is not displayed, refresh thestorage system information. If it cannot be updated, make sure that thesystem configuration and specified settings in the CCI configuration definitionfile are correct.


Recognition of storage systems

To ensure that Device Manager server correctly recognizes storage systemsthat comprise existing copy pairs, confirm that each storage system appearsin the list of storage systems. If not, register the storage system with theDevice Manager server.

Items to be checked from Replication Manager GUIIn the Pair Configuration view, select the pair management server thatmanages the existing copy pairs to make sure that information about theseitems are correct:

• The configuration definition file for CCI that exists on the pairmanagement server

• Copy groups that are defined in the CCI configuration definition file• Copy pairs that configure copy groups.

If the above items are not displayed correctly, refresh the configurationinformation for Device Manager server. For details, see the Hitachi ReplicationManager User Guide.

If a validation code is displayed in the instruction of list of configurationdefinition files in the Pair Configuration view, see the topic that explainsabout validation codes in the online help to check the cause and the action tobe taken.

Creation of TrueCopy Extended Distance or COW Snapshotcopy pairs fails (HUS100 Series)

This topic discusses conditions under which pair creation on the HUS Serieswill fail with the error message RPM-03327. Follow the instructions in theapplicable sub-section to resolve the problem.

Pool utilization

Creating a copy pair may fail when the replication data release thresholdvalue of a DP pool used for Copy-on-Write Snapshot or TrueCopy ExtendedDistance meet the following condition:

Pool utilization >= replication data release threshold - 5%

Configure the DP pool not to exceed the above threshold, and then create thecopy pair.

Difference data and management area

Creating a Copy-on-Write Snapshot or TrueCopy Extended Distance copy pairmay fail if both these conditions are true:


• The volume for which the copy pair is to be created is already being usedas a volume for a Copy-on-Write Snapshot or TrueCopy ExtendedDistance copy pair.

• The difference data and management area used for the existing copy pairare associated with different DP pools.

To create a copy pair under these circumstances, use the storage systemoperation management software (such as Hitachi Storage Navigator Modular2).

Specifying a DP pool

Creating a Copy-on-Write Snapshot or TrueCopy Extended Distance copy pairmay fail if both these conditions are true:

• The volume for which the copy pair is to be created is already being usedas a volume for a Copy-on-Write Snapshot or TrueCopy ExtendedDistance copy pair.

• A DP pool is specified other than the one associated with the existing copypair.

You must specify the same DP pool used for the existing copy pair.

Cascade configuration

If Replication Manager is used to create a Copy-on-Write Snapshot copy pair,the status of the pair volume changes from Pair to Split. As a result, if aTrueCopy Extended Distance secondary volume and a Copy-on-WriteSnapshot primary volume are simultaneously created for a cascadeconfiguration, the attempt to create a copy pair will fail.

Follow this procedure to create the cascade configuration:

1. Create a TrueCopy Extended Distance copy pair.2. Change the status of the TrueCopy Extended Distance copy pair to Split.3. Create a Copy-on-Write Snapshot copy pair.

Troubleshooting replica operationsThis section covers error conditions and log events that may occur and howto address them:

• Replica creation fails silently on page 7-20• Backup server is not recognized as a pair management server on page

7-20• Restoring a replica with roll-forward fails with error message RPM-11510

on page 7-20• Creating a replica fails with error message RPM-10006 on page 7-21• Creating a replica fails with event IDs 17, 1 and 10010 on page 7-21


• Disk status remains online after replica operation is complete on page7-21

Replica creation fails silentlyIf replica creation fails when there is not enough disk space to createtransaction log files, there may be no error messages displayed. To deletetransaction logs periodically, select Truncate Exchange transaction logfiles in the Execution Options of the Create Replica Wizard (2. Setup Options)page. When this option is selected, transaction log files will be automaticallydeleted every time a backup is performed.

Backup server is not recognized as a pair management serverIf Replication Manager does not recognize the backup server as a pairmanagement server, make sure that the CCI instance on the backup server isrunning before performing the following operations:

• Executing Setup Agent or Refresh Hosts• Executing Mount Replica or Unmount Replica.

Tip: Even if Replication Manager appears to recognize the backup server as apair management server, you should still confirm that the CCI instance on thebackup server is running if the following conditions are true:

• The configuration is a cluster configuration.• The backup server contains the configuration definition file on the

secondary machine, and no primary configuration file exists.

Restoring a replica with roll-forward fails with error messageRPM-11510

When restoring a replica with the roll-forward option, if the storage group torecover has more than 1,008 transaction log files, the restore and roll-forward will complete, but the information store will not be mounted and themessage RPM-11510 is output. Follow this procedure to complete the mountoperation:

1. Start the event viewer for the operating system on the database server.2. Confirm that the error log with the event source MSExchangeIS and the

Event ID 9518 are recorded. Open the properties for the error log, andconfirm that the description field reads Error 0xfffffd9a hasoccurred. If this event is recorded in the log, skip to step 4.

3. If the error log in step 2 is not recorded, confirm that an information logwith event source ESE, event ID is 302, and the description field readsDatabase engine normally completed the recovery steps. Alsocheck that this log is followed immediately by an information log withevent source ESE, event ID 101, and the description Database engine isstopped.


Note: If you do not find either of the error logs described in steps 2 and3, do not continue this procedure.

4. Start Exchange System Manager and view the properties of the storagegroup to be recovered. Check the location of the transaction logs as wellas the initial characters of the log file. The initial characters are E0n,where n is from 0 to 3.

5. Of the transaction log files in the storage group to be recovered, movethose not matching the description in step 4 to a new folder.

6. From the Exchange System Manager, mount the information store to berecovered.

7. Check that the information store is mounted, and then delete thetransaction log files moved in step 5.

Creating a replica fails with error message RPM-10006If different logical volumes are mounted at mount points in a hierarchicalrelationship, 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 andRPM-20062) will be output.

If this happens, only the lowest-level mount point can be specified forbackup, so if you want to specify multiple mount points for backup (includingdirectory mount points), create a configuration in which there is nohierarchical relationship between the mount points.

Creating a replica fails with event IDs 17, 1 and 10010If a backup operation fails, the status of the Windows Logical Disk ManagerAdministrative service will remain stopped, and Windows log entries withevent IDs 17, 1, and 10010 will be output. The backup attempt fails becausethe Logical Disk Manager Administrative service hangs up. If this happens,restart the backup server. After the restart, check the effect of the operationon the backup server.

Disk status remains online after replica operation is completeIn Windows Server 2008 and Windows Server 2012 environments, the diskstatus of secondary volumes on the backup server change to Offline after abackup operation is performed. However, note that if the operation fails, thestatus of the secondary volumes on the backup server might remain Online.If this happens, perform the following procedure to change the disk status ofsecondary volumes on the backup server to Offline:

1. Use the CCI command inqraid $Phys -CLI to check the disk numbers ofall secondary volumes that are the backup destinations.The disk numbers are shown in the DEVICE_FILE column.

2. Start the diskpart command.


3. To display the current disk statuses, enter list disk.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 inthe Status column, statuses of disks whose disk numbers correspond tothe disk numbers on the secondary volumes are Online.

4. For each secondary volume whose disk status is Online, perform thefollowing procedure:

a. Enter select disk disk-number.b. The following message is displayed: Disk disk-number is now the

selected disk.c. Enter offline disk.

The following message is displayed: DiskPart successfullyofflined the selected disk.

5. To display the current status of the disks, enter list disk.Make sure that the disk statuses of the secondary volumes are Offline inthe Status column.

6. Enter exit to end the diskpart command.


AVersion compatibility with other HCS

products

This appendix describes the compatibility between versions of ReplicationManager and other Hitachi Command Suite product versions.

□ Restrictions when Replication Manager and Device Manager versions differ

□ Restrictions when Replication Manager and Business Continuity Managerversions differ

Version compatibility with other HCS products A-1Hitachi Replication Manager Configuration Guide

Restrictions when Replication Manager and Device Managerversions differ

The following restrictions for configuring the Replication Manager system aredependent on the version of Device Manager that is installed on thecomponents (management server, pair management server, and hosts).

Table A-1 Restrictions when Replication Manager and Device Managerversions differ

Release Number Restriction

Device Manager Server or DeviceManager Agent 6.0 or earlier

The following information cannot be acquired:• License usage rate• DMLU status• Remote path listThe following functions are not supported:• License usage and alert settings• DMLU settings (addition and deletion)• Remote path settings (creation, editing, and

deletion)


The following functions are not supported:• Deletion of copy pairs related to remote paths• LDEV format output of configuration definition

files


Takeover and takeback operations are notsupported.


The following restrictions apply:• specifying CTGID manually with the Pair

Configuration Wizard is not supported• The maximum number of LDEVs that can be

managed for an open system; in the case ofMedium the number is 80,000, and in the caseof Large the number is 130,000

Device Manager Server or DeviceManager Agent 7.0.1 or earlier andrunning on open systems

The notification of when the Device Manager andReplication Manager configurations are notsynchronized and will not be properly executed.Instead, the notification that you shouldsynchronize the configuration will always bedisplayed, instead of only when necessary.


Mainframe system volume attributes may notdisplay correctly.


The DMLU capacity addition function for theHUS100 series is not supported.

Device Manager Server or DeviceManager Agent 7.4.1 or earlier

The following functions are not supported on opensystems:• Editing the group name using the Pair

Configuration Wizard

A-2 Version compatibility with other HCS productsHitachi Replication Manager Configuration Guide


• Specifying syncwait option using the ChangePair Status Wizard


The following functions are not supported:• Displaying and editing the system

configuration option• Displaying the mirror information• Editing the mirror option


The following functions are not supported:• Displaying and editing the path group ID of a

copy group using the Pair ConfigurationWizard

• Displaying the path group ID of a copy pair, orpath group ID defined in the configurationdefinition file


The following functions are not supported:• Managing more than 64 generations of Thin

Image copy pairs.


The following functions are not supported:• Pair management using global-active device.• Automatic user authentication for command

devices. (You must perform authenticationmanually using the raidcom command.)


The CTG setting for GAD copy groups is notsupported.


GAD 3DC delta resync configuration is notsupported.


You cannot specify a pair operation that splits thepair automatically after the pair is resynchronized(take snapshot) in the Change Pair Status Wizard.

Restrictions when Replication Manager and BusinessContinuity Manager versions differ

The following restrictions for configuring the Replication Manager system aredependent on the versions of Business Continuity Manager and MainframeAgent that are installed on the host pair management server.

Table A-2 Restrictions when Replication Manager and Business ContinuityManager versions differ


Business Continuity Manager orMainframe Agent 6.1 or earlier, that

The following functions are not supported:• Management and distribution of disk

configuration files using volume scans

Version compatibility with other HCS products A-3Hitachi Replication Manager Configuration Guide


are registered as informationsources

• Copy pair definitions• Changing of copy pair statuses

Business Continuity Manager 6.6.1or earlier

The creation, distribution, and editing of diskconfiguration definition files are not supported.

Business Continuity ManagerVersion 6.6.1 or earlier

Primary and secondary volume capacity checking(to determine if volume capacities match) whendefining copy pairs is not supported.

A-4 Version compatibility with other HCS productsHitachi Replication Manager Configuration Guide

BSupported functions and unsupported

configurations

This appendix provides information on functions and supported by ReplicationManager.

□ Supported paths for acquiring information and performing processing

□ List of tasks supported for each storage system

□ Unsupported configurations (open systems)

□ Unsupported configurations (mainframe systems)

Supported functions and unsupported configurations B-1Hitachi Replication Manager Configuration Guide

Supported paths for acquiring information and performingprocessing

The following table shows the relationship between Replication Managerserver functions and the supported paths for acquiring information andperforming processing:

Open Mainframe

HDvMServer HDvM Agent BCM Mainframe

Agent

Core functions

Acquiringreplicationconfigurationinformation

Open volume Y Y N N

Mainframevolume

N N Y Y

Acquiringreplicationstatus (pairstatus)

Open volume Y Y N N

Mainframevolume

N N Y Y

Acquiringreplicationstatus(remote copyperformanceinformation)

Open volume N Y N N

Mainframevolume

N N Y Y

Replication configuration support functions

Acquiring theprogramproductlicense forcopy

Configurationinformation

Y N N N

Status orusage

Y N N N

Acquiringstoragesystemconfigurationinformation

Configurationinformationand remotepath status

Y N N N

Journal orPool status orusage

N Y N N

Creating and deleting copypairs

N Y Y * N

Replication operation support functionality

Changing copy pair statuses N Y Y N

Legend

* - Only the pair definition function for creating a copy group definition file issupported. The creation of copy pairs is not supported.

B-2 Supported functions and unsupported configurationsHitachi Replication Manager Configuration Guide

List of tasks supported for each storage systemThe tasks supported by Replication Manager depend on the storage systemmodel. The following table lists the tasks supported for each storage system.

List of tasks supported for each storage system (enterprise-classstorage systems) (open systems)

Task

Support for each storage system

VSP G1000VSP G1500VSP F1500

VirtualStoragePlatform

UniversalStoragePlatform

V/VM

Replication Manager and resource settings

Registration and removal of informationsource, and acquisition of information

Y Y Y

Discovery of replication configurations Y Y Y

Volume scan -- -- --

Managing resources and sites Y Y Y

Preparation for replication (storage system settings)

Command device settings Y Y Y

DMLU settings -- -- --

Remote path settings Y Y Y

Pool settings Y Y Y

Journal group settings Y Y Y

V-VOL settings Y Y Y

Pair management server settings forsnapshot groups

Y Y N

Editing maximum initial copy activities(Universal Replicator)

Y Y N

Managing pair life cycle

Creating and editing of pair configurationdefinition

Y2 Y1,2 Y1

Changing the copy pair status (create,delete)3,4

Y2 Y2 Y

Changing the copy pair status (split,resync, restore, take snapshot)3

Y Y Y

Changing the copy pair status (takeover,force-split, swap, takeover-recovery(resync), takeover-recovery(recreate))3,4

Y2 Y2 Y

Managing application replicas


Task





V/VM

Creating and restoring an applicationreplica4,5

Y Y Y

Displaying pair monitoring and management status

Displaying My Copy Groups4 Y Y Y

Displaying the copy pair status Y Y Y

Displaying the copy pair setting Y Y Y

Displaying performance information Y Y Y

Monitoring Replication Manager operating status and troubleshooting

Setting monitoring conditions for copypair status4

Y Y Y

Setting performance monitoringconditions for each copy group4

Y Y Y

Setting performance monitoringconditions for each pool

Y Y Y

Setting performance monitoringconditions for each journal group4

Y Y Y

Setting monitoring conditions for copylicense usage4

Y Y Y

Automated read management ofrereported alerts4

Y Y Y

Monitoring detailed information for eachcopy pair and reporting alerts4

Y Y Y

Legend:

Y: Supported

N: Not supported

--: Not applicable

1. Not available for HAM pair.2. Not available for copy pairs defined in a device group.3. Available pair operations differ depending on the copy type. See the

Conditions for copy pair operations (basic versus advanced) section in theHitachi Command Suite Replication Manager User Guide for details.

4. Not available for copy pairs defined in a snapshot group.5. Not available for GAD pair.


List of tasks supported for each storage system (enterprise-classstorage systems) (mainframe systems)

Task





V/VM


Registration and removal of informationsource, and acquisition of information1

Y Y Y

Discovery of replication configurations Y Y Y

Volume scan Y Y Y

Managing resources and sites Y Y Y


Command device settings N N N

DMLU settings -- -- --

Remote path settings N N N

Pool settings -- -- --

Journal group settings N2 N2 N2

V-VOL settings -- -- --


Creating and editing of pair configurationdefinition

Y3 Y3 Y3

Changing the copy pair status (create,delete)4

Y3 Y3 Y3

Changing the copy pair status (split,resync, restore)4

Y Y Y

Changing the copy pair status (takeover,force-split, swap, takeover-recovery(resync), takeover-recovery(recreate))

N N N


Creating and restoring an applicationreplica

-- -- --


Displaying My Copy Groups Y Y Y

Displaying the copy pair status Y Y Y

Displaying the copy pair setting Y Y Y

Displaying performance information Y Y Y


Task





V/VM


Setting monitoring conditions for copypair status

Y Y Y

Setting performance monitoringconditions for each copy group

Y Y Y

Setting performance monitoringconditions for each pool

-- -- --

Setting performance monitoringconditions for each journal group

N N N

Setting monitoring conditions for copylicense usage

Y Y Y

Automated read management ofrereported alerts

Y Y Y

Monitoring detailed information for eachcopy pair and reporting alerts

Y Y Y

Legend:

Y: Supported

N: Not supported

--: Not applicable

1. LDEV label information cannot be acquired. Device Manager cannot setthe label.

2. Only displaying the list of journal groups is available.3. Creating copy pair is not supported.4. Available pair operations differ depending on the copy type. See the

Conditions for copy pair operations (basic versus advanced) section in theHitachi Command Suite Replication Manager User Guide for details.


List of tasks supported for each storage system (midrange storagesystems, VSP Gx00 models, VSP Fx00 models, and HUS VM)

Task


VSPGx00

modelsVSPFx00

models

HUS VM HUS100HitachiAMS200

0

HitachiAMS/W

MS

HitachiSMS


Registration andremoval of informationsource, and acquisitionof information

Y Y Y Y Y Y

Discovery of replicationconfigurations

Y Y -- -- -- --

Volume scan -- -- -- -- -- --

Managing resourcesand sites

Y Y Y Y Y Y


Command devicesettings

Y Y Y Y Y Y

DMLU settings -- -- Y Y Y --

Remote path settings Y Y Y Y Y --

Pool settings Y Y -- Y Y --

Journal group settings Y Y -- -- -- --

V-VOL settings Y Y N N N N

Pair managementserver settings forsnapshot groups

Y Y -- -- -- --

Editing maximum initialcopy activities(Universal Replicator)

Y Y -- -- -- --


Creating and editing ofpair configurationdefinition

Y1,2 Y1,2 Y Y Y Y

Changing the copy pairstatus (create,delete)3,4

Y2 Y2 Y Y Y Y

Changing the copy pairstatus (split, resync,restore, takesnapshot)3

Y Y Y Y Y Y


Task


VSPGx00

modelsVSPFx00

models


0

HitachiAMS/W

MS

HitachiSMS

Changing the copy pairstatus (takeover, force-split, swap, takeover-recovery(resync),takeover-recovery(recreate))3,4

Y2 Y2 Y Y Y N


Creating and restoringan application replica4,5

Y Y Y Y Y N


Displaying My CopyGroups4

Y Y Y Y Y Y

Displaying the copypair status

Y Y Y Y Y Y

Displaying the copypair setting

Y Y Y Y Y Y

Displaying performanceinformation

Y Y Y Y Y --


Setting monitoringconditions for copy pairstatus4

Y Y Y Y Y Y

Setting performancemonitoring conditionsfor each copy group4

Y Y Y Y Y --

Setting performancemonitoring conditionsfor each pool

Y Y Y Y Y --

Setting performancemonitoring conditionsfor each journal group4

Y Y -- -- -- --

Setting monitoringconditions for copylicense usage4

Y Y -- -- -- --

Automated readmanagement ofrereported alerts4

Y Y Y Y Y Y


Task


VSPGx00

modelsVSPFx00

models


0

HitachiAMS/W

MS

HitachiSMS

Monitoring detailedinformation for eachcopy pair and reportingalerts4

Y Y Y Y Y Y

Legend:

Y: Supported

N: Not supported

--: Not applicable

1. Not available for HAM pair.2. Not available for copy pairs defined in a device group.3. Available pair operations differ depending on the copy type. See the

information on conditions for copy pair operations (basic versusadvanced) in the Hitachi Command Suite Replication Manager User Guidefor details.

4. Not available for copy pairs defined in a snapshot group.5. Not available for GAD pair.

Unsupported configurations (open systems)The following is a list of unsupported open systems pair configurations. ThePair Configuration Wizard cannot be initiated to perform operations to modifythese configurations. The copy group definition file should either be editeddirectly, or use storage management software other than Hitachi CommandSuite (such as Storage Navigator or Storage Navigator Modular) to define theconfiguration. It is impossible to recover from these configurations usingReplication Manager.

Unsupportedconfiguration

Requirement forconfiguration

Alternative configurationto implementrequirement

A copy group defined inHORCM files with a singlecopy group definition thatincludes virtual commanddevice settings.

To modify all the pairs in thecopy group at once.

Each pair modification mustbe executed separately.

The number of pairs in thechild group of a cascade

To create a backup of onlysome volumes.

None.





configuration is greater thanthe number of pairs in theparent group.

Pairs in the copy group usethe same P-VOL.

To set up an SI multi-targetconfiguration.

Use different copy groupsfor each S-VOL if there arecopy pairs using the sameP-VOL in the copy group.

Pairs in the copy group usethe same S-VOL.

None None

There are different types ofcopy pairs in the same copygroup.

The storage systems for theprimary volumes in thesame copy group aredifferent.

To perform an operationsimultaneously on pairs thatspan multiple storagesystems.

Unify the P-VOLs using thesame storage system intothe same CTG*.

The storage systems for thesecondary volumes in thesame copy group aredifferent.

Unify the S-VOLs using thesame storage system intothe same CTG*.

A TCE pair with different DPPool IDs for differential andmanagement data storedboth in primary as well assecondary site.

The copy group definitionfile has to be createdmanually. (It is not possibleto restore it with ReplicationManager.)

None

A copy pair is defined byboth a snapshot group and acopy group.

To share a copy pair with adifferent type of group.

None

The following virtual storagemachine-relatedconfigurations areunsupported:Local copy• A copy pair comprising

volumes from differentvirtual storagemachines.

• A copy pair comprisingvirtual storage machinevolumes and physicalstorage systemvolumes.

• A copy groupcomprising multiplecopy pairs fromdifferent virtual storagemachines.

None None





• Copy pairs from avirtual storage machineand a physical storagesystem that coexist in acopy group.

Remote copy• A virtual storage

machine volume andphysical storage systemvolume coexist in acopy topology, and acopy pair comprisingonly physical storagesystem volumes existsin the topology.

• A copy pair comprisinga virtual storagemachine volume andphysical storage systemvolume exist in a copygroup, and differentvirtual storage machinevolumes exist in thecopy group.

The following configurationsare unsupported for GADpair management:• Virtual IDs of primary

and secondary volumesof the pair are notidentical.

• The attribute of thesecondary volume isGAD Reserved, and itsstatus is simplex, andthe primary orsecondary volumebelongs to a differentvirtual storage machine.

None None

Legend:

*: When primary volumes and secondary volumes in the same copy groupbelong to different storage systems, it is necessary to create CTGs withvolumes that have the same combination of primary and secondary storagesystems.


Unsupported configurations (mainframe systems)The following are a list of unsupported mainframe pair configurations. ThePair Configuration Wizard cannot be initiated to perform operations to modifythese configurations. The copy group definition file should be edited directlybecause it is impossible to recover from these configurations usingReplication Manager.




The number of pairs at thecascade source and cascadedestination is different.


None

The number of pairs inmulti-target configurationsis different.

Pairs in the copy group usethe same P-VOL.

To set up an SI multi-targetconfiguration.

Use different copy groupsfor each S-VOL if there arecopy pairs using the sameP-VOL in the copy group.

Pairs in the copy group usethe same S-VOL.

None None

There are different types ofcopy pairs in the same copygroup.

The storage systems for theprimary volumes in thesame copy group aredifferent.

To perform an operationsimultaneously on pairs thatspan multiple storagesystems.

Unify the P-VOLs using thesame storage system intothe same CTG*.

The storage systems for thesecondary volumes in thesame copy group aredifferent.

Unify the S-VOLs using thesame storage system intothe same CTG*.

The cascade configurationconsists of a container and acopy group.

To perform an operationsimultaneously on pairs thatspan multiple storagesystems, withoutmaintaining consistency.

Divide the destination copygroups into multiple CTGsaccording to the cascadesource CTGs.

The cascade destinationcontains multiple copygroups.


Create CTGs in the cascadesource according to thecascade destination copygroups. Pairs in the cascadesource must belong to anyCTG.

Legend:

*: When primary volumes and secondary volumes in the same copy groupbelong to different storage systems, it is necessary to create CTGs with


volumes that have the same combination of primary and secondary storagesystems.



Acronyms and Abbreviations

The following acronyms and abbreviations appear in this guide.

A

ASCIIAmerican Standard Code for Information Interchange

B

BCMBusiness Continuity Manager

C

CHAPChallenge Handshake Authentication Protocol

C/TConsistency Time

CCICommand Control Interface

CLICommand Line Interface

CNCommon Name

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Acronyms-1Hitachi Replication Manager Configuration Guide

CPUCentral Processing Unit

CUControl Unit

D

DEVNDEVice Number

DITDirectory Information Tree

DKCDisK Controller

DNDistinguished Name

DNSDomain Name System

F

FCFibre Channel

FC-SPFibre Channel Security Protocol

FQDNFully Qualified Domain Name

FTPFile Transfer Protocol

G

GUIGraphical User Interface



H

HDvMHitachi Device Manager

HRpMHitachi Replication Manager

HTMLHyperText Markup Language

HTTPHyperText Transfer Protocol

HTTPSHyperText Transfer Protocol Security

I

IPInternet Protocol

IPFItanium® Processor Family

iSCSIInternet Small Computer System Interface

J

JDKJava Development Kit

L

LANLocal Area Network

LDAPLightweight Directory Access Protocol



LDEVLogical DEVice

LULogical Unit

LUNLogical Unit Number

M

MCUMain Control Unit

MFAMainframe Agent

MIBManagement Information Base

N

NATNetwork Address Translation

NICNetwork Interface Card

NTPNetwork Time Protocol

O

OSOperating System

P

PAPPassword Authentication Protocol



PPRCPeer-to-Peer Remote Copy

R

RADIUSRemote Authentication Dial In User Service

RCURemote Control Unit

RDNRelative Distinguished Name

RFCRequest For Comments

S

SANStorage Area Network

SNMPSimple Network Management Protocol

SPService Pack

SSLSecure Sockets Layer

SSOSingle Sign-On

SVGASuper Video Graphics Array

SVPSerVice Processor



T

TCPTransmission Control Protocol

TLSTransport Layer Security

U

UACUser Account Control

URLUniform Resource Locator

V

VCSVeritas Cluster Server

W

WSFCWindows Server Failover Clustering



Glossary

This glossary defines the special terms used in this document. Click the desired letter belowto display the glossary entries that start with that letter.

#

3DC multi-target configurationA configuration in which, in addition to the local site, a connection is establishedbetween a nearby remote site and a distant remote site and TrueCopy and UniversalReplicator are used to copy storage system volumes among the three sites (called datacenters). Such a configuration provides support for disaster recovery through the use ofdata at the distant remote site.If the delta resync function is used between the nearby and distant remote sites,journal-copying of only the minimum data required is performed following a failure,which minimizes the recovery time.

A

Application AgentSoftware that allows Replication Manager to perform replica operations on database andbackup servers where Application Agent is installed.

application replicaA database backup managed as a series of secondary volumes that can be createdmanually or on a scheduled basis. Replicas can be mounted and dumped to tape usingscripts executed through Replication Manager.In this document, creating a replica or backup refers to creating a replica usingApplication Agent.


Glossary-1Hitachi Replication Manager Configuration Guide

B

batch collection command for maintenance informationSoftware that collects necessary information, such as log files and properties files thatare related to a problem that cannot be resolved at the user level, for forwarding tocustomer support.

BCM (Business Continuity Manager)Software used to control a storage system from a host in a mainframe system. By usingBusiness Continuity Manager to issue commands from the host to the storage system,you can acquire copy pair configuration and status information. Replication Managermanages copy pair configurations and statuses in conjunction with Business ContinuityManager.

C

cascade structureA structure of consecutive copy pairs. In a cascade structure, the secondary volume ofone copy pair is the primary volume of another copy pair. This volume is called asecondary/primary volume (SP-VOL).

CCICommand Control Interface. Software used to control volume replication functionality(such as TrueCopy or ShadowImage) by means of commands issued from a host to astorage system. A command device must be set up in the storage system to enable thestorage system to receive commands from CCI.In an open system, Replication Manager uses the CCI configuration definition files tomodify copy pair configurations and to acquire configuration information. Copy pairmodification processing, such as splitting and re-synchronizing copy pairs, is executedon the storage system using CCI.

cluster configurationIn a Replication Manager operating environment, the term cluster configuration refers toa configuration that consists of an executing node and a standby node, each of whichincludes a duplicate management server.

cluster softwareSoftware installed on management server nodes to boost overall availability byduplicating management servers as a cluster system. Available software depends on theOS that runs on the management server.

consistency groupAn 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 ismandatory for asynchronous remote copy, but is not mandatory for local copy.



Consistency groups are used in TrueCopy, Universal Replicator, Thin Image, or global-active device to maintain integrity of the update order for volumes.

copy groupA group of copy pairs. You can perform operations, such as modifying pair statuses, onall the copy pairs in the group.

Copy-on-Write SnapshotSoftware used to duplicate volumes in a single storage system. Copy-on-Write Snapshotduplicates differential data in a data pool. The secondary volume is a virtual volume thatconsists of the primary volume and the differential data. By duplicating only thedifferential data, Copy-on-Write Snapshot can copy data in a very short time as well asreduce the capacity required of the volume used for duplication. For more information,see the Copy-on-Write Snapshot manuals.

copy pairDenotes a primary and secondary volume pair linked by the volume replicationfunctionality of a storage system. Also called a pair volume. In this manual, copy pair issometimes referred to simply as pair.

copy pair stateA value that represents the status of both a primary volume and a secondary volume.The copy pair state displayed in Replication Manager corresponds to the copy pair statusdisplayed in prerequisite products (such as Device Manager, CCI, and BusinessContinuity Manager) and in storage system operation management software (such asStorage Navigator and Storage Navigator Modular).

copy pair statusA value that represents the status of a copy pair. Six status values are defined inReplication Manager: error, suspend, copying, sync, simplex, and unknown. Eachstatus is indicated by an icon. The copy pair status is determined by the combination ofthe copy pair states of the primary and secondary volumes. Also called pair status.

copy progressProgress status of the volume replication functionality executed by the storage system.Replication Manager displays the copy progress, which depends on the copy pair status,for items that are Active or Inactive. For Active items, the copy progress is displayedwhen the copy pair status is copying or sync. For Inactive items, the copy progress isdisplayed when the copy pair status is error or suspend.

CU (Control Unit)A virtual control unit created in an enterprise-class storage system. (Also known as aCU image.) The LDEVs created in a storage system are connected to a single CU, and anumber is assigned to each CU for identifying its LDEVs. Therefore, volumes (LDEVs) ina storage system are specified by the CU number (CU#) and LDEV number.



D

DAD (Device Address Domain)A DAD is a group of volumes that is managed by Business Continuity Manager. Volumesare registered in a DAD during a volume scan (discovery) by Business ContinuityManager. Depending on the type of volume scan, volumes are assigned the local DAD,Non Gen'ed DAD, or remote DAD attribute.

DAD IDA name that identifies a DAD.

delta resyncA status in which synchronization processing is performed by copying differential data toa Universal Replicator copy pair in which part of the copy pair exists on the local siteand part exists on a remote site in a 3DC Multi-Target configuration.

Device ManagerSoftware that enables integrated management of resources and the hardwareconfiguration of storage systems. Device Manager can be used to operate and manage asystem consisting of multiple Hitachi storage systems.

DEVN (Device Number)A device number that is assigned to identify an LDEV when it is being used by amainframe system. A DEVN is expressed as a 4-digit hexadecimal number.

Dummy DEVNA dummy DEVN is assigned by the user during a Non Gen'ed scan or remote scan. Thisinformation allows Business Continuity Manager to manage volumes to which no DEVNshave been assigned by the mainframe host.

G

GADGlobal-active device. A high-availability solution for Hitachi VSP G1000, VSP G1500,VSP F1500, VSP Gx00 modelsi, and VSP Fx00 models storage systems. A GADconfiguration comprises mirrored volumes that accept read/write I/O on both the mainand reserve sides. For complete information on configuration requirements andmanagement procedures for global-active device configurations, see the Hitachi VirtualStorage Platform G1000 Global-Active Device User Guide and the Hitachi CommandSuite User Guide.

Gen’ed VolumeA volume recognized by a mainframe host.



H

Hitachi Command Suite Common ComponentA component that bundles common functions used by Hitachi Command Suite products.Installed as part of Replication Manager, this component provides functions such assingle logon, integrated output of logs, commands for starting and stopping services, acommon GUI interface, and more.

host storage domainA group defined in Device Manager that is used to strengthen security of volumes instorage systems. By associating and grouping hosts and volumes by storage systemport, host storage domains can be used to restrict access from hosts to volumes.Device Manager defines the host groups set up with the storage system LUN securityfunction as host storage domains. Host storage domains for storage systems that do nothave host groups are defined in the same manner as if they had been set with the LUNsecurity function.

I

information sourceReplication Manager manages information about the copy pairs managed by instancesof Device Manager server, instances of Business Continuity Manager, instances ofMainframe Agent, or Application Agent installed at a number of different sites. Oncethese are registered in Replication Manager as such, these programs provideinformation to Replication Manager and are called information sources.

L

LDEV (Logical DEVice)A volume created in a storage system; it is called an LDEV (logical device) in bothmainframe and open systems.

LU (Logical Unit)A volume created in a storage system - known as an LU (logical unit) in an opensystem. Volumes created in a midrange storage system, however, are called an LDEV inReplication Manager.

LUN (Logical Unit Number)A management number assigned to an LU in a storage system. A LUN is a numberassigned to identify an LU for the port in the storage system to which the LU isconnected, either by the port or by the host group assigned to the port. An open systemhost uses a LUN to access a particular LU.



M

Mainframe AgentSoftware used to acquire information about mainframe system hosts and storagesystems. In conjunction with Mainframe Agent, Replication Manager monitorsconfiguration and status information about copy pairs created using PPRC.

MIB (Management Information Base)A database that defines the structure of information used by SNMP. The MIB used forReplication Manager defines the information set for alerts, such as monitored targets,conditions, and messages.

multiple subchannel setsTo resolve the problem of insufficient subchannels in a large-scale system configuration,this z/OS function identifies multiple subchannel sets from one host using a 64Kaddressable device (subchannel) as one set.

multi-target configurationA copy pair configuration with a one-to-many relationship between the primary andsecondary volumes. Information from one volume is copied to multiple volumes.

N

Non-Gen’ed VolumeA volume that is not recognized by a mainframe host.

Non-Gen’ed ScanA volume scan that can be performed on Non Gen'ed volumes within the site whereBusiness Continuity Manager resides. The Non Gen'ed DAD attribute is assigned to thedisk configuration definition file in which the discovered volumes are stored.

P

pairIn this manual, pair means copy pair.

pair statusIndicates the current status of the copy pair. Replication Manager uses six statusvalues: error, suspend, copying, sync, simplex, and unknown. A pair status is alsocalled copy pair status.



paired volumeDenotes a primary and secondary volume pair linked by a volume replicationfunctionality of a storage system. Also called a copy pair. In this manual, copy pair issometimes written simply as pair.

physical IDAn ID associated with a physical resource as opposed to a virtual one. See virtual ID.

prefixThe prefix portion of a copy group definition file created by Business Continuity Manageror Mainframe Agent. Copy group definition files are created individually by prefix, soReplication Manager uses this prefix as a unique name to identify copy group definitionfiles created by Business Continuity Manager or Mainframe Agent.

P-VOL (primary volume)The source volume that is copied to another volume using the volume replicationfunctionality of a storage system.

property filesGeneric term for the files that define a Replication Manager operating environment. TheReplication Manager operating environment can be modified by changing theappropriate property files.

Q

Quorum DiskA GAD configuration includes a quorum disk to determine the owner node in case offailure of the primary or secondary storage system, allowing operations to continuewithout interruption.

R

refreshThe term refresh refers to updating the database that is maintained by ReplicationManager by using the most recent information. This database stores copy pairconfiguration information and copy pair status information obtained from DeviceManager servers, Device Manager Agent, Business Continuity Manager, MainframeAgent, and Application Agent.

remote pathA logical path linking storage systems that is used for remote copying (replication ofvolumes between storage systems). In this manual, logical path is a generic term for apath that links the local system with the remote system in an enterprise-class storagesystem, as well as linking the local system with the remote system in a midrangestorage system.



Remote ScanA volume scan that can be performed on Non Gen'ed volumes outside the site whereBusiness Continuity Manager resides. The remote DAD attribute is assigned to the diskconfiguration definition file in which the discovered volumes are stored.

RMIRemote Method Invocation.

S

SP-VOL (secondary-primary volume)The volume located in the middle of a cascade structure, when a cascade structure isused by the volume replication functionality of a storage system. Indicates thesecondary volume in an upper level copy pair or the primary volume in a lower levelcopy pair.

S-VOL (secondary volume)The copy destination volume of two volumes that are associated in a copy pair by astorage system volume replication functionality.

ShadowImageSoftware used to duplicate volumes in a single storage system. ShadowImageduplicates all data on a volume. The fact that ShadowImage duplicates all data on avolume means that the data can be restored, even if the primary volume has beendamaged or destroyed. For more information, see the ShadowImage manuals.

Snapshot GroupA group of pairs created using Copy-on-Write Snapshot/Thin Image. Use of a snapshotgroup allows the same operation to be applied to more than one pair at a time. Likedevice groups, snapshot groups are managed in the storage system rather than theconfiguration definition file.

systemAn external storage system connected to a host.

summary pair statusBy displaying only the summary copy pair status of the copy groups that contain copypairs, Replication Manager allows users to quickly check copy pair statuses. ReplicationManager determines the summary copy pair status for each copy function (such asShadowImage and TrueCopy) in turn.



T

Thin ImageSoftware that has Copy-on-Write Snapshot functionality as well as Copy after Writefunctionality installed on Virtual Storage Platform, VSP G1000, VSP G1500, VSP F1500,VSP Gx00 models, VSP Fx00 models, or HUS VM storage systems. Thin Image creates aThin Image pool that adapts the DP pool feature as a data pool. If necessary, you canalso create the volume which is copied data of an entire volume instead of just thedifferential data. For details, see the Thin Image documentation.

TrueCopySoftware that duplicates volumes between storage systems. TrueCopy duplicates alldata on the volumes. Three types of TrueCopy are provided: synchronous TrueCopySync, asynchronous TrueCopy Synchronous Async, and asynchronous TrueCopySynchronous Extended Distance. For more information, see the TrueCopy manuals.

U

Universal ReplicatorSoftware that asynchronously duplicates multiple volumes between storage systems.Universal Replicator temporarily stores differential data on a journal volume and thenduplicates the data. Universal Replicator can duplicate data on remote sites; it can alsobe used to create 3DC multi-target and cascade configurations among multiple sites.For more information, see the Universal Replicator manuals.

V

VDI meta fileA file output when you back up an SQL server database containing the configurationinformation. The VDI meta file is used for database restoration.

virtual IDResources can be assigned virtual IDs to enable migration without having to stop theresource. For more information, refer to the Hitachi Command Suite User Guide.

virtual storage machineA virtual storage system that allows multiple resource groups to be treated as a singledevice. For more information, refer to the Hitachi Command Suite User Guide.

volumeA collective name for the logical devices (LDEVs) and logical units (LUs) that are createdin a storage system.



volume replication functionalityA generic term used to refer to functionality used to perform high-speed duplication ofvolumes in storage systems. This functionality allows volumes to be duplicated fromsoftware, such as ShadowImage or TrueCopy, that is loaded in the storage system. Thissoftware can be used once the license for it has been registered.

VSS ProviderA general name for software that provides the volume copy function used by ApplicationAgent.



Index

A

Administrator privileges (UAC) 5-2agent.logger.properties 4-23agentif.properties file 5-13Application Agent

and CCI 4-12cluster configuration 4-14described 4-2error log options 4-23installing 4-10log files 4-20, 7-6, 7-7maximum number 4-6port numbers 4-21reinstalling 4-6service 4-22troubleshooting 7-5

audit event 6-9audit log

event categories 6-9

B

base.properties file 5-15base.repositry.synchronize.polling 5-15BCM Agent 2-16, 2-18, 2-37bcmif.properties file 5-12Business Continuity Manager (BCM) 2-16, 2-17,2-37

version differences A-3

C

CCI 2-12, 4-13

checking operation statusReplication Manager 5-4

commandhcmds64getlogs 7-3

Common Agent service 4-12, 4-22Copy Controller service 4-12, 4-22Core functions B-2

open versus mainframe B-2

D

data collectionin mainframe systems 2-36in open system 2-34

Device Manager 2-12, 2-17version differences A-2

Device Manager agent 2-12drmjobsch.exe command 4-14DRMVSSServer 4-21dynamic recognition 4-6

E

Error 0xfffffd9a has occurred 7-20error message

RPM-03327 7-18RPM-10006 7-21RPM-11510 7-20RPM-20062 7-21

event ID 9518 7-20event IDs 17, 1 and 10010 7-21

Index-1Hitachi Replication Manager Configuration Guide

F

firewallexception list (Application Agent) 4-12exceptions (Replication Manager) 2-32

H

hcmds64link command 3-8Hitachi Command Suite Common Component 2-12,2-17HORCM environment variables 4-5host 2-11host (pair management server) 2-16, 2-28hrpmap_getras command 7-8

I

information source Glossary-5infrastructure

mainframe 3-6open systems 3-5

inqraid $Phys -CLI command 7-21

L

LDEVmaximum number 2-31

link menu 3-8log file

log amount of data 5-11logger.properties file 5-8

M

mainframeconfigurations not supported B-12

Mainframe Agent 2-17mainframe configuration 2-13management client 2-10, 2-15, 2-28management server 2-10, 2-15maximum

copy pairs 2-30LDEVs 2-31resources 2-29

N

networksecurity 6-2

O

open system configuration 2-2open systems

configurations not supported B-9

P

pair configurationunsupported, mainframe B-9, B-12

Pair Configuration Wizardunsupported configurations, mainframe B-9,B-12

pair management serverdescribed 2-10

physical ID 2-19port numbers

firewall exceptions 2-32properties file 5-5

agentif.properties 5-13base.properties 5-15bcmif.properties 5-12logger.properties 5-8RpMCLI.properties 5-18serverstorageif.properties 5-12

protection function 4-13

R

replica operationsconfigurations 2-25defined 1-3disk status remains online 7-21out of disk space 7-20transaction logs 7-20troubleshooting 7-19

Replication Manager 2-12, 2-17and BCM versions A-3and Device Manager versions A-2checking operation status 5-4standby configuration 2-28stopping 5-3

RM Shadow Copy 7-6


roll-forward option 7-20RPM-03327 error message 7-18RPM-10006 error message 7-21RPM-11510 error message 7-20RPM-20062 error message 7-21RpM.properties file 5-18

S

securitymanagement 6-1network 6-2

serverstorageif.properties file 5-12settings

properties file 5-5standby configuration 2-28stopping

Replication Manager 5-3storage system 2-11, 2-16system configuration

for mainframe system 2-13for open system 2-2

system limits 2-29

T

troubleshooting 7-1maintenance information 7-3resolving errors 7-2

U

UAC 5-2unsupported configurations B-9, B-12

V

virtual ID 2-19virtual storage machine 2-19VSS Provider

log files 7-6, 7-7



Hitachi Replication Manager Configuration Guide

Hitachi Vantara Corporate Headquarters2845 Lafayette StreetSanta Clara, CA 95050-2639 USAwww.HitachiVantara.comcommunity.HitachiVantara.com

Regional Contact InformationAmericas: +1 866 374 5822 or [email protected], Middle East and Africa: +44 (0) 1753 618000 or [email protected] Pacific: +852 3189 7900 or [email protected]

https://www.linkedin.com/company/hitachi-vantara

https://twitter.com/hitachivantara

https://www.facebook.com/HitachiVantara

https://www.youtube.com/user/HDScorp

Documents

Hitachi Command Suite Replication Manager