Hitachi Command Suite. Replication Manager. Configuration Guide. Document Organization. Product Version. Getting Help. Contents MK-98HC151-27

Size: px
Start display at page:

Download "Hitachi Command Suite. Replication Manager. Configuration Guide. Document Organization. Product Version. Getting Help. Contents MK-98HC151-27"

Transcription

1 Hitachi Command Suite Replication Manager Configuration Guide Document Organization Product Version Getting Help Contents MK-98HC151-27

2 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data Systems Corporation (collectively Hitachi ). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials. Materials mean text, data, photographs, graphics, audio, video and documents. Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication. Some of the features described in the Materials 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 Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi Data Systems Corporation. By using this software, you agree that you are responsible for: 1) Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals to access relevant data; and 2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws. 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. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eserver, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/os, z9, z10, z13, z/vm, and z/vse are registered trademarks or trademarks of International Business Machines Corporation. Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. ii

3 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 About Replication Manager Features Replication Manager operations roadmap Replication Manager system configurations and requirements Replication Manager system configurations Configurations for open systems Open system components Configurations for mainframe systems Mainframe system components Mainframe Agent versus BCM Agent Prerequisites for managing copy pairs on mainframe systems using CCI Prerequisites for data migration using virtual IDs (VSP and HUS VM) Prerequisites for data migration using virtual IDs (VSP G1000, VSP Gx00 models, or VSP Fx00 models) Prerequisites for managing global-active device copy pairs Prerequisites for managing copy pairs using snapshot groups Mainframe pairs and Device Manager Agent Configurations for mainframe monitoring Virtual command device requirements for managing copy pairs Specifying port numbers for pair management servers Configurations for replica management iii

4 Components for replica management Replication Manager in standby configuration System requirements System requirements for the management server Operating systems Server specifications Virtual memory requirements Resource Limits Maximum number of copy pairs Maximum number of LDEVs Log data and number of copy pairs System requirements for the management client Required memory for management clients System requirements for hosts and pair management servers Requirements for open systems CCI version requirement CCI version and consistency group support Functional limitations when software versions do not match Requirements for mainframe systems Supported storage systems Firewall exceptions How Replication Manager collects data Data collection in open systems Data collection in mainframe systems Setting up Replication Manager Overview Concerning upgrade installations Items to be checked after upgrading Replication Manager Setting up the prerequisite environment Open systems environment Mainframe systems environment Application replica environment Adding a link menu to the GUI display hcmds64link command options Creating a user-defined application file Setting up Application Agent About Application Agent Application Agent functions System requirements and supported environments Application Agent system requirements Host OS and database server requirements Database and backup server requirements Additional server requirements VSS Provider requirements Storage systems requirements Cluster support Cluster considerations Virtual environments supported by Application Agent VMware ESX/ESXi Server iv

5 Windows Server Hyper-V Hyper-V Live Migration Virtual memory required for Application Agent on a virtual machine of Windows Server Hyper-V Application Agent installation location Application Agent installation path restrictions If you plan to install Application Agent on the management server Installing Application Agent Adding Application Agent to the Windows Firewall Exception list Application Agent and CCI Command line interface for CCI Protection function of CCI Using CCI to configure pair volumes Device Manager and CCI Starting and stopping CCI Configuring a system to back up an SQL Server database Configuring a system to create Exchange Server database replicas Settings for Application Agent in a cluster configuration Unsupported cluster configuration Creating SQL Server replicas in a cluster configuration Creating Exchange Server replicas in a cluster configuration Exchange Server 2007 in Windows Server Failover Clustering Requirements and precautions for volume configurations Requirements for unmounting and mounting volumes Requirements for backing up and restoring volumes Precautions when changing a volume configuration Precautions for disk partition styles Application Agent and Replication Manager log output Changing Application Agent port numbers Creating file system replicas Starting and stopping the Application Agent Services Copy Controller service Common Agent service Setting error logging options for Application Agent Operating the management server About executing commands on the management server User permissions Setting up the PATH environment variable in Linux Starting and stopping Replication Manager Starting Replication Manager Stopping Replication Manager Checking the operation status of Replication Manager Changing settings in the properties files Properties related to Replication Manager logger.properties About Replication Manager log output serverstorageif.properties bcmif.properties agentif.properties appagentif.properties base.properties v

6 RpMCLI.properties Security management Network communications security Securing communications between Hitachi Command Suite Common Component and Web browsers Securing communications between Replication Manager and the Device Manager server Securing communications between Replication Manager and Business Continuity Manager (IHS) Collecting audit logs Troubleshooting Overview General problem resolution Collecting maintenance information Executing the collection command Examples of collection commands Troubleshooting Application Agent operations Resolving Application Agent installation and removal errors Application Agent and VSS Provider installer trace log files Resolving Application Agent operation errors About collecting support information Collecting support information with the hrpmap_getras command Application Agent events that can be ignored Troubleshooting when copy pairs are not recognized Items to be checked on the pair management server Installation of Device Manager Agent Link between Device Manager server and Device Manager Agent Properties of Device Manager Agent Settings in the CCI configuration definition file Items to be checked from Device Manager GUI Recognition of Device Manager Agent Recognition of the command device Recognition of the replication configuration Recognition of storage systems Items to be checked from Replication Manager GUI Creation of TrueCopy Extended Distance or COW Snapshot copy pairs fails (HUS100 Series) Troubleshooting replica operations Replica creation fails silently Backup server is not recognized as a pair management server Restoring a replica with roll-forward fails with error message RPM Creating a replica fails with error message RPM Creating a replica fails with event IDs 17, 1 and Disk status remains online after replica operation is complete A Version compatibility with other HCS products...a-1 Restrictions when Replication Manager and Device Manager versions differ... A-2 vi

7 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-11 Acronyms and Abbreviations Glossary Index vii

8 viii

9 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

10 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.4 or later. Release notes Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. 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 Description Provides a functional overview of Replication Manager and explains its characteristics and its terminology. x Preface

11 Chapter Description Chapter 2, Replication Manager system configurations and requirements on page 2-1 Describes the system configurations, system components, and system requirements of Replication Manager. Chapter 3, Setting up Replication Manager on page 3-1 Chapter 4, Setting up Application Agent on page 4-1 Chapter 5, Operating the management server on page 5-1 Chapter 6, Security management on page 6-1 Chapter 7, Troubleshooting on page 7-1 Appendix A, Version compatibility with other HCS products on page A-1 Appendix B, Supported functions and unsupported configurations on page B-1 Describes how to set up the necessary environment for Replication Manager. Describes how to set up the necessary environment and install Application Agent. 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. Describes the security functions available for Replication Manager. Describes what to do if problems occur during Replication Manager operation. Describes the compatibility between versions of Replication Manager and other Hitachi Command Suite product versions. 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

12 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 in a window, including window titles, menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a emphasized words in list items. Italic Indicates a document title or emphasized words in text. Indicates a variable, which is a placeholder for actual text provided by the user or for output by the system. Example: pairdisplay -g group (For exceptions to this convention for variables, see the entry for angle brackets.) Monospace < > angled brackets [ ] square brackets Indicates text that is displayed on screen or entered by the user. Example: pairdisplay -g oradb Indicates a variable in the following scenarios: Variables are not clearly separated from the surrounding text or from other variables. Example: Status-<report-name><file-version>.csv Variables in headings. 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

13 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 (10 3 ) bytes 1 megabyte (MB) 1,000 KB or 1,000 2 bytes 1 gigabyte (GB) 1,000 MB or 1,000 3 bytes 1 terabyte (TB) 1,000 GB or 1,000 4 bytes 1 petabyte (PB) 1,000 TB or 1,000 5 bytes 1 exabyte (EB) 1,000 PB or 1,000 6 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 cylinder Mainframe: 870 KB Open-systems: OPEN-V: 960 KB Others: 720 KB 1 KB 1,024 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes Preface xiii

14 Logical capacity unit Value 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Product documentation is available on Hitachi Data Systems Support Connect: 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 Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document to doc.comments@hds.com. Include the document title, and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you! xiv Preface

15 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 Overview of Replication Manager 1-1

16 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 Overview of Replication Manager

17 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. Overview of Replication Manager 1-3

18 You can continue monitoring the system even when not logged in to Replication Manager, because alerts can be reported in the form of 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 Device Manager 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 Overview of Replication Manager

19 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. Overview of Replication Manager 1-5

20 1-6 Overview of Replication Manager

21 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

22 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: 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 Replication Manager system configurations and requirements

23 Figure 2-1 Single site configuration in open systems Replication Manager system configurations and requirements 2-3

24 Figure 2-2 Two-site configuration in open systems 2-4 Replication Manager system configurations and requirements

25 Figure 2-3 Three-site configuration in open systems Replication Manager system configurations and requirements 2-5

26 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: Global-Active Device User Guide Hitachi Command Suite User Guide 2-6 Replication Manager system configurations and requirements

27 Note: The following conditions apply: GAD configurations are only supported on VSP G1000 or VSP Gx00 models storage systems. Application Agent does not support replica management using GAD copy pairs. Open system components Figure 2-5 Example GAD configuration The following tables list and describe system components for each type of system and provide an overview of the software components: Replication Manager system configurations and requirements 2-7

28 Table 2-1 System components (for open systems) on page 2-8 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 Description Management client Web browser 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. Management server Pair management server Replication Manager Device Manager server CCI Device Manager Agent A management server provides management information in response to requests from management clients. Replication Manager and Device Manager server (a prerequisite program of Replication Manager) are installed on the management server. If multiple sites are used, a management server is required for each site. Replication Manager and Device Manager server are installed on the management server at the local site. 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 Replication Manager User Guide. 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. 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. 2-8 Replication Manager system configurations and requirements

29 System components Software included in 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: Pair management servers must be connected to an SVP, a server that provides functions of storage system management, or a virtual command device server through UDP. Host Device Manager Agent 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 Replication Manager. Storage system Microprograms Note: If necessary, register licenses for products (such as Universal Replicator or ShadowImage). A storage system is an external storage system connected to a host. Replication Manager system configurations and requirements 2-9

30 Table 2-2 Overview of mandatory software (for open systems) Software Replication Manager Device Manager server Device Manager agent CCI Description Used to centrally manage the replication of storage system volumes in large-scale system configurations. 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. 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 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.3 or later For VSP G800: v8.2 or later For VSP Fx00 models: v8.2.1 or later For details about these agents, see the Hitachi Command Suite Administrator Guide. 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.) 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 system configurations and requirements

31 Software Description 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 Replication Manager system configurations and requirements 2-11

32 Figure 2-6 Mainframe configuration using Business Continuity Manager (BCM) 2-12 Replication Manager system configurations and requirements

33 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 Software included in system components Description Management client Web browser A management client is a computer on which users use a Web browser to run the GUI for Replication Manager. Replication Manager runs on the management server. Management server Replication Manager Device Manager server A management server provides management information in response to requests from management clients. Replication Manager and Device Manager server (a prerequisite program Replication Manager system configurations and requirements 2-13

34 System components Software included in system components Description of Replication Manager) are installed on the management server. If multiple sites are used, a management server is required for the local site. Host (pair management server) Storage system Business Continuity Manager or Mainframe Agent Microprograms Note: If necessary, register licenses for products (such as for TrueCopy Sync or Universal Replicator). 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 Replication Manager User Guide. 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 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. A storage system is used to store data accessed by hosts Replication Manager system configurations and requirements

35 Table 2-4 Overview of mandatory software for mainframe management Software Replication Manager Device Manager server Business Continuity Manager and BCM Agent Mainframe Agent Description Used to centrally manage the replication of storage system volumes in large-scale system configurations. 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. 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 Command Suite Administrator Guide. 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: 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. Replication Manager system configurations and requirements 2-15

36 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: 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 Replication Manager system configurations and requirements

37 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 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, VSP Gx00 models, or VSP Fx00 models) 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 authentication on page WARNING: Do not attempt to create a copy pair if all the following conditions are true: The Device Manager Agent version is v The CCI version is /xx. Replication Manager system configurations and requirements 2-17

38 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, VSP Gx00 models, or VSP Fx00 models, 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 /xx or later If the CCI version is /xx or later, the following conditions apply: 2-18 Replication Manager system configurations and requirements

39 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 Requirements Storage system The physical storage system is VSP Gx00 models or 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 Check the conditions described in About adding a copy group to an existing GAD pair on page Replication Manager system configurations and requirements 2-19

40 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 Gx00 models, VSP Fx00 models, 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 authentication on page 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 Replication Manager system configurations and requirements

41 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 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 Gx00 models or VSP Fx00 models, and a server that provides functions of storage system management 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. Replication Manager system configurations and requirements 2-21

42 SSL communication is established between the Device Manager server and Device Manager Agent. 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 Gx00 models, VSP Fx00 models, 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: Device Manager Agent 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 Replication Manager system configurations and requirements

43 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 SuiteAdministrator Guide. Condition Port numbers for each pair management server Device Manager Agent version CCI version Port numbers Default values v8.1.0 or later /xx or later instance-number to instance-number - (range - 1) 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. v8.0.1 Earlier than /xx /xx or later instance-number and instance-number -1 Where instance-number is the value specified for the Device Manager Agent property server.agent.temporaryinstance (default value: 4094) and 4093 v8.0.0 Earlier than /xx All versions instance-number 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): Note: In this document, creating replica or backup refers to creating replica using Application Agent. Figure 2-8 Example system configuration managing copy pairs and application replicas (Exchange) on page 2-24 Figure 2-9 Example system configuration managing copy pairs and application replicas (SQL Server) on page 2-25 Replication Manager system configurations and requirements 2-23

