hitachi virtual infrastructure integrator administration guidea instal l ing virtual infrastructure...

Hitachi Virtual Infrastructure IntegratorAdministration Guide

Release 3.1

MK-92HNAS003-09

© 2011, 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronicor mechanical, including copying and recording, or stored in a database or retrieval system forcommercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any suchcopy is: (i) created as an essential step in utilization of the Software as licensed and is used in noother manner; or (ii) used for archival purposes. Licensee may not make any other copies of theMaterials. “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 assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

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

Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi 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; and2. 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 besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility to obtainlicenses to export, re-export, or import the Document and any Compliant Products.

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

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

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

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

2Hitachi Virtual Infrastructure Integrator Administration Guide

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

Contents

About this document..............................................................................9Accessing product documentation............................................................................. 9Related VMware documentation ............................................................................... 9Related Hitachi NAS documentation ..........................................................................9Getting help...........................................................................................................11Comments.............................................................................................................11

1 About Hitachi Virtual Infrastructure Integrator software..................... 13Hitachi Virtual Infrastructure Integrator architecture................................................. 14Understanding the vSphere environment................................................................. 14

VMware terms and concepts..............................................................................15Virtual applications........................................................................................... 16vCenter Server................................................................................................. 17NFS file storage datastores................................................................................17Block storage datastores................................................................................... 17Block storage and ESXi host configuration.......................................................... 17VVol datastores................................................................................................ 18

About Virtual Volumes ................................................................................ 19About Storage Policy-Based Management......................................................20

Understanding the Hitachi Virtual Infrastructure Integrator environment.................... 21Hitachi Virtual Infrastructure Integrator server software...................................... 22Hitachi Virtual Infrastructure Integrator Web client plugin....................................22

About Virtual Infrastructure Integrator entities......................................................... 22Searching for entities........................................................................................ 23Hosts...............................................................................................................23ESXi Clusters.................................................................................................... 23Hitachi NAS Clusters......................................................................................... 23All VMs on Hitachi Storage.................................................................................23Datastores....................................................................................................... 23Datastore Clusters............................................................................................ 24Custom Groups of VMs and vApps......................................................................24System Groups of VMs and vApps...................................................................... 25Virtual Machines............................................................................................... 25

Virtual Machine discovery.............................................................................26Snapshot backups.............................................................................................26


Schedules........................................................................................................ 26vApps.............................................................................................................. 26File Systems.....................................................................................................27

About the Hitachi Virtual Infrastructure Integrator user interface............................... 27About entity hierarchy.......................................................................................28About the Getting Started tab............................................................................29About the Compliance Dashboard tab.................................................................30About ESXi Clusters.......................................................................................... 31About Hosts..................................................................................................... 33About Datastores..............................................................................................35About Datastore Clusters...................................................................................38About File Systems........................................................................................... 40About HNAS Clusters.........................................................................................42About All VMs on Hitachi Storage....................................................................... 43About Groups................................................................................................... 44About Virtual Machines......................................................................................46About Backups................................................................................................. 50About vApps.....................................................................................................51About Schedules...............................................................................................53About information tables................................................................................... 55About tooltips...................................................................................................55About context menus........................................................................................55Unsupported characters.................................................................................... 56

2 System requirements.......................................................................57Hardware requirements.......................................................................................... 58Operating system requirements...............................................................................58Storage software requirements................................................................................59Other software requirements.................................................................................. 59VMware requirements.............................................................................................59Command Control Interface (CCI) requirements....................................................... 60Port requirements.................................................................................................. 60Log requirements...................................................................................................61License requirements..............................................................................................61Quiescing requirements.......................................................................................... 61Firewall requirements............................................................................................. 61

3 Installing Virtual Infrastructure Integrator software........................... 63Install prerequisites................................................................................................64Install components.................................................................................................65Deployment options............................................................................................... 65Install locations......................................................................................................67Finding server install software and log files.............................................................. 68Installing Virtual Infrastructure Integrator server software.........................................68Installing Virtual Infrastructure Integrator Web client service plugin to vCenter Server............................................................................................................................ 69Upgrading Virtual Infrastructure Integrator software.................................................70Uninstalling Virtual Infrastructure Integrator............................................................ 72


4 Installing Virtual Infrastructure Integrator Web Client Plugin in vCSA.. 73Installing Web Client Plugin for Linux.......................................................................74

5 Configuring Virtual Infrastructure Integrator software........................ 77Configuration prerequisites..................................................................................... 78Minimum user rights for using vCenter.....................................................................79Using vSphere Web Client to configure Virtual Infrastructure Integrator software........80Displaying attached storage and file systems............................................................85Managing Virtual Infrastructure Integrator license keys.............................................86

Managing the demonstration license.................................................................. 86Displaying the system ID...................................................................................86Installing license keys....................................................................................... 87Expiring license keys.........................................................................................87

6 Using snapshot backup and restore for VMs...................................... 89Displaying snapshot backup details..........................................................................91Understanding quiescing before backups................................................................. 91Creating on-demand snapshot backups....................................................................92About snapshot backup schedules........................................................................... 94Snapshot backup schedule retention policies............................................................ 96Creating snapshot backup schedules....................................................................... 97Single-click direct access to VM hardware snapshots.................................................99

Directly accessing a VMDK snapshot.................................................................100About mounting VMDKs differences .................................................................100About unmounting snapshot VMDKs.................................................................101Unmounting snapshot VMDKs.......................................................................... 101Accessing snapshot VMDKs for a Windows Guest OS ........................................ 101Accessing snapshot VMDKs for a Linux guest OS (without LVM)......................... 102Accessing snapshot VMDKs for a Linux guest OS (with LVM) ............................. 103

Running pre- and post-process scripts....................................................................106Displaying snapshot backup schedule details.......................................................... 107Editing snapshot backup schedules........................................................................107Disabling snapshot backup schedules.....................................................................107Deleting snapshot backups....................................................................................108Restoring snapshot backups..................................................................................108

VVol datastore snapshot considerations............................................................ 108Restoring a snapshot backup........................................................................... 109Restoring a snapshot backup after VM migration............................................... 109

Deleting all orphan snapshot backups.................................................................... 109Snapshot backup status reports.............................................................................109

Snapshot backup report types..........................................................................110Report terminology......................................................................................... 111Viewing a report............................................................................................. 112Printing a report............................................................................................. 113

7 Using snapshot vaulting for enhanced data protection......................115About vaulting for enhanced data protection.......................................................... 116Configuring the HNAS server for vaulting............................................................... 117About the vault details..........................................................................................117


Viewing vault details.............................................................................................118

8 Backing up and recovering Virtual Infrastructure Integrator service...119Strategies for VM backup and data protection.........................................................120Recovery scenario 1 - VM has issues......................................................................121Recovery scenario 2 - VM accidently deleted.......................................................... 121Recovery scenario 3 - No VM backup is available.................................................... 122

9 Compliance dashboard for Hitachi NAS NFS best practices................123Understanding Hitachi NAS NFS best practices compliance...................................... 124Validating Hitachi NAS NFS best practices...............................................................125Identifying VM misalignment................................................................................. 125

10 Using Hitachi NAS Fast Clone......................................................... 127Cloning VMs and vApps.........................................................................................128Cloning snapshot backups to alternate locations..................................................... 128

11 Using Groups ............................................................................... 131About Groups.......................................................................................................132Viewing storage server clusters, and their nodes and datastores..............................133Viewing file system resources................................................................................134Using System Groups............................................................................................134Using Custom Groups........................................................................................... 135

Creating a group of VMs and vApps..................................................................136Editing a group of VMs and vApps....................................................................137Deleting a group of VMs and vApps..................................................................137

About the Host group in block storage configuration............................................... 137

12 Using auto-deploy for NFS datastores............................................. 139Understanding auto-deploy of NFS datastores........................................................ 140Auto-deploying NFS datastores to all ESXi hosts..................................................... 140

13 Managing logs and collecting diagnostic information........................ 143Displaying the Log Viewer.....................................................................................144Setting logging levels............................................................................................144Exporting logs......................................................................................................145Collecting diagnostic information........................................................................... 145Displaying the Event Log.......................................................................................146

Displaying Event Details.................................................................................. 146Displaying Alerts...................................................................................................147

14 Troubleshooting Virtual Infrastructure Integrator............................. 149Installation issues.................................................................................................150Configuration issues............................................................................................. 151Operations issues................................................................................................. 152


A Installing Virtual Infrastructure Integrator Command Line Interface(CLI)............................................................................................ 157

Installing Virtual Infrastructure Integrator CLI for Windows..................................... 158Installing Virtual Infrastructure Integrator CLI for Linux...........................................158

B Installing Virtual Infrastructure Integrator Command Control Interface(CCI)............................................................................................159

Installing CCI software..........................................................................................160Using CCI and HORCM as a Windows service......................................................... 160Configuring Command Devices for the Virtual Infrastructure Integrator.................... 162Using multiple HORCM files for a single Virtual Infrastructure Integrator...................163Determining presence of another CCI Command Device..........................................163Example HORCM configuration files....................................................................... 165

C Using Virtual Infrastructure Integrator Command Line Interface withVMware PowerCLI......................................................................... 167

Fast Clone script sample....................................................................................... 168Restore script sample........................................................................................... 169Snapshot backup script sample..............................................................................169

D Open source and third-party licensing.............................................171Axis2...................................................................................................................172OpenSSL..............................................................................................................172Jetty Server ........................................................................................................ 175Google Charts ..................................................................................................... 175Winsw ................................................................................................................ 175Apache 2.0 license .............................................................................................. 176Eclipse Public License Version 1.0 ......................................................................... 180

Index................................................................................................ 185


About this documentThis document provides an overview of the Hitachi Virtual InfrastructureIntegrator product. The document describes how to install, configure, andtroubleshoot the software. It also provides detailed information about how touse the product features.

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.

Related VMware documentationFor more information about VMware vSphere, refer to the vSphere 6 guidesprovided by VMware.

VMware documentation is located at: https://www.vmware.com/support/pubs/

Related Hitachi NAS documentationRelease Notes provide the most up-to-date information about the system,including new feature summaries, upgrade instructions, and fixed and knowndefects.

Hitachi NAS Administration Guides

• System Access Guide (MK-92HNAS014) Explains how to log in to thesystem, provides information about accessing the NAS server/cluster CLIand the SMU CLI, and provides information about the documentation, help,and search capabilities available in the system.

• Server and Cluster Administration Guide (MK-92HNAS010) Providesinformation about administering servers, clusters, and server farms.Includes information about licensing, name spaces, upgrading software,monitoring servers and clusters, the backing up and restoringconfigurations.

• Storage System User Administration Guide (MK-92HNAS013)• Network Administration Guide (MK-92HNAS008) Provides information

about the server's network usage, and explains how to configure networkinterfaces, IP addressing, name and directory services.

About this document 9Hitachi Virtual Infrastructure Integrator Administration Guide

https://knowledge.hds.com/Documents

https://www.vmware.com/support/pubs/


• File Services Administration Guide (MK-92HNAS006) Explains about filesystem formats, and provides information about creating and managingfile systems, and enabling and configuring file services (file serviceprotocols).

• Storage System User Administration Guide (MK-92HNAS012) Explains usermanagement, including the different types of system administrator, theirroles, and how to create and manage these users.

• Replication and Disaster Recovery Administration Guide MK-92HNAS009

Note: For a complete list of Hitachi NAS open source software copyrights andlicenses, see the System Access Guide.

Hitachi NAS Hardware References• Series 4000 Hitachi NAS Platform and Hitachi Unified Storage Series 4000

Hardware Reference (MK-92HNAS030)

Hitachi NAS Best Practices• Hitachi NAS Platform Best Practices Guide for NFS with VMware vSphere

(MK-92HNAS028) — This document covers best practices specific to usingVMware vSphere with the Hitachi NAS platform.

• Hitachi USP-V/VSP Best Practice Guide for HNAS Solutions(MK-92HNAS025) —The practices outlined in this document describe howto configure the system to achieve the best results.

• Hitachi Unified Storage VM Best Practices Guide for HNAS Solutions(MK-92HNAS026) PDF—The system is capable of heavily driving a storagearray and disks. The practices outlined in this document describe how toconfigure the system to achieve the best results.

• Brocade VDX 6730 Switch Configuration for use in an HNAS ClusterConfiguration Guide (MK-92HNAS046) This document describes how toconfigure a Brocade VDX 6730 switch for use as an ISL (inter-switch link)or an ICC (inter-cluster communication) switch.

• Hitachi NAS Platform v 12.1 HDP Best Practices (MK-92HNAS063) Thisdocument details the best practices for configuring and using storagepools, related features, and Hitachi Dynamic Provisioning (HDP).

• Hitachi NAS 12.1 HDP Best Practices (MK-92HNAS057) —This documentlists frequently asked questions regarding the use of Hitachi DynamicProvisioning.

• Hitachi Multi-tenancy Implementation and Best Practice Guide(MK-92HNAS059) —This document details the best practices forconfiguring and using Multi-Tenancy and related features, and EVSsecurity.

10 About this documentHitachi Virtual Infrastructure Integrator Administration Guide

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.

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!

About this document 11Hitachi Virtual Infrastructure Integrator Administration Guide

https://knowledge.hds.com/

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

https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]

12 About this documentHitachi Virtual Infrastructure Integrator Administration Guide

1About Hitachi Virtual Infrastructure

Integrator softwareBy integrating into the VMware vSphere virtual environment, the VirtualInfrastructure Integrator software provides data management servicesincluding managed snapshot backups, snapshot restores, and snapshotbackup scheduling operations on virtual machines (VMs) and VMwarevSphere® vApp(s)™ (vApp(s)) that are hosted exclusively on Hitachi Storagedevices. You can apply snapshot backup schedules to specific VMs andvApp(s) by grouping them according to your needs. The Virtual InfrastructureIntegrator also enables the creation of VM and vApp clones instantly, evenwhile the VMs and vApp(s) are powered on.

The software takes advantage of Hitachi NAS platforms File Clone technologyto deliver VM and VMDK hardware-level snapshot backups, which can beinstantly created or restored. The same technology is used to create efficientclones and linked-clone VMs. When configured for block storage, Hitachi ThinImage (HTI) is also supported.

Note: The Virtual Infrastructure Integrator software is now released as a 64-bit executable to support 64-bit applications. However, the VirtualInfrastructure Integrator CLIs remain at 32-bit to provide compatibility withboth platforms.

□ Hitachi Virtual Infrastructure Integrator architecture

□ Understanding the vSphere environment

□ Understanding the Hitachi Virtual Infrastructure Integrator environment

□ About Virtual Infrastructure Integrator entities

□ About the Hitachi Virtual Infrastructure Integrator user interface

About Hitachi Virtual Infrastructure Integrator software 13Hitachi Virtual Infrastructure Integrator Administration Guide

Hitachi Virtual Infrastructure Integrator architectureThe Hitachi Virtual Infrastructure Integrator architecture consists of severalcomponents working together and coordinating with VMware vSphere.

Understanding the vSphere environmentThe term vSphere is used in two ways: one is as a collective name for theVMware-based virtual environment, which includes the VMware vSphere®software, VMware® vCenter Server™ software, VMware® ESXi™ clusters andhosts managed by the vCenter Server, and the virtual machines (VMs) andVMware vSphere® vApp(s)™ hosted on those ESXi clusters. The second useof the vSphere term is as a product--vSphere is the name of the GUI for thevCenter product. The vSphere software:• Manages a large collection of physical resources, such as CPUs, memory,

storage, and networking between different locations.• Converts physical resources into a pool of dynamic virtual resources for

the computing and datacenter needs of IT organizations.• Offers a flexible, scalable, and reliable virtual environment for complex

computing needs, and for managing IT services in real-time.

See VMware documentation at https://www.vmware.com/support/pubs/ formore details.

14 About Hitachi Virtual Infrastructure Integrator softwareHitachi Virtual Infrastructure Integrator Administration Guide


A familiarity with the following vSphere subjects is necessary for a betterunderstanding of the Virtual Infrastructure Integrator application:• ESXi clusters, vApps, vCenter Server, and block and NFS datastores on

ESXi servers.• ESXi servers represent the "bare-metal" architecture, which is partitioned

into multiple VMs. These VMs can run simultaneously by sharing thephysical resource of the underlying ESXi server. Each server can beimplemented on a standalone physical machine, or on a group of physicalmachines working as a cluster with features such as high availability, loadbalancing, and so forth. These servers host VMs and vApps.

• Virtual Infrastructure Integrator works with standalone or clustered ESXiservers hosting VMs and vApps.

VMware terms and conceptsThis section briefly describes key terms and VMware environment objectsthat are relevant to the Storage Provider for file storage.

The following table describes key terms and objects:

Note: See the VMware documentation at https://www.vmware.com/support/pubs/ for more details.

Term or acronym Definition

Protocol endpoint PE. An ESXi host uses a PE as a logical I/O proxy to communicate withvirtual volumes (VVols) and the virtual machine disks (VMDKs) that theVVols contain. The PE must be accessible on the physical fabric and is usedas the data path by the ESXi host for direct access to the VVols. Theattached storage manages all other aspects of VVols.

The Storage Provider for file storage automatically creates the PEs; no useraction is required.

For a NAS file system, a PE is a fully-qualified NFS export comprised of ahost name (or IP address) and an export name.

For example: 172.19.9.160:/hnas1/test

RDM Raw Device Mapping. An RDM is a type of VMware mapping file that goes in

a VMDK volume. There are two types of RDMs, physical RDM (pRDM) and

virtual (vRDM).An RDM contains metadata required for managing and redirecting diskaccess to the physical device. The file gives you some of the advantages ofdirect access to a physical device, while still having some of the advantagesof a virtual disk in VMFS.

When you need to use raw devices, you need to use an RDM.

Note: Only Command control Interface (CCI) RDMs aresupported at this time.




Term or acronym Definition

SPBM Storage Policy-Based Management leverages the new VVol-based storage.Storage provisioning uses SPBM to match storage array capabilities toestablished VMDK profiles. See About Storage Policy-Based Management onpage 20 for more details.

Storage array A data storage system on block or file storage. In Hitachi NAS terms, a

storage array is a Hitachi NAS cluster or a single node NAS array.

Storage container A logical grouping of virtual volumes. New virtual volumes (VVols, or theirderivatives) are created inside a storage container. Consider a storagecontainer a pool of raw storage capacity or an aggregation of storagecapabilities that a storage system can provide to VVols.

Storage containers:• Are not known to protocol endpoints (PEs)• Are not discoverable using in-band means• Have two attributes: name and maximum capacity• Can be homogenous, such as high-end storage for high-performance

VVols or a mixture of storage with a wide range of VVols

VASA vSphere APIs for Storage Awareness. These APIs make possible theintegration between the vSphere, vCenter, and Hitachi NAS software, andthe backend storage. Using VASA, the storage array and its storagecontainers are presented to VMs for consumption.

VMDK Virtual Machine Disk. With the transformation of SAN and NAS storageentities into VM-centric devices, a VMDK becomes the native representationof the VM at the array level.

VMFS Virtual Machine File System. VMFS is VMware's clustered file system for

vSphere. VMFS is optimized for virtual machines and works with shared

storage to allow multiple hosts to read and write to the same storage

simultaneously.

vSphere The term vSphere is used in two ways:• The VMware vSphere product is the graphical user interface (GUI) and

management interface for working with vCenter.• The term vSphere is also used as the collective name for the VMware-

based virtual environment, which includes the VMware vSpheresoftware, VMware vCenter Server software, VMware ESXi clusters andhosts managed by the vCenter Server, and the virtual machines (VMs)and vApps hosted on those ESXi clusters.

VVol Virtual Volume. The VMware Virtual Volume (VVol) feature defines a newvirtual disk container (Virtual Volume) that is independent of the underlyingphysical storage representation, allowing for finer control. In other terms,with Virtual Volumes, the virtual disk becomes the primary unit of datamanagement at the storage level. See About Virtual Volumes on page 19

VVol datastore A VVol datastore or virtual datastore represents a storage container to thevCenter Server software. The VVol datastore defines capacity boundariesand access logic, and exposes a set of data services that are accessible tothe VMs provisioned in the pool. Virtual datastores are purely logicalconstructs.

Virtual applicationsVirtual applications (vApps) are logical entities comprising one or more VMs,which uses the Open Virtualization Format standard to specify and


encapsulate all components of a multi-tier application, as well as theoperational policies and service levels associated with it. A vApp can consistof any applications running on any OS. It provides a mechanism to move theapplications across different VMware clusters without affecting their servicelevels.

vCenter ServerThe vCenter Server provides central visibility and administration for vSpherehosts, ESXi Clusters, and VMs. Using the vSphere Web Client, you canconnect to vCenter and perform tasks such as allocating VM resources,configuring vClusters, and managing datastores. The Virtual InfrastructureIntegrator software interacts directly with vCenter when performing snapshotbackups and File Clone operations.

NFS file storage datastoresIn NFS file datastores, ESXi clusters access a designated NFS volume locatedon a NAS Server, mounts the volume, and utilizes it for its storage needs.Use NFS volumes to store and boot VMs in the same manner you use VMFSdatastores mounted on SCSI-based or SAN storage systems.

NFS file-level datastores are typically easier to setup and manage in ESXiservers because they do not require the logical configuration details thatstorage network technologies such as iSCSI and FC need. The tradeoffbetween NFS file stores and block storage is the latter is considered moreflexible, efficient, and reliable, at the expense of being somewhat morecomplicated to configure.

Important: The Virtual Infrastructure Integrator software only manages VMsthat use Hitachi Storage Services.

Block storage datastoresThe Virtual Infrastructure Integrator supports both file and block datastores.In some applications, block storage is often more efficient and flexible thanfile-based storage.

File storage has the benefit of being simpler to implement.

Block storage and ESXi host configurationWhile file-based storage can rely on IP addresses or resolved domain names,block storage requires addressing through the HBA World Wide Name (WWN)number, a unique host address usually expressed as a series of hexadecimalpairs.

For block storage-based datastores to be visible in the Virtual InfrastructureIntegrator inventory, the corresponding ESXi host must be configured withthe HBA WWN number. One way you can see this information is in theStorage Adapters hardware area, on the Configuration tab within the vSphereClient application.


Therefore, after adding the ESXi host HBA WWN number during configurationwithin the Hitachi Storage Navigator, under Storage Systems, for each host,the host group listing will have:• Port ID• HBA WWN• Host Name• Host Group Name

The following illustration shows two such ESXi block storage hosts configuredin the 4B-G00 (00) group.

Note: If the ESXi block storage host is not configured with the HBA WWNnumber, it will not be visible in the Virtual Infrastructure Integrator inventoryas an available datastore resource.

For more information, refer to the Hitachi Storage Navigator documentationand online help.

VVol datastoresThe VMware VASA 2.0 VVol (virtual volume) datastore option allows you toperform snapshots and restores at the VM-level. VVol datastores simplifystorage operations and delivery of storage service levels.


Important: Virtual Infrastructure Integrator only supports VVols for NAS(file) storage at this time.

When you create a VM and select the type of datastore in the VirtualInfrastructure Integrator, select the VVol datastore option for your storagetype.

See System requirements on page 57 for details.

About Virtual VolumesThe VMware Virtual Volumes (VVols) feature is based on a new integrationand management framework between the vSphere product software and astorage system (storage array).

The VVols technology virtualizes SAN and NAS devices by abstracting physicalhardware resources into logical pools of capacity (called virtual or VVoldatastores). These pools can be more flexibly consumed and configured tospan a portion of one or several storage arrays. VVols implements an out-of-band bidirectional control path through the vSphere APIs for StorageAwareness (VASA) and leverages unmodified standard data transportprotocols for the data path, for example NFS, iSCSI, and Fibre Channel.

On the array side, two new components are added to the storageenvironment: VASA Storage Provider for integration with the VASA APIs, andProtocol Endpoints (PE), which allow the storage controller to direct I/Os tothe correct virtual volumes.

On the vSphere product, there are three dependent features: VASA, VVols,and Storage Policy-Based Management (SPBM). To create policies at thevSphere level, a set of published capabilities must first be defined in thestorage array. Then, once defined, these capabilities are surfaced up tovSphere using the VASA Provider.

The virtual datastore defines capacity boundaries and access logic, andexposes a set of data services that are accessible to the VMs provisioned inthe pool. Virtual Datastores are purely logical constructs that can beconfigured as needed, without disruption or the requirement of a formattedfile system.

A VVol is defined as a new virtual disk container that is independent of theunderlying physical storage representation, thereby allowing for finer control.In other terms, with VVols, the virtual disk becomes the primary unit of datamanagement at the array level. This model turns the Virtual Datastore into aVM-centric pool of capacity. It then becomes possible to execute storageoperations with VM granularity and to provision native array-based dataservices to individual VMs. This capability allows administrators to provide thecorrect storage service levels to each individual VM.

Using the VVols feature can help you:• Simplify storage operations


○ Separation of consumption and provisioning○ End-to-end visibility

• Simplify delivery of storage service levels○ Finer control, dynamic adjustment○ Improved resource utilization○ Maximized storage offload potential

The VVols feature offers the following scalability:• Snapshots:

○ For Hitachi NAS, up to 100 million snapshots and clones• VVols:

○ For Hitachi NAS, up to 400,000 VVols initially, with architectural supportfor 10 million VVols

○ For Hitachi Virtual Storage Platform (VSP) G1000, 64,000 VVols, 1million snapshots or clones

About Storage Policy-Based ManagementStorage Policy-Based Management (SPBM) can be viewed as efficientoperations through automation. To enable efficient storage operations atscale, even when managing thousands of VMs, VVols uses vSphere SPBM.SPBM is the implementation of the policy-driven control plane in the VMwareSoftware Defined Services (SDS) model.

SPBM allows capturing storage service levels requirements (capacity,performance, availability, and so on) in the form of logical templates(policies) to which VMs are associated. SPBM automates VM placement byidentifying available datastores that meet policy requirements, and, coupledwith VVols, SPBM dynamically instantiates the necessary data services.Through policy enforcement, SPBM also automates service level monitoringand compliance throughout the life cycle of the VM.


