Hitachi Data Instance Director

Transcription

1 Hitachi Data Instance Director Quick Start Guide MK-93HDID002-04

2 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. 2

3 Contents Preface... 5 Software version...6 Intended audience... 6 Related documents... 6 Document conventions... 6 Conventions for storage capacity values...7 Accessing product documentation... 8 Getting help...8 Comments Introduction Architecture...12 Policy orientated data management Setup workflows Installation and license activation...15 Installation prerequisites...16 Hitachi Content Platform indexing requirement Firewall configuration...16 Hitachi block and file requirements Installing Data Instance Director Installation on Windows, Linux, and Solaris platforms...19 Installation on AIX platforms Installation on a Windows cluster environment Installing Data Instance Director on the controlling node Installing Data Instance Director on remaining nodes Adding the Hub service...25 Licensing the software Upgrading Data Instance Director...25 Upgrade order...26 Upgrade precautions...26 Upgrading clients from Master

4 Licensing Data Instance Director Manual license activation...28 Cluster environment license activation...28 Uninstalling Data Instance Director...29 Glossary...33 Index

5 Preface This document describes how to install and use Hitachi Data Instance Director Software version Intended audience Related documents Document conventions Conventions for storage capacity values Accessing product documentation Getting help Comments Preface 5

6 Software version This document revision applies to Data Instance Director version 5.5. Intended audience This document is intended for system administrators and other users who are responsible for installing, configuring, and operating Hitachi Data Instance Director. Related documents Hitachi Data Instance Director Software Release Notes, RN-93HDID000 Hitachi Data Instance Director User s Guide, MK-93HDID001, 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 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 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.) 6 Preface