44 Figure 2-8 Example system configuration managing copy pairs and application replicas (Exchange) Note: Only TCS is supported for creating a remote copy Replication Manager system configurations and requirements

45 Figure 2-9 Example system configuration managing copy pairs and application replicas (SQL Server) Note: Depending on the configuration, backup servers are not required for SQL Server configurations. 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 Replication Manager system configurations and requirements 2-25

46 Table 2-5 System components (for replica management) System components Software included in system components Description 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. Table 2-6 Overview of mandatory software (for replica management) Software Application Agent VSS provider: RM Shadow Copy (Exchange only) Description 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. 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. 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 Replication Manager system configurations and requirements

47 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 Operating systems 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-33 Resource Limits on page 2-36 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-11 Requirements for a cluster environment on page Replication Manager system configurations and requirements 2-27

48 If you plan to use the Replication Manager CLI, see Table 2-10 Requirements for using the Replication Manager CLI on a management server on page 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 Server 2008 R2 SP1 Windows operating system Supports IPv4 and IPv6 connections Also runs as a guest OS of Windows Server 2008 Hyper-V and V2 Also runs under VMware ESXi Server 5.x.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 Supports IPv4 and IPv6 connections Also runs under VMware ESXi Server 5.x. To execute Replication Manager on the virtual server, configure the virtual server using the recommended configuration. Operation on Server Core is not supported Operation on Minimal Server Interface is not supported Also runs as a guest OS of KVM on Red Hat Linux 6.4. Windows Server 2012 R2 Supports IPv4 and IPv6 connections Also runs under VMware ESXi Server 5.x. To execute Replication Manager on the virtual server, configure the virtual server using the recommended configuration. Operation on Server Core is not supported Operation on Minimal Server Interface is not supported Also runs as a guest OS of KVM on Red Hat Linux 6.4. Note: 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: 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) 2-28 Replication Manager system configurations and requirements

49 The following table lists the server specifications required for a Linux environment. Table 2-8 Linux OS and programs for a management server (1/2) Linux operating system Red Hat Enterprise Linux 5.8 Supports IPv4 and IPv6 connections The following RPM package 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 Prerequisite programs Device Manager server Red Hat Enterprise Linux 5.9 Supports IPv4 and IPv6 connections The following RPM package 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 Red Hat Enterprise Linux 5.10 Supports IPv4 and IPv6 connections The following RPM package 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 Red Hat Enterprise Linux 5.11 Supports IPv4 and IPv6 connections The following RPM package 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 Red Hat Enterprise Linux 6.0 Supports IPv4 and IPv6 connections 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 Replication Manager system configurations and requirements 2-29

50 Linux operating system 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 kernel el6.x86_64.rpm or later kernel-firmware el6.noarch.rpm or later Prerequisite programs Red Hat Enterprise Linux 6.1 Supports IPv4 and IPv6 connections 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 kernel el6.x86_64.rpm or later kernel-firmware el6.noarch.rpm or later Red Hat Enterprise Linux 6.2 Supports IPv4 and IPv6 connections 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 kernel el6.x86_64.rpm or later kernel-firmware el6.noarch.rpm or later Red Hat Enterprise Linux 6.3 Supports IPv4 and IPv6 connections The following RPM package 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 Red Hat Enterprise Linux 6.4 Supports IPv4 and IPv6 connections Also runs under Kernel-based Virtual Machine (KVM) on Red Hat Enterprise Linux 6.4. The following RPM package 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 2-30 Replication Manager system configurations and requirements

51 Linux operating system net-snmp-agent-libs-rpm-package-version.x86_64.rpm net-snmp-devel-rpm-package-version.x86_64.rpm Prerequisite programs Table 2-9 Linux OS and programs for a management server (2/2) Linux operating system Red Hat Enterprise Linux 6.5 Supports IPv4 and IPv6 connections The following RPM package must be applied to this OS: upstart 0.6.5_13.el6_5.3.x86_64.rpm 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 Prerequisite programs Device Manager server Red Hat Enterprise Linux 6.6 Supports IPv4 and IPv6 connections 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 Red Hat Enterprise Linux 6.7 Supports IPv4 and IPv6 connections 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 Red Hat Enterprise Linux 7.0 Supports IPv4 and IPv6 connections 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 glibc el7.i686.rpm or later Replication Manager system configurations and requirements 2-31

52 Linux operating system tcsh el7.x86_64.rpm or later net-tools git.el7.x86_64.rpm or later perl el7.x86_64.rpm or later Prerequisite programs Red Hat Enterprise Linux 7.1 Supports IPv4 and IPv6 connections 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 glibc el7.i686.rpm or later tcsh el7.x86_64.rpm or later net-tools git.el7.x86_64.rpm or later perl el7.x86_64.rpm or later Red Hat Enterprise Linux 7.2 Supports IPv4 and IPv6 connections 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 glibc el7.i686.rpm or later tcsh el7.x86_64.rpm or later net-tools git.el7.x86_64.rpm or later perl el7.x86_64.rpm or later SUSE Linux Enterprise Server 11 (No SP, SP1, SP2, SP3, SP4) Supports IPv4 and IPv6 connections The following RPM package must be applied to this OS: net-snmp-rpm-package-version.x86_64.rpm SUSE Linux Enterprise Server 12 (No SP, SP1) Supports IPv4 and IPv6 connections The following RPM package must be applied to this OS: sysstat x86_64.rpm or later Note: If you link to a Device Manager Agent running on a guest OS of 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 Replication Manager system configurations and requirements

53 The same OSs provided as a guest OS of VMware ESXi Server 6.0 are also supported. If you operate Replication Manager on a virtualization server, use the recommended configuration of the server virtualization software. The following table lists the server specifications required for use of the Replication Manage CLI. Table 2-10 Requirements for using the Replication Manager CLI on a management server Operating system Edition Windows Windows server 2008 R2 SP1 Windows Server 2012 no SP Windows Server 2012 R2 Linux Red Hat Enterprise Linux 5.11, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 7.0, 7.1, and 7.2 SUSE Linux Enterprise Server 11 no SP, SP1, SP2, SP3, SP4 SUSE Linux Enterprise Server 12 no SP, SP1 The following table lists the server specifications required for a cluster environment. Table 2-11 Requirements for a cluster environment Operating system Cluster software Windows Microsoft Windows Server 2008 R2 SP1 Windows Server Failover Microsoft Windows Server 2012 no SP Clustering Microsoft Windows Server 2012 R2 Linux Red Hat Enterprise Linux 6.5 Red Hat Enterprise Linux High Availability Server specifications For management server requirements to run Replication Manager (and Device Manager and Tiered Storage Manager), see the Hitachi Command Suite System Requirements. 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-34 and Table 2-14 Virtual memory requirements for each product (32-bit) on page 2-35 should be taken into account. Replication Manager system configurations and requirements 2-33

54 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 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) 2501 Hitachi Command Suite 1 Device Manager Tiered Storage Manager Replication Manager Host Data Collector Device Manager has small memory heap size Device Manager has medium memory heap size Device Manager has large memory heap size 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. Example calculation (for 64-bit) For example, it is necessary to allocate a virtual memory capacity greater than 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 MB of virtual memory is already allocated for the operating system and other programs. The calculation is as follows: 1780 (Common Component) (64-bit) (Hitachi Command Suite) (Allocated virtual memory) = Replication Manager system configurations and requirements

55 Table 2-13 Agent virtual memory requirements Agent Device Manager Agent Application Agent (Replication Manager) Tuning Manager Agent Tuning Manager Requirement Specify the virtual memory size value for the server.agent.maxmemorysize property. (See the Hitachi Command Suite Administrator Guide for more information.) See Virtual memory on page 4-12 for more information. See the Hitachi Command Suite Tuning Manager Installation Guide. 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 Virtual memory capacity (MB) Common Component (for 32-bit) Small memory heap size 1524 Medium memory heap size 1780 Large memory heap size 2292 Hitachi NAS Manager Hitachi File Services Manager Storage Navigator Modular Note: 1. The virtual memory capacities for Hitachi NAS Manager, Hitachi File Services Manager, and Storage Navigator Modular 2 are for version 6.4, 5.2.1, and 28.02, 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 MB of virtual memory is already allocated for the operating system and other programs. The calculation is as follows: 2292 (Common Component) (Hitachi NAS Manager) (Allocated virtual memory) Replication Manager system configurations and requirements 2-35

56 = 3804 Resource Limits Tip: If you install the 64-bit and 32-bit product on a management server, you must allocate the virtual memory requirements for both. 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-36 Maximum number of LDEVs on page 2-37 Log data and number of copy pairs on page 2-38 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. Table 2-15 Maximum number of copy pairs that can be managed Environment Number of copy pairs by memory heap size Small Medium Large Open systems only 6,000 12,000 24,000 Mainframe systems only 40,000 60,000 90,000 Combined open and mainframe 1 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 2-36 Replication Manager system configurations and requirements

57 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 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 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 Open systems only Environment The LDEV information acquisition source is a local Device Manager The LDEV information acquisition source is a remote Device Manager Number of LDEVs by memory heap size Small Medium Large 50,000 80,000 1,000, ,000 Mainframe systems only 80, , ,000 Replication Manager system configurations and requirements 2-37

58 Environment Number of LDEVs by memory heap size Small Medium Large Combined open and mainframe The LDEV information acquisition source is a local Device Manager on the open system The LDEV information acquisition source is a remote Device Manager on the open system 80, , ,000, ,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. 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-17 Supported Windows OS and web browsers for a management client Windows operating system Web browser Windows Server 2008 SP2 (32- Internet Explorer 9.0 bit) 1 Windows Server 2008 R2 no SP Internet Explorer 9.0 (64-bit) 2 (only the 32-bit version is supported) Windows Server 2008 R2 SP1 (64- Internet Explorer 9.0, 11.0 bit) 1 (only the 32 bit version is supported) Windows Server 2008 SP2 (64- Internet Explorer 9.0 bit) 1 (only the 32-bit version is supported) 2-38 Replication Manager system configurations and requirements

59 Windows operating system Web browser Windows Server 2012 no SP 1, 2 Internet Explorer 10.0 (only the 32-bit version is supported) Windows Server 2012 R2 no SP 1, 2 Internet Explorer 11.0 (only the 32-bit version is supported) Windows Vista SP2 Internet Explorer 9.0 (only the 32-bit version is supported) Windows 7 no SP Internet Explorer 9.0 (only the 32-bit version is supported) Windows 7 SP1 Internet Explorer 9.0, 11.0 (only the 32-bit version is supported) Windows 8 no SP Internet Explorer 10.0 (only the 32-bit version is supported) Windows 8.1 no SP Internet Explorer 11.0 (only the 32-bit version is supported) Notes: 1. Operation on Server Core is not supported. 2. Operation on Minimal Server Interface is not supported Table 2-18 Supported Linux OS and web browsers for a management client Linux operating system Web browser Red Hat Enterprise Linux 5.3 (32- bit) Red Hat Enterprise Linux 5.4 (32- bit) Red Hat Enterprise Linux 5.5 (32- bit) Red Hat Enterprise Linux 5.6 (32- bit) Red Hat Enterprise Linux 5.7 (32- bit) Red Hat Enterprise Linux 5.8 (32- bit) Red Hat Enterprise Linux 5.9 (32- bit) Red Hat Enterprise Linux 5.10 (32- bit) Red Hat Enterprise Linux 5.11 (32- bit) 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 17.0.x Firefox ESR 17.0.x Replication Manager system configurations and requirements 2-39

60 Linux operating system Red Hat Enterprise Linux 6.0 (32- bit) Red Hat Enterprise Linux 6.1 (32- bit) Red Hat Enterprise Linux 6.2 (32- bit) Red Hat Enterprise Linux 6.3 (32- bit) Red Hat Enterprise Linux 6.4 (32- bit) Red Hat Enterprise Linux 6.5 (32- bit) Red Hat Enterprise Linux 6.6 (32- bit) Red Hat Enterprise Linux 6.7 (32- bit and 64-bit) Red Hat Enterprise Linux 7.0 (64- bit) Red Hat Enterprise Linux 7.1 (64- bit) Red Hat Enterprise Linux 7.2 (64- bit) SUSE Linux Enterprise Server 11 no SP (32-bit) SUSE Linux Enterprise Server 11 SP1 or SP2 (32-bit) SUSE Linux Enterprise Server 11 SP3 (32-bit) SUSE Linux Enterprise Server 11 SP4 (32-bit and 64-bit) SUSE Linux Enterprise Server 12 No SP (64-bit) SUSE Linux Enterprise Server 12 SP1 (64-bit) Web browser Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 17.0.x, Firefox ESR 24.1.x, Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 Firefox ESR 31, Firefox ESR 38 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 Replication Manager system configurations and requirements

61 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 Operating system Prerequisite programs Host Pair management server The Device Manager Agent must support the OS. For information about supported operating systems for the host or pair management server, see the Hitachi Command Suite Installation and Configuration Guide. 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 or later, we strongly recommend that the version of CCI running on the same host as the agent be /05 or later for Windows or /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 /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). Replication Manager system configurations and requirements 2-41

62 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 The following operations are not supported if you are using Business Continuity Manager 6.6.1: 2-42 Replication Manager system configurations and requirements

63 When using Business Continuity Manager 6.6.1, if a volume scan using Replication Manager is performed, an error (RPM-00539) occurs in Replication Manager. 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 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 VSP Gx00 models VSP Fx00 models 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 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: Table 2-21 Port numbers to register as firewall exceptions between the management server and management clients on page 2-44 Replication Manager system configurations and requirements 2-43