Understanding the Hitachi Virtual Infrastructure Integratorenvironment

The Virtual Infrastructure Integrator product uses a server component and aWeb client service plugin component for configuration and managingfeatures. These components can exist on the same or different physicalmachines. Each component has an installer. If the Virtual InfrastructureIntegrator server is installed on the vCenter Server, then the VirtualInfrastructure Integrator Web client service plugin is already installed. If not,then the Virtual Infrastructure Integrator Web client service plugin must beinstalled on the vCenter Server.


Hitachi Virtual Infrastructure Integrator server softwareThe Virtual Infrastructure Integrator server software has a single instancethat performs the following:• Communicates with the vCenter Server to retrieve information about

existing ESXi hosts and ESXi Clusters.• Communicates directly with Hitachi Storage Services to perform file

system snapshot and File Clone operations on VMs hosted on HitachiStorage Services.

• Stores the Virtual Infrastructure Integrator configuration information,including VM backup data, schedules, and logs.

• Runs as a service that starts automatically when the host machine starts.

Hitachi Virtual Infrastructure Integrator Web client pluginThe Virtual Infrastructure Integrator Web client plugin installs within vCenter,and serves up the Virtual Infrastructure Integrator user interface. The pluginprovides an interface for all storage operations and configurations that areperformed by the Virtual Infrastructure Integrator server.

About Virtual Infrastructure Integrator entitiesThe following entity types display as nodes in the Virtual InfrastructureIntegrator application:• ESXi Clusters on page 23 (virtual clusters)• Hosts on page 23• Datastores on page 23• Datastore Clusters on page 24• File Systems on page 27


• Hitachi NAS Clusters on page 23• All VMs on Hitachi Storage on page 23• Custom Groups of VMs and vApps on page 24 (user-defined groups)• System Groups of VMs and vApps on page 25 (pre-defined groups)• Virtual Machines on page 25• Snapshot backups on page 26 (snapshot backups)• vApps on page 26 ( container that contains one or more virtual

machines)• Schedules on page 26

Searching for entitiesTo search for entities in Virtual Infrastructure Integrator, use the vSphereWeb Client filter field.

HostsA VMware® ESXi™ host, called here a Host, is an ESXi server that isconfigured to provide centralized resource availability to host VMs and vApps.An ESXi host is implemented as a standalone physical machine .

ESXi ClustersA VMware® ESXi™ Cluster, called here an ESXi Cluster, is a collection of ESXiservers that are configured to work together as a unit, providing centralizedresource availability to host VMs and vApps. An ESXi Cluster may beimplemented as a standalone physical machine or as a cluster of physicalmachines with support for load balancing and high availability features.

ESXi Clusters are the core of high availability in VMware virtualinfrastructures. The ESXi Clusters enable VMs and vApps to be dynamicallymigrated between hosts in the event of a hardware or software failure.

Hitachi NAS ClustersThe Hitachi NAS clusters entity grouping allows you to view the clusters ofHitachi NAS nodes. This capability gives you greater visibility in to theinterdependence of VMs to particular Hitachi NAS clusters.

All VMs on Hitachi StorageThe All VMs on Hitachi Storage entity grouping allows you to view all of theexisting VMs that reside on Hitachi storage systems. This capability gives yougreater visibility in to the interdependence of VMs to particular Hitachi NASclusters.

DatastoresThe VMware software perceives a Virtual Infrastructure Integrator datastoreentity as a normal datastore, and the nested individual datastores as nodes.


The Virtual Infrastructure Integrator client GUI lists all datastores that arehosted on Hitachi Storage Services regardless whether the datastore containsVMs.

Datastore ClustersThe Virtual Infrastructure Integrator datastore clusters entity grouping allowsyou to view all of the Integrator's datastore clusters in a single place.

Just as the VMware software perceives Virtual Infrastructure Integratordatastore entities as normal datastores, the software perceives VirtualInfrastructure Integrator datastore cluster entities as normal datastoreclusters. The software also perceives both of their nested individualdatastores as nodes.

The Hitachi Virtual Infrastructure Integrator client GUI lists all datastoreclusters that are hosted on Hitachi Storage Services regardless whether thedatastores contain VMs.

Datastore cluster characteristics:• Can be of NFS type and VMFS type• If a datastore cluster contains one or more non-qualified datastores, then

the datastore cluster is not qualified• Maximum of 32 datastores per datastore cluster• Datastores can be added to an existing datastore cluster• Datastore cannot exist in more than one datacenter in the same instance

of the vSphere Web Client• If a datastore is removed from a datastore cluster, the datastore remains

in the vSphere Web Client inventory and is not unmounted from the host• All hosts attached to the datastore must be running ESXi 5.0 or later

To perform successfully, datastore clusters must contain similar orinterchangeable datastores. While datastore clusters can contain a mixture ofdatastores with different sizes and I/O capacities, there are other exceptions.

Important: The following types of datastores cannot coexist in a datastorecluster:• NFS and block datastores cannot be combined in the same datastore

cluster.• VVOL datastores cannot be created as a datastore cluster (unsupported by

VMware).• Replicated datastores cannot be combined with non-replicated datastores

in the same storage-DRS-enabled datastore cluster.

Custom Groups of VMs and vAppsCustom Groups are basically customizable groups, allowing you to edit thegroup and select which VMs you want contained in the group. This grouping


allows you to manually group a set of VMs on the same file system or a set ofvApps that are related.

Additional pre-defined System Groups are available and are automaticallypopulated by the Virtual Infrastructure Integrator server based on availabledatastores. These additional groups provide the ability to visualize where VMsare located on Hitachi storage. This type of VM visualization allows you todevelop non-conflicting backup schedules to ensure optimum systemperformance.

Using Virtual Infrastructure Integrator, you may create custom groups of VMsand vApps from the All VMs on Hitachi Storage group, and then manage thegroups in real-time.

Group-level operations include:• Creating, editing, deleting, enabling, and disabling snapshot backup

schedules.• Creating on-demand snapshot backups of an entire group.• Editing a group by adding or removing VMs and vApps, or changing the

group details.• Deleting a custom group.

System Groups of VMs and vAppsSystem Groups are pre-defined groups for VMs and vApps that areautomatically populated by the Virtual Infrastructure Integrator Server whenthe inventory is retrieved from the vCenter Server.

System Groups provide the ability to visualize where VMs are located onHitachi storage. This type of VM visualization allows you to develop non-conflicting backup schedules to ensure optimum system performance.

If you have VMs hosted on VVol Datastores, these groups contain VMs andare grouped based on Snapshot Backup Importance capability values.

The available capability values are: Critical, Important, Best Effort, and None,with Critical being the default value. The group None contains VMs that haveno snapshot backup class capability assigned.

Virtual MachinesVirtual machines (VMs) are software representations of physical hardwarethat run an operating system and provide services to the enterprise throughsoftware applications. In the Virtual Infrastructure Integrator software, theVirtual Machines entity is the basic entity on which snapshot backups andFast Clone operations are performed.

Virtual Machine entity-level operations in Virtual Infrastructure Integratorsoftware include:• Creating, editing, deleting, enabling, and disabling snapshot backup

schedules.• Creating on-demand snapshot backups.


• Creating a VM clone using Fast Clone.• Restoring a VM to a previous state using an available snapshot backup

under the VM.

Note: Virtual Machines (VMs) that are hosted on both File and Block serversare not managed by the Virtual Infrastructure Integrator plugin. Therefore,such VMs are not listed in the Virtual Infrastructure Integrator inventory.

Virtual Machine discoveryThe Virtual Infrastructure Integrator software discovers all virtual machines(VMs) and vApps registered with the vCenter Server. However, the VirtualInfrastructure Integrator software only displays and supports VMs and vAppson supported Hitachi storage platforms.

The virtual hard disk (VHD) defined for the VM or vApp might not display ifone or more VHDs are not based on a NAS Platform.

Note: VMs that are on migrated or archived file systems must first bereverse-migrated before you can use the backup or Fast Clone features.

Snapshot backupsSnapshots are a storage-efficient copy of a VM or vApp for backup. A groupor vApp snapshot backup consists of snapshot backups of each VM containedin the group or vApp. All available snapshot backups display as subnodesunder the respective VM nodes in the navigation tree.

Snapshot backup is possible on VMs, vApps, and groups of VMs and vApps.On-demand snapshot backups provide an instant snapshot backup of aselected target. Scheduled snapshot backups are generated by the VirtualInfrastructure Integrator software based on the configured schedule.

Orphan snapshot backups can exist on Hitachi storage and are associatedwith deleted VMs.

SchedulesThe Schedules entity grouping allows you to view the existing snapshotbackup schedules.

When you select Schedules, any configured schedule objects are displayed.

vAppsA vApp is a logical group of VMs working together as an enterpriseapplication. It can include any number of applications running on differentVMs without affecting their service levels. A vApp can have sub-vAppsrunning under it.

The vApp-level operations include:


• Creating, editing, deleting, enabling, and disabling snapshot backupschedules.

• Creating on-demand snapshot backups.• Restoring a vApp to a previous state using an available snapshot backup.• Creating a vApp clone using File Clone.

File SystemsThe File Systems entity provides a grouping of VMs by shared file systems,which gives you greater visibility in to the interdependence of VMs to sharedfile systems. This visibility can assist you in the operational placement ofVMs.

About the Hitachi Virtual Infrastructure Integrator userinterface

The Virtual Infrastructure Integrator interface displays when you launch theapplication by clicking the Hitachi Storage Services icon in the vSphere WebClient interface.


Item Component Description

1 Navigation

pane

Left pane in the UI. Contains the Hitachi Virtual Infrastructure Integrator

navigation tree (inventory list). This is a collection of entities from a

vSphere and Hitachi Storage Services platform storage perspective.

2 Information

pane

Center pane in the UI. Initially shows the Getting Started tab and

Compliance Dashboard tab, as well as the Configure Hitachi Virtual

Infrastructure Integrator button (depending on your browser window size,

it may be necessary to scroll down to view the button). When you select an

entity, the pane displays information on that object and its related objects.

3 Toolbar At the top of the center pane of the UI, the toolbar includes access to

frequently required operations, and the online help. Different buttons come

available based on the node selected. The scope of operations initiated

from the toolbar is limited to the selected node.• About License• Alerts• Refresh• Help• About Storage Services Plugin• View Logs• Logging Level• Collect Diagnostic Information• Reports

4 Tasks and

Alarms panel

Right pane of the UI. Contains sections that display information about the

following:• Recent Tasks, including status• Work in Progress• Alarms

About entity hierarchyThe Virtual Infrastructure Integrator (Hitachi Storage Services) navigationtree (inventory list) displays all supported entities hierarchically.

Entity types Sub-entities

Hitachi Storage Services (rootnode)

No sub-entities

ESXi Clusters All ESXi clusters

Hosts All available ESXi hosts

Datastores All available datastores

Datastore Clusters All available datastore clusters

File Systems All available file systems where datastores are present

Hitachi NAS Clusters All Hitachi NAS clustered nodes attached to ESXi hosts

All VMs on Hitachi Storage All VMs, vApps, and Schedules on Hitachi storage, per HitachiNAS node or cluster

Custom Groups User defined groups of VMs


Entity types Sub-entities

System Groups Pre-defined groups

Virtual Machines All Virtual Machines present on Hitachi storage

Backups All snapshot backups available for the selected VM

vApp All VMs and vApps within the vApp

Schedules All available snapshot backup schedules

About the Getting Started tabThe Getting Started tab in the task pane provides an overview of the mainfeatures of the Hitachi Virtual Infrastructure Integrator software. The tab alsoincludes a toolbar of buttons for high level options, and also contains theConfigure Hitachi Virtual Infrastructure Integrator button.

The overview describes the features and the icons used to represent them. Itshould be noted that the overview is informational only.

Icon Feature

Snapshot Backup

Schedule Snapshot Backup

Snapshot Restore

Snapshot Vaulting

Create Group

Fast Clone

The toolbar option buttons include the following:

Button Option Description

About License Opens the License dialog where you can view or enter the

license number.

Alert Opens the Alerts details screen, where you can refresh,

view, refresh, acknowledge, and export alert information.


Button Option Description

Reports Allows you to view and print reports.

Refresh Refreshes the data that displays in a screen with the most

current values.

Help Opens the Virtual Infrastructure Integrator online help

system.

About Hitachi Storage

Services Plugin

Displays version information about the Virtual

Infrastructure Integrator components that are installed.

View Logs Opens the Log viewer, where you can refresh, view, and

export log information.

Logging Level Allows you to set the level for logging information to

normal, additional info, or detailed info.

Collect Diagnostic

Information

Launches a page for collecting diagnostic logs and other

configuration information to aid in troubleshooting or for

submission to HDS Support.

About the Compliance Dashboard tabThe Hitachi NAS NFS Best Practices Compliance Dashboard tab in the taskpane displays information about the Hitachi Virtual Infrastructure Integratorenvironment configuration. The dashboard enables Hitachi Storage Servicesand VMware customers to confirm they have configured their environmentoptimally for Hitachi Storage Services as a shared storage resource.

The Virtual Infrastructure Integrator software can run validation checking andreport findings. You can then choose to manually respond by making therecommended configuration changes.

The Compliance Dashboard has tabs that provide information for non-compliant entities. The tables are unpopulated when all entities arecompliant.


Compliance is monitored for the following entities:

Note: The Hitachi NAS NFS Best Practices Compliance Dashboard applies toHitachi NAS (HNAS) file storage, not block storage configurations.

Item Description

Hosts tab • List of Hosts• Best Practices Parameters• Details

HNAS Storage Servers tab • List of Hosts• Best Practices Parameters• Details

Datastores tab • List of Hosts• Best Practices Parameters• Details

Check VM Alignment tab • Misaligned VM Details

About ESXi ClustersWhen you select ESXi Clusters any configured ESXi Cluster objects aredisplayed.


For ESXi Cluster resources, the Objects tab displays:

Item Description

Name The name of the ESXi Cluster

Path The path where the cluster is located

Hosts The number of hosts associated with the cluster

When you select a specific ESXi Cluster resource, the Summary tab displays:

Item Description

Name of the ESXi resource Name of the resource

Path Path to the resource

Number of hosts associated with

the resource

How many hosts are associate with the resource

A formatted table listing storage

information details (if available),

including:

• Storage address• Platform• Version• File systems


The Related Objects tab displays:

Item Description

Datastores • Name• Device• Free Space• Block Size• Total Space• File System Name• LUN

Virtual Machines • Name• Last Backup Time• Age of Last Backup• Backups• Next Backup Time• Schedules• Guest OS• Datastore

vApps • Name• Description• ESXi Host• Virtual Machines• Storage Device

Schedules • Name• Entity Name• Next Backup Time• Type• Status• Last Backup Time• Entity Type• Description

Hosts • Host Name• Virtual Machines

About HostsWhen you select Hosts, any configured Hosts objects display.

For Hosts resources, the Objects tab displays:


Item Description

Host Name Configured name of the host

Virtual Machines Number of virtual machines configured on each host

When you select a specific Host resource, the Summary tab displays.

Item Description

Host Name Name of the Host resource

Virtual Machines Number of virtual machines on the host

Storage Info. A formatted tablelisting storage information details(if available), including:

• Storage Address• Platform• Version• File Systems

If you select the Related Objects tab, buttons allow you to view:

Item Description


Virtual Machines • Name• Last Backup Time• Age of Last Backup• Backups• Next Backup Time• Schedules• Guest OS


Item Description

• Datastore



About DatastoresWhen you select Datastores, any configured datastore objects display.

For Datastore resources, the Objects tab displays:

Item Description

Name Name of the datastore

Device Device on which the datastore is located

Free Space Amount of free space available on the device

Block Size Block size used by the datastore

Total Space Total configured space on the datastore


Item Description

File System Name Name of the installed file system, or N/A if not applicable

LUN Logical unit number

When you select a specific Datastore resource, the Summary tab displays.

Note: The information shown varies depending on whether the datastore isusing file or block storage. The items displayed are similar for file and block,but block has an additional table.

For both file and block storage, the following Summary information displays:

Item Description

Name Name of the datastore resource

ESXi Host Name Name of the ESXi host

Location Location of the datastore

Formatted table listing systeminformation details (if available),including:

• File System• EVS IP• Free Space• Block Size• VMs• Datastores• File System Type

Formatted table listing Scheduled VMbackup information (if available),including:

• Scheduled Backups Count at Group Level• Last Backup Time• Next Backup Time


Item Description

• Scheduled Backups at Item Level

For block storage systems, anadditional formatted table listing:

• Host Name• Serial Number• HORCM Instance• Microcode Version• Host WWN• Host WWPN• Host LUNID• Storage WWN• Storage WWPN• LDEVID• LDEV Name• LDEV Host Group Name• LDEV Port ID

If you select the Monitor tab for a datastore resource object, you can viewevents associated with the resource listing:

Item Description

Start Time Time when the event began

Completed Time Time when the event ended

Status Status of the event

Operation Operation being performed when event occurred

Operation details Details about the operation being performed


Item Description




About Datastore ClustersWhen you select Datastore Clusters, any configured datastore cluster objectsdisplay.

For datastore cluster resources, the Objects tab displays:

Item Description

Name Name of the datastore cluster

Total Space Total amount of space available on the device


Type Type of datastore cluster: NFS (file), VMFS (block), VVol

No. of Datastores Number of datastores in each datastore cluster

File System Name Name of the installed file system, or N/A if not applicable

When you select a specific Datastore Cluster resource, the Summary tabdisplays.

Note: The information shown varies depending on whether the datastorecluster is using file or block storage. The items displayed are similar for fileand block, but block has an additional table.


For both file and block storage, the following Summary information displays:

Item Description

Name Name of the datastore resource

Total Space Total space available to the datastore cluster

Used Space Total space used by the datastore cluster


Type Storage type

No. of Datastores Number of datastores in the cluster

Location Location of the datastore

If available, a formatted table listing filesystem information details, including:

• File System• EVS IP• Free Space• Block Size• VMs• Datastores• File System Type

If available, a formatted table listingScheduled VM backup information,including:

• Scheduled Backups Count at Group Level• Last Backup Time• Next Backup Time• Scheduled Backups at Item Level

For block storage systems, an additionalformatted table listing, including:

• Host Name• Serial Number• HORCM Instance• Microcode Version• Host WWN• Host WWPN• Host LUNID• Storage WWN• Storage WWPN• LDEVID• LDEV Name• LDEV Host Group Name• LDEV Port ID

If you select the Related Objects tab, the following displays:


Buttons allow you to view:

Buttons Fields




About File SystemsWhen you select File Systems, any configured file systems objects aredisplayed.

For file systems resources, the Objects tab displays:


Item Description

Name Name of the file system

EVS IP Address EVS IP address(es) associated with the file system

Virtual Machines Number of virtual machines on the file system

Datastores Number of datastores on the file system

Free Space Amount of free space available on the file system

Block Size Configured block size of the file system

File System Type Type of file system configured

When you select a specific file system resource, the Summary tab displays,duplicating the table information from the Objects display.

If you select the Related Objects tab, you can view any associateddatastores:

Item Description

Name Name of the datastore

Device Device on which the datastore is located


Block Size Block size used by the datastore

Total Space Total configured space on the datastore

File System Name Name of the installed file system, or N/A if notapplicable

LUN Logical unit number


About HNAS ClustersWhen you select HNAS Clusters, any configured HNAS Cluster objects aredisplayed.

For HNAS Cluster resources, the Objects tab displays:

Item Description

HNAS Cluster Name Name of the HNAS Cluster

Cluster IP Address IP address where the cluster is located

Clustered Yes or No

Nodes Number of nodes associated with the cluster

Health Status message indicating the health of the HNASCluster

When you select a specific HNAS Cluster resource, the Summary tabdisplays:

Item Description

Name Name of the HNAS Cluster

Cluster IP Address IP address where the cluster is located

Nodes Number of nodes associated with the resource


If you select the Related Objects tab, buttons allow you to view HNAS Nodesinformation, including:

Item Description

Host Name Name of the host

IP Address IP address where the host is located

Name

Status Status of the host

Model Model of the host

Firmware Version of the firmware

About All VMs on Hitachi StorageWhen you select All VMs on Hitachi Storage any configured objects aredisplayed.

For All VMs on Hitachi Storage resources, the Objects tab displays:

Item Description

Name Name of the All VMs on Hitachi Storage resource

ESXi Host Name Name of the ESXi Host Name resource

Description Description of the All VMs on Hitachi Storage resource

When you select a specific resource, the Summary tab displays, listing thesame Name, ESXI host name, and Description, as well as a formatted tablelisting scheduled VM backup information, if available, including:


Item Description

Name Name of the All VMs on Hitachi Storage resource

ESXi Host Name Name of the ESXi Host Name resource

Description Description of the All VMs on Hitachi Storage resource

Formatted table listing scheduled VMbackup information, if available,including:



Item Description




About GroupsThere are now two types of Groups: System Groups and Custom Groups.


When you select System Groups or Custom Groups, any configured Groupsobjects are displayed.

For Groups resources, the Objects tab displays:

Item Description

Name Name of the group

Description Description of the group, if available

When you select a specific resource, the Summary tab displays, listing thesame Name and Description, as well as a formatted table listing scheduledVM backup information, if available, including:

Item Description





If you select the Monitor tab for a Groups resource object, you can viewevents associated with the resource, listing:


Item Description







Item Description




About Virtual MachinesWhen you select Virtual Machines, any configured Virtual Machine (VM)objects are displayed.

Note: Virtual Machines (VMs) that are hosted on both File and Block serversare not managed by the Virtual Infrastructure Integrator plugin. Therefore,such VMs are not listed in the Virtual Infrastructure Integrator inventory. Thisissue can occur in the following scenarios:• If you have a VM that is hosted on local datastore and then add another

datastore that is from file (NAS) or block storage.• If you have NFS exports and a block datastore in your environment and

then create a VM that has hard disks from both file and block storageservers.

For Virtual Machine resources, the Objects tab displays:


Item Description

Name Name of the VM

Last Backup Time Time the last backup occurred

Age of Last Backup How old the back up is in hours and minutes

Backups Number of backups

Next Backup Time Time of next scheduled backup

Schedules Number of schedules associated with each VM

GuestOS Operating system being hosted on the VM

Datastore Datastore being used for the VM


When you select a specific Virtual Machine resource, the Summary tabdisplays. The information shown will vary depending on whether the VM ishosted using file or block storage. The items displayed are similar for file andblock, but block has an additional table.

For file and block storage, the information shown is:


Item Description

Name Name of the VM

GuestOS Operating system used for the GuestOS

VM IP Address IP Address of the VM

VM Computer Name Name of the computer where the VM resides

Storage Type Type of file system used on the storage, for example,VMFS

Parent Info - If available, a formattedtable listing parent information details,including:

• ESXi Host• Storage Server

Backup Info - If available, a formattedtable listing backup information,including:

• Last Backup Time• Next Backup Time• Oldest Backup Time

Description - If available, a formattedtable listing description information,including:

• VM Description

Related Objects Info - If available, aformatted table listing related objectsinformation, including:

• Backup Count• Schedule Count• Datastore• Group

Block Storage Details - For block storage,the Summary information shown alsoincludes a formatted table listing:

• Host Name• Serial Number• HORCM Instance• Microcode Version• Host WWN• Host WWPN


Item Description

• Host LUNID• Storage WWN• Storage WWPN• LDEVID• LDEV Name• LDEV Host Group Name• LDEV Port ID

If you select the Monitor tab for a Virtual Machine resource object, you canview events associated with the resource, listing:

Item Description







Item Description

Backups • Backup Name• Entity Name• Age• Creation Timestamp• Backup Type• Backup ID• Description


Item Description

• Schedule Name• Datastore



About BackupsWhen you select the Backups resource, a list of current backups is displayed.

The Summary tab in the task pane displays information about the selectedbackup, as well as any available actions.

Note: The sections and fields displayed depend on whether the backupresource is on file or block storage. The items displayed are similar for fileand block, but block has an additional table.


For file or block backup resources, the Summary tab displays:

Item Description

Backup ID ID of the backup

Host IP Address IP address of the host

Description Description of the backup (for example, "Every hour")

Age Age of the last backup performed

Creation Timestamp Creation timestamp of the last successful snapshotbackup

Entity Name Name of the entity

A formatted table listing all current filestorage backups

If available, a formatted table listing allcurrent block storage backups

• Serial number• Host LUNID• S-VOL• LDEVID• HTI Pool ID• HTI Pool Name• HTI Pool Capacity Total• HTI Pool Capacity Free

About vAppsWhen you select vApps any configured vApp (virtual application) objects aredisplayed.

For vApps resources, the Objects tab displays:


Item Description

Name Name of the vApp

Description Description of the vApp, if needed

ESXi Host IP Address of ESXi Host

Virtual Machines Number of virtual machines

Storage Device Number of storage devices

When you select a specific vApps resource, the Summary tab displays,showing:

Item Description

Name of the vApp Name of the vApp

Description Description of the vApp, if needed

ESXi host name IP Address of ESXi Host

Virtual Machines Number of virtual machines

Storage Device Number of storage devices

If you select the Monitor tab for a vApps resource object, you can viewevents associated with the resource, listing:

Item Description





Item Description


Operation Details Details about the operation being performed


Item Description



Backups • Backup Name• Entity Name• Age• Creation Timestamp• Backup Type• Backup ID• Description• Schedule Name• Datastore


About SchedulesWhen you select Schedules, any configured schedule objects are displayed.

For Schedules resources, the Objects tab displays:


Item Description

Name Name of the schedule



Type Type of schedule, for example, WEEKLY

Status Status of the schedule, for example, Schedule Disabled


Entity Type Type of entity, for example, Dynamic Group

Description Description of the schedule, if needed

When you select a specific Schedules resource, the Summary tab displays:

Item Description

Name Name of the schedule


Entity Type Type of entity, for example, Dynamic Group

Description Description of the schedule, if needed

Type Type of schedule, for example, WEEKLY




If you select the Monitor tab for a Schedules resource object, you can viewevents associated with the resource, listing:

