Hitachi Virtual Infrastructure Integrator Administration Guide

Transcription

1 Hitachi Virtual Infrastructure Integrator Administration Guide Release 3.1 MK-92HNAS003-09

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

3 Contents About this document...9 Accessing product documentation... 9 Related VMware documentation... 9 Related Hitachi NAS documentation...9 Getting help...11 Comments About Hitachi Virtual Infrastructure Integrator software Hitachi Virtual Infrastructure Integrator architecture Understanding the vsphere environment VMware terms and concepts...15 Virtual applications vcenter Server NFS file storage datastores...17 Block storage datastores Block storage and ESXi host configuration VVol datastores About Virtual Volumes About Storage Policy-Based Management...20 Understanding the Hitachi Virtual Infrastructure Integrator environment Hitachi Virtual Infrastructure Integrator server software Hitachi Virtual Infrastructure Integrator Web client plugin...22 About Virtual Infrastructure Integrator entities Searching for entities Hosts...23 ESXi Clusters Hitachi NAS Clusters All VMs on Hitachi Storage...23 Datastores Datastore Clusters Custom Groups of VMs and vapps...24 System Groups of VMs and vapps Virtual Machines Virtual Machine discovery...26 Snapshot backups

4 Schedules vapps File Systems...27 About the Hitachi Virtual Infrastructure Integrator user interface About entity hierarchy...28 About the Getting Started tab...29 About the Compliance Dashboard tab...30 About ESXi Clusters About Hosts About Datastores...35 About Datastore Clusters...38 About File Systems About HNAS Clusters...42 About All VMs on Hitachi Storage About Groups About Virtual Machines...46 About Backups About vapps...51 About Schedules...53 About information tables About tooltips...55 About context menus...55 Unsupported characters System requirements...57 Hardware requirements Operating system requirements...58 Storage software requirements...59 Other software requirements VMware requirements...59 Command Control Interface (CCI) requirements Port requirements Log requirements...61 License requirements...61 Quiescing requirements Firewall requirements Installing Virtual Infrastructure Integrator software Install prerequisites...64 Install components...65 Deployment options Install locations...67 Finding server install software and log files Installing Virtual Infrastructure Integrator server software...68 Installing Virtual Infrastructure Integrator Web client service plugin to vcenter Server Upgrading Virtual Infrastructure Integrator software...70 Uninstalling Virtual Infrastructure Integrator

5 4 Installing Virtual Infrastructure Integrator Web Client Plugin in vcsa.. 73 Installing Web Client Plugin for Linux Configuring Virtual Infrastructure Integrator software Configuration prerequisites Minimum user rights for using vcenter...79 Using vsphere Web Client to configure Virtual Infrastructure Integrator software...80 Displaying attached storage and file systems...85 Managing Virtual Infrastructure Integrator license keys...86 Managing the demonstration license Displaying the system ID...86 Installing license keys Expiring license keys Using snapshot backup and restore for VMs Displaying snapshot backup details...91 Understanding quiescing before backups Creating on-demand snapshot backups...92 About snapshot backup schedules Snapshot backup schedule retention policies Creating snapshot backup schedules Single-click direct access to VM hardware snapshots...99 Directly accessing a VMDK snapshot About mounting VMDKs differences About unmounting snapshot VMDKs Unmounting snapshot VMDKs Accessing snapshot VMDKs for a Windows Guest OS Accessing snapshot VMDKs for a Linux guest OS (without LVM) Accessing snapshot VMDKs for a Linux guest OS (with LVM) 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 VVol datastore snapshot considerations Restoring a snapshot backup Restoring a snapshot backup after VM migration Deleting all orphan snapshot backups Snapshot backup status reports Snapshot backup report types Report terminology Viewing a report Printing a report Using snapshot vaulting for enhanced data protection About vaulting for enhanced data protection Configuring the HNAS server for vaulting About the vault details

6 Viewing vault details Backing up and recovering Virtual Infrastructure Integrator service 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 Compliance dashboard for Hitachi NAS NFS best practices Understanding Hitachi NAS NFS best practices compliance Validating Hitachi NAS NFS best practices Identifying VM misalignment Using Hitachi NAS Fast Clone Cloning VMs and vapps Cloning snapshot backups to alternate locations Using Groups About Groups Viewing storage server clusters, and their nodes and datastores Viewing file system resources Using System Groups Using Custom Groups Creating a group of VMs and vapps Editing a group of VMs and vapps Deleting a group of VMs and vapps About the Host group in block storage configuration Using auto-deploy for NFS datastores Understanding auto-deploy of NFS datastores Auto-deploying NFS datastores to all ESXi hosts Managing logs and collecting diagnostic information Displaying the Log Viewer Setting logging levels Exporting logs Collecting diagnostic information Displaying the Event Log Displaying Event Details Displaying Alerts Troubleshooting Virtual Infrastructure Integrator Installation issues Configuration issues Operations issues

7 A Installing Virtual Infrastructure Integrator Command Line Interface (CLI) Installing Virtual Infrastructure Integrator CLI for Windows Installing Virtual Infrastructure Integrator CLI for Linux B Installing Virtual Infrastructure Integrator Command Control Interface (CCI) 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 C Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLI Fast Clone script sample Restore script sample Snapshot backup script sample D Open source and third-party licensing Axis OpenSSL Jetty Server Google Charts Winsw Apache 2.0 license Eclipse Public License Version Index

8 8

9 About this document This document provides an overview of the Hitachi Virtual Infrastructure Integrator product. The document describes how to install, configure, and troubleshoot the software. It also provides detailed information about how to use the product features. Accessing product documentation Product user documentation is available on Hitachi Data Systems Support Connect: Check this site for the most current documentation, including important updates that may have been made after the release of the product. Related VMware documentation For more information about VMware vsphere, refer to the vsphere 6 guides provided by VMware. VMware documentation is located at: pubs/ Related Hitachi NAS documentation Release Notes provide the most up-to-date information about the system, including new feature summaries, upgrade instructions, and fixed and known defects. Hitachi NAS Administration Guides System Access Guide (MK-92HNAS014) Explains how to log in to the system, provides information about accessing the NAS server/cluster CLI and the SMU CLI, and provides information about the documentation, help, and search capabilities available in the system. Server and Cluster Administration Guide (MK-92HNAS010) Provides information about administering servers, clusters, and server farms. Includes information about licensing, name spaces, upgrading software, monitoring servers and clusters, the backing up and restoring configurations. 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 network interfaces, IP addressing, name and directory services. About this document 9

10 File Services Administration Guide (MK-92HNAS006) Explains about file system formats, and provides information about creating and managing file systems, and enabling and configuring file services (file service protocols). Storage System User Administration Guide (MK-92HNAS012) Explains user management, including the different types of system administrator, their roles, 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 and licenses, 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 using VMware 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 how to 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 storage array and disks. The practices outlined in this document describe how to configure the system to achieve the best results. Brocade VDX 6730 Switch Configuration for use in an HNAS Cluster Configuration Guide (MK-92HNAS046) This document describes how to configure 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) This document details the best practices for configuring and using storage pools, related features, and Hitachi Dynamic Provisioning (HDP). Hitachi NAS 12.1 HDP Best Practices (MK-92HNAS057) This document lists frequently asked questions regarding the use of Hitachi Dynamic Provisioning. Hitachi Multi-tenancy Implementation and Best Practice Guide (MK-92HNAS059) This document details the best practices for configuring and using Multi-Tenancy and related features, and EVS security. 10 About this document

11 Getting help Hitachi Data Systems Support Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document to doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you! About this document 11

12 12 About this document