64 Table 2-22 Port numbers to register as firewall exceptions between the Replication Manager management server and remote Device Manager management server on page 2-44 Table 2-23 Port numbers to register as firewall exceptions between the management server and the pair management server, or the host (open system) on page 2-45 Table 2-24 Port numbers to register as firewall exceptions between the management server and the host (mainframe system) on page 2-45 Table 2-25 Port numbers to register as firewall exceptions between the management server and the database or backup server on page 2-45 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-36 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 /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 Originator Destination Description 2001/tcp Replication Manager management server Remote Device Manager management server 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 Replication Manager system configurations and requirements

65 Port number Originator Destination Description 2443/tcp Replication Manager management server Remote Device Manager management server This port is used to communicate with Device Manager Server via SSL. It represents the value of the server.https.port property in the server.properties file for Device Manager Server. This port is required for SSL connections. Table 2-23 Port numbers to register as firewall exceptions between the management server and the pair management server, or the host (open system) Port number Originator Destination Description 24041/tcp 24042/tcp Management server Pair management server Host (open system) This port is used to communicate with Device Manager Agent. It represents the value of the server.agent.port property in the server.properties file for Device Manager Agent. Table 2-24 Port numbers to register as firewall exceptions between the management server and the host (mainframe system) Port number Originator Destination Description 24042/tcp Management server Host (mainframe system) This port is used to communicate with Business Continuity Manager (when IHS is not being used 1 ), 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. Table 2-25 Port numbers to register as firewall exceptions between the management server and the database or backup server Port number Originator Destination Description 24041/tcp 24042/tcp Management server database server backup server This port is used to communicate with Device Manager Agent. It represents the value of the server.agent.port property in the server.properties file for Common Agent Component. Replication Manager system configurations and requirements 2-45

66 Table 2-26 Port numbers to register as firewall exceptions between the database server and the backup server Port number Originator Destination Description 22300/tcp database server backup server database server backup server 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 Replication Manager system configurations and requirements

67 Figure 2-11 Data collection (open systems) Acquiring configuration and license information Replication Manager acquires the following information using Device Manager server: Copy pair configuration information Volume configuration information (including the command device, pool volumes, and journal volumes) License information for the volume replication functionality Device Manager server stores information acquired from storage systems, while Replication Manager stores information acquired from Device 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. Replication Manager system configurations and requirements 2-47

68 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 Replication Manager system configurations and requirements

69 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 Replication Manager system configurations and requirements 2-49

70 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) Replication Manager system configurations and requirements

71 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 Setting up Replication Manager 3-1

72 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 For a cluster environment, follow the appropriate procedure in the Hitachi Command Suite Installation and Configuration Guide before installing Replication Manager. 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) Item Before (v6.x or v7.x) After (v8.x) Hitachi Command Suite common component command names Hitachi Command Suite default installation folder hcmdsxxxx For x86: %ProgramFiles%\HiCommand For x64: %ProgramFiles(x86)% \HiCommand hcmds64xxxx %ProgramFiles%\HiCommand 3-2 Setting up Replication Manager

73 Item Hitachi Command Suite common component default installation folder Before (v6.x or v7.x) After (v8.x) Note: %ProgramFiles% and %ProgramFiles(x86)% are Windows environment variables. Table 3-2 Command names and file paths changed after upgrade to v8.x (Linux) Item Before (v6.x or v7.x) After (v8.x) Hitachi Command Suite common component command names Hitachi Command Suite common component default installation directory hcmdsxxxx hcmds64xxxx Hitachi-Command-Suiteinstallation-folder\Base Hitachi-Command-Suiteinstallation-folder\Base64 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. Setting up Replication Manager 3-3

74 Figure 3-1 Infrastructure configuration workflow 3-4 Setting up Replication Manager

75 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 that are to be managed by Device Manager and 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 Command Suite Administrator Guide. After you edit the properties file, restart Device Manager Agents. For details about how to edit the properties file, the specification rules, and how to restart Device Manager Agents, see the Hitachi Command Suite Administrator Guide. Setting up Replication Manager 3-5

76 6. Install Device Manager Agents on the hosts. For details, see the Hitachi Command Suite Administrator Guide. Note: Hosts can be added manually or by the Host Data Collector (HDC) 7. If there is any host on which Device Manager Agent has not 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. 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 2. 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. 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: 3-6 Setting up Replication Manager

77 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 5. 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. The serial numbers for all storage systems managed by Device Manager are unique. Setting up Replication Manager 3-7

78 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 Replication Manager. 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 Setting up Replication Manager

79 Table 3-3 hcmds64link command options add delete Item file user-definedapplication-file user user-id pass password Description Specify this option to add a link. Specify this option to delete a link. Specify the file (the user-defined application file) used to register the link information. 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 The following table describes the available options. Table 3-4 Items specified in the user-defined application icon-url Description Start key for the user-defined application file. This item is required. 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. 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. Specifies the link name to be displayed in the Links dialog box. Specify Unicode characters in the range U to U+10FFFF, using no more than 80 characters. If you do not specify this item, the value specified in line is used as the link name. Specifies the order of values to be displayed in the Links dialog box. Specify a value from to Values specified here are displayed in ascending order in the Links dialog box. Specifies the location of the icon displayed beside the link. Use no more than 256 bytes. In IPv6 Setting up Replication Manager 3-9

80 @TOOL-END Item Description environments, specify a host name instead of an IPv6 address. 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 Setting up Replication Manager

81 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 Requirements and precautions for volume configurations Application Agent and Replication Manager log output Changing Application Agent port numbers Creating file system replicas Starting and stopping the Application Agent Services Setting error logging options for Application Agent Setting up Application Agent 4-1

82 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 Setting up Application Agent

83 MS Exchange databases contain the following two types of information stores: Mailbox stores for saving received messages, attachments, folders, documents, etc. Public folder stores for saving information shared among users ( 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. Setting up Application Agent 4-3

84 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 Exchange version Windows Server 2008 no SP (64-bit) Windows Server 2008 SP1 (64-bit) Windows Server 2008 no SP 2 Windows Server 2008 no SP (64-bit) Windows Server 2008 SP1 2 Windows Server 2008 SP1 (64-bit) , no SP 2, SP1, SP2, SP3 Windows Server 2008 SP2 (64-bit) Windows Server 2008 SP2 2 Windows Server 2008 SP2 (64-bit) no SP 2, SP1, SP2, SP no SP, SP1, SP2. SP3 Windows Server 2008 R2 no SP Windows Server 2008 R2 no SP SP3 Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP no SP, SP1, SP2. SP no SP, SP1 Windows Server 2012 no SP Windows Server 2012 no SP SP no SP, SP1 Windows Server 2012 no SP Windows Server 2012 R2 no SP SP1 4-4 Setting up Application Agent

85 Database server OS Backup server OS Exchange version Windows Server 2012 R2 no SP Windows Server 2012 no SP SP1 Windows Server 2012 R2 no SP Windows Server 2012 R2 no SP 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 SQL Server version Windows Server 2008 (no SP/SP1) Windows Server 2008 (SP2) Windows Server 2008 IPF(no SP/ SP1) Windows Server 2008 IPF (SP2) Windows Server 2008 R2 IPF (no SP) Windows Server 2008 R2 IPF (SP1) Windows Server 2008 x64 (no SP/ SP1) Windows Server 2008 x64 (SP2) Windows Server 2008 R2 (no SP) Windows Server 2008 R2 (SP1) Windows Server 2008 (no SP/ SP1) Windows Server 2008 (SP2) Windows Server 2008 IPF (no SP/SP1) Windows Server 2008 IPF (SP2) Windows Server 2008 R2 IPF (no SP) Windows Server 2008 R2 IPF (SP1) Windows Server 2008 x64 (no SP/SP1) Windows Server 2008 x64 (SP2) Windows Server 2008 R2 (no SP) Windows Server 2008 R2 (SP1) 2005 (SP2 1, SP3, SP4) 2008 (no SP 1, SP1, SP2, SP3, SP4 1 ) 2008 R2 (no SP, SP1 1, SP2 1, SP3 1 ) 2005 (SP2 1, SP3, SP4) 2005 IPF (SP2 1, SP3, SP4) 2008 (no SP 1, SP1, SP2, SP3, SP4 1 ) 2008 IPF (no SP 1, SP1, SP2, SP3, SP4 1 ) 2008 R2 (no SP, SP1 1, SP2 1, SP3 1 ) 2008 R2 IPF (no SP, SP1 1, SP2 1, SP3 1 ) 2005 (SP2 1, SP3, SP4) 2005 x64 (SP2 1, SP3, SP4) 2008 (no SP 1, SP1, SP2, SP3, SP4 1 ) 2008 x64 (no SP 1, SP1, SP2, SP3, SP4 1 ) 2008 R2 (no SP, SP1 1, SP2 1, SP3 1 ) 2008 R2 x64 (no SP, SP1 1, SP2 1, SP3 1 ) 2012 (no SP, SP1) (no SP, SP1) 4 Setting up Application Agent 4-5

86 Database server OS Backup server OS SQL Server version Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) 2012 (no SP 3, SP1, SP2) 2014 (no SP, SP1) 4 Notes: A backup server is only mandatory for data backup to a tape or for secondary use of the data. 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). 3. SQL Server 2012 no SP is supported only if both the database server and backup server are Windows Server If SQL Server 2014 (no SP, SP1) 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 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 Windows Server 2008 (32-bit) no SP or SP1, SP2 Windows Server 2008 no SP or SP1, SP2 (64-bit) Windows Server 2008 R2 no SP, SP1 Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) Backup server OS Windows Server 2008 (32-bit) no SP or SP1, SP2 Windows Server 2008 (32-bit) no SP or SP1, SP2 Windows Server 2008 (64-bit) no SP or 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) Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) File system type NTFS 4-6 Setting up Application Agent

87 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 Windows Server 2008 (32-bit) no SP or SP1, SP2 Windows Server 2008 IPF no SP or SP1, SP2 Windows Server 2008 R2 IPF no SP, SP1 Windows Server 2008 (64-bit) no SP or SP1, SP2 Windows Server 2008 R2 no SP, SP1 Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) Backup server OS Windows Server 2008 (32-bit) no SP or SP1, SP2 Windows Server 2008 IPF no SP or SP1, SP2 Windows Server 2008 (64-bit) no SP or SP1, SP2 Windows Server 2008 R2 no SP, SP1 Windows Server 2008 R2 IPF no SP, SP1 Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) File system type NTFS Database and backup server requirements This section describes database and backup server requirements. File systems are only supported using the Application Agent CLI. Note: When using IPv6, both IPv4 and IPv6 must be enabled on the database and backup servers. You can use IPv6 addresses only if they are global addresses. Table 4-6 Database and backup server requirements (file systems) Operating system IPv6 support Required programs Windows Server 2008 no SP or SP1 5,7,8 Y CCI 14 Windows Server 2008 SP2 5,7,8 Windows Server 2008 IPF no SP or SP1 8,9,10 Windows Server 2008 IPF SP2 8,9,10 Y Y Y Logical Volume Manager (Windows LDM 3,11 ) Application Agent v 7.0 or later 11 Windows Server 2008 no SP or SP1 (64- bit) 5,7,8,9 Windows Server 2008 SP2 (64-bit) 5,7,8,9 Y Y Setting up Application Agent 4-7

88 Operating system IPv6 support Required programs Windows Server 2008 R2 no SP 8 Y 2 Windows Server 2008 R2 IPF no SP 1,5,7 Y Windows Server 2008 R2 SP1 1,5,7,8 Y 2 CCI 14 Windows Server 2008 R2 IPF SP1 8,9,10 Windows Server 2012 no SP 8,12 Y 2 CCI 14 Windows Server 2012 R2 no SP 8,12 Y 2 CCI 14 Y Volume Manager (Windows LDM 3,11 ) Application Agent v 7.1 or later 11 Volume Manager (Windows LDM 3, 10 ) Application Agent v 7.4 or later 11 Volume Manager (Windows LDM 3, 10 ) Application Agent v 7.4 or later 11 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 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. 4-8 Setting up Application Agent

89 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 , be sure and apply the module on all servers using VSS. 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 Y CCI 10 SP1 3,4.5.6 Windows Server 2008 SP2 3,4.5.6 Windows Server 2008 no SP or SP1 (IPF) 3,5 Y Y Logical volume manager (the standard Windows LDM 7,8 ) Application Agent v 6.4 or later 8 Device Manager Agent 2 Windows Server 2008 SP2 (IPF) 3,5 Windows Server 2008 no SP or SP1 (64-bit) 3,4 Windows Server 2008 no SP or SP2 (64-bit) 3 Y Y Y Windows Server 2008 R2 no SP Y 1 Windows Server 2008 R2 no SP (IPF) 3,5 Y Windows Server 2008 R2 SP1 3,4.5 Y 1 CCI 10 Windows Server 2008 R2 SP1 (IPF) 3,5 Windows Server 2012 no SP 5,10 Y 1 CCI 10 Windows Server 2012 R2 no SP 5,10 Y 1 CCI 10 Y Logical volume manager (the standard Windows LDM 7,8 ) Application Agent v 7.1 or later Device Manager Agent 2 Logical volume manager (the standard Windows LDM 7,8 ) Application Agent v 7.4 or later Device Manager Agent 2 Logical volume manager (the standard Windows LDM 7,8 ) Application Agent v 7.4 or later Device Manager Agent 2 Setting up Application Agent 4-9