Item Description

Start Time Time when the schedule began

Completed Time Time when the schedule ended


Operation

Operation Details

About information tablesThe Virtual Infrastructure Integrator application displays relevant informationin tables. The columns and information in the tables varies depending onwhat type of component or resource is being shown. The tables provide thefollowing capabilities:

Action Description

Sorting Helps locate specific records. Successively clicking a column heading toggles the

data in ascending or descending order.

Moving columns Drag and drop the column headings to the desired location in the table.

Resizing columns Resize by selecting and dragging the column header borders.

Scrolling Horizontal and vertical scroll bars display automatically if the information does

not fit within the limits of the table.

About tooltipsWhen a field does not fit within the limits of the navigation pane, mouse overthe field to display a tooltip with the entire contents.

About context menusThe context menu displays when you right-click a VM in the NavigatorInventory list. The context menu offers quick access to the operations at thatnode level.


Unsupported charactersThe Virtual Infrastructure Integrator and vSphere applications do not supportthe use of certain characters. Do not use these characters in the names ofany objects, including virtual machines, clusters, datastores, groups,backups, objects, schedules, clones, folders, or files.

The unsupported characters are:

Symbol Description

% Percent

& Ampersand

^ Caret

* Asterisk

$ Dollar

# Number

@ At symbol

! Exclamation point

/ Forward slash

\ Back slash

: Colon

; Semicolon

? Question mark

' Single quote

" Double quote

< Less than

> Greater than

| Pipe

+ Plus sign


2System requirements

This section describes the requirements for successfully using the VirtualInfrastructure Integrator software product.

Note: The Virtual Infrastructure Integrator software is a 64-bit executable.However, the Virtual Infrastructure Integrator CLIs are 32-bit to providecompatibility with both 32-bit and 64-bit platforms.

□ Hardware requirements

□ Operating system requirements

□ Storage software requirements

□ Other software requirements

□ VMware requirements

□ Command Control Interface (CCI) requirements

□ Port requirements

□ Log requirements

□ License requirements

□ Quiescing requirements

□ Firewall requirements

System requirements 57Hitachi Virtual Infrastructure Integrator Administration Guide

Hardware requirementsThe Virtual Infrastructure Integrator product supports the following hardware.

Note: The Virtual Infrastructure Integrator product does not supportvirtualized or external storage.

File storage Block storage

Hitachi NAS Platform: 3080 and 3090,4060, 4080, and 4100

N/A

Hitachi Virtual Storage Platform VSP SeriesG (VSP G400, G600, G800) and Series F(F400, F600, F800) fitted with NAS module

Hitachi Virtual Storage Platform (VSP), VSP Series G(VSP G200, G400, G600, G800, G1000, or G1500)and Series F (Fx00), Hitachi Unified Storage VM(HUSVM)

Operating system requirementsThe Virtual Infrastructure Integrator product requires the following operatingsystems.

Important: The Virtual Infrastructure Integrator software supports only 64-bit Windows versions.

Deployment model Supported OS

Single system setup: MicrosoftWindows®

Virtual Infrastructure Integrator server:• Windows Server 2008 SP 2• Windows Server 2008 R2• Windows Server 2008 R2, SP 1• Windows Server 2012• Windows Server 2012 R2• Windows Server 2016

Single system setup: Linux Not supported

Distributed setup: Windows Virtual Infrastructure Integrator web client:• Windows Server 2008 SP 2• Windows Server 2008 R2• Windows Server 2008 R2, SP 1• Windows Server 2012• Windows Server 2012 R2• Windows Server 2016

Virtual Infrastructure Integrator server:• Windows Server 2008 (Standard, Enterprise, Datacenter)• Windows Server 2008 R2• Windows Server 2012• Windows Server 2012 R2

58 System requirementsHitachi Virtual Infrastructure Integrator Administration Guide

Deployment model Supported OS

• Windows Server 2016

Distributed setup: Linux Virtual Infrastructure Integrator web client:• VMware vCenter Server Virtual Appliance 5.5 and later

Virtual Infrastructure Integrator server:• Windows Server 2008 (Standard, Enterprise, Datacenter)• Windows Server 2008 R2• Windows Server 2012• Windows Server 2012 R2• Windows Server 2016

Storage software requirementsThe Virtual Infrastructure Integrator product requires the following storagesoftware.

Item Storage firmware

Hitachi File Storage Hitachi NAS Platform OS 12.2.3753.08 or later

Hitachi VSP G400, G600, G800with NAS module

Hitachi NAS OS 12.6.4150.08 or later

Supported Hitachi block storageplatforms

• VSP 70-06-33-00/00 or later• HUS-VM 73-03-42-00/00 or later• VSP G1000 80-03-30-00/00 or later• Hitachi Virtual Storage Platform (VSP G200, VSP G400, VSP

G600, VSP G800) 83-01-24-(40/60)/00 or later• VSP G1500 80-05-01-00/00 or later

Other software requirementsThe Virtual Infrastructure Integrator product supports the following Hitachiproduct software.

Item File storage Block storage

Hitachi Storage Provider for vCenter (VASA) 3.3.0.5664 or later Not supported

VMware requirementsThe Virtual Infrastructure Integrator product requires the following VMwaresoftware.

See VMware documentation at https://www.vmware.com/support/pubs/ fordetails.




VMware vCenter and vCenter required components 5.5, 6.0 5.5, 6.0

VMware vSphere and VMware vSphere Web Client

required components

5.5, 6.0 5.5, 6.0

VMware VVol datastores 6.0 Not supported

VMware vCenter Server Appliance 5.5, 6.0 5.5, 6.0

VMware vCenter Server Appliance VVol datastores 6.0 Not supported

Command Control Interface (CCI) requirementsThe Virtual Infrastructure Integrator product requires the following HitachiCCI software.


Command Control Interface software versions N/A 1-35-03/04 or later

CCI for VSP G1500 N/A 01-39-03/04 or later

Port requirementsThe Virtual Infrastructure Integrator product has the following portrequirements.

Port Description

8443 Port used for the Virtual Infrastructure Integrator server to register the VirtualInfrastructure Plugin with the vCenter Server.

The setting is configurable during installation.

Typically, port 8443 is the default port for Virtual Infrastructure Integrator Webserver communication.

11443

(alternate)

When port 8443 is already in use, use port 11443 as the default port for Virtual

Infrastructure Integrator Web service communication. (Port 8443 would already be

in use if you have installed the Virtual Infrastructure Integrator server on the

vCenter server.)

9000 Port used by the Virtual Infrastructure Integrator server to communicate with the

Virtual Infrastructure Integrator Web client service plugin. Configurable in the

Virtual Infrastructure Integrator server Hitachi Storage Service ServerConfiguration screen.


Log requirementsThe Virtual Infrastructure Integrator product has the following logrequirements.

Collecting diagnostic logs requires 1 GB of space as a minimum. An errordisplays if you attempt to collect logs when there is insufficient disk space.

License requirementsThe Virtual Infrastructure Integrator product has the following licenserequirements.

In addition to the requisite Virtual Infrastructure Integrator license, thefollowing licenses are also required:• Hitachi NAS Platforms: File Clone license enabled or FSRS (FS Recover

from Snapshot) license enabled.• Hitachi Block Storage Platforms: Hitachi Dynamic Provisioning (HDP) and

Hitachi Thin Image (HTI) licenses.

Quiescing requirementsThe Virtual Infrastructure Integrator product has the following quiescingrequirements.

Important: If you use the VMware VM quiesce option as part of your backupstrategy, you must install VMware Tools version 10.0.9 or later on each VM.

Firewall requirementsThe Virtual Infrastructure Integrator product has the following firewallrequirements.

There are cases when firewall requirements come into play, for example:• Distributed setups, where the vCenter Server and the Virtual

Infrastructure Integrator server software are installed on separate servers,and a firewall is enabled. You must open port 9000 for any IP address thatis inbound on the server where the Virtual Infrastructure Integrator serveris installed. See Install locations on page 67 for more details.

• Virtual Infrastructure Integrator server is hosted on a VM. You mustconfigure the inbound and outbound firewall settings for source anddestination and TCP/UDP.

The following ports must be opened on the Virtual Infrastructure Integratorserver:


Port Protocol Rules type Source Destination

9000 TCP Inbound Any Virtual Infrastructure Integrator server IP or

any

8443 TCP Inbound Any Virtual Infrastructure Integrator server IP or

any


3Installing Virtual Infrastructure

Integrator softwareThis section guides you through the installation process, one phase at a time.

The Virtual Infrastructure Integrator installer checks for an existinginstallation, and then provides the following options:• Fresh installation, if no previous installation is detected.

• Remove the current installation, if the currently installed version and theinstaller version match.

• Upgrade, if the installer is a later version than the currently installedversion.

□ Install prerequisites

□ Install components

□ Deployment options

□ Install locations

□ Finding server install software and log files

□ Installing Virtual Infrastructure Integrator server software

□ Installing Virtual Infrastructure Integrator Web client service plugin tovCenter Server

□ Upgrading Virtual Infrastructure Integrator software

□ Uninstalling Virtual Infrastructure Integrator

Installing Virtual Infrastructure Integrator software 63Hitachi Virtual Infrastructure Integrator Administration Guide

Install prerequisitesIn addition to meeting all of the systems requirements, you must meetcertain additional prerequisites when installing the Virtual InfrastructureIntegrator product.

See the System requirements on page 57 for those details.

Note: The functionality and appearance of the Hitachi Virtual InfrastructureIntegrator software may vary, depending on whether file storage, blockstorage, or both have been installed and configured. Specifically, if only filestorage has been set up, only those options are available, and similarly forblock storage. If both are set up, then options for both file and block storageconfiguration are available.

Prior to installing the Virtual Infrastructure Integrator software you mustperform the following:

NAS Server• See the System requirements on page 57 for hardware, firmware, and

license requirements• Network: NAS Server must be accessible to the Virtual Infrastructure

Integrator Server; that is, both need to be on the same network.

Hitachi Block Storage• See the System requirements on page 57 for hardware, firmware, and

license requirements.• HTI Pool:

○ Minimum of one (1) dedicated pool [block only].○ The pool must be a dedicated pool for Virtual Infrastructure Integrator

use only.○ As best practice, limit the HTI threshold to 80 percent. If you anticipate

the pool might fill quickly, set the threshold even lower.• Hitachi Command Control Interface (CCI) LDEV:

○ Create CCI LDEV, size 100 MB.○ Enable User Authentication for CCI LDEV.○ Add the CCI LDEV to a host group.

• Host group: Add ESXi WWN# to the host group for which LDEV and CCILDEV are assigned.

• Switch: Add ESXi host and port group in the same zone in the switch (ifapplicable).

• CCI software:

64 Installing Virtual Infrastructure Integrator softwareHitachi Virtual Infrastructure Integrator Administration Guide

Important: Follow all steps mentioned for CCI LDEV and HORCMinstance. See the Command Control Interface (CCI) requirementson page 60 for requirement details.

○ The Hitachi Open Remote Copy Manager (HORCM) instance must berunning.

Note: The HORCM instance must not changed once it isconfigured with the Virtual Infrastructure Integrator plugin.

○ CCI software must be installed on the same system where the VirtualInfrastructure Integrator server is installed.

Install componentsThe Virtual Infrastructure Integrator software has two components:

• Server software• Web client service plugin

Note: The vSphere Web Client must be installed before the VirtualInfrastructure Integrator server software and the Web client service plugin.

There are different installation requirements and components neededdepending on whether:• The installation is to be on a single system or distributed• Windows only or Linux and Windows• Support for Hitachi NAS file storage only, Hitachi Block Storage only, or

both

See these details in:• System requirements on page 57• Install prerequisites on page 64

Deployment optionsYou can install the Virtual Infrastructure Integrator Server and the VirtualInfrastructure Integrator Web Client plugin on the same server (singlesystem) or on separate servers (distributed).

Each deployment scheme has different prerequisites and system compatibilityrequirements. In addition, file storage, block storage, or support for both alsohave differing installation requirements. Consider the following:


• If you do not have sufficient user permissions to perform the installation orupgrade, an error message displays, describing what permissions areneeded to continue.

• If any services need to be stopped, you are prompted for confirmation. Ifyou decline the stop request, the installation or upgrade aborts and anychanges that were made are reverted to their original pre-installation orpre-upgrade state.

• In cases when a system restart is needed, you are prompted to approvethe restart.

• If for any reason the installation or upgrade is aborted or fails, everythingis rolled back to its original state, and the installation logs can be used todiagnose and troubleshoot any problems.

Single system deployment:• Windows

○ Install the Virtual Infrastructure Integrator Server on the same Windowssystem where vCenter Server and CCI (block only) is installed.

○ For supported Windows versions, see Operating system requirements onpage 58.

○ There is no need to separately install the Virtual InfrastructureIntegrator Web Client plugin because it is included with the serverinstallation.

○ Note: Confirm the port for Hitachi Storage web server is enabledon the system. This port is typically port 8443. See Portrequirements on page 60 for more information.

• Linux: Not supported.

Distributed system deployment:• Windows

○ The Virtual Infrastructure Integrator Web Client plugin must be installedon the same Windows system where vCenter Server is installed.

○ The Virtual Infrastructure Integrator Server and CCI should be installedtogether on the same Windows system.

Important: Use a dedicated VM for Windows. Other than theVirtual Infrastructure Integrator server and CCI software, do notinstall any other software related to Hitachi or VMware in this VM.


○ Enable port 9000 between the server system and the web client pluginsystem. See Port requirements on page 60 for more information.

• Linux


○ The Virtual Infrastructure Integrator Web Client plugin must be installedon VMware vCenter™ Server Appliance™where vCenter Server isrunning.

○ The Virtual Infrastructure Integrator Server cannot be installed on aLinux system. Install the Server only on a Windows system, and installthe CCI there as well.

Note: Use a dedicated VM for Windows. Other than the VirtualInfrastructure Integrator server and CCI software, no othersoftware related to Hitachi or VMware must be installed in thisVM.


○ Enable port 9000 between the server system and the web client pluginsystem.

Install locationsInstall the software components in the appropriate places.

The Virtual Infrastructure Integrator server software installation program,HDS_V2I_Server_Installer.exe, runs on a 64-bit platform.

The Virtual Infrastructure Integrator server software can be installed on:• Same server as the VMware vCenter server• Dedicated Windows Virtual Machine (VM)• Separate physical server with Windows OS.

Virtual Infrastructure Integrator server software can be installed on the samesystem as the vCenter Server or it can be installed on a separate system in adistributed setup. During installation, the server installer will attempt toregister the Virtual Infrastructure Integrator client plug-in with the vCenterServer.

Important: If you install Virtual Infrastructure Integrator server componentas a distributed setup, where the vCenter Server is on separate server and afirewall is enabled, you must open port 9000 for any IP address that isinbound on the server where the Virtual Infrastructure Integrator server isinstalled.

Enable the port for Hitachi Storage web server on the system. This port istypically port 8443. See Port requirements on page 60 for more information.

Once port 9000 has been opened, ensure that the system running thevSphere Web Client can communicate with the server where the VirtualInfrastructure Integrator server is installed. Failure to do so results in certainfeatures of the Virtual Infrastructure Integrator Web Client Plugin to fail.


Important: The HDS_V2I_Server_Installer.exe must be installed on thesame server as the vCenter server. If the plugin registration fails for anyreason, install the client by running the HDS_V2I_WebClient_Installer.exe.This will re-register the plugin.

Finding server install software and log filesThe Virtual Infrastructure Integrator server software and log files can befound in the following locations.

Important: The Virtual Infrastructure Integrator software is a 64-bitWindows application; therefore, the software is installed in the Program Filesfolder.

The server binaries are installed to ..\Program Files\Hitachi\HNAS-V2I\Server

The log files can be found in ..\Program Files\Hitachi\HNAS-V2I\Server\log\HNAS-V2I.log

Installing Virtual Infrastructure Integrator server softwareUse these steps to install the Virtual Infrastructure Integrator serversoftware.

Important: You must first install the Virtual Infrastructure Integrator serversoftware before installing the Virtual Infrastructure Integrator Web clientservice plugin software.

See Install locations on page 67 for details about where Virtual InfrastructureIntegrator software can be installed.

Following the installation, if the Virtual Infrastructure Integrator server hasbeen installed on the same system where the vCenter is installed, then theVirtual Infrastructure Integrator server installer registers the VirtualInfrastructure Integrator Web client service plugin with the vCenter Server.

Note: If this is a non-vCenter Server installation, see Installing VirtualInfrastructure Integrator Web client service plugin to vCenter Server onpage 69.

Procedure

1. From the CD, launch the server installer HDS_V2I_Server_Installer.exe.2. While logged in with administrative rights, double-click the installer to

launch the installation wizard, and then click Next.3. Review and accept the license agreement, and then click Next.


4. Click Install.5. Provide a port number for the Hitachi Storage Services Web Server Port

number.The default port is typically 8443, or 11443 if 8443 is already in use. See Port requirements on page 60 for details.

Important: For vCenter 6.0, you are prompted to enter apassword for VMware vCenter Server keystore password. In asingle-server deployment, leave the default password as it is, ifthe keystore password has not been changed.

6. Click Finish to complete the installation.7. Restart the Webservices if required for your installation scenario. Follow

the instructions on the installer screens.

Important: This step is required to register the VirtualInfrastructure Integrator Web client service plugin with thevCenter software.

Important: Deployment methods for the Virtual InfrastructureIntegrator Web Client Plugin vary depending on your VMwareversion and your installation scenario. If your installation promptsyou to restart a particular service, do so.

Next steps

After installing the Virtual Infrastructure Integrator server software, proceedto Configuring Virtual Infrastructure Integrator software on page 77.

Installing Virtual Infrastructure Integrator Web clientservice plugin to vCenter Server

Use these steps to install the Virtual Infrastructure Integrator Web clientplugin software.

Note: The Web client installer uses the credentials of the logged-in Windowsuser, so make sure the logged-in Windows user has the administrator rolepermission on vCenter for Web Client plugin registration.

See Install locations on page 67 for details about where Virtual InfrastructureIntegrator software can be installed.


Procedure

1. Locate and copy the appropriate Virtual Infrastructure Integrator Webclient services plugin installer (HDS_V2I_WebClient_Installer.exe) tothe vCenter Server machine.

2. Double-click the installer to launch the installation wizard:3. Click Next when the client installer is displayed, and follow the on-screen

instructions.4. Click Install when prompted.5. Provide the Hitachi Storage Services Web Server Domain Name/IP.6. Provide the Hitachi Storage Services Web Server Port number.

This port is typically the default port 8443; however, use the same portnumber that was used during the Virtual Infrastructure Integrator serverinstallation. See Port requirements on page 60 for supported portnumbers.

Important: For vCenter 6.0, you are prompted to enter apassword for VMware vCenter server keystore password, if thekeystore password has not been changed.

7. Restart the Webservices if required. Follow the instructions on theinstaller screens.

Important: Deployment methods for the Virtual InfrastructureIntegrator Web Client Plugin vary depending on your VMwareversion and your installation scenario. If your installation promptsyou to restart a particular service, do so.

Important: This step is required to register the VirtualInfrastructure Integrator Web client services plugin with vCenter.

8. Log in to the vSphere Web Client and confirm that the Hitachi StorageServices plugin displays in the vSphere Web Client.The presence of the plugin indicates that the Virtual InfrastructureIntegrator software installed successfully.

Next steps

After installing the Virtual Infrastructure Integrator server software, proceedto Configuring Virtual Infrastructure Integrator software on page 77.

Upgrading Virtual Infrastructure Integrator softwareYou can upgrade the Virtual Infrastructure Integrator software version from3.0 and later.


Before you begin• Stop the Virtual Infrastructure Integrator server for the upgrade process.

Stopping the server ensures no backups occur during the upgrade. If youhave not already done so, you are prompted to stop the server.

• When performing an upgrade on a distributed setup, upgrade the VirtualInfrastructure Integrator server first, then upgrade the Web Client plugin.

• Do not interrupt the upgrade and migration processes.• During upgrades, the current log and metadata files are maintained. As a

best practice, collect the Virtual Infrastructure Integrator diagnosticinformation prior to the upgrade process and store it on a separatesystem. See Collecting diagnostic information on page 145 for detailsabout how to collect diagnostic information.

Important: When prompted for the port to be used for the VirtualInfrastructure Integrator server to register the Virtual Infrastructure pluginwith the vCenter Server, use port number 8443.

The Virtual Infrastructure Integrator server installer performs the following:• The installer installs the new version of the server software on the system.

Your existing software license will be migrated to the newly installedversion. However, it is not possible to upgrade over an expireddemonstration license.

• If the Virtual Infrastructure Integrator server is running, you are promptedto stop it for the upgrade. If you decline to stop it, the upgrade installationwill exit.

• The installer registers the updated Virtual Infrastructure Integrator Webclient plugin with the vCenter Server, if available. You do not have toreconfigure the Virtual Infrastructure Integrator to use the Web clientservices plug in to view your Virtual Infrastructure Integrator inventory,and any previously configured backup schedules continue to function.

• Any required configuration file updates or conversions are handled by theupgrade process, and any conversion that results in a change to theenvironment is logged.

• If a restart is needed, you are prompted to confirm it.• If for any reason there is a failure in the upgrade process, everything is

rolled back to the state it was in before the upgrade was attempted,including restored configuration files and settings.

Procedure

1. Confirm that you are using port 8443.2. Copy the HDS_V2I_Server_Installer.exe file to a temporary location on

the server where the Virtual Infrastructure Integrator server waspreviously installed, and then double-click it to launch the installer.The installer automatically identifies the presence of the previous versionof the Virtual Infrastructure Integrator software.


3. Click Next to continue the installation, and follow the upgrade wizardprompts.

The upgrade process migrates all snapshot backup data from the earlierVirtual Infrastructure Integrator software version to the VirtualInfrastructure Integrator server directory.

Note: If the Virtual Infrastructure Integrator server was installedon the same system as vCenter Server, after the server upgradecompletes, an entry for the Virtual Infrastructure Integrator serverdisplays in the Windows Control Panel > Programs and Features.As well, the upgraded plug-in displays in the vSphere Web Client.If the Virtual Infrastructure Integrator was not installed on thesame server as vCenter Server, follow the instructions in InstallingVirtual Infrastructure Integrator Web client service plugin tovCenter Server on page 69 to install the Virtual InfrastructureIntegrator Web client services plugin.

4. Import the certificate for Virtual Infrastructure Integrator. See UsingvSphere Web Client to configure Virtual Infrastructure Integratorsoftware on page 80 for instructions.

Next stepsFollowing an upgrade installation, you should check to make sure the VirtualInfrastructure Integrator software installed and that your configurations weremigrated correctly.

Uninstalling Virtual Infrastructure IntegratorProcedure

1. Navigate to the Windows Control Panel > Programs and Features or> Add or Remove Programs (depending on your Windows version).

2. Locate Hitachi Storage Services Server from the list, and then clickUninstall.

3. Click Yes to confirm.


4Installing Virtual Infrastructure

Integrator Web Client Plugin in vCSAFor operation with Linux, the VMware vCenter Server Appliance (vCSA)requires a Linux Web Client Plugin (WCP) to be installed.

□ Installing Web Client Plugin for Linux

Installing Virtual Infrastructure Integrator Web Client Plugin in vCSA 73Hitachi Virtual Infrastructure Integrator Administration Guide

Installing Web Client Plugin for LinuxTo install the Web Client Plugin (WCP) for Linux, follow these steps:

Procedure

1. Using administrator-level credentials, log in to the VMware vCenterServer Appliance (vCSA) 5.5 or 6.0 VM.

2. Copy the installer file, WCPLinuxInstaller.tar.gz, to the VMwarevCenter Server Appliance 5.5 or 6.0 VM.As a best practice, use WinSCP software to copy the .gz file to VCSA /tmp directory.

3. Extract the copied installer file.4. If necessary, change the permissions for the file LinuxInstaller.sh to

755.5. Run the LinuxInstaller.sh file with the options shown here:

./LinuxInstaller.sh install <vCenter username> <vCenterpassword>

Important: If the vCenter Server password uses the specialcharacters $, &, or !, then you must insert a backward slash (\)before each of those special characters and enclose the passwordin single quotes. Without these changes, the password fails.

Example: If the password is P@$$w0rd&! , then provide thepassword to the script as 'P@\$\$w0rd\&\!'

6. When prompted in the install screens, provide the following information:a. Keystore password. (Press Enter for default password.)b. Hitachi Storage Services web server IP/Domain name (this is the

Virtual Infrastructure Integrator server IP).c. Hitachi Storage Services web server port number (configured during

the Virtual Infrastructure Integrator server install).This port is typically the default port 8443; however, use the sameport number that was used during the Virtual Infrastructure Integratorserver installation. See Port requirements on page 60 for supportedport numbers.

7. Restart the vCenter Server Service and the vSphere Web Client serviceusing the below commands:

For vCenter 5.5:• service vmware-vpxd restart for restarting vCenter Server Service• service vsphere-client restart for restarting vSphere Web Client

For vCenter 6.0:

74 Installing Virtual Infrastructure Integrator Web Client Plugin in vCSAHitachi Virtual Infrastructure Integrator Administration Guide

• service vsphere-client restart for restarting vSphere Web Client8. Launch the web interface, where <vCSA host address> is the address or

resolved name of the vCSA host system:• For vCenter 5.5: vSphere Web Client by default includes the port

number (9443) in the URL. For example: https://<vCSA hostaddress>:9443/vsphere-client

• For vCenter Server 6.0, including port 9443 in the URL is not required.

Installing Virtual Infrastructure Integrator Web Client Plugin in vCSA 75Hitachi Virtual Infrastructure Integrator Administration Guide

76 Installing Virtual Infrastructure Integrator Web Client Plugin in vCSAHitachi Virtual Infrastructure Integrator Administration Guide

5Configuring Virtual Infrastructure

Integrator softwareThis section guides you through the configuration process, one phase at atime.

□ Configuration prerequisites

□ Minimum user rights for using vCenter

