Replication Manager Configuration Guide

Transcription

Hitachi Command Suite
Replication Manager
Configuration Guide
Document Organization
Product Version
Getting Help
Contents
MK-98HC151-23
© 2014, 2015 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 photocopying and recording, or stored in a database or retrieval
system for any purpose without the express written permission of Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and
assumes no responsibility for its use. This document contains the most current information available
at the time of publication. When new or revised information becomes available, this entire
document will be updated and distributed to all registered users.
Some of the features described in this document might not be currently available. Refer to the most
recent product announcement for information about feature and product availability, or contact
Hitachi Data Systems Corporation at https://portal.hds.com.
Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of
the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is
governed by the terms of your agreements with Hitachi Data Systems Corporation.
Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries. Hitachi
Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and
other countries.
Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,
Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are
registered trademarks of Hitachi Data Systems. AIX, AS/400, DB2, Domino, DS6000, DS8000,
Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390,
System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered
trademarks or trademarks of International Business Machines Corporation.
All other trademarks, service marks, and company names in this document or website are
properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
Notice on Export Controls. The technical data and technology inherent in this Document may be
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to
obtain licenses to export, re-export, or import the Document and any Compliant Products.
ii
Hitachi Replication Manager Configuration Guide
Contents
Preface.................................................................................................. ix
Intended audience..................................................................................................... x
Product version..........................................................................................................x
Release notes............................................................................................................ x
Document organization...............................................................................................x
Referenced documents.............................................................................................. xi
Document conventions..............................................................................................xii
Convention for storage capacity values......................................................................xiii
Accessing product documentation............................................................................. xiv
Getting help............................................................................................................ xiv
Comments.............................................................................................................. xiv
1 Overview of Replication Manager........................................................... 1-1
About Replication Manager...................................................................................... 1-2
Features.......................................................................................................... 1-3
Replication Manager operations roadmap................................................................. 1-4
2 Replication Manager system configurations and requirements.................. 2-1
Replication Manager system configurations...............................................................2-2
Configurations for open systems........................................................................ 2-2
Open system components........................................................................2-7
Configurations for mainframe systems..............................................................2-11
Mainframe system components.............................................................. 2-13
Mainframe Agent versus BCM Agent....................................................... 2-16
Prerequisites for managing copy pairs on mainframe systems using CCI............. 2-16
Prerequisites for data migration using virtual IDs (VSP and HUS VM).................. 2-17
Prerequisites for data migration using virtual IDs (VSP G1000)...........................2-17
Prerequisites for managing global-active device copy pairs.................................2-19
Prerequisites for managing copy pairs using snapshot groups............................ 2-20
Mainframe pairs and Device Manager Agent..................................................... 2-20
Configurations for mainframe monitoring..........................................................2-20
Virtual command device requirements for managing copy pairs..........................2-21
Specifying port numbers for pair management servers............................. 2-23
Configurations for replica management............................................................ 2-23
Components for replica management......................................................2-25
iii
Replication Manager in standby configuration................................................... 2-26
System requirements.............................................................................................2-27
System requirements for the management server............................................. 2-27
Operating systems.................................................................................2-27
Server specifications.............................................................................. 2-32
Virtual memory requirements................................................................. 2-33
Resource Limits.....................................................................................2-35
Maximum number of copy pairs..............................................................2-35
Maximum number of LDEVs................................................................... 2-36
Log data and number of copy pairs.........................................................2-37
System requirements for the management client...............................................2-37
Required memory for management clients.............................................. 2-39
System requirements for hosts and pair management servers ........................... 2-39
Requirements for open systems..............................................................2-40
CCI version requirement........................................................................ 2-40
CCI version and consistency group support............................................. 2-40
Functional limitations when software versions do not match..................... 2-40
Requirements for mainframe systems..................................................... 2-41
Supported storage systems.................................................................... 2-42
Firewall exceptions................................................................................................2-42
How Replication Manager collects data................................................................... 2-45
Data collection in open systems....................................................................... 2-45
Data collection in mainframe systems...............................................................2-47
3 Setting up Replication Manager..............................................................3-1
Overview................................................................................................................3-2
Concerning upgrade installations..............................................................................3-2
Items to be checked after upgrading Replication Manager................................... 3-2
Setting up the prerequisite environment................................................................... 3-3
Open systems environment............................................................................... 3-5
Mainframe systems environment........................................................................3-6
Application replica environment......................................................................... 3-8
Adding a link menu to the GUI display .....................................................................3-8
hcmds64link command options.......................................................................... 3-8
Creating a user-defined application file...............................................................3-9
4 Setting up Application Agent..................................................................4-1
About Application Agent.......................................................................................... 4-2
Application Agent functions............................................................................... 4-2
System requirements and supported environments................................................... 4-3
Application Agent system requirements.............................................................. 4-3
Host OS and database server requirements...............................................4-4
Database and backup server requirements................................................4-7
Additional server requirements............................................................... 4-12
VSS Provider requirements.....................................................................4-16
Storage systems requirements................................................................4-17
Cluster support............................................................................................... 4-18
Cluster considerations............................................................................4-19
Virtual environments supported by Application Agent...............................................4-20
VMware ESX/ESXi Server.................................................................................4-20
Windows Server Hyper-V.................................................................................4-22
iv
Hyper-V Live Migration.................................................................................... 4-24
Virtual memory required for Application Agent on a virtual machine of Windows
Server Hyper-V ..............................................................................................4-24
Application Agent installation location..................................................................... 4-25
Application Agent installation path restrictions.................................................. 4-25
If you plan to install Application Agent on the management server..................... 4-25
Installing Application Agent....................................................................................4-26
Adding Application Agent to the Windows Firewall Exception list...............................4-28
Application Agent and CCI..................................................................................... 4-28
Command line interface for CCI....................................................................... 4-28
Protection function of CCI................................................................................4-29
Using CCI to configure pair volumes.................................................................4-29
Device Manager and CCI................................................................................. 4-29
Starting and stopping CCI................................................................................4-29
Settings for Application Agent in a cluster configuration........................................... 4-29
Application Agent and Replication Manager log output............................................. 4-31
Changing Application Agent port numbers...............................................................4-31
Starting and stopping the Application Agent Services............................................... 4-32
Copy Controller service....................................................................................4-32
Common Agent service....................................................................................4-32
Setting error logging options for Application Agent.................................................. 4-33
5 Operating the management server.........................................................5-1
About executing commands on the management server............................................ 5-2
User permissions.............................................................................................. 5-2
Setting up the PATH environment variable in Linux............................................. 5-2
Starting and stopping Replication Manager............................................................... 5-2
Starting Replication Manager............................................................................. 5-2
Stopping Replication Manager ...........................................................................5-3
Checking the operation status of Replication Manager ........................................ 5-4
Changing settings in the properties files................................................................... 5-5
Properties related to Replication Manager...........................................................5-5
logger.properties.............................................................................................. 5-8
About Replication Manager log output.....................................................5-11
serverstorageif.properties................................................................................5-11
bcmif.properties..............................................................................................5-12
agentif.properties........................................................................................... 5-13
appagentif.properties...................................................................................... 5-14
base.properties...............................................................................................5-14
RpMCLI.properties.......................................................................................... 5-17
6 Security management........................................................................... 6-1
Network communications security............................................................................ 6-2
Securing communications between Hitachi Command Suite Common Component and
Web browsers.................................................................................................. 6-4
Securing communications between Replication Manager and the Device Manager
server..............................................................................................................6-5
Securing communications between Replication Manager and Business Continuity
Manager (IHS)................................................................................................. 6-7
Collecting audit logs ...............................................................................................6-9
v
7 Troubleshooting....................................................................................7-1
Overview................................................................................................................7-2
General problem resolution......................................................................................7-2
Collecting maintenance information..........................................................................7-3
Executing the collection command..................................................................... 7-3
Examples of collection commands............................................................ 7-5
Troubleshooting Application Agent operations........................................................... 7-5
Resolving Application Agent installation and removal errors................................. 7-6
Application Agent and VSS Provider installer trace log files......................... 7-6
Resolving Application Agent operation errors...................................................... 7-8
Collecting support information with the hrpmap_getras command........................7-8
Application Agent events that can be ignored....................................................7-10
Troubleshooting when copy pairs are not recognized............................................... 7-14
Items to be checked on the pair management server........................................ 7-14
Installation of Device Manager Agent...................................................... 7-15
Link between Device Manager server and Device Manager Agent..............7-15
Properties of Device Manager Agent....................................................... 7-16
Settings in the CCI configuration definition file.........................................7-16
Items to be checked from Device Manager GUI.................................................7-16
Recognition of Device Manager Agent..................................................... 7-16
Recognition of the command device........................................................7-16
Recognition of the replication configuration............................................. 7-17
Recognition of storage systems.............................................................. 7-17
Items to be checked from Replication Manager GUI.......................................... 7-17
Creation of TrueCopy Extended Distance or COW Snapshot copy pairs fails (HUS100
Series)................................................................................................................. 7-18
Troubleshooting replica operations......................................................................... 7-19
Replica creation fails silently............................................................................ 7-19
Backup server is not recognized as a pair management server........................... 7-19
Restoring a replica with roll-forward fails with error message RPM-11510........... 7-20
Creating a replica fails with error message RPM-10006...................................... 7-20
Creating a replica fails with event IDs 17, 1 and 10010......................................7-21
Disk status remains online after replica operation is complete............................ 7-21
A Version compatibility with other HCS products........................................ A-1
Restrictions when Replication Manager and Device Manager versions differ................ A-2
Restrictions when Replication Manager and Business Continuity Manager versions differ
............................................................................................................................. A-3
B Supported functions and unsupported configurations.............................. B-1
Supported paths for acquiring information and performing processing........................ B-2
List of tasks supported for each storage system........................................................ B-3
Unsupported configurations (open systems)............................................................. B-9
Unsupported configurations (mainframe systems)................................................... B-12
Acronyms and Abbreviations
Glossary
vi
Index
vii
viii
Preface
This document describes the installation and configuration process for Hitachi
Replication 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
ix
Intended audience
This manual is intended for the following system administrators who use
Replication 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 management
software used to operate storage systems
•
Knowledge of storage system volume replication functionality (such as
ShadowImage 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 version
This document revision applies to Replication Manager v8.1.3 or later.
Release notes
Release notes contain requirements and more recent product information that
may not be fully described in this manual. Be sure to review the release notes
before installation.
Document organization
The following table provides an overview of the contents and organization of
this 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.
Chapter
Chapter 1, Overview of
Replication Manager on
page 1-1
x
Description
Provides a functional overview of Replication Manager and
explains its characteristics and its terminology.
Preface
Chapter
Description
Chapter 2, Replication
Describes the system configurations, system components,
Manager system
and system requirements of Replication Manager.
configurations and
requirements on page 2-1
Chapter 3, Setting up
Replication Manager on
page 3-1
Describes how to set up the necessary environment for
Chapter 4, Setting up
Application Agent on
page 4-1
Describes how to set up the necessary environment and
install Application Agent.
Chapter 5, Operating the
management server on
page 5-1
Describes Replication Manager settings, including those for
starting and stopping services, how to back up and restore
databases, and how to edit the properties file.
Chapter 6, Security
management on page
6-1
Describes the security functions available for Replication
Manager.
Chapter 7,
Troubleshooting on page
7-1
Describes what to do if problems occur during Replication
Manager operation.
Appendix A, Version
compatibility with other
HCS products on page
A-1
Describes the compatibility between versions of Replication
Manager and other Hitachi Command Suite product versions.
Appendix B, Supported
functions and
unsupported
configurations on page
B-1
Contains tables that summarize supported functions and
configurations that are not supported.
Referenced documents
The following Hitachi referenced documents can be found on the applicable
Hitachi documentation CD:
Hitachi Command Suite Documents:
¢
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 Replication Manager CLI Reference Guide,
MK-90HC181
Hitachi Command Suite Replication Manager CLI User Guide,
MK-90HC189
Hitachi Command Suite Messages, MK-90HC178
Preface
xi
¢
¢
¢
¢
¢
Hitachi Command Suite Business Continuity Manager User Guide,
MK-94RD247
Hitachi Command Suite Business Continuity Manager Installation User
Guide, MK-95HC104
Hitachi Command Suite Mainframe Agent Installation and
Configuration Guide, MK-96HC130
Hitachi Command Suite Replication Manager Application Agent CLI
Reference Guide, MK-90HC181
Hitachi Command Suite Replication Manager Application Agent CLI
User Guide, MK-90HC189
Document conventions
This document uses the following typographic conventions:
Convention
Description
Bold
Indicates text on a window, other than the
window title, including menus, menu
options, buttons, fields, and labels.
Example: Click OK.
Italic
Indicates a variable, which is a placeholder
for actual text provided by the user or
system. Example: copy source-file
target-file
Note: Angled brackets (< >) are also used
to indicate variables.
screen/code
Indicates text that is displayed on screen or
entered by the user. Example: #
pairdisplay -g oradb
< > angled brackets
Indicates a variable, which is a placeholder
for actual text provided by the user or
system. Example: # pairdisplay -g
<group>
Note: Italic font is also used to indicate
variables.
[ ] square brackets
Indicates optional values. Example: [ a |
b ] indicates that you can choose a, b, or
nothing.
{ } braces
Indicates required or expected values.
Example: { a | b } indicates that you must
choose either a or b.
| vertical bar
Indicates that you have a choice between
two or more options or arguments.
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:
xii
Preface
Icon
Label
Description
Note
Calls attention to important or additional information.
Tip
Provides helpful information, guidelines, or suggestions for
performing tasks more effectively.
Caution
Warns the user of adverse conditions or consequences (for
example, disruptive operations).
WARNING
Warns the user of severe conditions or consequences (for
example, destructive operations).
Convention for storage capacity values
Physical storage capacity values (for example, drive capacity) are calculated
based 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 storage capacity values (for example, logical device capacity) are
calculated based on the following values:
Logical capacity unit
Value
1 block
512 bytes
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
1 PB
1,024 TB or 1,0245 bytes
1 EB
1,024 PB or 1,0246 bytes
Preface
xiii
Accessing product documentation
Product user documentation is available on the Hitachi Data Systems Portal:
https://portal.hds.com. Check this site for the most current
documentation, including important updates that may have been made after
the release of the product.
Getting help
Hitachi Data Systems Support Portal is the destination for technical support of
your current or previously-sold storage systems, midrange and enterprise
servers, and combined solution offerings. The Hitachi Data Systems customer
support staff is available 24 hours a day, seven days a week. If you need
technical support, log on to the Hitachi Data Systems Portal for contact
information: https://portal.hds.com.
Hitachi Data Systems Community is a new global online community for HDS
customers, partners, independent software vendors, employees, and
prospects. It is an open discussion among these groups about the HDS
portfolio of products and services. It is the destination to get answers,
discover insights, and make connections. The HDS Community complements
our existing Support Portal and support services by providing an area where
you can get answers to non-critical issues and questions. Join the
conversation today! Go to community.hds.com, register, and complete your
profile.
Comments
Please send us your comments on this document: [email protected].
Include the document title, number, and revision, and refer to specific
sections and paragraphs whenever possible. All comments become the
property of Hitachi Data Systems Corporation.
Thank you!
xiv
Preface
1
Overview of Replication Manager
This chapter provides information that you will need to understand before
running a system that incorporates Replication Manager. This information
also includes an overview of the system.
□ About Replication Manager
□ Replication Manager operations roadmap
1-1
About Replication Manager
Replication Manager allows you to manage the replication of storage system
volumes in large-scale system configurations.
To prevent data loss or disruption of work services due to unforeseen
accidents or disasters, a replication environment that is designed with
disaster recovery already taken into account is required. Replication Manager
uses the volume replication functionality of Hitachi storage systems to reduce
the workload involved in management tasks such as protecting and restoring
system data. The following figure illustrates an example of a replication
environment designed for disaster recovery, in which a number of separate
sites are linked together.
Figure 1-1 Example of a replication environment
Volume replication indicates the replication of volumes within a specific
storage system (local copying) or across multiple storage systems (remote
copying). You can improve system reliability by using a combination of local
copying and remote copying, to back up and manage important work data.
For example, local and remote copying enables you to respond efficiently to
disruptions caused by hardware failures. Also, by using remote copying to
copy data to distant locations, you can recover and continue business
operation if a disaster occurs.
1-2
Features
Replication Manager provides the following features to assist storage
administrators.
Centralized management of the replication environment
Replication Manager can be used to manage storage systems (such as
Universal Storage Platform V/VM, or Hitachi AMS2000) and hosts (such as
Windows, Linux, or mainframes) that are at a number of different sites. A
single instance of Replication Manager can manage up to 24,000 open copy
pairs. The status of the large number of copy pairs in these systems, the
progress of copy operations, and performance information (such as data
transfer 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 SQL
Server databases. Known as application replicas, these backup snapshots are
managed as a series of secondary volumes that are rotated on a scheduled
basis. Replication Manager manages the relationships between backup
objects and their associated logical units within storage systems, the
relationships between primary and secondary volumes, and the backup
history. Replicas can be mounted and dumped to tape, using scripts that are
executed through Replication Manager.
Visual representation of replication structures
Administrators can visually check the structure of copy pairs that are
configured across multiple storage systems by examining the structure from
the perspective of a host, a storage system, an application, or a copy pair
configuration definition. Copy pairs in complex configurations can be viewed
as lists. Complex configurations include multi-target configurations in which
one volume is copied to multiple volumes; and cascade configurations in
which primary and secondary volume relationships occur consecutively (so
that, for example, the secondary volume of one copy pair becomes the
primary volume of another copy pair).
Immediate notification of error information
To enable prompt error detection and resolution, the environment must
support error notification from the source of the problem, enabling the
administrator to identify the location of the error. In Replication Manager, you
can specify monitoring conditions for designated copy pairs and sidefiles, and
alerts will be automatically generated when the conditions are satisfied. Such
measures allow you to work out strategies to prevent possible problems from
occurring. For example, you can develop strategies to prevent transfer
performance deterioration due to insufficient network capacity, or to prevent
pairs from being blocked due to a buffer overflow. The status of application
replicas is tracked and reflected in summary form so that the administrator
knows to what extent the application databases are protected.
1-3
You can continue monitoring the system even when not logged in to
Replication Manager, because alerts can be reported in the form of email
messages or SNMP traps.
Modification of replication structures
You can configure additional copy pairs as business operations expand, and
improve performance by expanding buffer space for copying volumes. You
can also change pair states manually after error recovery. Using GUI-based
wizards, you can set up pairs while visually keeping track of complex
replication structures.
Monitoring and analyzing remote copy performance (write delay
time)
When using Universal Replicator, you can check copy performance visually
using the Replication tab of the Hitachi Command Suite GUI.
Note: Use of the Replication tab requires licenses for Device Manager and
Tuning Manager.
When a drop in performance occurs, you can analyze the cause by checking
the detailed information provided by the Replication tab. For more
information, see the Hitachi Command Suite User Guide.
Replication Manager operations roadmap
The following figure shows the roadmap for system configuration, operation,
and maintenance, using Replication Manager.
1-4
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 on
page 1-5. For detailed information about operation, see the Hitachi
Replication Manager User Guide.
1-5
1-6
2
Replication Manager system
configurations and requirements
This chapter describes the system configurations, system components, and
system requirements of Replication Manager. To help you understand
systems that use Replication Manager, this chapter also describes the flow of
control and data between programs.
□ Replication Manager system configurations
□ System requirements
□ Firewall exceptions
□ How Replication Manager collects data
Replication Manager system configurations and requirements
2-1
Replication Manager system configurations
This section describes the basic system configurations for Replication
Manager. Although the following descriptions treat open systems and
mainframe systems separately, Replication Manager also supports
environments that contain both.
Configurations for open systems
This section describes basic system configurations for open systems. The
following figures show examples of site configurations:
2-2
•
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-4 Redundant pair management server configuration in open
systems on page 2-6
•
Figure 2-5 Example GAD configuration on page 2-7
Figure 2-1 Single site configuration in open systems
2-3
Figure 2-2 Two-site configuration in open systems
2-4
Figure 2-3 Three-site configuration in open systems
2-5
Figure 2-4 Redundant pair management server configuration in open
systems
For more information on redundant configurations, see the Hitachi Replication
Manager User Guide.
Global-active device configurations
This guide does not include detailed information on global-active device
(GAD) configurations. For complete setup requirements and management
procedures, see:
2-6
•
Hitachi Virtual Storage Platform G1000 Global-Active Device User Guide
•
Hitachi Command Suite User Guide
Note: The following conditions apply:
•
GAD configurations are only supported on VSP G1000 storage systems.
•
Application Agent does not support replica management using GAD copy
pairs.
Figure 2-5 Example GAD configuration
Open system components
The following tables list and describe system components for each type of
system and provide an overview of the software components:
•
Table 2-1 System components (for open systems) on page 2-8
2-7
•
Table 2-2 Overview of mandatory software (for open systems) on page
2-10
Table 2-1 System components (for open systems)
System components
Software included in
system components
Management client
Web browser
Management server
Replication Manager
Description
A management client is a computer on
which a Web browser is used to run the
GUI for Device Manager and Replication
Manager. Replication Manager runs on
the management server.
A management server provides
Device Manager server management information in response to
requests from management clients.
Replication Manager and Device
Manager server (a prerequisite program
of Replication Manager) are installed on
If multiple sites are used, a
management server is required for each
site. Replication Manager and Device
Manager server are installed on the
management server at the local site.
Device Manager server is installed on
the management server at the remote
site.
Note: When a remote copy is
performed between sites, the
information displayed by the GUI is
limited dependent upon the storage
system model. For details about how
the system configuration limits
displayed information, see the Hitachi
For communication between a
management server and pair
management server, ensure that each
can resolve the others’ IP address from
their host names. If the settings are
specified so that address conversion is
performed between the sites (such as
for a private address and NAT),
Replication Manager might not correctly
connect to Device Manager Agents at
other sites.
Pair management
server
2-8
CCI
Device Manager Agent
A pair management server collects
management information, including
copy pair statuses and performance
information for remote copying. CCI
(Command Control Interface) and
Device Manager Agent are installed on
each pair management server.
System components
system components
Description
By installing CCI and Device Manager
Agent, you can manipulate copy pairs
from Replication Manager. The pair
management server must recognize the
command device in the target storage
system.
If multiple sites are used, at least one
pair management server is required for
each site. Multiple pair management
servers can be set up at each site.
A pair management server can also be
used as a host. When determining
whether to set up pair management
servers to be independent of hosts,
consider security and the loads on the
hosts.
For communication between pair
management servers; if you perform a
remote copy using multiple pair
management servers, ensure that the
pair management server at the primary
site and the pair management server at
the secondary site can determine the IP
address from their respective host
names. If they cannot, an error might
occur during copy pair creation.
Note: For some operations such as
GAD, the pair management server will
need to access a command device with
user authentication enabled. In this
case, it is necessary to configure the
SSL communication between the Device
Manager server and the Device
Manager Agent. If not, the CCI login to
the command device must be
performed manually for each array.
Note: Pair management servers must
be connected to an SVP, a CTL1/CTL2,
or a virtual command device server
through UDP.
Host
Normally, a host is a computer on which
application programs are installed.
Device Manager Agent is also installed
on a host. A host uses storage systems
as external storage systems.
Installing Device Manager Agent is
optional. If you install Device Manager
Agent on a host, you can view
information about that host (such as IP
address and mount points) from
Storage system
Microprograms
A storage system is an external storage
system connected to a host.
2-9
system components
System components
Description
Note: If necessary,
register licenses for
products (such as
Universal Replicator or
ShadowImage).
Table 2-2 Overview of mandatory software (for open systems)
Software
Replication Manager
Description
Used to centrally manage the replication of storage system
Replication Manager includes Hitachi Command Suite Common
Component, a collection of functions that are shared by Hitachi
Command Suite products. Common Component is installed as a
component of the Hitachi Command Suite server products and is
upgraded with the latest version during installation.
Device Manager
server
Used for integrated management of resources and for configuring
storage system hardware. You can run and manage a system
that consists of multiple storage systems.
An instance of Device Manager server running on the same
management server as Replication Manager is called an instance
of "local Device Manager." Instances of Device Manager running
on the a management server different from the management
server on which Replication Manager is running are called
instances of "remote Device Manager."
Note that even when the instance of Device Manager server is
running on a primary site, if Replication Manager is running on a
different management server, the instance of Device Manager
server on the primary site is still called "remote Device Manager.”
Replication Manager performs copy pair operations and other
operations on volumes of storage systems that are managed by
Device Manager server. For details about this server, see the
Hitachi Command Suite Administrator Guide.
Device Manager
agent
Device Manager agents instruct CCI to perform copy pair
operations in response to requests from Replication Manager and
provide Device Manager server with host information.
If you plan to manage copy groups defined by device group, an
appropriate Device Manager agent version, which depends on the
storage system as follows, must be installed:
•
For VSP G1000: v8.0 or later
•
For Virtual Storage Platform: v7.1 or later
•
For HUS VM: v7.2.1 or later
•
For VSP G200, G400, G600: v8.1.2 or later
For details about these agents, see the Hitachi Command Suite
Administrator Guide.
CCI
2-10
Software that controls volume replication functions (such as
TrueCopy or ShadowImage), by issuing commands from a host to
storage systems. (Make certain that the version of CCI supports
your storage system.)
Software
Description
Replication Manager uses the CCI configuration definition file to
change a copy pair configuration and acquire configuration
information. For details, see the manual for the corresponding
version of CCI.
Replication Manager manages the configuration definition file
using Device Manager Agent. For details, refer to the Hitachi
Command Suite Administrator Guide.
Configurations for mainframe systems
This section describes the basic system configurations in use when the host is
a mainframe system host. Mainframe system configurations use either
Business Continuity Manager or Mainframe Agent. The following figures show
examples of configurations depending on the software program:
•
Figure 2-6 Mainframe configuration using Business Continuity Manager
(BCM) on page 2-12
•
Figure 2-7 Mainframe configuration using Device Manager server and
Mainframe Agent on page 2-13
2-11
Figure 2-6 Mainframe configuration using Business Continuity Manager
(BCM)
2-12
Figure 2-7 Mainframe configuration using Device Manager server and
Mainframe Agent
Mainframe system components
The following tables describe system components for each type of system and
provide an overview of the software components:
•
Table 2-3 System components (for mainframe systems) on page 2-13
•
Table 2-4 Overview of mandatory software for mainframe management
on page 2-15
Table 2-3 System components (for mainframe systems)
System components
system components
Management client
Web browser
Management server
Replication Manager
Description
A management client is a computer on
which users use a Web browser to run
the GUI for Replication Manager.
Replication Manager runs on the
management server.
A management server provides
Device Manager server management information in response to
requests from management clients.
Replication Manager and Device
Manager server (a prerequisite program
2-13
System components
system components
Description
of Replication Manager) are installed on
If multiple sites are used, a
management server is required for the
local site.
Host (pair
management server)
Business Continuity
Manager or Mainframe
Agent
Usually, a host is the computer on
which the application programs are
installed. Business Continuity Manager
or Mainframe Agent is installed on a
host.
Note: If Device Manager server is not
registered as an information source, or
Mainframe Agent is being used, the
information displayed by the GUI is
limited. For details, see the Hitachi
By installing Business Continuity
Manager (6.2 or later), you can manage
copy pairs from Replication Manager.
BCM Agent (installed as part of
Business Continuity Manager) handles
requests from Replication Manager. For
more information, see Mainframe Agent
versus BCM Agent on page 2-16.
If you use the remote scan function of
Business Continuity Manager, there is
no need to install a host (pair
management server) at the remote site.
Note: You must set up an environment
prior to performing remote scans or
using pair management functions. For
details, see the Hitachi Business
Continuity Manager User Guide.
Like a pair management server in an
open system, a mainframe system host
collects management information,
including copy pair statuses and
performance information for remote
copying. Therefore, a mainframe
system host is sometimes called a pair
management server.
Storage system
Microprograms
Note: If necessary,
register licenses for
products (such as for
TrueCopy Sync or
Universal Replicator).
2-14
A storage system is used to store data
accessed by hosts.
Table 2-4 Overview of mandatory software for mainframe management
Software
Replication Manager
Description
Used to centrally manage the replication of storage system
Replication Manager includes Hitachi Command Suite Common
Component, a collection of functions shared by Hitachi
Command Suite products. Common Component is installed as a
component of the Hitachi Command Suite server products and is
upgraded to the latest version during installation.
Device Manager server Used to achieve integrated management of disk resources and
for configuring storage system hardware. You can run and
manage a system consisting of multiple storage systems.
An instance of Device Manager server running on the same
management server as Replication Manager is called an instance
of "local Device Manager." Instances of Device Manager running
on the a management server different from the management
server on which Replication Manager is running are called
instances of "remote Device Manager."
Note that even when the instance of Device Manager server is
running on a primary site, if Replication Manager is running on a
different management server, the instance of Device Manager
server on the primary site is still called "remote Device
Manager."
For details about Device Manager server, see the Hitachi
Business Continuity
Manager and BCM
Agent
Used to control copy group configurations located on storage
systems from a host.
Via BCM Agent, Replication Manager monitors and performs
copy pair operations on storage systems managed by Business
Continuity Manager. For details about Business Continuity
Manager, see the Hitachi Business Continuity Manager User
Guide.
Note: Pair management using Replication Manager requires the
use of Business Continuity Manager 6.2 or later - earlier releases
only support data collection.
If you manage copy pairs using the HyperSwap function, or
define a consistency group consisting of one copy group and
another created using CCI, the following hardware/software
versions are required:
Mainframe Agent
•
VSP G1000: v8.0.0 or later
•
VSP: v6.1.1 or later
•
USP V/VM: v6.3 or later
Used to collect information about hosts and storage systems.
In conjunction with Mainframe Agent, Replication Manager
monitors information about configurations and statuses of copy
pairs created by Peer to Peer Remote Copy (PPRC). For details
about Mainframe Agent, see the Hitachi Command Suite
Mainframe Agent Installation and Configuration Guide.
2-15
Note: Do not perform concurrent operations from other applications
(including Business Continuity Manager) on volumes, copy groups, or copy
pairs that are the target of running (or scheduled) tasks. Doing so might
result in an error.
Mainframe Agent versus BCM Agent
Mainframe Agent is installed on a pair management server and allows
Replication Manager to monitor mainframe pairs. BCM Agent is installed as
part of Business Continuity Manager and enables Replication Manager to
manage mainframe pairs. In effect, Business Continuity Manager replaces
Mainframe Agent, with BCM Agent acting as a link with Replication Manager.
•
If you are adding Business Continuity Manager to your storage
configuration, and instances of Mainframe Agent are already configured, it
is not necessary to remove them.
•
If you are setting up a new configuration with Business Continuity
Manager and Replication Manager, there is no need to install Mainframe
Agent.
•
If you are replacing an instance of Mainframe Agent with Business
Continuity Manager, we recommend removing the Mainframe Agent first.
Prerequisites for managing copy pairs on mainframe systems using
CCI
With Hitachi VSP and VSP G1000 systems, you can manage volumes and
copy pairs on mainframe systems using CCI. In this case, you must use the
views and the Pair Configuration wizard for open systems. 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:
¢
¢
¢
2-16
A copy pair managed by Business Continuity Manager is not defined in
the configuration definition file of CCI.
No volumes that consist of a copy pair in a mainframe system
managed by CCI are scanned by Business Continuity Manager, and
Business Continuity Manager is not aware of LDEVs that comprise the
same copy pair.
The value of server.agent.rm.centralizePairConfiguration in the
server.properties file of Device Manager Agent must be set to
enable. For details, see the Hitachi Command Suite Administrator
Guide.
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 resource
group used for a data migration function that uses virtual IDs, Replication
Manager can display the physical IDs and define pair configurations by
specifying the physical IDs. However, the following functions are not
available:
•
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 as
follows:
•
Copy pairs must be configured in such a way that they are managed with
the central management method.
•
The configuration definition file must be re-created to match the migrated
environment.
•
Authentication mode is enabled for the command device assigned to a
pair management server.
•
Fulfill the requirements described in Device Manager Agent and user
authentication on page 2-18.
For details about the central management method and the configuration
definition file, see the Hitachi Command Suite Administrator Guide.
Prerequisites for data migration using virtual IDs (VSP G1000)
The prerequisites for defining or managing such a configuration are as
follows:
•
If you are using physical IDs, copy pairs must be configured in such a
way that they are managed with the central management method.
•
The configuration definition file from the old storage system must be recreated to match the environment to which you are migrating. When the
migration is complete and the copy pairs are functional, do not make
further changes to the configuration definition file.
•
If you are using physical IDs, authentication mode must be enabled for
the command device assigned to the pair management server.
•
Check the conditions described in Device Manager Agent and user
WARNING: Do not attempt to create a copy pair if all the following
conditions are true:
•
The Device Manager Agent version is v8.0.0.
•
The CCI version is 01-32-03/xx.
2-17
•
The physical and virtual storage machines that share the same serial
numbers and LDEV IDs coexist and the storage machines do not coexist
in one LDEV.
Virtual ID and resource group limitations
If the storage system is VSP G1000 and the volume belongs to a resource
group migrated using virtual IDs, then Replication Manager can display the
physical and virtual IDs and define copy pair configurations. However, the
following functions 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 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.
If these conditions are not satisfied, perform the user authentication
manually:
1.
If the pair management server OS is Windows, change the log on account
of the Device Manager Agent service to an Administrators group account.
2.
If the pair management server OS is Windows, log on as the log on
account of the Device Manager Agent service. If the pair management
server 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 use
virtual 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:
2-18
•
The virtual ID needs to be specified for HORCM_VCMD. If a command
device is defined in HORCM_CMD, you need to review the configuration
definition file whenever you upgrade CCI.
•
If you plan to use both physical and virtual IDs, create separate
configuration definition files for each. For the physical ID, define a storage
system that does not support virtual storage machines.
Application Agent support for virtual IDs and virtual storage
machines
Application Agent supports the following configurations using virtual IDs and
virtual storage machines.
For local copy: A copy pair consisting of volumes in one virtual storage
machine configured in one physical storage machine.
For remote copy:
•
A copy pair consisting of volumes in one virtual storage machine
configured in multiple physical storage machines.
•
A copy pair consisting of volumes in multiple virtual storage machines
with each virtual storage machine configured in different physical storage
machines.
Caution: Take note of the following:
•
If you migrate data using a virtual storage machine, any existing backup
catalogs are no longer valid. After the migration is complete, re-create
the dictionary map file as described in the Hitachi Command Suite
Replication Manager CLI User Guide and run a new backup.
•
If an LU that is a target of Application Agent commands is recognized
using a virtual ID by the host, and the LU is defined in the configuration
definition file of CCI using a physical ID, the Application Agent commands
might terminate abnormally.
Prerequisites for managing global-active device copy pairs
The following table describes prerequisites and precautions for GAD copy
pairs.
Settings
Storage system
Requirements
•
The physical storage system is VSP G1000.
•
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 secondary
storage systems.
•
Check the conditions described in Virtual IDs and Device
Manager Agent and CCI versions on page 2-18.
•
Check the conditions described in About adding a copy
group to an existing GAD pair on page 2-20.
2-19
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 multitarget configuration when created on the primary side and a cascade on the
secondary.
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 the
virtual IDs of the virtual storage machine. To use virtual IDs, you must
configure a separate pair management server for each storage system.
WARNING: Application Agent does not support multi-target and cascade
global-active device configurations.
Prerequisites for managing copy pairs using snapshot groups
If a volume is a VSP, VSP G1000, VSP G200, G400, G600, or HUS VM,
Replication Manager can manage copy pairs using snapshot groups. However,
the following functions are not available:
•
Setting alert (pool usage monitoring function for Thin Image is available)
•
Managing My Copy Groups
•
Managing replicas
The prerequisites for managing copy pairs using snapshot groups are as
follows:
•
Authentication mode is enabled for the command device assigned to a
pair management server.
•
Check the conditions described in Device Manager Agent and user
Mainframe pairs and Device Manager Agent
Beginning with v7.4.0, Replication Manager supports configurations in which
mainframe system pairs are managed by Device Manager Agent. As with
open system pairs, the status of a pair managed through Device Manager
Agent is acquired from the Replication Manager Agent instance on the
relevant pair management server. The information that can be acquired is the
same as for open system pairs.
Configurations for mainframe monitoring
As of release 6.3, Replication Manager supports monitoring of IBM
environments (z/OS, z/VM, z/VSE and z/Linux) and non-IBM environments
using only Device Manager (without Business Continuity Manager or
Mainframe Agent installed). Replication Manager retrieves the status of
2-20
TCS/TCA/SI, as well as UR copy pairs directly from storage systems, without
depending on mainframe host types. The minimum interval of automatic
refresh 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 pairs
The requirements are as follows:
•
The configuration information is being updated using the same HORCM
file that was used to set up the virtual command device.
•
If you plan to use a virtual command device server as a virtual command
device, 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 the
configuration definition file on the virtual command device server, the
following conditions apply:
¢
¢
The default port must be used as the CCI initiator port of the pair
management server.
The port number must be specified for each pair management server
as described in Specifying port numbers for pair management servers
on page 2-23
The following related considerations apply to using virtual command devices
to manage copy pairs:
•
User authentication for virtual command devices on page 2-21
•
Monitoring volume or journal usage rates on page 2-22
•
CCI command response time on page 2-22
User authentication for virtual command devices
If the following conditions are true, user authentication needs to be
completed using 01-25-03/01 or later version of CCI prior to starting
operation:
•
The storage system is VSP G1000, Virtual Storage Platform, or HUS VM
and an SVP is used as a virtual command device.
•
The storage system is VSP G200, G400, G600 and a CTL1/CTL2 is used as
a 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.
2-21
When the above conditions are not satisfied, you must perform user
authentication manually as follows:
1.
If the pair management server OS is Windows, change the log on account
of 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 of
VSP G1000, VSP G200, G400, G600, VSP, USP V/VM, Hitachi USP, or HUS VM
storage systems, one of the following conditions must be satisfied:
•
The host or virtual command device server connected to the command
device 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 or
changing a configuration definition file updates information of a newly added
storage system.
CCI command response time
When you manage copy pairs using a virtual command device, the CCI
command takes longer to respond than with a physical command device.
To prevent possible timeout errors from Device Manager Agent, we
recommend the following property file settings:
•
Set the server.atent.rm.moduleTimeOut property in the
server.properties file to 1800 or greater.
•
Set the agent.rm.TimeOut property in the agent.properties file to
1800 or greater.
Replication Manager
•
Set the hdvmagtif.MaxPollingCount property in the
agentif.properties file to 100.
•
Set the hdvmagtif.PollingInterval property in the
agentif.properties file to 60 or greater.
For details about editing property files, see Properties related to Replication
Manager on page 5-5. After changing property files, you must restart
Replication Manager as described in Starting and stopping Replication
Manager on page 5-2.
2-22
Specifying port numbers for pair management servers
The port numbers that depend on Device Manager Agent version and CCI
version must be specified for each pair management server as shown in the
table below.
For details on instance numbers of HORCM files for monitoring, see the
Hitachi Command Suite Administrator Guide.
Condition
Device Manager
Agent version
v8.1.0 or later
Port numbers for each pair management server
CCI version
01-32-03/xx or
later
Port numbers
instance-number to instance-number - (range 1)
Default values
1948 to 2047
Where:
•
instance-number is the value specified for
the Device Manager Agent property
server.agent.temporaryInstance
(default value: 2047).
•
range is the value specified for the Device
Manager Agent property
agent.rm.horcmRange (default value: 100).
Note: You do not need to set any instance
numbers you want to reject.
Earlier than
01-32-03/xx
v8.0.1
01-32-03/xx or
later
Earlier than
01-32-03/xx
v8.0.0
All versions
instance-number and instance-number -1
4094 and 4093
Where instance-number is the value specified
for the Device Manager Agent property
server.agent.temporaryInstance (default
value: 4094).
instance-number
4094
Where instance-number is the value specified
for the Device Manager Agent property
server.agent.temporaryInstance (default
value: 4094).
Configurations for replica management
The following figures depicts composite configuration where copy pairs and
application replicas are managed. The system components (hosts) are labeled
with both the pair management terms (example: pair management server)
and the replica management counterpart (example: backup server):
•
Figure 2-8 Example system configuration managing copy pairs and
application replicas (Exchange) on page 2-24
•
application replicas (SQL Server) on page 2-25
2-23
application replicas (Exchange)
Note: Only TCS is supported for creating a remote copy.
2-24
application replicas (SQL Server)
Note: Depending on the configuration, backup servers are not required for
SQL Server configurations.
Components for replica management
The following tables describe the system components that are unique to
replica management and their counterparts to pair management:
•
Table 2-5 System components (for replica management) on page 2-26
•
Table 2-6 Overview of mandatory software (for replica management) on
page 2-26
2-25
Table 2-5 System components (for replica management)
System components
system components
Database server
Application Agent
A host where Exchange or SQL Server
is installed. Application Agent is
installed on the database server.
Backup server
Application Agent
A host where the secondary volumes
are located. Application Agent is also
installed on the backup server.
Description
Table 2-6 Overview of mandatory software (for replica management)
Software
Description
Application Agent
Allows Replication Manager to perform database backup and
restore operations. The agent internally manages the
relationships between backup objects and their associated
logical units within the storage systems, the relationships
between primary and secondary volumes, and the backup
history.
VSS provider:
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 and
one backup server) to back up Exchange data. The database
server can manage the primary volumes. The backup server
imports VSS snapshots and verifies the Exchange database.
RM Shadow Copy
(Exchange only)
Replication Manager in standby configuration
To prepare for disaster recovery, you can install Replication Manager on a
management server at the standby site and leave it operating in maintenance
mode. Should the primary server fail, the standby server can be brought into
service by taking it out of maintenance mode. For details about how to set
maintenance mode, see the Hitachi Replication Manager User Guide.
2-26
Figure 2-10 Standby Replication Manager (multi-platform, multi-site
configuration)
System requirements
This section describes the system requirements for management servers,
management clients, pair management servers, hosts, and storage systems
that make up a Replication Manager system. Each computer must be
connected to a TCP/IP network and a static IP address is required for the
management server.
System requirements for the management server
The following describes the requirements for the management server on
which Replication Manager is to be installed:
•
Operating systems on page 2-27
•
Server specifications on page 2-32
•
Resource Limits on page 2-35
Operating systems
This section describes the system requirements for the OS and cluster
environment for a management server. If you run the management server in
a cluster environment, also see Table 2-10 Requirements for a cluster
environment on page 2-32.
2-27
If you plan to use the Replication Manager CLI, see Table 2-9 Requirements
for using the Replication Manager CLI on a management server on page
2-32.
Note: When using IPv6, both IPv4 and IPv6 must be enabled on the
management server. You can use IPv6 addresses only if they are global
addresses.
Table 2-7 Windows OS and programs for a management server
Windows operating system
Windows Server 2008 R2 SP1
•
Supports IPv4 and IPv6 connections
•
Also runs as a guest OS of Windows Server 2008 Hyper-V and V2
•
Also runs under VMware ESX/ESXi Server 4.x, VMware ESXi
Server 5.0, VMware ESXi Server 5.1, or VMware ESXi Server 5.5.
To execute Replication Manager on the virtual server, configure
the virtual server using the recommended configuration.
•
Operation on Server Core is not supported
Prerequisite
programs
Device Manager
server
Windows Server 2012 no SP
•
•
Also runs under VMware ESXi Server 5.1 or VMware ESXi Server
5.5. To execute Replication Manager on the virtual server,
configure the virtual server using the recommended
configuration.
•
•
Operation on Minimal Server Interface is not supported
•
Also runs as a guest OS of KVM.
Windows Server 2012 R2
•
•
Also runs under VMware ESXi Server 5.1 or VMware ESXi Server
5.5. To execute Replication Manager on the virtual server,
configure the virtual server using the recommended
configuration.
•
•
Note: If you link to a Device Manager Agent running on a guest OS of
VMware ESX 4.x or VMware ESXi 4.x, use v7.0.1 or later of Device Manager
server and Device Manager Agent. If you link to a Device Manager Agent
running on a guest OS of VMware ESX 5.x, use v7.2 or later of Device
Manager server and Device Manager Agent.
WARNING: Do not use a Managed Service Account if Windows Server 2008
R2 is the OS on the pair management server, database server, or backup
server. If a Managed Service Account is specified for one of the following
services, errors might occur when Replication Manager operations are being
performed:
2-28
•
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)
The following table lists the server specifications required for a Linux
environment.
Table 2-8 Linux OS and programs for a management server
Linux operating system
Red Hat Enterprise Linux 5.8
Prerequisite
programs
Device Manager
server
The following RPM packages must be applied to this OS:
•
net-snmp-<RPM-package-version>.x86_64.rpm
•
net-snmp-libs-<RPM-package-version>.x86_64.rpm
•
net-snmp-utils-<RPM-package-version>.x86_64.rpm
•
net-snmp-agent-libs-<RPM-package-version>.x86_64.rpm
•
net-snmp-devel-<RPM-package-version>.x86_64.rpm
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2-29
•
•
•
•
•
•
kernel-2.6.32-220.4.2.el6.x86_64.rpm or later
•
kernel-firmware-2.6.32-220.4.2.el6.noarch.rpm or later
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Also runs under Kernel-based Virtual Machine (KVM).
2-30
Prerequisite
programs
Prerequisite
programs
•
•
•
•
•
•
upstart 0.6.5_13.el6_5.3.x86_64.rpm
•
•
•
•
•
•
upstart 0.6.5_13.el6_5.3.x86_64.rpm
•
•
•
•
•
•
•
•
•
•
•
glibc-2.17-55.el7.i686.rpm
•
tcsh-6.18.01-7.el7.x86_64.rpm
•
net-tools-2.0-0.17.20131004git.el7.x86_64.rpm
•
perl-5.16.3-283.el7.x86_64.rpm
SUSE Linux Enterprise Server 11 (No SP, SP1, SP2, SP3)
The following RPM package must be applied to this OS:
•
2-31
Note: If you link to a Device Manager Agent running on a guest OS of
VMware ESX 4.x, VMware ESXi 4.x, or VMware ESXi 5.x, use v7.0.1 or later
of both Device Manager server and Device Manager agent.
If you link to a Device Manager Agent running on a guest OS of VMware ESX
5.x, use v7.2 or later of Device Manager server and Device Manager Agent.
The following table lists the server specifications required for use of the
Replication Manage CLI.
Table 2-9 Requirements for using the Replication Manager CLI on a
management server
Operating
system
Windows
Edition
Windows server 2008 R2 SP1
Windows Server 2012 R2
Linux
Red Hat Enterprise Linux 5.11, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6 and 7.0
SUSE Linux Enterprise Server 11 no SP, SP1, SP2, SP3
The following table lists the server specifications required for a cluster
environment.
Table 2-10 Requirements for a cluster environment
Operating system
Windows
Cluster software
Microsoft Windows Server 2008 R2 SP1
Microsoft Windows Server 2012 no SP
Windows Server Failover
Clustering
Microsoft Windows Server 2012 R2
Linux
Red Hat Enterprise Linux High
Availability
Server specifications
The following table lists the server specifications required for a management
server to run Replication Manager.
Table 2-11 Required server specifications for a management server
Item
2-32
Minimum
requirement
Recommended specification
CPU clock speed
1 GHz
2 GHz or higher
Memory size
3 GB
6 GB or more
Disk size
750 MB
750 MB to 6.6 GB (depends on the
number of resources managed)
The disk size required for operations of the (required) Device Manager server
must also be taken into account. For details about the server specifications
for Device Manager server, see the Hitachi Command Suite Administrator
Guide.
Note: These requirements also apply to installing Replication Manager on a
virtual system.
Virtual memory requirements
If adequate virtual memory is not allocated on the management server,
Hitachi Command Suite products and any other installed programs might
become unstable or might not start. To ensure stable operation, in addition to
the virtual memory required for the OS and other programs, the information
in Table 2-12 Virtual memory requirements for each product (64-bit) on page
2-33 and Table 2-14 Virtual memory requirements for each product (32-bit)
on page 2-34 should be taken into account.
When agents associated with each product are installed on the management
server, additional virtual memory must be allocated as described in Table
2-13 Agent virtual memory requirements on page 2-34.
For details on the latest virtual memory requirements, see the documentation
for each product.
Table 2-12 Virtual memory requirements for each product (64-bit)
Product
Virtual memory capacity (MB)
Common Component (64-bit)
Hitachi Command Suite1
•
Device Manager
•
Tiered Storage Manager
•
Replication Manager
•
Host Data Collector
2501
Device Manager has small memory heap 6700
size
Device Manager has medium memory
heap size
7200
Device Manager has large memory heap
size
8200
Tuning Manager server
4000
Global Link Manager
1000
Compute Systems Manager
When you use Deployment Manager
6400
When you do not use Deployment
Manager
5000
Hitachi Automation Director
7000
Note:
1.
Device Manager, Tiered Storage Manager, Replication Manager, and Host
Data Collector are always installed at the same time.
2-33
Example calculation (for 64-bit)
For example, it is necessary to allocate a virtual memory capacity greater
than 11701 MB when operating a management server under the following
conditions:
•
The memory heap size of the Device Manager server is set to Large
•
Only Hitachi Command Suite (Device Manager, Tiered Storage Manager,
Replication Manager, and Host Data Collector) is installed on the
management server.
•
1000 MB of virtual memory is already allocated for the operating system
and other programs.
The calculation is as follows:
1780 (Common Component) (64-bit)
+ 8200 (Hitachi Command Suite)
+ 1000 (Allocated virtual memory)
= 11701
Table 2-13 Agent virtual memory requirements
Agent
Requirement
Specify the virtual memory size value for the
server.agent.maxMemorySize property. (See the Hitachi
Command Suite Administrator Guide for more information.)
Application Agent
(Replication Manager)
See Virtual memory on page 4-12 for more information.
Tuning Manager Agent See the Hitachi Command Suite Tuning Manager Installation
Guide.
Tuning Manager
For the virtual memory size, see the documentation for required
memory size in the manual for each agent.
Table 2-14 Virtual memory requirements for each product (32-bit)
Product
Common Component (for 32-bit)
Virtual memory capacity (MB)
Small memory heap size
1524
Medium memory heap size
1780
Large memory heap size
2292
Hitachi NAS Manager1
512
Hitachi File Services Manager1
1024
Storage Navigator Modular 21
200
Note:
1.
2-34
The virtual memory capacities for Hitachi NAS Manager, Hitachi File
Services Manager, and Storage Navigator Modular 2 are for version 6.4,
5.2, and 27.77, respectively. For the most recently updated values for
virtual memory capacity, see the respective manuals for each product.
Example calculation (for 32-bit)
For example, it is necessary to allocate a virtual memory capacity greater
than 3804 MB when operating a management server under the following
conditions:
•
The memory heap size of the Device Manager server is set to Large
•
Hitachi NAS Manager is installed on the management server.
•
1000 MB of virtual memory is already allocated for the operating system
and other programs.
The calculation is as follows:
2292 (Common Component)
+ 512 (Hitachi NAS Manager)
+ 1000 (Allocated virtual memory)
= 3804
Tip: If you install the 64-bit and 32-bit product on a management server, you
must allocate the virtual memory requirements for both.
Resource Limits
The maximum number of resources that can be managed by Replication
Manager depends on the memory heap size (Small, Medium, or Large). Set
an appropriate memory heap size, depending on the maximum number for
each resource.
Note: 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 Hitachi
Command Suite Installation and Configuration Guide.
This section discusses the following:
•
Maximum number of copy pairs on page 2-35
•
Maximum number of LDEVs on page 2-36
•
Log data and number of copy pairs on page 2-37
Note: Mainframe system resources managed by CCI must be managed as
open system resources. See Prerequisites for managing copy pairs on
mainframe systems using CCI on page 2-16 for more information.
Maximum number of copy pairs
The following table shows the maximum number of copy pairs.
2-35
Table 2-15 Maximum number of copy pairs that can be managed
Number of copy pairs
by memory heap size
Environment
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-pairsfor-mainframe-systems
Note: In consideration of response time and memory usage, the maximum
number of both open and mainframe pairs that can be operated on by the
Pair Configuration Wizard at one time is 1,000. In the case of a mainframe
system, when operating a copy group or consistency group that includes
25,000 or more copy pairs, specify Medium or Large for the memory size.
Number of copy pairs on open systems
If the number of copy pairs is 5,000 or more, edit the following Device
Manager Agent properties on the pair management server:
•
server.agent.maxMemorySize in the server.properties file
•
agent.rm.TimeOut in the agent.properties file
For details about how to edit the properties, see the “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 the
number of copy pairs managed by Business Continuity Manager, confirm that
the larger number of copy pairs is less than or equal to the value shown in
Table 2-15 Maximum number of copy pairs that can be managed on page
2-36.
Maximum number of LDEVs
The maximum number of manageable LDEVs is based on the total number of
LDEVs in all managed storage systems. The following table shows the
maximum number of LDEVs.
In an environment where there are multiple sources for LDEV information
acquisition, confirm that the total number of LDEVs acquired from each
information acquisition source is less than or equal to than the maximum
number. In an open system environment, when the memory heap size is
2-36
Small or Medium, the maximum number is the total number of LDEVs
acquired from both the local and remote instances of Device Manager. When
the memory heap size is Large, the maximum number differs for the LDEVs
acquired from the local and remote instances of Device Manager.
Table 2-16 Maximum number of LDEVs that can be managed
Number of LDEVs by
memory heap size
Environment
Small
Open systems
only
The LDEV information
acquisition source is a
local Device Manager
50,000
Medium
80,000
remote Device Manager
Large
1,000,000
256,000
Mainframe systems only
80,000
120,000
200,000
Combined open
and mainframe
80,0001
120,0001
1,000,000
local Device Manager on
the open system
remote Device Manager
on 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 the
number is less than or equal to the maximum:
(number-of-open-LDEVs * 2) + number-of-mainframe-LDEVs
Log data and number of copy pairs
The amount of log data depends on the number of copy pairs to be managed.
You can change the maximum number of log files and the maximum data size
for each log file. For details, see logger.properties on page 5-8.
System requirements for the management client
The following tables lists the supported operating systems and Web browsers
for a management client that allows you to use the GUI.
management server. You can use IPv6 addresses only if they are global
addresses.
2-37
Table 2-17 Supported Windows OS and web browsers for a management
client
Windows operating system
Web browser
Windows Server 2008 SP2 (32bit)1
Internet Explorer 9.0
Windows Server 2008 R2 no SP
(64-bit)2
Windows Server 2008 R2 SP1 (64bit)1
Internet Explorer 9.0, 11.0
Windows Server 2008 SP2 (64bit)1
Windows Server 2012 no SP1, 2
(only the 32-bit version is supported)
(only the 32 bit version is supported)
Windows Server 2012 R2 no SP1, 2
Windows Vista SP2
Windows 7 no SP
Windows 7 SP1
Internet Explorer 9.0, 11.0
Windows 8 no SP
Windows 8.1 no SP
Notes:
1.
Operation on Server Core is not supported.
2.
Table 2-18 Supported Linux OS and web browsers for a management
client
2-38
Web browser
Red Hat Enterprise Linux 5.3 (32bit)
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Web browser
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x
Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR
31
31
31
31
31
31
Firefox ESR 31
Firefox ESR 31
SUSE Linux Enterprise Server 11
no SP (32-bit)
Firefox ESR 17.0.x
SP1 or SP2 (32-bit)
31
SP3 (32-bit)
31
Required memory for management clients
The minimum required memory size for a management client for all operating
systems is at least 512 MB.
System requirements for hosts and pair management servers
This section describes the requirements for hosts and pair management
servers.
2-39
Requirements for open systems
The following table shows the requirements for hosts and pair management
servers. For information on restrictions, see Restrictions when Replication
Manager and Device Manager versions differ on page A-2.
Table 2-19 Requirements for hosts and pair management servers (for open
systems)
Type
Host
Operating system
The Device Manager Agent
must support the OS.
Pair management
server
For information about
supported operating systems
for the host or pair
management server, see the
Hitachi Command Suite
Installation and Configuration
Guide.
Prerequisite programs
Device Manager Agent. For
information on agent compatibility
with hosts managed by Device
Manager, see the Hitachi Command
Suite Administrator Guide.
•
CCI
•
Device Manager Agent 6.0 or
later
CCI version requirement
If the version of Device Manager Agent used with Replication Manager is
6.4.0 or later, we strongly recommend that the version of CCI running on the
same host as the agent be 01-17-03/05 or later for Windows or 01-21-03/05
for Linux. If an earlier version of CCI is used, an error will occur that requires
a property file setting described below.
When a host running Device Manager Agent and CCI is restarted, device
information is updated. This update can render the configuration definition
file used to identify command devices obsolete (because values referring to
pre-update device information remain unchanged). This might make it
impossible to gather pair, pool and journal information from Replication
Manager.
To prevent this error, specify the following Device Manager Agent property in
the server.properties file:
server.agent.rm.optimization.userHorcmFile=true
CCI version and consistency group support
To create remote pairs with the CTG option, CCI 01-21-03/02 or later must
be installed on the pair management server. If an earlier version is installed,
pairs can be created successfully, but they are not members of a CT group
(because the CTG option is ignored).
Functional limitations when software versions do not match
The version numbers of Hitachi Command Suite products are synchronized to
ensure feature compatibility. For example, v6.4 of Replication Manager and
Device Manager support the same feature set (including, for example, HORC
Takeover support).
2-40
In an environment where the Hitachi Command Suite product versions are
mixed, support is limited to the feature set of the earlier version. For
example, although Application Agent v6.3 can be used with Replication
Manager v6.4, v6.3 does not include SQL Server support.
For best results, ensure that the version numbers of installed Hitachi
Command Suite products are synchronized.
Requirements for mainframe systems
The following table describes the requirements for hosts. For information on
restrictions, see Restrictions when Replication Manager and Business
Continuity Manager versions differ on page A-3.
Table 2-20 Requirements for hosts (for mainframe systems)
Operating system
Must support Business Continuity
Manager or Mainframe Agent
Prerequisite programs
Business Continuity Manager 5.0, or Mainframe
Agent 6.0 or later.
For pair management: Business Continuity
Manager 6.2 or later.
For monitoring only: Business Continuity
Manager (6.1 or earlier) or Mainframe Agent
(6.0 or later).
Note: If you want to use an IPv6 connection or HTTPS (SSL) communication
between Hitachi Replication Manager (HRpM) and BCM, you must set up the
IBM HTTP Server (IHS).
For Business Continuity Manager requirements, see the Hitachi Business
Continuity Manager Installation Guide. For the requirements for Mainframe
Agent, see the Hitachi Command Suite Mainframe Agent Installation and
Configuration Guide.
Support for UR x UR configurations
Cascade and multi-target configurations of UR x UR are supported in
conjunction with Business Continuity Manager v7.3. BCM must be used to
create the configuration; Replication Manager can only be used to update an
existing UR x UR configuration.
Note: When attempting to delete copy pairs from a UR x UR configuration for
a mainframe system, switch the status of all the copy pairs in the
concatenated copy groups of the two instances to Suspend, and then delete
the copy pairs.
Restrictions on using Business Continuity Manager 6.6.1
The following operations are not supported if you are using Business
Continuity Manager 6.6.1:
2-41
•
When using Business Continuity Manager 6.6.1, if a volume scan using
Replication Manager is performed, an error (RPM-00539) occurs in
•
When Replication Manager is used to distribute disk configuration
definitions files to a host linked with Business Continuity Manager 6.6.1,
an error occurs (RPM-00568) in Replication Manager.
In either of the above cases, Replication Manager cannot be used to edit the
disk configuration definition files that were created by Business Continuity
Manager 6.6.1. Instead, you must use Business Continuity Manager 6.7 or
later to edit the disk configuration definition files and then perform volume
scan or distribution with Replication Manager).
Supported storage systems
Replication Manager supports all storage systems supported by Device
Manager server:
•
Hitachi USP
•
Universal Storage Platform V/VM
•
Virtual Storage Platform
•
Virtual Storage Platform G1000
•
Hitachi AMS/WMS
•
Hitachi AMS 2000
•
Hitachi AMS 2010/2100/2300/2500
•
Hitachi SMS
•
HUS100
•
HUS VM
For details, see the Hitachi Command Suite Administrator Guide.
Tip: For best results, ensure that you have the latest version of the storage
system microcode as well as the latest version of CCI installed.
Note: Before using copy groups defined in storage, ensure that the
microcode version of the VSP or VSP G1000 system is 70-02-00-XX/XX or
later.
Firewall exceptions
If a firewall is present, the port number for transmissions to and from
Replication Manager must be registered as an exception. The tables that
follow describe the port numbers associated with each type of configuration:
•
2-42
Table 2-21 Port numbers to register as firewall exceptions between the
management server and management clients on page 2-43
•
Replication Manager management server and remote Device Manager
management server on page 2-43
•
management server and the pair management server, or the host (open
system) on page 2-44
•
management server and the host (mainframe system) on page 2-44
•
management server and the database or backup server on page 2-44
The number of each port can be changed. For details about how to change
the 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 Business
Continuity Manager Installation Guide
•
For port numbers used by Mainframe Agent: Hitachi Command Suite
Mainframe Agent Installation and Configuration Guide
•
For port numbers used by Application Agent, see Changing Application
Agent port numbers on page 4-31
Table 2-21 Port numbers to register as firewall exceptions between the management
server and management clients
Port number
Originator
Destination
Description
22015/tcp
Management client
Management server
This port is used to access the HBase 64
Storage Mgmt Web Service of Common
Component when communicating with a
management client. This port is required
for non-SSL connections.
22016/tcp
Management client
Management server
This port is used to access the HBase 64
Storage Mgmt Web Service of Common
Component when communicating with a
management client via SSL. This port is
required for SSL connections.
Table 2-22 Port numbers to register as firewall exceptions between the Replication
Manager management server and remote Device Manager management server
Port number
2001/tcp
Originator
Replication
Manager
management
server
Destination
Remote Device
Manager
management
server
Description
This port is used to communicate with
Device Manager Server. It represents the
value of the server.http.port property
coded in the server.properties file for
Device Manager Server. This port is required
for non-SSL connections.
2-43
Port number
Originator
2443/tcp
Replication
Manager
management
server
Destination
Remote Device
Manager
management
server
Description
Device Manager Server via SSL. It
represents the value of the
server.https.port property in the
server.properties file for Device Manager
Server. This port is required for SSL
connections.
server and the pair management server, or the host (open system)
Port number
Originator
24041/tcp
Destination
Management server •
24042/tcp
•
Pair management
server
Host (open
system)
Description
Device Manager Agent. It represents the
value of the server.agent.port
property in the server.properties file
for Device Manager Agent.
server and the host (mainframe system)
Port number
Originator
24042/tcp
Destination
Management server Host (mainframe
system)
Description
Business Continuity Manager (when IHS
is not being used1), or Mainframe Agent.
It represents the value in the TCP/IP
environment settings file
(PROFILE.TCPIP profile) for a mainframe
system.
Notes:
1.
When IHS is used to communicate with Business Continuity Manager via
SSL, register the port number for IHS as a firewall exception.
server and the database or backup server
Port number
Originator
Destination
24041/tcp
Management server •
24042/tcp
•
2-44
database server
backup server
Description
Device Manager Agent. It represents the
value of the server.agent.port
property in the server.properties file
for Common Agent Component.
Table 2-26 Port numbers to register as firewall exceptions between the database server
and the backup server
Port number
22300/tcp
Originator
•
database
server
•
backup server
Destination
•
database server
•
backup server
Description
This port is used to communicate
between Application Agents. This is the
value registered as DRMVSSServer in the
Windows services file.
How Replication Manager collects data
This section describes how data is acquired and the flow of processing
between individual programs. The elements of the following diagram are
explained in the text that follows.
Data collection in open systems
This section describes the data collection and flow of processing between
programs in open systems.
2-45
Figure 2-11 Data collection (open systems)
Acquiring configuration and license information
Replication Manager acquires the following information using Device
Manager server:
¢
¢
¢
2-46
Copy pair configuration information
Volume configuration information (including the command device,
pool volumes, and journal volumes)
License information for the volume replication functionality
Device Manager server stores information acquired from storage
systems, while Replication Manager stores information acquired from
Device Manager server.
Information for performing remote copy between multiple sites (in
which a copy pair is defined between multiple Device Manager
servers) is acquired using Device Manager Agent because this
information cannot be retained by Device Manager server.
Note: Replication Manager acquires configuration information from
the Device Manager server at the following times:
•
For a local Device Manager:
The configuration management information displayed in each
window is acquired from Device Manager when each source
management window of Replication Manager is displayed. You
need not manually refresh the system configuration information
before using Replication Manager to set up a storage system or
define copy pair configurations.
•
For a remote Device Manager, all configuration information is
acquired when a configuration refresh is performed.
Acquiring copy pair statuses
Replication Manager sends a request to Device Manager Agent, which in
turn 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 Navigator
and Storage Navigator Modular), the status is acquired from Device
Manager server because the CCI configuration definition file is not
available.
Acquiring performance information
Replication Manager issues a request to Device Manager Agent to acquire
performance information (such as the sidefile usage rate, pool volume
usage rate, and write delay time (C/T delta)). In turn, Device Manager
Agent uses CCI to obtain the data from the storage system.
Creating and deleting copy pairs and changing copy pair statuses
Replication Manager issues a request to Device Manager Agent to create
and delete copy pairs or to change the status of copy pairs. The Device
Manager Agent uses CCI to perform the operations on the storage
system.
Data collection in mainframe systems
This section describes the data collection and flow of processing between
programs in mainframe systems.
2-47
Figure 2-12 Data collection (mainframe systems)
Note: Although not shown in this simplified diagram, all requests for
Business Continuity Manager from Replication Manager are handled by BCM
Agent (which resides on the same host as BCM).
Acquiring and deleting copy pair configuration information
Replication Manager issues a request to Business Continuity Manager to
acquire or delete copy pairs. BCM performs the operations on the storage
system.
Acquiring and changing copy pair statuses
Replication Manager issues a request to Business Continuity Manager or
Mainframe Agent, which acquires the status of copy pairs from the
storage system. (Only BCM can change the status.)
Acquiring performance information
Replication Manager issues a request to Business Continuity Manager or
Mainframe Agent to acquire performance information from the storage
system (such as the sidefile usage rate, journal volume usage rate, pool
volume usage rate, and write delay time (C/T delta)). The journal volume
usage rate is acquired as described below.
Acquiring license information
2-48
To acquire license information for the volume replication functionality in
mainframe systems, Device Manager server must be registered as an
information acquisition source.
Replication Manager obtains this license information from the Device
Manager database (acquired from the storage system).
2-49
2-50
3
Setting 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
3-1
Overview
This section is an overview that lists all the tasks that need to be performed.
To set up and configure Replication Manager:
1.
Before installing Replication Manager, you must back up the databases of
other Hitachi Command Suite products in use, on the management server
where Replication Manager is installed. For details about how to back up
databases, see the application product manuals.
2.
Set up the necessary infrastructure as described in Setting up the
prerequisite environment on page 3-3.
3.
For a cluster environment, follow the appropriate procedure in the Hitachi
Command Suite Installation and Configuration Guide before installing
Note: After installing or updating Replication Manager, you must back up the
new configuration data.
Concerning upgrade installations
If you are currently using Replication Manager v6.x or v7.x, you can upgrade
to v8.x. For details about the upgrade installation procedure, see the Hitachi
Command Suite Installation Guide. When the upgrade is complete, consult
the items that follow.
Items to be checked after upgrading Replication Manager
The upgrade changes certain command names and default installation
folders. If you created any scripts that use the command names or file paths
shown in Table 3-1 Command names and file paths changed after upgrade to
v8.x (Windows) on page 3-2 or Table 3-2 Command names and file paths
changed after upgrade to v8.x (Linux) on page 3-3, you should make the
changes indicated.
Table 3-1 Command names and file paths changed after upgrade to v8.x (Windows)
Before
(v6.x or v7.x)
Item
After
(v8.x)
Hitachi Command Suite common
component command names
hcmdsxxxx
hcmds64xxxx
Hitachi Command Suite default
installation folder
For x86:
%ProgramFiles%\HiCommand
%ProgramFiles%\HiCommand
For x64:
%ProgramFiles(x86)%
\HiCommand
3-2
Before
(v6.x or v7.x)
Item
component default installation
folder
Hitachi-Command-Suiteinstallation-folder\Base
After
(v8.x)
Hitachi-Command-Suiteinstallation-folder\Base64
Note: %ProgramFiles% and %ProgramFiles(x86)% are Windows environment
variables.
Table 3-2 Command names and file paths changed after upgrade to v8.x (Linux)
Before
(v6.x or v7.x)
Item
After
(v8.x)
component command names
hcmdsxxxx
hcmds64xxxx
component default installation
directory
Hitachi-Command-Suiteinstallation-folder/Base
Hitachi-Command-Suiteinstallation-folder/Base64
Note: For Linux, the upgrade process does not change the Hitachi Command
Suite default installation folder.
Setting up the prerequisite environment
This section describes how to set up the necessary infrastructure for
Replication Manager. You can follow the workflow figures or the detailed
procedures. 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 both
mainframe and open systems.
3-3
Figure 3-1 Infrastructure configuration workflow
3-4
Open systems environment
To configure the required infrastructure for Replication Manager for an open
system:
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.
Add the resources (storage systems) that are to be managed by
Replication Manager. For details about adding storage systems to Device
Manager, see Hitachi Command 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 device
in 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 information
required for using them. The setup procedure involves the specification of
CCI-related information (such as where to install Device Manager Agent
or whether to use the central management method). Specify settings
appropriate to the environment. For details about how to install and set
up Device Manager Agents, see the Hitachi Command Suite Administrator
Guide.
5.
Configure Device Manager Agents by editing the properties file(s) that are
stored on the pair management servers.
Note: If you have specified settings for CCI in step 4, you can skip step
5.
You need to modify the specific files as directed if any of the conditions
listed 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 Device
Manager Agents have been installed on different drives.
In the server.properties file, specify the CCI installation target in
the server.agent.rm.location property.
The central management method is used for management of copy
pairs.
In the server.properties file, specify enable in the
server.agent.rm.centralizePairConfiguration property.
For details about the central management method, see the Hitachi
After you edit the properties file, restart Device Manager Agents. For
details about how to edit the properties file, the specification rules, and
3-5
how to restart Device Manager Agents, see the Hitachi Command Suite
6.
Install Device Manager Agents on the hosts.
For details, see the Hitachi Command Suite Administrator Guide.
Note: If there are resources on hosts where Device Manager Agent is not
installed, manually add the resource (host).
7.
If there is any host on which Device Manager Agent has not been
installed, manually add the resource (host) to Device Manager.
For details about how to add hosts in Device Manager, see Hitachi
Command Suite Help or the Hitachi Device Manager Command Line
Interface (CLI) User Guide.
8.
Ensure that all of the conditions below are satisfied:
¢
¢
¢
¢
¢
The requirements (microcode and system configuration) for
ShadowImage or TrueCopy or other required storage system volume
replication functions must be satisfied. For details about the
requirements and the configuration procedures, see the storage
system documentation for the applicable storage system model.
The storage systems to which the primary and secondary volumes
belong are registered as management targets of Device Manager, and
the applicable Device Manager server is registered as a Replication
Manager information source.
The pair management server recognizes the command device in the
target storage system.
The primary and secondary volumes are recognized individually from
the hosts.
The serial numbers for all storage systems managed by Device
Manager are unique.
Mainframe systems environment
To configure Replication Manager for a mainframe environment:
1.
2.
Install Hitachi Command Suite on the management servers.
For details, see the Hitachi Command Suite Server Installation Guide. If
necessary, also see the following manuals:
¢
Hitachi Command Suite Administrator Guide
¢
Hitachi Command Suite Help
¢
Hitachi Command Suite CLI Reference Guide
Install Business Continuity Manager or Mainframe Agent on the hosts.
Note: Mainframe pair configuration requires Business Continuity Manager
6.2 or later. Earlier releases only support monitoring functions.
3.
3-6
After installation of Business Continuity Manager or Mainframe Agent, you
must specify the information required for linking with Replication
Manager.
4.
You must configure BCM as follows:
¢
¢
¢
¢
¢
¢
5.
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 files
The following BCM setup operations need to be performed:
¢
¢
¢
¢
Identify DADIDs and prefixes used by Replication Manager and specify
them as initialization parameters for BCM Agent
Set up route lists and command devices to achieve either of the
following:
(a) To retrieve or monitor C/T Delta with Replication Manager / BCM
(b) To discover volumes or perform pair operation on remote DKCs
using local instances of BCM (when no BCM exists on the secondary
site)
For the MODE initialization parameter of BCM Agent, specify EDIT (the
initial value is MONITOR). This allows the management of copy groups
from Replication Manager. (If a function that updates a definition or
changes a status is used when the startup mode is MONITOR, an
YKY727E error occurs in BCM Agent.)
The LOCK initialization parameter can also be set to manage conflicts
between operations performed by Replication Manager and Business
Continuity Manager.
Note: If you want to use an IPv6 connection or HTTPS (SSL)
communication between HRpM and BCM, you must set up the IBM HTTP
Server (IHS).
6.
Ensure that all of the conditions below are satisfied:
¢
¢
¢
The requirements (microcode and system configuration) of the
storage system volume replication functionality (such as
ShadowImage or TrueCopy) are satisfied. For details about the
requirements and the configuration procedures, see the storage
system documentation for the applicable storage system model.
The storage systems to which the primary and secondary volumes
belong are registered as management targets of Device Manager, and
the applicable Device Manager server is registered as a Replication
Manager information source.
The primary and secondary volumes are recognized individually from
the hosts.
3-7
¢
The serial numbers for all storage systems managed by Device
Manager are unique.
For complete information, see the Hitachi Business Continuity Manager
Installation Guide and the Hitachi Business Continuity Manager User Guide,
which include respective chapters on setting up and using the BCM with
For Mainframe Agent, refer to the Hitachi Command Suite Mainframe Agent
Installation and Configuration Guide.
Application replica environment
To configure the required infrastructure for Replication Manager for
application (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, see
the Hitachi Command Suite Administrator Guide.
4.
Install Application Agent on the hosts (database server and backups
server).
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 tasks
bar area. To register or delete a link, execute the hcmds64link command, as
follows.
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 options
The options for the command are shown in the following table.
3-8
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-definedapplication-file
Specify the file (the user-defined application file) used to
register the link information.
user user-ID pass
password
Specify the user ID and password for logging in to Replication
Manager. Specify the user ID of a user who has the Admin
(Replication Manager management) permission.
Creating a user-defined application file
In the file specified for registering the link information, specify that
information in the following format:
@TOOL-LINK
@NAME registration-key-name
@URL startup-URL
@DISPLAYNAME display-name-in-links-dialog-box
@DISPLAYORDER display-order-in-links-dialog-box
@ICONURL icon-URL
@TOOL-END
The following table describes the available options.
Table 3-4 Items specified in the user-defined application file
Item
Description
@TOOL-LINK
Start key for the user-defined application file. This
item is required.
@NAME registration-key-name
This information is used as the registration key.
Specify a name that makes the link information
unique, and use no more than 256 bytes. This item
is required.
@URL startup-URL
Specifies the URL to be started in the GUI. Use no
more than 256 bytes. Note: In IPv6 environments,
specify a host name instead of an IPv6 address.
@DISPLAYNAME display-name-in- Specifies the link name to be displayed in the Links
links-dialog-box
dialog box. Specify Unicode characters in the range
U+10000 to U+10FFFF, using no more than 80
characters. If you do not specify this item, the value
specified in the @NAME line is used as the link name.
@DISPLAYORDER display-orderin-links-dialog-box
Specifies the order of values to be displayed in the
Links dialog box. Specify a value from -2147483648
to 2147483647. Values specified here are displayed
in ascending order in the Links dialog box.
@ICONURL icon-URL
Specifies the location of the icon displayed beside
the link. Use no more than 256 bytes. In IPv6
3-9
Item
Description
environments, specify a host name instead of an
IPv6 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 available
control 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
3-10
4
Setting up Application Agent
This chapter describes the Replication Manager Application Agent, the system
requirements, and how to install the software on backup servers and
database servers.
□ About Application Agent
□ System requirements and supported environments
□ Virtual environments supported by Application Agent
□ Application Agent installation location
□ Installing Application Agent
□ Adding Application Agent to the Windows Firewall Exception list
□ Application Agent and CCI
□ Settings for Application Agent in a cluster configuration
□ Application Agent and Replication Manager log output
□ Changing Application Agent port numbers
□ Starting and stopping the Application Agent Services
□ Setting error logging options for Application Agent
4-1
About Application Agent
Application Agent extends the functionality of Replication Manager to include
application awareness, which allows application resources to be managed
using the Replication Manager interface. Specifically, Application Agent allows
Replication Manager to create and restore replicas of MS Exchange and SQL
Server databases. By linking Application Agent with DBMS products on
application servers, the databases can be backed up and restored.
Application Agent internally manages the relationships between these backup
objects and their associated logical units within storage systems, the
relationships between primary and secondary volumes, and the backup
history. Application Agent also provides information to Replication Manager
whenever necessary.
The following describes how Application Agent controls other software
components:
•
Application Agent pauses databases in storage systems to ensure reliable
backup operations.
•
Using CCI, Application Agent backs up or restores volumes that have
already been operated on using the functions built into the storage
systems.
•
Application Agent operates in conjunction with other backup management
products to perform tape backup and restore operations, such as
NetBackup and Backup Exec.
Tip: Application Agent uses a command line interface (CLI) to communicate
with CCI, the Logical Volume Manager (Windows standard LDM), and other
backup management products. Such products must be installed before using
Application Agent.
Application Agent functions
Application 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 highspeed disk-copying operations. A storage group is a group containing one or
more MS Exchange 2007 information stores. Storage groups can be used to
manage multiple information stores at the same time.
Note: Exchange 2010/2013 does not use storage groups.
4-2
MS Exchange databases contain the following two types of information
stores:
•
Mailbox stores for saving received email messages, attachments, folders,
documents, etc.
•
Public folder stores for saving information shared among users (email
messages, documents, MS Outlook custom forms, etc.)
Data management across storage systems
Application Agent allows you to back up and restore secondary volumes to
and from a local site (the storage system where the primary volume resides)
and a remote site (a storage system different from that of the primary
volume).
Replication Manager can perform the following operations on a remote site
using 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 single
primary volume. (These secondary volumes are referred to as generations.)
When selecting a secondary volume for a backup, you can either select it
manually or have Application Agent automatically rotate the volumes in the
same way that tape backups are re-used (local backups only). At the same
time, Application Agent allows you to lock the contents of certain secondary
volumes and only use other (unlocked) secondary volumes for backups. For
more information, see the Hitachi Replication Manager User Guide.
Note: The number of generations supported by Application Agent depends on
the volume replication function used, but the procedures are the same.
System requirements and supported environments
This section describes the requirements for hardware and software and the
virtual environments supported by Application Agent.
Application Agent system requirements
This section describes the hardware, host type, server, and storage system
necessary to configure a system for the use of Application Agent.
4-3
Note: Replication Manager identifies the database application running on
each host according to the version of the Application Agent installed
(Exchange or SQL Server). Therefore, do not install a version of Application
Agent on a host that does not have the corresponding database application
installed.
If an inappropriate version of Application Agent is installed on a server,
Replication Manager will fail to collect information during Refresh Host
processing and display an error message.
Table 4-1 Server hardware requirements
Item
Minimum
Recommended
CPU
1 GHz
2 GHz or higher
Memory
1 GB
2 GB or greater
Disk space
1 GB
2 GB or greater
Host OS and database server requirements
The following tables list the operating systems, backup-server combinations,
database versions, and programs required by Application Agent.
Note: You must perform a clean installation to upgrade a Host OS. If you
perform an upgrade installation, you may have problems with Application
Agent operation.
Table 4-2 Supported database and backup server combinations (Microsoft Exchange
Server)
Database server OS
Backup server OS
Windows Server 2008 no SP (64-bit)
Windows Server 2008 no SP2
Windows Server 2008 SP1 (64-bit)
Windows Server 2008 no SP (64-bit)
Exchange version
20071, no SP2, SP1,
SP2, SP3
Windows Server 2008 SP12
20071 no SP2, SP1,
SP2, SP3
20101 no SP, SP1,
SP2. SP3
20071 SP3
20101 no SP, SP1,
SP2. SP3
20131 no SP, SP1
20101 SP3
20131 no SP, SP1
4-4
20131 SP1
Database server OS
Backup server OS
Exchange version
20131 SP1
20131 SP1
Note: The same Service Pack should be applied on both the database and
backup server operating systems.
Notes:
1.
The Exchange Management Tool is required on the database server and
backup server. For details, see the section Exchange Management Tool.
2.
This is supported only when using the Application Agent CLI.
Table 4-3 Supported database and backup server combinations (Microsoft SQL Server)
Database server OS
Backup server OS
Windows Server 2008 (no SP/SP1) Windows Server 2008 (no SP/
SP1)
Windows Server 2008 (SP2)
Windows Server 2008 (SP2)
SQL Server version
2005 (SP21, SP3, SP4)
2008 (no SP1, SP1, SP2, SP3)
2008 R2 (no SP, SP11, SP21)
Windows Server 2008 IPF(no SP/
SP1)
Windows Server 2008 IPF (no
SP/SP1)
Windows Server 2008 IPF (SP2)
Windows Server 2008 IPF (SP2)
Windows Server 2008 R2 IPF (no
SP)
Windows Server 2008 R2 IPF
(no SP)
2008 IPF (no SP1, SP1, SP2, SP3)
(SP1)
(SP1)
2008 R2 IPF (no SP, SP11, SP21)
Windows Server 2008 x64 (no SP/ Windows Server 2008 x64 (no
SP1)
SP/SP1)
Windows Server 2008 x64 (SP2)
Windows Server 2008 x64 (SP2)
Windows Server 2008 R2 (no SP)
Windows Server 2008 R2 (no
SP)
Windows Server 2008 R2 (SP1)
Windows Server 2008 R2 (SP1)
2005 (SP21, SP3, SP4)
2005 IPF (SP21, SP3, SP4)
2008 (no SP1, SP1, SP2, SP3)
2008 R2 (no SP, SP11, SP21)
2005 (SP21, SP3, SP4)
2005 x64 (SP21, SP3, SP4)
2008 (no SP1, SP1, SP2, SP3)
2008 x64 (no SP1, SP1, SP2, SP3)
2008 R2 (no SP, SP11, SP21)
2008 R2 x64 (no SP, SP11, SP21)
2012 (no SP, SP1)2
2014 (no SP)4
Windows Server 2012 (no SP)
2012 (no SP3, SP1, SP2)
Windows Server 2012 R2 (no
SP)
2014 (no SP)4
Notes:
1.
Supported only for use with the Application Agent CLI.
2.
Supported when the database server and backup server are Windows
Server 2008 x64 (SP2) or Windows Server 2008 R2 (SP1).
4-5
3.
SQL Server 2012 no SP is supported only if both the database server and
backup server are Windows Server 2012.
4.
If SQL Server 2014 (no SP) is used, the following cluster configuration is
not supported:
¢
A cluster shared volume (CSV) is used as a shared disk of the cluster
configuration.
Note: Application Agent does not support a combination of SQL Server 2008
and Windows Server 2008 32-bit (because a 64-bit OS is expected to serve
as the basic environment for this combination).
Table 4-4 Supported database and backup server OS combinations (when
using a file system and VSS)
Database server OS
Backup server OS
File
system
type
Windows Server 2008 (32-bit) no SP
or SP1, SP2
Windows Server 2008 (32-bit) no SP or NTFS
SP1, SP2
Windows Server 2008 no SP or SP1,
SP2 (64-bit)
Windows Server 2008 (32-bit) no SP or
SP1, SP2
SP1, SP2
Windows Server 2008 R2 no SP, SP1
Windows Server 2008 x86 (no SP, SP1,
SP2)
Windows Server 2008 x64 (no SP, SP1,
SP2)
Windows Server 2008 R2 (no SP, SP1)
Note: When executing a backup using VSS, the same Service Pack should be
applied on both the database and backup server operating systems.
Table 4-5 Supported database and backup server OS combinations (when
using a file system but not VSS)
Database server OS
or SP1, SP2
Backup server OS
Windows Server 2008 (32-bit) no SP or NTFS
SP1, SP2
Windows Server 2008 IPF no SP or
SP1, SP2
4-6
File
system
type
Database server OS
SP1, SP2
Windows Server 2008 R2 IPF no SP,
SP1
Backup server OS
File
system
type
SP1, SP2
Windows Server 2008 R2 IPF no SP,
SP1
or SP1, SP2
Database and backup server requirements
This section describes database and backup server requirements. File
systems are only supported using the Application Agent CLI.
database and backup servers. You can use IPv6 addresses only if they are
global addresses.
Table 4-6 Database and backup server requirements (file systems)
Operating system
IPv6
support
Required programs
Windows Server 2008 no SP or SP15,7,8
Y
CCI14
Windows Server 2008 SP25,7,8
Y
Logical Volume Manager
(Windows LDM3,11)
SP18,9,10
Y
Application Agent v 7.0 or
later11
Windows Server 2008 IPF SP28,9,10
Y
Windows Server 2008 no SP or SP1 (64bit)5,7,8,9
Y
Windows Server 2008 SP2 (64-bit)5,7,8,9
Y
Windows Server 2008 R2 no SP8
Y2
Windows Server 2008 R2 IPF no SP1,5,7
Y
Windows Server 2008 R2 SP11,5,7,8
Y2
CCI14
Windows Server 2008 R2 IPF SP18,9,10
Y
Volume Manager
(Windows LDM3,11)
4-7
Operating system
IPv6
support
Required programs
later11
Windows Server 2012 no SP8,12
Y2
CCI14
Volume Manager
(Windows LDM3, 10)
later11
Windows Server 2012 R2 no SP8,12
Y2
CCI14
Volume Manager
(Windows LDM3, 10)
later11
Notes:
1.
Backups using VSS are not supported.
2.
Communication using IPv6 is supported even when using FTP with the
CLI. For details, see the Hitachi Command Suite Replication Manager
Application Agent CLI User Guide.
3.
LDM basic disks are supported.
4.
Application Agent does not support Veritas Dynamic Multiple Pathing.
5.
Provided as a guest OS of virtual server product Windows Server 2008
Hyper-V which is also supported. To execute Application Agent (CLI) on
the virtual server, configure the virtual server as the recommended
configuration.
6.
In the cluster configuration, GPT disks are not supported. Use MBR disks
when using this product to perform a backup.
7.
Provided as a guest OS of virtual server product VMware ESX/ESXi Server
4.x and 5.x are also supported. However, VMware FT is not supported.
For Application Agent (CLI), configurations are not supported in which a
software FCoE adapter is used to connect a primary or secondary volume
to a database server, backup server, or pair management server on a
guest OS. To execute Application Agent (CLI) on the virtual server,
configure the virtual server as the recommended configuration written in
the manual.
8.
The Server Core feature is not supported.
9.
The VSS function does not work on 64-bit operating systems (x64 Edition,
IPF Edition).
10. Dynamic disks are not supported.
11. Configurations including storage pools are not supported.
12. Operation on Minimal Server Interface is not supported,
13. When applying the VSS correction module that includes Hotfix 940349, be
sure and apply the module on all servers using VSS.
4-8
14. The architecture of CCI must match that of the OS.
Table 4-7 Database and backup server requirements (Microsoft SQL
Server)
Operating system
IPv6
support
Required programs
Windows Server 2008 no SP or
SP13,4.5.6
Y
CCI12
Windows Server 2008 SP23,4.5.6
Y
Logical volume manager (the
standard Windows LDM7,9)
Windows Server 2008 no SP or SP1
(IPF)3,5
Y
Windows Server 2008 SP2 (IPF)3,5
Y
(64-bit)3,4
Y
(64-bit)3
Y
Y1
(IPF)3,5
Y
Windows Server 2008 R2 SP13,4.5
Y1
CCI12
Windows Server 2008 R2 SP1 (IPF)3,5
Y
Application Agent v 6.4 or later9
Device Manager Agent2
Application Agent v 7.1 or later
Y1
CCI12
Y1
CCI12
Notes:
1.
CLI. For details, see the Hitachi Command Suite Replication Manager
Application Agent CLI User Guide.
2.
If either of the following conditions apply when installing Device Manager
agent:
4-9
¢
The version of Device Manager agent is earlier than 6.4.
The version of CCI is earlier than 01-17-03/05.
You must configure the following setting in the Device Manager properties
(server.properties) file:
¢
If you do not add this value, Replication Manager might not be able to
acquire pair, pool, and journal information. For details on editing the
properties file, see the Hitachi Command Suite Installation and
Configuration Guide.
3.
Dynamic disks are not supported. For details about dynamic disk
configurations supported by the Application Agent CLI, see the Hitachi
Command Suite Replication Manager Application Agent CLI User Guide.
For details about Device Manager agent versions that correspond to each
OS, see the Device Manager Release Notes.
4.
Provided as a guest OS of virtual server product Windows Server 2008
Hyper-V is also supported. To execute Application Agent on the virtual
server, configure the virtual server as the recommended configuration.
5.
The Server Core feature is not supported.
6.
Provided as a guest OS of virtual server product VMware ESX/ESXi Server
4.x and 5 are also supported. However, VMware FT is not supported. To
execute Application Agent on the virtual server, configure the virtual
server using the recommended configuration described in the manual.
7.
LDM basic structure is supported.
Dynamic disks are not supported. For details about dynamic disk
configurations supported by the Application Agent CLI, see the Hitachi
Command Suite Replication Manager Application Agent CLI User Guide.
8.
This is supported when using the Application Agent CLI.
9.
Application Agent does not support the Veritas Dynamic Multiple Pathing
function.
10. Configurations including storage pools are not supported.
11. Operation on Minimal Server Interface is not supported.
Table 4-8 Database and backup server requirements (Microsoft Exchange
Server)
Operating system
(64-bit)
IPv6
support
Y
Required programs
CCI13
standard Windows LDM6)
RM Shadow Copy Provider (VSS
Provider) 01-02-03/05
4-10
Operating system
IPv6
support
Required programs
Y
Windows Server 2008 R2 no SP2
Y1
CCI13
Provider) 01-02-03/05
Device Manager Agent v 6.0 or later2
Y1
CCI13
Provider) 01-02-03/05
Y1
CCI13
Y1
CCI13
Notes:
1.
CLI. For details about using FTP with the CLI, see the Hitachi Command
Suite Replication Manager Application Agent CLI User Guide.
2.
If either of the following conditions apply when installing Device Manager
agent:
¢
The version of Device Manager agent is earlier than 6.4
The version of CCI is earlier than 01-17-03/05
You must configure the following setting in the Device Manager properties
(server.properties) file:
¢
If you do not add this value, Replication Manager might not be able to
acquire pair, pool, and journal information. For details on editing the
4-11
properties file, see the Hitachi Command Suite Installation and
Configuration Guide. For details about Device Manager agent versions
that correspond to each OS, see the Device Manager Release Notes.
3.
When performing a VSS backup, dynamic disks are not supported.
4.
In the cluster configuration, GPT disks are not supported. Use MBR disks
when using this product to perform a backup.
5.
Provided as a guest OS of virtual server product VMware ESX/ESXi
Servers 4.x and 5 are also supported. However, VMware FT is not
supported. To execute Application Agent on the virtual server, configure
the virtual server as the recommended configuration written in the
manual.
6.
LDM basic structure is supported.
7.
This is supported when using the Application Agent CLI.
8.
Be sure to install the same version of Application Agent on the database
and backup servers.
9.
Configurations including storage pools are not supported.
10. Operation on Server Core is not supported.
11. Operation on Minimal Server Interface is not supported.
12. When applying the VSS correction module that includes Hotfix 940349, be
sure and apply the module on all servers using VSS.
Caution: If you execute a VSS backup for a GPT disk, registry keys
related to the backup server GPT disk are added. If the VSS backup is
repeated and too many device entries have accumulated in the registry,
the backup might fail. Therefore, we do not recommend using Application
Agent in an environment that uses GPT disks. If you want to execute a
VSS backup for a GPT disk, follow the instructions in the Microsoft
technical information note KB934234, and clean up the backup server
registry after executing a VSS backup.
Additional server requirements
The following are other requirements and precautions for the database and
backup servers.
Virtual memory
Application Agent requires virtual memory on the database and backup
servers. If the virtual memory area is insufficient, program operation might
become unstable. Use the formula below to calculate the amount of virtual
memory required.
Virtual memory = (8.0 + number-of-databases + number-of-data-files +
number-of-mounted-drives * 2.0 + number-of-physical-disks + number-ofsecondary-volumes * 0.2 + number-of-paired-volumes * 0.2 + number-ofdatabases-to-be-backed-up * 0.3 + number-of-data-files-to-be-backed-up *
4.0 + number-of-drives-to-be-backed-up * 0.3 + number-of-files-or-
4-12
directories-to-be-backed-up * 4.0 + number-of-paired-volumes-to-bebacked-up * 0.1) * number-of-backup-catalogs
The number-of-backup-catalogs is determined as follows:
•
For a database server: The number of backup catalogs backed up from
the P-VOLs to the S-VOLs. If a single P-VOL is defined to be paired with
multiple S-VOLs, Application Agent can manage multiple backup
generations. The number corresponds to the number of backups made in
such a configuration.
•
For a backup server: The number of backup catalogs backed up from the
S-VOL to a tape.
User authorization for command execution
The following authorizations are required to execute Application Agent
commands:
•
OS administrator permissions and administrator privileges
A user executing a Application Agent command must have local
Administrator authorization on the server on which the command is to be
executed. In a Windows Server 2008 operating environment, the user
must also have OS administrator privileges. If the user does not have OS
administrator privileges, an error message appears, and command
execution fails.
•
Database access authorization
¢
¢
When backing up an SQL Server database: When a user executes a
Application Agent command, Windows must first authenticate the user
before gaining access to the SQL Server. A user must have sysadmin
authorization to execute Application Agent commands for an SQL
server.
When backing up an Exchange database: A user must be assigned to
the Enterprise Admins group or the Exchange Domain Servers group
of a domain to execute Application Agent commands.
Account for Application Agent Services
Before installing Application Agent, you must create an account that will be
used to execute the Application Agent Services (a collective term for the Copy
Controller service and the Common Agent Service).
The account must satisfy the following conditions:
•
It must have OS administrator permissions.
•
In Security Policy, Logon as a service must be enabled and Deny logon
as a service must be disabled.
•
It must have the following database access permissions:
For backing up an Exchange database: The account used to execute
Common Agent Service must belong to the Enterprise Admins group or
Exchange Domain Servers group in the domain.
4-13
For backing up a SQL Server database: Application Agent accesses SQL
Server using Windows authentication. Therefore, the account used to
execute the Common Agent Service must be registered as a member that
has a sysadmin fixed server role for SQL Server.
Exchange Management Tool
The same version of Exchange Management Tool must be installed on the
database and backup servers.
Environment variables
Do not specify HORCMINST or HORCC_MRCF in a system environment variable.
Also, do not specify HORCM_CONF or HORCMPERM in a system or user
environment variable.
HORCM options and CCI
HORCM_DEV, HORCM_LDEV, or HORCM_LDEVG need to be specified in the
configuration 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-VOL
configuration definition files. (If you omit HORCM_LDEVG, the P-VOL might be
disconnected from the database server when you perform an Application
Agent operation.)
Make sure that there are no copy pairs consisting of disks that are not
connected 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 be
assigned as a network drive. The P-VOL of a file system that is a target of
backup and restore operations needs to be mounted.
Application Agent versions on database and backup servers
The same version of Application Agent must be installed on database and
backup server pairs. Do not, for example, install version 6.3 on the database
server and 6.4 on the corresponding backup server.
Remote copy type support
Microsoft Exchange Server uses VSS to create replicas. Because VSS only
supports TCS for remote copies, Replication Manager must use TCS to create
remote replicas. (TCA and UR remote replicas are not supported. VSS does
not allow the split time to exceed 10 seconds, and these copy types cannot
meet this requirement.)
4-14
Because Microsoft SQL Server does not use VSS (it uses VDI), there is no
limitation on the remote copy type for linkage with Microsoft SQL Server.
TCS, TCA, and UR are also supported.
Replica operations between storage systems
Application Agent is compatible with TrueCopy and Universal Replicator
backups to (and restorations from) remote site storage systems, for when a
failure occurs on a local site storage system. Depending on the DBMS product
linked to, different volume replication functions can be used:
•
Exchange Server: TrueCopy Sync
•
SQL Server: TrueCopy and Universal Replicator
Copy types supported for replica operation
The following system configurations can be used to perform backups and
restorations 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#0
disk among the physical disks that are connected to the device adapter port
for the primary and secondary volumes. When the physical disk of LUN#0 is
used, other physical disks might not be recognized.
When reinstalling Application Agent
When Application Agent is removed, configuration files might remain. Before
re-installing Application Agent, you should manually delete the entire
directory where Application Agent was installed.
Maximum number of Application Agent instances
The maximum number of Application Agent instances that can be registered
is 128.
SQL server log distribution function
The SQL Server log distribution function can be used when SQL Server
databases are backed up. To do this, there must be two servers; a server
from which to distribute the log files and a server to which to send the log
files.
4-15
For this type of configuration, Application Agent must be installed on both
servers.
VSS Provider requirements
The following are requirements for RM Shadow Copy (VSS Provider) installed
with Application Agent.
Software version
Replication Manager and Application Agent support VSS Provider 01-02-03/05
or later. The prerequisite CCI version is 01-19-03/04 or later.
VSS backups and Windows Server 2008/2012
The following applies to Windows Server 2008/2012 environments.
After a VSS backup, a disk containing a backup server's secondary volume is
taken offline. However, if the backup fails, the disk might be put online. In
such a case, follow the procedure described in Disk status remains online
after replica operation is complete on page 7-21.
Host Bus Adapter (HBA)
Make sure that both the HBA and HBA driver support VSS. Application Agent
does not support Emulex Full Port drivers.
Windows services
Before you install Application Agent, use the Services pane in the Server
Manager console to ensure that the Windows services are set to the default
settings as shown in the following table.
Table 4-9 Services and settings required for installation of VSS Provider
Service name
4-16
Displayed name
Prerequisite condition for
startup
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 are
not set to their default settings, the VSS Provider service will not be
registered as a Windows service.
Storage systems requirements
Application Agent supports the following storage systems:
•
Hitachi WMS series
•
Hitachi AMS series
•
Hitachi AMS2000 series
•
Hitachi USP
•
Universal Storage Platform V
•
Universal Storage Platform VM
•
Virtual Storage Platform
•
Virtual Storage Platform G1000
•
HUS100 series
•
HUS VM
•
VSP G200, G400, G600
Note: If the backup or database server operating system is Windows Server
2012, Application Agent only supports the Virtual Storage Platform, VSP
G1000, HUS VM, and HUS100 series.
The volume replication functions required to use Application Agent with the
storage systems are listed in the following table.
Table 4-10 Copy types supported
Storage system
Volume replication function
Hitachi AMS series
ShadowImage
Hitachi WMS series
TrueCopy
Hitachi AMS2000 series
Copy-on-Write SnapShot
HUS100 series
Hitachi USP
ShadowImage
Universal Storage Platform V
TrueCopy
Universal Storage Platform VM
TrueCopy Asynchronous
Universal Replicator
Hitachi VSP
ShadowImage
TrueCopy
Thin Image
Hitachi VSP G1000
ShadowImage
4-17
Storage system
Volume replication function
TrueCopy
Thin Image
global-active device
HUS VM
ShadowImage
VSP G200, G400, G600
Thin Image
TrueCopy
Note: Application Agent for Exchange does not support Universal Replicator.
Note: Replication Manager supports Virtual Storage Platform as of version
7.0.0, VSP G1000 as of version 8.0.0, and HUS VM as of version 7.3.1.
However, the following limitations apply:
•
If a version of Replication Manager earlier than v7.1.0 is used, user
authentication on the command device must not be set to Enabled.
•
Replication Manager and Application Agent must not be installed on the
same server (v7.1.0 or later).
•
On systems where Replication Manager is running on the pair
management server: if a configuration definition file has been created
through Replication Manager, and subsequently CCI commands are
executed by using a script or other method that does not go through
Replication Manager, a user authentication command (raidcom -login or
raidcom -logout) must be executed (v7.1.0 or later).
Cluster support
Application Agent can be linked to cluster software to increase the availability
of the system. The following tables summarize the cluster software
configurations that can be used with Application Agent.
Table 4-11 Database server requirements for cluster environment
(Exchange Server 2007)
Database server OS
Windows Server 2008 no SP/SP1, SP2
Windows Server 2008 R2 no SP or SP1
4-18
Cluster software
Clustering
Table 4-12 Database server requirements for cluster environment (SQL
Server and file systems)
Database server OS
Windows Server 2008 no SP/SP1, SP2
Windows Server 2008 IPF no SP/SP1, SP2
Cluster software
Clustering
Windows Server 2008 no SP/SP1, SP2 (64-bit)
Windows Server 2008 R2 no SP or SP1
Windows Server 2008 R2 IPF no SP or SP1
Windows Server 2012 no SP 1
Windows Server 2012 R2 no SP 1
Notes:
1.
Be sure to install the FailoverCluster-CmdInterface (an optional
component of WSFC). For details about optional components, see the
Microsoft documentation.
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 (ActivePassive). 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 database
is taken offline while the cluster resources that are monitoring the
database are still online, a failover will occur. This usually requires
controlling control cluster resources manually. With Application Agent,
cluster resources that monitor the database are automatically taken down
and brought back online whenever Application Agent is used to perform a
backup or restore operation for data.
•
In a cluster environment using WSFC, you can choose whether to perform
a restore operation while the cluster resources that monitor the database
are online or offline. For a restore operation in which the cluster resources
are offline, you need to take all the databases that are using the database
services offline. However, for a restore operation in which the cluster
resources are currently online, you only need to take the databases offline
that are involved in the restore operation.
•
You can put together a cluster configuration using only database servers.
You cannot allocate one cluster server to a database server and the other
cluster server to a backup server.
•
Depending on the storage system type and features of the operating
system, you might not be able to perform a restore operation while the
cluster is online.
4-19
Virtual environments supported by Application Agent
This section describes the following virtual environments supported by
Application Agent:
•
VMware ESX/ESXi Server on page 4-20
•
Windows Server Hyper-V on page 4-22
VMware ESX/ESXi Server
Application Agent supports a Windows environment that functions as a guest
OS. If provided as a guest OS of the virtual server products, VMware ESX/
ESXi Server 4.x and 5.x are also supported. Supported guest OSs are shown
in this table.
Table 4-13 Guest operating systems and VMware ESX/ESXi version
VMware ESX/ESXi
version
ESX 4.0
Guest OS
Windows Server 2008, Windows Server 2008 R2
ESXi 4.0
ESX 4.1
ESXi 4.1
ESXi 5.0 (no update,
Update 1, Update 3)
ESXi 5.0 (Update 2)
Windows Server 2008, Windows Server 2008 R2, Windows
Server 20121, Windows Server 2012 R21
Update 1, Update 2)
Windows Server 2008, Windows Server 2008 R2
Update 1)
Windows Server 2008, Windows Server 2008 R2, Windows
Server 20121, Windows Server 2012 R21
1.
Only SQL Server is supported.
Notes:
4-20
•
Application Agent does not support VMware FT (Fault Tolerance).
•
Do not run VMware live migration (VMware vMotion) and Application
Agent at the same time. If you run both concurrently, execution of
Application Agent might fail. In such a case, please take action according
to message shown in the troubleshooting information.
•
Application Agent can only perform backups of RAW LUNs to which RAW
device mapping has been applied by using the physical compatibility
mode).
•
For VMware ESXi 5.x, configurations are not supported in which a
software FCoE adapter is used to connect a primary or secondary volume
to a database server, backup server, or pair management server on a
guest OS.
•
Depending on the connection method used by the guest OS, the VMware
ESX/ESXi support status varies. The support status for each connection
method used by the guest OS is as follows:
Table 4-14 VMware ESX/ESXi support status for each connection method
used by the guest OS
Physical
connection
FC
Raw device mapping
iSCSI
Compatible
mode
Disk type
Supported/Not
Supported
Physical
Yes1
Virtual
No
Virtual disk
―
No
Raw device mapping
Physical
Yes1
Virtual
No
―
No
Virtual disk
Directly connected to a guest ―
OS
Yes
Notes:
1.
Database servers that are configured on a guest OS are supported.
Backup servers that are configured on a guest OS are supported if all of
the following conditions are satisfied:
¢
The backup target is a file system or SQL Server.
¢
The secondary volume is a single generation.
¢
The backup is not made with VSS.
¢
¢
In the Setup Application Agent dialog box when making settings for
the backup server, on the Replica Options tab, the Prohibit backup
server from accessing unmounted replicas check box is not
selected (default setting). If you want to use the Application Agent
CLI to disable Prohibit backup server from accessing unmounted
replicas, you must disable the dynamic recognition of secondary
volumes. For details about how to disable dynamic recognition of the
secondary volumes, see the Hitachi Command Suite Replication
Manager CLI User Guide.
If any of the conditions above is not satisfied, do not configure the
server in a virtual environment.
Required virtual memory when running Application Agent on a
VMware ESX/ESXi virtual machine
See Virtual memory on page 4-12 for information on virtual memory
requirements.
4-21
Windows Server Hyper-V
Application Agent supports a Windows environment that is run as a guest OS
of Windows Server 2008 Hyper-V and Windows Server 2012 Hyper-V. The
following tables list the scope of support for each Application Agent product.
Table 4-15 Guest OS of Windows Server Hyper-V supported by Application Agent
Guest OS of
Windows
Windows
Server HyperServer HyperV version
V
Windows
Server 2008
Hyper-V
Windows
Server 2012
Hyper-V
Windows
Server 2012
R2 Hyper-V
Application Agent
Exchange
Exchange
Server 2007 Server 2010
Exchange
Server
2013
SQL
Server1
File
system
Windows
Server 2008
(32-bit) (no
SP/SP1, SP2)
N
N
N
Y2
Y
Windows
Server 2008
(64-bit) (no
SP/SP1, SP2)
Y
Y
N
Y2
Y
Windows
Y
Server 2008 R2
(no SP, SP1)
Y
Y
Y2, 3
Y
Windows
N
Server 2008 R2
(no SP, SP1)
Y
Y
N
N
Windows
Server 2012
(no SP)
N
N
Y
Y2
Y
Windows
N
Server 2012 R2
(no SP)4
N
N
Y2, 5
N
Legend:
Y: Supported
N: Not supported
Notes:
1.
If your environment meets the following requirements and you use the
Application Agent CLI, then Live Migration (such as Hyper-V Live
Migration) is supported:
Note: If the requirements are not met, ensure that the guest OS where
Application Agent is installed is not a target of Live Migration.
¢
4-22
If you use Windows Server 2008 Hyper-V, the host OS is Windows
Server 2008 R2, and the SQL Server version is one of the following:
SQL Server 2005 SP3 or later
SQL Server 2008 SP1 or later
SQL Server 2008 R2
¢
¢
¢
¢
¢
If you use Windows Server 2012 Hyper-V, the SQL Server version is
either of the following:
SQL Server 2012
SQL Server 2014
A cluster configuration is set up for the host OS
A virtual command device is used. For details about how to set up a
virtual command device, see the CCI documentation.
While it is possible to use a configuration where the command device
is connected directly to the database server, you must perform
operations on the host OS to disconnect the command device's drive
from the guest OS prior to live migration and reconnect it after
completion. For details about these disconnection and connection
operations, see the Microsoft documentation related to Windows
Server Hyper-V.
A configuration is used where the system drive of the guest OS is
positioned in the VHD format on the drive managed as a cluster
shared volume (CSV) by the WSFC of the host OS Replication
Manager does not support configurations where the system drive of
the guest OS is positioned on a drive that is used as a normal physical
disk resource of a WSFC.
The period of executing Live Migration does not overlap with the
period of executing Application Agent CLI. (If they overlap, Application
Agent CLI may fail.)
2.
When the disk used is an iSCSI direct connect, the SQL Server cluster
configuration on multiple guest operating systems is supported.
3.
SQL Server 2005 SP3 or later is supported.
4.
When you install a guest OS on Windows Server 2012 R2 Hyper-V, you
can choose a first or second generation virtual machine. However,
Application Agent only supports the first generation.
5.
SQL Server 2012 SP1 or later is supported.
Table 4-16 Windows Server Hyper-V support based on the guest OS connection method
Physical
connection
Fibre Channel
Guest OS connection
method
Guest OS
Supported
Pass through
RAID (offline)
RAID
Y
VHD/VHDX Variable/Fixed
RAID
Non-RAID
N
RAID
Non-RAID
N
Direct connection
--
RAID
N
Pass through
RAID (offline)
RAID
Y
VHD/VHDX Variable/Fixed
RAID
Non-RAID
N
RAID
Non-RAID
N
Registered as a
CSV
iSCSI
Host OS
Registered as a
CSV
4-23
Physical
connection
Guest OS connection
method
Direct connection
Host OS
--
Guest OS
RAID
Supported
Y
Note: The following restrictions apply:
•
SQL Server cluster configurations are not supported on guest operating
systems, except for a limited subset of configurations between guest
operating systems, which are supported only in Replication Manager
version 7.1 and later. However, note that in these configurations, you
must use disks that are directly connected to iSCSI, and the SQL version
must be one of the following: SQL Server 2005, SQL Server 2008, SQL
Server 2008 R2, and SQL Server 2012.
•
The backup server cannot support a Windows Server Hyper-V
environment if a pass-through connection is used and the secondary
volume is recognized dynamically (hidden). Backup using VSS is not
supported if a pass-through connection is used.
Hyper-V Live Migration
In addition to the notes provided in the Application Agent CLI and Windows
Server 2008 Hyper-V documentation, please note the following points when
using the Application Agent CLI under a guest OS intended for live migration:
•
Use a configuration where the command device is not connected directly
to the database server; be sure to use a virtual command device. For
details about how to set up a virtual command device, see the CCI
documentation.
While it is possible to use a configuration where the command device is
connected directly to the database server, you must perform operations
on the host OS to disconnect the command device's drive from the guest
OS prior to live migration and reconnect it after completion. For details
about these disconnection and connection operations, see the Microsoft
documentation related to Windows Server 2008 Hyper-V.
•
Use a configuration where the system drive of the guest OS is positioned
in the VHD format on the drive managed as a cluster shared volume
(CSV) by the WSFC of the host OS. Replication Manager does not support
configurations where the system drive of the guest OS is positioned on a
drive that is used as a normal physical disk resource of a WSFC.
Virtual memory required for Application Agent on a virtual machine
of Windows Server Hyper-V
See Virtual memory on page 4-12 for information on virtual memory
requirements.
4-24
Application Agent installation location
By default, the Application-Agent-installation-folder is defined as
follows.
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-Agentinstallation-folder is defined as follows:
folder-specified-by-HDvM-Agent-installer\HBaseAgent
Application Agent installation path restrictions
Make sure the paths used in the installation of Application Agent meet the
following requirements:
•
For the download destination path, the installation path for Application
Agent, and the path specified in the environment variable %TMP%, do not
use a directory name that starts or ends with one or more spaces.
•
For the path specified in the environment variable %TMP%, do not use a
directory name that includes the following characters:
%`&^;
•
For the download destination path for Application Agent, do not use a
directory name that includes the following characters:
%`
•
The installation path must be an absolute path consisting of 124 bytes or
less (subject to program restrictions).
If you plan to install Application Agent on the management server
If you plan to install Application Agent on the management server, you must
first do the following:
If Replication Manager is already installed on the management
server:
1.
Set the value of base.refreshdginfo.exec in the base.properties file
to 0.
2.
Restart the Common Component service as described in Starting
Replication Manager on page 5-2
3.
Select all the remote Device Manager instances and execute Refresh
Configuration
4.
Select all of the storage devices managed by the local Device Manager
instance and execute Refresh Storage System Information.
4-25
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 Manager
cannot manage copy groups defined in storage (device groups).
Installing Application Agent
Note: This procedure applies to both cluster and non-cluster configurations.
Before starting the installation, stop all running programs. For example,
Exchange Server 2013 includes services such as the Microsoft Exchange
Health Manager service. You must stop all services associated with Microsoft
Exchange Server or SQL Server prior to installing Application Agent.
Caution: If you perform an upgrade or overwrite installation of Application
Agent, the existing setting of the Application Agent service is preserved, but
the login account of the common agent component service (HBsA) might be
reset to the default local system account. In this case, when the installation is
completed, select HBsA Service from the Windows Services dialog and then
set the logon account of the service to an Administrators group user.
To install the agent, follow this procedure:
1.
Log on to Windows as a member of the Administrators group on each of
the database and backup servers where you plan to install Application
Agent.
2.
If you are installing from the integrated installer, insert the media.
If you are installing from the GUI, proceed to step 4.
3.
Start the installer as follows:
¢
¢
In the case of the integrated installer media for Windows:
In the displayed window, click the Install button next to Replication
Manager Application Agent.
If the window is not displayed, manually execute the installer
(setup.exe). The Installer is stored in drive:/AGENTS/HRPM_APP.
In the case of the integrated installer media for UNIX:
Execute the installer (setup.exe). The Installer is stored in drive:/
AGENTS/HRPM_APP.
Proceed to step 7.
4.
4-26
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. Then
click Next.
9.
You will be prompted to choose a destination location in the Destination
Location field in the next window. Use the Browse... button to navigate
to your selection. Then click Next.
10. After selecting a destination, you are prompted to select the components
to install or remove using Select Features. The choices are Component
for SQL and Component for Exchange.
Note: When installing on Windows Server 2008 (32-bit) and Windows
Server 2012, the option to install the Component for Exchange may
not be displayed. If you plan to perform VSS backups, you must select to
install the Component for SQL instead and then install the Shadow Copy
Provider manually. (The Shadow Copy provider is bundled with the
Component for Exchange.) For information on installing the Shadow
Copy 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 the
Browse... button to navigate to your selection. Then click Next.
13. You will now be prompted whether you would like to register the
Application Agent to the allowed program configuration of your firewall in
order for the agent to work while that firewall is activated. Select the Yes
or the No button in the Windows Firewall Settings window to set your
choice. Then click Next.
14. The Start Copying Files window appears, allowing you to review your
settings before proceeding with the file copying. Review the settings. If
you wish to change any, use the Back button. If you are satisfied with
the settings, click Next to begin copying files.
15. The Setup Status window appears, displaying the progress of the
operation.
16. The Replication Manager - Application Agent Setup window appears.
Enter the User name and Password in the respective fields, for an
account that has Administrator permissions and the “Log on as a service”
permission and click Next.
17. You are asked if you wish to setup the Device Manager agent. If you
choose Yes, follow the instructions for installation and configuration of
the HDvM agent as described in the Hitachi Command Suite Installation
and Configuration Guide.
18. When the installation finishes, restart Windows.
4-27
Note: If the Application Agent is installed on a host without a database
application installed, Replication Manager will fail in any attempts to
obtain information by refreshing the host. If this occurs, one of the
following error messages is displayed:
RPM-11004 - The specified SQL instance name is invalid or no
SQL instance settings exist. RPM-11509 - Exchange Server has
not yet been installed on this system.
Adding Application Agent to the Windows Firewall Exception
list
Note: This procedure is not required unless:
•
You selected not to add the exceptions when prompted during the
Application Agent installation (or the process of adding the exceptions
failed).
•
You enabled the firewall after installing Application Agent.
•
You migrated Protection Manager to Application Agent.
The Application Agent service services are as follows:
•
Copy Controller
•
Common Agent
To configure these services as exceptions:
1.
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 CCI
The following sections concern the interaction of Application Agent and CCI:
•
Command line interface for CCI on page 4-28
•
Protection function of CCI on page 4-29
•
Using CCI to configure pair volumes on page 4-29
•
Device Manager and CCI on page 4-29
•
Starting and stopping CCI on page 4-29
Command line interface for CCI
Note the following precautions regarding using the CCI command line
interface:
4-28
•
Do not use the CCI command line interface while carrying out replica
operations from Replication Manager.
•
If you use the CCI command line interface to change a copy pair
configuration, be sure and refresh the system from Device Manager,
followed by updating the pair configuration and refreshing the hosts from
Protection function of CCI
Application Agent does not support the protection function of CCI. This
function should be disabled on servers where Application Agent is installed.
Using CCI to configure pair volumes
Within a copy group, only include the pair volumes for one application. If the
pair volumes of multiple applications are mixed together in one copy group,
unintended backups and restorations might occur.
Device Manager and CCI
For 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 CCI
instance on both the backup and database servers before carrying out replica
operations. (If CCI is not started, the replica operation will fail.)
Starting and stopping CCI
Application Agent automatically starts and stops the local CCI instance as
needed. However, if CCI is already running when Application Agent executes
a command, CCI might not be stopped when the command completes. You
should take this into account when choosing the startup method for each CCI
instance.
Settings for Application Agent in a cluster configuration
This section describes the steps necessary to configure replica operations
properly in a cluster configuration. Application Agent provides a dedicated
command (drmjobsch.exe) for switching the target node. You must set up
this command in the cluster software so that it runs automatically when a
failover occurs.
Verify the following before performing the appropriate procedure for the
cluster software you are using:
•
Application Agent and the cluster software have been installed
successfully.
•
You have logged in as a member of the Administrators group.
4-29
Perform the following procedure on each server that makes up the
virtual server:
1.
Create a VBScript file named RecoverJob.vbs in the following location:
Application-Agent-installation-folder\DRM\schedule
You can specify a different name and location for the VBScript file, but for
maintenance reasons, we recommend that you use the above file name
and file storage location.
2.
In the VBScript file, specify the recovery processing to be performed by
drmjobsch.exe. At the entry point Function Online( ), specify that the
following command is to be executed (where virtual-server-name is the
name of a virtual server to be put online):
Application-Agent-installation-directory\DRM\bin\drmjobsch.exe
-recover -hostname virtual-server-name
See Sample VBScript file on page 4-30 for a completed script. In the
example, Application-Agent-installation-folder is C:\Program
Files\HITACHI\DRM.
3.
Use the Failover Cluster Management wizard to add the new resource to
the cluster resource group with the name virtual-server-name (such as
a cluster resource group for Exchange Server).
Resource type: Generic script
Script file path: Path name of the created VBScript file
If the VBScript file is stored on a shared disk for nodes, be sure and
register this shared disk as a physical disk resource in the Resource
dependencies field in the Dependencies dialog box.
Sample VBScript file
Note: CHR(34) indicates a double quotation mark ("). When Application
Agent-installation-folder does not contain any spaces, you do not need
to specify CHR(34). The following is the specification when there are no
spaces:
"C:\drm\bin\drmjobsch.exe" & " -recover -hostname virtual-servername"
For details on the specification method, consult your VBScript documentation.
'Script-Level Global Variables
Resource.LogInformation("Script-wide code begins execution")
Dim WshShell, oExec
Set WshShell = CreateObject("WScript.Shell")
Function Online( )
Online = 0
Resource.LogInformation "Entering Online"
Set oExec = WshShell.Exec (CHR(34) & "C:\Program Files\HITACHI
\drm\bin\drmjobsch.exe" & CHR(34) & " -recover -hostname virtualserver-name")
Do While oExec.Status = 0
Set oWait = WshShell.Exec("timeout /t 1")
Loop
Resource.LogInformation "Exiting Online"
End Function
Function Offline( )
4-30
Offline = 0
End Function
Function LooksAlive( )
LooksAlive = 0
End Function
Function IsAlive( )
IsAlive = 0
End Function
Function Open( )
Open = 0
End Function
Function Close( )
Close = 0
End Function
Function Terminate( )
Terminate = 0
End Function
Application Agent and Replication Manager log output
The number of Application Agent instances in your storage configuration must
be considered when configuring the amount of log output, as described in
About Replication Manager log output on page 5-11.
If the number of target Application Agent instances exceeds 30, you need to
tune the file capacity and number of files as follows:
Trace log size = current-file-capacity + 2.6 * number-of-Application-Agent
instances
Database log size = current-file-capacity + 0.5 * number-of-ApplicationAgent instances
Application status log size = current-file-capacity + 3.8 * number-ofApplication-Agent instances
Changing Application Agent port numbers
Tip: The port number used for communication between Application Agent
instances (backup and database servers) can be changed during Application
Agent setup (the default is 22300). If this port number has already been
used, you must register the port number into the Windows Services file as
DRMVSSServer.
You can change the port numbers used by the Agent daemon, the API
response process, and communication with the API response process, by
editing the server.properties file on the backup and database servers. The
file 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
4-31
The properties and default values are listed in the following table.
Table 4-17 Port numbers in server.properties file
Property
Default value (port
number)
Purpose
server.agent.port
24041
Port number for the
Common agent daemon
process (service).
server.http.port
24042
Port number for the
communication between the
Common agent daemon
process and the web server
process.
server.http.localPort
24043
Port number for Common
agent Web server.
Note the following:
•
Acceptable port number values are 1-65535.
•
Avoid using small port numbers because such numbers might conflict with
other applications.
•
The port numbers set in the server.properties file must be unique and
cannot be shared by any other processes.
•
If you change the value of server.agent.port, you must also change the
port number for Application Agents registered as information sources.
•
After changing these values, the Common Agent Service must be
restarted.
Starting and stopping the Application Agent Services
To use Replication Manager to perform a backup, the Application Agent
Services 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 and
stopped automatically on the database or backup server where the agent is
installed. Should you need to start or stop them manually, use the commands
described in the sections that follow (Administrator privileges are required).
Copy Controller service
To start or stop the Copy Controller service, launch the service screen of
Server Manager and start or stop the Protection Manager Service.
Common Agent service
To stop and start the Common Agent Service, use the following commands:
4-32
Hitachi-Command-Suite-Common-Agent-Component-installation-folder
\bin\hbsasrv.exe stop
Hitachi-Command-Suite-Common-Agent-Component-installation-folder
\bin\hbsasrv.exe start
Tip: After installing Application Agent, if the Copy Controller service or the
Common Agent Service is Disabled, change the setting to Automatic.
The Common Agent Service is used by other agent programs (such as Device
Manager Agent). When you stop Common Agent Service, you should
determine whether or not the operation of other agents is affected.
Setting error logging options for Application Agent
The agent.logger.properties file is used to specify the values of log
output-related properties. 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 the
specified value is outside the specifiable range, the default value is used.
The following tables list the available properties, the types of information
logged, and the parameters that are stored when values are logged.
Table 4-18 List of properties in the agent.logger.properties file
Property
agent.logger.loglevel
Description
The output level of the Replication Manager log file.
Messages matching the type are output to the log
file.
Specifiable values: One of the three following
scenarios: DEBUG and INFO, WARN,
or ERROR and FATAL.
See Table 4-19 Error values and descriptions on page
4-34 for a description of the types and Table 4-20
Logged values on page 4-34 for a list of types
logged for each level. These values can be entered in
any combination of upper and lower case.
Default value: INFO
agent.logger.MaxBackupIndex
The maximum number of log files created in
Replication Manager. When the number of log files
reaches this value, the existing files are reused,
starting with the oldest file.
Specifiable values: 1 to 20 (files)
Default value: 10
agent.logger.MaxFileSize
The maximum size of a single Replication Manager
log file. This value must be specified in bytes,
kilobytes, or megabytes. If the specified value is not
followed by KB or MB, the size is assumed to be in
bytes.
4-33
Property
Description
Specifiable values are determined by the specified
unit as follows:
Bytes: 524288 to 33554432
KB: 512K B to 32768 KB
MB: 1 MB to 32 MB
Default value: 5 MB
Table 4-19 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 the
process execution continues.
ERROR
Error occurred during the process execution or startup.
FATAL
Fatal exception occurred in the code and the execution stops.
Table 4-20 Logged values
Values
Logged
DEBUG
INFO
DEBUG
WARN
ERROR
X
INFO
4-34
WARN
X
X
ERROR
X
X
X
FATAL
X
X
X
X
FATAL
5
Operating the management server
This chapter describes the Replication Manager settings and operating
procedures, including how to start and stop Replication Manager and how to
back up and restore the databases.
□ About executing commands on the management server
□ Starting and stopping Replication Manager
□ Changing settings in the properties files
5-1
About executing commands on the management server
This section includes information related to the execution of commands that
are required for Replication Manager operation.
User permissions
To execute the commands described in this manual, you must log in as a
member 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 to
elevate your current privileges to the Administrator level. Because some
commands necessary to operate a management server require just such
privileges, you should do so (unless specifically instructed otherwise).
To elevate your privileges to the Administrator level for executing a
command:
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 Linux
The directories for basic OS commands must be specified as the first entries
in the PATH environment variable. If an error occurs when you execute a
command because a command was not found or because another utility
exists in a path with the same name, edit the PATH environment variable so
that the directories for basic OS commands are specified first.
Starting and stopping Replication Manager
This 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). This
means that you start and stop Replication Manager by starting or stopping
the Hitachi Command Suite Common Component services.
For more information see Starting and stopping the Application Agent
Services on page 4-32.
Note: Device Manager must be running for Replication Manager to operate
properly.
Starting Replication Manager
To start Replication Manager, use the appropriate procedure below.
5-2
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 > Manage
Services > Start - HCS.
Select All Apps from the Start menu, then select Hitachi Command
Suite > 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 -start
When you execute the command, the services of other Hitachi Command
Suite products are also started. However, if Hitachi Command Suite Common
Component services are already running, the services of Hitachi Command
Suite products are not automatically started, and you must start them
manually. Because Device Manager must be running for Replication Manager
to operate properly, start the Device Manager service first. For details about
how to start this service, see the Hitachi Command Suite Administrator
Guide. For details about how to start the services of other Hitachi Command
Suite products, see the manuals for each product.
Stopping Replication Manager
To stop Replication Manager, use the appropriate procedure below.
In Windows
1.
2.
a.
Services > Stop - HCS.
Suite > Manage Services > Stop - HCS.
b.
Common-Component-installation-folder\bin\hcmds64srv /stop
5-3
In Linux
1.
2.
Common-Component-installation-directory/bin/hcmds64srv -stop
This command also stops the services of other Hitachi Command Suite
products, so you should consider the operation of these products before
executing this command.
Checking the operation status of Replication Manager
To see whether Replication Manager is running, use the appropriate
procedure below.
In Windows
1.
2.
a.
Services > Status - HCS.
Suite > Manage Services > Status - HCS.
b.
Common-Component-installation-folder\bin\hcmds64srv /status
In Linux
1.
2.
Common-Component-installation-directory/bin/hcmds64srv -status
Example 1: Execution results if Replication Manager is running
KAPM05007-I Already started
Mgmt Web Service
Mgmt Web SSO Service
Mgmt SSO Service
Web Service
Mgmt Common Service
Server Service
Manager Server Service
5-4
service. service-name=HBase 64 Storage
service. service-name=HCS Device Manager
service. service-name=Device Manager
service. service-name=Tiered Storage
Example 2: Execution results if Replication Manager has stopped
KAPM05009-I Already stopped
Mgmt Web Service
Mgmt Web SSO Service
Mgmt SSO Service
Web Service
Mgmt Common Service
Server Service
Manager Server Service
service. service-name=HCS Device Manager
service. service-name=Device Manager
service. service-name=Tiered Storage
If you execute the command as described above, you can also check whether
the HiRDB service is running. If it is running, the following message appears
in the execution results:
KAPM06440-I The HiRDB service has already started.
The following message appears if the service is not running:
KAPM06441-I The HiRDB service has already stopped.
Changing settings in the properties files
This section describes the settings in the properties files used by Replication
Manager and how to change them.
Use a text editor to alter parameters in the properties files. After making
changes, you must do the following:
•
Restart Replication Manager. To do this, you must first stop and then
start the services. For details, see Starting and stopping Replication
Manager on page 5-2.
•
In a cluster environment, the values in the properties files of the
executing and standby nodes must match. (If you change a properties file
on the executing node, you must do the same for the standby node.)
Note: Inappropriate changes to properties files can have unexpected
results. We recommend that you use the default values unless they cause
problems.
Properties related to Replication Manager
The properties required by Replication Manager are specified in the following
properties files stored on the management server:
•
logger.properties on page 5-8
•
serverstorageif.properties on page 5-11
•
bcmif.properties on page 5-12
5-5
•
agentif.properties on page 5-13
•
appagentif.properties on page 5-14
•
base.properties on page 5-14
•
RpMCLI.properties on page 5-17
With the exception of RpMCLI.properties, these files are in the following
directories/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 (not
conf).
The following table lists the properties and default values for each file.
Note: Under normal circumstances, the agentif.properties properties do
not need to be changed. To change their values, you need expert knowledge
of Device Manager Agent.
Table 5-1 List of Replication Manager properties
File
logger.properties
5-6
Property
Default
value (unit)
logger.loglevel
20
logger.sysloglevel
0
logger.MaxBackupIndex
6 (files)
logger.MaxFileSize
20MB
logger.DB.loglevel
20
logger.DB.MaxBackupIndex
6
logger.DB.MaxFileSize
20MB
logger.RefreshConfig.enabled
true
logger.RefreshConfig.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
10MB
logger.AppConfig.MaxBackupIndex
3 (files)
File
serverstorageif.propert
ies
bcmif.properties
agentif.properties
appagentif.properties
base.properties
Property
Default
value (unit)
logger.AppConfig.MaxFileSize
10 (MB)
logger.AppConfig.enabled
true
logger.AppStatus.MaxBackupIndex
6 (files)
logger.AppStatus.MaxFileSize
20 (MB)
logger.AppStatus.enabled
true
ssif.socketTimeout
3600
(seconds)
ssif.socketConnectTimeout
5 (seconds)
ssif.alertTimeout
1800
(seconds)
bcmif.socketTimeout
3600
(seconds)
bcmif.socketConnectTimeout
5 (seconds)
bcmif.ReconnectionInterval
60 (seconds)
bcmif.ReconnectionCount
5 (times)
agentif.connectTimeout
30 (seconds)
agentif.responseTimeout
3600
(seconds)
hdvmagtif.connectTimeout
30 (seconds)
hdvmagtif.responseTimeout
3600
(seconds)
hdvmagtif.MaxPollingCount
50 (times)
hdvmagtif.PollingInterval
30 (seconds)
appagentif.connectTimeout
30 (seconds)
appagentif.responseTimeout
3600
(seconds)
base.repositry.synchronize.polling
true
base.taskscheck.interval
120
(seconds)
base.taskscheck.maxcount
0 (times)
base.taskscheck.mf.interval
120
(seconds)
base.taskscheck.mf.maxcount
0 (times)
base.alert.automarking
true
base.refreshdginfo.exec
1
base.repositry.synchronize.interval
10 (minutes)
5-7
File
Default
value (unit)
Property
RpMCLI.properties
base.repositry.synchrocheck.interval
10 (minutes)
base.rmi.port
25200
base.rmi.enabled
false
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
true
RpMCLI.diaglevel
INFO
RpMTaskCLI.MaxBackupIndex
6 (files)
RpMTaskCLI.MaxFileSize
20 (MB)
logger.properties
The logger.properties file is used to specify the values of log outputrelated properties. If a value is not specified in the logger.properties file,
or if the specified value is outside the specifiable range, the default value will
be used. The following table describes the available properties and settings.
Note: File size values must be specified in bytes, kilobytes, or megabytes. If
the specified value is not followed by KB or MB, the size is assumed to be in
bytes. Specifiable values are determined by the specified unit as follows:
Bytes: 4096 to 2147483647
KB: 4 KB to 2097151 KB
MB: 1 MB to 2047 MB
Table 5-2 List of properties in the logger.properties file
Property
logger.loglevel
Description
The threshold value for the output level of
the Replication Manager log files.
Messages containing values that are equal
to or less than this value are output to the
log file.
Specifiable values: 0, 10, 20, 30 (in
decreasing order of importance from left
to right).
Default value: 20
logger.sysloglevel
5-8
The threshold value for the output level of
the OS event log or syslog that is output
using Replication Manager. Messages
Property
Description
containing values that are equal to or less
than this value are output to the log file.
Specifiable values: 0, 10, 20, and 30 (in
to right).
Default value: 0
logger.MaxBackupIndex
The maximum number of log files created
in Replication Manager. When the number
of log files reaches this value, the existing
files are reused, starting with the oldest
file.
Default value: 6
logger.MaxFileSize
The maximum size of a single Replication
Manager log file.
Default value: 20MB
logger.DB.loglevel
Threshold value for output of a databaserelated log file.
Specifiable values: 0, 10, 20, and 30 (in
to right).
Default value: 20
logger.DB.MaxBackupIndex
Maximum number of backup files for a
database-related log file.
Default value: 9
logger.DB.MaxFileSize
Maximum size of a database-related log
file.
Default value: 20 MB
logger.RefreshConfig.enabled
Enabling or disabling of the configuration
update logging function.
Specifiable values: true or false
Default value: true
logger.RefreshConfig.MaxBackupIndex
configuration update log file.
Default value: 5
logger.RefreshConfig.MaxFileSize
Maximum size of a configuration update
log file.
logger.UserOperation.enabled
Enabling or disabling of the user operation
logging function.
Default value: true
5-9
Property
logger.UserOperation.MaxBackupIndex
Description
user operation log file.
Default value: 5
logger.UserOperation.MaxFileSize
Maximum size of a user operation log file.
logger.RefreshStatus.enabled
Enabling or disabling of the pair status
update logging function.
Default value: true
logger.RefreshStatus.MaxBackupIndex
Maximum number of backup files for a pair
status update log file.
Default value: 2
logger.RefreshStatus.MaxFileSize
Maximum size of a pair status update log
file.
logger.AppConfig.MaxBackupIndex
Maximum number of application
configuration log backup files.
Specifiable values: 1-32 (files).
Default value: 3
logger.AppConfig.MaxFileSize
Maximum size of the application
configuration log file.
Specifiable values: 1-2047 (MB).
Default value: 10
logger.AppConfig.enabled
Log function on/off switch for the
application configuration log.
Specifiable values: true or false.
Default value: true
logger.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 log
file
Specifiable values: 1 to 2047 (MB).
Default value: 20
logger.AppStatus.enabled
Log function on/off switch for the
application status log.
Specifiable values: true or false.
Default value: true
5-10
The following are the output levels of log files and the contents of output
messages:
0: Critical error, high-priority information
10: Non-critical error, medium-priority information
20: Warning
30: All debug information
About Replication Manager log output
The amount of information output to the Replication Manager log files
depends on the memory heap size of the system. Therefore, you must
change the values of the xxxx.MaxBackupIndex and xxxx.MaxFileSize
parameters in the logger.properties file to appropriate values for the
memory heap size. The following table shows the recommended amount of
log data to be retained.
Note: The default values in the logger.properties file assume 6,000 pairs
in an open system and 40,000 pairs in a mainframe system.
Table 5-3 Memory size and amount of output log information
Amount of log data to be retained (MB)
Memory
heap size
Transmission logs
Trace
log
Database log
Configuration
update log
User
operations
log
Pair status
update log
Small
120
120
50
50
20
Medium
130
170
70
50
30
Large
140
230
100
50
30
serverstorageif.properties
The serverstorageif.properties file is used to specify the values of
properties related to the interface between Replication Manager and Device
Manager server. The following table describes the available properties and
settings.
Table 5-4 List of properties in the serverstorageif.properties file
Property
ssif.socketTimeout
Description
The amount of time Replication Manager waits to read data
from Device Manager server. If 0 is specified, Replication
Manager waits until all data is read without timing out.
Specifiable values: 0 to 86400 (seconds)
Default value: 3600
5-11
Property
ssif.socketConnectTi
meout
Description
The amount of time Replication Manager waits to connect to
Device Manager server. If 0 is specified, Replication Manager
waits until a connection is established without timing out.
Default value: 5
ssif.alertTimeout
The amount of time Replication Manager waits to issue an
alert message query to Device Manager server.
Default value: 1800
Note: When you change this value, do not specify a value
greater than the value specified for ssif.socketTimeout
(except zero). If you specify a greater value, alerts might not
be received immediately.
bcmif.properties
The bcmif.properties file is used to specify the values of properties related
to the interface between Replication Manager and Business Continuity
Manager or between Replication Manager and Mainframe Agent. The following
table describes the available properties and settings.
Table 5-5 List of properties in the bcmif.properties file
Property
bcmif.socketTimeout
Description
The amount of time Replication Manager waits to
read data from Business Continuity Manager or
Mainframe Agent. If 0 is specified, Replication
Manager waits until all data is read without timing
out.
Default value: 3600
bcmif.socketConnectTimeout
connect to Business Continuity Manager or Mainframe
Agent. If 0 is specified, Replication Manager waits
until a connection is established without timing out.
Default value: 5
bcmif.ReconnectionInterval
The retry interval when Replication Manager cannot
establish a connection with Business Continuity
Manager or Mainframe Agent. If 0 is specified,
Replication Manager continually attempts to establish
a connection.
Default value: 60
bcmif.ReconnectionCount
5-12
The number of retries attempted when Replication
Manager cannot establish a connection with Business
Property
Description
Continuity Manager or Mainframe Agent. If 0 is
specified, the number of retries is unlimited.
Specifiable values: 0 to 100 (times)
Default value: 5
agentif.properties
The agentif.properties file is used to specify the values of properties
necessary for the interface between Replication Manager and a Device
Manager Agent. Normally, you do not need to change these values. To
change the values, you need expert knowledge of Device Manager Agent. The
following table describes the available properties and settings.
Table 5-6 List of properties in the agentif.properties File
Property
agentif.connectTimeout
Description
connect to a Device Manager Agent when collecting
copy pair statuses. If 0 is specified, Replication
Manager waits until a connection is established without
timing out.
Default value: 30
agentif.responseTimeout
receive a response from a Device Manager Agent when
collecting copy pair statuses. If 0 is specified,
Replication Manager waits for a response is without
timing out.
Default value: 3600
hdvmagtif.connectTimeout
connect to a Device Manager Agent when collecting
configuration information or performing copy pair
operations. If 0 is specified, Replication Manager waits
until a connection is established without timing out.
Default value: 30
hdvmagtif.responseTimeout
receive a response from a Device Manager Agent when
collecting configuration information or performing copy
pair operations. If 0 is specified, Replication Manager
waits for a response without timing out.
Default value: 3600
hdvmagtif.MaxPollingCount
The maximum number of times that Replication
Manager checks the processing status of a Device
5-13
Property
Description
Manager Agent when Device Manager Agent takes an
indefinite period of time to collect configuration
information or to perform copy pair operations. If 0 is
specified, there is no limit on the number of retries.
Default value: 50
hdvmagtif.PollingInterval
The interval at which Replication Manager checks the
processing status of a Device Manager Agent when
Device Manager Agent takes an indefinite period of
time to collect configuration information or to perform
copy pair operations.
Default value: 30
appagentif.properties
The appagentif.properties file is used to specify the values of properties
necessary for the interface between Replication Manager and Application
Agent. Normally, you do not need to change these values. To change the
values, you need expert knowledge of Application Agent. The following table
describes the available properties and settings.
Table 5-7 List of properties in the appagentif.properties File
Property
appagentif.connectTimeout
Description
connect to an Application Agent when collecting
configuration statuses. If 0 is specified, Replication
Manager waits until a connection is established
without timing out.
Default value: 30
appagentif.responseTimeout
receive a response from an Application Agent when
collecting configuration statuses. If 0 is specified,
Replication Manager waits for a response without
timing out. If the specified value exceeds the
maximum, the default value is used.
Default value: 3600
base.properties
The base.properties file is used to specify the values of properties
necessary for the internal processing of Replication Manager. The following
table describes the available properties and settings.
5-14
Table 5-8 List of properties in the base.properties file
Property
Description
base.repositry.sync Specifies whether Replication Manager automatically
hronize.polling
synchronizes with a Device Manager database. A value of true
means that automatic synchronization occurs, and a value of
false means that it does not.
Default value: true
base.taskscheck.int The interval at which Replication Manager checks whether a task
erval
related to a copy pair operation has finished.
Default value: 120
base.taskscheck.max The maximum number of times that Replication Manager checks
count
whether a task related to a copy pair operation has finished. If 0
is specified, there is no limit.
Default value: 0
base.taskscheck.mf. The interval at which Replication Manager checks whether a task
interval
related to a mainframe copy pair operation has finished.
Default value: 120
base.taskscheck.mf. The maximum number of times that Replication Manager checks
maxcount
whether a task related to a mainframe copy pair operation has
finished. If 0 is specified, there is no limit.
Default value: 0
base.repositry.sync The interval at which the HDvM (Hitachi Device Manager)
hronize.interval
database synchronization function performs a check.
Specifiable values: 10 to 1440 (minutes)
Default value: 10
base.repository.syn The interval at which Replication Manager automatically checks
chrocheck.interval
the Device Manager database to see if it has been updated. If 0
is specified, the automatic checking is disabled.
This property is only enabled when the information source is a
remote Device Manager.
Specifiable values: 0 to 1440 (minutes)
Default value: 10
base.refreshdginfo. This property specifies whether to acquire definition information
exec
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 1
Default value: 1
5-15
Property
Description
base.alert.automark This property specifies whether Replication Manager
ing
automatically controls the transition of alerts from Not
Completed to Completed status and whether detection of
transitions in copy pair status in copy groups is performed for
each copy group.
To specify that control and detection are to be performed,
specify true.
To specify that control and detection not be performed, specify
false.
Values that can be specified: true or false
Default value: true
base.rmi.port
This property specifies the RMI registry port number used by
Replication Manager for receiving requests. You must specify
this property if you use the Replication Manager CLI or the
Replication tab of . If you use the Replication tab, you must
set the rpmlib.rpm.port property in the rpmlib.properties
file on the Device Manager server. For details, see the Hitachi
This property is available if the value of the base.rmi.enabled
property is set to true.
Values that can be specified: 1-65535
Default value: 25200
base.rmi.enabled
This property specifies whether the RMI registry is started. You
must specify this property if you use the Replication Manager
CLI or the Replication tab of Hitachi Command Suite.
You must set this property to true if you use the Replication
Manager CLI or the Replication tab of Hitachi Command Suite.
Default value: false
base.rmi.backlog
This property specifies the maximum number of requests
Replication Manager can receive. You must specify this property
if you use the Replication Manager CLI or the Replication tab of
Hitachi Command Suite.
A value of zero (0) sets the value to the Java default value (50).
This property is available if the value of the base.rmi.enabled
property is set to true.
Default value: 100
base.taskschedule.t This property specifies the maximum number of tasks
hreadmax
Replication Manager can execute concurrently.
Default value: 10
base.refreshstorage This property specifies the length of time Replication Manager
.polling.timeout
waits for a Device Manager server refresh of storage system
information.
5-16
Property
Description
Default value: 60
base.pair.performan This property specifies the interval of copy pair performance
ce.interval
information (C/T delta) acquisition from Device Manager agent.
If 0 is specified, the acquisition is not performed.
Value that can be specified: 0-60 (0 and measures of 60)
Default value: 1
base.pair.performan This property specifies the aggregate value of C/T delta.
ce.aggregate
Default value: 5
base.vmhost.enabled The property specifies whether the Hosts view lists virtualization
servers. If some virtualization servers are managed by a remote
Device Manager, refresh the configuration information of the
Device Manager after you change the value of this property.
Default value: true
RpMCLI.properties
The RpMCLI.properties file is used to specify the values of properties
necessary for the Replication Manager CLI.
The following table describes the available properties and settings.
Table 5-9 List of properties in the RpMCLI.properties File
Property
RpMCLI.diaglevel
Description
This property specifies output level of the Replication Manager
CLI trace log. The values that can be specified are: ERROR, WARN,
INFO, DEBUG.
Default value: INFO
The values are case sensitive. The meaning of each value is as
follows:
•
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.MaxBacku This property specifies the maximum number of trace log files
pIndex
(RpMTaskCLIn.log), which are created when the GetTasks or
ExecuteTask command is executed. If a new log file is required
when the number of log files has been reached this value, the
oldest log file is overwritten.
Values that can be specified: 1-16 (files)
5-17
Property
Description
Default value: 6
RpMTaskCLI.MaxFileS This property specifies the maximum size of a trace log file,
ize
which are created when the GetTasks or ExecuteTask command
is executed.
Values that can be specified: 1-20 (MB)
Default value: 20
5-18
6
Security management
This chapter explains security functions that can be used in Replication
Manager.
□ Network communications security
□ Collecting audit logs
Security management
6-1
Network communications security
To provide security for the communication routes used by Replication
Manager, you can use the HTTPS protocol to encrypt communications. The
following routes can be encrypted:
(1) Between Hitachi Command Suite Common Component on the
management server and the Web browser on the management client.
(2) Between Replication Manager on one management server and Device
Manager server on another management server (local or remote).
(3) Between Replication Manager (on the management server) and Business
Continuity Manager (on a host) using IHS.
The numbers (1), (2), and (3) correspond to the diagram that follows.
6-2
Security management
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 Device
Manager Agent (on a pair management server)
•
Between Replication Manager (on the management server) and a
Business Continuity Manager (on the host) unless IHS is used.
•
Between Replication Manager (on the management server) and
Mainframe Agent (on the host).
•
Between Replication Manager (on the management server) and
Application Agent (on the database server or backup server).
Security management
6-3
Securing communications between Hitachi Command Suite Common
Component and Web browsers
To encrypt communications between Hitachi Command Suite Common
Component on the management server and the Web browser on the
management client, you must create a server certificate for Common
Component on the management server and import it into the Web browser on
the management client.
Figure 6-2 Flow of operations for setting up secure communications
between Common Component and a Web browser
For more information on the procedures, see the following descriptions in the
Hitachi Command Suite Administrator Guide:
6-4
•
Creating a secret key and a certificate signing request for Common
Component
•
Applying to a certificate authority for a Common Component server
certificate
•
Enabling SSL/TLS for Common Component
•
Changing the URL for accessing Hitachi Command Suite products
(hcmds64chgurl command)
•
Importing a server certificate into a Web browser
•
Changing pop-up blocker settings
Security management
Note: A secure method must be used to transmit the server certificate for
Hitachi Command Suite Common Component to management clients.
Securing communications between Replication Manager and the
Device Manager server
To encrypt communications between Replication Manager on the
management server and the Device Manager server (local or remote), you
must create a server certificate for the Device Manager server and import it
into the truststore (jssecacerts) file in Replication Manager.
Security management
6-5
Figure 6-3 Flow of operations for setting up secure communications
between Replication Manager and the Device Manager server
If you use a well-known certificate authority (CA), its server certificate might
already be in the truststore (jssecacerts). In this case, you do not need to
import the CA’s server certificate again.
Note: Regarding server certificates:
•
6-6
If you manage multiple Device Manager servers as information sources,
you must create server certificates for each server and import them into
the truststore (jssecacerts) for the management server running
Security management
•
A secure method must be used to transmit the server certificate for the
remote Device Manager to the management server running Replication
Manager.
For more information on the procedures for the Device Manager server and
Common Component, and information on the truststore, see the following
descriptions 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 the
truststore (jssecacerts), select HTTPS as the transmission protocol in the
Replication Manager GUI window for adding (or the window for editing) the
information source, and specify the port number for HTTPS communications.
For more information on how to add or edit the information source, see the
online Help.
Note: If you want to restrict which cipher suites are used for SSL/TLS
communication, change the value of the
server.https.enabledCipherSuites property in the server.properties
file of the Device Manager server. See the Hitachi Command Suite
Administrator Guide for more information.
Securing communications between Replication Manager and
Business Continuity Manager (IHS)
To encrypt communications between Replication Manager on the
management server and BCM on the host, you must set IHS as the reverse
proxy server and import the IHS server certificate into the truststore
(jssecacerts) of Replication Manager.
Security management
6-7
Figure 6-4 Flow of operation for setting up secure communications
between Replication Manager and BCM (IHS)
If you use a well-known certificate authority (CA), its server certificate might
already be in the truststore (jssecacerts). In this case, you do not need to
import the CA’s server certificate again.
For more information on the procedure for using BCM (IHS) as an SSL server,
see the description of setting up HTTPS connections in the Hitachi Business
Continuity Manager Installation Guide.
For more information on the procedures for Common Component and
information on the truststore, see the following descriptions in the Hitachi
Command Suite Administrator Guide:
6-8
•
Importing a server certificate into the truststore of Hitachi Command
Suite
•
Checking the server certificates imported into the truststore of Hitachi
Command Suite
Security management
After importing the server certificate for the IHS to the truststore
(jssecacerts), select HTTPS as the transmission protocol in the Replication
Manager GUI window for adding (or the window for editing) the information
source, and specify the port number for HTTPS communications. For more
information on how to add or edit the information source, see the online Help.
Note: Regarding server certificates:
•
If you manage multiple BCM (IHS) hosts as information sources, you
must create server certificates for each server and import them into the
truststore (jssecacerts) for the management server running Replication
Manager.
•
A secure method must be used to transmit the server certificate for the
IHS to the management server running Replication Manager.
Collecting audit logs
This section describes the information output in the Replication Manager audit
log for the ConfigurationAccess category. For details about the information
for other audit categories, please see the Hitachi Command Suite
Each audit event is assigned a severity level. You can filter audit log data to
be output according to the severity levels of events.
Table 6-1 Audit events for the ConfigurationAccess category
Description
of category
Resource group
creation (GUI)
Audit event
Severity
Message ID
Successful resource group creation
6
KAPM02630-I
Failed resource group creation
3
KAPM02635-E
6
KAPM02670-I
Resource group Successful resource group creation
creation (GUI or
CLI)
Failed resource group creation
KAPM07257-I
3
KAPM02675-E
KAPM07258-E
Resource group
deletion (GUI)
Successful resource group deletion
6
KAPM02631-I
Failed resource group deletion
3
KAPM02636-E
Resource group
deletion (GUI or
CLI)
Successful resource group deletion
6
KAPM02671-I
KAPM07259-I
Failed resource group deletion
3
KAPM02676-E
KAPM07260-E
Editing of
Successful resource group property editing
resource group
properties (GUI) Failed resource group property editing
6
KAPM02634-I
3
KAPM02639-E
Editing of
resource group
6
KAPM02674-I
Successful resource group property editing
KAPM07261-I
Security management
6-9
Description
of category
Audit event
Severity
Message ID
properties (GUI
or CLI)
Failed resource group property editing
Addition of a
user to a
resource group
(GUI)
Successful user addition to a resource group
6
KAPM02632-I
Failed user addition to a resource group
3
KAPM02637-E
Removing of a
user from a
resource group
(GUI)
Successful user removal from a resource group
6
KAPM02633-I
Failed user removal from a resource group
3
KAPM02638-E
3
KAPM02679-E
KAPM07262-E
Assignment of a
user to a
resource 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 pair
operation
The pair operation task (pair create, delete, modify, or
edit group name) has started.
6
KAVN10001-I
KAVN10006-I
KAVN10010-I
KAVN10089-I
The pair operation task (node addition or deletion) has
started.
6
The pair operation task (node addition or deletion) was
successful.
6
The pair operation task (pair create, delete, modify, or
edit group name) was successful.
6
KAVN10085-I
KAVN10087-I
KAVN10086-I
KAVN10088-I
KAVN10002-I
KAVN10007-I
KAVN10011-I
KAVN10090-I
The pair operation task (pair create, delete, or modify)
4
timed out. (The command was executed successfully, but
whether the pair status was changed correctly could not
be confirmed.)
KAVN10003-W
The pair operation task has failed.
3
KAVN10009-E
Failed to update the configuration definition file after
deleting the pair.
4
KAVN10004-W
Editing or distribution of the disk configuration definition
file has started.
6
The disk configuration definition file was successfully
edited or distributed.
6
An attempt to edit or distribute the disk configuration
definition file has failed.
3
KAVN10008-W
KAVN10030-W
KAVN10005-W
KAVN10015-I
KAVN10021-I
KAVN10016-I
KAVN10022-I
KAVN10014-E
KAVN10017-E
KAVN10020-E
KAVN10023-E
6-10
Security management
Description
of category
Management
host change
operation
Secondary
volume hiding
operation
Audit event
Severity
Message ID
Editing or distribution of the copy group configuration
definition file has started.
6
KAVN10024-I
The copy group configuration definition file was
successfully edited or distributed.
6
An attempt to edit or distribute the copy group
configuration definition file has failed.
3
KAVN10009-E
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
Secondary volume hiding operation started.
6
KAVN10073-I
KAVN10028-I
KAVN10025-I
KAVN10029-I
KAVN10079-I
Secondary volume hiding operation completed.
6
KAVN10074-I
KAVN10080-I
Secondary volume hiding operation failed.
3
KAVN10075-E
KAVN10081-E
Canceling of a secondary volume hiding operation
started.
6
Canceling of a secondary volume hiding operation
completed.
6
Canceling of a secondary volume hiding operation failed.
3
KAVN10076-I
KAVN10082-I
KAVN10077-I
KAVN10083-I
KAVN10078-E
KAVN10084-E
Replica
operation
Creation, editing, execution, canceling, or deletion of a
task has started.
6
KAVN10031-I
KAVN10034-I
KAVN10037-I
KAVN10040-I
KAVN10043-I
task has succeeded.
6
KAVN10032-I
KAVN10035-I
KAVN10038-I
KAVN10041-I
KAVN10044-I
task has failed.
3
KAVN10033-E
KAVN10036-E
KAVN10039-E
KAVN10042-E
KAVN10045-E
Mounting or unmounting has started.
6
KAVN10046-I
KAVN10049-I
Security management
6-11
Description
of category
Audit event
Mounting or unmounting has succeeded.
Severity
6
Message ID
KAVN10047-I
KAVN10050-I
Mounting or unmounting has failed.
3
KAVN10048-E
KAVN10051-E
Take over operation has started
6
KAVN10052-I
KAVN10064-I
Take over operation is terminated
6
KAVN10053-I
KAVN10065-I
Take over operation timed out. (The command execution
was successful, but completion could not be confirmed.)
4
Take back operation has started.
6
KAVN10054-W
KAVN10066-W
KAVN10058-I
KAVN10061-I
Take back operation is terminated.
6
KAVN10059-I
KAVN10062-I
6-12
Take back operation timed out. (The command execution 4
was successful, but completion could not be confirmed.)
KAVN10060-W
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
Security management
KAVN10063-W
7
Troubleshooting
This chapter describes how to handle the errors that might occur during
operation of Replication Manager.
If you need technical support, see Getting help on page xiv.
□ 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-1
Overview
This chapter describes what to do if a problem occurs:
•
If issues arise with Application Agent (including installation and removal),
see Troubleshooting Application Agent operations on page 7-5.
•
When installing Replication Manager in an environment where Device
Manager and CCI manage copy pairs, if you cannot acquire the current
copy pair information after refreshing the configuration information, see
Troubleshooting when copy pairs are not recognized on page 7-14 to
solve the problem.
•
If the problem is not related to installation or removal, take action
according to General problem resolution on page 7-2.
General problem resolution
This section describes how to deal with a problem that is not explicitly
described in this chapter. Follow the general procedure in the flowchart seen
below.
Figure 7-1 Sequence of actions to take if a problem occurs
7-2
Troubleshooting
1.
Check the displayed messages for information about the problem and
correct 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 and
correct the error. For details on how to view the event log data, see the
Hitachi Replication Manager User Guide.
3.
If you cannot correct the error, execute the hcmds64getlogs command to
obtain the maintenance information and contact the Support Center.
Send all the information to the Support Center . For details on how to execute
specific maintenance commands, see Collecting maintenance information on
page 7-3.
If the error occurred on a host or pair management server, also obtain
maintenance information from Device Manager Agent. For details, see the
Hitachi Command Suite Installation and Configuration Guide.
Collecting maintenance information
The hcmds64getlogs command allows you to collect maintenance information
about Replication Manager and other Hitachi Command Suite products
installed on the same host. All the necessary information is collected by a
batch 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 command
This 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 the
same time. Also, do not execute this command and the hcmdsdbmove or
hcmds64dbclustersetup command at the same time.
•
If no message is displayed indicating that the hcmds64getlogs command
succeeded or failed (KAPM05318-I or KAPM05319-E), it means the
Troubleshooting
7-3
command was interrupted due to insufficient disk space in the specified
directory (dir option). Allocate sufficient space in the output destination
and re-execute the command.
In Windows:
Common-Component-installation-folder\bin\hcmds64getlogs /dir
directory-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 the
collected maintenance information is to be stored. You need to
create a new directory or specify an existing empty directory.
The maximum length allowed for a directory name is 41 bytes if
no value is specified for the type option, and 35 bytes if
Replication Manager is specified as the type. For details about the
maximum directory name length for products other than
Replication Manager, see the manual for the applicable product.
7-4
types HitachiCommand-Suiteproduct-name
Specifies the name of the product from which maintenance
information will be collected. If this option is omitted, information
is collected from all Hitachi Command Suite products installed on
the management server (which may consume a great deal of disk
space). Use the batch collection command for maintenance
information twice to collect the maintenance information from
Replication Manager and Device Manager separately, or omit the
type option to collect the maintenance information from every
Hitachi Command Suite product. For details about Device
Manager maintenance information, see the Hitachi Command
Suite Administrator Guide.
arc archive-filename
Specifies the name of the archive file to be created. The archive
file is output to the directory specified for the dir option. Do not
specify a path for the archive file name. If you do, the command
might terminate abnormally. If this option is omitted, the archive
file 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 logfiletypes
Specifies the types of the log files to be collected if only specific
types of log files can be collected for some reason (such as a
failure):
Troubleshooting
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 are
collected.
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\Base\bin\hcmds64getlogs" /dir C:
\logfile /types ReplicationManager
In Linux:
/opt/HiCommand/Base64/bin/hcmds64getlogs -dir /logfile -types
ReplicationManager
To collect all the maintenance information for Hitachi Command Suite
products and output it to the Hitachi_log output archive file:
In Windows:
"C:\Program Files\HiCommand\Base\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 operations
This section explains how to troubleshoot problems with Application Agent,
including how to collect information when calling for support:
•
Resolving Application Agent installation and 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
Troubleshooting
7-5
•
Application Agent events that can be ignored on page 7-10
Tip: When collecting event log information to diagnose a problem on the host
where Application Agent is installed, be sure to collect maintenance
information for the Replication Manager server as well. This will help identify
problems caused by communication errors between Application Agent and the
server. For more information, see Collecting maintenance information on
page 7-3.
Resolving Application Agent installation and removal errors
Sometimes, an Application Agent installation or removal might not end
properly, such as when an error occurs during the installation, or the
installation is canceled while files are being copied. In such cases, resolve the
problem by following the same sequence used for installation of Replication
Manager.
Note: After the RM Shadow Copy (VSS Provider) window has been started, if
the installation fails or the Cancel button is used to stop the installation, you
have 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 the
Application Agent installer.
To resolve Application Agent installation or removal errors:
1.
Check the displayed messages for information about the problem, and
then try to resolve it.
2.
Check the trace log files that were output during the installation or
removal, and then try to resolve the problem.
For details, see Application Agent and VSS Provider installer trace log files
on page 7-6.
3.
If you cannot resolve the problem, collect the trace log files and contact
the 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 that
can be ignored on page 7-10, to determine whether the displayed message
can 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 can
use these files to analyze the causes of errors that occurred during
installation or removal.
Application Agent
rpm_app_agt_inst.log
7-6
Troubleshooting
VSS Provider
vssprv_inst.log
Output folder
The output folder of the Application Agent and VSS Provider trace log files
differ depending on whether the installation-folder-for-ApplicationAgent\DRM\log folder exists. If this folder does not exist, the log files are
placed on the desktop.
Output format
The formats of data output to the trace log files are as follows:
Format 1
yyyy/mm/dd hh:mm:ss
Format 2
The format of Windows Installer logs
Windows Installer log data is output from the Application Agent installer. An
example of output log data is as follows:
2009/10/02 05:56:22 Windows Installer logging started.=== Logging
started: 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 Installer
logging ended.
Application Agent log entries related to VSS Provider
In the Application Agent installer log file, check whether the following data
has been output to the log. If the data has been output, an error occurred
during a VSS Provider installation or removal. If that is the case, check the
VSS Provider installer log file to view the details of the error.
The following are examples of data output to the log when an error occurred
during a VSS Provider operation.
Installation log entry
2009/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 now
stop.
Removal log entry
2009/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:53
Problem: An installation error occurred. The installation will
now stop.
Troubleshooting
7-7
Resolving Application Agent operation errors
Application Agent is set up to support application linkage on hosts (database
and backup servers). If an error occurs during user operation, an error
message provides information indicating the host where the error occurred,
regardless of whether that host is a database or backup server. For this
reason, you must collect information about the host occurred. When multiple
agents are installed (such as Device Manager Agent), it is necessary to collect
information 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 are
installed, run both the hcmds64getlogs command on the management
server and hrmap_getras command on the host where Application Agent
is installed.
•
On hosts where only Application Agent is installed, you need only run the
hrmap_getras command.
For more information, see Collecting support information with the
hrpmap_getras command on page 7-8 and Collecting maintenance
information on page 7-3.
Collecting support information with the hrpmap_getras command
The hrmap_getras command collects the Application Agent configuration and
log files necessary for problem analysis. The command is located on hosts
where Application Agent is installed and is invoked as follows:
C:\Common-Agent-installation-folder\bin\hrmap_getras datacollection-folder
If you do not specify a data-collection-folder, the files are placed in the
working 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 Application
Agent logs
agent.properties
Configuration file for Application
Agent
trace.log[1-n]
Trace log of Application Agent
Common-Agent-installationfolder\mod\hrpmap\log\
SET_EXPORT_CATALOG_PATH.bat
Batch file for setting export
catalog path
Common-Agent-installationfolder\mod\hrpmap\bin\
7-8
Common-Agent-installationfolder\mod\hrpmap\config\
Troubleshooting
Table 7-3 List of files collected in the hbsainfo folder
Files
Description
logger.properties
Application Agent log
configuration file
server.properties
Application Agent
configuration file
access.log
Application Agent log files
Common-Agent-installation-folder\agent
\logs
Deployment descriptor file
of Application Agent
Common-Agent-installation-folder\mod
\hrpmap
error.log
Common-Agent-installation-folder\agent
\config
service.log
trace.log
alet.xml
Table 7-4 List of files collected in the drminfo folder
Files
Description
.version*
Application Agent version
information file
Common-Agent-installationfolder\
all
Files for each type of Application
Agent environment setting
Common-Agent-installationfolder\conf
drm_output.log
Application Agent logfiles
Common-Agent-installationfolder\log
drm_output.log.old
rm_pp_trace[1-16].log
Application Agent trace log files
drm_inst.log
Application Agent installation
trace log files
all
Dictionary map files
Common-Agent-installationfolder\db
all
Schedule-related log files
For physical server:
Common-Agent-installationfolder\schedule
For virtual server:
cluster path specified in sch.conf
Table 7-5 List of files collected in the ExportCatalog folder
Files
all
Description
Catalog information files
Path set for
%EXPORT_CATALOG_PATH%
Troubleshooting
7-9
Application Agent events that can be ignored
Sometimes events (error messages) are logged to the Windows event log
that have no effect on Application Agent operation. The following table lists
these events.
Server on
which
event
occurred
When message
is output to
event log
Type
Source
Event
ID
Message
Log type
File Server,
Database
Server, and
Backup
Server
The volume is
mounted or
unmounted.
Error
VDS Basic 1
Provider
Unexpected Failure.
Error code:
2@01010013
System log
Backup
server
A VSS backup is
executed.
Error
VDS Basic 1
Provider
Unexpected Failure.
Error code:
1@01010013
System log
Backup
server
A VSS backup is
executed.
Error
Virtual
Disk
Service
1
Unexpected Failure.
Error code:
1@02000018
System log
Backup
server
A VSS backup is
executed.
Error
Virtual
Disk
Service
1
Unexpected Failure.
Error code:
48F@02000018
System log
Backup
server
A VSS backup is
executed.
Error
VDS
Dynamic
Provider
10
The provider failed
while storing
notifications from the
driver. The Virtual Disk
Service should be
restarted.
hr=80042505
System log
Backup
server
A VSS backup is
executed.
Error
PlugPlayM 12
anager
The device "xxxxxxxx"
disappeared from the
system without first
being prepared for
removal.
System log
Backup
server
A VSS backup is
executed.
Error
Disk
15
The device, xxxxxxxx,
is not ready for access
yet.
System log
Backup
server
A VSS backup is
executed.
Warning
ntfs
50
{Delayed Write Failed} System log
Windows was unable to
save all the data for the
file. The data has been
lost.
Backup
server
A VSS backup is
executed.
Warning
disk
51
An error was detected
on device device path
during a paging
operation.
System log
Database
server and
backup
server
•
A VSS backup Warning
is executed.
ftdisk
57
System log
•
A volume is
placed offline
The system failed to
flush data to the
transaction log.
Corruption may occur.
7-10
Troubleshooting
Server on
which
event
occurred
When message
is output to
event log
Type
Source
Event
ID
Message
Log type
after a VSS
backup has
been
completed.
•
The volume is
unmounted
during a VSS
restoration.
Database
server
A VSS restoration
is performed.
Warning
Microsoft
Exchange
Search
Indexer
107
Exchange Search
Application
Indexer has temporarily log
disabled indexing of the
Mailbox Database
xxxxxxxx due to an
error xxxxxxxx.
Backup
server
Simultaneous
backups are
executed in a
cascade
configuration.
Warning
PlugPlayM 257
anager
Timed out sending
notification of target
device change to
window of LDM Service
System log
Backup
server
Simultaneous
backups are
executed in a
cascade
configuration.
Warning
PlugPlayM 257
anager
Timed out sending
notification of target
device change to
window of "VDS
Notification Thread
Hidden Window
{xxxxxxxx-xxxx-xxxxxxxx-xxxxxxxxxxxx}"
System log
Passive
node in a
CCR env.
and the
SCR env.
target
A VSS backup is
executed.
Error
ESE
522
Microsoft.Exchange.Clu Application
ster.ReplayService
log
(xxxx) Log Verifier exx
xxx: An attempt to
open the device name
"xxx" containing "xxx"
failed with system error
5 (0x00000005):
"Access is denied. ".
The operation will fail
with error -1032
(0xfffffbf8).
SCR env.
target
A VSS backup is
executed.
Error
Microsoft
Exchange
Repl
2104
Log file action LogCopy
failed for storage group
"xxx". Reason:
CreateFile("xxx") = 2
Backup
server
Simultaneous
backups are
executed in a
cascade
configuration.
Error
Service
Control
Manager
7034
The Logical Disk
System log
Manager Administrative
Service service
terminated
unexpectedly. It has
done this xx time(s).
Troubleshooting
Application
log
7-11
Server on
which
event
occurred
When message
is output to
event log
Type
Source
Event
ID
Message
Log type
Backup
server
A VSS backup is
executed.
Error
Service
Control
Manager
7034
The Virtual Disk Service System log
service terminated
unexpectedly. It has
done this xx time(s).
Backup
server
The OS is
Windows Server
2008 or 2012 and
during a VSS
import, COPY/
COPY or PAIR/
PAIR volumes
other than the
volumes to be
processed exist.
Error
VSS
8193
Volume Shadow Copy
Service error:
Unexpected error
calling routine xxxx
Application
log
Backup
server
The OS is
Windows Server
2008 and 2012
and during a VSS
import, COPY/
COPY or PAIR/
PAIR volumes
other than the
volumes to be
processed exist.
Error
VSS
12289
Volume Shadow Copy
Service error: xxxx.
Application
log
Backup
server
A VSS backup is
executed.
Error
VSS
12290
Volume Shadow Copy
Service warning:
GetVolumeInformation
W( \\?
\Volume{ xxxxxxxxxxxx-xxxx-xxxxxxxxxxxxxxxx }\,NULL,
0,NULL,NULL,
[0x00000000], , 260)
== 0x00000001. hr =
0x00000000.
Application
log
Backup
server
A VSS backup is
executed.
Error
VSS
12290
Volume Shadow Copy
Service warning:
GetVolumeInformation
W( \\?
\Volume{ xxxxxxxxxxxx-xxxx-xxxxxxxxxxxxxxxx }\,NULL,
0,NULL,NULL,
[0x00000000], , 260)
== 0x00000057. hr =
0x00000000.
Application
log
Database
server and
backup
server
A VSS backup is
executed.
Warning
VSS
12333
Volume Shadow Copy
Warning: The provider
has reported a storage
Application
log
7-12
Troubleshooting
Server on
which
event
occurred
When message
is output to
event log
Type
Source
Event
ID
Message
Log type
identifier that is not
supported by VSS
Backup
server
Backup
server
Backup
server
•
A VSS backup Error
is executed
•
Dynamic
recognition of
secondary
volumes is
enabled, and
a secondary
volume is
unmounted
•
Dynamic
recognition of
secondary
volumes is
enabled, and
a secondary
volume is
concealed
•
A VSS backup Error
is executed
•
Dynamic
recognition of
secondary
volumes is
enabled, and
a secondary
volume is
unmounted
•
Dynamic
recognition of
secondary
volumes is
enabled, and
a secondary
volume is
concealed
•
A VSS backup Error
is executed
•
Dynamic
recognition of
secondary
volumes is
enabled, and
a secondary
volume is
unmounted
•
Dynamic
recognition of
DLM
Manager
32787
KAPL08019-E The path Application
(xxxxxxxxx) detected
log
an error (0x00000000).
(0x00000001)
DLM
Manager
32790
KAPL08022-E A path
error occurred.
ErrorCode = xxxxxxxx
PathID = xx PathName
= xx DNum = xx
HDevName = xx
Application
log
DLM
Manager
32794
KAPL08026-E An error
occurred on all the
paths of the LU. PathID
= xx
Application
log
Troubleshooting
7-13
Server on
which
event
occurred
When message
is output to
event log
Type
Source
Event
ID
Message
Log type
secondary
volumes is
enabled, and
a secondary
volume is
concealed
Troubleshooting when copy pairs are not recognized
In an environment where Device Manager and CCI manage copy pairs, if
information about the existing copy pairs cannot be recognized after
refreshing the configuration information, take the following actions to correct
the problem:
1.
Go to Items to be checked on the pair management server on page
7-14, to make sure that the configuration definition files for Device
Manager Agent and CCI are correct.
2.
Go to Items to be checked from Device Manager GUI on page 7-16, to
make sure that information about hosts or pair management servers that
are managed by Device Manager server is correct.
3.
Go to Items to be checked from Replication Manager GUI on page 7-17,
to make sure that information about hosts that are managed by the
Replication Manager server is correct.
Items to be checked on the pair management server
This section describes how to make sure that the settings in the configuration
definition files for Device Manager Agent and CCI are correct:
1.
Installation of Device Manager Agent on page 7-15
2.
Link between Device Manager server and Device Manager Agent on page
7-15
3.
Properties of Device Manager Agent on page 7-16
4.
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 configuration
definition files that are supported by Device Manager, see the Hitachi
Note: When using Device Manager Agent on VMware 4.x, it is necessary to
confirm the prerequisite combination of Device manager server and Device
Manager Agent. Even if you use Device Manager and the Device Manager
Agent for which the prior prerequisite combination has been confirmed, the
following precaution must be noted:
7-14
Troubleshooting
•
If the target volume is set as a command device on the virtual machine,
by using Add CMD Devices, the virtualization server needs to be restarted
in order to recognize the set command device.
Installation of Device Manager Agent
Make sure Device Manager Agent is installed on both pair management
servers that manage a primary and secondary volume.
Link between Device Manager server and Device Manager Agent
Make sure Device Manager Agent links correctly with Device Manager server
using the hdvmagt_account command. If the link is incorrect, execute this
command on the pair management server to change the settings.
1.
Log in to the pair management server as a user with Administrator or
super user permissions. If the OS you are using is Windows Server 2008
x86, Windows Server 2008 x64, Windows Server 2008 R2, or Windows
Server 2012, start the command prompt as Administrator.
2.
Execute the hdvmagt_account command and make sure the Device
Manager agent is correctly linked to the Device Manager server.
For Windows:
Device-Manager-agent-installation-folder>\bin
\hdvmagt_account.bat
For Solaris, Linux or HP-UX:
/opt/HDVM/HBaseAgent/bin/hdvmagt_account
For AIX:
/usr/HDVM/HBaseAgent/bin/hdvmagt_account
3.
If the agent is not correctly linked to the server, enter the following
information in response to the command request:
IP address or host name
Specify the IP address or host name of the Device Manager server.
¢
Specifying an IP address:
In IPv4, specify the address in dotted-quad form.
In IPv6, specify the address by using hexadecimal numbers delimited
by colons. Abbreviated forms can also be used.
Specifying a host name: Specify the host name by using a string of up
to 50 bytes. The following characters can be used: a-z A-Z 0-9 - . @ _
Port number
Specify the port number of the Device Manager server to which the
Device Manager agent is connected. A number from 0 to 65535 can be
specified as the port number.
User ID and password
Specify the user ID and password for the Device Manager agent that is
registered on the Device Manager server. The user ID of the built-in
account for the Device Manager agent is HaUser, and the default
password is haset. If you want to change the account used for the Device
Manager agent, you must first register the new user ID in the PeerGroup.
¢
Troubleshooting
7-15
For details about how to configure a user group, see the Hitachi
Command Suite Installation and Configuration Guide.
4.
If the OS you are using is windows-based, restart the Device Manager
Agent.
Properties of Device Manager Agent
Make sure Device Manager Agent properties (stored in the pair management
server) are correct. For details about the properties to be specified, see
Setting up the prerequisite environment on page 3-3. If you change the
properties, restart Device Manager Agent.
Settings in the CCI configuration definition file
Make sure that the specified settings in the CCI configuration definition files
are correct, and the HORCM instances that correspond to these files can start
without any problems. Also, make sure that parameter formats and specified
settings in the configuration definition files are supported by Device Manager.
Items to be checked from Device Manager GUI
This section describes how to check information about hosts (pair
management servers) that are managed by Device Manager using the Device
Manager GUI:
1.
Recognition of Device Manager Agent on page 7-16
2.
Recognition of the command device on page 7-16
3.
Recognition of the replication configuration on page 7-17
4.
Recognition of storage systems on page 7-17
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 correctly
recognizes Device Manager Agent on a host or pair management server that
manages existing copy pairs:
•
Hosts or pair management servers that manage copy pairs are displayed
in the host list.
•
A button to refresh host information is displayed in the host properties
window.
If the above items are not displayed, Device Manager Agent and the
connection-target Device Manager server are not linked correctly. See Link
between Device Manager server and Device Manager Agent on page 7-15 to
correct the problem.
Recognition of the command device
Check the following to make sure Device Manager server correctly recognizes
the command device that is allocated to the host or pair management server:
7-16
Troubleshooting
•
In the host properties window, make sure that the last updated date and
time 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 disk
information on the pair management server to make sure that LUs that
correspond to the command device are correctly recognized by the OS.
Recognition of the replication configuration
Make sure that Device Manager server correctly recognizes the replication
configuration that is managed by a host or pair management server.
Note: On copy pairs that configure remote copies, you do not need to check
this item.
Check the following:
•
On the host (pair management server) properties window, make sure that
you can click the button to view the pair information managed by the
host.
•
On the window displayed by clicking the button to view the pair
information, make sure that existing copy group names and copy pair
names are displayed.
If the button is not activated or the information is not displayed, refresh the
storage system information. If it cannot be updated, make sure that the
system configuration and specified settings in the CCI configuration definition
file are correct.
Recognition of storage systems
To ensure that Device Manager server correctly recognizes storage systems
that comprise existing copy pairs, confirm that each storage system appears
in the list of storage systems. If not, register the storage system with the
Device Manager server.
Items to be checked from Replication Manager GUI
In the Pair Configuration view, select the pair management server that
manages the existing copy pairs to make sure that information about these
items are correct:
•
The configuration definition file for CCI that exists on the pair
management 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 configuration
information for Device Manager server. For details, see the Hitachi Replication
Manager User Guide.
Troubleshooting
7-17
If a validation code is displayed in the instruction of list of configuration
definition files in the Pair Configuration view, see the topic that explains
about validation codes in the online help to check the cause and the action to
be taken.
Creation of TrueCopy Extended Distance or COW Snapshot
copy pairs fails (HUS100 Series)
This topic discusses conditions under which pair creation on the HUS Series
will fail with the error message RPM-03327. Follow the instructions in the
applicable sub-section to resolve the problem.
Pool utilization
Creating a copy pair may fail when the replication data release threshold
value of a DP pool used for Copy-on-Write Snapshot or TrueCopy Extended
Distance meet the following condition:
Pool utilization >= replication data release threshold - 5%
Configure the DP pool not to exceed the above threshold, and then create the
copy pair.
Difference data and management area
Creating a Copy-on-Write Snapshot or TrueCopy Extended Distance copy pair
may fail if both these conditions are true:
•
The volume for which the copy pair is to be created is already being used
as a volume for a Copy-on-Write Snapshot or TrueCopy Extended
Distance copy pair.
•
The difference data and management area used for the existing copy pair
are associated with different DP pools.
To create a copy pair under these circumstances, use the storage system
operation management software (such as Hitachi Storage Navigator Modular
2).
Specifying a DP pool
Creating a Copy-on-Write Snapshot or TrueCopy Extended Distance copy pair
may fail if both these conditions are true:
•
The volume for which the copy pair is to be created is already being used
as a volume for a Copy-on-Write Snapshot or TrueCopy Extended
Distance copy pair.
•
A DP pool is specified other than the one associated with the existing copy
pair.
You must specify the same DP pool used for the existing copy pair.
7-18
Troubleshooting
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 a
TrueCopy Extended Distance secondary volume and a Copy-on-Write
Snapshot primary volume are simultaneously created for a cascade
configuration, 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 operations
This section covers error conditions and log events that may occur and how
to address them:
•
Replica creation fails silently on page 7-19
•
Backup server is not recognized as a pair management server on page
7-19
•
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-20
•
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 page
7-21
Replica creation fails silently
If replica creation fails when there is not enough disk space to create
transaction log files, there may be no error messages displayed. To delete
transaction logs periodically, select Truncate Exchange transaction log
files in the Execution Options of the Create Replica Wizard (2. Setup Options)
page. When this option is selected, transaction log files will be automatically
deleted every time a backup is performed.
Backup server is not recognized as a pair management server
If Replication Manager does not recognize the backup server as a pair
management server, make sure that the CCI instance on the backup server is
running before performing the following operations:
•
Executing Setup Agent or Refresh Hosts
•
Executing Mount Replica or Unmount Replica.
Troubleshooting
7-19
Tip: Even if Replication Manager appears to recognize the backup server as a
pair management server, you should still confirm that the CCI instance on the
backup 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 message
RPM-11510
When restoring a replica with the roll-forward option, if the storage group to
recover has more than 1,008 transaction log files, the restore and rollforward will complete, but the information store will not be mounted and the
message RPM-11510 is output. Follow this procedure to complete the mount
operation:
1.
Start the event viewer for the operating system on the database server.
2.
Confirm that the error log with the event source MSExchangeIS and the
Event ID 9518 are recorded. Open the properties for the error log, and
confirm that the description field reads Error 0xfffffd9a has
occurred. 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 log
with event source ESE, event ID is 302, and the description field reads
Database engine normally completed the recovery steps. Also
check that this log is followed immediately by an information log with
event source ESE, event ID 101, and the description Database engine is
stopped.
Note: If you do not find either of the error logs described in steps 2 and
3, do not continue this procedure.
4.
Start Exchange System Manager and view the properties of the storage
group to be recovered. Check the location of the transaction logs as well
as the initial characters of the log file. The initial characters are E0n,
where n is from 0 to 3.
5.
Of the transaction log files in the storage group to be recovered, move
those not matching the description in step 4 to a new folder.
6.
From the Exchange System Manager, mount the information store to be
recovered.
7.
Check that the information store is mounted, and then delete the
transaction log files moved in step 5.
Creating a replica fails with error message RPM-10006
If different logical volumes are mounted at mount points in a hierarchical
relationship, such as M:\ and M:\MNT, any mount points that hold a lowerlevel directory mount point (in this case, M:\) cannot be specified for backup.
7-20
Troubleshooting
If specified, the backup will fail, and an error message (RPM-10006 and
RPM-20062) will be output.
If this happens, only the lowest-level mount point can be specified for
backup, so if you want to specify multiple mount points for backup (including
directory mount points), create a configuration in which there is no
hierarchical relationship between the mount points.
Creating a replica fails with event IDs 17, 1 and 10010
If a backup operation fails, the status of the Windows Logical Disk Manager
Administrative service will remain stopped, and Windows log entries with
event IDs 17, 1, and 10010 will be output. The backup attempt fails because
the Logical Disk Manager Administrative service hangs up. If this happens,
restart the backup server. After the restart, check the effect of the operation
on the backup server.
Disk status remains online after replica operation is complete
In Windows Server 2008, Windows Server 2008 R2, and Windows Server
2012 environments, the disk status of secondary volumes on the backup
server change to Offline after a backup operation is performed. However,
note that if the operation fails, the status of the secondary volumes on the
backup server might remain Online. If this happens, perform the following
procedure to change the disk status of secondary volumes on the backup
server to Offline:
1.
Use the CCI command inqraid $Phys -CLI to check the disk numbers of
all secondary volumes that are the backup destinations.
The disk numbers are shown in the DEVICE_FILE column.
2.
Start the diskpart command.
3.
To display the current disk statuses, enter list disk.
A list of disks that are currently connected to the server will be displayed.
The disk numbers are shown in the Disk ### column. Make sure that in
the Status column, statuses of disks whose disk numbers correspond to
the disk numbers on the secondary volumes are Online.
4.
For each secondary volume whose disk status is Online, perform the
following procedure:
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 successfully
offlined 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 in
the Status column.
Troubleshooting
7-21
6.
7-22
Enter exit to end the diskpart command.
Troubleshooting
A
Version compatibility with other HCS
products
This appendix describes the compatibility between versions of Replication
Manager and other Hitachi Command Suite product versions.
□ Restrictions when Replication Manager and Device Manager versions differ
□ Restrictions when Replication Manager and Business Continuity Manager
versions differ
Version compatibility with other HCS products
A-1
Restrictions when Replication Manager and Device Manager
versions differ
The following restrictions for configuring the Replication Manager system are
dependent on the version of Device Manager that is installed on the
components (management server, pair management server, and hosts).
Table A-1 Restrictions when Replication Manager and Device Manager
versions differ
Release Number
Device Manager Server or Device
Manager Agent 6.0 or earlier
Restriction
The following information cannot be acquired:
•
License usage rate
•
DMLU status
•
Remote path list
The following functions are not supported:
•
License usage and alert settings
•
DMLU settings (addition and deletion)
•
Remote path settings (creation, editing, and
deletion)
•
Deletion of copy pairs related to remote paths
•
LDEV format output of configuration definition
files
Takeover and takeback operations are not
supported.
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 of
Medium the number is 80,000, and in the case
of Large the number is 130,000
Manager Agent 7.0.1 or earlier and
running on open systems
The notification of when the Device Manager and
Replication Manager configurations are not
synchronized and will not be properly executed.
Instead, the notification that you should
synchronize the configuration will always be
displayed, instead of only when necessary.
Mainframe system volume attributes may not
display correctly.
The DMLU capacity addition function for the
HUS100 series is not supported.
Manager Agent 7.4.1 or earlier
The following functions are not supported on open
systems:
•
A-2
Editing the group name using the Pair
Configuration Wizard
Release Number
Restriction
•
Specifying syncwait option using the Change
Pair Status Wizard
•
Displaying and editing the system
configuration option
•
Displaying the mirror information
•
Editing the mirror option
•
Displaying and editing the path group ID of a
copy group using the Pair Configuration
Wizard
•
Displaying the path group ID of a copy pair, or
path group ID defined in the configuration
definition file
•
Managing more than 64 generations of Thin
Image copy pairs.
•
Pair management using global-active device.
•
Automatic user authentication for command
devices. (You must perform authentication
manually using the raidcom command.)
The CTG setting for GAD copy groups is not
supported.
Restrictions when Replication Manager and Business
Continuity Manager versions differ
The following restrictions for configuring the Replication Manager system are
dependent on the versions of Business Continuity Manager and Mainframe
Agent that are installed on the host pair management server.
Table A-2 Restrictions when Replication Manager and Business Continuity
Manager versions differ
Release Number
Business Continuity Manager or
Mainframe Agent 6.1 or earlier, that
are registered as information
sources
Business Continuity Manager 6.6.1
or earlier
Restriction
•
Management and distribution of disk
configuration files using volume scans
•
Copy pair definitions
•
Changing of copy pair statuses
The creation, distribution, and editing of disk
configuration definition files are not supported.
A-3
Release Number
Business Continuity Manager
Version 6.6.1 or earlier
A-4
Restriction
Primary and secondary volume capacity checking
(to determine if volume capacities match) when
defining copy pairs is not supported.
B
Supported functions and unsupported
configurations
This appendix provides information on functions and supported by Replication
Manager.
□ 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-1
Supported paths for acquiring information and performing
processing
The following table shows the relationship between Replication Manager
server functions and the supported paths for acquiring information and
performing processing:
Open
HDvM
Server
Mainframe
HDvM Agent
BCM
Mainframe
Agent
Core functions
Acquiring
replication
configuration
information
Open volume
Y
Y
N
N
Mainframe
volume
N
N
Y
Y
Acquiring
replication
status (pair
status)
Open volume
Y
Y
N
N
Mainframe
volume
N
N
Y
Y
N
Y
N
N
N
N
Y
Y
Acquiring
Open volume
replication
Mainframe
status
(remote copy volume
performance
information)
Replication configuration support functions
Acquiring the
program
product
license for
copy
Configuration Y
information
N
N
N
Status or
usage
Y
N
N
N
Acquiring
storage
system
configuration
information
Configuration Y
information
and remote
path status
N
N
N
Journal or
N
Pool status or
usage
Y
N
N
Y
Y*
N
Y
N
Creating and deleting copy
pairs
N
Replication operation support functionality
Changing copy pair statuses
N
Y
Legend
* - Only the pair definition function for creating a copy group definition file is
supported. The creation of copy pairs is not supported.
B-2
List of tasks supported for each storage system
The tasks supported by Replication Manager depend on the storage system
model. The following table lists the tasks supported for each storage system.
List of tasks supported for each storage system (enterprise-class
storage systems)
Support for each storage system
Upper row: open system
Lower row: mainframe system
Task
Universal
Storage
Platform
V/VM
Hitachi USP
Virtual
Storage
Platform and
VSP G1000
Replication configuration discovery (Open)
Registration/removal of Device
Manager servers for discovery
Discovery of open replication
configurations
Y
Y
Y
n/a
n/a
n/a
n/a
n/a
n/a
Y
Y
Y
n/a
n/a
Y4
Y4
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Replication configuration discovery (Mainframe)
Registration/removal of BCM (MF
Agent) servers for discovery
Discovery of mainframe replication
configurations
Mainframe volume scan (management/ n/a
distribution of disk configuration
Y4
definition file)
Replication configuration display
Applications view
User customized view
Replication status display
Acquisition of latest pair statuses
Acquisition of latest remote-copy
performance information
Replication management logical-group creation and deletion
Site-view-based "Site" definition
Separate replication management
tasks based on access control
Y
Y
Y
Y
Y
Y
Y
Y
Y
B-3
Task
Universal
Storage
Platform
V/VM
Hitachi USP
Y
Y
Virtual
Storage
Platform and
VSP G1000
Y
HRpM operating status collection and troubleshooting
Pair monitoring and management
status display
Y
Y
Y
Y
Y
Y
Pair management task display
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
Creating, editing, and
deletion
Y
Y
Y
N
N
N
Listing
Y
Y
Y
n/a
n/a
n/a
Y
Y
Y
n/a
n/a
n/a
Usage monitoring and Y
over-threshold
n/a
notification
Y
Y
n/a
n/a
Listing
Y
Y
Pair management workflow display
Managing pair count display
Copy program product license monitoring
Registered license display
License utilization display
License utilization monitoring and
over-threshold notification
Storage system settings
Command
devices
Listing
Volume pools
deletion
Remote path
B-4
Y
Task
Universal
Storage
Platform
V/VM
Hitachi USP
V-VOLs
N
N
N
deletion
Y
Y
Y
N
N
N
Related pair deletion
Y
Y
Y
N
N
N
N
Y
Y
n/a
n/a
n/a
deletion
N
Y
Y
n/a
n/a
n/a
Listing
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
Usage monitoring and Y
over-threshold
N
notification
Y
Y
N
N
Listing
Journal groups
Virtual
Storage
Platform and
VSP G1000
deletion
Copy pair creation and deletion
Label-based identification of managed
volumes
Y
Y
Y
N
N
N
Copy types and cross-site cascade pair
configuration definition
Y
Y
Y
Y2,4
Y2,4
Y2,4
Defined pair grouping
Y
Y
Y
Y2,4
Y2,4
Y2,4
Y
Y
Y
Y2,4
Y2,4
Y2,4
Y
Y
Y
Y2,4
Y2,4
Y2,4
Y
Y
Y
Y2,4
Y2,4
Y2,4
Pair creation scheduling
Workflow saving and loading
Managed volume protection
B-5
Task
Universal
Storage
Platform
V/VM
Hitachi USP
Defining copy groups by using device
groups
Virtual
Storage
Platform and
VSP G1000
?
?
N
?
?
n/a
Y
Y
Y
Y
Y
Y
Changing copy pair statuses (creating
and deleting) 1
Y
Y
Y
Y3,4
Y3,4
Y3,4
Changing copy pair statuses (resynchronizing, splitting, and
restoring)1
Y
Y
Y
Y4
Y4
Y4
Batch recovering from site failures
Y5,6
Y5,6
Y6,7
N
N
N
?
?
Y
?
?
n/a
Replication failure analysis
Logging and exporting remote copy
performance information
Replication recovery
Changing statuses of copy pairs in
copy groups defined by device groups
Legend:
Y : Supported
N : Not supported
n/a: Not applicable
Notes:
B-6
1.
If a HORCM instance is specified not to be managed for the pairs in the
properties file (server.properties) provided by Device Manager agent,
operations for the copy pairs in the instance will not be allowed.
2.
Only the function for defining copy pairs is supported (creating copy
group definition files). The creation of copy pairs is not supported.
3.
Only the function for deleting copy pairs is supported. The creation of
copy pairs is not supported.
4.
This function can be used only when BCM is used. It cannot be used with
Mainframe Agent.
5.
Universal Replicator, TrueCopy Asynchronous, and TrueCopy Synchronous
are supported. No other remote copy or local copy functions are
supported.
6.
Device Manager agent 8.0 or later must be installed on the host.
7.
Universal Replicator and TrueCopy Synchronous are supported. No other
remote copy or local copy functions are supported.
List of tasks supported for each storage system (midrange storage
systems)
Task
Hitachi
Hitachi
AMS2000 /
AMS/WM
HUS VM
HUS100
S
Series
Hitachi
SMS
Discovery of replication configuration (open)
Addition and deletion of HDvM servers for discovery
Y
Y
Y
Y
n/a
n/a
n/a
n/a
Y
Y
Y
Y
Discovery of open replication configuration
Discovery of replication configuration (mainframe)
Addition and deletion of BCM (MF-Agent) servers for
discovery
Discovery of MF replication configuration
Replication configuration display
Business perspective view
User-specific custom view
Y
Display of copy group information defined by the
device group
n/a
n/a
Y
n/a
Acquisition of latest pair status
Y
Y
Y
Y
Acquisition of latest remote copy performance
information
Y
Y
Y
Y
Y
Y
Y
Replication status display
Creation and deletion of logical groups for replication management
Site view definition of "site"
Y
Division of replication management by access control
Recognition of HRpM operation status, troubleshooting
Pair monitoring, display of management operation
status
Y
Y
Y
Y
Display of pair management tasks
Y
Y
Y
N
Workflow editing and deletion
Y
Y
Y
N
Display of managed pair count
Y
Y
Y
Y
Cancellation and deletion of pair management tasks
Display of pair creation workflow
B-7
Task
Hitachi
Hitachi
AMS2000 /
AMS/WM
HUS VM
HUS100
S
Series
Hitachi
SMS
Replication error analysis
Collection and export of performance information logs
for remote copy
Y
Y
Y
Y
Copy pair status change(create, delete) 1
Y
Y
Y4
Y
Copy pair status change(resync, divide, restore) 1
Y
Y
y4
Y
Batch recovery from site failure
Y1,2
Y1,2
Y1,2
N
Status change to copy pairs of device group-defined
copy groups
n/a
n/a
Y
n/a
Display of registered license
Y
Y
Y
N
Display of license usage
n/a
n/a
Y
n/a
Replication recovery
Copy license monitoring
License usage monitoring and over-threshold
notification
Y
Command devices
Command
devices
Listing
Y
Y
Y
N
Creation, editing, and deletion
Y
Y
Y
N
Volume pools
Listing
Y
Y3
n/a
N
Y
Y3
n/a
N
Usage monitoring and overthreshold notification
Y
Y3
n/a
N
Listing
Y
Y
Y
N
Y
Y
Y
N
Listing
N
N
n/a
N
N
N
n/a
N
Listing
Y
Y
Y
N
Y
Y
Y
N
Deletion of related pairs
Y
Y
Y
N
Label-based identification of managed volumes
Y
Y
Y
Y
Defining cascaded pair configurations across copy
types and sites
Y
Y
Y
N
DMLU
V-VOL
Remote paths
Copy pair creation and deletion
B-8
Task
Grouping of defined pairs
Hitachi
Hitachi
AMS2000 /
AMS/WM
HUS VM
HUS100
S
Series
Y
Y
Y
Hitachi
SMS
Y
Scheduling for pair creation
Saving and loading workflows
Target volume protection
Legend:
Y : Supported
N : Not supported
n/a: Not applicable
Notes:
1.
UR and TCS are supported. No other types of remote or local copies are
supported.
2.
Device Manager agent 6.4.0 or later must be installed on the host.
3.
The HUS100 series does not support volume pools.
4.
If the properties file (server.properties) provided by Device Manager
Agent specifies to exclude an HORCM instance from pair management, no
operations can be performed on copy pairs in that instance.
Unsupported configurations (open systems)
The following is a list of unsupported open systems pair configurations. The
Pair Configuration Wizard cannot be initiated to perform operations to modify
these configurations. The copy group definition file should either be edited
directly, or use storage management software other than Hitachi Command
Suite (such as Storage Navigator or Storage Navigator Modular) to define the
configuration. It is impossible to recover from these configurations using
Unsupported
configuration
Requirement for
configuration
Alternative configuration
to implement
requirement
A copy group defined in
HORCM files with a single
copy group definition that
includes virtual command
device settings.
To modify all the pairs in the Each pair modification must
copy group at once.
be executed separately.
The number of pairs in the
child group of a cascade
To create a backup of only
some volumes.
None.
B-9
Unsupported
configuration
Requirement for
configuration
to implement
requirement
configuration is greater than
the number of pairs in the
parent group.
Pairs in the copy group use
the same P-VOL.
To set up an SI multi-target
configuration.
Use different copy groups
for each S-VOL if there are
copy pairs using the same
P-VOL in the copy group.
the same S-VOL.
None
None
To perform an operation
simultaneously on pairs that
span multiple storage
systems.
Unify the P-VOLs using the
same storage system into
the same CTG*.
There are different types of
copy pairs in the same copy
group.
The storage systems for the
primary volumes in the
same copy group are
different.
secondary volumes in the
same copy group are
different.
A TCE pair with different DP
Pool IDs for differential and
management data stored
both in primary as well as
secondary site.
Unify the S-VOLs using the
the same CTG*.
The copy group definition
file has to be created
manually. (It is not possible
to restore it with Replication
Manager.)
None
A copy pair is defined by
To share a copy pair with a
both a snapshot group and a different type of group.
copy group.
None
The following virtual storage None
machine-related
configurations are
unsupported:
None
Local copy
B-10
•
A copy pair comprising
volumes from different
virtual storage
machines.
•
virtual storage machine
volumes and physical
storage system
volumes.
•
A copy group
comprising multiple
copy pairs from
different virtual storage
machines.
Unsupported
configuration
•
Requirement for
configuration
to implement
requirement
Copy pairs from a
and a physical storage
system that coexist in a
copy group.
Remote copy
•
A virtual storage
machine volume and
physical storage system
volume coexist in a
copy topology, and a
copy pair comprising
only physical storage
system volumes exists
in the topology.
•
a virtual storage
machine volume and
physical storage system
volume exist in a copy
group, and different
volumes exist in the
copy group.
The following configurations
are unsupported for GAD
pair management:
•
Virtual IDs of primary
and secondary volumes
of the pair are not
identical.
•
The attribute of the
secondary volume is
GAD Reserved, and its
status is simplex, and
the primary or
secondary volume
belongs to a different
virtual storage machine.
None
None
Legend:
*: When primary volumes and secondary volumes in the same copy group
belong to different storage systems, it is necessary to create CTGs with
volumes that have the same combination of primary and secondary storage
systems.
B-11
Unsupported configurations (mainframe systems)
The following are a list of unsupported mainframe pair configurations. The
Pair Configuration Wizard cannot be initiated to perform operations to modify
these configurations. The copy group definition file should be edited directly
because it is impossible to recover from these configurations using
Unsupported
configuration
The number of pairs at the
cascade source and cascade
destination is different.
Requirement for
configuration
some volumes.
to implement
requirement
None
The number of pairs in
multi-target configurations
is different.
the same P-VOL.
To set up an SI multi-target Use different copy groups
configuration.
for each S-VOL if there are
copy pairs using the same
P-VOL in the copy group.
the same S-VOL.
None
None
simultaneously on pairs that
systems.
Unify the P-VOLs using the
the same CTG*.
There are different types of
copy pairs in the same copy
group.
primary volumes in the
same copy group are
different.
secondary volumes in the
same copy group are
different.
Unify the S-VOLs using the
the same CTG*.
The cascade configuration
consists of a container and a simultaneously on pairs that
copy group.
systems, without
maintaining consistency.
Divide the destination copy
groups into multiple CTGs
according to the cascade
source CTGs.
The cascade destination
contains multiple copy
groups.
Create CTGs in the cascade
source according to the
cascade destination copy
groups. Pairs in the cascade
source must belong to any
CTG.
some volumes.
Legend:
*: When primary volumes and secondary volumes in the same copy group
belong to different storage systems, it is necessary to create CTGs with
B-12
volumes that have the same combination of primary and secondary storage
systems.
B-13
B-14
Acronyms and Abbreviations
The following acronyms and abbreviations appear in this guide.
A
ASCII
American Standard Code for Information Interchange
B
BCM
Business Continuity Manager
C
CHAP
Challenge Handshake Authentication Protocol
C/T
Consistency Time
CCI
Command Control Interface
CLI
Command Line Interface
CN
#
Common 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-1
CPU
Central Processing Unit
CTL
Controller
CU
Control Unit
D
DEVN
DEVice Number
DIT
Directory Information Tree
DKC
DisK Controller
DN
Distinguished Name
DNS
Domain Name System
F
FC
Fibre Channel
FC-SP
Fibre Channel Security Protocol
FQDN
Fully Qualified Domain Name
FTP
File Transfer Protocol
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Acronyms-2
T
U
V
W X
Y
Z
G
GUI
Graphical User Interface
H
HDvM
Hitachi Device Manager
HRpM
Hitachi Replication Manager
HTML
HyperText Markup Language
HTTP
HyperText Transfer Protocol
HTTPS
HyperText Transfer Protocol Security
I
IP
Internet Protocol
IPF
Itanium® Processor Family
iSCSI
Internet Small Computer System Interface
J
JDK
Java Development Kit
#
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-3
L
LAN
Local Area Network
LDAP
Lightweight Directory Access Protocol
LDEV
Logical DEVice
LU
Logical Unit
LUN
Logical Unit Number
M
MCU
Main Control Unit
MFA
Mainframe Agent
MIB
Management Information Base
N
NAS
Network Attached Storage
NAT
Network Address Translation
NIC
Network Interface Card
NTP
Network Time Protocol
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Acronyms-4
T
U
V
W X
Y
Z
O
OS
Operating System
P
PAP
Password Authentication Protocol
PPRC
Peer-to-Peer Remote Copy
R
RADIUS
Remote Authentication Dial In User Service
RCU
Remote Control Unit
RDN
Relative Distinguished Name
RFC
Request For Comments
S
SAN
Storage Area Network
SNMP
Simple Network Management Protocol
SP
Service Pack
SSL
Secure Sockets Layer
#
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-5
SSO
Single Sign-On
SVGA
Super Video Graphics Array
SVP
SerVice Processor
T
TCP
Transmission Control Protocol
TLS
Transport Layer Security
U
UAC
User Account Control
URL
Uniform Resource Locator
V
VCS
Veritas Cluster Server
W
WSFC
Windows Server Failover Clustering
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Acronyms-6
T
U
V
W X
Y
Z
Glossary
This glossary defines the special terms used in this document. Click the desired letter below
to display the glossary entries that start with that letter.
#
3DC multi-target configuration
A configuration in which, in addition to the local site, a connection is established
between a nearby remote site and a distant remote site and TrueCopy and Universal
Replicator are used to copy storage system volumes among the three sites (called data
centers). Such a configuration provides support for disaster recovery through the use of
data 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 Agent
Software that allows Replication Manager to perform replica operations on database and
backup servers where Application Agent is installed.
application replica
A database backup managed as a series of secondary volumes that can be created
manually or on a scheduled basis. Replicas can be mounted and dumped to tape using
scripts executed through Replication Manager.
#
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
Glossary-1
B
batch collection command for maintenance information
Software that collects necessary information, such as log files and properties files that
are related to a problem that cannot be resolved at the user level, for forwarding to
customer support.
BCM (Business Continuity Manager)
Software used to control a storage system from a host in a mainframe system. By using
Business Continuity Manager to issue commands from the host to the storage system,
you can acquire copy pair configuration and status information. Replication Manager
manages copy pair configurations and statuses in conjunction with Business Continuity
Manager.
C
cascade structure
A structure of consecutive copy pairs. In a cascade structure, the secondary volume of
one copy pair is the primary volume of another copy pair. This volume is called a
secondary/primary volume (SP-VOL).
CCI
Command Control Interface. Software used to control volume replication functionality
(such as TrueCopy or ShadowImage) by means of commands issued from a host to a
storage system. A command device must be set up in the storage system to enable the
storage system to receive commands from CCI.
In an open system, Replication Manager uses the CCI configuration definition files to
modify copy pair configurations and to acquire configuration information. Copy pair
modification processing, such as splitting and re-synchronizing copy pairs, is executed
on the storage system using CCI.
cluster configuration
In a Replication Manager operating environment, the term cluster configuration refers to
a configuration that consists of an executing node and a standby node, each of which
includes a duplicate management server.
cluster software
Software installed on management server nodes to boost overall availability by
duplicating management servers as a cluster system. Available software depends on the
OS that runs on the management server.
consistency group
An attribute to maintain integrity of data between copy pairs. As a general guideline,
the attribute is assigned for each copy group or snapshot group. The attribute is
mandatory for asynchronous remote copy, but is not mandatory for local copy.
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Glossary-2
T
U
V
W X
Y
Z
Consistency groups are used in TrueCopy, Universal Replicator, Thin Image, or globalactive device to maintain integrity of the update order for volumes.
copy group
A group of copy pairs. You can perform operations, such as modifying pair statuses, on
all the copy pairs in the group.
Copy-on-Write Snapshot
Software used to duplicate volumes in a single storage system. Copy-on-Write Snapshot
duplicates differential data in a data pool. The secondary volume is a virtual volume that
consists of the primary volume and the differential data. By duplicating only the
differential data, Copy-on-Write Snapshot can copy data in a very short time as well as
reduce the capacity required of the volume used for duplication. For more information,
see the Copy-on-Write Snapshot manuals.
copy pair
Denotes a primary and secondary volume pair linked by the volume replication
functionality of a storage system. Also called a pair volume. In this manual, copy pair is
sometimes referred to simply as pair.
copy pair state
A 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 status
displayed in prerequisite products (such as Device Manager, CCI, and Business
Continuity Manager) and in storage system operation management software (such as
Storage Navigator and Storage Navigator Modular).
copy pair status
A value that represents the status of a copy pair. Six status values are defined in
Replication Manager: error, suspend, copying, sync, simplex, and unknown. Each
status is indicated by an icon. The copy pair status is determined by the combination of
the copy pair states of the primary and secondary volumes. Also called pair status.
copy progress
Progress 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 displayed
when the copy pair status is copying or sync. For Inactive items, the copy progress is
displayed 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 a
CU image.) The LDEVs created in a storage system are connected to a single CU, and a
number is assigned to each CU for identifying its LDEVs. Therefore, volumes (LDEVs) in
a storage system are specified by the CU number (CU#) and LDEV number.
#
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
Glossary-3
D
DAD (Device Address Domain)
A DAD is a group of volumes that is managed by Business Continuity Manager. Volumes
are registered in a DAD during a volume scan (discovery) by Business Continuity
Manager. Depending on the type of volume scan, volumes are assigned the local DAD,
Non Gen'ed DAD, or remote DAD attribute.
DAD ID
A name that identifies a DAD.
delta resync
A status in which synchronization processing is performed by copying differential data to
a Universal Replicator copy pair in which part of the copy pair exists on the local site
and part exists on a remote site in a 3DC Multi-Target configuration.
Device Manager
Software that enables integrated management of resources and the hardware
configuration of storage systems. Device Manager can be used to operate and manage a
system 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 a
mainframe system. A DEVN is expressed as a 4-digit hexadecimal number.
G
GAD
Global-active device. A high-availability solution for Hitachi VSP G1000 storage systems.
A GAD configuration comprises mirrored volumes that accept read/write I/O on both the
main and reserve sides. For complete information on configuration requirements and
management procedures for global-active device configurations, see the Hitachi Virtual
Storage Platform G1000 Global-Active Device User Guide and the Hitachi Command
Suite User Guide.
Gen’ed Volume
A volume recognized by a mainframe host.
H
Hitachi Command Suite Common Component
A component that bundles common functions used by Hitachi Command Suite products.
Installed as part of Replication Manager, this component provides functions such as
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Glossary-4
T
U
V
W X
Y
Z
single logon, integrated output of logs, commands for starting and stopping services, a
common GUI interface, and more.
host storage domain
A group defined in Device Manager that is used to strengthen security of volumes in
storage systems. By associating and grouping hosts and volumes by storage system
port, 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 security
function as host storage domains. Host storage domains for storage systems that do not
have host groups are defined in the same manner as if they had been set with the LUN
security function.
I
information source
Replication Manager manages information about the copy pairs managed by instances
of Device Manager server, instances of Business Continuity Manager, instances of
Mainframe Agent, or Application Agent installed at a number of different sites. Once
these are registered in Replication Manager as such, these programs provide
information 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 both
mainframe and open systems.
LU (Logical Unit)
A volume created in a storage system - known as an LU (logical unit) in an open
system. Volumes created in a midrange storage system, however, are called an LDEV in
LUN (Logical Unit Number)
A management number assigned to an LU in a storage system. A LUN is a number
assigned to identify an LU for the port in the storage system to which the LU is
connected, either by the port or by the host group assigned to the port. An open system
host uses a LUN to access a particular LU.
#
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
Glossary-5
M
Mainframe Agent
Software used to acquire information about mainframe system hosts and storage
systems. In conjunction with Mainframe Agent, Replication Manager monitors
configuration 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 for
Replication Manager defines the information set for alerts, such as monitored targets,
conditions, and messages.
multi-target configuration
A copy pair configuration with a one-to-many relationship between the primary and
secondary volumes. Information from one volume is copied to multiple volumes.
N
Non-Gen’ed Volume
A volume that is not recognized by a mainframe host.
P
pair
In this manual, pair means copy pair.
pair status
Indicates the current status of the copy pair. Replication Manager uses six status
values: error, suspend, copying, sync, simplex, and unknown. A pair status is also
called copy pair status.
paired volume
Denotes a primary and secondary volume pair linked by a volume replication
functionality of a storage system. Also called a copy pair. In this manual, copy pair is
sometimes written simply as pair.
physical ID
An ID associated with a physical resource as opposed to a virtual one. See virtual ID.
prefix
The prefix portion of a copy group definition file created by Business Continuity Manager
or Mainframe Agent. Copy group definition files are created individually by prefix, so
Replication Manager uses this prefix as a unique name to identify copy group definition
files created by Business Continuity Manager or Mainframe Agent.
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Glossary-6
T
U
V
W X
Y
Z
P-VOL (primary volume)
The source volume that is copied to another volume using the volume replication
functionality of a storage system.
property files
Generic term for the files that define a Replication Manager operating environment. The
Replication Manager operating environment can be modified by changing the
appropriate property files.
Q
Quorum Disk
A GAD configuration includes a quorum disk to determine the owner node in case of
failure of the primary or secondary storage system, allowing operations to continue
without interruption.
R
refresh
The term refresh refers to updating the database that is maintained by Replication
Manager by using the most recent information. This database stores copy pair
configuration information and copy pair status information obtained from Device
Manager servers, Device Manager Agent, Business Continuity Manager, Mainframe
Agent, and Application Agent.
remote path
A logical path linking storage systems that is used for remote copying (replication of
volumes between storage systems). In this manual, logical path is a generic term for a
path that links the local system with the remote system in an enterprise-class storage
system, as well as linking the local system with the remote system in a midrange
storage system.
Remote Scan
A volume scan that can be performed on Non Gen'ed volumes outside the site where
Business Continuity Manager resides. The remote DAD attribute is assigned to the disk
configuration definition file in which the discovered volumes are stored.
RMI
Remote Method Invocation.
#
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
Glossary-7
S
SP-VOL (secondary-primary volume)
The volume located in the middle of a cascade structure, when a cascade structure is
used by the volume replication functionality of a storage system. Indicates the
secondary volume in an upper level copy pair or the primary volume in a lower level
copy pair.
S-VOL (secondary volume)
The copy destination volume of two volumes that are associated in a copy pair by a
storage system volume replication functionality.
ShadowImage
Software used to duplicate volumes in a single storage system. ShadowImage
duplicates all data on a volume. The fact that ShadowImage duplicates all data on a
volume means that the data can be restored, even if the primary volume has been
damaged or destroyed. For more information, see the ShadowImage manuals.
Snapshot Group
A group of pairs created using Copy-on-Write Snapshot/Thin Image. Use of a snapshot
group allows the same operation to be applied to more than one pair at a time. Like
device groups, snapshot groups are managed in the storage system rather than the
configuration definition file.
system
An external storage system connected to a host.
summary pair status
By displaying only the summary copy pair status of the copy groups that contain copy
pairs, Replication Manager allows users to quickly check copy pair statuses. Replication
Manager determines the summary copy pair status for each copy function (such as
ShadowImage and TrueCopy) in turn.
T
Thin Image
Software that has Copy-on-Write Snapshot functionality as well as Copy after Write
functionality installed on Virtual Storage Platform, VSP G1000, or HUS VM storage
systems. Thin Image creates a Thin Image pool that adapts the DP pool feature as a
data pool. For details, see the Thin Image documentation.
TrueCopy
Software that duplicates volumes between storage systems. TrueCopy duplicates all
data on the volumes. Three types of TrueCopy are provided: synchronous TrueCopy
Sync, asynchronous TrueCopy Synchronous Async, and asynchronous TrueCopy
Synchronous Extended Distance. For more information, see the TrueCopy manuals.
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Glossary-8
T
U
V
W X
Y
Z
U
Software that asynchronously duplicates multiple volumes between storage systems.
Universal Replicator temporarily stores differential data on a journal volume and then
duplicates the data. Universal Replicator can duplicate data on remote sites; it can also
be used to create 3DC multi-target and cascade configurations among multiple sites.
For more information, see the Universal Replicator manuals.
V
VDI meta file
A file output when you back up an SQL server database containing the configuration
information. The VDI meta file is used for database restoration.
virtual ID
Resources can be assigned virtual IDs to enable migration without having to stop the
resource. For more information, refer to the Hitachi Command Suite User Guide.
A virtual storage system that you create on a VSP G1000 system that allows multiple
resource groups to be treated as a single device. For more information, refer to the
Hitachi Command Suite User Guide.
volume
A collective name for the logical devices (LDEVs) and logical units (LUs) that are created
in a storage system.
volume replication functionality
A generic term used to refer to functionality used to perform high-speed duplication of
volumes in storage systems. This functionality allows volumes to be duplicated from
software, such as ShadowImage or TrueCopy, that is loaded in the storage system. This
software can be used once the license for it has been registered.
VSS Provider
A general name for software that provides the volume copy function used by Application
Agent.
#
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
Glossary-9
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
Glossary-10
T
U
V
W X
Y
Z
Index
A
C
Administrator privileges (UAC) 5-2
agent.logger.properties 4-33
agentif.properties file 5-13
Application Agent
and CCI 4-28
cluster configuration 4-18, 4-29
described 4-2
error log options 4-33
installing 4-26
log files 4-31, 7-6, 7-7
maximum number 4-15
port numbers 4-31
reinstalling 4-15
requirements 4-3, 4-17
service 4-32
troubleshooting 7-5
audit event 6-9
CCI 2-10
checking operation status
Replication Manager 5-4
cluster software 2-32
command
hcmds64getlogs 7-3
Common Agent service 4-28, 4-32
Copy Controller service 4-28, 4-32
Core functions B-2
open versus mainframe B-2
audit log
event categories
6-9
B
base.properties file 5-14
base.repositry.synchronize.polling 5-15
BCM Agent 2-14, 2-16, 2-48
bcmif.properties file 5-12
Business Continuity Manager (BCM) 2-14, 2-15,
2-48
version differences A-3
D
data collection
in mainframe systems 2-47
in open system 2-45
Device Manager 2-10, 2-15
version differences A-2
Device Manager agent 2-10
drmjobsch.exe command 4-29
DRMVSSServer 4-31
dynamic recognition 4-15
E
Error 0xfffffd9a
error message
RPM-03327
RPM-10006
RPM-11510
RPM-20062
event ID 9518
has occurred
7-20
7-18
7-20
7-20
7-20
7-20
Index-1
event IDs 17, 1 and 10010
7-21
maximum
copy pairs 2-36
LDEVs 2-36
resources 2-35
F
firewall
exception list (Application Agent)
exceptions (Replication Manager)
4-28
2-42
N
network
security
H
hcmds64link command 3-8
Hitachi Command Suite Common Component 2-10,
2-15
HORCM environment variables 4-14
host 2-9
system requirements 2-39
host (pair management server) 2-14, 2-26
host requirements 2-39
hrpmap_getras command 7-8
I
information source Glossary-5
infrastructure
mainframe 3-6
open systems 3-5
inqraid $Phys -CLI command 7-21
L
LDEV
maximum number 2-36
link menu 3-8
log file
log amount of data 5-11
logger.properties file 5-8
M
6-2
O
open system configuration 2-2
open systems
configurations not supported B-9
P
pair configuration
unsupported, mainframe B-9, B-12
Pair Configuration Wizard
unsupported configurations, mainframe
B-12
pair management server
described 2-8
physical ID 2-17
port numbers
firewall exceptions 2-42
properties file 5-5
agentif.properties 5-13
base.properties 5-14
bcmif.properties 5-12
logger.properties 5-8
RpMCLI.properties 5-17
serverstorageif.properties 5-11
protection function 4-29
R
mainframe
configurations not supported B-12
Mainframe Agent 2-15
mainframe configuration 2-11
management client 2-8, 2-13, 2-26
management server 2-8, 2-13
replica operations
configurations 2-23
defined 1-3
disk status remains online
out of disk space 7-19
transaction logs 7-19
troubleshooting 7-19
Index-2
7-21
B-9,
V
Replication Manager 2-10, 2-15
and BCM versions A-3
and Device Manager versions A-2
checking operation status 5-4
standby configuration 2-26
stopping 5-3
RM Shadow Copy 4-16, 7-6
roll-forward option 7-20
RPM-03327 error message 7-18
RPM-10006 error message
RpM.properties file 5-17
virtual ID 2-17
virtual storage machine 2-17
VMware ESX/ESXi support 4-20
VSS Provider
log files 7-6, 7-7
requirements 4-16
7-20
7-20
7-20
S
security
management 6-1
network 6-2
serverstorageif.properties file 5-11
settings
properties file 5-5
standby configuration 2-26
stopping
Replication Manager 5-3
storage system 2-9, 2-14
supported storage systems 2-42
system configuration
for mainframe system 2-11
for open system 2-2
system requirements
2-27
hosts and pair management servers
management client 2-37
management server
2-27
2-39
T
troubleshooting 7-1
maintenance information
resolving errors 7-2
7-3
U
UAC 5-2
unsupported configurations
B-9, B-12
Index-3
Index-4
Hitachi Data Systems
Corporate Headquarters
2845 Lafayette Street
Santa Clara, California 95050-2639
U.S.A.
www.hds.com
Regional Contact Information
Americas
+1 408 970 1000
[email protected]
Europe, Middle East, and Africa
+44 (0)1753 618000
[email protected]
Asia Pacific
+852 3189 7900
[email protected]
MK-98HC151-23

Replication Manager Configuration Guide

Transcription

Similar documents

Ziua doctoranzilor

CP-WX3530WN - Digital Media Division

Tech Spec

Photobucket With Hitachi Cloud Services

FOR LEASE 4023 State Street

clinical stabilometry standardization - ada

Featuring private in-suite swimming pools

How To Use Rsync Backup Module

Matthews Station Retail 6.6.16.pub