90 Notes: 1. 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. 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 /05. You must configure the following setting in the Device Manager properties (server.properties) file: server.agent.rm.optimization.userhorcmfile=true If you do not add this value, Replication Manager might not be able to acquire pair, pool, and journal information. For details on editing the properties file, see the 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 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. Application Agent does not support the Veritas Dynamic Multiple Pathing function. 9. Operation on Minimal Server Interface is not supported. 10. The architecture of CCI must match that of the OS. Table 4-8 Database and backup server requirements (Microsoft Exchange Server) Operating system IPv6 support Required programs Windows Server 2008 no SP/SP1 or Y CCI 7 SP2 (64-bit) 6 Logical volume manager (the standard Windows LDM 3 ) 4-10 Setting up Application Agent

91 Operating system IPv6 support Required programs Application Agent v 6.3 or later 5 RM Shadow Copy Provider (VSS Provider) /05 or later Device Manager Agent 2 Windows Server 2008 no SP/SP1 or Y CCI 7 SP2 (32-bit) 4,6 Windows Server 2008 R2 no SP2 6 Y 1 Windows Server 2008 R2 SP1 6 Y 1 CCI 7 Windows Server 2012 no SP 6 Y 1 CCI 7 Windows Server 2012 R2 no SP 6 Y 1 CCI 7 Logical volume manager (the standard Windows LDM 3 ) Application Agent v 7.0 or later 5 RM Shadow Copy Provider (VSS Provider) /05 or later Device Manager Agent v 6.0 or later 2 Logical volume manager (the standard Windows LDM 3 ) Application Agent v 7.1 or later 5 RM Shadow Copy Provider (VSS Provider) /05 or later Device Manager Agent 2 Logical volume manager (the standard Windows LDM 3 ) Application Agent v 7.6 or later 5 RM Shadow Copy Provider (VSS Provider) /05 or later Device Manager Agent 2 Logical volume manager (the standard Windows LDM 3 ) Application Agent v 7.6 or later 5 RM Shadow Copy Provider (VSS Provider) /05 or later Device Manager Agent 2 Notes: 1. Communication using IPv6 is supported even when using FTP with the 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 /05 Setting up Application Agent 4-11

92 You must configure the following setting in the Device Manager properties (server.properties) file: server.agent.rm.optimization.userhorcmfile=true If you do not add this value, Replication Manager might not be able to acquire pair, pool, and journal information. For details on editing the properties file, see the 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. LDM basic structure is supported. 4. This is supported when using the Application Agent CLI. 5. Be sure to install the same version of Application Agent on the database and backup servers. 6. Operation on Server Core is not supported. 7. The architecture of CCI must match that of the OS. 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 * number-of-physical-disks + number-ofsecondary-volumes * number-of-paired-volumes * number-ofdatabases-to-be-backed-up * number-of-data-files-to-be-backed-up * number-of-drives-to-be-backed-up * number-of-files-ordirectories-to-be-backed-up * 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 Setting up Application Agent

93 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 an 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 an 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. 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. Setting up Application Agent 4-13

94 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. For additional notes regarding pair configuration, refer to the requirements when using CCI to configure a pair volume documented in the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. Application Agent versions on database and backup servers The same version of Application Agent must be installed on database 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.) 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: 4-14 Setting up Application Agent

95 Exchange Server: TrueCopy Sync SQL Server: TrueCopy and Universal Replicator For additional information, refer to the precautions on backing up and restoring data between storage systems documented in the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. 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. 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. Setting up Application Agent 4-15

96 Software version Replication Manager and Application Agent support VSS Provider /05 or later. The prerequisite CCI version is /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 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 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: 4-16 Setting up Application Agent

97 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 Gx00 models VSP Fx00 models Note: If the backup or database server operating system is Windows Server 2012, Application Agent only supports the Virtual Storage Platform, VSP G1000, VSP Gx00 models, VSP Fx00 models, 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 Hitachi AMS series Hitachi WMS series Hitachi AMS2000 series HUS100 series Hitachi USP Universal Storage Platform V Universal Storage Platform VM Hitachi VSP Hitachi VSP G1000 VSP Gx00 models HUS VM Volume replication function ShadowImage TrueCopy Copy-on-Write SnapShot ShadowImage TrueCopy TrueCopy Asynchronous Copy-on-Write SnapShot Universal Replicator ShadowImage TrueCopy Thin Image Copy-on-Write SnapShot Universal Replicator ShadowImage TrueCopy Thin Image Universal Replicator global-active device ShadowImage Setting up Application Agent 4-17

98 VSP Fx00 models Storage system Volume replication function Thin Image TrueCopy Universal Replicator Note: Application Agent for Exchange does not support Universal Replicator. Cluster support 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 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). 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 Cluster software Windows Server Failover 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 Windows Server Failover 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 SP Setting up Application Agent

99 Database server OS Cluster software Windows Server 2012 no SP 1,2 Windows Server 2012 R2 no SP 1,2 Notes: Cluster considerations 1. Be sure to install the FailoverCluster-CmdInterface (an optional component of WSFC). For details about optional components, see the Microsoft documentation. 2. Restoration while cluster resources are online is not supported. Use Windows Server 2008 or Windows Server 2008 R2 if you need the online restoration. The following considerations apply to cluster support and operations: Application Agent supports both mutual standby cluster configurations (Active-Active) and operational standby cluster configurations (Active- Passive). However, For the cluster configuration, Replication Manager (Server) supports the Active - Passive configuration only. To restore backup data, the database must be taken offline. If a 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. 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 Setting up Application Agent 4-19

100 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 5.x and 6.0 are also supported. Table 4-13 Guest Operating systems and VMware ESX/ESXi version VMware ESX/ESXi version ESXi 5.0 (no update, Update 1, Update 3) 1,2 ESXi 5.0 (Update 2) 1,2 ESXi 5.1 (no update, Update 1, Update 2) 1,2 ESXi 5.5 (no update, Update 1, Update 2) 1,2,4 ESXi 6.0 (no update) 1,2,5 Guest OS Windows Server 2008, Windows Server 2008 R2 Windows Server 2008, Windows Server 2008 R2, Windows Server , Windows Server 2012 R2 3 Windows Server 2008, Windows Server 2008 R2 Windows Server 2008, Windows Server 2008 R2, Windows Server , Windows Server 2012 R2 3 Windows Server 2008, Windows Server 2008 R2, Windows Server , Windows Server 2012 R2 3 Notes: 1. Do not run VMware live migration (VMware vmotion) and Application Agent at the same time. If you run them simultaneously, Application Agent might fail. In such a case, please take action according to message shown in the troubleshooting information. 2. Application Agent does not support VMware FT (Fault Tolerance). 3. Only SQL Server is supported. 4. Windows Server 2012 or later is supported. 5. Application Agent does not support VMware VVol (Virtual Volume). The following considerations apply to Application Agent and VMware ESX/ESXi Server operations: 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 4-20 Setting up Application Agent

101 method used by the guest OS of VMware ESX/ESXi Server 5.x and 6.0 is as follows. Table 4-14 VMware ESX/ESXi support status for each connection method used by the guest OS Physical connection Disk type Compatible mode Supported/Not Supported FC Raw device mapping Physical Yes 1 Virtual No Virtual disk No iscsi Raw device mapping Physical Yes 1 Virtual No Virtual disk No 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. Setting up Application Agent 4-21

102 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 Windows Server Hyper- V version Guest OS of Windows Server Hyper- V Exchange Server 2007 Exchange Server 2010 Application Agent Exchange Server 2013 SQL Server 1 File system Windows Server 2008 Hyper-V Windows Server 2012 Hyper-V Windows Server 2012 R2 Hyper-V Windows Server 2008 (32-bit) (no SP/SP1, SP2) Windows Server 2008 (64-bit) (no SP/SP1, SP2) Windows Server 2008 R2 (no SP, SP1) Windows Server 2008 R2 (no SP, SP1) Windows Server 2012 (no SP) Windows Server 2012 R2 (no SP) 5 N N N Y 2 Y Y Y N Y 2 Y Y Y Y Y 2, 3 Y N Y Y N N N N Y Y 2,4 Y N N N Y 2,6 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. 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 4-22 Setting up Application Agent

103 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. SQL Server 2012 and SQL Server 2014 are supported. 5. 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. 6. SQL Server 2012 SP1 or later and SQL Server 2014 are supported. Table 4-16 Windows Server Hyper-V support based on the guest OS connection method Physical connection Guest OS connection method Supported Fibre Channel Pass through Y 1,2,3 VHD/VHDX Virtual FC 4 N N iscsi Pass through Y 1,2,3 VHD/VHDX Direct connection N Y Notes: Setting up Application Agent 4-23

104 1. The backup server does not support operation in a virtual environment if the secondary volume is concealed. In that case, you must configure the backup server without virtualization servers. 2. The backup server does not support operation in a virtual environment if you perform VSS backup using the Application Agent CLI. In that case, you must configure the backup server without virtualization servers. 3. SQL Server cluster configurations are not supported on guest operating systems. In these configurations, you must use drives that are directly connected to iscsi. 4. Applicable for Windows Server 2012 Hyper-V or Windows Server 2012 R2 Hyper-V. 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. 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: 4-24 Setting up Application Agent

105 %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 Caution: If Hitachi Command Suite Common agent component and Device Manager agent are not installed on the computer when you start the Application Agent installation, they are automatically installed as follows: The Common agent component is installed in the same location as documented for Application Agent The Device Manager Agent is installed in this location: Common-agent-component-installation-folder\mod\hdvm If you want to specify an arbitrary folder for these installation folders, install the components before you start the Application Agent installation. 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 Restart the Common Component service as described in Starting Replication Manager on page Select all the remote Device Manager instances and execute Refresh Configuration Setting up Application Agent 4-25

106 4. Select all of the storage devices managed by the local Device Manager instance and execute Refresh Storage System Information. 5. Install Application Agent on the management server. If Application Agent is already installed on the management server: 1. Install Replication Manager on the management server. 2. Set the value of base.refreshdginfo.exec in the base.properties file to 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 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 Setting up Application Agent

107 Proceed to step 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: If you plan to perform VSS backups, select to install the Component for Exchange to install the Shadow Copy Provider. If the option to install the Component for Exchange is not displayed, 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 Setting up Application Agent 4-27

108 the HDvM agent as described in the Hitachi Command Suite Installation and Configuration Guide. 18. When the installation finishes, restart Windows. Note: If the Application Agent is installed on a host without a database application installed, Replication Manager will fail in any attempts to obtain information by refreshing the host. If this occurs, one of the following error messages is displayed: RPM The specified SQL instance name is invalid or no SQL instance settings exist. RPM 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-29 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 Setting up Application Agent

109 Command line interface for CCI Note the following precautions regarding using the CCI command line interface: 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 Replication Manager. 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 CCI instances are necessary to execute Application Agent commands. We recommend that you manually start both the CCI instance that manages the primary volume and the instance that manages the secondary volume, prior to executing an Application Agent command. Only on the host where you execute the command, Application Agent automatically starts the instance when you execute the command, and automatically stops the instance when the command completes. You must start the following CCI instance manually prior to executing an Application Agent command: When you execute the command on the database server or file server: CCI instance that manages the secondary volume When you execute the command on the backup server: CCI instance that manages the primary volume Setting up Application Agent 4-29

110 Configuring a system to back up an SQL Server database The following items need to be considered to design a system to back up SQL Server database using Application Agent: All databases that coexist on a volume must be backed up simultaneously. Store each database in an appropriate volume to meet your backup plan. Due to the VDI quiesce operation, the drmsqlbackup command can only back up 64 databases in a single invocation. Use the drmsqlbackup command multiple times if you need to back up more than 64 databases. For information on requirements and precautions for backing up SQL Server databases or restoring an SQL Server database to an alternate location, see the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. Configuring a system to create Exchange Server database replicas This section includes important information on creating Exchange Server database replicas using Application Agent. For additional information, see the requirements and precautions for backing up Exchange databases in the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. Installing the Exchange management tool Install the Exchange management tool on the database and backup servers. (Ensure the same version is installed on both servers.) Refer to the Exchange Server documentation for more details. Using the ESEUTIL command If you perform either of the following operations using the ESEUTIL command, the electronic signature of the database is changed: Restoration of information store (ESEUTIL /p) Defragmentation (ESEUTIL /d) As a result, roll forward restoration is not available for replicas that created before the operation. To correct this problem, you must recreate the Exchange database replica using the Create Replica Wizard. 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 Setting up Application Agent

111 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. 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-31 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 virtual- Setting up Application Agent 4-31

112 server-name") Do While oexec.status = 0 Set owait = WshShell.Exec("timeout /t 1") Loop Resource.LogInformation "Exiting Online" End Function Function Offline( ) 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 Unsupported cluster configuration Application Agent supports operation-standby or mutual-standby cluster configurations. However, the following configuration is not available: One node of the cluster configuration is assigned as file server or database server, and the other node is assigned as backup server. For details about operation-standby or mutual-standby cluster configurations, refer to the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. Creating SQL Server replicas in a cluster configuration Note the following: Do not register multiple resources of SQL Server instances in a cluster group. In a cluster configuration, the owner of backup target database must a domain user that is recognized by both nodes. A local user of a node is not handled the same as a user of another node (even if the user name and password are identical). If the cluster system fails over to a node that does not recognize the owner, database backup fails. Install the SQL Server instance as a failover cluster. Creating Exchange Server replicas in a cluster configuration Note the following: 4-32 Setting up Application Agent