□ Using vSphere Web Client to configure Virtual Infrastructure Integratorsoftware

□ Displaying attached storage and file systems

□ Managing Virtual Infrastructure Integrator license keys

Configuring Virtual Infrastructure Integrator software 77Hitachi Virtual Infrastructure Integrator Administration Guide

Configuration prerequisitesYou must meet certain additional prerequisites when configuring the VirtualInfrastructure Integrator product.

• Have minimum user rights assigned to you to perform all activitiesassociated with the software. See Minimum user rights for using vCenteron page 79.

• Have the following information available:○ Virtual Infrastructure Integrator server IP address or host name.○ vCenter Server IP address or host name, and login credentials.○ For file storage: IP addresses or host names, and login credentials of

each NAS Platform attached to the ESXi Clusters and hosts managed bythe vCenter Server.

Note: The IP address or host name refers to the admin servicesEVS on the NAS Platform, or, for the VSP models with the NASmodule, the controller IP address.

○ For block storage: IP addresses or host names, Hitachi Open RemoteCopy Manager (HORCM) instance, login credentials for the storagearray, and Hitachi Thin Image (HTI) Pool preference.

• Virtual Infrastructure Integrator server is running.• NAS Platform servers are running and VMs are hosted on the NAS

platform.• Port 9000 is not blocked by the firewall on the Virtual Infrastructure

Integrator server. If needed, check with the administrator about thefirewall properties.

• Hitachi Storage Services Web Server Port number is set to 8443.

Note: The typical port number is 8443; however, if 8443 is alreadyin use, you can use 11443. See Port requirements on page 60.

• For file storage: NAS Platform server Admin EVS or the Controller IPaddress is reachable from the vCenter Server.

• For block storage:○ Have a dedicated user account for the Hitachi storage server with

complete administrator rights for Virtual Infrastructure Integrator. Thenuse this account for Virtual Infrastructure Integrator block configuration.

○ Have the HORCM instance running on the Virtual InfrastructureIntegrator server VM as a Windows service, and that RAID commandscan be issued to the storage array from the VM.

○ HTI: As best practice, limit the HTI threshold to 80 percent. If youanticipate the pool might fill quickly, set the threshold even lower.

78 Configuring Virtual Infrastructure Integrator softwareHitachi Virtual Infrastructure Integrator Administration Guide

Minimum user rights for using vCenterWorking with the Virtual Infrastructure Integrator software requires that youhave minimum user rights assigned to you to perform all activities associatedwith the software.

For installation, you must use a vCenter Administrator role.

Important: As a best practice, clone the administrator role and use theclone for Backup and Restore operations. This role has all the necessaryprivileges to perform the operations in all environments.

If needed, create a new role specifically for the Virtual InfrastructureIntegrator software. Navigate to vCenter > Administration > Roles to createthe role.

This new role must include the rights in the following table, at a minimum.

Category Role

Datastore • Allocate space

Host • Configuration > Storage partition configuration• Local operation > Reconfigure virtual machines

Network • Assign network• Configure

Resource • Assign virtual machine to resource pool• Migrate powered off virtual machine• Migrate powered on virtual machine• Query vMotion

Task • Create task• Update task

Virtual machine • Configuration > Remove disk• Configuration > Add existing disk• Configuration > Add new disk• Configuration > Add or remove device• Configuration > Advanced• Configuration > Change CPU count• Configuration > Change managed by• Configuration > Change resource• Configuration > Disk change tracking• Configuration > Disk lease• Configuration > Display connection setting• Configuration > Extend virtual disk• Configuration > Host USB device• Configuration > Memory• Configuration > Modify device settings• Configuration > Query fault tolerance compatibility• Configuration > Query unowned files• Configuration > Raw device• Configuration > Reload from path


Category Role

• Configuration > Remove disk• Configuration > Rename• Configuration > Reset guest information• Configuration > Set annotation• Configuration > Setting• Configuration > Swapfile placement• Configuration > Unlock virtual machine• Interaction > Answer question• Inventory > Create new• Inventory > Register• Inventory > Unregister• Provisioning > Allow disk access• Snapshot management > Create snapshot• Snapshot management > Remove snapshot• Snapshot management > Revert snapshot

Using vSphere Web Client to configure VirtualInfrastructure Integrator software

Use the following procedure to initially configure the Virtual InfrastructureIntegrator software. Launch the configuration wizard later to add servers, ormodify existing settings.

Before you begin

Confirm that you have met the Configuration prerequisites on page 78.

Procedure

1. In the vSphere Web Client, launch the Virtual Infrastructure IntegratorWeb client service plugin by clicking the Hitachi Storage Services icon.

2. At the bottom of the Getting Started tab, click Configure HitachiVirtual Infrastructure Integrator.

3. If you are using vSphere 5.5, perform the following steps:

Important: Leave the default password as it is, if the keystorepassword has not been changed.

a. When the cacerts password window displays, click OK.b. Restart the vSphere Web Client Services by navigating to the Windows

Control Panel > Services and restarting the services.

Note: Restarting the vSphere Web Client Services from theControl Panel typically takes three to five minutes. Also, afterinitial set-up has been completed, subsequent reconfigurationdoes not require the cacerts or client services restart steps.


c. After the vSphere Web Client Services has restarted, re-login to thevSphere Web Client.

4. Enter the Virtual Infrastructure Integrator server IP address or hostname and port number in the first screen of the configuration wizard,and click Next. You may use the default port or another port on whichthe V2I service is running.

Important: If using server host names rather than IP addresses,some form of DNS resolution or look-up needs to be available.Otherwise, the system cannot locate the host(s) on the network.

5. Enter the vCenter Server credentials, including IP address or host name,

and username and password, then click Next.

Note: This user must have minimum user rights or administrationprivileges. See Minimum user rights for using vCenter on page 79for details.


6. When the Hitachi Storage details screen displays, if you are not

configuring Hitachi NAS storage, skip to the next step. Otherwise, clickthe HNAS Storage tab and perform the following steps:• For NAS Server: Add the Admin EVS IP address.• For NAS module: Enter the Host Name or IP Address of either of the

controllers. Only input the IP address of one of the controllers.

a. Add the username and password to access those server systems.b. You can add multiple resources by clicking Add after each one has

been configured.

c. If you need to edit an Hitachi NAS Storage resource, click the iconnext to the resource to be edited.

d. To delete a resource, click the icon on its line, but use care as adeletion cannot be undone.

Note: When deleting resources, use care because a deletioncannot be undone.

e. When finished configuring Hitachi NAS Storage, click Next, or if youneed to configure block storage, continue to the next step.


7. To configure block storage, click the Hitachi Block Storage tab.

a. When the HORCM Instance identifies the Hitachi Online Remote CopyManager instance to use for block storage configuration, to select aninstance, click the drop-down list and select the appropriate one fromthe list of available instances. This will automatically populate theSerial Number field as well.

b. Enter a Username and Password for a user ID with administrativeaccess.

c. Click Add. It will take a few seconds for the list of Hitachi Thin Image(HTI) pools to be populated.

d. Click the HTI Pool drop-down list and select an available HTI poolfrom the list.

Important: It is critical to select the appropriate HTI pool atthis stage because the selection cannot be changed after ablock storage resource has been added to the VirtualInfrastructure Integrator product. The Virtual InfrastructureIntegrator software does not require its own HTI pool. Select anexisting pool, but make certain that it is one that will not bedeleted. Never delete this pool.

e. Click Save to commit the HTI-Pool selection.

f. If you need to edit a block storage resource, click the icon next tothe resource to be edited.


Note: When editing a configured block storage resource, theHTI Pool drop-down list will be grayed-out, meaning it cannot bechanged.

g. To delete a resource, click the icon on its line, but use care as adeletion cannot be undone.

h. When finished configuring Hitachi Block Storage, click Next.

i. Verify the configuration settings on the Configuration Summary page.

If you need to make changes, click Back. Otherwise, if satisfied, clickFinish.


The Virtual Infrastructure Integrator inventory list is refreshed and theplugin is ready to use.

j. If you need to reconfigure the Virtual Infrastructure Integrator, youcan do so from the Getting Started screen by clicking ConfigureHitachi Virtual Infrastructure Integrator again.

8. For NAS module: Once configured/accessed via a provided Controller IPAddress, the second controller address is automatically detected.

Displaying attached storage and file systemsYou can display the existing attached storage and file systems.

Procedure

1. Navigate to Hitachi Storage Services > Hosts or ESXi Clusters.2. Select a host or cluster, as appropriate.

The Storage Info table displays the following details:

Item Description

Storage Address Hitachi storage host name and IP address

Platform Hitachi storage platform type

Version Hitachi storage operating system version

File Systems List of the file systems exported from a specific storage host


3. Click the link displayed for the number of file systems to display thedetails.

Item Description

Name Name of the file system used

Type Type of file system format, for example: WFS-1 or WFS-2

Total Space Total storage space on the datastore

Free Space Available free space on the datastore

Snapshots Hosted Number of snapshots hosted by the datastore

4. Click x on the upper right corner to close the list of file systemsdisplayed.

Managing Virtual Infrastructure Integrator license keys

Managing the demonstration licenseThe Virtual Infrastructure Integrator software installs with a 60-daydemonstration license key, which enables all Virtual Infrastructure Integratorfeatures for evaluation. To determine your remaining demonstration period,

go to the Hitachi Storage Services > Getting Started tab, click the key icon to open the license key dialog. If no other licenses are applied, theDemo license key type displays along with its expiration date.

Displaying the system IDPermanent license keys are issued based on the unique system ID that isgenerated during the installation. To display the Virtual InfrastructureIntegrator system ID:

Procedure

1. In the vSphere Web Client, launch the Virtual Infrastructure IntegratorWeb client service plugin by clicking the Hitachi Storage Services icon.

2. Click the key ( ) icon About License on the Hitachi StorageServices > Getting Started tab.The License Key dialog is displayed with the system ID appearing at thetop.

3. Copy and paste the system ID into an email, and send it to your salesrepresentative with the customer system order number (located on thepacking slip). Also, send the information on the vCenter Server licensetype installed on your system (foundation or standard).


Installing license keysAfter you receive a permanent Virtual Infrastructure Integrator license key,use the Virtual Infrastructure Integrator Web Client Plugin to enable it. TheVirtual Infrastructure Integrator server software validates and stores thelicense key.

Procedure

1. In the vSphere Web Client, launch the Virtual Infrastructure IntegratorWeb Client Plugin by clicking the Hitachi Storage Services icon.

2. Click the key ( ) icon About License on the Hitachi StorageServices > Getting Started tab.The License Key dialog is displayed.

3. Copy and paste the license key into the License Key field.4. Click OK.

Next steps

Click the key ( ) button to validate the installed license.

Expiring license keysBefore your demonstration license expires, contact customer support forassistance, or log on to the HDS Support Portal: https://portal.hds.com


https://portal.hds.com

6Using snapshot backup and restore for

VMsYou can configure the Virtual Infrastructure Integrator software to capturesnapshot backups on VMs, vApps, and groups of VMs and vApps.

Supported types of snapshot backups include:• On-demand snapshot backups, which are instant snapshot backups you

can take.• Scheduled snapshot backups, which are backups that the Virtual

Infrastructure Integrator software generates based on snapshot backupschedule settings.

• VVol snapshot backups, which are backups set at the VM level.

Unsupported types of snapshot backups include:• Snapshots of VMs on virtualized or external storage.

Note: Although the Hitachi Universal Volume Manager (UVM)product supports snapshots of VMs stored on virtualized or externalstorage, the Virtual Infrastructure Integrator product does notsupport snapshots of VMs stored on these types of storage.

Snapshot backup scheduling automates the task of taking snapshot backupsat regular intervals. Snapshot backup schedules enable you to select thedate, time, retention period, and frequency of backups. Backup schedules arecreated for individual entities, such as a VM, vApp, or Groups. You maymodify backup schedules, and create several different backup schedules forone entity.

□ Displaying snapshot backup details

□ Understanding quiescing before backups

□ Creating on-demand snapshot backups

Using snapshot backup and restore for VMs 89Hitachi Virtual Infrastructure Integrator Administration Guide

□ About snapshot backup schedules

□ Snapshot backup schedule retention policies

□ Creating snapshot backup schedules

□ Single-click direct access to VM hardware snapshots

□ Running pre- and post-process scripts

□ Displaying snapshot backup schedule details

□ Editing snapshot backup schedules

□ Disabling snapshot backup schedules

□ Deleting snapshot backups

□ Restoring snapshot backups

□ Deleting all orphan snapshot backups

□ Snapshot backup status reports

90 Using snapshot backup and restore for VMsHitachi Virtual Infrastructure Integrator Administration Guide

Displaying snapshot backup detailsYou can view the details for existing snapshot backups in the vSphere GUI.

Procedure

1. Under Schedules, select a VM snapshot backup from the navigationtree.

2. In the task pane, review the creation timestamp, age, and description ofthe selected snapshot backup.

3. In the displayed Summary, you can view:• Backup ID• Host IP Address• Description• Age• Creation Timestamp• Entity Name• A formatted table showing the backup list

4. If the backup involves block storage, also displayed are the block storagedetails, including:• Serial Number• Host LUNID• LDEVID• HTI Pool ID• HTI Pool Name• HTI Pool Capacity Total• HTI Pool Capacity Free

Understanding quiescing before backupsThe Virtual Infrastructure Integrator product supports creation of application-consistent snapshot backups. To use this feature, select the quiesce optionwhen you use Snapshot Backup Now or Schedule Snapshot Backupoperations.

If you plan to use quiesce before creating a backup, consider the following: • By default, the quiesce option for backups and schedule backups is set to

off.• On each VM, you must have installed VMware Tools version 10.0.9 or later,

and use supported OS versions and patches.

Typically, when the quiesce flag is set to true, the VMware APIs create the VMsnapshot; that is, an application-consistent snapshot backup. However, theability to create an application-consistent snapshot backup depends onvarious factors and sometimes an issue or failure can occur. In that case, the


APIs instead create a crash-consistent snapshot backup to ensure that atleast a backup occurs.

The following issues could lead to a crash-consistent snapshot backup beingcreated:• VMs not powered on, Guest OS running an unsupported version of VMware

Tools, or VMware Tools not currently running.• VMs not responding or cannot start due to broken parent and child virtual

disk dependencies.• VMs not responding or do not start due to redo logs residing on datastores

that do not have free space.• Snapshot delete or remove operations result in the vSphere or VMware

Infrastructure (VI) Client timing out.• Backups fail if quiescing during a snapshot operation.• VMs already running a quiesced snapshot operation.

Note: Failure cases other than those previously listed may also result increation of a crash-consistent snapshot backup, instead of the intendedapplication-consistent snapshot backup.

For failure details, see the Virtual Infrastructure Integrator server log andevents.

Creating on-demand snapshot backupsBefore you begin• If you plan to use quiesce, use VMware Tools version 10.0.9 or later, and

supported OS versions and patches on each VM that is to be backed up.• By default, the quiesce option for backups and schedule backups is set to

off.• For supported and unsupported snapshot backup types, see Using

snapshot backup and restore for VMs on page 89.

Procedure

1. In the vSphere Web Client, click the Hitachi Storage Services icon tolaunch its GUI.

2. Select Virtual Machines.3. Create an on-demand snapshot backup from the navigation tree:

• Right-click the node you want to backup, and select SnapshotBackup Now.

• In the Objects tab, select an entry in the table, and click on thetoolbar.


4. Enter a name and description for the backup.

Note: Names must be 24 characters or fewer.

5. Enable the Quiesce guest operating system option, if necessary. Thequiesce operation pauses operations and flushes buffers to put theVirtual Machine's file system in a 'quiet' state for the backup.

Note: VMware Tools 10.0.9 or later must be installed for quiesceto be available. (More information is available via VMwaresupport.)

Note: In the Snapshot Backup Now display, below the QuiesceVirtual Machine prior to backup checkbox is a link for Pre andPost Processing Using VMware Tools. This link goes to additionalHitachi Data Systems documentation, "Application ConsistentBackup with Hitachi Virtual Infrastructure Integrator." Specifically,it includes details on performing application-consistent backups forMySQL and Oracle, which require additional freezing/thawing andquiesce operations to ensure consistent and correct backups.Downloadable scripts and step-by-step instructions for doing thisare also available at that site. Additional details on automating


https://www.vmware.com/support/packages


https://community.hds.com/docs/DOC-1004498


Virtual Machine backups and recovering 1TB VMs quickly areavailable as well.

6. Select the Backup Retention Policy expiration date.7. Click Ok to create the snapshot backup.

About snapshot backup schedulesSnapshot backup schedules automate the task of taking snapshot backups.Create snapshot backup schedules at the following levels:• About Schedules on page 53• About vApps on page 51• About Groups on page 44• About Datastores on page 35• About Datastore Clusters on page 38


A snapshot backup schedule applies only to the entity that you selected inthe Virtual Infrastructure Integrator navigation tree. If you create multiplesnapshot backup schedules on the same entity, only the enabled snapshotbackup schedules concurrently apply on that entity, and generate snapshotbackups independently from their specified start dates and times andspecified recurrence intervals.

Specify the start date and time, in hours and minutes when you create asnapshot backup schedule. The first snapshot backup occurs at the specifiedsetting, and all subsequent snapshot backups generate according to therecurrence control settings.


Table 1 Snapshot backup schedule recurrence settings

Type Description

Minute Occurs after each specified interval, which ranges from 10 to 1439 minutes.

Hourly Occurs after each specified interval, which ranges from 1 to 23 hours.

Daily Occurs either after each specified interval, which ranges from 1 to 365 days, or onall weekdays.

Weekly Occurs after each specified interval, which ranges from 1 to 52 weeks on theselected day of the week.

Monthly Occurs on the specified day of each month, ranging from 1 to 31. If the monthdoes not have the specified day (for example, a setting of 31 in February), thesnapshot backup occurs on the last day of the month. Alternatively, you can specifya week day and week of the month (for example, a setting of the last Thursday ofevery month).

Snapshot backup schedule retention policiesUsing snapshot backup retention policies, you can automatically delete oldsnapshot backups, which frees storage space. Apply a retention policy whilecreating an on-demand snapshot backup, or while creating or editing asnapshot backup schedule. Examples of snapshot backup retention policyoptions:• Number of day(s) examples:

○ Set the retention days to 10 while creating an on-demand snapshotbackup. The Virtual Infrastructure Integrator software creates asnapshot backup of that VM, retains it for 10 days, and then deletesonce it is 10 days old.

○ Take an on-demand snapshot backup with a retention days to 5 andname it K. K is on a VM with 10 preexisting on-demand snapshotbackups named in order of creation A through J. The VirtualInfrastructure Integrator software retains snapshot backups with an ageless than 5 days old, and deletes the remaining snapshot backups.

○ Set the retention days to 10 while creating a snapshot backup scheduleon a vApp. The Virtual Infrastructure Integrator software createssnapshot backups at the specified time intervals from the specified dateand time. The system retains each backup under that backup schedulefor 10 days, and then deletes it when a backup on the same entity isperformed.

○ Change the retention days from 20 to 10 while editing a snapshotbackup schedule on a vApp. The Virtual Infrastructure Integratorsoftware continues creating snapshot backups at the specified settings.The system also checks how many earlier snapshot backups under thatschedule are available, deletes any that are older than 10 days, andcontinues deleting backups as they reach an age of 10 days.

• Total backups to keep examples:○ Set the retention number to 10 while creating an on-demand snapshot

backup of a group of VMs and vApps. The Virtual Infrastructure


Integrator software creates a snapshot backup, and checks how manyearlier on-demand snapshot backups of that group of VMs and vAppsare available. It retains only the 10 most recent backups, and deletes allothers.

○ You take an on-demand snapshot backup with a retention number of 5and name it K. K is on a VM with 10 pre-existing on-demand snapshotbackups named in order of creation A through J. The VirtualInfrastructure Integrator software retains G through K, and deletes theremaining backups.

○ Set the retention number to 10 while creating a snapshot backupschedule on a vApp. The Virtual Infrastructure Integrator softwarecreates snapshot backups at the specified time intervals from thespecified date and time. It retains only the 10 most recent backups, anddeletes all others.

○ Change the retention number from 20 to 10 while editing a snapshotbackup schedule on a vApp. The Virtual Infrastructure Integratorsoftware continues creating snapshot backups at the specified settings.The system also checks how many earlier snapshot backups under thatschedule are available, retaining only the 10 most recent backups, anddeleting all others.

Creating snapshot backup schedulesCreate schedules to automate your snapshot backups.

Before you begin• If you plan to use quiesce, use VMware Tools version 10.0.9 or later, and

supported OS versions and patches on each VM that is to be backed up.• By default, the quiesce option for backups and schedule backups is set to

off.• For supported and unsupported snapshot backup types, see Using

snapshot backup and restore for VMs on page 89.

Procedure


2. Select Virtual Machines.3. Schedule the snapshot backup from either the navigation tree (inventory

list) or the Related Objects tab on the Schedules page:• From the navigation tree, right-click the node, and select Schedule

Snapshot Backup.

• In the Objects tab, select an entry in the table, and click on thetoolbar.


4. Enter a name and description for the backup.5. Fill the Quiesce Virtual Machine prior to backup check box to quiesce

the Virtual Machine's file system before a snapshot is taken by thesystem, if necessary. The quiesce operation pauses operations andflushes buffers to put the file system in a 'quiet' state for the backup.

Note: VMware Tools 10.0.9 or later must be installed for quiesceto be available. (More information is available via VMwaresupport.)

6. Fill the Enable checkbox to enable the backup schedule.

Note: In the Schedule Snapshot Backup display, below theEnable checkbox is a link for Pre and Post Processing Using





VMware Tools. This link goes to additional Hitachi Data Systemsdocumentation, "Application Consistent Backup with Hitachi VirtualInfrastructure Integrator." Specifically, it includes details onperforming application-consistent backups for MySQL and Oracle,which require additional freezing/thawing and quiesce operationsto ensure consistent and correct backups. Downloadable scriptsand step-by-step instructions for doing this are also available atthat site. Additional details on automating Virtual Machine backupsand recovering 1TB VMs quickly are available as well.

7. Set the frequency at which the system takes snapshot backups using theoptions in the Backup Details and Type and Recurrence options.

8. Set the retention duration using the Time and Retention options.9. Click OK to apply the settings.

Single-click direct access to VM hardware snapshotsThis feature provides an additional single-click method to mount a virtualmachine (VM) hardware snapshot directly from HDS storage back to aproduction VM to allow application owners to perform self-directed datarecovery. This method preserves the backup, while still providing a read/writeoption to access the backup data. Application owners or administrators canthen quickly copy data from the newly added disk within the guest OS.

When the VM admin configures a backup to be mounted, the VirtualInfrastructure Integrator server gets the request and clones the specifiedsnapshot backup to an alternate location. A folder called /.recovery/<vm_name> is created on the respective filesystem corresponding to thatsnapshot backup. For example, if that snapshot backup resides on an HNASfilesystem called FS-01, then the clone of that snapshot backup is stored inthe folder at /.recovery/<hnasvm1>.

The Virtual Infrastructure Integrator server uses the VMware API to add andmount the respective VMDK or VMDKs to the production VM and reconfigureit. Upon the successful addition of the new VMDK or VMDKs to the respectiveproduction VM, the Virtual Infrastructure Integrator server sends back aresponse to the Virtual Infrastructure Integrator web client. The web clientthen updates the GUI and reports the final results along with newly addedrecovery disk details. At that point, you can access the snapshot from aWindows or Linux server operating system.

Consider the following VMDK characteristics with mounted snapshots:• When a virtual disk is added as part of the Mount VMDKs Accessible

option, the disk has the same UUID as that of the currently configuredvirtual disk of a production VM. This action results in the VMware softwareasking you to allow virtual disks with same UUID. The VirtualInfrastructure Integrator software handles the action with the VMware API



AnswerVM(). However, when that VM is later powered on, the VMwaresoftware requires your manual response, specifically, answer Yes or Nowhether to allow assignment of virtual disks with same UUID.

• VMware vSphere® Storage vMotion® does not support online VMs withmultiple virtual disks that have the same UUID. The choices are to removethe snapshot VMDK from the VM when done, prior to using StoragevMotion, or migrate the VMs in powered-off state.

Directly accessing a VMDK snapshotYou can mount a VM snapshot through the Hitachi Virtual InfrastructureIntegrator GUI. This GUI is launched from within the VMware vSphere WebClient.

See About mounting VMDKs differences on page 100 for details about usingVMDKs for block storage.

Important: Once a block-based backup is used for a mount VMDK operation,it can no longer be used for restoring a VM from that backup. However, youcan continue to mount and unmount the backup.

Procedure


2. In the navigation pane at the left, navigate to Hitachi Storage Services> Backups.

3. Right-click the snapshot backup that you want to access, and then selectMount Snapshot Backup VMDKs.

4. In the Recent Tasks pane, you can view the operation progress andresults.

About mounting VMDKs differencesThis section describes differences between the methods in which the VirtualInfrastructure Integrator softwares handles VMDKs and the mounting ofVMDKs for file and block storage systems.

The Virtual Infrastructure Integrator software for file storage can clone theVMDK files in a backup and present those cloned files to a running virtualmachine (VM). Then, you can extract erroneously deleted or corrupted filesdirectly from the attached disks without having to revert the entire VM to aprevious backup.

As part of the mounting of the backup disks to a running VM, a guestoperating system (OS), such as Microsoft Windows® operating system,modifies the signature on the disks to resolve a conflict with the existingvirtual disks. This type of modification changes the backup data, making itunusable. To avoid this issue, for VMDK files hosted on an Hitachi NASsystem, the Virtual Infrastructure Integrator software makes a clone of the


cloned backup files instead. This way the original backup remains unmodifiedand these temporary VMDKs may be disposed of after use.

The block platform provides a way to make a writable copy of a backup filethat is already on a snapshot disk. However, to provide the mount VMDKoperation for block, the VMDK files on the backup LUN are presented directlythe running host. The only alternative to this method is to use a third partysolution, such as Microsoft Shadow Services.