13 1 About Hitachi Virtual Infrastructure Integrator software By integrating into the VMware vsphere virtual environment, the Virtual Infrastructure Integrator software provides data management services including managed snapshot backups, snapshot restores, and snapshot backup scheduling operations on virtual machines (VMs) and VMware vsphere vapp(s) (vapp(s)) that are hosted exclusively on Hitachi Storage devices. You can apply snapshot backup schedules to specific VMs and vapp(s) by grouping them according to your needs. The Virtual Infrastructure Integrator also enables the creation of VM and vapp clones instantly, even while the VMs and vapp(s) are powered on. The software takes advantage of Hitachi NAS platforms File Clone technology to deliver VM and VMDK hardware-level snapshot backups, which can be instantly created or restored. The same technology is used to create efficient clones and linked-clone VMs. When configured for block storage, Hitachi Thin Image (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 Virtual Infrastructure Integrator CLIs remain at 32-bit to provide compatibility with both 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 13

14 Hitachi Virtual Infrastructure Integrator architecture The Hitachi Virtual Infrastructure Integrator architecture consists of several components working together and coordinating with VMware vsphere. Understanding the vsphere environment The term vsphere is used in two ways: one is as a collective name for the VMware-based virtual environment, which includes the VMware vsphere software, VMware vcenter Server software, VMware ESXi clusters and hosts managed by the vcenter Server, and the virtual machines (VMs) and VMware vsphere vapp(s) hosted on those ESXi clusters. The second use of the vsphere term is as a product--vsphere is the name of the GUI for the vcenter 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 for more details. 14 About Hitachi Virtual Infrastructure Integrator software

15 A familiarity with the following vsphere subjects is necessary for a better understanding 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 the physical resource of the underlying ESXi server. Each server can be implemented on a standalone physical machine, or on a group of physical machines working as a cluster with features such as high availability, load balancing, and so forth. These servers host VMs and vapps. Virtual Infrastructure Integrator works with standalone or clustered ESXi servers hosting VMs and vapps. VMware terms and concepts This section briefly describes key terms and VMware environment objects that are relevant to the Storage Provider for file storage. The following table describes key terms and objects: Note: See the VMware documentation at pubs/ for more details. Term or acronym Protocol endpoint Definition PE. An ESXi host uses a PE as a logical I/O proxy to communicate with virtual volumes (VVols) and the virtual machine disks (VMDKs) that the VVols contain. The PE must be accessible on the physical fabric and is used as the data path by the ESXi host for direct access to the VVols. The attached storage manages all other aspects of VVols. The Storage Provider for file storage automatically creates the PEs; no user action is required. For a NAS file system, a PE is a fully-qualified NFS export comprised of a host name (or IP address) and an export name. For example: :/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 disk access to the physical device. The file gives you some of the advantages of direct access to a physical device, while still having some of the advantages of 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 are supported at this time. About Hitachi Virtual Infrastructure Integrator software 15

16 Term or acronym SPBM Storage array Storage container Definition Storage Policy-Based Management leverages the new VVol-based storage. Storage provisioning uses SPBM to match storage array capabilities to established VMDK profiles. See About Storage Policy-Based Management on page 20 for more details. 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. A logical grouping of virtual volumes. New virtual volumes (VVols, or their derivatives) are created inside a storage container. Consider a storage container a pool of raw storage capacity or an aggregation of storage capabilities 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 VMDK VMFS vsphere VVol VVol datastore vsphere APIs for Storage Awareness. These APIs make possible the integration between the vsphere, vcenter, and Hitachi NAS software, and the backend storage. Using VASA, the storage array and its storage containers are presented to VMs for consumption. Virtual Machine Disk. With the transformation of SAN and NAS storage entities into VM-centric devices, a VMDK becomes the native representation of the VM at the array level. 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. 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 VMwarebased virtual environment, which includes the VMware vsphere software, VMware vcenter Server software, VMware ESXi clusters and hosts managed by the vcenter Server, and the virtual machines (VMs) and vapps hosted on those ESXi clusters. Virtual Volume. The VMware Virtual Volume (VVol) feature defines a new virtual disk container (Virtual Volume) that is independent of the underlying physical storage representation, allowing for finer control. In other terms, with Virtual Volumes, the virtual disk becomes the primary unit of data management at the storage level. See About Virtual Volumes on page 19 A VVol datastore or virtual datastore represents a storage container to the vcenter Server software. The VVol datastore defines capacity boundaries and access logic, and exposes a set of data services that are accessible to the VMs provisioned in the pool. Virtual datastores are purely logical constructs. Virtual applications Virtual applications (vapps) are logical entities comprising one or more VMs, which uses the Open Virtualization Format standard to specify and 16 About Hitachi Virtual Infrastructure Integrator software

17 vcenter Server encapsulate all components of a multi-tier application, as well as the operational policies and service levels associated with it. A vapp can consist of any applications running on any OS. It provides a mechanism to move the applications across different VMware clusters without affecting their service levels. The vcenter Server provides central visibility and administration for vsphere hosts, ESXi Clusters, and VMs. Using the vsphere Web Client, you can connect to vcenter and perform tasks such as allocating VM resources, configuring vclusters, and managing datastores. The Virtual Infrastructure Integrator software interacts directly with vcenter when performing snapshot backups and File Clone operations. NFS file storage datastores In NFS file datastores, ESXi clusters access a designated NFS volume located on 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 VMFS datastores mounted on SCSI-based or SAN storage systems. NFS file-level datastores are typically easier to setup and manage in ESXi servers because they do not require the logical configuration details that storage network technologies such as iscsi and FC need. The tradeoff between NFS file stores and block storage is the latter is considered more flexible, efficient, and reliable, at the expense of being somewhat more complicated to configure. Important: The Virtual Infrastructure Integrator software only manages VMs that use Hitachi Storage Services. Block storage datastores The Virtual Infrastructure Integrator supports both file and block datastores. In some applications, block storage is often more efficient and flexible than file-based storage. File storage has the benefit of being simpler to implement. Block storage and ESXi host configuration While 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 hexadecimal pairs. For block storage-based datastores to be visible in the Virtual Infrastructure Integrator inventory, the corresponding ESXi host must be configured with the HBA WWN number. One way you can see this information is in the Storage Adapters hardware area, on the Configuration tab within the vsphere Client application. About Hitachi Virtual Infrastructure Integrator software 17

18 Therefore, after adding the ESXi host HBA WWN number during configuration within 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 configured in the 4B-G00 (00) group. Note: If the ESXi block storage host is not configured with the HBA WWN number, it will not be visible in the Virtual Infrastructure Integrator inventory as an available datastore resource. For more information, refer to the Hitachi Storage Navigator documentation and online help. VVol datastores The VMware VASA 2.0 VVol (virtual volume) datastore option allows you to perform snapshots and restores at the VM-level. VVol datastores simplify storage operations and delivery of storage service levels. 18 About Hitachi Virtual Infrastructure Integrator software

19 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 Virtual Infrastructure Integrator, select the VVol datastore option for your storage type. See System requirements on page 57 for details. About Virtual Volumes The VMware Virtual Volumes (VVols) feature is based on a new integration and management framework between the vsphere product software and a storage system (storage array). The VVols technology virtualizes SAN and NAS devices by abstracting physical hardware resources into logical pools of capacity (called virtual or VVol datastores). These pools can be more flexibly consumed and configured to span a portion of one or several storage arrays. VVols implements an out-ofband bidirectional control path through the vsphere APIs for Storage Awareness (VASA) and leverages unmodified standard data transport protocols for the data path, for example NFS, iscsi, and Fibre Channel. On the array side, two new components are added to the storage environment: VASA Storage Provider for integration with the VASA APIs, and Protocol Endpoints (PE), which allow the storage controller to direct I/Os to the correct virtual volumes. On the vsphere product, there are three dependent features: VASA, VVols, and Storage Policy-Based Management (SPBM). To create policies at the vsphere level, a set of published capabilities must first be defined in the storage array. Then, once defined, these capabilities are surfaced up to vsphere using the VASA Provider. The virtual datastore defines capacity boundaries and access logic, and exposes a set of data services that are accessible to the VMs provisioned in the pool. Virtual Datastores are purely logical constructs that can be configured as needed, without disruption or the requirement of a formatted file system. A VVol is defined as a new virtual disk container that is independent of the underlying physical storage representation, thereby allowing for finer control. In other terms, with VVols, the virtual disk becomes the primary unit of data management at the array level. This model turns the Virtual Datastore into a VM-centric pool of capacity. It then becomes possible to execute storage operations with VM granularity and to provision native array-based data services to individual VMs. This capability allows administrators to provide the correct storage service levels to each individual VM. Using the VVols feature can help you: Simplify storage operations About Hitachi Virtual Infrastructure Integrator software 19

20 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 support for 10 million VVols For Hitachi Virtual Storage Platform (VSP) G1000, 64,000 VVols, 1 million snapshots or clones About Storage Policy-Based Management Storage Policy-Based Management (SPBM) can be viewed as efficient operations through automation. To enable efficient storage operations at scale, even when managing thousands of VMs, VVols uses vsphere SPBM. SPBM is the implementation of the policy-driven control plane in the VMware Software 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 by identifying available datastores that meet policy requirements, and, coupled with VVols, SPBM dynamically instantiates the necessary data services. Through policy enforcement, SPBM also automates service level monitoring and compliance throughout the life cycle of the VM. 20 About Hitachi Virtual Infrastructure Integrator software

21 Understanding the Hitachi Virtual Infrastructure Integrator environment The Virtual Infrastructure Integrator product uses a server component and a Web client service plugin component for configuration and managing features. These components can exist on the same or different physical machines. Each component has an installer. If the Virtual Infrastructure Integrator server is installed on the vcenter Server, then the Virtual Infrastructure Integrator Web client service plugin is already installed. If not, then the Virtual Infrastructure Integrator Web client service plugin must be installed on the vcenter Server. About Hitachi Virtual Infrastructure Integrator software 21

22 Hitachi Virtual Infrastructure Integrator server software The Virtual Infrastructure Integrator server software has a single instance that 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 Hitachi Storage 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 plugin The Virtual Infrastructure Integrator Web client plugin installs within vcenter, and serves up the Virtual Infrastructure Integrator user interface. The plugin provides an interface for all storage operations and configurations that are performed by the Virtual Infrastructure Integrator server. About Virtual Infrastructure Integrator entities The following entity types display as nodes in the Virtual Infrastructure Integrator 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 About Hitachi Virtual Infrastructure Integrator software

23 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 entities To search for entities in Virtual Infrastructure Integrator, use the vsphere Web Client filter field. Hosts A VMware ESXi host, called here a Host, is an ESXi server that is configured to provide centralized resource availability to host VMs and vapps. An ESXi host is implemented as a standalone physical machine. ESXi Clusters A VMware ESXi Cluster, called here an ESXi Cluster, is a collection of ESXi servers that are configured to work together as a unit, providing centralized resource availability to host VMs and vapps. An ESXi Cluster may be implemented as a standalone physical machine or as a cluster of physical machines with support for load balancing and high availability features. ESXi Clusters are the core of high availability in VMware virtual infrastructures. The ESXi Clusters enable VMs and vapps to be dynamically migrated between hosts in the event of a hardware or software failure. Hitachi NAS Clusters The Hitachi NAS clusters entity grouping allows you to view the clusters of Hitachi NAS nodes. This capability gives you greater visibility in to the interdependence of VMs to particular Hitachi NAS clusters. All VMs on Hitachi Storage The All VMs on Hitachi Storage entity grouping allows you to view all of the existing VMs that reside on Hitachi storage systems. This capability gives you greater visibility in to the interdependence of VMs to particular Hitachi NAS clusters. Datastores The VMware software perceives a Virtual Infrastructure Integrator datastore entity as a normal datastore, and the nested individual datastores as nodes. About Hitachi Virtual Infrastructure Integrator software 23

24 The Virtual Infrastructure Integrator client GUI lists all datastores that are hosted on Hitachi Storage Services regardless whether the datastore contains VMs. Datastore Clusters The Virtual Infrastructure Integrator datastore clusters entity grouping allows you to view all of the Integrator's datastore clusters in a single place. Just as the VMware software perceives Virtual Infrastructure Integrator datastore entities as normal datastores, the software perceives Virtual Infrastructure Integrator datastore cluster entities as normal datastore clusters. The software also perceives both of their nested individual datastores as nodes. The Hitachi Virtual Infrastructure Integrator client GUI lists all datastore clusters that are hosted on Hitachi Storage Services regardless whether the datastores 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 or interchangeable datastores. While datastore clusters can contain a mixture of datastores with different sizes and I/O capacities, there are other exceptions. Important: The following types of datastores cannot coexist in a datastore cluster: 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 vapps Custom Groups are basically customizable groups, allowing you to edit the group and select which VMs you want contained in the group. This grouping 24 About Hitachi Virtual Infrastructure Integrator software

25 allows you to manually group a set of VMs on the same file system or a set of vapps that are related. Additional pre-defined System Groups are available and are automatically populated by the Virtual Infrastructure Integrator server based on available datastores. These additional groups provide the ability to visualize where VMs are located on Hitachi storage. This type of VM visualization allows you to develop non-conflicting backup schedules to ensure optimum system performance. Using Virtual Infrastructure Integrator, you may create custom groups of VMs and vapps from the All VMs on Hitachi Storage group, and then manage the groups 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 vapps System Groups are pre-defined groups for VMs and vapps that are automatically populated by the Virtual Infrastructure Integrator Server when the inventory is retrieved from the vcenter Server. System Groups provide the ability to visualize where VMs are located on Hitachi storage. This type of VM visualization allows you to develop nonconflicting backup schedules to ensure optimum system performance. If you have VMs hosted on VVol Datastores, these groups contain VMs and are 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 have no snapshot backup class capability assigned. Virtual Machines Virtual machines (VMs) are software representations of physical hardware that run an operating system and provide services to the enterprise through software applications. In the Virtual Infrastructure Integrator software, the Virtual Machines entity is the basic entity on which snapshot backups and Fast Clone operations are performed. Virtual Machine entity-level operations in Virtual Infrastructure Integrator software include: Creating, editing, deleting, enabling, and disabling snapshot backup schedules. Creating on-demand snapshot backups. About Hitachi Virtual Infrastructure Integrator software 25

26 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 servers are not managed by the Virtual Infrastructure Integrator plugin. Therefore, such VMs are not listed in the Virtual Infrastructure Integrator inventory. Virtual Machine discovery The Virtual Infrastructure Integrator software discovers all virtual machines (VMs) and vapps registered with the vcenter Server. However, the Virtual Infrastructure Integrator software only displays and supports VMs and vapps on supported Hitachi storage platforms. The virtual hard disk (VHD) defined for the VM or vapp might not display if one or more VHDs are not based on a NAS Platform. Note: VMs that are on migrated or archived file systems must first be reverse-migrated before you can use the backup or Fast Clone features. Snapshot backups Snapshots are a storage-efficient copy of a VM or vapp for backup. A group or vapp snapshot backup consists of snapshot backups of each VM contained in the group or vapp. All available snapshot backups display as subnodes under the respective VM nodes in the navigation tree. Schedules vapps Snapshot backup is possible on VMs, vapps, and groups of VMs and vapps. On-demand snapshot backups provide an instant snapshot backup of a selected target. Scheduled snapshot backups are generated by the Virtual Infrastructure Integrator software based on the configured schedule. Orphan snapshot backups can exist on Hitachi storage and are associated with deleted VMs. The Schedules entity grouping allows you to view the existing snapshot backup schedules. When you select Schedules, any configured schedule objects are displayed. A vapp is a logical group of VMs working together as an enterprise application. It can include any number of applications running on different VMs without affecting their service levels. A vapp can have sub-vapps running under it. The vapp-level operations include: 26 About Hitachi Virtual Infrastructure Integrator software

27 File Systems Creating, editing, deleting, enabling, and disabling snapshot backup schedules. Creating on-demand snapshot backups. Restoring a vapp to a previous state using an available snapshot backup. Creating a vapp clone using File Clone. The File Systems entity provides a grouping of VMs by shared file systems, which gives you greater visibility in to the interdependence of VMs to shared file systems. This visibility can assist you in the operational placement of VMs. About the Hitachi Virtual Infrastructure Integrator user interface The Virtual Infrastructure Integrator interface displays when you launch the application by clicking the Hitachi Storage Services icon in the vsphere Web Client interface. About Hitachi Virtual Infrastructure Integrator software 27

28 Item Component Description 1 Navigation pane 2 Information 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. 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 hierarchy The Virtual Infrastructure Integrator (Hitachi Storage Services) navigation tree (inventory list) displays all supported entities hierarchically. Entity types Hitachi Storage Services (root node) ESXi Clusters Hosts Datastores Datastore Clusters File Systems Hitachi NAS Clusters All VMs on Hitachi Storage Custom Groups Sub-entities No sub-entities All ESXi clusters All available ESXi hosts All available datastores All available datastore clusters All available file systems where datastores are present All Hitachi NAS clustered nodes attached to ESXi hosts All VMs, vapps, and Schedules on Hitachi storage, per Hitachi NAS node or cluster User defined groups of VMs 28 About Hitachi Virtual Infrastructure Integrator software

29 Entity types System Groups Virtual Machines Backups vapp Schedules Sub-entities Pre-defined groups All Virtual Machines present on Hitachi storage All snapshot backups available for the selected VM All VMs and vapps within the vapp All available snapshot backup schedules About the Getting Started tab The Getting Started tab in the task pane provides an overview of the main features of the Hitachi Virtual Infrastructure Integrator software. The tab also includes a toolbar of buttons for high level options, and also contains the Configure Hitachi Virtual Infrastructure Integrator button. The overview describes the features and the icons used to represent them. It should 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. About Hitachi Virtual Infrastructure Integrator software 29

30 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 tab The Hitachi NAS NFS Best Practices Compliance Dashboard tab in the task pane displays information about the Hitachi Virtual Infrastructure Integrator environment configuration. The dashboard enables Hitachi Storage Services and VMware customers to confirm they have configured their environment optimally for Hitachi Storage Services as a shared storage resource. The Virtual Infrastructure Integrator software can run validation checking and report findings. You can then choose to manually respond by making the recommended configuration changes. The Compliance Dashboard has tabs that provide information for noncompliant entities. The tables are unpopulated when all entities are compliant. 30 About Hitachi Virtual Infrastructure Integrator software

31 Compliance is monitored for the following entities: Note: The Hitachi NAS NFS Best Practices Compliance Dashboard applies to Hitachi 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 Clusters When you select ESXi Clusters any configured ESXi Cluster objects are displayed. About Hitachi Virtual Infrastructure Integrator software 31

32 For ESXi Cluster resources, the Objects tab displays: Item Name Path Hosts Description The name of the ESXi Cluster The path where the cluster is located The number of hosts associated with the cluster When you select a specific ESXi Cluster resource, the Summary tab displays: Item Name of the ESXi resource Path Number of hosts associated with the resource A formatted table listing storage information details (if available), including: Description Name of the resource Path to the resource How many hosts are associate with the resource Storage address Platform Version File systems 32 About Hitachi Virtual Infrastructure Integrator software

33 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 Hosts When you select Hosts, any configured Hosts objects display. For Hosts resources, the Objects tab displays: About Hitachi Virtual Infrastructure Integrator software 33

34 Item Host Name Virtual Machines Description Configured name of the host Number of virtual machines configured on each host When you select a specific Host resource, the Summary tab displays. Item Host Name Virtual Machines Storage Info. A formatted table listing storage information details (if available), including: Description Name of the Host resource Number of virtual machines on the host Storage Address Platform Version File Systems If you select the Related Objects tab, buttons allow you to view: 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 34 About Hitachi Virtual Infrastructure Integrator software

35 Item Description 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 About Datastores When you select Datastores, any configured datastore objects display. For Datastore resources, the Objects tab displays: Item Name Device Free Space Block Size Total Space Description Name of the datastore Device on which the datastore is located Amount of free space available on the device Block size used by the datastore Total configured space on the datastore About Hitachi Virtual Infrastructure Integrator software 35

36 Item File System Name LUN Description Name of the installed file system, or N/A if not applicable Logical unit number When you select a specific Datastore resource, the Summary tab displays. Note: The information shown varies depending on whether the datastore is using 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 Name ESXi Host Name Location Formatted table listing system information details (if available), including: Formatted table listing Scheduled VM backup information (if available), including: Description Name of the datastore resource Name of the ESXi host Location of the datastore File System EVS IP Free Space Block Size VMs Datastores File System Type Scheduled Backups Count at Group Level Last Backup Time Next Backup Time 36 About Hitachi Virtual Infrastructure Integrator software

37 Item Description Scheduled Backups at Item Level For block storage systems, an additional 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 view events associated with the resource listing: Item Start Time Completed Time Status Operation Operation details Description Time when the event began Time when the event ended Status of the event Operation being performed when event occurred Details about the operation being performed 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 Datastore Schedules Name Entity Name Next Backup Time Type Status Last Backup Time Entity Type Description About Hitachi Virtual Infrastructure Integrator software 37

38 About Datastore Clusters When you select Datastore Clusters, any configured datastore cluster objects display. For datastore cluster resources, the Objects tab displays: Item Name Total Space Free Space Type No. of Datastores File System Name Description Name of the datastore cluster Total amount of space available on the device Amount of free space available on the device Type of datastore cluster: NFS (file), VMFS (block), VVol Number of datastores in each datastore cluster Name of the installed file system, or N/A if not applicable When you select a specific Datastore Cluster resource, the Summary tab displays. Note: The information shown varies depending on whether the datastore cluster is using file or block storage. The items displayed are similar for file and block, but block has an additional table. 38 About Hitachi Virtual Infrastructure Integrator software

39 For both file and block storage, the following Summary information displays: Item Name Total Space Used Space Free Space Type No. of Datastores Location If available, a formatted table listing file system information details, including: If available, a formatted table listing Scheduled VM backup information, including: For block storage systems, an additional formatted table listing, including: Description Name of the datastore resource Total space available to the datastore cluster Total space used by the datastore cluster Amount of free space available on the device Storage type Number of datastores in the cluster Location of the datastore File System EVS IP Free Space Block Size VMs Datastores File System Type Scheduled Backups Count at Group Level Last Backup Time Next Backup Time Scheduled Backups at Item Level 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: About Hitachi Virtual Infrastructure Integrator software 39

40 Buttons allow you to view: Buttons Fields 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 Schedules Name Entity Name Next Backup Time Type Status Last Backup Time Entity Type Description About File Systems When you select File Systems, any configured file systems objects are displayed. For file systems resources, the Objects tab displays: 40 About Hitachi Virtual Infrastructure Integrator software

41 Item Name EVS IP Address Virtual Machines Datastores Free Space Block Size File System Type Description Name of the file system EVS IP address(es) associated with the file system Number of virtual machines on the file system Number of datastores on the file system Amount of free space available on the file system Configured block size of the file system 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 associated datastores: Item Name Device Free Space Block Size Total Space File System Name LUN Description Name of the datastore Device on which the datastore is located Amount of free space available on the device Block size used by the datastore Total configured space on the datastore Name of the installed file system, or N/A if not applicable Logical unit number About Hitachi Virtual Infrastructure Integrator software 41

42 About HNAS Clusters When you select HNAS Clusters, any configured HNAS Cluster objects are displayed. For HNAS Cluster resources, the Objects tab displays: Item HNAS Cluster Name Cluster IP Address Clustered Nodes Health Description Name of the HNAS Cluster IP address where the cluster is located Yes or No Number of nodes associated with the cluster Status message indicating the health of the HNAS Cluster When you select a specific HNAS Cluster resource, the Summary tab displays: Item Name Cluster IP Address Nodes Description Name of the HNAS Cluster IP address where the cluster is located Number of nodes associated with the resource 42 About Hitachi Virtual Infrastructure Integrator software

43 If you select the Related Objects tab, buttons allow you to view HNAS Nodes information, including: Item Host Name IP Address Name Status Model Firmware Description Name of the host IP address where the host is located Status of the host Model of the host Version of the firmware About All VMs on Hitachi Storage When you select All VMs on Hitachi Storage any configured objects are displayed. For All VMs on Hitachi Storage resources, the Objects tab displays: Item Name ESXi Host Name Description Description Name of the All VMs on Hitachi Storage resource Name of the ESXi Host Name resource Description of the All VMs on Hitachi Storage resource When you select a specific resource, the Summary tab displays, listing the same Name, ESXI host name, and Description, as well as a formatted table listing scheduled VM backup information, if available, including: About Hitachi Virtual Infrastructure Integrator software 43

44 Item Name ESXi Host Name Description Formatted table listing scheduled VM backup information, if available, including: Description Name of the All VMs on Hitachi Storage resource Name of the ESXi Host Name resource Description of the All VMs on Hitachi Storage resource Scheduled Backups Count at Group Level Last Backup Time Next Backup Time Scheduled Backups at Item Level 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 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 About Groups There are now two types of Groups: System Groups and Custom Groups. 44 About Hitachi Virtual Infrastructure Integrator software

45 When you select System Groups or Custom Groups, any configured Groups objects are displayed. For Groups resources, the Objects tab displays: Item Name Description Description Name of the group Description of the group, if available When you select a specific resource, the Summary tab displays, listing the same Name and Description, as well as a formatted table listing scheduled VM backup information, if available, including: Item Name Description Formatted table listing scheduled VM backup information, if available, including: Description Name of the group Description of the group, if available Scheduled Backups Count at Group Level Last Backup Time Next Backup Time Scheduled Backups at Item Level If you select the Monitor tab for a Groups resource object, you can view events associated with the resource, listing: About Hitachi Virtual Infrastructure Integrator software 45

46 Item Start Time Completed Time Status Operation Operation details Description Time when the event began Time when the event ended Status of the event Operation being performed when event occurred Details about the operation being performed 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 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 About Virtual Machines When you select Virtual Machines, any configured Virtual Machine (VM) objects are displayed. Note: Virtual Machines (VMs) that are hosted on both File and Block servers are not managed by the Virtual Infrastructure Integrator plugin. Therefore, such VMs are not listed in the Virtual Infrastructure Integrator 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 environment and then create a VM that has hard disks from both file and block storage servers. For Virtual Machine resources, the Objects tab displays: 46 About Hitachi Virtual Infrastructure Integrator software

47 Item Name Last Backup Time Age of Last Backup Backups Next Backup Time Schedules GuestOS Datastore Free Space Description Name of the VM Time the last backup occurred How old the back up is in hours and minutes Number of backups Time of next scheduled backup Number of schedules associated with each VM Operating system being hosted on the VM Datastore being used for the VM Amount of free space available on the device When you select a specific Virtual Machine resource, the Summary tab displays. The information shown will vary depending on whether the VM is hosted using file or block storage. The items displayed are similar for file and block, but block has an additional table. For file and block storage, the information shown is: About Hitachi Virtual Infrastructure Integrator software 47

48 Item Name GuestOS VM IP Address VM Computer Name Storage Type Parent Info - If available, a formatted table listing parent information details, including: Backup Info - If available, a formatted table listing backup information, including: Description - If available, a formatted table listing description information, including: Related Objects Info - If available, a formatted table listing related objects information, including: Block Storage Details - For block storage, the Summary information shown also includes a formatted table listing: Description Name of the VM Operating system used for the GuestOS IP Address of the VM Name of the computer where the VM resides Type of file system used on the storage, for example, VMFS ESXi Host Storage Server Last Backup Time Next Backup Time Oldest Backup Time VM Description Backup Count Schedule Count Datastore Group Host Name Serial Number HORCM Instance Microcode Version Host WWN Host WWPN 48 About Hitachi Virtual Infrastructure Integrator software

49 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 can view events associated with the resource, listing: Item Start Time Completed Time Status Operation Operation details Description Time when the event began Time when the event ended Status of the event Operation being performed when event occurred Details about the operation being performed If you select the Related Objects tab, buttons allow you to view: Item Description Backups Backup Name Entity Name Age Creation Timestamp Backup Type Backup ID Description About Hitachi Virtual Infrastructure Integrator software 49

50 Item Description Schedule Name Datastore Schedules Name Entity Name Next Backup Time Type Status Last Backup Time Entity Type Description Datastores Name Device Free Space Block Size Total Space File System Name LUN About Backups When you select the Backups resource, a list of current backups is displayed. The Summary tab in the task pane displays information about the selected backup, as well as any available actions. Note: The sections and fields displayed depend on whether the backup resource is on file or block storage. The items displayed are similar for file and block, but block has an additional table. 50 About Hitachi Virtual Infrastructure Integrator software

51 For file or block backup resources, the Summary tab displays: Item Backup ID Host IP Address Description Age Creation Timestamp Entity Name A formatted table listing all current file storage backups If available, a formatted table listing all current block storage backups Description ID of the backup IP address of the host Description of the backup (for example, "Every hour") Age of the last backup performed Creation timestamp of the last successful snapshot backup Name of the entity Serial number Host LUNID S-VOL LDEVID HTI Pool ID HTI Pool Name HTI Pool Capacity Total HTI Pool Capacity Free About vapps When you select vapps any configured vapp (virtual application) objects are displayed. For vapps resources, the Objects tab displays: About Hitachi Virtual Infrastructure Integrator software 51

52 Item Name Description ESXi Host Virtual Machines Storage Device Description Name of the vapp Description of the vapp, if needed IP Address of ESXi Host Number of virtual machines Number of storage devices When you select a specific vapps resource, the Summary tab displays, showing: Item Name of the vapp Description ESXi host name Virtual Machines Storage Device Description Name of the vapp Description of the vapp, if needed IP Address of ESXi Host Number of virtual machines Number of storage devices If you select the Monitor tab for a vapps resource object, you can view events associated with the resource, listing: Item Start Time Completed Time Status Description Time when the event began Time when the event ended Status of the event 52 About Hitachi Virtual Infrastructure Integrator software

53 Item Operation Operation Details Description Operation being performed when event occurred Details about the operation being performed 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 Datastore vapps Name Description ESXi Host Virtual Machines Storage Device Backups Backup Name Entity Name Age Creation Timestamp Backup Type Backup ID Description Schedule Name Datastore Schedules Name Entity Name Next Backup Time Type Status Last Backup Time Entity Type Description About Schedules When you select Schedules, any configured schedule objects are displayed. For Schedules resources, the Objects tab displays: About Hitachi Virtual Infrastructure Integrator software 53

54 Item Name Entity Name Next Backup Time Type Status Last Backup Time Entity Type Description Description Name of the schedule Name of the entity Time of next scheduled backup Type of schedule, for example, WEEKLY Status of the schedule, for example, Schedule Disabled Time the last backup occurred Type of entity, for example, Dynamic Group Description of the schedule, if needed When you select a specific Schedules resource, the Summary tab displays: Item Name Entity Name Entity Type Description Type Last Backup Time Next Backup Time Description Name of the schedule Name of the entity Type of entity, for example, Dynamic Group Description of the schedule, if needed Type of schedule, for example, WEEKLY Time the last backup occurred Time of next scheduled backup 54 About Hitachi Virtual Infrastructure Integrator software

55 If you select the Monitor tab for a Schedules resource object, you can view events associated with the resource, listing: Item Start Time Completed Time Status Operation Operation Details Description Time when the schedule began Time when the schedule ended Status of the event About information tables The Virtual Infrastructure Integrator application displays relevant information in tables. The columns and information in the tables varies depending on what type of component or resource is being shown. The tables provide the following capabilities: Action Sorting Moving columns Resizing columns Scrolling Description Helps locate specific records. Successively clicking a column heading toggles the data in ascending or descending order. Drag and drop the column headings to the desired location in the table. Resize by selecting and dragging the column header borders. Horizontal and vertical scroll bars display automatically if the information does not fit within the limits of the table. About tooltips When a field does not fit within the limits of the navigation pane, mouse over the field to display a tooltip with the entire contents. About context menus The context menu displays when you right-click a VM in the Navigator Inventory list. The context menu offers quick access to the operations at that node level. About Hitachi Virtual Infrastructure Integrator software 55

56 Unsupported characters The Virtual Infrastructure Integrator and vsphere applications do not support the use of certain characters. Do not use these characters in the names of any 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 # At symbol! Exclamation point / Forward slash \ Back slash : Colon ; Semicolon? Question mark ' Single quote " Double quote < Less than > Greater than Pipe + Plus sign 56 About Hitachi Virtual Infrastructure Integrator software

57 2 System requirements This section describes the requirements for successfully using the Virtual Infrastructure Integrator software product. Note: The Virtual Infrastructure Integrator software is a 64-bit executable. However, the Virtual Infrastructure Integrator CLIs are 32-bit to provide compatibility 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 57

58 Hardware requirements The Virtual Infrastructure Integrator product supports the following hardware. Note: The Virtual Infrastructure Integrator product does not support virtualized or external storage. File storage Hitachi NAS Platform: 3080 and 3090, 4060, 4080, and 4100 Hitachi Virtual Storage Platform VSP Series G (VSP G400, G600, G800) and Series F (F400, F600, F800) fitted with NAS module Block storage N/A 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 requirements The Virtual Infrastructure Integrator product requires the following operating systems. Important: The Virtual Infrastructure Integrator software supports only 64- bit Windows versions. Deployment model Single system setup: Microsoft Windows Single system setup: Linux Distributed setup: Windows Supported OS 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 Not supported 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 requirements

59 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 requirements The Virtual Infrastructure Integrator product requires the following storage software. Item Hitachi File Storage Hitachi VSP G400, G600, G800 with NAS module Supported Hitachi block storage platforms Storage firmware Hitachi NAS Platform OS or later Hitachi NAS OS or later VSP /00 or later HUS-VM /00 or later VSP G /00 or later Hitachi Virtual Storage Platform (VSP G200, VSP G400, VSP G600, VSP G800) (40/60)/00 or later VSP G /00 or later Other software requirements The Virtual Infrastructure Integrator product supports the following Hitachi product software. Item File storage Block storage Hitachi Storage Provider for vcenter (VASA) or later Not supported VMware requirements The Virtual Infrastructure Integrator product requires the following VMware software. See VMware documentation at for details. System requirements 59

60 Item File storage Block storage VMware vcenter and vcenter required components 5.5, , 6.0 VMware vsphere and VMware vsphere Web Client required components 5.5, , 6.0 VMware VVol datastores 6.0 Not supported VMware vcenter Server Appliance 5.5, , 6.0 VMware vcenter Server Appliance VVol datastores 6.0 Not supported Command Control Interface (CCI) requirements The Virtual Infrastructure Integrator product requires the following Hitachi CCI software. Item File storage Block storage Command Control Interface software versions N/A /04 or later CCI for VSP G1500 N/A /04 or later Port requirements The Virtual Infrastructure Integrator product has the following port requirements. Port Description 8443 Port used for the Virtual Infrastructure Integrator server to register the Virtual Infrastructure Plugin with the vcenter Server. The setting is configurable during installation. Typically, port 8443 is the default port for Virtual Infrastructure Integrator Web server communication (alternate) When port 8443 is already in use, use port 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 Server Configuration screen. 60 System requirements

61 Log requirements The Virtual Infrastructure Integrator product has the following log requirements. Collecting diagnostic logs requires 1 GB of space as a minimum. An error displays if you attempt to collect logs when there is insufficient disk space. License requirements The Virtual Infrastructure Integrator product has the following license requirements. In addition to the requisite Virtual Infrastructure Integrator license, the following 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 requirements The Virtual Infrastructure Integrator product has the following quiescing requirements. Important: If you use the VMware VM quiesce option as part of your backup strategy, you must install VMware Tools version or later on each VM. Firewall requirements The Virtual Infrastructure Integrator product has the following firewall requirements. 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 that is inbound on the server where the Virtual Infrastructure Integrator server is installed. See Install locations on page 67 for more details. Virtual Infrastructure Integrator server is hosted on a VM. You must configure the inbound and outbound firewall settings for source and destination and TCP/UDP. The following ports must be opened on the Virtual Infrastructure Integrator server: System requirements 61

62 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 62 System requirements

63 3 Installing Virtual Infrastructure Integrator software This section guides you through the installation process, one phase at a time. The Virtual Infrastructure Integrator installer checks for an existing installation, and then provides the following options: Fresh installation, if no previous installation is detected. Remove the current installation, if the currently installed version and the installer version match. Upgrade, if the installer is a later version than the currently installed version. 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 to vcenter Server Upgrading Virtual Infrastructure Integrator software Uninstalling Virtual Infrastructure Integrator Installing Virtual Infrastructure Integrator software 63

64 Install prerequisites In addition to meeting all of the systems requirements, you must meet certain additional prerequisites when installing the Virtual Infrastructure Integrator product. See the System requirements on page 57 for those details. Note: The functionality and appearance of the Hitachi Virtual Infrastructure Integrator software may vary, depending on whether file storage, block storage, or both have been installed and configured. Specifically, if only file storage has been set up, only those options are available, and similarly for block storage. If both are set up, then options for both file and block storage configuration are available. Prior to installing the Virtual Infrastructure Integrator software you must perform 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 CCI LDEV are assigned. Switch: Add ESXi host and port group in the same zone in the switch (if applicable). CCI software: 64 Installing Virtual Infrastructure Integrator software

65 Important: Follow all steps mentioned for CCI LDEV and HORCM instance. See the Command Control Interface (CCI) requirements on page 60 for requirement details. The Hitachi Open Remote Copy Manager (HORCM) instance must be running. Note: The HORCM instance must not changed once it is configured with the Virtual Infrastructure Integrator plugin. CCI software must be installed on the same system where the Virtual Infrastructure Integrator server is installed. Install components The Virtual Infrastructure Integrator software has two components: Server software Web client service plugin Note: The vsphere Web Client must be installed before the Virtual Infrastructure Integrator server software and the Web client service plugin. There are different installation requirements and components needed depending 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 options You can install the Virtual Infrastructure Integrator Server and the Virtual Infrastructure Integrator Web Client plugin on the same server (single system) or on separate servers (distributed). Each deployment scheme has different prerequisites and system compatibility requirements. In addition, file storage, block storage, or support for both also have differing installation requirements. Consider the following: Installing Virtual Infrastructure Integrator software 65

66 If you do not have sufficient user permissions to perform the installation or upgrade, an error message displays, describing what permissions are needed to continue. If any services need to be stopped, you are prompted for confirmation. If you decline the stop request, the installation or upgrade aborts and any changes that were made are reverted to their original pre-installation or pre-upgrade state. In cases when a system restart is needed, you are prompted to approve the restart. If for any reason the installation or upgrade is aborted or fails, everything is rolled back to its original state, and the installation logs can be used to diagnose and troubleshoot any problems. Single system deployment: Windows Install the Virtual Infrastructure Integrator Server on the same Windows system where vcenter Server and CCI (block only) is installed. For supported Windows versions, see Operating system requirements on page 58. There is no need to separately install the Virtual Infrastructure Integrator Web Client plugin because it is included with the server installation. Note: Confirm the port for Hitachi Storage web server is enabled on the system. This port is typically port See Port requirements on page 60 for more information. Linux: Not supported. Distributed system deployment: Windows The Virtual Infrastructure Integrator Web Client plugin must be installed on the same Windows system where vcenter Server is installed. The Virtual Infrastructure Integrator Server and CCI should be installed together on the same Windows system. Important: Use a dedicated VM for Windows. Other than the Virtual Infrastructure Integrator server and CCI software, do not install any other software related to Hitachi or VMware in this VM. For supported Windows versions, see Operating system requirements on page 58. Enable port 9000 between the server system and the web client plugin system. See Port requirements on page 60 for more information. Linux 66 Installing Virtual Infrastructure Integrator software

67 The Virtual Infrastructure Integrator Web Client plugin must be installed on VMware vcenter Server Appliance where vcenter Server is running. The Virtual Infrastructure Integrator Server cannot be installed on a Linux system. Install the Server only on a Windows system, and install the CCI there as well. Note: Use a dedicated VM for Windows. Other than the Virtual Infrastructure Integrator server and CCI software, no other software related to Hitachi or VMware must be installed in this VM. For supported Windows versions, see Operating system requirements on page 58. Enable port 9000 between the server system and the web client plugin system. Install locations Install 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 same system as the vcenter Server or it can be installed on a separate system in a distributed setup. During installation, the server installer will attempt to register the Virtual Infrastructure Integrator client plug-in with the vcenter Server. Important: If you install Virtual Infrastructure Integrator server component as a distributed setup, where the vcenter Server is on separate server and a firewall is enabled, you must open port 9000 for any IP address that is inbound on the server where the Virtual Infrastructure Integrator server is installed. Enable the port for Hitachi Storage web server on the system. This port is typically port See Port requirements on page 60 for more information. Once port 9000 has been opened, ensure that the system running the vsphere Web Client can communicate with the server where the Virtual Infrastructure Integrator server is installed. Failure to do so results in certain features of the Virtual Infrastructure Integrator Web Client Plugin to fail. Installing Virtual Infrastructure Integrator software 67

68 Important: The HDS_V2I_Server_Installer.exe must be installed on the same server as the vcenter server. If the plugin registration fails for any reason, install the client by running the HDS_V2I_WebClient_Installer.exe. This will re-register the plugin. Finding server install software and log files The Virtual Infrastructure Integrator server software and log files can be found in the following locations. Important: The Virtual Infrastructure Integrator software is a 64-bit Windows application; therefore, the software is installed in the Program Files folder. 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 software Use these steps to install the Virtual Infrastructure Integrator server software. Important: You must first install the Virtual Infrastructure Integrator server software before installing the Virtual Infrastructure Integrator Web client service plugin software. See Install locations on page 67 for details about where Virtual Infrastructure Integrator software can be installed. Following the installation, if the Virtual Infrastructure Integrator server has been installed on the same system where the vcenter is installed, then the Virtual Infrastructure Integrator server installer registers the Virtual Infrastructure Integrator Web client service plugin with the vcenter Server. Note: If this is a non-vcenter Server installation, see Installing Virtual Infrastructure Integrator Web client service plugin to vcenter Server on page 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. 68 Installing Virtual Infrastructure Integrator software

69 4. Click Install. 5. Provide a port number for the Hitachi Storage Services Web Server Port number. The default port is typically 8443, or if 8443 is already in use. See Port requirements on page 60 for details. Important: For vcenter 6.0, you are prompted to enter a password for VMware vcenter Server keystore password. In a single-server deployment, leave the default password as it is, if the 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 Virtual Infrastructure Integrator Web client service plugin with the vcenter software. Important: Deployment methods for the Virtual Infrastructure Integrator Web Client Plugin vary depending on your VMware version and your installation scenario. If your installation prompts you to restart a particular service, do so. Next steps After installing the Virtual Infrastructure Integrator server software, proceed to Configuring Virtual Infrastructure Integrator software on page 77. Installing Virtual Infrastructure Integrator Web client service plugin to vcenter Server Use these steps to install the Virtual Infrastructure Integrator Web client plugin software. Note: The Web client installer uses the credentials of the logged-in Windows user, so make sure the logged-in Windows user has the administrator role permission on vcenter for Web Client plugin registration. See Install locations on page 67 for details about where Virtual Infrastructure Integrator software can be installed. Installing Virtual Infrastructure Integrator software 69

70 Procedure 1. Locate and copy the appropriate Virtual Infrastructure Integrator Web client services plugin installer (HDS_V2I_WebClient_Installer.exe) to the 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 port number that was used during the Virtual Infrastructure Integrator server installation. See Port requirements on page 60 for supported port numbers. Important: For vcenter 6.0, you are prompted to enter a password for VMware vcenter server keystore password, if the keystore password has not been changed. 7. Restart the Webservices if required. Follow the instructions on the installer screens. Important: Deployment methods for the Virtual Infrastructure Integrator Web Client Plugin vary depending on your VMware version and your installation scenario. If your installation prompts you to restart a particular service, do so. Important: This step is required to register the Virtual Infrastructure Integrator Web client services plugin with vcenter. 8. Log in to the vsphere Web Client and confirm that the Hitachi Storage Services plugin displays in the vsphere Web Client. The presence of the plugin indicates that the Virtual Infrastructure Integrator software installed successfully. Next steps After installing the Virtual Infrastructure Integrator server software, proceed to Configuring Virtual Infrastructure Integrator software on page 77. Upgrading Virtual Infrastructure Integrator software You can upgrade the Virtual Infrastructure Integrator software version from 3.0 and later. 70 Installing Virtual Infrastructure Integrator software

71 Before you begin Stop the Virtual Infrastructure Integrator server for the upgrade process. Stopping the server ensures no backups occur during the upgrade. If you have not already done so, you are prompted to stop the server. When performing an upgrade on a distributed setup, upgrade the Virtual Infrastructure 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 diagnostic information prior to the upgrade process and store it on a separate system. See Collecting diagnostic information on page 145 for details about how to collect diagnostic information. Important: When prompted for the port to be used for the Virtual Infrastructure Integrator server to register the Virtual Infrastructure plugin with the vcenter Server, use port number 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 installed version. However, it is not possible to upgrade over an expired demonstration license. If the Virtual Infrastructure Integrator server is running, you are prompted to stop it for the upgrade. If you decline to stop it, the upgrade installation will exit. The installer registers the updated Virtual Infrastructure Integrator Web client plugin with the vcenter Server, if available. You do not have to reconfigure the Virtual Infrastructure Integrator to use the Web client services 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 the upgrade process, and any conversion that results in a change to the environment 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 Copy the HDS_V2I_Server_Installer.exe file to a temporary location on the server where the Virtual Infrastructure Integrator server was previously installed, and then double-click it to launch the installer. The installer automatically identifies the presence of the previous version of the Virtual Infrastructure Integrator software. Installing Virtual Infrastructure Integrator software 71

72 3. Click Next to continue the installation, and follow the upgrade wizard prompts. The upgrade process migrates all snapshot backup data from the earlier Virtual Infrastructure Integrator software version to the Virtual Infrastructure Integrator server directory. Note: If the Virtual Infrastructure Integrator server was installed on the same system as vcenter Server, after the server upgrade completes, an entry for the Virtual Infrastructure Integrator server displays 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 the same server as vcenter Server, follow the instructions in Installing Virtual Infrastructure Integrator Web client service plugin to vcenter Server on page 69 to install the Virtual Infrastructure Integrator Web client services plugin. 4. Import the certificate for Virtual Infrastructure Integrator. See Using vsphere Web Client to configure Virtual Infrastructure Integrator software on page 80 for instructions. Next steps Following an upgrade installation, you should check to make sure the Virtual Infrastructure Integrator software installed and that your configurations were migrated correctly. Uninstalling Virtual Infrastructure Integrator Procedure 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 click Uninstall. 3. Click Yes to confirm. 72 Installing Virtual Infrastructure Integrator software

73 4 Installing Virtual Infrastructure Integrator Web Client Plugin in vcsa For 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 73

74 Installing Web Client Plugin for Linux To install the Web Client Plugin (WCP) for Linux, follow these steps: Procedure 1. Using administrator-level credentials, log in to the VMware vcenter Server Appliance (vcsa) 5.5 or 6.0 VM. 2. Copy the installer file, WCPLinuxInstaller.tar.gz, to the VMware vcenter 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 Run the LinuxInstaller.sh file with the options shown here:./linuxinstaller.sh install <vcenter username> <vcenter password> Important: If the vcenter Server password uses the special characters $, &, or!, then you must insert a backward slash (\) before each of those special characters and enclose the password in single quotes. Without these changes, the password fails. Example: If the password is P@$$w0rd&!, then provide the password 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 same port number that was used during the Virtual Infrastructure Integrator server installation. See Port requirements on page 60 for supported port numbers. 7. Restart the vcenter Server Service and the vsphere Web Client service using 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 vcsa

75 service vsphere-client restart for restarting vsphere Web Client 8. 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: host address>: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 75

76 76 Installing Virtual Infrastructure Integrator Web Client Plugin in vcsa

77 5 Configuring Virtual Infrastructure Integrator software This section guides you through the configuration process, one phase at a time. Configuration prerequisites Minimum user rights for using vcenter Using vsphere Web Client to configure Virtual Infrastructure Integrator software Displaying attached storage and file systems Managing Virtual Infrastructure Integrator license keys Configuring Virtual Infrastructure Integrator software 77

78 Configuration prerequisites You must meet certain additional prerequisites when configuring the Virtual Infrastructure Integrator product. Have minimum user rights assigned to you to perform all activities associated with the software. See Minimum user rights for using vcenter on 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 by the vcenter Server. Note: The IP address or host name refers to the admin services EVS on the NAS Platform, or, for the VSP models with the NAS module, the controller IP address. For block storage: IP addresses or host names, Hitachi Open Remote Copy Manager (HORCM) instance, login credentials for the storage array, 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 the firewall properties. Hitachi Storage Services Web Server Port number is set to Note: The typical port number is 8443; however, if 8443 is already in use, you can use See Port requirements on page 60. For file storage: NAS Platform server Admin EVS or the Controller IP address 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. Then use this account for Virtual Infrastructure Integrator block configuration. Have the HORCM instance running on the Virtual Infrastructure Integrator server VM as a Windows service, and that RAID commands can be issued to the storage array from the VM. HTI: As best practice, limit the HTI threshold to 80 percent. If you anticipate the pool might fill quickly, set the threshold even lower. 78 Configuring Virtual Infrastructure Integrator software

79 Minimum user rights for using vcenter Working with the Virtual Infrastructure Integrator software requires that you have minimum user rights assigned to you to perform all activities associated with the software. For installation, you must use a vcenter Administrator role. Important: As a best practice, clone the administrator role and use the clone for Backup and Restore operations. This role has all the necessary privileges to perform the operations in all environments. If needed, create a new role specifically for the Virtual Infrastructure Integrator software. Navigate to vcenter > Administration > Roles to create the 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 Configuring Virtual Infrastructure Integrator software 79

80 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 Virtual Infrastructure Integrator software Use the following procedure to initially configure the Virtual Infrastructure Integrator software. Launch the configuration wizard later to add servers, or modify 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 Integrator Web client service plugin by clicking the Hitachi Storage Services icon. 2. At the bottom of the Getting Started tab, click Configure Hitachi Virtual Infrastructure Integrator. 3. If you are using vsphere 5.5, perform the following steps: Important: Leave the default password as it is, if the keystore password 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 the Control Panel typically takes three to five minutes. Also, after initial set-up has been completed, subsequent reconfiguration does not require the cacerts or client services restart steps. 80 Configuring Virtual Infrastructure Integrator software

81 c. After the vsphere Web Client Services has restarted, re-login to the vsphere Web Client. 4. Enter the Virtual Infrastructure Integrator server IP address or host name and port number in the first screen of the configuration wizard, and click Next. You may use the default port or another port on which the 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 administration privileges. See Minimum user rights for using vcenter on page 79 for details. Configuring Virtual Infrastructure Integrator software 81

82 6. When the Hitachi Storage details screen displays, if you are not configuring Hitachi NAS storage, skip to the next step. Otherwise, click the 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 icon next to the resource to be edited. d. To delete a resource, click the icon on its line, but use care as a deletion cannot be undone. Note: When deleting resources, use care because a deletion cannot be undone. e. When finished configuring Hitachi NAS Storage, click Next, or if you need to configure block storage, continue to the next step. 82 Configuring Virtual Infrastructure Integrator software

83 7. To configure block storage, click the Hitachi Block Storage tab. a. When the HORCM Instance identifies the Hitachi Online Remote Copy Manager instance to use for block storage configuration, to select an instance, click the drop-down list and select the appropriate one from the list of available instances. This will automatically populate the Serial Number field as well. b. Enter a Username and Password for a user ID with administrative access. 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 pool from the list. Important: It is critical to select the appropriate HTI pool at this stage because the selection cannot be changed after a block storage resource has been added to the Virtual Infrastructure Integrator product. The Virtual Infrastructure Integrator software does not require its own HTI pool. Select an existing pool, but make certain that it is one that will not be deleted. 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 to the resource to be edited. Configuring Virtual Infrastructure Integrator software 83

84 Note: When editing a configured block storage resource, the HTI Pool drop-down list will be grayed-out, meaning it cannot be changed. g. To delete a resource, click the icon on its line, but use care as a deletion 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, click Finish. 84 Configuring Virtual Infrastructure Integrator software

85 The Virtual Infrastructure Integrator inventory list is refreshed and the plugin is ready to use. j. If you need to reconfigure the Virtual Infrastructure Integrator, you can do so from the Getting Started screen by clicking Configure Hitachi Virtual Infrastructure Integrator again. 8. For NAS module: Once configured/accessed via a provided Controller IP Address, the second controller address is automatically detected. Displaying attached storage and file systems You 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 Platform Version File Systems Hitachi storage host name and IP address Hitachi storage platform type Hitachi storage operating system version List of the file systems exported from a specific storage host Configuring Virtual Infrastructure Integrator software 85

86 3. Click the link displayed for the number of file systems to display the details. Item Description Name Type Total Space Free Space Snapshots Hosted Name of the file system used Type of file system format, for example: WFS-1 or WFS-2 Total storage space on the datastore Available free space on the datastore Number of snapshots hosted by the datastore 4. Click x on the upper right corner to close the list of file systems displayed. Managing Virtual Infrastructure Integrator license keys Managing the demonstration license The Virtual Infrastructure Integrator software installs with a 60-day demonstration license key, which enables all Virtual Infrastructure Integrator features 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, the Demo license key type displays along with its expiration date. Displaying the system ID Permanent license keys are issued based on the unique system ID that is generated during the installation. To display the Virtual Infrastructure Integrator system ID: Procedure 1. In the vsphere Web Client, launch the Virtual Infrastructure Integrator Web client service plugin by clicking the Hitachi Storage Services icon. 2. Click the key ( ) icon About License on the Hitachi Storage Services > Getting Started tab. The License Key dialog is displayed with the system ID appearing at the top. 3. Copy and paste the system ID into an , and send it to your sales representative with the customer system order number (located on the packing slip). Also, send the information on the vcenter Server license type installed on your system (foundation or standard). 86 Configuring Virtual Infrastructure Integrator software

87 Installing license keys After you receive a permanent Virtual Infrastructure Integrator license key, use the Virtual Infrastructure Integrator Web Client Plugin to enable it. The Virtual Infrastructure Integrator server software validates and stores the license key. Procedure 1. In the vsphere Web Client, launch the Virtual Infrastructure Integrator Web Client Plugin by clicking the Hitachi Storage Services icon. 2. Click the key ( ) icon About License on the Hitachi Storage Services > 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 keys Before your demonstration license expires, contact customer support for assistance, or log on to the HDS Support Portal: Configuring Virtual Infrastructure Integrator software 87

88 88 Configuring Virtual Infrastructure Integrator software

89 6 Using snapshot backup and restore for VMs You can configure the Virtual Infrastructure Integrator software to capture snapshot 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 backup schedule 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 external storage, the Virtual Infrastructure Integrator product does not support snapshots of VMs stored on these types of storage. Snapshot backup scheduling automates the task of taking snapshot backups at regular intervals. Snapshot backup schedules enable you to select the date, time, retention period, and frequency of backups. Backup schedules are created for individual entities, such as a VM, vapp, or Groups. You may modify backup schedules, and create several different backup schedules for one entity. Displaying snapshot backup details Understanding quiescing before backups Creating on-demand snapshot backups Using snapshot backup and restore for VMs 89

90 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 VMs

91 Displaying snapshot backup details You can view the details for existing snapshot backups in the vsphere GUI. Procedure 1. Under Schedules, select a VM snapshot backup from the navigation tree. 2. In the task pane, review the creation timestamp, age, and description of the 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 storage details, including: Serial Number Host LUNID LDEVID HTI Pool ID HTI Pool Name HTI Pool Capacity Total HTI Pool Capacity Free Understanding quiescing before backups The Virtual Infrastructure Integrator product supports creation of applicationconsistent snapshot backups. To use this feature, select the quiesce option when you use Snapshot Backup Now or Schedule Snapshot Backup operations. 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 or later, and use supported OS versions and patches. Typically, when the quiesce flag is set to true, the VMware APIs create the VM snapshot; that is, an application-consistent snapshot backup. However, the ability to create an application-consistent snapshot backup depends on various factors and sometimes an issue or failure can occur. In that case, the Using snapshot backup and restore for VMs 91

92 APIs instead create a crash-consistent snapshot backup to ensure that at least a backup occurs. The following issues could lead to a crash-consistent snapshot backup being created: 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 in creation of a crash-consistent snapshot backup, instead of the intended application-consistent snapshot backup. For failure details, see the Virtual Infrastructure Integrator server log and events. Creating on-demand snapshot backups Before you begin If you plan to use quiesce, use VMware Tools version 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 to launch 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 Snapshot Backup Now. In the Objects tab, select an entry in the table, and click on the toolbar. 92 Using snapshot backup and restore for VMs

93 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. The quiesce operation pauses operations and flushes buffers to put the Virtual Machine's file system in a 'quiet' state for the backup. Note: VMware Tools or later must be installed for quiesce to be available. (More information is available via VMware support.) Note: In the Snapshot Backup Now display, below the Quiesce Virtual Machine prior to backup checkbox is a link for Pre and Post Processing Using VMware Tools. This link goes to additional Hitachi Data Systems documentation, "Application Consistent Backup with Hitachi Virtual Infrastructure Integrator." Specifically, it includes details on performing application-consistent backups for MySQL and Oracle, which require additional freezing/thawing and quiesce operations to ensure consistent and correct backups. Downloadable scripts and step-by-step instructions for doing this are also available at that site. Additional details on automating Using snapshot backup and restore for VMs 93

94 Virtual Machine backups and recovering 1TB VMs quickly are available as well. 6. Select the Backup Retention Policy expiration date. 7. Click Ok to create the snapshot backup. About snapshot backup schedules Snapshot 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 Using snapshot backup and restore for VMs

95 A snapshot backup schedule applies only to the entity that you selected in the Virtual Infrastructure Integrator navigation tree. If you create multiple snapshot backup schedules on the same entity, only the enabled snapshot backup schedules concurrently apply on that entity, and generate snapshot backups independently from their specified start dates and times and specified recurrence intervals. Specify the start date and time, in hours and minutes when you create a snapshot backup schedule. The first snapshot backup occurs at the specified setting, and all subsequent snapshot backups generate according to the recurrence control settings. Using snapshot backup and restore for VMs 95

96 Table 1 Snapshot backup schedule recurrence settings Type Minute Hourly Daily Weekly Monthly Description Occurs after each specified interval, which ranges from 10 to 1439 minutes. Occurs after each specified interval, which ranges from 1 to 23 hours. Occurs either after each specified interval, which ranges from 1 to 365 days, or on all weekdays. Occurs after each specified interval, which ranges from 1 to 52 weeks on the selected day of the week. Occurs on the specified day of each month, ranging from 1 to 31. If the month does not have the specified day (for example, a setting of 31 in February), the snapshot backup occurs on the last day of the month. Alternatively, you can specify a week day and week of the month (for example, a setting of the last Thursday of every month). Snapshot backup schedule retention policies Using snapshot backup retention policies, you can automatically delete old snapshot backups, which frees storage space. Apply a retention policy while creating an on-demand snapshot backup, or while creating or editing a snapshot backup schedule. Examples of snapshot backup retention policy options: Number of day(s) examples: Set the retention days to 10 while creating an on-demand snapshot backup. The Virtual Infrastructure Integrator software creates a snapshot backup of that VM, retains it for 10 days, and then deletes once it is 10 days old. Take an on-demand snapshot backup with a retention days to 5 and name it K. K is on a VM with 10 preexisting on-demand snapshot backups named in order of creation A through J. The Virtual Infrastructure Integrator software retains snapshot backups with an age less than 5 days old, and deletes the remaining snapshot backups. Set the retention days to 10 while creating a snapshot backup schedule on a vapp. The Virtual Infrastructure Integrator software creates snapshot backups at the specified time intervals from the specified date and time. The system retains each backup under that backup schedule for 10 days, and then deletes it when a backup on the same entity is performed. Change the retention days from 20 to 10 while editing a snapshot backup schedule on a vapp. The Virtual Infrastructure Integrator software continues creating snapshot backups at the specified settings. The system also checks how many earlier snapshot backups under that schedule are available, deletes any that are older than 10 days, and continues 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 96 Using snapshot backup and restore for VMs

97 Integrator software creates a snapshot backup, and checks how many earlier on-demand snapshot backups of that group of VMs and vapps are available. It retains only the 10 most recent backups, and deletes all others. You take an on-demand snapshot backup with a retention number of 5 and name it K. K is on a VM with 10 pre-existing on-demand snapshot backups named in order of creation A through J. The Virtual Infrastructure Integrator software retains G through K, and deletes the remaining backups. Set the retention number to 10 while creating a snapshot backup schedule on a vapp. The Virtual Infrastructure Integrator software creates snapshot backups at the specified time intervals from the specified date and time. It retains only the 10 most recent backups, and deletes all others. Change the retention number from 20 to 10 while editing a snapshot backup schedule on a vapp. The Virtual Infrastructure Integrator software continues creating snapshot backups at the specified settings. The system also checks how many earlier snapshot backups under that schedule are available, retaining only the 10 most recent backups, and deleting all others. Creating snapshot backup schedules Create schedules to automate your snapshot backups. Before you begin If you plan to use quiesce, use VMware Tools version 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 to launch its GUI. 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 the toolbar. Using snapshot backup and restore for VMs 97

98 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 the system, if necessary. The quiesce operation pauses operations and flushes buffers to put the file system in a 'quiet' state for the backup. Note: VMware Tools or later must be installed for quiesce to be available. (More information is available via VMware support.) 6. Fill the Enable checkbox to enable the backup schedule. Note: In the Schedule Snapshot Backup display, below the Enable checkbox is a link for Pre and Post Processing Using 98 Using snapshot backup and restore for VMs

99 VMware Tools. This link goes to additional Hitachi Data Systems documentation, "Application Consistent Backup with Hitachi Virtual Infrastructure Integrator." Specifically, it includes details on performing application-consistent backups for MySQL and Oracle, which require additional freezing/thawing and quiesce operations to ensure consistent and correct backups. Downloadable scripts and step-by-step instructions for doing this are also available at that site. Additional details on automating Virtual Machine backups and recovering 1TB VMs quickly are available as well. 7. Set the frequency at which the system takes snapshot backups using the options 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 snapshots This feature provides an additional single-click method to mount a virtual machine (VM) hardware snapshot directly from HDS storage back to a production VM to allow application owners to perform self-directed data recovery. This method preserves the backup, while still providing a read/write option to access the backup data. Application owners or administrators can then quickly copy data from the newly added disk within the guest OS. When the VM admin configures a backup to be mounted, the Virtual Infrastructure Integrator server gets the request and clones the specified snapshot backup to an alternate location. A folder called /.recovery/ <vm_name> is created on the respective filesystem corresponding to that snapshot backup. For example, if that snapshot backup resides on an HNAS filesystem called FS-01, then the clone of that snapshot backup is stored in the folder at /.recovery/<hnasvm1>. The Virtual Infrastructure Integrator server uses the VMware API to add and mount the respective VMDK or VMDKs to the production VM and reconfigure it. Upon the successful addition of the new VMDK or VMDKs to the respective production VM, the Virtual Infrastructure Integrator server sends back a response to the Virtual Infrastructure Integrator web client. The web client then updates the GUI and reports the final results along with newly added recovery disk details. At that point, you can access the snapshot from a Windows 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 configured virtual disk of a production VM. This action results in the VMware software asking you to allow virtual disks with same UUID. The Virtual Infrastructure Integrator software handles the action with the VMware API Using snapshot backup and restore for VMs 99

100 AnswerVM(). However, when that VM is later powered on, the VMware software requires your manual response, specifically, answer Yes or No whether to allow assignment of virtual disks with same UUID. VMware vsphere Storage vmotion does not support online VMs with multiple virtual disks that have the same UUID. The choices are to remove the snapshot VMDK from the VM when done, prior to using Storage vmotion, or migrate the VMs in powered-off state. Directly accessing a VMDK snapshot You can mount a VM snapshot through the Hitachi Virtual Infrastructure Integrator GUI. This GUI is launched from within the VMware vsphere Web Client. See About mounting VMDKs differences on page 100 for details about using VMDKs 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, you can continue to mount and unmount the backup. Procedure 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch its GUI. 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 select Mount Snapshot Backup VMDKs. 4. In the Recent Tasks pane, you can view the operation progress and results. About mounting VMDKs differences This section describes differences between the methods in which the Virtual Infrastructure Integrator softwares handles VMDKs and the mounting of VMDKs for file and block storage systems. The Virtual Infrastructure Integrator software for file storage can clone the VMDK files in a backup and present those cloned files to a running virtual machine (VM). Then, you can extract erroneously deleted or corrupted files directly from the attached disks without having to revert the entire VM to a previous backup. As part of the mounting of the backup disks to a running VM, a guest operating system (OS), such as Microsoft Windows operating system, modifies the signature on the disks to resolve a conflict with the existing virtual disks. This type of modification changes the backup data, making it unusable. To avoid this issue, for VMDK files hosted on an Hitachi NAS system, the Virtual Infrastructure Integrator software makes a clone of the 100 Using snapshot backup and restore for VMs

101 cloned backup files instead. This way the original backup remains unmodified and these temporary VMDKs may be disposed of after use. The block platform provides a way to make a writable copy of a backup file that is already on a snapshot disk. However, to provide the mount VMDK operation for block, the VMDK files on the backup LUN are presented directly the running host. The only alternative to this method is to use a third party solution, such as Microsoft Shadow Services. About unmounting snapshot VMDKs The Unmount Snapshot Backup VMDKs operation enables you to remove the VMDKs that were previously added to a production VM. You can unmount the VMDKs as part of a single or multiple Mount Snapshot VMDK(s) operation on the VM. The Unmount Snapshot VMDK(s) operation is available on the VM that has the VMDK(s) added to it as part of the earlier Mount Snapshot VMDK(s) operation(s). Using the Unmount Snapshot VMDK(s) operation does not remove existing VMDKs from a VM. The operation only removes any VMDKs added to it as part of an earlier Mount Snapshot VMDK(s) operation. You can use the context menu option provided on the Host and Cluster entity pages to perform the Unmount Snapshot VMDK(s) operation on multiple VMs. Unmounting snapshot VMDKs You 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. OR 1. 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 OS You can access snapshot backups that were added from a guest operating system (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. Using snapshot backup and restore for VMs 101

102 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 Storage Services > Virtual Machines, and double-click that same Windows VM. 3. Select Related Objects, right-click the backup that you just took, and then select Mount Snapshot Backup VMDKs. 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. Note: If the new VMDK are not visible, return to the Virtual Infrastructure Integrator UI and click the Refresh button in the toolbar. 5. In the Windows guest OS, the application owner or admin performs the following 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 the Windows 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 is running the Linux operating system but not using Linux Volume Manager. Procedure 1. To take a Hitachi NAS 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. 102 Using snapshot backup and restore for VMs

103 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 Virtual Infrastructure Integrator UI and click the Refresh button in the toolbar. 5. Login as root to the Linux VM and run the following command: # echo "- - -" > /sys/class/scsi_host/host<h>/scan Where "- - -" 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 the virtual disk by issuing the following command: # fdisk lu /dev/sdb Disk /dev/sdb: 42.9 GB, bytes 255 heads, 63 sectors/track, 5221 cylinders, total sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * Linux /dev/sdb e Linux LVM During installations, Red Hat software currently uses Linux logical volume management (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 the following 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 is running 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. Using snapshot backup and restore for VMs 103

104 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. Note: If the new VMDK are not visible, return to the Virtual Infrastructure Integrator UI and click the Refresh button in the toolbar. 5. Login as root to the Linux VM and run the following command: # echo "- - -" > /sys/class/scsi_host/host<h>/scan Where "- - -" 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 the virtual disk by issuing the following command: # fdisk lu /dev/sdb Disk /dev/sdb: 42.9 GB, bytes 255 heads, 63 sectors/track, 5221 cylinders, total sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * Linux /dev/sdb e Linux LVM During installations, Red Hat software currently uses Linux logical volume management (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 the following commands: # mkdir /mnt/bootbk # mount /dev/sdb1 /mnt/bootbk 104 Using snapshot backup and restore for VMs

105 If you are using LVM, the file system fails to directly mount. # mount /dev/sdc2 /v2i mount: unknown filesystem type 'LVM2_member' The failure occurs because the added VMDK has volume groups, physical volumes, 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 your guest. You must change these without damaging the live VG, PV, and LV by using the vgimportclone command. 8. To resolve the previous failure, issue the following command: # vgimportclone -n vg_new /dev/sdb2 WARNING: 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 lvm2 At this point, you still cannot use the logical volumes. When you view the lvdisplay results, you can see that while the VG was renamed from VolGroup00 to vg_new, and new UUIDs were assigned, the LVs are marked 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 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 Using snapshot backup and restore for VMs 105

106 11. Mount the file system by issuing the following commands: # mkdir /mnt/lv00 # mount /dev/vg00clone/logvol00 /mnt/lv To clean-up the file system, perform the following steps: a. Unmount the cloned file system with the command: # umount /mnt/ lv00 b. Remove the clone VG and PV (if you were using LVM) by issuing the following commands: # vgremove vg_new Do 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/sdb2 Labels on physical volume "/dev/sdb2" successfully wiped c. Unmount the snapshot backup VMDKs on the VM using virtual infrastructure integrator or remove the VMDKs using the Edit Settings option in the VM. Running pre- and post-process scripts Before running a specific backup, you can configure pre- and post-process scripts that are triggered by Virtual Infrastructure Integrator operations. This allows you to start and stop services and VMs before and after backup operations. 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 Windows PowerShell scripts, Python scripts,.net programs, and so forth from these files for any specific backup entity. See the "Using Virtual Infrastructure Integrator Command Line Interface with VMware PowerCLI on page 167" section for scripting samples. 106 Using snapshot backup and restore for VMs

107 Displaying snapshot backup schedule details View the details for a particular snapshot schedule. Procedure 1. In the Virtual Infrastructure Integrator navigate to Hitachi Storage Services > Schedules. The Objects tab displays a summary of the currently scheduled backups. 2. To view more details for a particular backup schedule, in the navigation tree at the left, select the backup schedule that you want to view, and select one of the tabs. While all tabs may not always be visible, the available tabs include: Summary Monitor Editing snapshot backup schedules Edit 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 schedules Disabling a backup schedule causes the Last Backup Time value to become blank. The last backup time that was displayed in the Objects tab for that schedule becomes blank (only a dash symbol). You can see this behavior in the HNAS Virtual Infrastructure Integrator GUI when you navigate to Hitachi Storage Services > 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. Using snapshot backup and restore for VMs 107

108 Note: After re-enabling the schedule, only Next Backup Time is displayed; Last backup time remains blank. Deleting snapshot backups Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Backups. 2. Right-click the backup to be deleted, and select Delete Snapshot Backup(s). 3. Click Yes to confirm. Restoring snapshot backups Use the Restore from Snapshot Backup option on a VM to restore it to a previous state using one of the available snapshot backups. Using the vcenter software, including the Restore from Snapshot Backup option, requires that you have the appropriate rights. See Minimum user rights for using vcenter on page 79 for details. A snapshot backup at the group level is a collection of snapshot backups for each folder containing a VM. All available snapshot backups are listed in the Backups tab on the Related Objects tab for the respective VM node selected in the inventory list. The snapshot restore operation also recovers a deleted VM. VVol datastore snapshot considerations When taking snapshots of VVol datastores, there are some considerations to keep in mind. 108 Using snapshot backup and restore for VMs

109 If you need to perform a restore, you must reassign a storage policy after the restore is complete. Restoring a snapshot backup You can use the snapshot restore option on a VM to restore it to a previous state 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 migration After VM migration, the restore snapshot option restores to the original datastore, instead of the migrated datastore. The Virtual Infrastructure Integrator software stores the snapshot backup information, which also contains the respective datastore for the VM. After performing the VMware Storage vmotion (migration) operation on the VM to move it to new datastore, the existing snapshot backups are not updated to contain new datastore information. The reference to the previous datastore causes the VM to be restored back on the previous datastore. This limitation is due to NAS Platform server software behavior. Deleting all orphan snapshot backups This procedure deletes all orphan snapshot backups on all hosts and ESXi Clusters. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Hosts or ESXi Clusters 2. Right-click a host node or ESXi Cluster, and select Delete Orphan Snapshots. 3. Click OK to confirm. Snapshot backup status reports These pre-defined reports allow you to quickly identify the success of daily backup jobs and quickly see any backups that have failed or have issues. Using snapshot backup and restore for VMs 109

110 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 identify which VMs do or do not have snapshots, and help you keep track of and avoid missed VMs as you provision new VMs. Roll-up report values: Color Yellow Green Red Gray Description 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. 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. Identifies scheduled backup failure to complete. 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 types Virtual Infrastructure Integrator provides four types of pre-defined backup job status reports. You can run the reports only for VMs and backups. Note: You cannot add, modify, or delete the predefined reports. Report VM Protection Summary VM Backup Job Status Summary Data Protection Status Report Backup Job Status Summary Description 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. Provides information for all the backup jobs executed in the last 30 days. Provides information about all the jobs executed and classified by VMs in the last 30 days. Provides information about all scheduled jobs for last 30 days or per retention, whichever is earlier. 110 Using snapshot backup and restore for VMs

111 Report Description Note: This report contains a hyperlink. It takes you to a printable form of the report that gives details about an individual job. Use CTRL+P to print. Report terminology The following terminology is used in the different reports and can help you better 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 State Number of Backups Number of Schedules Last Backup Time Next Scheduled Backup The name given to the VM. 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. Current number of backups for the VM. Current number of schedules applied to the VM. The last date and time the VM was backed up. The next schedule date and time for the VM to be backed up. VM Backup Job Status Summary Job ID Job Name Status Backup ID Job Run Time Type Age 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. The name of the schedule or the individual manual backup job. The status of the job: Success or Fail. The backup ID of an individual backup of a VM. This is a single backup ID per backup job per VM. The date and time the job ran. The type of job: Scheduled or On-demand. The age of the backup in days and hours. Using snapshot backup and restore for VMs 111

112 Term Retention Job Info Description The schedule retention period. Information about the success or failure of the backup. Backup Job Status Summary Job ID Status Start Time End Time Backup Valid Till Details Job Report 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. The status of the job: Success or Fail. The start date and time of the job. The end date and time of the job. The date and time to which the backup is valid; blank if not set. 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 ID Job Name VM Name Status Job Type Last Run Time Next Run Time Quiesce Age Retention Job Info 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. The name of the schedule or the individual manual backup job. The name given to the VM. The status of the job: Success or Fail. The type of job: Scheduled or On-demand. The last date and time the VM was backed up. The next schedule date and time for the VM to be backed up. The selected setting for whether to quiesce the VM before performing the back up: Yes or No. The age of the backup in days and hours. The schedule retention period. Information about the success or failure of the backup. Viewing a report You can review a report for up to 30 days. 112 Using snapshot backup and restore for VMs

113 Procedure 1. In the vsphere Web Client, in the navigation tree, navigate to Hitachi Storage 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 report You can print a snapshot backup status report using the print feature of a browser. Note: Only detailed job reports within the Backup job summary report can be printed. Procedure 1. In the vsphere Web Client, in the navigation tree, navigate to Hitachi Storage 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. Using snapshot backup and restore for VMs 113

114 114 Using snapshot backup and restore for VMs

115 7 Using snapshot vaulting for enhanced data protection The Virtual Infrastructure Integrator software provides high availability and enhanced data protection with support for vaulting. Vaulting is also referred to as replication in some systems. Vaulting can protect file systems and the virtual machines (VMs) they contain by creating a copy of them at another location. Similar to replication, vaulting can protect datastores and VM hardware snapshots on Hitachi Storage Services by space efficiently replicating a copy of the snapshots to another Hitachi storage device, residing in the same datacenter 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 115

116 About vaulting for enhanced data protection Consider the following Virtual Infrastructure Integrator software vaulting characteristics: Note: Some new features contained in Virtual Infrastructure Integrator version 3.0 require a newer version of the HNAS OS and NAS Manager software. For the vaulting feature, HNAS OS v or later is required. The vaulting feature requires an underlying replication license on the HNAS system. Vaulting using Object Replication is pre-configured by the storage admin. The vaulting feature supports vault viewing capability to show the frequency at which snapshots are being vaulted. It does not support the capability to configure, modify, or manage the vault directly. Before you can use vaulting, you must have already configured the vaulting or replication policy between the source and target HNAS systems. Selecting specific backup jobs to vault is not supported because some backup jobs are automatically vaulted. For example, any backup contained on a specific file system that has an object replication job associated with it is automatically vaulted. A vault is an HNAS storage server that is being used as an object replication target. The server can be another server in the environment or a remote server in another location. Pre-configure the vault on the target HNAS storage server. The vaulting feature defines an object replication job for a given file system on an HNAS system that is being vaulted to another location. The object replication job displays the information for the file system that contains the VMs. Entire file systems can be vaulted; however, vaulting of specific files is not supported. The GUI displays when a backup is set to be vaulted. The file system that contains 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 similar to 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 protection

117 Configuring the HNAS server for vaulting Before you can use vaulting, you must configure the target HNAS server to accept 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 file system 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 details The available vault information for a Virtual Infrastructure Integrator resource entity displays on the entity's Summary page in the Virtual Infrastructure Integrator 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 the Summary 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 Last Backup Time Number of such backups present Time last backup occurred Using snapshot vaulting for enhanced data protection 117

118 Section Item Description Next Backup Time Scheduled Backups at Item Level Time next backup is to occur 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 details You can view the configuration details for vaults in the Virtual Infrastructure Integrator Web client service plugin GUI. This GUI is launched from within the VMware vsphere GUI. Before you begin The vault must be pre-configured on the HNAS storage server to which the Virtual Infrastructure Integrator software is referring. Procedure 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch the Virtual Infrastructure Integrator Web client service plugin GUI. 2. In the navigation pane at the left, click the Datastore, Groups, Virtual Machines, Backups, or vapps entity type for which you want to view vault 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 protection

119 8 Backing up and recovering Virtual Infrastructure Integrator service This section describes how you can back up and recover from a Virtual Infrastructure Integrator service failure. Hitachi Data Systems recommends that you configure the Virtual Infrastructure Integrator service to run as a separate VM, instead of running on 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 the Virtual Infrastructure Integrator VM is running is being vaulted (replicated). Generally, you recover the Virtual Infrastructure Integrator VM from a previous 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, you can just restore the config directory if the case arises. Note: The config directory in the VM contains the Virtual Infrastructure Integrator configuration data. This directory also hosts a Backups.xml database 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 119

120 Strategies for VM backup and data protection Follow these strategies to improve your data protection and recovery efforts. When you are file replicating the primary file system(s) to your secondary site, you always have the latest replicated copy in the secondary site. The secondary site would contain the datastores (exports) to which you would connect 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 will also get the Virtual Infrastructure Integrator VM snapshots, plus the primary file system. This means that the vaulted image is a mirror image of that on the primary file system(s). In that case, there is no need to recover from the Virtual Infrastructure Integrator snapshots on a per VM or datastore basis because all of the VMs would derive from that latest copy, including the Virtual Infrastructure Integrator VM. Typically, you vault to a local environment to enable faster recovery if an issue occurred with the primary system and then replicate to a remote environment for disaster recovery purposes. 120 Backing up and recovering Virtual Infrastructure Integrator service

121 Important: The Virtual Infrastructure Integrator Server, and vcenter and ESXi servers must be time synchronized to prevent Backup(s) from being listed with age as "-". Recovery scenario 1 - VM has issues There are a number of options for recovery when the Virtual Infrastructure Integrator VM is experiencing issues. Note: If you try this recovery process and it is unsuccessful, you can recover the 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 Integrator VM). Or, use Fast Clone Snapshot Backup (create a temporary VM from the snapshot 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 deleted If you accidentally delete the Virtual Infrastructure Integrator VM or need to recover the full Virtual Infrastructure Integrator VM, use the latest snapshot backup of the VM. Procedure 1. Use SSH to access the HNAS console and find the Virtual Infrastructure Integrator VM name in the /.jetapi directory. 2. Use the tree-clone-job-submit CLI command to clone the VM snapshot back 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 121

122 a. Re-register the Virtual Infrastructure Integrator VM by browsing to that location for the.vmx file of the Virtual Infrastructure Integrator VM. b. Power on the VM. c. Rerun the configure Virtual Infrastructure Integrator service. Virtual Infrastructure Integrator is now recovered to that point in time snapshot backup. Recovery scenario 3 - No VM backup is available If no Virtual Infrastructure Integrator VM backup is available to be recovered, then the Virtual Infrastructure Integrator softwre cannot recreate the config and 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 those snapshots that are not showing up in Virtual Infrastructure Integrator, a manual workaround exists. Procedure 1. Use SSH to find the Virtual Infrastructure Integrator VM name in the.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 service

123 9 Compliance dashboard for Hitachi NAS NFS best practices When configuring Hitachi storage, follow the Hitachi Data Systems prescribed best practices for using Hitachi NAS NFS with VMware vsphere environments to optimize the storage usage and VM I/O performance. The dashboard also provides a way for you to identify VM misalignment issues. To help ensure that Hitachi NAS best practice guidelines are met, the Hitachi Virtual Infrastructure Integrator software can run validation checking and report findings. You can then choose to manually respond by making the recommended configuration changes. Note: The Hitachi NAS NFS Compliance Dashboard is applicable for file storage 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 123

124 Understanding Hitachi NAS NFS best practices compliance The Hitachi Virtual Infrastructure Integrator software's compliance validation feature helps to assure compliance with Hitachi NAS best practices for using the Virtual Infrastructure Integrator with VMware vsphere environments. The checks validate that the environment is optimally configured as a NAS shared storage resource. After the checks run, the software reports any noncompliance with Hitachi NAS NFS best practices in the summary information of the Hitachi Virtual Infrastructure Integrator GUI and displays the recommended configuration. You can then use that information to fine tune the Hitachi NAS storage and VM provisioning for best possible performance and optimized storage space usage. Note: The Hitachi Virtual Infrastructure Integrator software checks for compliance with the numerous prescribed best practices. However, the validation checks only support checking of VMs that are configured to be protected by the software. See the Hitachi NAS Platform Best Practices Guide for NFS with VMware vsphere for more details about best practices. 124 Compliance dashboard for Hitachi NAS NFS best practices

125 Validating Hitachi NAS NFS best practices Configure your Virtual Infrastructure Integrator software to validate that the Hitachi storage best practices are being assured in your environment. See the Hitachi NAS Platform Best Practices Guide for NFS with VMware vsphere for more details about the best practices. Note: Some new features contained in Virtual Infrastructure Integrator version 3.0 and higher require a newer version of the HNAS OS and NAS Manager software. For the Compliance Dashboard feature, you may see a dash ( - ) for some compliance checkers where information is not yet available due to the use of earlier versions of the HNAS OS and NAS Manager software. Procedure 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch its GUI. 2. In the content pane at the right, select the Compliance Dashboard tab. The Hitachi NAS NFS Best Practices Compliance Dashboard page displays the various ESXi hosts, Hitachi Storage Server Nodes and Clusters, and Datastores from Hitachi Storage Server that are not complying with the Hitachi NAS NFS Best Practices. The Compliance Dashboard provides the CLI output required to apply NFS best practices to the storage cluster. This output can be shared with the storage admin. Additionally, the VM admin can select to have the CLI applied to the storage cluster. 3. View the displayed information and take the best actions that are suitable for your situation and environment. Identifying VM misalignment As a Virtual Infrastructure Integrator administrator, you can check for VM misalignment on Hitachi NAS storage through the Compliance Dashboard and resolve 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 125

126 Any VMs that have Windows 2003, XP, or earlier operating systems are misaligned by default. Misaligned VMs can cause serious performance issues, such as slow performance due to unnecessary I/O operations. Check that the VM alignment feature displays and lists the misaligned VMs and their VMDKs, along with their fully qualified VMDK paths on the filesystem. Procedure 1. In the Virtual Infrastructure Integrator Web Client GUI, select the Compliance Dashboard tab. 2. In the Hitachi NAS NFS Best Practices Compliance Dashboard screen, select the Check VM alignment tab. 3. Click Get Misaligned VMs to identify any misaligned VMs. The Virtual Infrastructure Integrator scans the datastores for any misaligned VMs and lists those found in the Misaligned VM Details section. 4. After you identify the misaligned VMs, use your favorite tool to resolve the misalignment. 126 Compliance dashboard for Hitachi NAS NFS best practices

127 10 Using Hitachi NAS Fast Clone The Hitachi NAS Fast Clone writable clone utility is different from the VMware clone utility. The Fast Clone utility clones a VM or vapp immediately, without over-burdening storage space. Note: Fast Clone is unsupported for block storage. You can use writable clones of VMs and vapps as templates to expedite provisioning. You can also use the Virtual Infrastructure Integrator software to rapidly scale to high numbers of virtual machines for tasks such as performance intensive testing. The Fast Clone utility operates on an existing VM or vapp. By default, the Fast Clone is registered in the group called All VMs on Hitachi Storage in the navigation tree that contains the resource cloned. Using the vsphere Web Client, you can move the VM or vapp clone to another folder, or migrate the clone to another host. Note: The Virtual Infrastructure Integrator software does not support performing a Fast Clone with the WFS-1 file system type. Only current generation WFS-2- based file systems are supported. Cloning VMs and vapps Cloning snapshot backups to alternate locations Using Hitachi NAS Fast Clone 127

128 Cloning VMs and vapps You can clone a VM or vapp. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Virtual Machines 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 ^, *,, \, /, <, or >. See Unsupported characters on page 56 for the complete list of unsupported characters. Result When creating more than one clone, the clone file names are appended with an incremental numeric suffix. Cloning snapshot backups to alternate locations Unlike the Restore from Snapshot option, which restores the backup to the same location from which the backup was created, Fast Clone Snapshot Backup allows you to clone the selected backup to an alternate location on the same file system. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Virtual Machines, and select the VM node. 2. Select the Related Objects tab, and then the Backups button to display the snapshot backups associated with the selected Virtual Machine. 3. Right-click the backup that you want to clone, and select Fast Clone Snapshot Backup. 128 Using Hitachi NAS Fast Clone

129 4. Enter a name for the destination clone, and click Start. The clone operation initiates, and the status panel displays the progress of the operation. Using Hitachi NAS Fast Clone 129

130 130 Using Hitachi NAS Fast Clone

131 11 Using Groups There are now two types of Groups you can use for working with VMs and vapps: 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 131

132 About Groups There are now two types of Groups: System Groups and Custom Groups. When you select System Groups or Custom Groups, any configured Groups objects are displayed. For Groups resources, the Objects tab displays: Item Name Description Description Name of the group Description of the group, if available When you select a specific resource, the Summary tab displays, listing the same Name and Description, as well as a formatted table listing scheduled VM backup information, if available, including: Item Name Description Description Name of the group Description of the group, if available 132 Using Groups

133 Item Formatted table listing scheduled VM backup information, if available, including: Description Scheduled Backups Count at Group Level Last Backup Time Next Backup Time Scheduled Backups at Item Level If you select the Monitor tab for a Groups resource object, you can view events associated with the resource, listing: Item Start Time Completed Time Status Operation Operation details Description Time when the event began Time when the event ended Status of the event Operation being performed when event occurred Details about the operation being performed 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 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 Viewing storage server clusters, and their nodes and datastores You can view the HNAS storage server clusters and their respective server nodes, and the datastores contained on the nodes. Using Groups 133

134 Procedure 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch its GUI. 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 resources You can view the list of datastores that share the same Hitachi storage file systems and the summary information on those file systems. The Hitachi Virtual Infrastructure Integrator interface displays which VMs and datastores are being delivered by which cluster and also provides visibility to interdependence of VMs to shared storage resources (file systems). This information assists in operational placement of VMs and maintenance activities. 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 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch its GUI. 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 for datastores 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 Infrastructure Integrator contain the All VMs on Hitachi Storage group. This group is dynamic and cannot be edited. Using System Groups The Virtual Infrastructure Integrator provides predefined system groups for use. 134 Using Groups

135 You can perform functions within the Virtual Infrastructure Integrator on System 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 on Hitachi storage. This type of VM visualization allows you to develop nonconflicting backup schedules to ensure optimum system performance. If you have VMs hosted on VVol Datastores, these groups contain VMs and are 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 have no snapshot backup class capability assigned. Using Custom Groups Use the Virtual Infrastructure Integrator to create, edit, and delete custom groups of VMs and vapps from the All VMs on Hitachi Storage group. You can perform functions within the Virtual Infrastructure Integrator on defined 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 Using Groups 135

136 Note: All hosts and ESXi Clusters in Virtual Infrastructure Integrator contain the All VMs on Hitachi Storage group. This group is dynamic and cannot be edited. Creating a group of VMs and vapps Following 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 Select VMs for Group list. Click < to remove the selected VMs. It a VM or vapps cannot be selected, it is listed as being unavailable. 5. Click Ok to save the group. 136 Using Groups

137 Editing a group of VMs and vapps You can edit a Custom Group of VMs or vapps. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Groups. 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 or vapps. 5. Click Ok to save the changes. Deleting a group of VMs and vapps You can delete a group of VMs or vapps. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Groups. 2. Right-click the group node, and select Delete Group. 3. Click Yes to confirm. About the Host group in block storage configuration When the Virtual Infrastructure Integrator software is configured for block storage, the system automatically creates a host group named V2I_Only_HostGrp within the same port as the LDEV(s). Important: Do not modify, use, or delete this group. Using Groups 137

138 138 Using Groups

139 12 Using auto-deploy for NFS datastores The Virtual Infrastructure Integrator software provides the ability to deploy new NFS datastores to all ESXi hosts simultaneously. This method differs from the current method of VM administrators connecting to each ESXi host and deploying each host individually. This time saving, efficient feature greatly 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 139

140 Understanding auto-deploy of NFS datastores The Virtual Infrastructure Integrator software supports the simultaneously deployment of NFS datastores. Typically, a storage admin creates an NFS export, 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 datastore and deploy it to all of the ESXi hosts in one click. The previous method required you to connect through the vsphere Web Client 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 deployment operation: 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. That is, excluding the hosts on which the datastore is already mounted. d. Sends the updated list to the Virtual Infrastructure Integrator Web client 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 must already be created in the environment. Procedure 1. In the vsphere Web Client, click the Hitachi Storage Services icon to launch its GUI. 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 datastores

141 Note: If the vsphere Web Client is using the same vcenter Server as configured in Virtual Infrastructure Integrator Web client service plugin, then only the operation progress is displayed on the task pane. Using auto-deploy for NFS datastores 141

142 142 Using auto-deploy for NFS datastores

143 13 Managing logs and collecting diagnostic information Display logs, set logging levels to refine your results, export logs for diagnostics, 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 143

144 Displaying the Log Viewer Procedure 1. Click on the Hitachi Storage Services > Getting Started tab to open the Log Viewer. Event logs are also available as Actions in the Datastores, All VMs on Hitachi Storage, Groups, Virtual Machines, Backups, and Schedules resource information tables, and display event information 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 levels The Virtual Infrastructure Integrator server creates a HDS_V2I.log file to record all activities and operations. See Finding server install software and log files on page 68 for log file locations. 144 Managing logs and collecting diagnostic information

145 Using the Virtual Infrastructure Integrator client, you set the following logging 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 Integrator software 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 logs Export 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 information Use this procedure to collect diagnostic information. See the log information in the section of the Troubleshooting chapter for details 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, including vcenter and the Hitachi Virtual Infrastructure Integrator. Managing logs and collecting diagnostic information 145

146 Note: The collection and compilation process may take some time to complete. 3. To download the compressed (.zip) file with all the logs and other information, 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 attachment for HDS Support assistance. Displaying the Event Log The Event Log displays the operation records that occur on an entity, such as VMs, vapps, or groups. Events include backup, clone, and restore operations. Procedure 1. In the navigation tree, navigate to Hitachi Storage Services > Virtual Machines. 2. Right-click the node, and select View Event Log. Field Description Start Time Completed Time Status Operation Operation Details Specifies the time the task started. Specifies the time the task completed. Indicates the success or failure of the operation. Specifies the task accomplished. 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 > Virtual Machines. 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. 146 Managing logs and collecting diagnostic information

147 Displaying Alerts The Virtual Infrastructure Integrator logs provide alert information to help you identify and resolve a failing backend task, or any critical error that occurs 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 Target Host/Cluster Operation Description Entity name from which the alert is logged. Host or cluster ID. Failed task. Status Condition of the operation. An displays if the operation fails. Date Time Description Date and time of the failure. 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. Managing logs and collecting diagnostic information 147

148 148 Managing logs and collecting diagnostic information

149 14 Troubleshooting Virtual Infrastructure Integrator This document provides information for troubleshooting issues with the Virtual Infrastructure Integrator software. Installation issues Configuration issues Operations issues Troubleshooting Virtual Infrastructure Integrator 149

150 Installation issues This document provides information for troubleshooting installation issues with 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. Virtual Infrastructure Integrator service is unreachable 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. Note: This issue only applies to installations where the vsphere Web Client is installed on a separate server from the vcenter Server. When installing the Virtual Infrastructure Integrator Web Client Plugin or using it for the first time, if for any reason the Virtual Infrastructure IntegratorService is unreachable, you may see an error similar to the following: Error downloading 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 action does not work. Instead, you must restart the vsphere Web Client service. This is required because VMware has changed their retry mechanism 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 Server Appliance 6.0 servers to vcenter Server Appliance 6.0 Update 1 and then access the Virtual Infrastructure Integrator Web Client Plugin. "Unable to connect to the Hitachi Virtual Infrastructure Integrator Server ( ) due to certificate issue. Please check that the Hitachi Storage Services Web Client plug-in SSL Certificate 'hdscacert' is installed properly in the keystore. Also make sure that VMware vsphere Web Client service is restarted after successful installation of 'hdscarcert' SSL certificate(1052)." To re-install the hdscacert, run the following command from the affected vcenter Server Appliance machine: #keytool -import -trustcacerts keystore /usr/java/jrevmware/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 VMware vcenter Server Appliance responds with Error in RegisterPluginWithCredentials. However, the Virtual Infrastructure Integrator software still installs. 150 Troubleshooting Virtual Infrastructure Integrator

151 Issue Possible solution If you receive this error when upgrading the Virtual Infrastructure Integrator Web Client Plugin on a VMware vcenter Server Appliance server, manually reboot that server and reinstall. This error is a known VMware issue. Configuration issues This document provides information for troubleshooting configuration issues with the Virtual Infrastructure Integrator software. Issue Virtual Infrastructure Integrator Web client service plugin not visible Virtual Infrastructure Integrator server not reachable during configuration vcenter Server not authenticated Null exceptions after clicking Finish during Virtual Infrastructure Integrator configuration Block storage configuration not visible Possible solution 1. Confirm the correct installation of the Virtual Infrastructure Integrator Web client plugin. Consult the setup instructions at Installing Virtual Infrastructure Integrator Web client service plugin to vcenter Server on page If using vcenter 5.5, restart the VMware VirtualCenter Management 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. 1. Confirm correct installation of the Virtual Infrastructure Integrator server. Consult the setup instructions at Installing Virtual Infrastructure Integrator server software on page Confirm that the Virtual Infrastructure Integrator server is running. Navigate to the Virtual Infrastructure Integrator server VM > Services. 3. Confirm that port 9000 is not blocked by the firewall on the Virtual Infrastructure Integrator server. Check with the VM administrator about the firewall properties. Confirm the following: 1. Correct IP address for the vcenter Server. 2. Correct credentials for the vcenter account. Take a screen shot and collect the logs for further analysis, then contact customer support. Confirm you have the correct CCI and HORCM settings. Troubleshooting Virtual Infrastructure Integrator 151

152 Issue Possible solution 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 issues This document provides information for troubleshooting operations issues with the Virtual Infrastructure Integrator software. Issue Block backup fails due to permission issue Backup fails due to HTI pool becoming full Possible solution 1. Check the log file error message. It will read similar to the following: Failed to Create SVOL "XX" for LUN id "YY" on block storage 'XYZ123'. Permission was denied to perform the operation.(histor Error 0x E). Error Code = Confirm User Authentication is enabled for CCI LDEV. If an HTI pool becomes 100 percent full, any subsequent write/read request is rejected. The Virtual Infrastructure Integrator software can no longer take additional snapshots, or perform snapshot restore or mount. To clear the pool, delete the snapshots from the target primary volume or increase the HTI pool, so that the pool recovers the free space. Note that deleting some of the snapshots does not increase the free space. As best practice, limit the HTI threshold to 80 percent. If you anticipate the pool might fill quickly, set the threshold even lower. Backup fails due to LUN 1. Check the error message. It will read similar to the following: ID for SVOL 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 because the LUN ID was for an SVOL. The Virtual Infrastructure Integrator software does not support creation of snapshot 152 Troubleshooting Virtual Infrastructure Integrator

153 Issue Possible solution volumes for SVOLs. An SVOL contains the snapshot data of the PVOL. 4. Confirm you are using the PVOL that was assigned to you by the storage administrator. Log collection utility times out If the log collection utility Web page times out, it is normally due to a network connectivity issue. In other words, the log collection utility cannot gather the logs due to its port being blocked. The log collection utility uses port Remove the policy that is blocking the port and retry gathering the logs. If this still fails, collect the logs as described in the following and send them to customer support for analysis. Hitachi folder for the Virtual Infrastructure Integrator server: Copy the entire Hitachi folder located on the Virtual Infrastructure Integrator server VM. The path is C:\Program Files\Hitachi HORCM folder for the Command Control Interface (CCI:) Copy the entire HORCM folder located on Virtual Infrastructure Integrator server VM. If it was installed on C:\, use the following path: C: \HORCM vcenter Server logs: Go to following location on a VM where the vcenter 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 you collect the latest three log files for vpxd. Sort the log files by date and time to find the latest copies. vsphere Web Client logs: Go to following location on a VM where the vsphere Web Client is running depending on the versions being used: 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 three log files for vsphere_client_virgo. Virtual Machine does not appear in Virtual Infrastructure Integrator inventory Virtual Machines (VMs) that are hosted on both File and Block servers are not managed by the Virtual Infrastructure Integrator plugin. Therefore, such VMs are not listed in the Virtual Infrastructure Integrator 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. Troubleshooting Virtual Infrastructure Integrator 153

154 Issue Possible solution 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 storage servers. If a VM has an RDM device configured that is not a CCI device. Certain Virtual Infrastructure Integrator workflows sometimes fail Certain Virtual Infrastructure Integrator workflows that use the ReconfigureVM function of the VMware Storage vmotion software can fail. Workflows that may fail include: restore, mount, unmount, clone, and unmount snapshot VMDKs. The failure displays a message, such as "PBM error occurred during PreMigrateCheckCallback" with the Unmount Snapshot VMDKs operation. This failure occurs when the VMware Profile-Driven Storage service is not running. The vsphere profile-driven storage service must be running for the vcenter Server that is currently configured with Virtual Infrastructure Integrator. Confirm the Profile-Driven Storage service is running. For vcenter Server Appliance: 1. To check the status of the service, issue the following command: service vmware-sps status 2. To start the vmware-sps service, issue the following command: service vmware-sps start 3. 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 for more information. Virtual Infrastructure Integrator plugin extension fails to automatically unregister The Virtual Infrastructure Integrator registration utility can fail to automatically unregister the plugin extension from vcenter Server's Managed Object Browser (MOB) inventory. The issue may occur if the vcenter services are not in running state. You can manually unregister the plugin by accessing the registration utility 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: remove com.hds.hnasv2i From the MOB, follow the instructions in the Resolution section of the VMware Knowledge Base article at: microsites/search.do? language=en_us&cmd=displaykc&externalid= Troubleshooting Virtual Infrastructure Integrator

155 Issue Snapshot Schedule task remains in progress Possible solution When a Virtual Infrastructure Integrator Snapshot Schedule task takes longer to complete than the SOAP API Auth timeout setting, the SOAP API Auth expires. An Auth Error is logged in the Virtual Infrastructure Integrator log. This issue only occurs if the VMware Configuration for SOAP (API) session timeout is less than the time required to complete the Virtual Infrastructure Integrator operation. You can extend the timeout value of the SOAP API session to avoid the issue. You also may need to restart the VMware VirtualCenter Server service after making this change. See the VMware Knowledge Base article at for details about session timeout values. Quiesced snapshot fails due to VMware Tools If you encounter issues quiescing a VM, ensure that you have VMware Tools version or later and all service packs, hot fixes, and updates installed for your Windows Guest OS. VMware has documented quiesce issues with VMware Tools earlier than version See the following VMware Tools Release Notes and Knowledge Base articles for more information: vmware-tools-1009-release-notes.html cmd=displaykc&doctype=kc&externalid= &sliceid=1& doctypeid=dt_kb_1_1&dialogid= &stateid=0%200% cmd=displaykc&doctype=kc&externalid= &sliceid=2&docty peid=dt_kb_1_1&dialogid= &stateid=0%200% After ensuring you have VMware Tools version or later and that all service packs, hot fixes and updates have been applied to the VM O/S (VM163_1), retry the quiesce snapshot operation. If the quiesce snapshot operation continues to fail, contact VMware Support, as this is a known VMware issue, not a Virtual Infrastructure Integrator issue. Virtual Infrastructure Integrator fails to connect after deletion/creation of HORCM device The following message displays: Error accessing configured Hitachi Block Storage: Unable to update Hitachi 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. (HiStor Error 0x001080AB). (HiStor Error 0x00180AB). If this issue occurs, restart the ESXi host. Troubleshooting Virtual Infrastructure Integrator 155

156 156 Troubleshooting Virtual Infrastructure Integrator

157 A Installing Virtual Infrastructure Integrator Command Line Interface (CLI) The Virtual Infrastructure Integrator CLI provides the following Windows and Linux 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 to display 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) 157

158 Installing Virtual Infrastructure Integrator CLI for Windows Installing the Virtual Infrastructure Integrator client automatically installs the Virtual Infrastructure Integrator Command Line Interface (CLI) to:..\program Files\Hitachi\HDS-V2I\Server\WindowsCLI\ If you do not wish to install the client, but need the commands installed on a Windows system: Procedure 1. Locate your Virtual Infrastructure Integrator Installation CD or compressed (.zip) file. 2. From the Virtual Infrastructure Integrator installation directory, copy the..\hds-v2i-cli\windowscli\ directory to your Windows system. Installing Virtual Infrastructure Integrator CLI for Linux Use these steps to install the CLI for Linux. Procedure 1. Locate your Hitachi Virtual Infrastructure Integrator Installation CD or compressed (.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 that references 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 /lib32/libssl.so Create a soft link to libcrypto.so.6 in your current 32-bit lib directory that references your current 32-bit libcrypto shared library file. For example, if your current 32-bit libcrypto file is named libcrypto.so , enter ln -s /lib32/libcrypto.so /lib32/ libcrypto.so.6. Result After the establishing the soft links, you can then run the Virtual Infrastructure Integrator commands for Linux by entering the command at the shell prompt. 158 Installing Virtual Infrastructure Integrator Command Line Interface (CLI)

159 B Installing Virtual Infrastructure Integrator Command Control Interface (CCI) The Hitachi Command Control Interface (CCI) software is used to configure and perform block storage system configuration and data management operations 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 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 only the 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) 159

160 Installing CCI software Use these steps to install the Command Control Interface (CCI) software for the Virtual Infrastructure Integrator product. Before you begin Set the pop-ups blocker on your browser to allow pop-ups from support.hds.com. Important: Be aware that the CCI installation method for Virtual Infrastructure 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 CCI documentation and software for installation, follow these steps: Procedure 1. Using any supported browser, go to the HDS portal site at partner.hds.com/ and log in with your credentials. 2. In the Search Partner Connect field at the top right, type download CCI, and click the search button. 3. Click the PDF name and save the documentation zip file to a location of your choosing. 4. To obtain the product software download, select the Products Downloads checkbox at the right of the screen. A list displays showing the search results with all matching software package names. 5. Click the software name of the download you want, then click Download. 6. A terms and conditions page displays. Once you have read it, click the radio button next to "I have read and accepted the terms..." and click I Agree to continue. 7. Select the location to download the iso zip file. Using CCI and HORCM as a Windows service Using CCI and Hitachi Open Remote Copy (HORCM) as a Windows service allows you to start and stop the HORCM instance without having to access it manually through the CLI. This saves you time when you must restart the Virtual Infrastructure Integrator software. Before you begin Have administrator privileges. 160 Installing Virtual Infrastructure Integrator Command Control Interface (CCI)

161 Command Device LDEV is created and mapped on the Virtual Infrastructure 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 your HORCM instance has a different number, replace the occurrences of 0 with your 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 CCI instance 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 in one 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), add HORCM_EVERYCLI=1 to the script: For INSTANCE# X, change to HORCMINST=X as needed: START: set HORCM_EVERYCLI=1 set HORCMINST=0 set HORCC_LOG=STDERROUT C:\HORCM\etc\horcmstart.exe exit 0 5. Start the CCI instance from the service. 6. Confirm starting and stopping using horcmstart 0 and horcmshutdown 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 Installing Virtual Infrastructure Integrator Command Control Interface (CCI) 161