113 Do not register multiple instances of Exchange resources in a cluster group. If you restore a backup to a node other than the one where it was created, the Exchange virtual server that uses the same shared drive must be running. Exchange Server 2007 in Windows Server Failover Clustering When you back up the database, all Exchange System Attendant and Exchange Information Store resources belonging to the cluster resource group must be online. If the resources are offline, the drmexgbackup or EX_DRM_EXG_BACKUP commands will terminate with an error. Do not apply a setting that takes an Exchange Information Store resource offline when the relevant cluster resource goes offline. Requirements and precautions for volume configurations This module describes the requirements and precautions for volume configurations when Application Agent is used: Requirements for unmounting and mounting volumes on page 4-33 Requirements for backing up and restoring volumes on page 4-34 Precautions when changing a volume configuration on page 4-35 Precautions for disk partition styles on page 4-36 Requirements for unmounting and mounting volumes When executing backup and restoration of file systems and databases, Application Agent mounts and unmounts the necessary volumes. The mount point directory name and path are dependent on the limitation for the CCI mount or unmount functionality: When performing a disk backup: The limitation applies to the length of the path where the primary volume has been mounted (for which cold backup operations are to be performed). When backing up to tape: The limitation applies to the length of the path for the mounted volume. (This limitation also applies to the length of the path for the secondary volume.) The limitations on folder names are the same as for Windows (no null characters). One mount point can be specified for each logical volume. Do not define the following as copy groups, and do not specify them as backup targets: directories at a directory mount point, or volumes mounted to a drive. We recommend that you create directory mount points for backup targets on the same directory level (to make them easier to manage). Setting up Application Agent 4-33

114 The following shows a configuration example of a mounted directory that is a suitable backup target. Data files and log files are mounted to a directory and specified as backup targets. Figure 4-1 Example of a suitable backup target (mounted directory) The following shows a configuration example of a mounted directory that is not a suitable backup target. When the configuration places a mount point directory on a directory below a volume, higher-level volumes that contain mounted volumes cannot be specified as a backup target. Figure 4-2 Example of an unsuitable backup target Requirements for backing up and restoring volumes Do not use any functions for expanding or reducing the capacity of a logical volume. If you use such functions, Application Agent will not perform backup and restoration correctly. This is because the number of physical volumes that make up the logical volume changes according to the change in capacity of the logical volume. Application Agent checks whether the configuration of logical volumes has been changed and, if changed, restoration terminates with an error. If the volumes to be processed by Application Agent contain an LDEV for which a mode other than the normal mode is specified for the access level 4-34 Setting up Application Agent

115 by using Data Retention Utility, neither a backup nor a restoration can be performed. Do not perform a backup to the primary volume for which the shadow copy functionality for the Windows shared folder is enabled or to the primary volume that was specified as a storage area for shadow copy. If backup is performed to these volumes, data consistency cannot be guaranteed. Allocate database files and file systems that are not subject to backup and restoration so that they are not included on the same disk as those that are subject to backup and restoration. Allocate database files and file systems that are backed up simultaneously but can be restored separately so that they are not included on the same disk as those that are subject to backup and restoration. Precautions when changing a volume configuration If the following operations or changes are performed on a logical volume manager that is a backup operation target, or on a file system or CCI configuration definition file (horcmn.conf), then update the dictionary map files before executing the backup: A new file system was mounted on a directory under the file system. A file system was unmounted. A file system was moved to another directory and mounted. A change was made in the CCI configuration definition file (horcmn.conf), such as adding or deleting a pair volume. Note: If you execute backup without updating the dictionary map files, a system inconsistency might occur. To update the dictionary map files, use the drmfsdisplay, drmsqldisplay, or drmexgdisplay commands. For details about how to use these commands, see the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. If you made changes to a configuration involving an update of the dictionary map files, to restore the data backed up before the change to a file server or database server, first restore the configuration for the logical volume manager and file system to the state that was in place at the time the backup was created, and then perform restoration. If you perform restoration incorrectly, a system inconsistency might occur. To review the configuration that was in place at the time the backup was created, use the drmfscat, drmsqlcat, or drmexgcat command. For details about how to use these commands, see Hitachi Command Suite Replication Manager Application Agent CLI User Guide. For details about restoration when a physical volume is replaced, see the section that mentions about replacing primary and secondary volume disks while Application Agent is running in the Hitachi Command Suite Replication Manager Application Agent CLI User Guide. Setting up Application Agent 4-35

116 Precautions for disk partition styles After performing a backup, disk partition styles cannot be modified. When replacing a disk, the new disk must have the same partition style as when the backup was performed. If the partition style was changed after the backup was performed, and you execute the restore command (drmfsrestore, drmsqlrestore, or drmexgrestore), or you execute the drmdevctl command with either the -sigview or -sigset option, the operation might end with an error. In this case, change the partition style to the one in use when the backup was performed. When the backup target is being managed in a cluster configuration, the disk signatures for the primary and secondary volumes must be the same as when the backup was performed. To view the original backup signatures, execute the drmdevctl command with the proper backup ID and the -sigview option. 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 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 * number-of-application-agent instances Database log size = current-file-capacity * number-of-application- Agent instances Application status log size = current-file-capacity * number-of- Application-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 4-36 Setting up Application Agent

117 For 64-bit Windows: %ProgramFiles(x86)%\HDVM\HBaseAgent\config\server.properties 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 Port number for the Common agent daemon process (service). server.http.port Port number for the communication between the Common agent daemon process and the web server process. server.http.localport Port number for Common agent Web server. Note the following: Acceptable port number values are 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. Creating file system replicas For important information on creating file system replicas using Application Agent, see the requirements and precautions for backing up file systems in Hitachi Command Suite Replication Manager Application Agent CLI User Guide. 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 Setting up Application Agent 4-37

118 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: 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-39 for a description of the types and Table 4-20 Logged values on page 4-39 for a list of types logged for each level. These values can be entered in any combination of upper and lower case Setting up Application Agent

119 Property agent.logger.maxbackupindex agent.logger.maxfilesize Default value: INFO Description 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 The maximum size of a single Replication Manager log file. This value must be specified in bytes, kilobytes, or megabytes. If the specified value is not followed by KB or MB, the size is assumed to be in bytes. Specifiable values are determined by the specified unit as follows: Bytes: to KB: 512K B to KB MB: 1 MB to 32 MB Default value: 5 MB Table 4-19 Error values and descriptions Type Description DEBUG INFO WARN ERROR FATAL Detailed information for the purpose of debugging. Information for the purpose of tracing the process flow. Messages that are raised when there are some limitations but the process execution continues. Error occurred during the process execution or startup. Fatal exception occurred in the code and the execution stops. Table 4-20 Logged values Values Logged INFO DEBUG WARN ERROR FATAL DEBUG X INFO WARN X X ERROR X X X FATAL X X X X Setting up Application Agent 4-39

120 4-40 Setting up Application Agent

121 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 Operating the management server 5-1

122 About executing commands on the management server User permissions This section includes information related to the execution of commands that are required for Replication Manager operation. 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 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 Operating the management server

123 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. In Windows Server 2012: 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. 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 > Stop - HCS. In Windows Server 2012: Select All Apps from the Start menu, then select Hitachi Command Suite > Manage Services > Stop - HCS. b. Using the command line: Common-Component-installation-folder\bin\hcmds64srv /stop Operating the management server 5-3

124 In Linux 1. Log in as root user. 2. Execute the following command: 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. 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 > Status - HCS. In Windows Server 2012: Select All Apps from the Start menu, then select Hitachi Command Suite > Manage Services > Status - HCS. b. Using the command line: Common-Component-installation-folder\bin\hcmds64srv /status In Linux 1. Log in as root user. 2. Execute the following command: Common-Component-installation-directory/bin/hcmds64srv -status Example 1: Execution results if Replication Manager is running KAPM05007-I Already started service. service-name=hbase 64 Storage Mgmt Web Service KAPM05007-I Already started service. service-name=hbase 64 Storage Mgmt Web SSO Service KAPM05007-I Already started service. service-name=hbase 64 Storage Mgmt SSO Service KAPM05007-I Already started service. service-name=hcs Device Manager Web Service KAPM05007-I Already started service. service-name=hbase 64 Storage Mgmt Common Service KAPM05007-I Already started service. service-name=device Manager Server Service KAPM05007-I Already started service. service-name=tiered Storage Manager Server Service 5-4 Operating the management server

125 Example 2: Execution results if Replication Manager has stopped KAPM05009-I Already stopped service. service-name=hbase 64 Storage Mgmt Web Service KAPM05009-I Already stopped service. service-name=hbase 64 Storage Mgmt Web SSO Service KAPM05009-I Already stopped service. service-name=hbase 64 Storage Mgmt SSO Service KAPM05009-I Already stopped service. service-name=hcs Device Manager Web Service KAPM05009-I Already stopped service. service-name=hbase 64 Storage Mgmt Common Service KAPM05009-I Already stopped service. service-name=device Manager Server Service KAPM05009-I Already stopped service. service-name=tiered Storage Manager Server Service If you execute the command as described above, you can also check whether the HiRDB service is running. If it is running, the following message appears in the execution results: KAPM06440-I The HiRDB service has already started. 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 Operating the management server 5-5

126 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 Property Default value (unit) logger.properties logger.loglevel 20 logger.sysloglevel 0 logger.maxbackupindex logger.maxfilesize 6 (files) 20MB logger.db.loglevel 20 logger.db.maxbackupindex 6 logger.db.maxfilesize logger.refreshconfig.enabled logger.refreshconfig.maxbackupindex logger.refreshconfig.maxfilesize logger.useroperation.enabled logger.useroperation.maxbackupindex logger.useroperation.maxfilesize logger.refreshstatus.enabled logger.refreshstatus.maxbackupindex logger.refreshstatus.maxfilesize logger.appconfig.maxbackupindex 20MB true 3 (files) 10MB true 5 (files) 10MB true 2 (files) 10MB 3 (files) 5-6 Operating the management server

127 File Property Default value (unit) serverstorageif.propert ies logger.appconfig.maxfilesize logger.appconfig.enabled logger.appstatus.maxbackupindex logger.appstatus.maxfilesize logger.appstatus.enabled 10 (MB) true 6 (files) 20 (MB) true ssif.sockettimeout 3600 (seconds) ssif.socketconnecttimeout 5 (seconds) ssif.alerttimeout 1800 (seconds) bcmif.properties bcmif.sockettimeout 3600 (seconds) bcmif.socketconnecttimeout bcmif.reconnectioninterval bcmif.reconnectioncount 5 (seconds) 60 (seconds) 5 (times) agentif.properties agentif.connecttimeout 30 (seconds) agentif.responsetimeout 3600 (seconds) hdvmagtif.connecttimeout 30 (seconds) hdvmagtif.responsetimeout 3600 (seconds) hdvmagtif.maxpollingcount hdvmagtif.pollinginterval 50 (times) 30 (seconds) appagentif.properties appagentif.connecttimeout 30 (seconds) appagentif.responsetimeout 3600 (seconds) base.properties base.operationmode.forcemaintenancemo de false base.pair.udpport.startnumber 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 base.alert.automarking 0 (times) true Operating the management server 5-7

128 File Property Default value (unit) base.refreshdginfo.exec 1 base.repositry.synchronize.interval base.repositry.synchrocheck.interval 10 (minutes) 10 (minutes) base.rmi.port base.rmi.backlog 100 base.taskschedule.threadmax 10 base.refreshstorage.polling.timeout base.pair.performance.interval 60 minutes 1 minute base.pair.performance.aggregate 5 base.vmhost.enabled true RpMCLI.properties RpMCLI.diaglevel INFO RpMTaskCLI.MaxBackupIndex RpMTaskCLI.MaxFileSize 6 (files) 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 KB: 4 KB to KB MB: 1 MB to 2047 MB Table 5-2 List of properties in the logger.properties file logger.loglevel logger.sysloglevel Property 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 The threshold value for the output level of the OS event log or syslog that is output 5-8 Operating the management server

129 Property logger.maxbackupindex logger.maxfilesize logger.db.loglevel logger.db.maxbackupindex logger.db.maxfilesize logger.refreshconfig.enabled logger.refreshconfig.maxbackupindex logger.refreshconfig.maxfilesize logger.useroperation.enabled Description using Replication Manager. Messages containing values that are equal to or less than this value are output to the log file. Specifiable values: 0, 10, 20, and 30 (in decreasing order of importance from left to right). Default value: 0 The maximum number of log files created in Replication Manager. When the number of log files reaches this value, the existing files are reused, starting with the oldest file. Specifiable values: 1 to 16 (files) Default value: 6 The maximum size of a single Replication Manager log file. Default value: 20MB Threshold value for output of a databaserelated log file. Specifiable values: 0, 10, 20, and 30 (in decreasing order of importance from left to right). Default value: 20 Maximum number of backup files for a database-related log file. Specifiable values: 1 to 16 (files) Default value: 9 Maximum size of a database-related log file. Default value: 20 MB Enabling or disabling of the configuration update logging function. Specifiable values: true or false Default value: true Maximum number of backup files for a configuration update log file. Specifiable values: 1 to 32 (files) Default value: 5 Maximum size of a configuration update log file. Default value: 10 MB Enabling or disabling of the user operation logging function. Specifiable values: true or false Default value: true Operating the management server 5-9