About unmounting snapshot VMDKsThe Unmount Snapshot Backup VMDKs operation enables you to remove theVMDKs that were previously added to a production VM. You can unmount theVMDKs as part of a single or multiple Mount Snapshot VMDK(s) operation onthe VM. The Unmount Snapshot VMDK(s) operation is available on the VMthat has the VMDK(s) added to it as part of the earlier Mount SnapshotVMDK(s) operation(s).

Using the Unmount Snapshot VMDK(s) operation does not remove existingVMDKs from a VM. The operation only removes any VMDKs added to it aspart of an earlier Mount Snapshot VMDK(s) operation.

You can use the context menu option provided on the Host and Cluster entitypages to perform the Unmount Snapshot VMDK(s) operation on multiple VMs.

Unmounting snapshot VMDKsYou can unmount a snapshot VMDK in different ways.

Procedure

Unmount the snapshot using one of the following methods:1. Locate and right-click the VM for which the snapshot was mounted.2. Select unmount VMDK.

OR1. Go to ESXi host/Cluster where VM is hosted.2. Right-click the ESXi host and select unmount VMDK snapshot.3. From the list of backups that are mounted as VMDK snapshots,

select the backup you want to unmount.4. Click OK to complete.

Accessing snapshot VMDKs for a Windows Guest OSYou can access snapshot backups that were added from a guest operatingsystem (OS) in a VM that is running the Microsoft Windows operating system.

Procedure

1. To take a Virtual Infrastructure Integrator snapshot backup of the VM,perform the following steps:a. Power on the VM that you want to snapshot.


b. Navigate to Hitachi Storage Services > Virtual Machines.c. Right-click the VM, and select Snapshot Backup Now.

2. To enable the VMDK on the Windows VM, navigate to Hitachi StorageServices > Virtual Machines, and double-click that same Windows VM.

3. Select Related Objects, right-click the backup that you just took, andthen select Mount Snapshot Backup VMDKs.

4. To confirm that the Snapshot Backup VMDKs are available for theWindows VMs, perform the following steps:a. Navigate to the vCenter UI, and select Virtual Machines in the object

navigator pane at the left.b. Right-click the VM, and select Edit Settings.c. In the Edit Settings dialog, check that the new hard disk has been

added.

Note: If the new VMDK are not visible, return to the VirtualInfrastructure Integrator UI and click the Refresh button in thetoolbar.

5. In the Windows guest OS, the application owner or admin performs thefollowing steps:a. Confirm that the disk is available in Disk Management.b. Confirm that the disk is in offline state.c. Now, make the same disk online.The new partition is created and the virtual disk is now accessible on theWindows guest OS.

Accessing snapshot VMDKs for a Linux guest OS (without LVM)You can access VMDKs that are added from a guest OS in a VM that isrunning the Linux operating system but not using Linux Volume Manager.

Procedure

1. To take a Hitachi NAS Virtual Infrastructure Integrator snapshot backupof the VM, perform the following steps:a. Navigate to Hitachi Storage Services > Virtual Machines.b. Power on the Linux VM that you want to snapshot.c. Right-click the Linux VM, and select Snapshot Backup Now.

2. To enable the VMDK on the Linux VM, navigate to Hitachi StorageServices > Virtual Machines, and double-click that same Linux VM.

3. Select Related Objects, right-click the backup just taken, and thenselect Mount Snapshot Backup VMDKs accessible.

4. To confirm that the Snapshot Backup VMDKs are available for theWindows VMs, perform the following steps:a. Navigate to the vCenter UI, and select Virtual Machines in the object

navigator pane at the left.b. Right-click the VM, and select Edit Settings.


c. In the Edit Settings dialog, check that the new hard disk has beenadded.


5. Login as root to the Linux VM and run the following command:# echo "- - -" > /sys/class/scsi_host/host<H>/scanWhere "- - -" are wildcards meaning re-scan everything.

Where <H> is the HBA number.

or# /usr/bin/rescan-scsi-bus.sh

6. View the partition table to confirm that the guest now recognizes thevirtual disk by issuing the following command:# fdisk –lu /dev/sdbDisk /dev/sdb: 42.9 GB, 42949672960 bytes 255 heads, 63 sectors/track, 5221 cylinders, total 83886080 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 63 208844 104391 83 Linux /dev/sdb2 208845 83875364 41833260 8e Linux LVMDuring installations, Red Hat software currently uses Linux logical volumemanagement (LVM) by default. Consider these characteristics:• The /boot file system is an ext3 file system in a primary partition