7 Convention Monospace Description 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 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: 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 and/or consequences (for example, disruptive operations, data loss, or a system crash). WARNING Warns the user of a hazardous situation which, if not avoided, could result in death or serious injury. Conventions for storage capacity values Physical storage capacity values (for example, disk 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 Preface 7

8 Physical capacity unit Value 1 petabyte (PB) 1,000 TB or 1,000 5 bytes 1 exabyte (EB) 1,000 PB or 1,000 6 bytes Logical capacity values (for example, logical device capacity, cache memory 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 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Product user 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. 8 Preface

9 Comments Please send us your comments on this document to 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! Preface 9

10 10 Preface

11 1 Introduction Hitachi Data Instance Director is a software application for the data center and IT infrastructure of small, medium, and large organizations. It supports the 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 to understand the installation options and provides brief summaries of the installation and configuration steps. Architecture Introduction 11

12 Architecture At the heart of the data management process is the Master Node, which provides 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 data among 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 and controlled by a single master node. Passive standby Master nodes can be installed on a Windows failover cluster so that one can be brought online in the event that the active master fails. Source Node: This node (server, workstation or virtual machine) stores data to be managed. The source node has an Active Data Change Agent, which is responsible for monitoring the host file system, and performing the relevant actions defined by the policies. Nodes must be configured as a source node if they need to transfer locally stored data, or implement data tracking, blocking, and auditing functions. Destination Node: This machine is capable of receiving data. This machine might be the Data Instance Director Repository, a general-purpose system designated as the recipient of data in a replication configuration. A machine can be simultaneously designated as multiple node types. A master node can also be either a source or destination node, or both. Policy orientated data management Data Instance Director is designed to allow your site to implement a business data protection process by using policies. Policies are mapped to machines or groups, and to the data management agents that implement those policies. A large, complex environment can be configured in a matter of minutes rather than 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 Introduction

13 Figure 1 Building a policy Setup workflows Once you have identified the machines and their role and responsibility, you can start the installation. After installing and licensing Data Instance Director, you can start initial configuration 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 policies 2. Defining a data flow 3. Distributing policies Introduction 13

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

15 2 Installation 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 15

16 Installation prerequisites Before you install Data Instance Director, confirm that your hardware and software meet the requirements that are outlined on the Data Instance Director product website at hitachi-data-instance-director.html. Hitachi Content Platform indexing requirement If you plan to use the Hitachi Content Platform (HCP) with Data Instance Director, then the following Search Facility Settings must be selected within the 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 configuration If a third party firewall is installed within your network, when processes are started as part of the Data Instance Director software installation, firewall warnings might be generated. Configure the firewall to allow access for all Internet-connected nodes (or nodes that are separated by firewalls) on one open port: (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) Hitachi block and file requirements If you plan to perform snapshotting and replication of Hitachi Block and File volumes, 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 activation

17 The command device is visible to the host OS where the ISM resides 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 is undefined if multiple command devices point to the same block storage 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 per replication pair. GAD requires virtualized LDEVs, available on VSP G series only Port security must be enabled on VSP VSP G1000 Installation and license activation 17

18 Anything done directly on Hitachi Block (outside of HDID) is not supported 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 sg3_utils.html Requires Multipath CLI command (install multipath package) Installing Data Instance Director Data Instance Director is distributed as an installation package for Windows, Linux, AIX, and Solaris. The installation process allows you to set the installation destination and select which components are to be installed. The same installation program is used for the Master node and Client node installations. The following sections provide installation instructions for both nodes. Instructions for installing Data Instance Director in a Microsoft Windows cluster configuration are also provided. Note: We recommend that you temporarily disable your antivirus software during 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 Instance Director on a 64-bit operating system, then you will be prompted to use the 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 Instance Director on a 32-bit operating system, then you will be prompted to use the 32-bit installer instead. 18 Installation and license activation

19 For the master and repository installation, Data Instance Director is supported on 64-bit operating systems, only. Source node installation can be done on either a 32-bit or 64-bit operating system. Only one active Master node can be installed in an environment. (A second standby Master can be installed on a Windows failover cluster see Installation on a Windows cluster environment on page 23). Install the Master node before installing other types of nodes. Windows 7, 8 and Vista are considered to be workstation operating systems, and by default, have additional security measures known as User Account Control (UAC). Installation of the Data Instance Director master components on a Windows 7, 8 or Vista machine requires that the UAC system be disabled. Ideally the Master node should be installed on serverbased operating systems, such as Windows 2008 or Windows If you must install Data Instance Director master components on a machine running Windows 7, 8 or Vista, you can disable UAC in the Control Panel. 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 Solaris operating system, then the installation will be for a client node, only. When installing Data Instance Director on a Solaris node, the GCC runtime library (version 4.5 or later) must be installed first. Type the following command (here version 4.5 is specified but the version number can increase in 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 required in the 'unused' portion of the LVM that is to be backed up using host based policies, which is in addition to the required space for the allocated storage area. This is not required for storage based backup policies. For example, if 100 GB of usable storage is required, then the total disk size will 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 Installation and license activation 19

20 Solaris: Ensure you have execute permissions and type the command: 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 the processor: x32, x64, or SPARC. The installation process is either presented using a set of dialogs, or if no windowing system is available on Linux the installations will display the same information using the text mode shell. 2. When Setup is started, it checks for previous installations of Data Instance Director. If a previous installation is found, Setup launches the upgrade process. See Upgrading Data Instance Director on page 25 for more information. 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 \HDID b. For Windows 64-bit installations - C:\Program Files\Hitachi\HDID c. For Linux installations - /opt/hitachi/hdid To install Data Instance Director in a different location, enter the path in the Installation Directory field or use the folder browser. Click Next. Note: If this is a new installation on a 32-bit Windows or any Linux 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 a Data Instance Director node can only be authorized and controlled by a single master node; see Installation on a Windows cluster environment on page 23. The main Data Instance Director user interface is installed and only accessible on the Master Node. The Data Instance Director environment is set up and managed through the Master 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 store data from Source Nodes in a Repository. Master nodes require Java to be installed. 20 Installation and license activation

21 b. Client: This option enables the node to be a Source Node, and allows data to be captured on that node. This is required if the machine will send data to another Data Instance Director enabled system. A Client will also be able to have block or track operations performed on it. c. Custom: This option allows specific components to be installed, allowing the Data Instance Director installation to be tailored to a specific need. 7. (For Custom installations only), select the Data Instance Director components to install, and click Next. By default, Data Source is selected. A Custom node can be any combination 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 a Data Instance Director node can only be authorized and controlled by a single master node. Standby Masters can be installed on a Windows failover cluster; see Installation on a Windows cluster environment on page 23). The main Data Instance Director user interface is installed and only accessible on the Master Node. The Data Instance Director environment is set up and managed through the Master Node. Master nodes require Java to be installed. b. Data Source: This option enables the node to be a Source Node, and allows data to be captured on that node. This is required if the machine will send data to another Data Instance Director enabled system. The Data Source component is also required to perform block or track operations. Application aware hardware snapshotting and replication also requires this component. c. Repository: (Windows only) This option enables the node to store data received from source nodes in a repository. Any machine used as a hardware proxy node for storage-based protection must also have this component installed because it also provides the ISM capability. Repository/ISM nodes require Java to be installed. Note: If the ISM capability is being installed on a node to be used 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 Replication Node, making it suitable for replication operations (mirroring). 8. If a Repository is being installed (Master or Custom installation only), the installer prompts you for a Repository Directory. This directory allows the Repository and the data stored within it to be separated from the other Data Instance Director components and files which are installed. Installation and license activation 21

22 Note: Because the Repository grows in large blocks, even for a small amount of stored data, ensure that the Repository Destination has a minimum of 200 GB of free space. For an ISM only (where no repository backups are required) 10GB of free space is required. 9. In the Node Details dialog, specify a node name to be used within Data Instance Director. By default, the name is set to the machine s host name. This name is only for running Data Instance Director, and will not change the name set in the operating system. If it is known that the node 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 prompt you to enter the Master Hostname or IP address or a DNS resolvable name of the Master node. 11. Indicate whether you want to place a Data Instance Director GUI shortcut 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 and the necessary components installed. 13. Click Finish when the message dialog opens stating that the installation is complete. You do not need to restart your machine. (The installer starts all the necessary Data Instance Director components on the system.) Note: If a third party firewall is installed on the network, then starting these processes generates firewall warnings. Configure the firewall to allow access for all Data Instance Director components on one open port: (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 platforms It 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 22 Installation and license activation

23 where m is the major and n is the minor version number and ppp is the processor: PPC Execute the.run file and then read and accept the license agreement as directed. 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 environment Data Instance Director Master, Repository and Source capabilities can be installed 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 Installing Data Instance Director on remaining nodes on page Adding the Hub service on page Licensing the software on page 25 Installing Data Instance Director on the controlling node Start with the node that is in control (the node which has access to the shared disk). If needed, you can identify this node by launching the cluster manager. Procedure 1. Double-click HDID-m.n-m.n.n.nnnnn-WIN-ppp.exe in the directory where you downloaded it on the server. Then, click Next in the Setup welcome dialog. 2. Read and accept the license agreement, then click Next. Installation and license activation 23

24 3. Change the installation directory to the shared drive. (For example, if your 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 to reference 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; for example: Q:\Hitachi\HDID Also, make a note of the specified path, as you will need to reference this later in the installation process. 8. Change the default Node name as all cluster nodes will have the same name. 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, repository location, and node name used in Installing Data Instance Director on the controlling node on page 23. Procedure 1. Double-click HDID-m.n-m.n.n.nnnnn-WIN-ppp.exe in the directory where you downloaded it on the server. Then, click Next in the Setup welcome dialog. 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. 24 Installation and license activation

25 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 service Complete 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 you want to configure. 3. Right-click Services and Applications, then click Configure a Service or 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 software See Cluster environment license activation on page 28. Upgrading Data Instance Director The Data Instance Director installation package automatically detects any currently installed versions of Data Instance Director. If a previous version is found, an upgrade can be run with the same installation package. An upgrade can be performed if a newer version of Data Instance Director is available or if the existing installation has become corrupt. During an upgrade no options are available to change the installation directory, repository directory (if installed), machine name, installation type, capabilities or master name or IP address. The contents of any classifications Installation and license activation 25

26 will not be changed, so if the HDID install location appears in a classification it 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 or completed. Upgrade order Note: We recommend upgrading Data Instance Director only after backups have been completed. It 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 nodes should be manually resynchronized with their sources. Upgrade precautions Ensure you save all desired changes as all unsaved changes will be discarded during the upgrade process. If this is an upgrade installation on a 32-bit operating system, all previouslydefined roles are retained. However, if you upgrade a 32-bit version Data Instance Director that is installed on a 64-bit operating system (in the installation default location), then in addition to retaining the previous roles, the installer converts Data Instance Director to a 64-bit version. The Hitachi file system structure (and the location of the filter log file) will be moved to the Program Files location, for example: C:\Program Files\Hitachi A warning message to this effect is displayed. The file system structure is not moved if Data Instance Director was installed in a non-default location. Click Yes to proceed with the upgrade, or No to quit and exit Setup. Upgrading clients from Master While the Master can be upgraded by running the update executable, Data Instance Director clients, Source, Repository, and Replication Nodes (virtual and physical) can be automatically updated with direct control from the Master. 26 Installation and license activation

27 To do this, place the updated Data Instance Director executable into the following 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 Director clients. Figure 4 Data Instance Director Clients list Select the check boxes on the nodes to upgrade and choose the installer version to use from the Available installers combo box at the bottom of the dialog. This will display all the executables that have been placed into the updater directory. The Master will push the install package and execute the upgrade automatically. Note: The Upgrade Clients dialog only lists nodes that are running on a Windows OS. Installation and license activation 27

28 Licensing Data Instance Director To distribute rules, the master machine must have a valid Data Instance Director activation key. As of Data Instance Director version 4.2.0, the software installation includes a built-in evaluation key for sites that want to use the product on a trial-topermanent 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 is required. (Existing, purchased customers who upgrade to version are unaffected by the feature: Their permanent license continues to convey during the upgrade.) After a trial license has expired, the permanent license must be entered manually. Note: Any node requiring encryption should have the Hub service restarted following the new license being sent to that node. If the node is already authorized, two Hub service restarts can be required. Manual license activation If you have a valid activation key, then it can be entered directly within the Data 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 Instance Director is unlicensed, then this will be opened automatically upon starting 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 activation Because each machine in the cluster has a different machine ID, a separate license for each node is required. 1. Launch Data Instance Director. The Data Instance Director License dialog displays and indicates the machine-specific ID. 2. Enter the license key for the machine, then click Enter Key.This node is now licensed. 3. Close all Data Instance Director windows. 28 Installation and license activation

29 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 deactivate active rules on client nodes. To do this, you must either clear the dataflow(s) and redistribute the rules before uninstalling, or uninstall the clients individually. Stubbed files and s are not automatically un-stubbed; this must be done manually, prior to uninstalling Data Instance Director, by running the sourcestubcli r command on each machine, restoring then deleting the 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 be required later if you wish to completely remove all traces of the installation and do not want to retain backup data retained in the repositories. 2. From the Start menu run Uninstall Hitachi Data Instance Director. Alternatively, navigate to the installation directory and execute the command uninstall.exe. A dialog will be displayed asking you to confirm that you wish to proceed. Running the command uninstall.exe --mode unattended will cause the uninstall process to proceed without requiring user interaction; although popups may briefly appear before being automatically dismissed. 3. Click Yes to proceed with the uninstall process (or No to abort the process). A Setup dialog is displayed containing an Uninstall Status bar and information about what actions are currently being performed. Installation and license activation 29

30 4. At some point during the uninstallation process you may be presented with a Warning dialog telling you that any repositories must be manually 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 uninstall process is complete. Click OK. 6. Delete any repository directories noted down before uninstalling. Ensure that there are no files or windows open at these locations or attempts at deletion may fail. HDID and its repositories are now uninstalled and you can end the procedure at this point. Some artefacts will still remain on your machine. These items are left in place either to facilitate easier reinstallation or because they remained after upgrading from an earlier version or from a failed install. If you want to remove these artefacts, then continue with the following steps: 7. Delete the HDID installation directory tree noted down before uninstalling. Ensure that there are no files or windows open at this location or attempts at deletion may fail. 8. Delete the Bitrock installer log files bitrock_installer.log and bitrock_installer_<nnnn>.log normally located in C:\Users \Administrator\AppData\Local\Temp 9. Open the Windows Registry Editor from the Start > Run... dialog by entering regedit.exe in the Open: field. The Registry Editor window is displayed. Alternatively use the reg delete command from within a Command Prompt. 10. Carefully delete the following registry keys: Caution: Incorrectly editing the Registry can cause the operating system to become unstable or stop working. Exercise extreme caution 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 Director 11. Confirm that the dcefltr and sdrefltr filter drivers are no longer installed on your system by entering the commands sc query dcefltr and sc query sdrefltr. You should see the following output in response to both commands: 30 Installation and license activation

31 The specified service does not exists as an installed service. Occasionally an uninstallation may fail to complete successfully. In this situation 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. Installation and license activation 31

32 32 Installation and license activation

33 Glossary A Archive A copy that is created for long-term retention. Asynchronous journaling Transactions are written to disk and also placed in a journal log file, to protect against data loss in the event of a system failure. Transactions from the log file are sent to the destination machine. Asynchronous replication Transactions are held in memory before being sent over the network. If the network is unavailable then transactions are written to disk and sent to the destination machine when the connection is re-established. Asynchronous replication is optimal for connections with sporadic efficiency. B Backup A copy that is created for operational and disaster recovery. Bandwidth throttling Used to control when and what proportion of available network bandwidth is used by Data Instance Director for replication. Batch backup A process by which the repository is updated periodically using scheduled resynchronizations. This method involves a scan of the source machine's file system, but only the changed bytes are transferred and stored. This method is useful for data that does not change often, such as data contained on the operating system disk. Linux based source nodes are only able to perform batch backups. See CDP below. Glossary 33

34 Blocking C Data Instance Director can be used to block access to files or directories on a given source machine. Only source nodes that are running on a Windows OS can be blocked. Clone An operation where a copy of the database is created in another storage location in a local or remote site. Continuous Data Protection (CDP) A method of capturing the state of a file system in near real time. CDP shares much of the functionality of Live Backup, except that RPO is measured in minutes, data is retained for a much shorter period of time and is not indexed by the MDS. Typically, CDP and Live Backup are used in conjunction. CDP is only supported on source nodes running the Microsoft Windows operating system. D Data flow Identifies the data sources, movers and destinations participating in a backup, along with interconnection paths between them. Policies are assigned 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 client software is installed. Deduplication A method of reducing the amount of storage space that your organization requires, to archive data, by replacing multiple instances of identical data with references to a single instance of that data. Destination node A machine that is capable of receiving data for the purposes of archiving. This machine might be the Data Instance Director Repository, a mirror, a tape library, cloud storage or tiered storage. F Forest The collective noun used to describe a group of tree structures without a common root node. 34 Glossary

35 G Groups H Within the Node Manager window, you can assign multiple machines to one or more groups. Then, within the Data Flow window, you can assign policies the nodes within these groups en-mass. Hitachi Content Platform (HCP) An object storage system recommended for large-scale archiving. Data Instance Director keeps only the file metadata in its repository, while HCP stores the data. L License key Live backup M Master node A unique, alphanumeric code that is associated with the unique machine ID that is generated during the Data Instance Director installation. The license key must be activated in order to use the software. A backup technique that avoids the need for bulk data transfers by continuously updating the repository with changes to the source file system. This is similar to CDP but with longer retention periods and RPOs being available. Live backups perform byte level change updates whereas batch backups perform block level change updates. The machine that controls the actions of other nodes within the Data Instance Director network. Metadata Store (MDS) Records metadata that describes items that are held in repositories, tape libraries and HCP. The MDS supports indexing of stored data, thus enabling fast searches when locating data for restoration. Mover Defines the type of data movement operation to be performed between source and destination nodes, during the creation of a data flow. Batch movers perform block level data transfers on a scheduled basis, whereas continuous movers perform byte level data transfers on a near-continuous basis. Mirror movers are a specific type of continuous mover used to create uni- and bi-directional mirrors. Glossary 35

36 O Outlook form P Policy R When viewing stubbed s within Microsoft Outlook, a custom Outlook form must be installed that allows Data Instance Director to retrieve the attachment from HCP. The Outlook Form must be installed within an Organizational level Exchange Public Folder within an Exchange Public Database, so it can be accessible by all Outlook users. A configurable data protection objective that is mapped to machines or groups, and to the data management agents that implement the policy. Multiple policies can be assigned to a single node. Recovery Point Objective (RPO) The frequency at which a backup will occur. This governs the point in time to which data can be recovered should a restore be needed. Replication An operation where a copy of the data is created in another local or remote location automatically. Repository S A destination node that stores data from one or more source nodes. The Data Instance Director Repository supports live backup, batch backup, archiving, and versioning policies. Snapshot (Thin Image) A point in time copy of the data that is based on references to the original data. Source node Any node (server, workstation or virtual machine) that hosts data to be protected by Data Instance Director. The source node has an Active Data Change Agent, which is responsible for monitoring the host file system and performing the relevant actions defined by the policies. Nodes need to be configured as a source node if they need to transfer locally stored data to a destination node, or implement data tracking, blocking and auditing functions. A node can be both a source and destination simultaneously. 36 Glossary

37 Stubbing The process by which the contents of a file, body, or attachment are replaced by a reference or link that points to the copy of the data that is stored on the HCP. Synchronous replication Transactions are transferred to the remote storage device immediately and the write operation is signaled as completed only once data is confirmed as written to both primary and secondary volumes. Synchronous replication is optimal for connections with high efficiency. T Tiering Tracking V Versioning A process in which data is taken from the repository and placed into HCP, at established backup cycles. Data Instance Director can be used to track access to files or directories on any given source machine. Each time a file is accessed, a log message is generated that lists the type of access and the user who accessed the file. Only source nodes that are running on a Windows OS can be tracked. Whenever a file is saved, any changes, are recorded. For instance, when applied to office documents, every time a document is saved, the previous version is retained and indexed. This allows a history of a file to be generated, showing how the file changed over time. Glossary 37