130 Property logger.useroperation.maxbackupindex logger.useroperation.maxfilesize logger.refreshstatus.enabled logger.refreshstatus.maxbackupindex logger.refreshstatus.maxfilesize logger.appconfig.maxbackupindex logger.appconfig.maxfilesize logger.appconfig.enabled logger.appstatus.maxbackupindex logger.appstatus.maxfilesize logger.appstatus.enabled Description Maximum number of backup files for a user operation log file. Specifiable values: 1 to 32 (files) Default value: 5 Maximum size of a user operation log file. Default value: 10 MB Enabling or disabling of the pair status update logging function. Specifiable values: true or false Default value: true Maximum number of backup files for a pair status update log file. Specifiable values: 1 to 32 (files) Default value: 2 Maximum size of a pair status update log file. Default value: 10 MB Maximum number of application configuration log backup files. Specifiable values: 1-32 (files). Default value: 3 Maximum size of the application configuration log file. Specifiable values: (MB). Default value: 10 Log function on/off switch for the application configuration log. Specifiable values: true or false. Default value: true Maximum number of the application status log backup files. Specifiable values: 1-32 (files). Default value: 6 Maximum size of the application status log file Specifiable values: 1 to 2047 (MB). Default value: 20 Log function on/off switch for the application status log. Specifiable values: true or false. Default value: true 5-10 Operating the management server

131 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 Trace log Database log Configuration update log Transmission logs User operations log Pair status update log Small Medium Large 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 (seconds) Default value: 3600 Operating the management server 5-11

132 Property ssif.socketconnectti meout ssif.alerttimeout Description The amount of time Replication Manager waits to connect to Device Manager server. If 0 is specified, Replication Manager waits until a connection is established without timing out. Specifiable values: 0 to 3600 (seconds) Default value: 5 The amount of time Replication Manager waits to issue an alert message query to Device Manager server. Specifiable values: 1 to 3600 (seconds) 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 bcmif.socketconnecttimeout bcmif.reconnectioninterval bcmif.reconnectioncount 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. Specifiable values: 0 to (seconds) Default value: 3600 The amount of time Replication Manager waits to connect to Business Continuity Manager or Mainframe Agent. If 0 is specified, Replication Manager waits until a connection is established without timing out. Specifiable values: 0 to 3600 (seconds) Default value: 5 The 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. Specifiable values: 0 to 1800 (seconds) Default value: 60 The number of retries attempted when Replication Manager cannot establish a connection with Business 5-12 Operating the management server

133 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 agentif.responsetimeout hdvmagtif.connecttimeout hdvmagtif.responsetimeout hdvmagtif.maxpollingcount Description The amount of time Replication Manager waits to connect to a Device Manager Agent when collecting copy pair statuses. If 0 is specified, Replication Manager waits until a connection is established without timing out. Specifiable values: 0 to 3600 (seconds) Default value: 30 The amount of time Replication Manager waits to 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. Specifiable values: 0 to (seconds) Default value: 3600 The amount of time Replication Manager waits to 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. Specifiable values: 0 to 3600 (seconds) Default value: 30 The amount of time Replication Manager waits to 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. Specifiable values: 0 to (seconds) Default value: 3600 The maximum number of times that Replication Manager checks the processing status of a Device Operating the management server 5-13

134 Property hdvmagtif.pollinginterval 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. Specifiable values: 0 to 100 (times) Default value: 50 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. Specifiable values: 5 to 1200 (seconds) 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 appagentif.responsetimeout Description The amount of time Replication Manager waits to connect to an Application Agent when collecting configuration statuses. If 0 is specified, Replication Manager waits until a connection is established without timing out. Specifiable values: 0 to 3600 (seconds) Default value: 30 The amount of time Replication Manager waits to 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. Specifiable values: 0 to (seconds) 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 Operating the management server

135 Table 5-8 List of properties in the base.properties file Property base.operationmode. forcemaintenancemod e base.pair.udpport.s tartnumber base.refreshhdvminf o.threads base.repositry.sync hronize.polling base.taskscheck.int erval base.taskscheck.max count base.taskscheck.mf. interval base.taskscheck.mf. maxcount base.repositry.sync hronize.interval Description Specifies to start Replication Manager in maintenance mode regardless of the current operation mode. If true is specified, Replication Manager starts with maintenance mode when the server services are started or restarted. If false, Replication Manager starts with the current operation mode when the server services are started or restarted. Specifiable values: true or false Default value: false The starting UDP port number used for communication between CCI instances. Specifiable values: 0 to Default value: Number of simultaneous threads used to acquire configuration information from remote Device Manager. Specifiable values: 1 to 4 Default value: 2 Specifies whether Replication Manager automatically 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. Specifiable values: true or false Default value: true The interval at which Replication Manager checks whether a task related to a copy pair operation has finished. Specifiable values: 30 to 3600 (seconds) Default value: 120 The maximum number of times that Replication Manager checks whether a task related to a copy pair operation has finished. If 0 is specified, there is no limit. Specifiable values: 0 to 100 (times) Default value: 0 The interval at which Replication Manager checks whether a task related to a mainframe copy pair operation has finished. Specifiable values: 30 to 3600 (seconds) Default value: 120 The maximum number of times that Replication Manager checks whether a task related to a mainframe copy pair operation has finished. If 0 is specified, there is no limit. Specifiable values: 0 to 100 (times) Default value: 0 The interval at which the HDvM (Hitachi Device Manager) database synchronization function performs a check. Specifiable values: 10 to 1440 (minutes) Operating the management server 5-15

136 Property base.repository.syn chrocheck.interval base.refreshdginfo. exec base.alert.automark ing base.rmi.port Default value: 10 Description The interval at which Replication Manager automatically checks 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 This property specifies whether to acquire definition information 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 This property specifies whether Replication Manager 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 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, the Replication tab of Device Manager, or you manage tasks created by Automation Director using Replication Manager. 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 Command Suite Administrator Guide or the Hitachi Command Suite Automation Director Installation and Configuration Guide. Values that can be specified: Default value: base.rmi.enabled If Replication Manager version is earlier than v8.2.1: This property specifies whether the RMI registry is started. You must set this property to true if you use the Replication tab of Device Manager or you manage tasks created by Automation Director using Replication Manager. Specifiable values: true or false Default value: true If Replication Manager version is v8.2.1 or later: This property is disabled. The RMI registry is always started regardless of the value of this property Operating the management server

137 Property base.rmi.backlog base.taskschedule.t hreadmax base.refreshstorage.polling.timeout base.pair.performan ce.interval base.pair.performan ce.aggregate base.vmhost.enabled Description This property specifies the maximum number of requests Replication Manager can receive. You must specify this property if you use the Replication Manager CLI, the Replication tab of Device Manager, or you manage tasks created by Automation Director using Replication Manager. A value of zero (0) sets the value to the Java default value (50). Values that can be specified: Default value: 100 This property specifies the maximum number of tasks Replication Manager can execute concurrently. Values that can be specified: Default value: 10 This property specifies the length of time Replication Manager waits for a Device Manager server refresh of storage system information. Values that can be specified: Default value: 60 This property specifies the interval of copy pair performance 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 This property specifies the aggregate value of C/T delta. Values that can be specified: 1-60 Default value: 5 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 after you change the value of this property. Specifiable values: true or false 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. Operating the management server 5-17

138 Property RpMTaskCLI.MaxBacku pindex RpMTaskCLI.MaxFileS ize Default value: INFO Description 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. This property specifies the maximum number of trace log files (RpMTaskCLIn.log), which are created when the GetTasks or ExecuteTask command is executed. If a new log file is required when the number of log files has been reached this value, the oldest log file is overwritten. Values that can be specified: 1-16 (files) Default value: 6 This property specifies the maximum size of a trace log file, which are created when the GetTasks or ExecuteTask command is executed. Values that can be specified: 1-20 (MB) Default value: Operating the management server

139 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

140 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

141 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

142 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: 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 6-4 Security management

143 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

144 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: 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 Replication Manager. 6-6 Security management

145 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

146 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: Importing a server certificate into the truststore of Hitachi Command Suite Checking the server certificates imported into the truststore of Hitachi Command Suite 6-8 Security management

147 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 Administrator Guide. Each audit event is assigned a severity level. You can filter audit log data to be output according to the severity levels of events. Table 6-1 Audit events for the ConfigurationAccess category Description of category Resource group creation (GUI) Resource group creation (GUI or CLI) Resource group deletion (GUI) Resource group deletion (GUI or CLI) Editing of resource group properties (GUI) Editing of resource group Audit event Severity Message ID Successful resource group creation 6 KAPM02630-I Failed resource group creation 3 KAPM02635-E Successful resource group creation 6 KAPM02670-I KAPM07257-I Failed resource group creation 3 KAPM02675-E KAPM07258-E Successful resource group deletion 6 KAPM02631-I Failed resource group deletion 3 KAPM02636-E Successful resource group deletion 6 KAPM02671-I KAPM07259-I Failed resource group deletion 3 KAPM02676-E KAPM07260-E Successful resource group property editing 6 KAPM02634-I Failed resource group property editing 3 KAPM02639-E Successful resource group property editing 6 KAPM02674-I KAPM07261-I Security management 6-9

148 Description of category properties (GUI or CLI) Addition of a user to a resource group (GUI) Removing of a user from a resource group (GUI) Assignment of a user to a resource group (GUI or CLI) Audit event Severity Message ID Failed resource group property editing 3 KAPM02679-E KAPM07262-E Successful user addition to a resource group 6 KAPM02632-I Failed user addition to a resource group 3 KAPM02637-E Successful user removal from a resource group 6 KAPM02633-I Failed user removal from a resource group 3 KAPM02638-E 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. The pair operation task (node addition or deletion) has started. The pair operation task (node addition or deletion) was successful. The pair operation task (pair create, delete, modify, or edit group name) was successful. The pair operation task (pair create, delete, or modify) timed out. (The command was executed successfully, but whether the pair status was changed correctly could not be confirmed.) 6 KAVN10001-I KAVN10006-I KAVN10010-I KAVN10089-I 6 KAVN10085-I KAVN10087-I 6 KAVN10086-I KAVN10088-I 6 KAVN10002-I KAVN10007-I KAVN10011-I KAVN10090-I 4 KAVN10003-W KAVN10008-W KAVN10030-W The pair operation task has failed. 3 KAVN10009-E Failed to update the configuration definition file after deleting the pair. Editing or distribution of the disk configuration definition file has started. The disk configuration definition file was successfully edited or distributed. An attempt to edit or distribute the disk configuration definition file has failed. 4 KAVN10004-W KAVN10005-W 6 KAVN10015-I KAVN10021-I 6 KAVN10016-I KAVN10022-I 3 KAVN10014-E KAVN10017-E KAVN10020-E KAVN10023-E 6-10 Security management

149 Description of category Audit event Severity Message ID Editing or distribution of the copy group configuration definition file has started. The copy group configuration definition file was successfully edited or distributed. An attempt to edit or distribute the copy group configuration definition file has failed. 6 KAVN10024-I KAVN10028-I 6 KAVN10025-I KAVN10029-I 3 KAVN10009-E Management host change operation Secondary volume hiding operation 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 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. Canceling of a secondary volume hiding operation completed. 6 KAVN10076-I KAVN10082-I 6 KAVN10077-I KAVN10083-I Canceling of a secondary volume hiding operation failed. 3 KAVN10078-E KAVN10084-E Replica operation Creation, editing, execution, canceling, or deletion of a task has started. Creation, editing, execution, canceling, or deletion of a task has succeeded. Creation, editing, execution, canceling, or deletion of a task has failed. 6 KAVN10031-I KAVN10034-I KAVN10037-I KAVN10040-I KAVN10043-I 6 KAVN10032-I KAVN10035-I KAVN10038-I KAVN10041-I KAVN10044-I 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

150 Description of category Audit event Severity Message ID Mounting or unmounting has succeeded. 6 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 KAVN10054-W KAVN10066-W Take back operation has started. 6 KAVN10058-I KAVN10061-I Take back operation is terminated. 6 KAVN10059-I KAVN10062-I Take back operation timed out. (The command execution was successful, but completion could not be confirmed.) 4 KAVN10060-W KAVN10063-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 6-12 Security management

151 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

152 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

Hitachi Command Suite

Hitachi Command Suite Hitachi Command Suite Installation and Configuration Guide MK-90HC173-23 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any

More information

Hitachi Command Suite

Hitachi Command Suite Hitachi Command Suite Virtual Appliance Installation Guide MK-92HC236-01 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means,

More information

Hitachi Converged Adapter 2.0 for VMware vcenter Operations HCA for vc OPs Third-Party Copyrights and Licenses

Hitachi Converged Adapter 2.0 for VMware vcenter Operations HCA for vc OPs Third-Party Copyrights and Licenses Hitachi Converged Adapter 2.0 for VMware vcenter Operations 5.8.4 MK-92UCP065-02 2014-2016 Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Thin Image. User Guide. Hitachi Virtual Storage Platform G200, G400, G600, G800. Hitachi Virtual Storage Platform F400, F600, F800

Hitachi Thin Image. User Guide. Hitachi Virtual Storage Platform G200, G400, G600, G800. Hitachi Virtual Storage Platform F400, F600, F800 Hitachi Thin Image User Guide Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform F400, F600, F800 Hitachi Virtual Storage Platform G1000 MK-92RD8011-08 May 2016 2014,

More information

Hitachi TrueCopy. User Guide. Hitachi Virtual Storage Platform G1000 and G1500. Hitachi Virtual Storage Platform F1500

Hitachi TrueCopy. User Guide. Hitachi Virtual Storage Platform G1000 and G1500. Hitachi Virtual Storage Platform F1500 Hitachi TrueCopy User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform

More information