(usually shows up as /dev/sda1. /• The swap, possibly tmp, and /var/log volumes are logical volumes in

a physical volume, usually in /dev/sda2.• Any file system other than LVM is easy to access.

7. Create the directory and try to mount the file system by issuing thefollowing commands:# mkdir /mnt/bootbk # mount /dev/sdb1 /mnt/bootbk

Accessing snapshot VMDKs for a Linux guest OS (with LVM)You can access VMDKs that are added from a guest OS in a VM that isrunning the Linux operating system and using Linux Volume Manager.

Procedure

1. To take a Virtual Infrastructure Integrator snapshot backup of the VM,perform the following steps:a. Navigate to Hitachi Storage Services > Virtual Machines.b. Power on the Linux VM that you want to snapshot.


c. Right-click the Linux VM, and select Snapshot Backup Now.2. To enable the VMDK on the Linux VM, navigate to Hitachi Storage

Services > Virtual Machines, and double-click that same Linux VM.3. Select Related Objects, right-click the backup just taken, and then

select Mount Snapshot Backup VMDKs accessible.4. To confirm that the Snapshot Backup VMDKs are available for the

Windows VMs, perform the following steps:a. Navigate to the vCenter UI, and select Virtual Machines in the object

navigator pane at the left.b. Right-click the VM, and select Edit Settings.c. In the Edit Settings dialog, check that the new hard disk has been

added.


5. Login as root to the Linux VM and run the following command:# echo "- - -" > /sys/class/scsi_host/host<H>/scanWhere "- - -" are wildcards meaning re-scan everything.

Where <H> is the HBA number.

or# /usr/bin/rescan-scsi-bus.sh

6. View the partition table to confirm that the guest now recognizes thevirtual disk by issuing the following command:# fdisk –lu /dev/sdbDisk /dev/sdb: 42.9 GB, 42949672960 bytes 255 heads, 63 sectors/track, 5221 cylinders, total 83886080 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 63 208844 104391 83 Linux /dev/sdb2 208845 83875364 41833260 8e Linux LVMDuring installations, Red Hat software currently uses Linux logical volumemanagement (LVM) by default. Consider these characteristics:• The /boot file system is an ext3 file system in a primary partition

(usually shows up as /dev/sda1. /• The swap, possibly tmp, and /var/log volumes are logical volumes in

a physical volume, usually in /dev/sda2.• Any file system other than LVM is easy to access.

7. Create the directory and try to mount the file system by issuing thefollowing commands:# mkdir /mnt/bootbk # mount /dev/sdb1 /mnt/bootbk


If you are using LVM, the file system fails to directly mount.# mount /dev/sdc2 /v2imount: unknown filesystem type 'LVM2_member'The failure occurs because the added VMDK has volume groups, physicalvolumes, and logical volumes (VG, PV, and LV) that have the same name(or label) and UUID as the original live, running VG, PV, and LV of yourguest. You must change these without damaging the live VG, PV, and LVby using the vgimportclone command.

8. To resolve the previous failure, issue the following command:# vgimportclone -n vg_new /dev/sdb2WARNING: Activation disabled. No device-mapper interaction will be attempted. Physical volume "/tmp/snap.qIW31527/vgimport0" changed 1 physical volume changed / 0 physical volumes not changed WARNING: Activation disabled. No device-mapper interaction will be attempted. Volume group "VolGroup00" successfully changed Volume group "VolGroup00" successfully renamed to "vg_new" Reading all physical volumes. This may take a while... Found volume group "vg_new" using metadata type lvm2 Found volume group "VolGroup00" using metadata type lvm2At this point, you still cannot use the logical volumes. When you view thelvdisplay results, you can see that while the VG was renamed fromVolGroup00 to vg_new, and new UUIDs were assigned, the LVs aremarked NOT available.

9. View the lvdisplay by issuing the following command:# lvdisplay --- Logical volume --- LV Name /dev/vg_new/LogVol00 VG Name vg00clone LV UUID jb8aZB-93kW-lue6-q7Vn-jt1i-NEG4-rcZ6Rk LV Write Access read/write LV Status NOT available <<<< LV Size 38.88 GB Current LE 1244 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Name /dev/vg_new/LogVol01 VG Name vg00clone LV UUID HbOy2u-3zdt-0otQ-dvrb-4Rm0-2ffa-P1qrfA LV Write Access read/write LV Status NOT available <<<< LV Size 1.00 GB Current LE 32 Segments 1 Allocation inherit Read ahead sectors auto

10. Make the LVs available by issuing the following command:lvchange


11. Mount the file system by issuing the following commands:

# mkdir /mnt/lv00 # mount /dev/vg00clone/LogVol00 /mnt/lv00

12. To clean-up the file system, perform the following steps:a. Unmount the cloned file system with the command: # umount /mnt/

lv00b. Remove the clone VG and PV (if you were using LVM) by issuing the

following commands:

# vgremove vg_newDo you really want to remove volume group "vg_new" containing 2 logical volumes? [y/n]: y Do you really want to remove active logical volume LogVol00? [y/n]: y Logical volume "LogVol00" successfully removed Logical volume "LogVol01" successfully removed Volume group "vg_new" successfully removed# pvremove /dev/sdb2Labels on physical volume "/dev/sdb2" successfully wiped

c. Unmount the snapshot backup VMDKs on the VM using virtualinfrastructure integrator or remove the VMDKs using the EditSettings option in the VM.

Running pre- and post-process scriptsBefore running a specific backup, you can configure pre- and post-processscripts that are triggered by Virtual Infrastructure Integrator operations. Thisallows you to start and stop services and VMs before and after backupoperations.

Scripts are located at ..\Program Files\Hitachi\HNAS-V2I\Server\config\scripts\, which include:• preScriptForManualBackup.bat• preScriptForScheduledBackup.bat• postScriptSuccessForManualBackup.bat• postScriptSuccessForScheduledBackup.bat• postScriptFailureForManualBackup.bat• postScriptFailureForScheduledBackup.bat

Using batch script commands, you can run your pre-existing WindowsPowerShell scripts, Python scripts, .net programs, and so forth from thesefiles for any specific backup entity.

See the "Using Virtual Infrastructure Integrator Command Line Interface withVMware PowerCLI on page 167" section for scripting samples.


Displaying snapshot backup schedule detailsView the details for a particular snapshot schedule.

Procedure

1. In the Virtual Infrastructure Integrator navigate to Hitachi StorageServices > Schedules.The Objects tab displays a summary of the currently scheduled backups.

2. To view more details for a particular backup schedule, in the navigationtree at the left, select the backup schedule that you want to view, andselect one of the tabs.

While all tabs may not always be visible, the available tabs include:• Summary• Monitor

Editing snapshot backup schedulesEdit a particular snapshot schedule, as needed.

Procedure

1. In the vSphere inventory list, navigate to Hitachi Storage Services >Schedules.

2. Right-click the schedule you want to edit, and select Edit Schedule.3. Make your changes and then click OK.

Disabling snapshot backup schedulesDisabling a backup schedule causes the Last Backup Time value to becomeblank.

The last backup time that was displayed in the Objects tab for that schedulebecomes blank (only a dash symbol). You can see this behavior in the HNASVirtual Infrastructure Integrator GUI when you navigate to Hitachi StorageServices > Schedules, and then locate the backup in the Objects table.

Procedure

1. Navigate to Hitachi Storage Services > Schedules Schedule.2. Right-click Schedules and select Edit Schedule.3. In the Schedule Snapshot Backup dialog, Backup details section, uncheck

Enable.


Note: After re-enabling the schedule, only Next Backup Time isdisplayed; Last backup time remains blank.

Deleting snapshot backupsProcedure

1. In the navigation tree, navigate to Hitachi Storage Services >Backups.

2. Right-click the backup to be deleted, and select Delete SnapshotBackup(s).

3. Click Yes to confirm.

Restoring snapshot backupsUse the Restore from Snapshot Backup option on a VM to restore it to aprevious state using one of the available snapshot backups.

Using the vCenter software, including the Restore from Snapshot Backupoption, requires that you have the appropriate rights. See Minimum userrights for using vCenter on page 79 for details.

A snapshot backup at the group level is a collection of snapshot backups foreach folder containing a VM. All available snapshot backups are listed in theBackups tab on the Related Objects tab for the respective VM node selectedin the inventory list. The snapshot restore operation also recovers a deletedVM.

VVol datastore snapshot considerationsWhen taking snapshots of VVol datastores, there are some considerations tokeep in mind.


• If you need to perform a restore, you must reassign a storage policy afterthe restore is complete.

Restoring a snapshot backupYou can use the snapshot restore option on a VM to restore it to a previousstate using one of the available snapshot backups.

Procedure

1. Power off the VM to restore.2. In the navigation tree, navigate to Hitachi Storage Services >

Backups.3. Right-click the backup to restore, and select Restore from Snapshot

Backup.4. Click Yes to confirm.

Restoring a snapshot backup after VM migrationAfter VM migration, the restore snapshot option restores to the originaldatastore, instead of the migrated datastore.

The Virtual Infrastructure Integrator software stores the snapshot backupinformation, which also contains the respective datastore for the VM. Afterperforming the VMware Storage vMotion (migration) operation on the VM tomove it to new datastore, the existing snapshot backups are not updated tocontain new datastore information. The reference to the previous datastorecauses the VM to be restored back on the previous datastore. This limitationis due to NAS Platform server software behavior.

Deleting all orphan snapshot backupsThis procedure deletes all orphan snapshot backups on all hosts and ESXiClusters.

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services > Hostsor ESXi Clusters

2. Right-click a host node or ESXi Cluster, and select Delete OrphanSnapshots.

3. Click OK to confirm.

Snapshot backup status reportsThese pre-defined reports allow you to quickly identify the success of dailybackup jobs and quickly see any backups that have failed or have issues.


Note: You cannot add, modify, or delete the pre-defined reports.

The reports can help you understand whether:• All backups are completing successfully. The reports provide a roll-up

report displaying the previous scheduled snapshot activity.• All VMs are getting adequate data protection. For example, no backups

were performed for VM X, Y, and Z in three weeks. The reports can identifywhich VMs do or do not have snapshots, and help you keep track of andavoid missed VMs as you provision new VMs.

Roll-up report values:

Color Description

Yellow Represents inability to complete 100% of operations, highlights issues in some

job(s) that were unable to be completed per original schedule, for example, quiesce

issues occurred on a certain VM.

Green Successful completion of the original schedule, meaning there were no VM or

datastore backup issues, no quiesce issues, no detected backup issues, and no

storage issues.

Red Identifies scheduled backup failure to complete.

Gray Represents orphan VMs that no longer exist on your vCenter server, but for which

backups still exist. These VMs are no longer protected.

Snapshot backup report typesVirtual Infrastructure Integrator provides four types of pre-defined backupjob status reports. You can run the reports only for VMs and backups.

Note: You cannot add, modify, or delete the predefined reports.

Report Description

VM Protection Summary Provides information about all the backup jobs executed on a VM for

the last 30 days, or for the backup retention period, whichever is

earlier.

VM Backup Job Status

Summary

Provides information for all the backup jobs executed in the last 30

days.

Data Protection Status

Report

Provides information about all the jobs executed and classified by VMs

in the last 30 days.

Backup Job Status

Summary

Provides information about all scheduled jobs for last 30 days or per

retention, whichever is earlier.


Report Description

Note: This report contains a hyperlink. It takes you to aprintable form of the report that gives details about anindividual job. Use CTRL+P to print.

Report terminologyThe following terminology is used in the different reports and can help youbetter understand the reports.

Term Description

General

Job A schedule that was created or an individual manual backup for a VM or a group

of VMs.

VM Protection Summary

VM Name The name given to the VM.

State The current state:• Protected: The state of a VM is considered protected when at least one

useable backup of it exists.• Unprotected: The state of a VM is considered unprotected if no backups

exist for it.

Number of

Backups

Current number of backups for the VM.

Number of

Schedules

Current number of schedules applied to the VM.

Last Backup Time The last date and time the VM was backed up.

Next Scheduled

Backup

The next schedule date and time for the VM to be backed up.

VM Backup Job Status Summary

Job ID The ID of a single job execution. A single schedule run is counted as one

backup execution and results in the creation of one backup Job ID. In Virtual

Infrastructure Integrator terminology, this is the Backup ID.

Job Name The name of the schedule or the individual manual backup job.

Status The status of the job: Success or Fail.

Backup ID The backup ID of an individual backup of a VM. This is a single backup ID per

backup job per VM.

Job Run Time The date and time the job ran.

Type The type of job: Scheduled or On-demand.

Age The age of the backup in days and hours.


Term Description

Retention The schedule retention period.

Job Info Information about the success or failure of the backup.

Backup Job Status Summary





Start Time The start date and time of the job.

End Time The end date and time of the job.

Backup Valid Till The date and time to which the backup is valid; blank if not set.

Details Job

Report

The link to the printable report. The Backup Per Job Report screen displays with

columns for these values:• VM Name:• States:• Backup ID:• Info:

Data Protection Status Report




Job Name The name of the schedule or the individual manual backup job.

VM Name The name given to the VM.


Job Type The type of job: Scheduled or On-demand.

Last Run Time The last date and time the VM was backed up.

Next Run Time The next schedule date and time for the VM to be backed up.

Quiesce The selected setting for whether to quiesce the VM before performing the back

up: Yes or No.

Age The age of the backup in days and hours.

Retention The schedule retention period.

Job Info Information about the success or failure of the backup.

Viewing a reportYou can review a report for up to 30 days.


Procedure

1. In the vSphere Web Client, in the navigation tree, navigate to HitachiStorage Services.

2. In the right pane, click (page icon) to launch reports.3. Enter your vCenter server credentials to view reports.4. From the right hand corner drop down menu, select the appropriate

report to view.

Printing a reportYou can print a snapshot backup status report using the print feature of abrowser.

Note: Only detailed job reports within the Backup job summary report can beprinted.

Procedure

1. In the vSphere Web Client, in the navigation tree, navigate to HitachiStorage Services.

2. In the right pane, click (page icon) to launch reports.3. Enter your vCenter server credentials to view reports.4. From the right hand corner drop down menu, select the Backup job

status report you want to view.5. Click the Details hyperlink to view the printable report, and then print

the report.


7Using snapshot vaulting for enhanced

data protectionThe Virtual Infrastructure Integrator software provides high availability andenhanced data protection with support for vaulting. Vaulting is also referredto as replication in some systems. Vaulting can protect file systems and thevirtual machines (VMs) they contain by creating a copy of them at anotherlocation.

Similar to replication, vaulting can protect datastores and VM hardwaresnapshots on Hitachi Storage Services by space efficiently replicating a copyof the snapshots to another Hitachi storage device, residing in the samedatacenter or remote datacenter.

Note: Snapshot vaulting is not supported for block storage.

□ About vaulting for enhanced data protection

□ Configuring the HNAS server for vaulting

□ About the vault details

□ Viewing vault details

Using snapshot vaulting for enhanced data protection 115Hitachi Virtual Infrastructure Integrator Administration Guide

About vaulting for enhanced data protectionConsider the following Virtual Infrastructure Integrator software vaultingcharacteristics:

Note: Some new features contained in Virtual Infrastructure Integratorversion 3.0 require a newer version of the HNAS OS and NAS Managersoftware. For the vaulting feature, HNAS OS v11.3.3450.14 or later isrequired.

• The vaulting feature requires an underlying replication license on the HNASsystem. Vaulting using Object Replication is pre-configured by the storageadmin.

• The vaulting feature supports vault viewing capability to show thefrequency at which snapshots are being vaulted. It does not support thecapability to configure, modify, or manage the vault directly.

• Before you can use vaulting, you must have already configured thevaulting or replication policy between the source and target HNASsystems.

• Selecting specific backup jobs to vault is not supported because somebackup jobs are automatically vaulted. For example, any backup containedon a specific file system that has an object replication job associated withit is automatically vaulted.

A vault is an HNAS storage server that is being used as an object replicationtarget. The server can be another server in the environment or a remoteserver in another location. Pre-configure the vault on the target HNASstorage server.

The vaulting feature defines an object replication job for a given file systemon an HNAS system that is being vaulted to another location. The objectreplication job displays the information for the file system that contains theVMs.

Entire file systems can be vaulted; however, vaulting of specific files is notsupported.

The GUI displays when a backup is set to be vaulted. The file system thatcontains the VMs to be vaulted must have an object replication job identified.If no job is identified, the application responds with a message that is similarto the following:

Ask your storage admin to enable Object Replication for File System <fs-name that contains the datastores for the VMs being protected>. See the File Systems tab to retrieve the fs-name for respective datastores.

116 Using snapshot vaulting for enhanced data protectionHitachi Virtual Infrastructure Integrator Administration Guide

Configuring the HNAS server for vaultingBefore you can use vaulting, you must configure the target HNAS server toaccept vaulting.

Procedure

1. From the SMU GUI, navigate to Data Protection > Object Replication> Add Object Replication Policy.

2. Add an NFS export to the vCenter Server that was created on the filesystem that has the object replication policy.

3. Confirm that the datastore was added.4. Select Hitachi Storage Services > File Systems, and select the file

system to which the vault belongs.5. Confirm the accuracy of the vault description information in the table

fields.

About the vault detailsThe available vault information for a Virtual Infrastructure Integrator resourceentity displays on the entity's Summary page in the Virtual InfrastructureIntegrator Web client service plugin GUI.

Vault details are available for the following resource entities:• File systems• Datastores• Virtual Machines• vApps• Backups• Groups

You can view the following vault information for each resource entity in theSummary tab:

Section Item Description

Summary Name Object name (for example, Datastore name)

ESXi Host Name The ESXi host name or address

Location Source HNAS system export (EVS IP address +

Export name)

Scheduled VM

Backup Info

Scheduled Backups Count

at Group Level

Number of such backups present

Last Backup Time Time last backup occurred

Using snapshot vaulting for enhanced data protection 117Hitachi Virtual Infrastructure Integrator Administration Guide

Section Item Description

Next Backup Time Time next backup is to occur

Scheduled Backups at

Item Level

Number of such backups present

You can also view the following vault information at the datastore level:

Item Description

Datastores detail • Name• Device• Free Space• Block Size• Total Space• File System• LUN

Viewing vault detailsYou can view the configuration details for vaults in the Virtual InfrastructureIntegrator Web client service plugin GUI. This GUI is launched from within theVMware vSphere GUI.

Before you begin

The vault must be pre-configured on the HNAS storage server to which theVirtual Infrastructure Integrator software is referring.

Procedure

1. In the vSphere Web Client, click the Hitachi Storage Services icon tolaunch the Virtual Infrastructure Integrator Web client service plugin GUI.

2. In the navigation pane at the left, click the Datastore, Groups, VirtualMachines, Backups, or vApps entity type for which you want to viewvault details.

3. Select the specific object.4. View the vault details in the Summary tab page for the selected backup.

118 Using snapshot vaulting for enhanced data protectionHitachi Virtual Infrastructure Integrator Administration Guide

8Backing up and recovering VirtualInfrastructure Integrator service

This section describes how you can back up and recover from a VirtualInfrastructure Integrator service failure.

Hitachi Data Systems recommends that you configure the VirtualInfrastructure Integrator service to run as a separate VM, instead of runningon the vCenter Server. For best results, confirm the following:• The Virtual Infrastructure Integrator service VM is being protected by a

Virtual Infrastructure Integrator scheduled backup policy.• If you are using vaulting (replication) to create a secondary or tertiary

copy of your VM infrastructure, ensure that the file system from which theVirtual Infrastructure Integrator VM is running is being vaulted(replicated).

Generally, you recover the Virtual Infrastructure Integrator VM from aprevious Virtual Infrastructure Integrator snapshot of that same VM.Restoring the full VM from the snapshot enables the required recovery.Optionally, if the existing Virtual Infrastructure Integrator VM is available, youcan just restore the config directory if the case arises.

Note: The config directory in the VM contains the Virtual InfrastructureIntegrator configuration data. This directory also hosts a Backups.xmldatabase file (C:\Program Files..Hitachi\HNAS-V2I\Server\Config).

□ Strategies for VM backup and data protection

□ Recovery scenario 1 - VM has issues

□ Recovery scenario 2 - VM accidently deleted

□ Recovery scenario 3 - No VM backup is available

Backing up and recovering Virtual Infrastructure Integrator service 119Hitachi Virtual Infrastructure Integrator Administration Guide

Strategies for VM backup and data protectionFollow these strategies to improve your data protection and recovery efforts.

When you are file replicating the primary file system(s) to your secondarysite, you always have the latest replicated copy in the secondary site. Thesecondary site would contain the datastores (exports) to which you wouldconnect the standby ESXi servers.

Note: Typically, you would exclude VM snapshots from being replicated.

Similarly, if you are vaulting the file system to the secondary site, you willalso get the Virtual Infrastructure Integrator VM snapshots, plus the primaryfile system. This means that the vaulted image is a mirror image of that onthe primary file system(s). In that case, there is no need to recover from theVirtual Infrastructure Integrator snapshots on a per VM or datastore basisbecause all of the VMs would derive from that latest copy, including theVirtual Infrastructure Integrator VM.

Typically, you vault to a local environment to enable faster recovery if anissue occurred with the primary system and then replicate to a remoteenvironment for disaster recovery purposes.

120 Backing up and recovering Virtual Infrastructure Integrator serviceHitachi Virtual Infrastructure Integrator Administration Guide

Important: The Virtual Infrastructure Integrator Server, and vCenter andESXi servers must be time synchronized to prevent Backup(s) from beinglisted with age as "-".

Recovery scenario 1 - VM has issuesThere are a number of options for recovery when the Virtual InfrastructureIntegrator VM is experiencing issues.

Note: If you try this recovery process and it is unsuccessful, you can recoverthe full Virtual Infrastructure Integrator VM from the snapshot as described in Recovery scenario 2 - VM accidently deleted on page 121.

Procedure

1. Use one of the following options for recovery:• Mount the Snapshot Backup VMDKs (specifically, mount the snapshot

backup for that VM to the existing Virtual Infrastructure IntegratorVM).

• Or, use Fast Clone Snapshot Backup (create a temporary VM from thesnapshot backup).

2. Retrieve, copy, and replace the config directory.3. Restart the Virtual Infrastructure Integrator VM.4. Reactivate any new schedules that were created since that snapshot

occurred.5. Run Unmount Snapshot Backup VMDKs or delete the temporary VM.

Recovery scenario 2 - VM accidently deletedIf you accidentally delete the Virtual Infrastructure Integrator VM or need torecover the full Virtual Infrastructure Integrator VM, use the latest snapshotbackup of the VM.

Procedure

1. Use SSH to access the HNAS console and find the Virtual InfrastructureIntegrator VM name in the /.jetapi directory.

2. Use the tree-clone-job-submit CLI command to clone the VM snapshotback to the datastore root location.For example:Clone V2I-vm snapshot within /.jetapi to root of datastore DS01 ; -$tree-clone-job-submit -f FS01 /.jetapi/HNAS-V2IClone_c9d7cb50-cd32-4ead-ad2f-af0763cd19d1/DS01/V2I-vm /DS01/V2I-vm

3. From vCenter, take the following steps:

Backing up and recovering Virtual Infrastructure Integrator service 121Hitachi Virtual Infrastructure Integrator Administration Guide

a. Re-register the Virtual Infrastructure Integrator VM by browsing tothat location for the .vmx file of the Virtual Infrastructure IntegratorVM.

b. Power on the VM.c. Rerun the configure Virtual Infrastructure Integrator service.Virtual Infrastructure Integrator is now recovered to that point in timesnapshot backup.

Recovery scenario 3 - No VM backup is availableIf no Virtual Infrastructure Integrator VM backup is available to be recovered,then the Virtual Infrastructure Integrator softwre cannot recreate the configand database xml file from scratch for those previous snapshots. However,HNAS tracks those snapshots.

In the event that you want to recover a production VM to one of thosesnapshots that are not showing up in Virtual Infrastructure Integrator, amanual workaround exists.

Procedure

1. Use SSH to find the Virtual Infrastructure Integrator VM name inthe .VMX files in the snapshot backup directory for that production VM.

2. Recover from the snapshot of that VM.

122 Backing up and recovering Virtual Infrastructure Integrator serviceHitachi Virtual Infrastructure Integrator Administration Guide

9Compliance dashboard for Hitachi NAS

NFS best practicesWhen configuring Hitachi storage, follow the Hitachi Data Systems prescribedbest practices for using Hitachi NAS NFS with VMware vSphere environmentsto optimize the storage usage and VM I/O performance. The dashboard alsoprovides a way for you to identify VM misalignment issues.

To help ensure that Hitachi NAS best practice guidelines are met, the HitachiVirtual Infrastructure Integrator software can run validation checking andreport findings. You can then choose to manually respond by making therecommended configuration changes.

Note: The Hitachi NAS NFS Compliance Dashboard is applicable for filestorage configurations, not block storage.

□ Understanding Hitachi NAS NFS best practices compliance

□ Validating Hitachi NAS NFS best practices

□ Identifying VM misalignment

Compliance dashboard for Hitachi NAS NFS best practices 123Hitachi Virtual Infrastructure Integrator Administration Guide

Understanding Hitachi NAS NFS best practices complianceThe Hitachi Virtual Infrastructure Integrator software's compliance validationfeature helps to assure compliance with Hitachi NAS best practices for usingthe Virtual Infrastructure Integrator with VMware vSphere environments.

The checks validate that the environment is optimally configured as a NASshared storage resource. After the checks run, the software reports any non-compliance with Hitachi NAS NFS best practices in the summary informationof the Hitachi Virtual Infrastructure Integrator GUI and displays therecommended configuration. You can then use that information to fine tunethe Hitachi NAS storage and VM provisioning for best possible performanceand optimized storage space usage.

Note: The Hitachi Virtual Infrastructure Integrator software checks forcompliance with the numerous prescribed best practices. However, thevalidation checks only support checking of VMs that are configured to beprotected by the software.

See the Hitachi NAS Platform Best Practices Guide for NFS with VMwarevSphere for more details about best practices.

124 Compliance dashboard for Hitachi NAS NFS best practicesHitachi Virtual Infrastructure Integrator Administration Guide

Validating Hitachi NAS NFS best practicesConfigure your Virtual Infrastructure Integrator software to validate that theHitachi storage best practices are being assured in your environment.

See the Hitachi NAS Platform Best Practices Guide for NFS with VMwarevSphere for more details about the best practices.

Note: Some new features contained in Virtual Infrastructure Integratorversion 3.0 and higher require a newer version of the HNAS OS and NASManager software. For the Compliance Dashboard feature, you may see adash (“-“) for some compliance checkers where information is not yetavailable due to the use of earlier versions of the HNAS OS and NAS Managersoftware.

Procedure


2. In the content pane at the right, select the Compliance Dashboard tab.

The Hitachi NAS NFS Best Practices Compliance Dashboard page displaysthe various ESXi hosts, Hitachi Storage Server Nodes and Clusters, andDatastores from Hitachi Storage Server that are not complying with theHitachi NAS NFS Best Practices.

The Compliance Dashboard provides the CLI output required to applyNFS best practices to the storage cluster. This output can be shared withthe storage admin. Additionally, the VM admin can select to have the CLIapplied to the storage cluster.

3. View the displayed information and take the best actions that aresuitable for your situation and environment.

Identifying VM misalignmentAs a Virtual Infrastructure Integrator administrator, you can check for VMmisalignment on Hitachi NAS storage through the Compliance Dashboard andresolve the issue using any third party tool.

Before you begin• Supported NAS Storage:

○ Hitachi NAS OS v12.4 or later○ File storage system

Note: Block storage is unsupported.

Compliance dashboard for Hitachi NAS NFS best practices 125Hitachi Virtual Infrastructure Integrator Administration Guide

Any VMs that have Windows 2003, XP, or earlier operating systems aremisaligned by default.

Misaligned VMs can cause serious performance issues, such as slowperformance due to unnecessary I/O operations.

Check that the VM alignment feature displays and lists the misaligned VMsand their VMDKs, along with their fully qualified VMDK paths on thefilesystem.

Procedure

1. In the Virtual Infrastructure Integrator Web Client GUI, select theCompliance Dashboard tab.

2. In the Hitachi NAS NFS Best Practices Compliance Dashboardscreen, select the Check VM alignment tab.

3. Click Get Misaligned VMs to identify any misaligned VMs.The Virtual Infrastructure Integrator scans the datastores for anymisaligned VMs and lists those found in the Misaligned VM Detailssection.

4. After you identify the misaligned VMs, use your favorite tool to resolvethe misalignment.

126 Compliance dashboard for Hitachi NAS NFS best practicesHitachi Virtual Infrastructure Integrator Administration Guide

10Using Hitachi NAS Fast Clone

The Hitachi NAS Fast Clone writable clone utility is different from the VMwareclone utility. The Fast Clone utility clones a VM or vApp immediately, withoutover-burdening storage space.

Note: Fast Clone is unsupported for block storage.

You can use writable clones of VMs and vApps as templates to expediteprovisioning. You can also use the Virtual Infrastructure Integrator softwareto rapidly scale to high numbers of virtual machines for tasks such asperformance intensive testing.

The Fast Clone utility operates on an existing VM or vApp. By default, theFast Clone is registered in the group called All VMs on Hitachi Storage in thenavigation tree that contains the resource cloned. Using the vSphere WebClient, you can move the VM or vApp clone to another folder, or migrate theclone to another host.

Note: The Virtual Infrastructure Integrator software does not supportperforming a Fast Clone with the WFS-1 file system type. Only currentgeneration WFS-2- based file systems are supported.

□ Cloning VMs and vApps

□ Cloning snapshot backups to alternate locations

Using Hitachi NAS Fast Clone 127Hitachi Virtual Infrastructure Integrator Administration Guide

Cloning VMs and vAppsYou can clone a VM or vApp.

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services > VirtualMachines or vApps.

2. Click in the toolbar, or right-click the node, and select Fast Clone.

3. Enter a name for the clone, specify number of desired clones, and then

click Start.

Note: The name cannot include many symbols, such as @, ^, *, |,\, /, <, or >. See Unsupported characters on page 56 for thecomplete list of unsupported characters.

ResultWhen creating more than one clone, the clone file names are appended withan incremental numeric suffix.

Cloning snapshot backups to alternate locationsUnlike the Restore from Snapshot option, which restores the backup to thesame location from which the backup was created, Fast Clone SnapshotBackup allows you to clone the selected backup to an alternate location onthe same file system.

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services > VirtualMachines, and select the VM node.

2. Select the Related Objects tab, and then the Backups button to displaythe snapshot backups associated with the selected Virtual Machine.

3. Right-click the backup that you want to clone, and select Fast CloneSnapshot Backup.

128 Using Hitachi NAS Fast CloneHitachi Virtual Infrastructure Integrator Administration Guide

4. Enter a name for the destination clone, and click Start.The clone operation initiates, and the status panel displays the progressof the operation.

Using Hitachi NAS Fast Clone 129Hitachi Virtual Infrastructure Integrator Administration Guide

130 Using Hitachi NAS Fast CloneHitachi Virtual Infrastructure Integrator Administration Guide

11Using Groups

There are now two types of Groups you can use for working with VMs andvApps: System Groups and Custom Groups.

□ About Groups

□ Viewing storage server clusters, and their nodes and datastores

□ Viewing file system resources

□ Using System Groups

□ Using Custom Groups

□ About the Host group in block storage configuration

Using Groups 131Hitachi Virtual Infrastructure Integrator Administration Guide

About GroupsThere are now two types of Groups: System Groups and Custom Groups.

When you select System Groups or Custom Groups, any configured Groupsobjects are displayed.

For Groups resources, the Objects tab displays:

Item Description



When you select a specific resource, the Summary tab displays, listing thesame Name and Description, as well as a formatted table listing scheduledVM backup information, if available, including:

Item Description



132 Using GroupsHitachi Virtual Infrastructure Integrator Administration Guide

Item Description



If you select the Monitor tab for a Groups resource object, you can viewevents associated with the resource, listing:

Item Description







Item Description




Viewing storage server clusters, and their nodes anddatastores

You can view the HNAS storage server clusters and their respective servernodes, and the datastores contained on the nodes.


Procedure


2. In the inventory list at the left, select the HNAS Clusters entity.3. From the list of individual HNAS storage server cluster entities, select the

cluster where the node resides.4. Select the individual HNAS node to expand the list.5. View the list of datastores that are hosted from the HNAS storage server

node.

Viewing file system resourcesYou can view the list of datastores that share the same Hitachi storage filesystems and the summary information on those file systems.

The Hitachi Virtual Infrastructure Integrator interface displays which VMs anddatastores are being delivered by which cluster and also provides visibility tointerdependence of VMs to shared storage resources (file systems). Thisinformation assists in operational placement of VMs and maintenanceactivities.

The summary includes the following information:• Whether the drive is a 32K or 4K file system• Breakdown of the space utilization of the file system• Whether a vault exists (yes or no), and if yes, the location of the vault

Procedure


2. In the inventory list at the left, select the File Systems entity.The list shows all file systems from HNAS storage currently in use fordatastores configured with ESXi hosts.

3. View the file systems and lists of datastores that share the file systems.4. To view summary information, select the file system that you want to

view, and then select the Summary tab.

Note: All hosts and ESXi Clusters in Virtual InfrastructureIntegrator contain the All VMs on Hitachi Storage group. Thisgroup is dynamic and cannot be edited.

Using System GroupsThe Virtual Infrastructure Integrator provides predefined system groups foruse.


You can perform functions within the Virtual Infrastructure Integrator onSystem groups including:• Snapshot backups of all members of a group• Schedule group snapshot backups• View all events associated with the VMs and vApps in the System group

System Groups provide the ability to visualize where VMs are located onHitachi storage. This type of VM visualization allows you to develop non-conflicting backup schedules to ensure optimum system performance.

If you have VMs hosted on VVol Datastores, these groups contain VMs andare grouped based on Snapshot Backup Importance capability values.

The available capability values are: Critical, Important, Best Effort, and None,with Critical being the default value. The group None contains VMs that haveno snapshot backup class capability assigned.

Using Custom GroupsUse the Virtual Infrastructure Integrator to create, edit, and delete customgroups of VMs and vApps from the All VMs on Hitachi Storage group.

You can perform functions within the Virtual Infrastructure Integrator ondefined groups including:• Snapshot backups of all members of a group• Schedule group snapshot backups• View all events associated with the VMs and vApps in a group


Note: All hosts and ESXi Clusters in Virtual Infrastructure Integrator containthe All VMs on Hitachi Storage group. This group is dynamic and cannot beedited.

Creating a group of VMs and vAppsFollowing are the steps for creating a group of VMs and/or vApps.

Note: Creating groups within groups is prohibited due to the following:• No number restrictions exist on the creation of custom groups under an

ESXi Cluster.• A single VM or vApp might belong to several custom groups under the

same ESXi Cluster.

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services >Groups.

2. Click in the toolbar, or right-click the node and select Create Group.

3. Enter a group name and description.4. Select a VM or vApp in the List of VMs on list, (hold the Shift key to

select multiple VMs or vApps) and click the > button to add to the SelectVMs for Group list. Click < to remove the selected VMs. It a VM or vAppscannot be selected, it is listed as being unavailable.

5. Click Ok to save the group.


Editing a group of VMs and vAppsYou can edit a Custom Group of VMs or vApps.

Procedure


2. Right-click the group you want to edit, and select Edit Group.3. In the Edit Group dialog, modify the group description as desired.4. Select a VM or vApp, and click the > or < buttons to add or remove the

selection, respectively. Hold the Shift key to select multiple VMs orvApps.

5. Click Ok to save the changes.

Deleting a group of VMs and vAppsYou can delete a group of VMs or vApps.

Procedure


2. Right-click the group node, and select Delete Group.3. Click Yes to confirm.

About the Host group in block storage configurationWhen the Virtual Infrastructure Integrator software is configured for blockstorage, the system automatically creates a host group namedV2I_Only_HostGrp within the same port as the LDEV(s).

Important: Do not modify, use, or delete this group.


12Using auto-deploy for NFS datastores

The Virtual Infrastructure Integrator software provides the ability to deploynew NFS datastores to all ESXi hosts simultaneously. This method differsfrom the current method of VM administrators connecting to each ESXi hostand deploying each host individually. This time saving, efficient featuregreatly reduces the overhead of your deployment operations.

□ Understanding auto-deploy of NFS datastores

□ Auto-deploying NFS datastores to all ESXi hosts

Using auto-deploy for NFS datastores 139Hitachi Virtual Infrastructure Integrator Administration Guide

Understanding auto-deploy of NFS datastoresThe Virtual Infrastructure Integrator software supports the simultaneouslydeployment of NFS datastores. Typically, a storage admin creates an NFSexport, which is mounted as a datastore to one host by the VMware admin.Now, you can select the ESXi Cluster that contains the new NFS datastoreand deploy it to all of the ESXi hosts in one click.

The previous method required you to connect through the vSphere WebClient to each ESXi host individually, and then click Configuration > Storage,and add the NFS datastores one by one.

At a high level, the following steps occur when you initiate the deploymentoperation:1. The Virtual Infrastructure Integrator Web client service plugin collects the

information and sends request to Virtual Infrastructure Integrator server.2. The server then performs the following:

a. Retrieves the list of configured clusters and ESXi hosts.b. Checks the host on which the datastore is mounted.c. Configures the specified datastores to all of the existing vSphere

clusters and ESXi hosts simultaneously using the VMware API. Thatis, excluding the hosts on which the datastore is already mounted.

d. Sends the updated list to the Virtual Infrastructure Integrator Webclient service plugin.

3. The service plugin displays the result in its GUI.

Auto-deploying NFS datastores to all ESXi hosts

Before you begin

The ESXi hosts you want to receive the NFS datastore deployment mustalready be created in the environment.

Procedure


2. In the navigation pane at the left, do the following:a. Click the Datastore entity type.b. Right-click the specific NFS datastore that you want to deploy to all

ESXi host simultaneously, and select Deploy to all Host(s).3. In the Recent Tasks pane, you can view the operation progress and

results.

140 Using auto-deploy for NFS datastoresHitachi Virtual Infrastructure Integrator Administration Guide

Note: If the vSphere Web Client is using the same vCenter Serveras configured in Virtual Infrastructure Integrator Web client serviceplugin, then only the operation progress is displayed on the taskpane.

Using auto-deploy for NFS datastores 141Hitachi Virtual Infrastructure Integrator Administration Guide

142 Using auto-deploy for NFS datastoresHitachi Virtual Infrastructure Integrator Administration Guide

13Managing logs and collecting diagnostic

informationDisplay logs, set logging levels to refine your results, export logs fordiagnostics, and collect diagnostic information.

□ Displaying the Log Viewer

□ Setting logging levels

□ Exporting logs

□ Collecting diagnostic information

□ Displaying the Event Log

□ Displaying Alerts

Managing logs and collecting diagnostic information 143Hitachi Virtual Infrastructure Integrator Administration Guide

Displaying the Log ViewerProcedure

1. Click on the Hitachi Storage Services > Getting Started tab toopen the Log Viewer. Event logs are also available as Actions in theDatastores, All VMs on Hitachi Storage, Groups, Virtual Machines,Backups, and Schedules resource information tables, and display eventinformation specific to those items.

2. Review all events logged by the Hitachi Virtual Infrastructure Integrator.The following event information displays:• Type: Red triangles represent errors, and yellow triangles represent

warnings. Use Filter to set how the events are displayed.• Time: When the event occurred.• Module: Where the event occurred.• Message: Description of the event.

Setting logging levelsThe Virtual Infrastructure Integrator server creates a HDS_V2I.log file torecord all activities and operations.

See Finding server install software and log files on page 68 for log filelocations.

144 Managing logs and collecting diagnostic informationHitachi Virtual Infrastructure Integrator Administration Guide

Using the Virtual Infrastructure Integrator client, you set the followinglogging levels:• Normal: Defines a limited number of progress messages; for example,

starting or stopping a service.• Additional Info: Defines all runtime messages and third-party calls.

Provides details of the parameter values, and returns error codes.

Note: Contact support if you need to run the Virtual Infrastructure Integratorsoftware at any logging level other than normal.

Procedure

1. Go to the Hitachi Storage Services > Getting Started tab.

2. Click the Logging Level icon ( ), and select the desired logging level.• Normal generates a runtime log.• Additional Info generates a debug log.

Exporting logsExport logs for your records or to help you identify issues.

Procedure

1. Go to the Hitachi Storage Services > Getting Started tab, and click

.2. Right-click the log you want to view, and select Export Logs.3. Click Save as, and enter a file name and location for the file.

Collecting diagnostic informationUse this procedure to collect diagnostic information.

See the log information in the section of the Troubleshooting chapter fordetails about collecting logs.

Procedure

1. Go to the Hitachi Storage Services > Getting Started tab, and click

.2. A page launches and begins collecting the diagnostics information. This

includes all logs and configuration details for the entire system, includingvCenter and the Hitachi Virtual Infrastructure Integrator.


Note: The collection and compilation process may take some timeto complete.

3. To download the compressed (.zip) file with all the logs and otherinformation, you will need a valid vCenter user name and password.

4. When prompted, select a location to save the downloaded diagnostic file.5. The compressed diagnostic file can be uncompressed in a local file folder

or sent as an email attachment for HDS Support assistance.

Displaying the Event LogThe Event Log displays the operation records that occur on an entity, suchas VMs, vApps, or groups. Events include backup, clone, and restoreoperations.

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services > VirtualMachines.

2. Right-click the node, and select View Event Log.

Field Description

Start Time Specifies the time the task started.

Completed Time Specifies the time the task completed.

Status Indicates the success or failure of the operation.

Operation Specifies the task accomplished.

Operation Details Indicates the success or failure for the event.

3. Click Close.

Displaying Event Details

Procedure

1. In the navigation tree, navigate to Hitachi Storage Services > VirtualMachines.

2. Right-click the node, and select View Event Log.3. In the Event Log dialog, right-click the event, and select More Info.4. Review the operation details in the dialog that displays.5. Click Close after you finish, and then close the Event Log dialog.


Displaying AlertsThe Virtual Infrastructure Integrator logs provide alert information to helpyou identify and resolve a failing backend task, or any critical error thatoccurs on the vCenter, ESXi, and Hitachi Storage Services.

Procedure

1. In the navigation tree, go to the Hitachi Storage Services > Getting

Started tab, and click on the toolbar.The alerts dialog is displayed.

Field Description

Target Entity name from which the alert is logged.

Host/Cluster Host or cluster ID.

Operation Failed task.

Status Condition of the operation. An displays if the operation fails.

Date Time Date and time of the failure.

Description Describes the failure type.

2. Right-click an alert to display available operations.• Select Refresh to display any new alert messages.• Select More Info to display additional details about the alert.• Select Acknowledge after resolving the alert to remove it from the

list.• Select Acknowledge All to remove all alert messages from the list.• Select View Columns to specify that all columns or only selected

columns display.• Select Export Alerts to save the alert messages to a text file.

3. Click Cancel to exit.


14Troubleshooting Virtual Infrastructure

IntegratorThis document provides information for troubleshooting issues with theVirtual Infrastructure Integrator software.

□ Installation issues

□ Configuration issues

□ Operations issues

Troubleshooting Virtual Infrastructure Integrator 149Hitachi Virtual Infrastructure Integrator Administration Guide

Installation issuesThis document provides information for troubleshooting installation issueswith the Virtual Infrastructure Integrator software.

Issue Possible solution

Virtual Infrastructure

Integrator Web client

service plugin install

screen asks for the IP of

the Virtual Infrastructure

Integrator server, but you

do not know it yet.

You must first install the Virtual Infrastructure Integrator server

software before installing the Virtual Infrastructure Integrator Web

client service plugin software, so you know the server's IP address.


Integrator service is

unreachableNote: This issue only applies to installations where thevSphere Web Client is installed on a separate server from thevCenter Server.

When installing the Virtual Infrastructure Integrator Web Client Pluginor using it for the first time, if for any reason the Virtual InfrastructureIntegratorService is unreachable, you may see an error similar to thefollowing:Error downloading https://198.18.3.205:10005/HSS/HNASV2I.zip. Make sure that the URL is reachable then logout/login to force another download. java.net.ConnectException:Connection refused: connect

When using the vSphere 6.0 Web Client, a simple logout or login actiondoes not work. Instead, you must restart the vSphere Web Clientservice. This is required because VMware has changed their retrymechanism for failed downloads in v6.0.

Upgrading VMware

vCenter™ Server

Appliance™ 6.0 to a new

update causes the Virtual

Infrastructure Integrator

Web Client Plugin

certificate to be

overwritten

This issue occurs when users have upgraded the vCenter ServerAppliance 6.0 servers to vCenter Server Appliance 6.0 Update 1 andthen access the Virtual Infrastructure Integrator Web Client Plugin.

"Unable to connect to the Hitachi Virtual Infrastructure IntegratorServer (3.0.33.0) due to certificate issue. Please check that the HitachiStorage Services Web Client plug-in SSL Certificate 'hdscacert' isinstalled properly in the keystore. Also make sure that VMware vSphereWeb Client service is restarted after successful installation of'hdscarcert' SSL certificate(1052)."

To re-install the hdscacert, run the following command from theaffected vCenter Server Appliance machine:

#keytool -import -trustcacerts –keystore /usr/java/jre-vmware/lib/security/cacerts -storepass changeit -noprompt -alias hdscacert -file hdscacert.cer

Upgrading on VMware

vCenter Server Appliance

responds with error

Upgrade of the Virtual Infrastructure Integrator software on a VMwarevCenter Server Appliance responds with Error inRegisterPluginWithCredentials. However, the Virtual InfrastructureIntegrator software still installs.

150 Troubleshooting Virtual Infrastructure IntegratorHitachi Virtual Infrastructure Integrator Administration Guide


If you receive this error when upgrading the Virtual InfrastructureIntegrator Web Client Plugin on a VMware vCenter Server Applianceserver, manually reboot that server and reinstall.

This error is a known VMware issue.

Configuration issuesThis document provides information for troubleshooting configuration issueswith the Virtual Infrastructure Integrator software.



Integrator Web client service

plugin not visible

1. Confirm the correct installation of the Virtual InfrastructureIntegrator Web client plugin. Consult the setup instructions at Installing Virtual Infrastructure Integrator Web client serviceplugin to vCenter Server on page 69.

2. If using vCenter 5.5, restart the VMware VirtualCenterManagement Webservices.

3. If using vCenter 6.0, perform the following:a. Establish with your users of the VMware vSphere Web

client a time when a restart is acceptable.b. Restart VMware vSphere Web client at the acceptable

time.4. Confirm whether the issue is resolved with the following steps:

a. Close the browser.b. Log in again to the vSphere Web client.c. Clear the cache.d. Check to see if the plugin is visible.


Integrator server not

reachable during

configuration

1. Confirm correct installation of the Virtual InfrastructureIntegrator server. Consult the setup instructions at InstallingVirtual Infrastructure Integrator server software on page 68.

2. Confirm that the Virtual Infrastructure Integrator server isrunning. Navigate to the Virtual Infrastructure Integratorserver VM > Services.

3. Confirm that port 9000 is not blocked by the firewall on theVirtual Infrastructure Integrator server. Check with the VMadministrator about the firewall properties.

vCenter Server not

authenticated

Confirm the following:1. Correct IP address for the vCenter Server.2. Correct credentials for the vCenter account.

Null exceptions after clicking

Finish during Virtual


configuration

Take a screen shot and collect the logs for further analysis, then

contact customer support.

Block storage configuration

not visible

Confirm you have the correct CCI and HORCM settings.



Block Configuration throws

error after selecting HORCM

instance and providing

credentials

Confirm the following:1. HORCM instance is running.2. Credentials for the Hitachi storage server have administrator

privileges.

Operations issuesThis document provides information for troubleshooting operations issueswith the Virtual Infrastructure Integrator software.


Block backup fails due to

permission issue

1. Check the log file error message. It will read similar to thefollowing: Failed to Create SVOL "XX" for LUN id "YY" onblock storage 'XYZ123'. Permission was denied to performthe operation.(HiStor Error 0x0010809E). Error Code =1081502

2. Confirm User Authentication is enabled for CCI LDEV.

Backup fails due to HTI

pool becoming full

If an HTI pool becomes 100 percent full, any subsequent write/readrequest is rejected. The Virtual Infrastructure Integrator software canno longer take additional snapshots, or perform snapshot restore ormount.

To clear the pool, delete the snapshots from the target primary volumeor increase the HTI pool, so that the pool recovers the free space. Notethat deleting some of the snapshots does not increase the free space.

As best practice, limit the HTI threshold to 80 percent. If you anticipatethe pool might fill quickly, set the threshold even lower.

Backup fails due to LUN

ID for SVOL

1. Check the error message. It will read similar to the following:

2. Confirm that the LUN ID for which the backup failed is the correct

datastore. The LUN ID must always be for a primary volume(PVOL).

3. Confirm that the LUN ID is not for a secondary volume (SVOL).

Note: The backup in the above example failed becausethe LUN ID was for an SVOL. The Virtual InfrastructureIntegrator software does not support creation of snapshot



volumes for SVOLs. An SVOL contains the snapshot dataof the PVOL.

4. Confirm you are using the PVOL that was assigned to you by thestorage administrator.

Log collection utility timesout

If the log collection utility Web page times out, it is normally due to anetwork connectivity issue. In other words, the log collection utilitycannot gather the logs due to its port being blocked. The log collectionutility uses port 9000.

Remove the policy that is blocking the port and retry gathering thelogs. If this still fails, collect the logs as described in the following andsend them to customer support for analysis.

• Hitachi folder for the Virtual Infrastructure Integrator server:Copy the entire Hitachi folder located on the Virtual InfrastructureIntegrator server VM. The path is C:\Program Files\Hitachi

• HORCM folder for the Command Control Interface (CCI:) Copy theentire HORCM folder located on Virtual Infrastructure Integratorserver VM. If it was installed on C:\, use the following path: C:\HORCM

• vCenter Server logs: Go to following location on a VM where thevCenter Server is running depending on the versions being used:• vCenter 5.5 (Windows) setup: C:\ProgramData\VMware\VMware

VirtualCenter\Logs\• vCSA 5.5 setup: /var/log/vmware/vpx/• vCenter 6.0 (Windows) setup: C:\ProgramData\VMware

\vCenterServer\logs\vmware-vpx• vCSA 6.0 setup: /storage/log/vmware/vpxd

Obtain the vpxd log file. Hitachi Data Systems recommends that youcollect the latest three log files for vpxd. Sort the log files by dateand time to find the latest copies.

• vSphere Web Client logs: Go to following location on a VM wherethe vSphere Web Client is running depending on the versions beingused:• vCenter 5.5 (Windows) setup: C:\ProgramData\VMware

\vSphere Web Client\serviceability\logs• vCSA 5.5 setup: /var/log/vmware/vsphere-client/logs• vCenter 6.0 (Windows) setup: C:\ProgramData\VMware

\vCenterServer\logs\vsphere-client\logs• vCSA 6.0 setup: /storage/log/vmware/vsphere-client/logs

Hitachi Data Systems recommends that you collect the latest threelog files for vsphere_client_virgo.

Virtual Machine does not

appear in Virtual


inventory

Virtual Machines (VMs) that are hosted on both File and Block serversare not managed by the Virtual Infrastructure Integrator plugin.Therefore, such VMs are not listed in the Virtual InfrastructureIntegrator inventory.

This issue can occur in the following scenarios:• If you have a VM that is hosted on local datastore and then add

another datastore that is from file (NAS) or block storage.



• If you have NFS exports and a block datastore in your environmentand then create a VM that has hard disks from both file and blockstorage servers.

• If a VM has an RDM device configured that is not a CCI device.

Certain Virtual


workflows sometimes fail

Certain Virtual Infrastructure Integrator workflows that use theReconfigureVM function of the VMware Storage vMotion software canfail. Workflows that may fail include: restore, mount, unmount, clone,and unmount snapshot VMDKs.

The failure displays a message, such as "PBM error occurred duringPreMigrateCheckCallback" with the Unmount Snapshot VMDKsoperation.

This failure occurs when the VMware Profile-Driven Storage service isnot running. The vSphere profile-driven storage service must berunning for the vCenter Server that is currently configured with VirtualInfrastructure Integrator. Confirm the Profile-Driven Storage service isrunning.

For vCenter Server Appliance:1. To check the status of the service, issue the following command:

service vmware-sps status2. To start the vmware-sps service, issue the following command:

service vmware-sps start3. To restart the vmware-sps service, issue the following command:

service vmware-sps restart

For vCenter Server:1. Log in as an administrator to the server that is running vCenter

Server.2. Click Start > Run, type services.msc and click Ok.3. From the list of services, check the status of the Profile-Driven

Storage service.

This is a known VMware issue. See the VMware Knowledge Base Article

2118551 for more information.


Integrator plugin

extension fails to

automatically unregister

The Virtual Infrastructure Integrator registration utility can fail toautomatically unregister the plugin extension from vCenter Server'sManaged Object Browser (MOB) inventory. The issue may occur if thevCenter services are not in running state.

You can manually unregister the plugin by accessing the registrationutility from the command line or through the MOB interface.

From the command line interface:1. Open a command window by Start > run > cmd.2. Go to the HNAS-V2I Regutility by issuing the following command:

C:\Program Files\Hitachi\HNAS-V2I\Server\HNAS-V2IRegUtil.exe

3. Unregister the plugin by issuing the following command: removecom.hds.hnasv2i

From the MOB, follow the instructions in the Resolution section of theVMware Knowledge Base article at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1025360


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1025360




Snapshot Schedule task

remains in progress

When a Virtual Infrastructure Integrator Snapshot Schedule task takeslonger to complete than the SOAP API Auth timeout setting, the SOAPAPI Auth expires. An Auth Error is logged in the Virtual InfrastructureIntegrator log.

This issue only occurs if the VMware Configuration for SOAP (API)session timeout is less than the time required to complete the VirtualInfrastructure Integrator operation.

You can extend the timeout value of the SOAP API session to avoid theissue. You also may need to restart the VMware VirtualCenter Serverservice after making this change.

See the VMware Knowledge Base article at http://kb.vmware.com/kb/2004663 for details about session timeout values.

Quiesced snapshot fails

due to VMware Tools

If you encounter issues quiescing a VM, ensure that you have VMwareTools version 10.0.9 or later and all service packs, hot fixes, andupdates installed for your Windows Guest OS. VMware has documentedquiesce issues with VMware Tools earlier than version 10.0.9.

See the following VMware Tools Release Notes and Knowledge Basearticles for more information:• https://pubs.vmware.com/Release_Notes/en/vmwaretools/1009/

vmware-tools-1009-release-notes.html• https://kb.vmware.com/selfservice/microsites/search.do?

cmd=displayKC&docType=kc&externalId=2115997&sliceId=1&docTypeID=DT_KB_1_1&dialogID=115566891&stateId=0%200%20115596452

• https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2145280&sliceId=2&docTypeID=DT_KB_1_1&dialogID=115566891&stateId=0%200%20115596452

After ensuring you have VMware Tools version 10.0.9 or later and thatall service packs, hot fixes and updates have been applied to the VMO/S (VM163_1), retry the quiesce snapshot operation. If the quiescesnapshot operation continues to fail, contact VMware Support, as this isa known VMware issue, not a Virtual Infrastructure Integrator issue.


Integrator fails to connect

after deletion/creation of

HORCM device

The following message displays:

Error accessing configured Hitachi Block Storage: Unable to updateHitachi Block Storage configuration information for Serial Number'212943' failed with error: Failed to login to block storage device'212943'. A command device could not be found for the device. (HiStorError 0x001080AB). (HiStor Error 0x00180AB).

If this issue occurs, restart the ESXi host.


http://kb.vmware.com/kb/2004663

http://kb.vmware.com/kb/2004663

https://pubs.vmware.com/Release_Notes/en/vmwaretools/1009/vmware-tools-1009-release-notes.html

https://pubs.vmware.com/Release_Notes/en/vmwaretools/1009/vmware-tools-1009-release-notes.html

https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2115997&sliceId=1&docTypeID=DT_KB_1_1&dialogID=115566891&stateId=0%200%20115596452








AInstalling Virtual Infrastructure

Integrator Command Line Interface(CLI)

The Virtual Infrastructure Integrator CLI provides the following Windows andLinux commands:

• Snapshot backup: v2i-backup• File Clone: v2i-clone• Mount: v2i-mount• Restore: v2i-restore• Tool to perform Group/Host operations: V2i-tools

At the command prompt, enter the command name and press Enter todisplay the command's help, which includes usage parameters and examples.

□ Installing Virtual Infrastructure Integrator CLI for Windows

□ Installing Virtual Infrastructure Integrator CLI for Linux

Installing Virtual Infrastructure Integrator Command Line Interface (CLI) 157Hitachi Virtual Infrastructure Integrator Administration Guide

Installing Virtual Infrastructure Integrator CLI for WindowsInstalling the Virtual Infrastructure Integrator client automatically installs theVirtual Infrastructure Integrator Command Line Interface (CLI) to: ..\ProgramFiles\Hitachi\HDS-V2I\Server\WindowsCLI\

If you do not wish to install the client, but need the commands installed on aWindows system:

Procedure

1. Locate your Virtual Infrastructure Integrator Installation CD orcompressed (.zip) file.

2. From the Virtual Infrastructure Integrator installation directory, copythe ..\HDS-V2I-CLI\WindowsCLI\ directory to your Windows system.

Installing Virtual Infrastructure Integrator CLI for LinuxUse these steps to install the CLI for Linux.

Procedure

1. Locate your Hitachi Virtual Infrastructure Integrator Installation CD orcompressed (.zip) file.

2. From the Hitachi Virtual Infrastructure Integrator installation directory,copy HDS_V2I_CLI_for_linux_x86.tar.gz from the ..\HDS-V2I-CLI\LinuxCLI\ directory to your Linux system.

3. Create a soft link to libssl.so.6 in your current 32-bit lib directory thatreferences your current 32-bit libssl shared library file.For example, if your current 32-bit libssl file is named libssl.so.1.0.0,enter ln -s /lib32/libssl.so.1.0.0 /lib32/libssl.so.6.

4. Create a soft link to libcrypto.so.6 in your current 32-bit lib directorythat references your current 32-bit libcrypto shared library file.For example, if your current 32-bit libcrypto file is named libcrypto.so.1.0.0, enter ln -s /lib32/libcrypto.so.1.0.0 /lib32/libcrypto.so.6.

ResultAfter the establishing the soft links, you can then run the VirtualInfrastructure Integrator commands for Linux by entering the command atthe shell prompt.

158 Installing Virtual Infrastructure Integrator Command Line Interface (CLI)Hitachi Virtual Infrastructure Integrator Administration Guide

BInstalling Virtual Infrastructure

Integrator Command Control Interface(CCI)

The Hitachi Command Control Interface (CCI) software is used to configureand perform block storage system configuration and data managementoperations on Hitachi RAID storage systems.

Important:• Be aware that the CCI installation method for Virtual Infrastructure

Integrator differs from others with which you may be familiar.• Block storage requires CCI software to configure its RAID storage.• File-only NAS configurations do not require CCI software.

Requirements• Set the pop-ups blocker on your browser to allow pop-ups from https://

support.hds.com.• The CCI software needs to be installed on the same system as the Virtual

Infrastructure Integrator server. SeeCommand Control Interface (CCI)requirements on page 60 for the supported CCI version level.

• For the CCI connection, the Virtual Infrastructure Integrator supports onlythe in-band method.

□ Installing CCI software

□ Using CCI and HORCM as a Windows service

□ Configuring Command Devices for the Virtual Infrastructure Integrator

□ Using multiple HORCM files for a single Virtual Infrastructure Integrator

□ Determining presence of another CCI Command Device

□ Example HORCM configuration files

Installing Virtual Infrastructure Integrator Command Control Interface (CCI) 159Hitachi Virtual Infrastructure Integrator Administration Guide

Installing CCI softwareUse these steps to install the Command Control Interface (CCI) software forthe Virtual Infrastructure Integrator product.

Before you begin

Set the pop-ups blocker on your browser to allow pop-ups from https://support.hds.com.

Important: Be aware that the CCI installation method for VirtualInfrastructure Integrator differs from others with which you may be familiar.Follow the instructions here closely.

For more information about selecting and installing the appropriate software,see the Hitachi Command Control Interface documentation. To locate the CCIdocumentation and software for installation, follow these steps:

Procedure

1. Using any supported browser, go to the HDS portal site at https://partner.hds.com/ and log in with your credentials.

2. In the Search Partner Connect field at the top right, type downloadCCI, and click the search button.

3. Click the PDF name and save the documentation zip file to a location ofyour choosing.

4. To obtain the product software download, select the Products Downloadscheckbox at the right of the screen.A list displays showing the search results with all matching softwarepackage names.

5. Click the software name of the download you want, then clickDownload.

6. A terms and conditions page displays. Once you have read it, click theradio button next to "I have read and accepted the terms..." and click IAgree to continue.

7. Select the location to download the iso zip file.

Using CCI and HORCM as a Windows serviceUsing CCI and Hitachi Open Remote Copy (HORCM) as a Windows serviceallows you to start and stop the HORCM instance without having to access itmanually through the CLI. This saves you time when you must restart theVirtual Infrastructure Integrator software.

Before you begin• Have administrator privileges.

160 Installing Virtual Infrastructure Integrator Command Control Interface (CCI)Hitachi Virtual Infrastructure Integrator Administration Guide

https://partner.hds.com/

https://partner.hds.com/

• Command Device LDEV is created and mapped on the VirtualInfrastructure Integrator server VM.

• CCI is installed on the Virtual Infrastructure Integrator server VM.• See Install prerequisites on page 64

The CCI software provides the svcexe.exe command and a sample script file(HORCM0_run.txt), so that CCI can be started automatically as a service.

Note: The following procedure uses HORCM instance number = 0. If yourHORCM instance has a different number, replace the occurrences of 0 withyour instance number in both:• HORCM0_run.txt script file name• Any steps where it occurs

Procedure

1. Register the CCI (HORCM) instance as a service by adding the CCIinstance using the following command:C:\HORCM\tool\>svcexe /S=HORCM0 "/A=C:\HORCM\tool\svcexe.exe"

2. Customize the sample script according to the CCI instance, if needed.For details, see the descriptions in the HORCM0_run.txt file.

3. Set the user account in the Virtual Infrastructure Integrator software inone of two ways:• In the Virtual Infrastructure Integrator GUI, navigate to

Administrative Tools > Services > Select HORCM0 > Logon• In the Virtual Infrastructure Integrator CLI, issue the following

command:C:\HORCM\tool\>sc config HORCM0 obj= AccountName password=password

4. If the system administrator used the default account (LocalSystem), addHORCM_EVERYCLI=1 to the script:For INSTANCE# X, change to HORCMINST=X as needed:START:set HORCM_EVERYCLI=1set HORCMINST=0set HORCC_LOG=STDERROUTC:\HORCM\etc\horcmstart.exeexit 0

5. Start the CCI instance from the service.6. Confirm starting and stopping using horcmstart 0 and horcmshutdown

0.7. Verify that HORCM 0 starts from the service and that HORCM 0 started

automatically from reboot, using the following command:C:\HORCM\tool\>net start HORCM0


8. Stop CCI as a service with the following command:C:\HORCM\tool\>net stop HORCM0

Configuring Command Devices for the Virtual InfrastructureIntegrator

Following are example steps for Command Device configuration for theVirtual Infrastructure Integrator. In some cases, it may be necessary to useor substitute values specific to your systems.

If you are using multiple HORCM files with a single Virtual InfrastructureIntegrator, see Using multiple HORCM files for a single Virtual InfrastructureIntegrator on page 163.

Procedure

1. Install the CCI software on a Windows VM where the VirtualInfrastructure Integrator will be installed. For information aboutsupported Windows operating system versions, see Operating systemrequirements on page 58.

2. Map the Command Device as a Remote Device Mapping to the WindowsVM. To do this, navigate to the Windows Disk Manager, put the newlyadded Command Device disk online, and initialize it as MBR.

3. Using any available text editor (such as Notepad), create the HORCMconfiguration file (for example, horcm0.conf) in the Windows operatingsystem directory (for example, C:\Windows). Any HORCM instancenumber can be used; the instance number "0" is shown in this and thefollowing example steps.Following is a simple example of a HORCM configuration file:HORCM_CMD#\\.\CMD-<Serial # of Raid System>\\.\CMD-212943For other systems, the serial number value would be replaced by theappropriate serial number.

4. Start the HORCM instance (instance 0 in this example) from thecommand prompt:C:\HORCM\etc>horcmstart.exe 0starting HORCM inst 0HORCM inst 0 starts successfully

5. After the HORCM instance (instance 0 in this example) is running, makesure there are no other Command Devices from the same HitachiStorage platform and under the same Host group. If there are anypresent, remove them from the Windows VM. For more information, see Determining presence of another CCI Command Device on page 163.


Note: If a Command Device needs to be removed, remove the onethat is not running the HORCM instance for the VirtualInfrastructure Integrator.

Using multiple HORCM files for a single VirtualInfrastructure Integrator

When you configure multiple HORCM files for a single Virtual InfrastructureIntegrator, certain components are required.

For a fully certified and supported solution, include the following components:• Dedicated VM that contains only the Virtual Infrastructure Integrator

HORCM instance.• Dedicated Virtual Infrastructure Integrator CCI and Command device.

Determining presence of another CCI Command DeviceThe following examples demonstrate the commands to be executed todetermine whether another CCI Command Device (LDEV) is present.

Example 1: Only one Command Device is present

The following output shows a valid configuration, with one Command Deviceon one Hitachi Storage server.

Example 2: Two Command Devices present from the same Hitachi StorageServer and same Host group

The following output shows an invalid configuration. There should be justone CCI LDEV for the same Hitachi Storage server and same Host group inthe Windows VM. You would need to remove the CCI LDEV that is not usedfor Virtual Infrastructure Integrator from this Windows VM. In this case, it isLDEV 18.


Example 3: Two Command Devices are present but belong to differentHitachi Storage servers

The following output shows a valid configuration, where there are twoCommand Devices, but they belong to different Hitachi Storage servers.There is no need to change anything.

Example 4: Multiple storage platforms and Command Devices

This example is more complex. For the purpose of this example, assumethere is one Command Device configured for one storage platform and twoCommand Devices configured for a second storage platform.

In the example output, on the 410016 storage server, you would need toremove the CCI LDEV ED, which is not being used for Virtual InfrastructureIntegrator, but keep LDEV C5 on that same storage server and LDEV 12 onthe 213466 storage server.

Note: Compare the LDEV number displayed in the CLI output with the CCILDEV number in the Hitachi Storage server and make sure to remove thecorrect CCI LDEV.

To remove the CCI LDEV from the Windows VM, follow these steps:1. Open the Edit Settings window for the Windows VM.2. Select the hard disk to be removed and click the Remove button.


3. Click OK to complete the action.

Example HORCM configuration filesWhen you are configure Command Devices for the Virtual InfrastructureIntegrator and need to create the HORCM configuration file, follow thesupported examples here.

Supported:

Here are two simple examples of supported HORCM configuration files,horcm0.conf, where the serial number of the associated RAID system is212943. For other systems, the serial number value would be replaced by theappropriate serial number.

Configuration 1:HORCM_CMD\\.\PhysicalDrive#<physical drive number of CCI LDEV>


Configuration 2:HORCM_CMD\\.\CMD-Serial#<Hitachi Storage Array serial number>\\.\CMD-212943Unsupported:

For reference, following are some examples of unsupported HORCMconfiguration files:

Important: This list is not comprehensive; other unsupported examplesexist. However, only Configuration 1 and 2 above are supported. All otherconfigurations are unsupported.

HORCM_MON#ip_address service poll(10ms) timeout(10ms)localhost 31000 -1 3000HORCM_MON#ip_address service poll(10ms) timeout(10ms)127.0.0.1 11000 1000 6000HORCM_CMD\\.\IPCMD-203.160.205.211-31001 \\.\IPCMD-203.160.205.211-31002HORCM_INST#dev_group ip_address serviceGW 127.0.0.1 11001HORCM_LDEV#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#GW GW_2 410670 0a:02HORCM_CMD#\\?\Volume{34001ca5-2704-11e6-80ba-005056a24f91}


CUsing Virtual Infrastructure IntegratorCommand Line Interface with VMware

PowerCLIThe following PowerCLI script samples demonstrate how you can use theVirtual Infrastructure Integrator Command Line Interface (CLI) in Windows toinitiate backup, File Clone , and restore operations.

□ Fast Clone script sample

□ Restore script sample

□ Snapshot backup script sample

Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLI 167Hitachi Virtual Infrastructure Integrator Administration Guide

Fast Clone script sample<#------------------------------------------------------------------------- Sample HNAS-V2I command FastClone (v2i-clone) Run FastClone against all VMs registered on specified VMHost and stored on HNAS server-------------------------------------------------------------------------#>

<#--- vCenter Variables ---#>$vCenterSrv = '192.168.35.174'$vCenterUsr = 'administrator'$vCenterPasswd = 'password'$vCenterProtocol = 'https'

#--- Connect to vCenter Server$objvCenterSrv=Connect-VIServer -Server $vCenterSrv -Protocol ` $vCenterProtocol -User $vCenterUsr -Password $vCenterPasswdWrite-Host "Connected to vCenter Server: $vCenterSrv"

#--- Find all VMs registered on specified VMHost and stored on HNAS server$vms = Get-VM -Datastore 'hnas_datastore' | ` Where-Object { $_.VMHost.Name -eq '192.168.46.226' }if ($vms) { #--- Run FastClone against all VMs registered on specified VMHost #--- and stored on HNAS storage foreach ($vm in $vms){ #--- Call v2i-clone.exe here &c:\hnas-v2i\v2i-clone.exe -HNASV2IServerIP '192.168.35.174' ` -HostOrClusterName '192.168.46.226' ` -SourceVM $vm ` -CloneName ([string]$vm+"_clone") ` -NoOfClone 1 }} else { Write-Warning "No VMs stored in HNAS Server Found"}

#--- Disconnect to VI ServerDisconnect-VIServer -Server $objvCenterSrv -Confirm:$FalseWrite-Host "Disconnected from vCenter Server: $vCenterSrv"

168 Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLIHitachi Virtual Infrastructure Integrator Administration Guide

Restore script sample<#------------------------------------------------------------------------- Sample HNAS-V2I command Restore (v2i-restore) Restore a latest snapshot to all VMs registered on specified VMHost and stored on HNAS storage-------------------------------------------------------------------------#>



#--- Find all VMs registered on specified VMHost and stored on HNAS server$vms = Get-VM -Datastore 'hnas_datastore' | ` Where-Object { $_.VMHost.Name -eq '192.168.46.226' }if ($vms) { #--- Restore a lastest snapshot to all VMs registered on #--- specified VMHost and stored on HNAS storage foreach ($vm in $vms) { #--- Call v2i-restore.exe here &c:\hnas-v2i\v2i-restore.exe -HNASV2IServerIP '192.168.35.174' ` -HostOrClusterName '192.168.46.226'` -SourceVM $vm ` -Confirm }} else { Write-Warning "No VMs stored in HNAS Server Found"}

#--- Disconnect to VI ServerDisconnect-VIServer -Server $vCenterSrv -Confirm:$FalseWrite-Host "Disconnected from vCenter Server: $vCenterSrv"

Snapshot backup script sample<#------------------------------------------------------------------------- Sample HNAS-V2I command Snapshot Backup (v2i-backup)

Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLI 169Hitachi Virtual Infrastructure Integrator Administration Guide

Take Snapshot Backup for all VMs registered on specified VMHost and stored on HNAS storage-------------------------------------------------------------------------#>



#--- Find all VMs registered on specified VMHost and stored on HNAS server$vms = Get-VM -Datastore 'hnas_datastore' | ` Where-Object { $_.VMHost.Name -eq '192.168.46.226' }

#--- Take Snapshot Backup for all VMs registered on specified VMHost#--- and stored on HNAS storageif ($vms){ foreach ($vm in $vms){ #--- Call v2i-backup.exe here &c:\hnas-v2i\v2i-backup.exe -HNASV2IServerIP '192.168.35.174' ` -HostOrClusterName '192.168.46.226' ` -SourceVM $vm ` -BackupName ([string]$vm+"_bkup") }} else { Write-Warning "No VMs stored in HNAS Server Found"}

#--- Disconnect to VI ServerDisconnect-VIServer -Server $objvCenterSrv -Confirm:$FalseWrite-Host "Disconnected from VI Server: $vCenterSrv"

170 Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLIHitachi Virtual Infrastructure Integrator Administration Guide

DOpen source and third-party licensing

This section lists the Open Source and third-party Software Copyrights andLicenses for software used by the Hitachi Virtual Infrastructure Integratorproduct.

□ Axis2

□ OpenSSL

□ Jetty Server

□ Google Charts

□ Winsw

□ Apache 2.0 license

□ Eclipse Public License Version 1.0

Open source and third-party licensing 171Hitachi Virtual Infrastructure Integrator Administration Guide

Axis2This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

Portions Copyright 2006 International Business Machines Corp.

Portions Copyright 2005-2007 WSO2, Inc.

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

Portions Copyright 2006 International Business Machines Corp.

Portions Copyright 2005-2007 WSO2, Inc.

This product also includes schemas and specification developed by:

- the W3C consortium (http://www.w3c.org)

This product also includes WS-* schemas developed by International

Business Machines Corporation, Microsoft Corporation, BEA Systems,

TIBCO Software, SAP AG, Sonic Software, and VeriSign

This product also includes a WSDL developed by salesforce.com

- Copyright 1999-2006 salesforce.com, inc.

Portions of the included xmlbeans library were originally based on thefollowing:

- software copyright (c) 2000-2003, BEA Systems, <http://www.bea.com/>.http://archive.apache.org/dist/axis/axis2/java/core/1.5.4/axis2-1.5.4-bin.zip

OpenSSLCopyright (c) 1998-2011 The OpenSSL Project. All rights reserved.

Copyright (C) 1995-1998 Eric Young ([email protected])

This product includes cryptographic software written by Eric Young. Thisproduct includes software written by Tim Hudson ([email protected]).

http://www.openssl.org/

OpenSSL License

/*===============================================

172 Open source and third-party licensingHitachi Virtual Infrastructure Integrator Administration Guide

http://archive.apache.org/dist/axis/axis2/java/core/1.5.4/axis2-1.5.4-bin.zip

http://www.openssl.org/

* Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:** 1. Redistributions of source code must retain the above copyright* notice, this list of conditions and the following disclaimer.** 2. Redistributions in binary form must reproduce the above copyright* notice, this list of conditions and the following disclaimer in* the documentation and/or other materials provided with the* distribution.** 3. All advertising materials mentioning features or use of this* software must display the following acknowledgment:* "This product includes software developed by the OpenSSL Project* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"** 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be usedto* endorse or promote products derived from this software without* prior written permission. For written permission, please contact* [email protected].** 5. Products derived from this software may not be called "OpenSSL"* nor may "OpenSSL" appear in their names without prior written* permission of the OpenSSL Project.** 6. Redistributions of any form whatsoever must retain the following* acknowledgment:* "This product includes software developed by the OpenSSL Project* for use in the OpenSSL Toolkit (http://www.openssl.org/)"** THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' ANDANY* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECTOR* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT,* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED* OF THE POSSIBILITY OF SUCH DAMAGE.*===============================================


** This product includes cryptographic software written by Eric Young* ([email protected]). This product includes software written by Tim* Hudson ([email protected]).**/

Original SSLeay License/* Copyright (C) 1995-1998 Eric Young ([email protected])* All rights reserved.** This package is an SSL implementation written* by Eric Young ([email protected]).* The implementation was written so as to conform with Netscapes SSL.** This library is free for commercial and non-commercial use as long as* the following conditions are aheared to. The following conditions* apply to all code found in this distribution, be it the RC4, RSA,* lhash, DES, etc., code; not just the SSL code. The SSL documentation* included with this distribution is covered by the same copyright terms* except that the holder is Tim Hudson ([email protected]).** Copyright remains Eric Young's, and as such any Copyright notices in* the code are not to be removed.* If this package is used in a product, Eric Young should be given attribution* as the author of the parts of the library used.* This can be in the form of a textual message at program startup or* in documentation (online or textual) provided with the package.** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:* 1. Redistributions of source code must retain the copyright* notice, this list of conditions and the following disclaimer.* 2. Redistributions in binary form must reproduce the above copyright* notice, this list of conditions and the following disclaimer in the* documentation and/or other materials provided with the distribution.* 3. All advertising materials mentioning features or use of this software* must display the following acknowledgement:* "This product includes cryptographic software written by* Eric Young ([email protected])"* The word 'cryptographic' can be left out if the rouines from the library* being used are not cryptographic related :-).* 4. If you include any Windows specific code (or a derivative thereof) from* the apps directory (application code) you must include anacknowledgement:* "This product includes software written by Tim Hudson([email protected])"** THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE


* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORSBE LIABLE* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF* SUCH DAMAGE.** The licence and distribution terms for any publically available version or* derivative of this code cannot be changed. i.e. this code cannot simply be* copied and put under another distribution licence* [including the GNU Public Licence.]*/

Jetty ServerCopyright 1995-2015 Mort Bay Consulting Pty Ltd.

http://www.eclipse.org/downloads/download.php?file=/jetty/updates/jetty-bundles-9.x/9.2.6.v20141205/Jetty-bundles-repository-9.2.6.v20141205.zip

The Jetty Server is dual-licensed under both:

Apache 2.0 license on page 176

Eclipse Public License Version 1.0 on page 180

Google ChartsGoogle Charts

Copyright Google Inc. 2009-2015

https://www.google.com/jsapi

Google Charts is licensed under Apache 2.0 license on page 176

WinswCopyright (c) 2010 Kohsuke Kawaguchi, Sun Microsystems, Inc., CloudBees,Inc.

http://repo.jenkins-ci.org/releases/com/sun/winsw/winsw/1.17/




https://www.google.com/jsapi

http://repo.jenkins-ci.org/releases/com/sun/winsw/winsw/1.17/

Permission is hereby granted, free of charge, to any person

obtaining a copy of this software and associated documentation

files (the "Software"), to deal in the Software without

restriction, including without limitation the rights to use,

copy, modify, merge, publish, distribute, sublicense, and/or sell

copies of the Software, and to permit persons to whom the

Software is furnished to do so, subject to the following

conditions:

The above copyright notice and this permission notice shall be

included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING

FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR

OTHER DEALINGS IN THE SOFTWARE.

Apache 2.0 licensehttp://www.apache.org/licenses/LICENSE-2.0

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, anddistribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by thecopyright owner that is granting the License.


http://www.apache.org/licenses/LICENSE-2.0

"Legal Entity" shall mean the union of the acting entity and all other entitiesthat control, are controlled by, or are under common control with that entity.For the purposes of this definition, "control" means (i) the power, direct orindirect, to cause the direction or management of such entity, whether bycontract or otherwise, or (ii) ownership of fifty percent (50%) or more of theoutstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercisingpermissions granted by this License.

"Source" form shall mean the preferred form for making modifications,including but not limited to software source code, documentation source, andconfiguration files.

"Object" form shall mean any form resulting from mechanical transformationor translation of a Source form, including but not limited to compiled objectcode, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form,made available under the License, as indicated by a copyright notice that isincluded in or attached to the work (an example is provided in the Appendixbelow).

"Derivative Works" shall mean any work, whether in Source or Object form,that is based on (or derived from) the Work and for which the editorialrevisions, annotations, elaborations, or other modifications represent, as awhole, an original work of authorship. For the purposes of this License,Derivative Works shall not include works that remain separable from, ormerely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

"Contribution" shall mean any work of authorship, including the originalversion of the Work and any modifications or additions to that Work orDerivative Works thereof, that is intentionally submitted to Licensor forinclusion in the Work by the copyright owner or by an individual or LegalEntity authorized to submit on behalf of the copyright owner. For thepurposes of this definition, "submitted" means any form of electronic, verbal,or written communication sent to the Licensor or its representatives,including but not limited to communication on electronic mailing lists, sourcecode control systems, and issue tracking systems that are managed by, or onbehalf of, the Licensor for the purpose of discussing and improving the Work,but excluding communication that is conspicuously marked or otherwisedesignated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalfof whom a Contribution has been received by Licensor and subsequentlyincorporated within the Work.

2. Grant of Copyright License.


Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable copyright license to reproduce, prepare Derivative Works of,publicly display, publicly perform, sublicense, and distribute the Work andsuch Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable (except as stated in this section) patent license to make, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, wheresuch license applies only to those patent claims licensable by suchContributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which suchContribution(s) was submitted. If You institute patent litigation against anyentity (including a cross-claim or counterclaim in a lawsuit) alleging that theWork or a Contribution incorporated within the Work constitutes direct orcontributory patent infringement, then any patent licenses granted to Youunder this License for that Work shall terminate as of the date such litigationis filed.

4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Worksthereof in any medium, with or without modifications, and in Source orObject form, provided that You meet the following conditions:

1. You must give any other recipients of the Work or Derivative Works a copyof this License; and

2. You must cause any modified files to carry prominent notices stating thatYou changed the files; and

3. You must retain, in the Source form of any Derivative Works that Youdistribute, all copyright, patent, trademark, and attribution notices from theSource form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, thenany Derivative Works that You distribute must include a readable copy of theattribution notices contained within such NOTICE file, excluding those noticesthat do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of theDerivative Works; within the Source form or documentation, if provided alongwith the Derivative Works; or, within a display generated by the DerivativeWorks, if and wherever such third-party notices normally appear. Thecontents of the NOTICE file are for informational purposes only and do notmodify the License. You may add Your own attribution notices withinDerivative Works that You distribute, alongside or as an addendum to the


NOTICE text from the Work, provided that such additional attribution noticescannot be construed as modifying the License. You may add Your owncopyright statement to Your modifications and may provide additional ordifferent license terms and conditions for use, reproduction, or distribution ofYour modifications, or for any such Derivative Works as a whole, providedYour use, reproduction, and distribution of the Work otherwise complies withthe conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, any Contribution intentionally submittedfor inclusion in the Work by You to the Licensor shall be under the terms andconditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify theterms of any separate license agreement you may have executed withLicensor regarding such Contributions.

6. Trademarks.

This License does not grant permission to use the trade names, trademarks,service marks, or product names of the Licensor, except as required forreasonable and customary use in describing the origin of the Work andreproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor providesthe Work (and each Contributor provides its Contributions) on an "AS IS"BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditionsof TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR APARTICULAR PURPOSE. You are solely responsible for determining theappropriateness of using or redistributing the Work and assume any risksassociated with Your exercise of permissions under this License.

8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberateand grossly negligent acts) or agreed to in writing, shall any Contributor beliable to You for damages, including any direct, indirect, special, incidental, orconsequential damages of any character arising as a result of this License orout of the use or inability to use the Work (including but not limited todamages for loss of goodwill, work stoppage, computer failure ormalfunction, or any and all other commercial damages or losses), even ifsuch Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose tooffer, and charge a fee for, acceptance of support, warranty, indemnity, or


other liability obligations and/or rights consistent with this License. However,in accepting such obligations, You may act only on Your own behalf and onYour sole responsibility, not on behalf of any other Contributor, and only ifYou agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason ofyour accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplatenotice, with the fields enclosed by brackets "[]" replaced with your ownidentifying information. (Don't include the brackets!) The text should beenclosed in the appropriate comment syntax for the file format. We alsorecommend that a file or class name and description of purpose be includedon the same "printed page" as the copyright notice for easier identificationwithin third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may notuse this file except in compliance with the License. You may obtain a copy ofthe License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributedunder the License is distributed on an "AS IS" BASIS, WITHOUTWARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. Seethe License for the specific language governing permissions and limitationsunder the License.

Eclipse Public License Version 1.0https://www.eclipse.org/legal/epl-v10.html

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THISECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION ORDISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCEOF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentationdistributed under this Agreement, and

b) in the case of each subsequent Contributor:

i) changes to the Program, and


https://www.eclipse.org/legal/epl-v10.html

ii) additions to the Program;

