Hitachi Data Instance Director · • Hitachi Data Instance Director Application Guide for protecting SAP HANA, MK-93HDID006 ... disruptive operations, data loss, or a system crash)

Hitachi Data Instance DirectorQuick Start Guide

MK-93HDID002-04

2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form orby any means, electronic or mechanical, including copying and recording, orstored in a database or retrieval system for commercial purposes without theexpress written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of theMaterials provided that any such copy is: (i) created as an essential step inutilization 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 theMaterials. “Materials” mean text, data, photographs, graphics, audio, videoand documents.

Hitachi reserves the right to make changes to this Material at any timewithout notice and assumes no responsibility for its use. The Materialscontain the most current information available at the time of publication.

Some of the features described in the Materials might not be currentlyavailable. Refer to the most recent product announcement for informationabout feature and product availability, or contact Hitachi Data SystemsCorporation at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the termsand conditions of the applicable Hitachi agreements. The use of Hitachiproducts is governed by the terms of your agreements with Hitachi DataSystems 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 toaccess relevant data; and

2. Verifying that data continues to be held, retrieved, deleted, or otherwiseprocessed in accordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent inthis Document may be subject to U.S. export control laws, including the U.S.Export Administration Act and its associated regulations, and may be subjectto export or import regulations in other countries. Reader agrees to complystrictly with all such regulations and acknowledges that Reader has theresponsibility to obtain licenses to export, re-export, or import the Documentand any Compliant Products.

2Hitachi Data Instance Director Quick Start Guide

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

Contents

Preface................................................................................................. 5Software version......................................................................................................6Intended audience................................................................................................... 6Related documents.................................................................................................. 6Document conventions............................................................................................. 6Conventions for storage capacity values.....................................................................7Accessing product documentation............................................................................. 8Getting help.............................................................................................................8Comments...............................................................................................................9

1 Introduction........................................................................................ 11Architecture...........................................................................................................12

Policy orientated data management................................................................... 12Setup workflows...............................................................................................13

2 Installation and license activation..........................................................15Installation prerequisites.........................................................................................16

Hitachi Content Platform indexing requirement................................................... 16Firewall configuration........................................................................................16Hitachi block and file requirements.................................................................... 16

Installing Data Instance Director............................................................................. 18Installation on Windows, Linux, and Solaris platforms..........................................19Installation on AIX platforms............................................................................. 22Installation on a Windows cluster environment................................................... 23

Installing Data Instance Director on the controlling node............................... 23Installing Data Instance Director on remaining nodes.................................... 24Adding the Hub service................................................................................25

Licensing the software...................................................................................... 25Upgrading Data Instance Director............................................................................25

Upgrade order..................................................................................................26Upgrade precautions.........................................................................................26Upgrading clients from Master........................................................................... 26


Licensing Data Instance Director............................................................................. 28Manual license activation...................................................................................28Cluster environment license activation................................................................28

Uninstalling Data Instance Director..........................................................................29

Glossary..............................................................................................33

Index..................................................................................................39


PrefaceThis document describes how to install and use Hitachi Data InstanceDirector

□ Software version

□ Intended audience

□ Related documents

□ Document conventions

□ Conventions for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface 5Hitachi Data Instance Director Quick Start Guide

Software versionThis document revision applies to Data Instance Director version 5.5.

Intended audienceThis document is intended for system administrators and other users who areresponsible for installing, configuring, and operating Hitachi Data InstanceDirector.

Related documents• Hitachi Data Instance Director Software Release Notes, RN-93HDID000• Hitachi Data Instance Director User’s Guide, MK-93HDID001• Hitachi Data Instance Director Quick Start Guide, MK-93HDID002• Hitachi Data Instance Director Disaster Recovery Reference,

MK-93HDID004• Hitachi Data Instance Director Application Guide for protecting SAP HANA,

MK-93HDID006• Hitachi Data Instance Director Application Guide for protecting Oracle,

MK-93HDID007• Hitachi Data Instance Director Application Guide for protecting Microsoft

SQL Server, MK-93HDID008• Hitachi Data Instance Director Application Guide for protecting Microsoft

Exchange Server, MK-93HDID009

Document conventionsThis 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 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 anglebrackets.)

6 PrefaceHitachi Data Instance Director Quick Start Guide

Convention Description

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

< > angle brackets Indicates variables 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.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a,b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that youmust 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:

Icon Label Description

Note Calls attention to important or additional information.

Tip Provides helpful information, guidelines, or suggestions for performingtasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (forexample, disruptive operations, data loss, or a system crash).

WARNING Warns the user of a hazardous situation which, if not avoided, couldresult in death or serious injury.

Conventions for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) arecalculated 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,0002 bytes

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

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


Physical capacity unit Value

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

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

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

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KB

Open-systems:• OPEN-V: 960 KB• Others: 720 KB

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://knowledge.hds.com/Documents. Check this site for themost current documentation, including important updates that may havebeen made after the release of the product.