Hitachi Universal Replicator

Hitachi Universal Replicator Hitachi Universal Replicator User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage

More information

Hitachi Command Suite

Hitachi Command Suite Hitachi Command Suite 8.6 Virtual Appliance Installation Guide This manual explains how to use the virtual appliance for Hitachi Command. MK-92HC236-02 May 2018 2016, 2018 Hitachi, Ltd. All rights reserved.

More information

Hitachi Virtual Storage Platform G series and F series

Hitachi Virtual Storage Platform G series and F series Hitachi Virtual Storage Platform G series and F series SVOS 7.3 Thin Image User Guide This document describes and provides instructions for using Hitachi Thin Image to plan, configure, and perform pair

More information

Performance Guide. Hitachi Performance Guide for Gx00 and Fx00 Models

Performance Guide. Hitachi Performance Guide for Gx00 and Fx00 Models Performance Guide Hitachi Performance Guide for Gx00 and Fx00 Models Hitachi Performance Monitor Hitachi Server Priority Manager Hitachi Virtual Partition Manager Product Version Getting Help Contents

More information

Hitachi Thin Image. User Guide. Hitachi Virtual Storage Platform G1000 and G1500. Hitachi Virtual Storage Platform F1500

Hitachi Thin Image. User Guide. Hitachi Virtual Storage Platform G1000 and G1500. Hitachi Virtual Storage Platform F1500 Hitachi Thin Image User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform

More information

Hitachi Universal Replicator for Mainframe

Hitachi Universal Replicator for Mainframe Hitachi Universal Replicator for Mainframe User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8022-11 October 2016 2014, 2016 Hitachi, Ltd. All rights

More information

Hitachi Universal Replicator for Mainframe

Hitachi Universal Replicator for Mainframe Hitachi Universal Replicator for Mainframe User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8022-12 March 2017 2014, 2017 Hitachi, Ltd. All rights

More information

Hitachi Command Suite

Hitachi Command Suite Hitachi Command Suite Installation and Configuration Guide MK-90HC173-22 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any

More information

Hitachi Converged Adapter 2.0 for Microsoft SCOM 2012 Administration Manual HCA for SCOM Administration Manual

Hitachi Converged Adapter 2.0 for Microsoft SCOM 2012 Administration Manual HCA for SCOM Administration Manual Hitachi Converged Adapter 2.0 for Microsoft SCOM 2012 Administration Manual MK-92UCP082-01 2014-2016 Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced

More information

Hitachi SNMP Agent. User Guide. Hitachi Virtual Storage Platform G200, G400, G600, G800. Hitachi Virtual Storage Platform F400, F600, F800

Hitachi SNMP Agent. User Guide. Hitachi Virtual Storage Platform G200, G400, G600, G800. Hitachi Virtual Storage Platform F400, F600, F800 Hitachi SNMP Agent User Guide Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform F400, F600, F800 MK-94HM8015-05 October 2016 2015, 2016 Hitachi, Ltd. All rights reserved.

More information

Hitachi WAN Optimizer VMware vsphere Setup Guide

Hitachi WAN Optimizer VMware vsphere Setup Guide Hitachi WAN Optimizer VMware vsphere Setup Guide FASTFIND LINKS Contents Product Version Getting Help MK-95HWO002-00 July 2016 2007, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Hitachi Adapter for Oracle Enterprise Manager - Database Cloning

Hitachi Adapter for Oracle Enterprise Manager - Database Cloning Hitachi Adapter for Oracle Enterprise Manager - Database Cloning v02.0.0 Release Notes Contents About This Document... 2 Intended Audience... 2 Getting Help... 2 About This Release... 2 Hardware Requirements...

More information

Hitachi Hyper Scale-Out Platform (HSP) Hortonworks Ambari VM Quick Reference Guide

Hitachi Hyper Scale-Out Platform (HSP) Hortonworks Ambari VM Quick Reference Guide Hitachi Hyper Scale-Out Platform (HSP) MK-95HSP013-03 14 October 2016 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic

More information

Hitachi Storage Adapter for the SAP HANA Cockpit

Hitachi Storage Adapter for the SAP HANA Cockpit Hitachi Storage Adapter for the SAP HANA Cockpit v01.1.0 Release Notes Contents About this Document... 2 Intended Audience... 2 Getting Help... 2 About Release v1.1.0... 2 Hardware and Software... 3 Hardware

More information

Hitachi Dynamic Link Manager (for VMware ) Release Notes

Hitachi Dynamic Link Manager (for VMware ) Release Notes Hitachi Dynamic Link Manager (for VMware ) 8.6.0-00 Release Notes Contents About this document... 1 Intended audience... 2 Accessing product downloads... 2 Getting help... 2 About this release... 2 Product

More information

Hitachi Storage Adapter for Microsoft System Center Virtual Machine Manager

Hitachi Storage Adapter for Microsoft System Center Virtual Machine Manager Hitachi Storage Adapter for Microsoft System Center Virtual Machine Manager v01.3.0 Release Notes Contents About This Document... 2 Intended Audience... 2 Getting Help... 2 Hardware Requirements... 3 Volume

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi TrueCopy User Guide Product Version Getting Help Contents MK-92RD8019-09 May 2016 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Nondisruptive Migration

Nondisruptive Migration Nondisruptive Migration User Guide Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform G1000, G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8086-06 2015, 2016

More information

Hitachi Command Suite. Automation Director. Messages MK-92HC221-02

Hitachi Command Suite. Automation Director. Messages MK-92HC221-02 Hitachi Command Suite Automation Director Messages MK92HC22102 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic

More information

Hitachi Data Ingestor

Hitachi Data Ingestor Hitachi Data Ingestor 6.4.0 Backup Restore Features Supplement for Hitachi Data Protection Suite This document describes the instructions for setting up an HDI environment to work with Hitachi Data Protection

More information

Nondisruptive Migration Hitachi Virtual Storage Platform F series and G series

Nondisruptive Migration Hitachi Virtual Storage Platform F series and G series Nondisruptive Migration Hitachi Virtual Storage Platform F series and G series User Guide This guide describes Hitachi Command Suite (HCS) nondisruptive migration and provides instructions for using nondisruptive

More information

Hitachi ShadowImage for Mainframe

Hitachi ShadowImage for Mainframe Hitachi ShadowImage for Mainframe User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8020-11 March 2017 2014, 2017 Hitachi, Ltd. All rights reserved.

More information

Replication Manager. Hitachi Command Suite. Application Agent CLI Reference Guide MK-90HC Document Organization. Product Version.

Replication Manager. Hitachi Command Suite. Application Agent CLI Reference Guide MK-90HC Document Organization. Product Version. Hitachi Command Suite Replication Manager Application Agent CLI Reference Guide Document Organization Product Version Getting Help Contents MK-90HC181-15 2014, 2015 Hitachi, Ltd. All rights reserved. No

More information

Hitachi Command Suite. Global Link Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC214-06

Hitachi Command Suite. Global Link Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC214-06 Hitachi Command Suite Global Link Manager User Guide Document Organization Product Version Getting Help Contents MK-92HC214-06 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Hitachi Command Suite. Global Link Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC214-05

Hitachi Command Suite. Global Link Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC214-05 Hitachi Command Suite Global Link Manager User Guide Document Organization Product Version Getting Help Contents MK-92HC214-05 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Hitachi Compatible FlashCopy

Hitachi Compatible FlashCopy Hitachi Compatible FlashCopy User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8010-10 March 2017 2014, 2017 Hitachi, Ltd. All rights reserved. No

More information

Hitachi Command Suite. Tuning Manager. Installation Guide. Document Organization. Product Version. Getting Help. Contents MK-96HC141-32

Hitachi Command Suite. Tuning Manager. Installation Guide. Document Organization. Product Version. Getting Help. Contents MK-96HC141-32 Hitachi Command Suite Tuning Manager Installation Guide Document Organization Product Version Getting Help Contents MK-96HC141-32 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Hitachi Data Instance Director Version 6.0

Hitachi Data Instance Director Version 6.0 Hitachi Data Instance Director Version 6.0 MS Exchange Server Application Guide MK-93HDID012-00 16th October 2017 2017 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or

More information

Hitachi Command Suite

Hitachi Command Suite Hitachi Command Suite Installation and Configuration Guide MK-90HC173-20 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any

More information

Hitachi Data Ingestor Hyper-V Installation Guide 6.0.0

Hitachi Data Ingestor Hyper-V Installation Guide 6.0.0 Hitachi Data Ingestor Hyper-V Installation Guide 6.0.0 This guide provides instructions for installing Hitachi Data Ingestor (HDI) on Hyper-V. Instances of HDI installed on Hyper-V are referred to as VMA.

More information

Hitachi Data Ingestor

Hitachi Data Ingestor Hitachi Data Ingestor Backup Restore Features Supplement for Hitachi Data Protection Suite Product Version Getting Help Contents MK-90HDICOM009-03 2010-2016 Hitachi, Ltd. All rights reserved. No part of

More information

Hitachi Virtual Storage Platform G series and F series SVOS 7.3.1

Hitachi Virtual Storage Platform G series and F series SVOS 7.3.1 Hitachi Virtual Storage Platform G series and F series SVOS 7.3.1 Encryption License Key User Guide This document describes and provides instructions for Encryption License Key, a feature of the VSP G

More information

Global Link Manager. Hitachi Command Suite. Installation and Configuration Guide MK-95HC Document Organization. Product Version.

Global Link Manager. Hitachi Command Suite. Installation and Configuration Guide MK-95HC Document Organization. Product Version. Hitachi Command Suite Global Link Manager Installation and Configuration Guide Document Organization Product Version Getting Help Contents MK-95HC107-18 2015 Hitachi, Ltd. All rights reserved. No part

More information

Hitachi Data Ingestor

Hitachi Data Ingestor Hitachi Data Ingestor Cluster Getting Started Guide Product Version Getting Help Contents MK-90HDICOM001-02 2010-2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or

More information

Hitachi Infrastructure Adapter for Microsoft System Center Operations Manager

Hitachi Infrastructure Adapter for Microsoft System Center Operations Manager Hitachi Infrastructure Adapter for Microsoft System Center Operations Manager v01.10.0 FASTFIND LINKS Contents Getting Help MK-92SCOM009-10 2012, 2016 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Data Instance Director Version 6.0

Hitachi Data Instance Director Version 6.0 Hitachi Data Instance Director Version 6.0 MS SQL Server Application Guide MK-93HDID011-00 16th October 2017 2017 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Mainframe Analytics Recorder v Release Notes

Mainframe Analytics Recorder v Release Notes Mainframe Analytics Recorder v8.2.1-00 Release Notes Contents About this document... 1 Intended audience... 1 Getting help... 2 About this release... 2 Product package contents... 2 New features and important

More information

Tuning Manager. Hitachi Command Suite. Getting Started Guide MK-96HC FASTFIND LINKS Document Organization. Product Version.

Tuning Manager. Hitachi Command Suite. Getting Started Guide MK-96HC FASTFIND LINKS Document Organization. Product Version. Hitachi Command Suite Tuning Manager Getting Started Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents MK-96HC120-23 2014, 2015 Hitachi, Ltd. All rights reserved No part

More information

Hitachi Virtual Storage Platform

Hitachi Virtual Storage Platform Hitachi Virtual Storage Platform Encryption License Key User Guide Document Organization Product Version Getting Help Contents MK-90RD7015-11 2010-2016 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Device Manager Mainframe Agent Release Notes Contents

Hitachi Device Manager Mainframe Agent Release Notes Contents Hitachi Device Manager Mainframe Agent 8.5.0-00 Release Notes Contents About this document... 2 Intended audience... 2 Getting help... 2 About this release... 2 Product package contents... 2 New features

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi Universal Replicator for Mainframe User Guide Product Version Getting Help Contents MK-92RD8022-10 June 2016 2014, 2016 Hitachi, Ltd. All rights reserved.

More information

Hitachi Command Suite. Automation Director. Installation and Configuration Guide MK-92HC204-02

Hitachi Command Suite. Automation Director. Installation and Configuration Guide MK-92HC204-02 Hitachi Command Suite Automation Director Installation and Configuration Guide MK-92HC204-02 2015 Hitachi, Ltd. All rights reserved No part of this publication may be reproduced or transmitted in any form

More information

Hitachi Dynamic Link Manager (for AIX) v Release Notes

Hitachi Dynamic Link Manager (for AIX) v Release Notes Hitachi Dynamic Link Manager (for AIX) v8.2.1-00 Release Notes Contents About this document... 1 Intended audience... 1 Getting help... 2 About this release... 2 Product package contents... 2 New features

More information

Hitachi Data Instance Director

Hitachi Data Instance Director Hitachi Data Instance Director Application Guide for protecting Microsoft SQL Server MK-93HDID008-00 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Storage Plug-in for VMware vcenter User's Guide Release v3.7.1

Hitachi Storage Plug-in for VMware vcenter User's Guide Release v3.7.1 Hitachi Storage Plug-in for VMware vcenter User's Guide Release v3.7.1 This guide explains how to install, configure and use Hitachi Storage Plug-in for VMware vcenter with supported Hitachi storage array

More information

Compute Systems Manager

Compute Systems Manager Hitachi Command Suite Compute Systems Manager User Guide MK-91HC194-14 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means,

More information

HCP Data Migrator Release Notes Release 6.1