where such changes and/or additions to the Program originate from and aredistributed by that particular Contributor. A Contribution 'originates' from aContributor if it was added to the Program by such Contributor itself oranyone acting on such Contributor's behalf. Contributions do not includeadditions to the Program which: (i) are separate modules of softwaredistributed in conjunction with the Program under their own licenseagreement, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents " mean patent claims licensable by a Contributor which arenecessarily infringed by the use or sale of its Contribution alone or whencombined with the Program.

"Program" means the Contributions distributed in accordance with thisAgreement.

"Recipient" means anyone who receives the Program under this Agreement,including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grantsRecipient a non-exclusive, worldwide, royalty-free copyright license toreproduce, prepare derivative works of, publicly display, publicly perform,distribute and sublicense the Contribution of such Contributor, if any, andsuch derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grantsRecipient a non-exclusive, worldwide, royalty-free patent license underLicensed Patents to make, use, sell, offer to sell, import and otherwisetransfer the Contribution of such Contributor, if any, in source code andobject code form. This patent license shall apply to the combination of theContribution and the Program if, at the time the Contribution is added by theContributor, such addition of the Contribution causes such combination to becovered by the Licensed Patents. The patent license shall not apply to anyother combinations which include the Contribution. No hardware per se islicensed hereunder.

c) Recipient understands that although each Contributor grants the licensesto its Contributions set forth herein, no assurances are provided by anyContributor that the Program does not infringe the patent or other intellectualproperty rights of any other entity. Each Contributor disclaims any liability toRecipient for claims brought by any other entity based on infringement ofintellectual property rights or otherwise. As a condition to exercising therights and licenses granted hereunder, each Recipient hereby assumes soleresponsibility to secure any other intellectual property rights needed, if any.For example, if a third party patent license is required to allow Recipient to