162 8. Stop CCI as a service with the following command: C:\HORCM\tool\>net stop HORCM0 Configuring Command Devices for the Virtual Infrastructure Integrator Following are example steps for Command Device configuration for the Virtual Infrastructure Integrator. In some cases, it may be necessary to use or substitute values specific to your systems. If you are using multiple HORCM files with a single Virtual Infrastructure Integrator, see Using multiple HORCM files for a single Virtual Infrastructure Integrator on page 163. Procedure 1. Install the CCI software on a Windows VM where the Virtual Infrastructure Integrator will be installed. For information about supported Windows operating system versions, see Operating system requirements on page Map the Command Device as a Remote Device Mapping to the Windows VM. To do this, navigate to the Windows Disk Manager, put the newly added Command Device disk online, and initialize it as MBR. 3. Using any available text editor (such as Notepad), create the HORCM configuration file (for example, horcm0.conf) in the Windows operating system directory (for example, C:\Windows). Any HORCM instance number can be used; the instance number "0" is shown in this and the following example steps. Following is a simple example of a HORCM configuration file: HORCM_CMD #\\.\CMD-<Serial # of Raid System> \\.\CMD For other systems, the serial number value would be replaced by the appropriate serial number. 4. Start the HORCM instance (instance 0 in this example) from the command prompt: C:\HORCM\etc>horcmstart.exe 0 starting HORCM inst 0 HORCM inst 0 starts successfully 5. After the HORCM instance (instance 0 in this example) is running, make sure there are no other Command Devices from the same Hitachi Storage platform and under the same Host group. If there are any present, remove them from the Windows VM. For more information, see Determining presence of another CCI Command Device on page Installing Virtual Infrastructure Integrator Command Control Interface (CCI)