HCP Data Migrator Release Notes Release 6.1 HCP Data Migrator Release Notes Release 6.1 Hitachi Content Platform Data Migrator RN-90ARC031-11 4 December 2017 2014, 2017 Hitachi Vantara Corporation. All rights reserved. No part of this publication

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Nondisruptive Migration User Guide MK-92RD8086-01 2015 Hitachi, Ltd All rights reserved No part of this publication may be reproduced or transmitted in any form or

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi ShadowImage for Mainframe User Guide Product Version Getting Help Contents MK-92RD8020-09 June 2016 2014, 2016 Hitachi, Ltd. All rights reserved. No part

More information

Hitachi Infrastructure Analytics Advisor. User Guide

Hitachi Infrastructure Analytics Advisor. User Guide Hitachi Infrastructure Analytics Advisor User Guide MK-96HIAA001-01 October 2016 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any

More information

Hitachi Command Suite. Dynamic Link Manager. (for VMware ) User Guide. Document Organization. Product Version. Getting Help. Contents MK-92DLM130-12

Hitachi Command Suite. Dynamic Link Manager. (for VMware ) User Guide. Document Organization. Product Version. Getting Help. Contents MK-92DLM130-12 Hitachi Command Suite Dynamic Link Manager (for VMware ) User Guide Document Organization Product Version Getting Help Contents MK-92DLM130-12 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi Compatible FlashCopy User Guide FASTFIND LINKS Contents Product Version Getting Help MK-92RD8010-02 2014 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Business Continuity Manager

Hitachi Business Continuity Manager Hitachi Business Continuity Manager Installation Guide Document Organization Product Version Getting Help Contents MK-95HC104-25 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Unified Compute Platform 4.1.2

Unified Compute Platform 4.1.2 Unified Compute Platform 4.1.2 MK-92UCP054-05 2014-2016 Hitachi Data Systems. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or

More information

Hitachi Compute Blade 500/2500 LSI MegaRAID SAS 3004 (imr) firmware update User s Guide

Hitachi Compute Blade 500/2500 LSI MegaRAID SAS 3004 (imr) firmware update User s Guide Hitachi Compute Blade 500/2500 LSI MegaRAID SAS 3004 (imr) firmware update User s Guide FASTFIND LINKS Document organization Product version Getting help Contents MK-99COM153-01 2010-2017 Hitachi, Ltd.

More information

Hitachi Data Ingestor

Hitachi Data Ingestor Hitachi Data Ingestor Cluster Getting Started Guide Product Version Getting Help Contents MK-90HDI001-13 2010-2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Virtual Storage Platform

Hitachi Virtual Storage Platform Hitachi Virtual Storage Platform Hitachi Copy-on-Write Snapshot User Guide Document Organization Product Version Getting Help Contents MK-90RD7013-13 December 2016 2010-2016 Hitachi, Ltd. All rights reserved.

More information

Hitachi Data Instance Director

Hitachi Data Instance Director Hitachi Data Instance Director Quick Start Guide FASTFIND LINKS Software Version Getting Help Contents MK-93HDID002-01 2013-2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced

More information

Hitachi Command Suite. Tuning Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC022-43

Hitachi Command Suite. Tuning Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC022-43 Hitachi Command Suite Tuning Manager User Guide Document Organization Product Version Getting Help Contents MK-92HC022-43 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be

More information

G200, G400, G600, G800

G200, G400, G600, G800 Hitachi ShadowImage User Guide Hitachi Virtual Storage Platform G200, G400, G600, G800 Hitachi Virtual Storage Platform F400, F600, F800 Product Version Getting Help Contents MK-94HM8021-04 May 2016 2015,

More information

Hitachi Storage Advisor

Hitachi Storage Advisor Hitachi Storage Advisor Getting Started Guide MK-94HSA001-00 May 2016 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic

More information

Hitachi Command Suite. Tuning Manager. Server Administration Guide. FASTFIND LINKS Contents. Product Version. Getting Help MK-92HC021-39

Hitachi Command Suite. Tuning Manager. Server Administration Guide. FASTFIND LINKS Contents. Product Version. Getting Help MK-92HC021-39 Hitachi Command Suite Tuning Manager Server Administration Guide FASTFIND LINKS Contents Product Version Getting Help MK-92HC021-39 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication

More information

BBI Quick Guide Networking OS for 1/10Gb LAN Switch Module

BBI Quick Guide Networking OS for 1/10Gb LAN Switch Module BBI Quick Guide Networking OS for 1/10Gb LAN Switch Module FASTFIND LINKS Product Version Getting Help Contents MK-99CB2500038-00 2014 Hitachi, Ltd. All rights reserved. No part of this publication may

More information

Hitachi NAS Platform F1000 Series

Hitachi NAS Platform F1000 Series Hitachi NAS Platform F1000 Series Backup Restore Features Supplement for Hitachi Data Protection Suite Product Version Getting Help Contents MK-92NAS069-07 2012-2015 Hitachi, Ltd. All rights reserved.

More information

Tuning Manager Software

Tuning Manager Software Hitachi Command Suite Tuning Manager Software Getting Started Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents MK-96HC120-08 Copyright 2010 Hitachi Ltd., Hitachi Data Systems

More information

Hitachi Compute Blade 2500 Intel LAN Driver Instruction Manual for SUSE Linux Enterprise Server

Hitachi Compute Blade 2500 Intel LAN Driver Instruction Manual for SUSE Linux Enterprise Server Hitachi Compute Blade 2500 Intel LAN Driver Instruction Manual for SUSE Linux Enterprise Server FASTFIND LINKS Getting Help Contents MK-99CB2500054-02 2016 Hitachi, Ltd. All rights reserved. No part of

More information

Hitachi Storage Advisor. User Guide

Hitachi Storage Advisor. User Guide Hitachi Storage Advisor User Guide MK-94HSA004-00 May 2016 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi Compatible FlashCopy User Guide Hitachi Compatible Mirroring for IBM FlashCopy V2 Hitachi Compatible Mirroring for IBM FlashCopy SE Product Version Getting

More information

Hitachi Data Center Analytics v7.0 Release Notes

Hitachi Data Center Analytics v7.0 Release Notes Hitachi Data Center Analytics v7.0 Release Notes Contents About this document... 2 Intended audience... 2 Getting help... 2 About this release... 2 New features and important enhancements... 3 Distribution

More information

Hitachi Compute Blade 2000 LSI MegaRAID SAS 2208 RAID controller firmware update User s Guide

Hitachi Compute Blade 2000 LSI MegaRAID SAS 2208 RAID controller firmware update User s Guide Hitachi Compute Blade 2000 LSI MegaRAID SAS 2208 RAID controller firmware update User s Guide FASTFIND LINKS Document organization Product version Getting help Contents MK-99BDS2K105-02 2010-2014 Hitachi,

More information

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Copy-on-Write Snapshot User s Guide

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Copy-on-Write Snapshot User s Guide Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Copy-on-Write Snapshot User s Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents MK-96RD607-15

More information

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Storage Navigator Messages

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Storage Navigator Messages Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Storage Navigator Messages FASTFIND LINKS Document Organization Product Version Getting Help Contents MK-96RD613-18 Copyright

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi ShadowImage for Mainframe User Guide FASTFIND LINKS Contents Product Version Getting Help MK-92RD8020-04 2014-2015 Hitachi, Ltd. All rights reserved. No part

More information

Hitachi Dynamic Link Manager (for VMware ) Release Notes

Hitachi Dynamic Link Manager (for VMware ) Release Notes Hitachi Dynamic Link Manager (for VMware ) 8.5.1-04 Release Notes Contents About this document... 1 Intended audience... 1 Getting help... 1 About this release... 2 Product package contents... 2 New features

More information

Hitachi Unified Storage VM Block Module

Hitachi Unified Storage VM Block Module Hitachi Unified Storage VM Block Module Hitachi Volume Shredder User Guide FASTFIND LINKS Contents Product Version Getting Help MK-92HM7021-05 2012-2015 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Storage Command Portal Installation and Configuration Guide

Hitachi Storage Command Portal Installation and Configuration Guide Hitachi Storage Command Portal Installation and Configuration Guide FASTFIND LINKS Document Organization Product Version Getting Help Table of Contents # MK-98HSCP002-04 Copyright 2010 Hitachi Data Systems

More information

Hitachi TrueCopy for Mainframe

Hitachi TrueCopy for Mainframe Hitachi TrueCopy for Mainframe User Guide Hitachi Virtual Storage Platform G1000 and G1500 Hitachi Virtual Storage Platform F1500 MK-92RD8018-10 October 2016 2014, 2016 Hitachi, Ltd. All rights reserved.

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 FASTFIND LINKS Contents Product Version Getting Help MK-92RD8019-02 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Compute Blade HVM Navigator Installation Manual

Hitachi Compute Blade HVM Navigator Installation Manual Hitachi Compute Blade HVM Navigator Installation Manual FASTFIND LINKS Document organization Product version Getting help Contents MK-99COM023-17 2012-2016 Hitachi, Ltd. All rights reserved. No part of

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Hitachi Volume Shredder User Guide FASTFIND LINKS Contents Product Version Getting Help MK-92RD8025-01 2014 Hitachi, Ltd. All rights reserved. No part of this publication

More information

Hitachi Content Platform Anywhere Deploying an HCP Anywhere VM System

Hitachi Content Platform Anywhere Deploying an HCP Anywhere VM System Hitachi Content Platform Anywhere MK-HCPAW011-05 2016 Hitachi Data Systems Corporation. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic

More information

Hitachi Command Suite. Tuning Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC022-39

Hitachi Command Suite. Tuning Manager. User Guide. Document Organization. Product Version. Getting Help. Contents MK-92HC022-39 Hitachi Command Suite Tuning Manager User Guide Document Organization Product Version Getting Help Contents MK-92HC022-39 c 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication may

More information

Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration

Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration FASTFIND LINKS Document organization Product version Getting help Contents MK-99COM042-11 2012-2015 Hitachi, Ltd. All rights reserved.

More information

Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration

Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration Hitachi Compute Blade HVM Navigator User s Guide - LPAR Configuration FASTFIND LINKS Document organization Product version Getting help Contents MK-99COM042-09 2012-2015 Hitachi, Ltd. All rights reserved.

More information

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Compatible PAV for IBM z/os User's Guide (Including Hyper PAV)

Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Compatible PAV for IBM z/os User's Guide (Including Hyper PAV) Hitachi Universal Storage Platform V Hitachi Universal Storage Platform VM Hitachi Compatible PAV for IBM z/os User's Guide (Including Hyper PAV) FASTFIND LINKS Document Organization Product Version Getting

More information

Unified Complute Platform Release Patch 1. UCP DOC Administrator Guide

Unified Complute Platform Release Patch 1. UCP DOC Administrator Guide Unified Complute Platform Release 4.2.1 Patch 1 MK-92UCP054-08 October 13, 2017 2014-2017 Hitachi Vantara Corporation. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Virtual Storage Platform

Hitachi Virtual Storage Platform Hitachi Virtual Storage Platform Hitachi Volume Shredder User Guide Document Organization Product Version Getting Help Contents MK-90RD7035-08 December 2016 2010-2016 Hitachi, Ltd. All rights reserved.

More information

Hitachi Storage Replication Adapter for VMware vcenter Site Recovery Manager Deployment Guide

Hitachi Storage Replication Adapter for VMware vcenter Site Recovery Manager Deployment Guide Hitachi Storage Replication Adapter for VMware vcenter Site Recovery Manager Deployment Guide MK-09RM6745-11 May 2017 2009, 2017 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced

More information

Hitachi Compute Blade 2500 Series

Hitachi Compute Blade 2500 Series Hitachi Compute Blade 2500 Series Logical partitioning manager User Guide Document Organization Product Version Getting Help Contents MK-99CB2500006-01 2014-2015 Hitachi, Ltd. All rights reserved. No part

More information

Hitachi Compute Blade CB Base-T 4-port LAN Adapter User's Guide

Hitachi Compute Blade CB Base-T 4-port LAN Adapter User's Guide Hitachi Compute Blade CB2500 1000Base-T 4-port LAN Adapter User's Guide FASTFIND LINKS Getting Help Contents MK-99CB2500025-00 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be

More information

Compute Systems Manager

Compute Systems Manager Hitachi Command Suite Compute Systems Manager Messages FASTFIND LINKS Document Organization Product Version Getting Help Contents MK91HC19713 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this

More information

Hitachi Compute Blade Logical VGA SnapShot

Hitachi Compute Blade Logical VGA SnapShot Hitachi Compute Blade Logical VGA SnapShot FASTFIND LINKS Getting Help Contents MK-99COM074-07 2010-2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted

More information

Hitachi Virtual Storage Platform G1000

Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform G1000 Global-Active Device User Guide Product Version Getting Help Contents MK-92RD8072-05 2014, 2015 Hitachi, Ltd. All rights reserved. No part of this publication may

More information

System Management Unit (SMU)

System Management Unit (SMU) System Management Unit (SMU) Hardware Reference Guide The SMU400 is a 1U rack mounted device, used to manage the servers and clusters of the Hitachi NAS Platform, Hitachi HUS File Module, and Hitachi Virtual

More information

Storage System User Administration Guide. Hitachi Virtual Storage Platform Gx00 and Fx00 with NAS Modules Hitachi NAS Platform Release 13.

Storage System User Administration Guide. Hitachi Virtual Storage Platform Gx00 and Fx00 with NAS Modules Hitachi NAS Platform Release 13. Storage System User Administration Guide Hitachi Virtual Storage Platform Gx00 and Fx00 with NAS Modules Hitachi NAS Platform Release 13.4 MK-92HNAS013-13 March 2018 2011, 2018 Hitachi, Ltd. All rights

More information