distribute the Program, it is Recipient's responsibility to acquire that licensebefore distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficientcopyright rights in its Contribution, if any, to grant the copyright license setforth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code formunder its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties andconditions, express and implied, including warranties or conditions of title andnon-infringement, and implied warranties or conditions of merchantabilityand fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages,including direct, indirect, special, incidental and consequential damages, suchas lost profits;

iii) states that any provisions which differ from this Agreement are offered bythat Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor,and informs licensees how to obtain it in a reasonable manner on or througha medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and

b) a copy of this Agreement must be included with each copy of the Program.

Contributors may not remove or alter any copyright notices contained withinthe Program.

Each Contributor must identify itself as the originator of its Contribution, ifany, in a manner that reasonably allows subsequent Recipients to identify theoriginator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities withrespect to end users, business partners and the like. While this license isintended to facilitate the commercial use of the Program, the Contributor whoincludes the Program in a commercial product offering should do so in amanner which does not create potential liability for other Contributors.Therefore, if a Contributor includes the Program in a commercial productoffering, such Contributor ("Commercial Contributor") hereby agrees to


defend and indemnify every other Contributor ("Indemnified Contributor")against any losses, damages and costs (collectively "Losses") arising fromclaims, lawsuits and other legal actions brought by a third party against theIndemnified Contributor to the extent caused by the acts or omissions ofsuch Commercial Contributor in connection with its distribution of theProgram in a commercial product offering. The obligations in this section donot apply to any claims or Losses relating to any actual or alleged intellectualproperty infringement. In order to qualify, an Indemnified Contributor must:a) promptly notify the Commercial Contributor in writing of such claim, andb) allow the Commercial Contributor to control, and cooperate with theCommercial Contributor in, the defense and any related settlementnegotiations. The Indemnified Contributor may participate in any such claimat its own expense.

For example, a Contributor might include the Program in a commercialproduct offering, Product X. That Contributor is then a CommercialContributor. If that Commercial Contributor then makes performance claims,or offers warranties related to Product X, those performance claims andwarranties are such Commercial Contributor's responsibility alone. Under thissection, the Commercial Contributor would have to defend claims against theother Contributors related to those performance claims and warranties, and ifa court requires any other Contributor to pay any damages as a result, theCommercial Contributor must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM ISPROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONSOF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUTLIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Each Recipient is solely responsible for determining theappropriateness of using and distributing the Program and assumes all risksassociated with its exercise of rights under this Agreement , including but notlimited to the risks and costs of program errors, compliance with applicablelaws, damage to or loss of data, programs or equipment, and unavailability orinterruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHERRECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAMOR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISEDOF THE POSSIBILITY OF SUCH DAMAGES.


7. GENERAL

If any provision of this Agreement is invalid or unenforceable underapplicable law, it shall not affect the validity or enforceability of theremainder of the terms of this Agreement, and without further action by theparties hereto, such provision shall be reformed to the minimum extentnecessary to make such provision valid and enforceable.

If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excludingcombinations of the Program with other software or hardware) infringes suchRecipient's patent(s), then such Recipient's rights granted under Section 2(b)shall terminate as of the date such litigation is filed.

All Recipient's rights under this Agreement shall terminate if it fails to complywith any of the material terms or conditions of this Agreement and does notcure such failure in a reasonable period of time after becoming aware of suchnoncompliance. If all Recipient's rights under this Agreement terminate,Recipient agrees to cease use and distribution of the Program as soon asreasonably practicable. However, Recipient's obligations under thisAgreement and any licenses granted by Recipient relating to the Programshall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but inorder to avoid inconsistency the Agreement is copyrighted and may only bemodified in the following manner. The Agreement Steward reserves the rightto publish new versions (including revisions) of this Agreement from time totime. No one other than the Agreement Steward has the right to modify thisAgreement. The Eclipse Foundation is the initial Agreement Steward. TheEclipse Foundation may assign the responsibility to serve as the AgreementSteward to a suitable separate entity. Each new version of the Agreement willbe given a distinguishing version number. The Program (includingContributions) may always be distributed subject to the version of theAgreement under which it was received. In addition, after a new version ofthe Agreement is published, Contributor may elect to distribute the Program(including its Contributions) under the new version. Except as expresslystated in Sections 2(a) and 2(b) above, Recipient receives no rights orlicenses to the intellectual property of any Contributor under this Agreement,whether expressly, by implication, estoppel or otherwise. All rights in theProgram not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and theintellectual property laws of the United States of America. No party to thisAgreement will bring a legal action under this Agreement more than one yearafter the cause of action arose. Each party waives its rights to a jury trial inany resulting litigation.


IndexA

accessingVMDK 100VMDK from Linux guest OS with LVM 103VMDK from Linux guest OS without LVM 102VMDK from Windows guest OS 101

alertsoperations 147display 147

All clusters on Hitachi NAS 23All VMs on Hitachi Storage

Summary tab 43All VMs on HNAS 24, 135Apache 2.0 license 176application-consistent backup

install 91architecture diagram 14auto-deploy NFS datastores 139Axis2 license 172

Bbackup

CLI 157backup and recovery

no VM available 122service 119strategies 120VM accidently deleted 121VM has issues 121

BackupsSummary tab 50

best practicesCompliance Dashboard 124NFS 123validate 124, 125

binaries location 68block 17

about mounting VMDKs 100configuration

requirements 78dedicated user account 79ESXi host 17host group 137

restrictionvisibility 17

storage 17edit storage resource 80Hitachi Thin Image support 13install

prerequisites 64restriction

Compliance Dashboard 123Fast Clone 127VVol datastore 18

block storage and ESXi configuration 17

Ccapability

values 25CCI

configure 162determine presence of command device 163HORCM file example 165install 159RDM support 15requirements 60use as a Windows service 160

CLIbackup 157clone 157for Linux 158group and host operations tool 157install 157

for Windows 158mount 157restore 157

client plugin 22clone

CLI 157cloning

VM 128to alternate location 128using 127vApp 128

collect diagnostic information 145Command Control Interface

install 160

Index 185Hitachi Virtual Infrastructure Integrator Administration Guide

Command Deviceconfigure 162

command line interface 157Compliance Dashboard

benefits 123NFS best practices 124tab 30validate compliance 125VM misalignment 125

configurationwizard 80

configureblock requirements 78CCI 162Command Device 162file requirements 78HNAS for vaulting 117user rights 79

context menus 55crash-consistent backup

avoiding 91creating

group of VMs and vApps 136snapshot backup schedule 97

Custom Groups 135

Ddatastore

clustercharacteristics 24restrictions 24

simultaneous deployment 140datastore benefits 17datastore cluster

about 38unsupported datastores 24

datastoresblock 17block restriction 18file 17VVol 18VVol snapshot considerations 108

DatastoresSummary tab 35

datastores on nodesview 133

deletingall orphan snapshot backups 109groups

VMs and vApps 137snapshot backups 108

demonstration license 86deploy

datastores 140options 65

determining presence of CCI LDEV 163diagnostic information

download 145

directly accessingVMDK 100

disable snapshot backup schedule 107display

attached storage 85alerts 147attached file systems 85CLI command 157cluster nodes 133datastores on nodes 133event information 144event log 146event log details 146HNAS clusters 133log viewer 144schedules 107shared storage

datastores 134shared file systems 134

snapshot backup details 91system ID 86vault details 118

distributed installation use of port 10443 60documentation 9

EEclipse Public License, Version 1.0 180editing

block storage resource 80file storage resource 80group of VMs and vApps 137snapshot backup schedule 107

enhanced data protectionabout 116

entityabout entities 22All VMs on Hitachi Storage 23Custom Groups of VMs and vApps 24datastore cluster 24hierarchy 28host 23schedules 26search 23

ESXi Clusterssummary tab 31

event logdisplay 146display details 146

export logs 145

FFast Clone 127file

configurationrequirements 78

installprerequisites 64

186 IndexHitachi Virtual Infrastructure Integrator Administration Guide

File SystemsSummary tab 40

findingfile location 68

firewallinstall consideration 67requirements 61

GGetting Started tab 27, 29Google Charts license 175groups 131

Custom Groups 135Hitachi NAS clusters vApps 23System Groups 134VMs and vApps 24

creating 136deleting 137editing 137

GroupsSummary tab 44, 132

Groups of VMs and vAppsSystem 25

GUI 27

Hhardware

requirements 58Hitachi Storage Services

user interface 27Hitachi Virtual Infrastructure Integrator

client 22demonstration license 86user interface 27

HNASconfigure for vaulting 117

HNAS ClustersSummary tab 42

HORCMmultiple HORCM files 163use as a Windows service 160

HORCM configuration file example 165host

ESXi host 23Host group

block 137Hosts

Summary tab 33

Iinformation tables

moving 55resizing 55scrolling 55sorting 55

initial configuration 80install

CCI 160CLI 157

for Linux 158for Windows 158

Command Control Interface 159license 87Linux WCP 73prerequisites 64Virtual Infrastructure Integrator serversoftware 68Virtual Infrastructure Integrator software 63

install locationVirtual Infrastructure Integrator Web clientservice plugin 67

inventory list 28

JJetty Server license 175

Llicense

Apache 2.0 176Axis2 172demonstration 86Eclipse Public License, Version 1.0 180expiration 87Google Charts 175install 87Jetty Server 175open source 171OpenSSL 172requirements 61third-party 171Winsw 175

locationconfiguration files 68log files 68server binaries 68

logfile location 68alerts 147events 146level setting 144log viewer 144managing 143requirements 61

Mmanaging logs 143minimum user rights for vCenter 79misaligned VM 123mount

about block 100


about file 100CLI 157VMDK 100

NNAS clusters 42navigation pane 27navigation tree 28NFS

best practices enablement 123validate best practices 125

NFS datastoresauto-deploy simultaneously 139

NFS file datastores 17node information 29, 30, 50nodes on clusters

view 133

Oon-demand snapshot backups 92Open source licenses 171OpenSSL license 172orphan snapshot backups 89

deleting 109

Ppermissions 79port

port 10443 use 60port 8443 use 60port 9000 use 60requirements 60

PowerCLI scripts 167pre- and post-scripts 106prerequisites 60, 64print

report 113protocol endpoint 15

Qquiesce 13, 92

before snapshot backup 91requirements 61

RRDM 15recovery

no VM available 122VM accidently deleted 121VM has issues 121

related Hitachi NAS documentation 9

reportbackup status 109print 113snapshot backup

status reports 109terminology 111types 110view 112

requirements 58CCI 60firewall 61hardware 58license 61log 61operating system 58other 59port 60quiesce 61storage software 59VASA Storage Provider support 59VMware software 59

restoreCLI 157snapshot backup 109snapshot backup after migration 109

restore rights 108retention policies

number of backups 96number of days 96

rights 79running scripts 106

Sschedules

display 107Schedules

Summary tab 53scripts

pre- and post-scripts 106running scripts 106

searchentities 23

server binaries location 68server configuration 80service backup and recovery 119set logging levels 144shared file systems

view 134shared storage

view 134simultaneous deployment 140simultaneous NFS datastore deployment

benefits 139snapshot backup

report types 110Snapshot Backup Now dialog 96snapshot backups 26

avoiding crash-consistent backups 91


cloning to alternate location 128considerations for VVol datastores 108creating on-demand 92creating schedules 97delete all orphans 109deleting 108disable schedule 107display details 91edit schedule 107quiesce considerations 91restore rights 108restoring 109retention policies 96schedules 94Summary tab 50supported types 89unsupported types 89

SPBM 15storage array 15storage container 15storage policy-based management

understanding 20value 20

storage softwarerequirements 59

Summary tabGroups 44, 132

System Groupentity 25using 134

system identification 86system requirements 57

Ttask pane 27terminology 15

report 111third-party licenses 171toolbar 27tooltips 55troubleshooting 149

configuration 151installation 150operations 152

Uuninstall Virtual Infrastructure Integrator 72unmount

VMDK snapshot 101VMDKs 101

unsupported characters 56unsupported datastores in datastore clusters 24upgrade

Virtual Infrastructure Integrator versions 70user rights 79

Vvalidation

best practices 124vApp 16, 26

cloning 128discovery 26

vAppsSummary tab 51

VASA 15vault

view details 118vaulting

about 116configure HNAS 117

vCenter Server 17vClusters 23view

cluster nodes 133datastores on nodes 133HNAS clusters 133report 112shared storage

datastores 134shared file systems 134

vault detail 118virtual applications 16virtual clusters 23virtual hard disk 26Virtual Infrastructure Integrator

architecture 14environment 21install on vCenter servers 68multiple HORCM files 163restriction 89server 22uninstall 72upgrade 70VMs on virtualized or external storage 89

Virtual Infrastructure Integrator entityview vault details 118

Virtual Infrastructure Integrator Web clientservice plugin

install location 67virtual machines 25Virtual Machines

Summary tab 46virtual volumes

understanding 19value 19

VM 25cloning 128discovery 26misalignment

identify 125resolve 125

misalignment correction 123VMDK 15

about block mounting 100about unmounting 101access from Linux with LVM 103


access from Linux without LVM 102access from Windows 101directly accessing 100understand single-click access 99unmount snapshot 101

VMwaredocumentation 9requirements 59terms and concepts 15VMware Tools relevance for quiescing 91

vSphere 15client 22terminology 15understanding 14

VVol 15VVol datastore 15, 18VVol datastore snapshot considerations 108

WWCP Linux installation 74Winsw license 175


Hitachi Virtual Infrastructure Integrator Administration 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-92HNAS003-09

http://www.hds.com

MAILTO:[email protected]