Getting helpHitachi Data Systems Support Connect is the destination for technical supportof products and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contactinformation: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is the destination to get answers, discover insights, and makeconnections. Join the conversation today! Go to community.hds.com,register, and complete your profile.


https://knowledge.hds.com/Documents

https://knowledge.hds.com/

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

https://community.hds.com/welcome

https://community.hds.com/welcome

CommentsPlease send us your comments on this document to [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!


mailto:[email protected]


1Introduction

Hitachi Data Instance Director is a software application for the data centerand IT infrastructure of small, medium, and large organizations. It supportsthe protection and management of all data, from Laptop to File Server,Application Server, and Direct Attached Storage or Enterprise Storage Array.This chapter introduces the important basic architecture you need to know tounderstand the installation options and provides brief summaries of theinstallation and configuration steps.

□ Architecture

Introduction 11Hitachi Data Instance Director Quick Start Guide

ArchitectureAt the heart of the data management process is the Master Node, whichprovides instruction to all other nodes. Unless specifically instructed to do so,the Master Node does not take part in the data flow, and nodes pass dataamong themselves as instructed by the Master Node.

The different node types are:• Master Node: The machine that controls the actions of all other nodes on

the system. Multiple Master nodes can coexist on the same network,however a Data Instance Director node can only be authorized andcontrolled by a single master node. Passive standby Master nodes can beinstalled on a Windows failover cluster so that one can be brought online inthe event that the active master fails.

• Source Node: This node (server, workstation or virtual machine) storesdata to be managed. The source node has an Active Data Change Agent,which is responsible for monitoring the host file system, and performingthe relevant actions defined by the policies. Nodes must be configured as asource node if they need to transfer locally stored data, or implement datatracking, blocking, and auditing functions.

• Destination Node: This machine is capable of receiving data. This machinemight be the Data Instance Director Repository, a general-purpose systemdesignated as the recipient of data in a replication configuration.

A machine can be simultaneously designated as multiple node types. Amaster node can also be either a source or destination node, or both.

Policy orientated data managementData Instance Director is designed to allow your site to implement a businessdata protection process by using policies. Policies are mapped to machines orgroups, and to the data management agents that implement those policies. Alarge, complex environment can be configured in a matter of minutes ratherthan days through the use of two windows:• The Policy Definition window defines the business objective in terms of

policies.• The Data Flow window defines where those policies are applied, and the

path of the data flow, reflecting the information life cycle.

12 IntroductionHitachi Data Instance Director Quick Start Guide

Figure 1 Building a policy

Setup workflowsOnce you have identified the machines and their role and responsibility, youcan start the installation.

After installing and licensing Data Instance Director, you can start initialconfiguration and setup tasks for your site’s data protection.

The following diagram provides an overview of the installation tasks.

Figure 2 Installation overview

Refer to the Hitachi Data Instance Director User’s Guide for full instructions,and to complete the post-installation configuration and setup tasks:1. Defining policies2. Defining a data flow3. Distributing policies

Introduction 13Hitachi Data Instance Director Quick Start Guide

Data Instance Director compiles the policies into more granular instructions,and sends those instructions to each of the elements involved in datamanagement activity.

14 IntroductionHitachi Data Instance Director Quick Start Guide

2Installation and license activation

This chapter describes how to install and Data Instance Director

□ Installation prerequisites

□ Installing Data Instance Director

□ Upgrading Data Instance Director

□ Licensing Data Instance Director

□ Uninstalling Data Instance Director

Installation and license activation 15Hitachi Data Instance Director Quick Start Guide

Installation prerequisitesBefore you install Data Instance Director, confirm that your hardware andsoftware meet the requirements that are outlined on the Data InstanceDirector product website at https://www.hds.com/products/storage-software/hitachi-data-instance-director.html.

Hitachi Content Platform indexing requirementIf you plan to use the Hitachi Content Platform (HCP) with Data InstanceDirector, then the following Search Facility Settings must be selected withinthe Settings tab of the HCP, for the Metadata Query Engine (MQE):• Enable indexing• Enable indexing of custom metadata

Click Update MQE Settings to reflect the changes.

Firewall configurationIf a third party firewall is installed within your network, when processes arestarted as part of the Data Instance Director software installation, firewallwarnings might be generated.

Configure the firewall to allow access for all Internet-connected nodes (ornodes that are separated by firewalls) on one open port: 30304 (TCP andUDP).

Additional ports that might need to be opened are:• The HCP node (30306, by default)

• The Data Instance Director Microsoft Exchange notification client (30500)

Hitachi block and file requirementsIf you plan to perform snapshotting and replication of Hitachi Block and Filevolumes, then the following prerequisites are required:

• General:○ A machine must be assigned as a proxy node that controls the storage

device. This proxy node must be a Windows machine with:– The HDID repository capability installed– CCI installed:– Access to a command device set up as follows:

– Security disabled– User authentication enabled– Device group definition disabled

16 Installation and license activationHitachi Data Instance Director Quick Start Guide

https://www.hds.com/products/storage-software/hitachi-data-instance-director.html

https://www.hds.com/products/storage-software/hitachi-data-instance-director.html

– The command device is visible to the host OS where the ISMresides

– The command device may be online or offline– Multiple command devices may be visible to an ISM as long as

each one points to a different block storage device (behavior isundefined if multiple command devices point to the same blockstorage device)

– Multipath for command devices is supported○ A dedicated user for HDID must be created in the Administration user

group for the storage device○ All paths or application data to be snapshotted or replicated must exist

on the same block hardware device

• Hitachi Block:○ The following licensed features are required:

– Dynamic Provisioning– Storage Navigator– Thin Image– ShadowImage– TrueCopy– Universal Replicator– Global-Active Device– Remote Replication Extended (for 3DC scenarios)

○ Primary volumes must be set up○ For application consistent snapshots, the application must be installed

and configured to use HDS block P-Vols○ The username specified in the VSP node’s credentials must be a

member of the Administration User Group on the VSP○ The password for authorizing a VSP node must contain only useable CCI

command characters: A-Za-z0-9’-./:@\_○ Must have adequate shared memory (see Provisioning and Technical

Guides)○ Pools must be created using Storage Navigator prior to selecting the

Target Storage in Data Instance Director:– For Thin Image (TI ) the TI Pools must be set up– For ShadowImage (SI) the Dynamic Provisioning Pools must be set

up– For TrueCopy (TC) and Universal Replicator (UR) the Dynamic

Provisioning Pools must be set up○ Journals must be set up for UR○ GAD requires the P-Vols to be set up in a host group and quorum disks

to be provided. Best practice is to provide one quorum disk perreplication pair.

○ GAD requires virtualized LDEVs, available on VSP G series only○ Port security must be enabled on VSP VSP G1000


○ Anything done directly on Hitachi Block (outside of HDID) is notsupported by HDID

• Hitachi File:○ The following licensed features are required:

– File Clone– NFS– Replication

○ Access configuration for NFS exports must include norootsquash

• Windows Nodes:○ None

• Linux Nodes:○ Requires rescan-scsi-bus.sh CLI tool (see http://sg.danny.cz/sg/

sg3_utils.html○ Requires Multipath CLI command (install multipath package)

Installing Data Instance DirectorData Instance Director is distributed as an installation package for Windows,Linux, AIX, and Solaris.

The installation process allows you to set the installation destination andselect which components are to be installed. The same installation program isused for the Master node and Client node installations. The following sectionsprovide installation instructions for both nodes. Instructions for installingData Instance Director in a Microsoft Windows cluster configuration are alsoprovided.

Note: We recommend that you temporarily disable your antivirus softwareduring the installation process.

Precautions• Data Instance Director only supports batch mode backup policies when

installed on Linux, AIX and Solaris operating systems.• Data Instance Director 32-bit version is supported for installation on a 32-

bit operating system. If you attempt to install a 32-bit Data InstanceDirector on a 64-bit operating system, then you will be prompted to usethe 64-bit installer instead.

• Data Instance Director 64-bit version is supported for installation on a 64-bit operating system. If you attempt to install a 64-bit Data InstanceDirector on a 32-bit operating system, then you will be prompted to usethe 32-bit installer instead.


http://sg.danny.cz/sg/sg3_utils.html

http://sg.danny.cz/sg/sg3_utils.html

• For the master and repository installation, Data Instance Director issupported on 64-bit operating systems, only. Source node installation canbe done on either a 32-bit or 64-bit operating system.

• Only one active Master node can be installed in an environment. (A secondstandby Master can be installed on a Windows failover cluster – see Installation on a Windows cluster environment on page 23). Install theMaster node before installing other types of nodes.

• Windows 7, 8 and Vista are considered to be workstation operatingsystems, and by default, have additional security measures known as UserAccount Control (UAC). Installation of the Data Instance Director mastercomponents on a Windows 7, 8 or Vista machine requires that the UACsystem be disabled. Ideally the Master node should be installed on server-based operating systems, such as Windows 2008 or Windows 2012.If you must install Data Instance Director master components on amachine running Windows 7, 8 or Vista, you can disable UAC in the ControlPanel. Go to User Accounts and select Turn User Account Control on or off.

Installation on Windows, Linux, and Solaris platforms

Before you begin

If this is a new installation on a 32-bit Windows or any Linux or Solarisoperating system, then the installation will be for a client node, only.

When installing Data Instance Director on a Solaris node, the GCC runtimelibrary (version 4.5 or later) must be installed first. Type the followingcommand (here version 4.5 is specified but the version number can increasein future releases):

pkg install gcc-45-runtime

We recommend that Linux source nodes have a Logical Volume Manager(LVM) on each volume group. A minimum of 10 GB of free space is requiredin the 'unused' portion of the LVM that is to be backed up using host basedpolicies, which is in addition to the required space for the allocated storagearea. This is not required for storage based backup policies.

For example, if 100 GB of usable storage is required, then the total disk sizewill be 110 GB (100 GB of usable storage and 10 GB of unused storage).

Procedure

1. Locate and run the installer as follows:• Windows: Double-click HDID-Rm.n-m.n.n.nnnnn-Win-ppp.exe in the

directory where you downloaded it.• Linux: Ensure you have execute permissions and type the command:

chmod 755 ./HDID-m.n-m.n.n.nnnnn-Linux-ppp.run


• Solaris: Ensure you have execute permissions and type thecommand:

chmod 755 ./HDID-m.n-m.n.n.nnnnn-Solaris-ppp.run

where m is the major and n is the minor version number and ppp is theprocessor: x32, x64, or SPARC.

The installation process is either presented using a set of dialogs, or if nowindowing system is available on Linux the installations will display thesame information using the text mode shell.

2. When Setup is started, it checks for previous installations of DataInstance Director.If a previous installation is found, Setup launches the upgrade process.See Upgrading Data Instance Director on page 25 for moreinformation.

3. Click Next in the Setup welcome dialog.4. When prompted, accept the License Agreement, and click Next.5. The default installation directory for Data Instance Director is entered

automatically:a. For Windows 32-bit installations - C:\Program Files (x86)\Hitachi

\HDIDb. For Windows 64-bit installations - C:\Program Files\Hitachi\HDIDc. For Linux installations - /opt/Hitachi/HDID

To install Data Instance Director in a different location, enter the pathin the Installation Directory field or use the folder browser. ClickNext.

Note: If this is a new installation on a 32-bit Windows or anyLinux operating system, then the installation will be for a client(data source) node only.

6. Select the Data Instance Director components to install, and click Next.By default, Client is selected.a. Master: (Only available on Windows) Installs the components

required to make the current system the Master Node.Multiple Master nodes can coexist on the same network, however aData Instance Director node can only be authorized and controlled bya single master node; see Installation on a Windows clusterenvironment on page 23. The main Data Instance Director userinterface is installed and only accessible on the Master Node. The DataInstance Director environment is set up and managed through theMaster Node. A Master can also act as a Client and a Repository,enabling the node to have data captured from it and be able to storedata from Source Nodes in a Repository. Master nodes require Java tobe installed.


b. Client: This option enables the node to be a Source Node, and allowsdata to be captured on that node.This is required if the machine will send data to another Data InstanceDirector enabled system. A Client will also be able to have block ortrack operations performed on it.

c. Custom: This option allows specific components to be installed,allowing the Data Instance Director installation to be tailored to aspecific need.

7. (For Custom installations only), select the Data Instance Directorcomponents to install, and click Next.By default, Data Source is selected. A Custom node can be anycombination of the following components:a. Master: (Only available on Windows) Installs the components

required to make the current system the Master Node.Multiple Master nodes can coexist on the same network, however aData Instance Director node can only be authorized and controlled bya single master node. Standby Masters can be installed on a Windowsfailover cluster; see Installation on a Windows cluster environment onpage 23). The main Data Instance Director user interface is installedand only accessible on the Master Node. The Data Instance Directorenvironment is set up and managed through the Master Node. Masternodes require Java to be installed.

b. Data Source: This option enables the node to be a Source Node, andallows data to be captured on that node.This is required if the machine will send data to another Data InstanceDirector enabled system. The Data Source component is also requiredto perform block or track operations. Application aware hardwaresnapshotting and replication also requires this component.

c. Repository: (Windows only) This option enables the node to storedata received from source nodes in a repository.Any machine used as a hardware proxy node for storage-basedprotection must also have this component installed because it alsoprovides the ISM capability. Repository/ISM nodes require Java to beinstalled.

Note: If the ISM capability is being installed on a node to beused as a block storage proxy in a multi tenancy environment,then it is import that the Data Source component is deselected.

d. Mirror: This option allows the node to be designated as a ReplicationNode, making it suitable for replication operations (mirroring).

8. If a Repository is being installed (Master or Custom installation only), theinstaller prompts you for a Repository Directory.This directory allows the Repository and the data stored within it to beseparated from the other Data Instance Director components and fileswhich are installed.


Note: Because the Repository grows in large blocks, even for asmall amount of stored data, ensure that the RepositoryDestination has a minimum of 200 GB of free space. For an ISMonly (where no repository backups are required) 10GB of freespace is required.

9. In the Node Details dialog, specify a node name to be used within DataInstance Director. By default, the name is set to the machine’s hostname. This name is only for running Data Instance Director, and will notchange the name set in the operating system. If it is known that thenode will be operating over a non-secure network, such as the Internet,then we recommend enabling the Internet connected node option.This will encrypt transmitted data as an extra security precaution

10. If the Master component was not selected, then the installer will promptyou to enter the Master Hostname or IP address or a DNS resolvablename of the Master node.

11. Indicate whether you want to place a Data Instance Director GUIshortcut on the desktop, then click Next.

12. Click Next when Setup indicates that it is ready to begin the installation.Data Instance Director files are copied to the designated directories andthe necessary components installed.

13. Click Finish when the message dialog opens stating that the installationis complete.You do not need to restart your machine. (The installer starts all thenecessary Data Instance Director components on the system.)

Note: If a third party firewall is installed on the network, thenstarting these processes generates firewall warnings. Configure thefirewall to allow access for all Data Instance Director componentson one open port: 30304 (TCP and UDP).

Additional ports that might need to be opened are:• The HCP node (30306, by default)• The Data Instance Director Microsoft Exchange notification client

(30500)

Installation on AIX platformsIt is only possible to install the Data Instance Director client on an AIX node.We recommend that the installer is run from the command line as follows:

Procedure

1. Ensure you have execute permissions and type the command:chmod 755 ./HDID-m.n-m.n.n.nnnnn-AIX-ppp.run


where m is the major and n is the minor version number and ppp is theprocessor: PPC-64.

2. Execute the .run file and then read and accept the license agreement asdirected.

3. Accept or change the installation directory.4. Accept or change the node name (the default is the AIX hostname).5. Configure the node as an internet connected node if connecting to the

master over an unsecured network. (This requires an encryption license.)6. Enter the DNS resolvable name or IP address for the master node.7. Start the installation process when prompted to do so.

The installer will display a progress bar during installation.8. Enter the following command to confirm that the Data Instance Director

Hub service is running:HDID-Install-Path/bin/hub status

9. Go to the master node GUI and authorize the AIX node.

Installation on a Windows cluster environmentData Instance Director Master, Repository and Source capabilities can beinstalled on servers in a Windows cluster. Before starting the installation,review the following:• Ensure that all servers meet the software prerequisites that are outlined in

Installation prerequisites on page 16.• Confirm that a cluster environment is set up and working correctly.• Ensure that you have all required license keys for Data Instance Director:

A separate license key for each master node is required.

The installation for a cluster environment involves the following main tasks:1. Installing Data Instance Director on the controlling node on page 232. Installing Data Instance Director on remaining nodes on page 243. Adding the Hub service on page 254. Licensing the software on page 25

Installing Data Instance Director on the controlling nodeStart with the node that is in control (the node which has access to theshared disk). If needed, you can identify this node by launching the clustermanager.

Procedure

1. Double-click HDID-m.n-m.n.n.nnnnn-WIN-ppp.exe in the directory whereyou downloaded it on the server. Then, click Next in the Setup welcomedialog.

2. Read and accept the license agreement, then click Next.


3. Change the installation directory to the shared drive. (For example, ifyour shared drive is Q:\ then the installation path might be: Q:\Hitachi\HDID).

Note: Make a note of the specified path, as you will need toreference this later in the installation process.

4. Click Next.5. Select the Custom installation type, then click Next.6. Select Master, Repository, Data Source or a combination as these are

the only supported clustered roles. Then, click Next.7. If the Repository role has been selected, select the location of the

repository, then click Next.

Note: The repository must be located on the shared drive; forexample: Q:\Hitachi\HDID Also, make a note of the specifiedpath, as you will need to reference this later in the installationprocess.

8. Change the default Node name as all cluster nodes will have the samename.Use a generic name such as Cluster, Master, or Repository. Click Next.

9. Select an option for a desktop shortcut, then click Next.10. Click Next to start the installation.11. Click Finish, then shut down the machine to invoke failover.

Installing Data Instance Director on remaining nodes

Before you begin

Be sure and supply the same installation directory, clustered role, repositorylocation, and node name used in Installing Data Instance Director on thecontrolling node on page 23.

Procedure

1. Double-click HDID-m.n-m.n.n.nnnnn-WIN-ppp.exe in the directory whereyou downloaded it on the server. Then, click Next in the Setup welcomedialog.

2. Read and accept the license agreement, then click Next.3. Specify the same installation directory as that specified on the controlling

node.4. Select the Custom installation type, then click Next.5. Specify the same clustered role as that specified on the controlling node.6. If you selected the Repository role when installing on the controlling

node, then select the same location for the repository. Click Next.


7. Specify the same node name as that specified on the controlling node.8. Select the option for a desktop shortcut, then click Next.9. Click Next to start the installation.

10. Click Finish, then shut down the machine to invoke failover.11. Repeat this procedure on each additional node. After Data Instance

Director has been installed on all nodes, restart each node.

Adding the Hub serviceComplete the following steps on just one node of the cluster.

Procedure

1. Launch Failover Clustering on the server by clicking Start >Administrative Tools > Failover Cluster Manager

2. If the console tree is collapsed, expand the tree for the cluster that youwant to configure.

3. Right-click Services and Applications, then click Configure a Serviceor Application.

4. At the Before You Begin wizard, click Next.5. Select Generic Service, then click Next.6. Select the Cofio Hub Service from the list.7. Name the service (for example, CofioHubService), assign an IP address,

then click Next.8. At the Select Storage dialog, click Next.9. At the Replicate Registry Settings dialog, Click Next.

10. At the confirmation prompt, check that all settings are correct.If a setting is incorrect, click Previous, otherwise click Next.

11. At the Summary dialog, click Finish.

Licensing the softwareSee Cluster environment license activation on page 28.

Upgrading Data Instance DirectorThe Data Instance Director installation package automatically detects anycurrently installed versions of Data Instance Director. If a previous version isfound, an upgrade can be run with the same installation package.

An upgrade can be performed if a newer version of Data Instance Director isavailable or if the existing installation has become corrupt.

During an upgrade no options are available to change the installationdirectory, repository directory (if installed), machine name, installation type,capabilities or master name or IP address. The contents of any classifications


will not be changed, so if the HDID install location appears in a classificationit will not be changed.

When an upgrade starts, the Data Instance Director services are shutdown.These services are restarted when the upgrade process is exited orcompleted.

Note: We recommend upgrading Data Instance Director only after backupshave been completed.

Upgrade orderIt is recommended that nodes be upgraded in the following order:• Master nodes• Repository destination nodes• Replication destination nodes• Source nodes

After upgrading, the rules should be redistributed and all destination nodesshould be manually resynchronized with their sources.

Upgrade precautionsEnsure you save all desired changes as all unsaved changes will be discardedduring the upgrade process.

If this is an upgrade installation on a 32-bit operating system, all previously-defined roles are retained.

However, if you upgrade a 32-bit version Data Instance Director that isinstalled on a 64-bit operating system (in the installation default location),then in addition to retaining the previous roles, the installer converts DataInstance Director to a 64-bit version. The Hitachi file system structure (andthe location of the filter log file) will be moved to the Program Fileslocation, for example:

C:\Program Files\Hitachi

A warning message to this effect is displayed. The file system structure is notmoved if Data Instance Director was installed in a non-default location. ClickYes to proceed with the upgrade, or No to quit and exit Setup.

Upgrading clients from MasterWhile the Master can be upgraded by running the update executable, DataInstance Director clients, Source, Repository, and Replication Nodes (virtualand physical) can be automatically updated with direct control from theMaster.


To do this, place the updated Data Instance Director executable into thefollowing directory on the Master:

installation-folder\Hitachi\HDID\runtime\updater

Then, select the Upgrade Clients option.

Figure 3 Upgrade Clients menu option

The Upgrade Clients dialog launches and lists all Data Instance Directorclients.

Figure 4 Data Instance Director Clients list

Select the check boxes on the nodes to upgrade and choose the installerversion to use from the Available installers combo box at the bottom of thedialog. This will display all the executables that have been placed into theupdater directory. The Master will push the install package and execute theupgrade automatically.

Note: The Upgrade Clients dialog only lists nodes that are running on aWindows OS.


Licensing Data Instance DirectorTo distribute rules, the master machine must have a valid Data InstanceDirector activation key.

As of Data Instance Director version 4.2.0, the software installation includesa built-in evaluation key for sites that want to use the product on a trial-to-permanent basis. After the software is installed, it can be used for 45 days,with up to 10 TB of maximum data usage, before a permanent license key isrequired. (Existing, purchased customers who upgrade to version 4.2.0 areunaffected by the feature: Their permanent license continues to conveyduring the upgrade.)

After a trial license has expired, the permanent license must be enteredmanually.

Note: Any node requiring encryption should have the Hub service restartedfollowing the new license being sent to that node. If the node is alreadyauthorized, two Hub service restarts can be required.

Manual license activationIf you have a valid activation key, then it can be entered directly within theData Instance Director GUI.1. Start Data Instance Director in one of the following ways:

• Double-click the desktop shortcut.• Select Programs > Data Instance Director > Data Instance Director

from the Start menu.

2. The Data Instance Director License dialog opens. If Data InstanceDirector is unlicensed, then this will be opened automatically uponstarting the user interface. Otherwise, it can be accessed through Help >License.

3. Select the Manual Activation tab.4. Enter the Activation Key then click Enter Key.

Cluster environment license activationBecause each machine in the cluster has a different machine ID, a separatelicense for each node is required.1. Launch Data Instance Director.

The Data Instance Director License dialog displays and indicates themachine-specific ID.

2. Enter the license key for the machine, then click Enter Key.This node isnow licensed.

3. Close all Data Instance Director windows.


4. Browse to the installation directory that you specified in the first task(Installing Data Instance Director on the controlling node on page 23)then navigate to Data-Instance-Director-installation\db\config\

5. Right click License.xml and open the file with WordPad.6. Copy line 2 and insert it as a new line (below line 2).7. Change the activation key to match your second node.8. Repeat steps 6 and 7 for each additional node.9. Save and close the file.

Uninstalling Data Instance Director

Note: Uninstalling the Data Instance Director master does not deactivateactive rules on client nodes. To do this, you must either clear the dataflow(s)and redistribute the rules before uninstalling, or uninstall the clientsindividually.

Stubbed files and emails are not automatically un-stubbed; this must bedone manually, prior to uninstalling Data Instance Director, by running thesourcestubcli r command on each machine, restoring email then deletingthe stubs.

For Linux and AIX:

Enter the following command and follow the on-screen instructions:

/opt/Hitachi/HDID/uninstall

For Windows:

Procedure

1. Note the path for the install directory and any repositories. These will berequired later if you wish to completely remove all traces of theinstallation and do not want to retain backup data retained in therepositories.

2. From the Start menu run Uninstall Hitachi Data Instance Director.Alternatively, navigate to the installation directory and execute thecommand uninstall.exe.A dialog will be displayed asking you to confirm that you wish to proceed.Running the command uninstall.exe --mode unattended will causethe uninstall process to proceed without requiring user interaction;although popups may briefly appear before being automaticallydismissed.

3. Click Yes to proceed with the uninstall process (or No to abort theprocess).A Setup dialog is displayed containing an Uninstall Status bar andinformation about what actions are currently being performed.


4. At some point during the uninstallation process you may be presentedwith a Warning dialog telling you that any repositories must bemanually deleted. The uninstall process will pause until you click OK.Manual removal of repositories is covered later on.

5. Eventually an Info dialog will be displayed stating that the uninstallprocess is complete. Click OK.

6. Delete any repository directories noted down before uninstalling. Ensurethat there are no files or windows open at these locations or attempts atdeletion may fail.HDID and its repositories are now uninstalled and you can end theprocedure at this point.

Some artefacts will still remain on your machine. These items are left inplace either to facilitate easier reinstallation or because they remainedafter upgrading from an earlier version or from a failed install. If youwant to remove these artefacts, then continue with the following steps:

7. Delete the HDID installation directory tree noted down beforeuninstalling. Ensure that there are no files or windows open at thislocation or attempts at deletion may fail.

8. Delete the Bitrock installer log files bitrock_installer.log andbitrock_installer_<nnnn>.log normally located in C:\Users\Administrator\AppData\Local\Temp

9. Open the Windows Registry Editor from the Start > Run... dialog byentering regedit.exe in the Open: field.The Registry Editor window is displayed. Alternatively use the regdelete command from within a Command Prompt.

10. Carefully delete the following registry keys:

Caution: Incorrectly editing the Registry can cause the operatingsystem to become unstable or stop working. Exercise extremecaution when performing this step.

• HKEY_LOCAL_MACHINE\SOFTWARE\Cofio Software• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cofio Software• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

\CofioHub• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

\dcefltr• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

\sdrefltr• HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi Data Systems\Hitachi

Data Instance Director11. Confirm that the dcefltr and sdrefltr filter drivers are no longer

installed on your system by entering the commands sc query dcefltrand sc query sdrefltr.You should see the following output in response to both commands:


The specified service does not exists as an installed service.

Occasionally an uninstallation may fail to complete successfully. In thissituation there are a number of things that can be done before retrying:• Ensure any files or folders that can block the uninstallation are closed.• Reboot the machine to return it to a known, stable state.• Reinstall HDID over the existing partially uninstalled version. In most

cases this will allow an uninstallation to be successfully re-performed.



GlossaryAArchive

A copy that is created for long-term retention.

Asynchronous journaling

Transactions are written to disk and also placed in a journal log file, toprotect against data loss in the event of a system failure. Transactionsfrom the log file are sent to the destination machine.

Asynchronous replicationTransactions are held in memory before being sent over the network. Ifthe network is unavailable then transactions are written to disk and sentto the destination machine when the connection is re-established.Asynchronous replication is optimal for connections with sporadicefficiency.

BBackup

A copy that is created for operational and disaster recovery.

Bandwidth throttlingUsed to control when and what proportion of available network bandwidthis used by Data Instance Director for replication.

Batch backupA process by which the repository is updated periodically using scheduledresynchronizations. This method involves a scan of the source machine'sfile system, but only the changed bytes are transferred and stored. Thismethod is useful for data that does not change often, such as datacontained on the operating system disk. Linux based source nodes areonly able to perform batch backups. See CDP below.

Glossary 33Hitachi Data Instance Director Quick Start Guide

BlockingData Instance Director can be used to block access to files or directorieson a given source machine. Only source nodes that are running on aWindows OS can be blocked.

CClone

An operation where a copy of the database is created in another storagelocation in a local or remote site.

Continuous Data Protection (CDP)A method of capturing the state of a file system in near real time. CDPshares much of the functionality of Live Backup, except that RPO ismeasured in minutes, data is retained for a much shorter period of timeand is not indexed by the MDS. Typically, CDP and Live Backup are usedin conjunction. CDP is only supported on source nodes running theMicrosoft Windows operating system.

DData flow

Identifies the data sources, movers and destinations participating in abackup, along with interconnection paths between them. Policies areassigned to each node to determine what type of data is backed up.

Data source

A machine hosting a file system or application where the HDID clientsoftware is installed.

DeduplicationA method of reducing the amount of storage space that your organizationrequires, to archive data, by replacing multiple instances of identical datawith references to a single instance of that data.

Destination nodeA machine that is capable of receiving data for the purposes of archiving.This machine might be the Data Instance Director Repository, a mirror, atape library, cloud storage or tiered storage.

FForest

The collective noun used to describe a group of tree structures without acommon root node.

34 GlossaryHitachi Data Instance Director Quick Start Guide

GGroups

Within the Node Manager window, you can assign multiple machines toone or more groups. Then, within the Data Flow window, you can assignpolicies the nodes within these groups en-mass.

HHitachi Content Platform (HCP)

An object storage system recommended for large-scale archiving. DataInstance Director keeps only the file metadata in its repository, while HCPstores the data.

LLicense key

A unique, alphanumeric code that is associated with the unique machineID that is generated during the Data Instance Director installation. Thelicense key must be activated in order to use the software.

Live backupA backup technique that avoids the need for bulk data transfers bycontinuously updating the repository with changes to the source filesystem. This is similar to CDP but with longer retention periods and RPOsbeing available. Live backups perform byte level change updates whereasbatch backups perform block level change updates.

MMaster node

The machine that controls the actions of other nodes within the DataInstance Director network.

Metadata Store (MDS)Records metadata that describes items that are held in repositories, tapelibraries and HCP. The MDS supports indexing of stored data, thusenabling fast searches when locating data for restoration.

MoverDefines the type of data movement operation to be performed betweensource and destination nodes, during the creation of a data flow. Batchmovers perform block level data transfers on a scheduled basis, whereascontinuous movers perform byte level data transfers on a near-continuousbasis. Mirror movers are a specific type of continuous mover used tocreate uni- and bi-directional mirrors.


OOutlook form

When viewing stubbed emails within Microsoft Outlook, a custom Outlookform must be installed that allows Data Instance Director to retrieve theattachment from HCP. The Outlook Form must be installed within anOrganizational level Exchange Public Folder within an Exchange PublicDatabase, so it can be accessible by all Outlook users.

PPolicy

A configurable data protection objective that is mapped to machines orgroups, and to the data management agents that implement the policy.Multiple policies can be assigned to a single node.

RRecovery Point Objective (RPO)

The frequency at which a backup will occur. This governs the point in timeto which data can be recovered should a restore be needed.

Replication

An operation where a copy of the data is created in another local orremote location automatically.

RepositoryA destination node that stores data from one or more source nodes. TheData Instance Director Repository supports live backup, batch backup,archiving, and versioning policies.

SSnapshot (Thin Image)

A point in time copy of the data that is based on references to the originaldata.

Source nodeAny node (server, workstation or virtual machine) that hosts data to beprotected by Data Instance Director. The source node has an Active DataChange Agent, which is responsible for monitoring the host file systemand performing the relevant actions defined by the policies. Nodes needto be configured as a source node if they need to transfer locally storeddata to a destination node, or implement data tracking, blocking andauditing functions. A node can be both a source and destinationsimultaneously.


StubbingThe process by which the contents of a file, email body, or emailattachment are replaced by a reference or link that points to the copy ofthe data that is stored on the HCP.

Synchronous replicationTransactions are transferred to the remote storage device immediatelyand the write operation is signaled as completed only once data isconfirmed as written to both primary and secondary volumes.Synchronous replication is optimal for connections with high efficiency.

TTiering

A process in which data is taken from the repository and placed into HCP,at established backup cycles.

TrackingData Instance Director can be used to track access to files or directorieson any given source machine. Each time a file is accessed, a log messageis generated that lists the type of access and the user who accessed thefile. Only source nodes that are running on a Windows OS can be tracked.

VVersioning

Whenever a file is saved, any changes, are recorded. For instance, whenapplied to office documents, every time a document is saved, theprevious version is retained and indexed. This allows a history of a file tobe generated, showing how the file changed over time.



IndexD

Data Instance Directorinstalling 18licensing 28uninstalling 29upgrading 25

HHCP indexing

prerequisites 16

IInstallation

Microsoft cluster 23Overview for Data Instance Director 18

LLicensing

Data Instance Director 28Microsoft cluster environment 28

MMicrosoft cluster

installation 23Microsoft Cluster

licensing 28

PPrerequisities

HCP indexing 16

UUninstalling

Data Instance Director 29Upgrading

Data Instance Director 25

VVSP snapshotting

Prerequisites 16

Index 39Hitachi Data Instance Director Quick Start Guide

40 IndexHitachi Data Instance Director Quick Start Guide

Hitachi Data Instance Director Quick Start Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0) 1753 [email protected]

Asia Pacific+852 3189 [email protected]

Contact Uswww.hds.com/en-us/contact.html

MK-93HDID002-04

http://www.hds.com

MAILTO:[email protected]