163 Note: If a Command Device needs to be removed, remove the one that is not running the HORCM instance for the Virtual Infrastructure Integrator. Using multiple HORCM files for a single Virtual Infrastructure Integrator When you configure multiple HORCM files for a single Virtual Infrastructure Integrator, 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 Device The following examples demonstrate the commands to be executed to determine 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 Device on one Hitachi Storage server. Example 2: Two Command Devices present from the same Hitachi Storage Server and same Host group The following output shows an invalid configuration. There should be just one CCI LDEV for the same Hitachi Storage server and same Host group in the Windows VM. You would need to remove the CCI LDEV that is not used for Virtual Infrastructure Integrator from this Windows VM. In this case, it is LDEV 18. Installing Virtual Infrastructure Integrator Command Control Interface (CCI) 163

164 Example 3: Two Command Devices are present but belong to different Hitachi Storage servers The following output shows a valid configuration, where there are two Command 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, assume there is one Command Device configured for one storage platform and two Command Devices configured for a second storage platform. In the example output, on the storage server, you would need to remove the CCI LDEV ED, which is not being used for Virtual Infrastructure Integrator, but keep LDEV C5 on that same storage server and LDEV 12 on the storage server. Note: Compare the LDEV number displayed in the CLI output with the CCI LDEV number in the Hitachi Storage server and make sure to remove the correct 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. 164 Installing Virtual Infrastructure Integrator Command Control Interface (CCI)

165 3. Click OK to complete the action. Example HORCM configuration files When you are configure Command Devices for the Virtual Infrastructure Integrator and need to create the HORCM configuration file, follow the supported examples here. Supported: Here are two simple examples of supported HORCM configuration files, horcm0.conf, where the serial number of the associated RAID system is For other systems, the serial number value would be replaced by the appropriate serial number. Configuration 1: HORCM_CMD \\.\PhysicalDrive#<physical drive number of CCI LDEV> Installing Virtual Infrastructure Integrator Command Control Interface (CCI) 165