host powertools for vmware - infinidat.zendesk.com1.1 what is infinidat host powertools for vmware...

LAST UPDATED: 03/04/2020

HOST POWERTOOLS FOR VMWARE USER GUIDE


2

Table of Contents1 Introduction to Host PowerTools for VMware _______________________________51.1 What is INFINIDAT Host PowerTools for VMware ....................................................................... 5

1.2 Locating the INFINIDAT View....................................................................................................... 7

2 Configuring Host PowerTools for VMware __________________________________92.1 Installation prerequisites ............................................................................................................ 9

2.2 Host PowerTools for VMware installation instructions ........................................................... 10

2.3 Upgrading Host PowerTools for VMware.................................................................................. 12

2.4 Uninstalling Host PowerTools for VMware ............................................................................... 17

2.5 Changing the Host PowerTools IP settings .............................................................................. 20

3 Preparing the ESXi hosts _______________________________________________213.1 ESXi hosts and clusters readiness ............................................................................................. 21

3.2 Setting up iSCSI hosts via Host PowerTools for VMware ......................................................... 23

3.3 Registering ESXi hosts and clusters .......................................................................................... 24

3.4 Adding new ESXi hosts to a registered cluster ......................................................................... 26

3.5 Moving ESXi host between clusters........................................................................................... 26

4 Storage managment using Host PowerTools for VMware _____________________274.1 Provisioning storage to vSphere ............................................................................................... 27

4.2 Viewing mapped volumes on Host Powertools for VMware .................................................... 30

4.3 Mapping an existing volume to vSphere................................................................................... 30

4.4 Creating a datastore on an existing volume............................................................................. 31

4.5 Renaming the device name to the volume name .................................................................... 32

4.6 Resizing datastores and volumes ............................................................................................. 33

4.7 Unmap datastores and volumes ............................................................................................... 34

4.8 Reclaiming freed space.............................................................................................................. 35

5 Backing up virtual machines ____________________________________________365.1 How to backup virtual machines .............................................................................................. 36

5.2 Modifying the snapshot name and description........................................................................ 38

5.3 Restoring from a backup ........................................................................................................... 38

5.4 Exposing a VM from snapshot ................................................................................................... 40


3

5.5 Deleting a snapshot ................................................................................................................... 42

5.6 Restoring the VM from the Snapshot Catalog .......................................................................... 43

6 Host PowerTools for VMware appendices _________________________________446.1 Host PowerTools for VMware administrative tasks ................................................................. 44

6.2 Appendix: Viewing volumes and hosts on the InfiniBox GUI ................................................... 45

6.3 Upgrading to Host PowerTools for VMware 5.3 (or later) from a previous version................ 45

7 Active-Active replication with vSphere ____________________________________497.1 Preparing ESXi hosts when using Non-uniform connectivity .................................................. 49

7.2 Settings Optimized/Non-optimized ESXi hosts........................................................................ 50

7.3 Viewing Active-Active volumes and datastores........................................................................ 52

7.4 Snapshots for Active-Active virtual machines .......................................................................... 54

7.5 Other operations on Active-Active datastores ......................................................................... 59


– 4


INTRODUCTION TO HOST POWERTOOLS FOR VMWARE – 5

1 Introduction to Host PowerTools for VMware

1.1 What is INFINIDAT Host PowerTools for VMware

1.1.1 AboutINFINIDAT Host PowerToolsTM for VMware is an application that provides the VMware administrator with provisioning capabilities and with an easing of the process of volumes backup and recovery.

INFINIDAT encourages a close cooperation between the storage administrator and the VMware administrator, as well as other applications administrators. According to this vision, the storage administrator maintains an overall control over the storage environment, and sets policies to be followed by all of the applications. Application administrators are granted with an autonomy to provision storage and to operate within the policies set by the storage administrator. This approach enables InfiniBox to intelligently automate most of the processes, and to monitor the administrator actions so as to prevent mistakes that can lead to downtime.

Combining these advanced management capabilities provided by InfiniBox in tight integration with VMware's newest and most advanced tools enables the storage and VMware administrators to provide a faster, better and more agile service to the business.

INFINIDAT strongly encourages organizations to adopt this policy-driven approach which accelerates business processes, but of course customers may also opt out of it. Working in this approach, Host PowerTools for VMware offers a read-only mode for the VMware administrator, where all changes are carried out by the storage team only.

Host PowerToolsTM is a trademark of INFINIDAT.

Terminology

InfiniBox The INFINIDAT storage system that Host PowerTools connects to.

Host A computer system to which the InfiniBox is attached and accessible for data storage and I/O.

Volume A set of disk blocks presented to an operating environment as a range of consecutively numbered logical blocks with disk-like storage and I/O semantics.

OVF / OVA OVF (Open Virtualization Format) is an industry standard developed by VMware for distribution purposes. It describes, in XML format, metadata related to virtual machine image.

This format is supported, among other platforms, by VMware vCenter 4.0 and above.

The OVA contains an OVF file along with other files needed for the deployment of the virtual machine.



VASA Provider VASA (VMware vSphere® API for Storage Awareness) is a set of APIs that allows storage vendors to provide vSphere with information about specific disk arrays for a tighter integration between storage and the virtual infrastructure.

The shared information includes details on storage virtualization, including health status, configuration, capacity and thin provisioning.

LUN Logical Unit Number. An identifier of the volume.

Pool The pool is a logical space that contains volume, snapshot and clones. The pool allocates physical and virtual storage space for these entities. The pool also determines a policy for automatic extension in case of space depletion.

Role-based access control INFINIDAT restricts system access to users according to roles and operations.

The available roles are system administrator, a read-only user, pool administrator (that is restricted to a given set of pools) and the host_tools (see below).

host_tools This user accesses the InfiniBox using the Host PowerTools.

This user has access to all of the InfiniBox pools.

Supported Platforms

See an up-to-date list on the INFINIDAT Support website.

Note:

• HPTVM is not supported on hosts that have an Active-Active volume mapped as LUN 0.

• HPTVM is compatible with SnapRotator according to the following matrix:

HPTVM 5.2.1 and later

SnapRotator 7.0.1 and later

Guide supported versions

This guide applies to Host PowerTools for VMware 4.x and above.

Last updated

March 4, 2020.

1.1.2 VASA ProviderThe installation of Host PowerTools for VMware also includes a VASA Provider. VASA (vStorage APIs for Storage Awareness) is a set of APIs that improve the way the vSphere vCenter operates on storage arrays. Storage awareness capabilities include RAID and native thin provisioning, all visible to the customer from within the vCenter.

https://infinidat.zendesk.com/hc/en-us/articles/202525152-INFINIDAT-software-compatibility

http://searchexchange.techtarget.com/definition/application-program-interface

http://searchstorage.techtarget.com/definition/array

http://searchstorage.techtarget.com/definition/array

http://searchstorage.techtarget.com/definition/RAID

http://searchstorage.techtarget.com/definition/thin-provisioning



The VASA Provider also provides information about the InfiniBox topology, capabilities and state, including events and alerts.

Once the VASA Provider is installed, you can see it registered in vCenter (under Home > Storage Providers).

1.1.3 Download site for the installation fileHost PowerTools for VMware installation file is provided in an OVA format. The OVA file is available from:

http://repo.infinidat.com/#host-power-tools-for-vmware-ng

1.1.4 Related documentationApplication Repository documentation on the Support site.

1.2 Locating the INFINIDAT View

1.2.1 AboutHost PowerTools for VMware creates a dedicated view (INFINIDAT view) within the vSphere Clients, which is available for the following vSphere objects:

• Clusters

• Hosts

• Datastores

• Folders

In order to locate the INFINIDAT view, see the instruction below.

• To access the view's content, the vCenter user should have proper permissions for the desired vSphere

object along with the following privilege granted: Host -> Storage partition configuration

1.2.2 On vSphere Web Client (Flash) 5.5 - 6.01. In the Navigator (left) pane select the desired vSphere object

• In the example below, a host was selected.

2. Select the Manage tab.

https://repo.infinidat.com/home/main-stable#host-power-tools-for-vmware-ng

https://infinidat.zendesk.com/hc/en-us/articles/203095701-Application-Repository



3. Choose INFINIDAT in the upper bar.

1.2.3 On vSphere Web Client (Flash) or vSphere Client (HTML5) 6.5 and above1. In the Navigator (left) pane select the desired vSphere object.

• In the example below, a cluster was selected.

2. Click the Configure tab.

3. Scroll down to the More category and select INFINIDAT.


CONFIGURING HOST POWERTOOLS FOR VMWARE – 9

2 Configuring Host PowerTools for VMware

2.1 Installation prerequisites

2.1.1 Installation requirements

vCPU 2

Available RAM 4GB

Disk space 10GB

Browser • When using VMware vSphere Client software, Internet

Explorer 10 or newer version must be installed on vSphere

client station.

• No limitations apply to the version of Internet Explorer

installed on the vCenter server itself (unless it serves as a

client station as well).

IP address for the appliance DHCP and manual configuration are supported

2.1.2 List of required ports

Source Target Purpose Port (TCP protocol)

Host PowerTools for VMware Appliance

InfiniBox HTTP Restful API 443

Client (browser) Host PowerTools for VMware Appliance

Network and update management

5480

vSphere client Host PowerTools for VMware Appliance

Webapp-content 443

vSphere client Host PowerTools for VMware Appliance

Plugin information 80

Host PowerTools for VMware cannot be deployed on a Datastore Cluster when Storage DSR is enabled.




vCenter Server SOAP API 80,443


Repo.infinidat.com Downloading software updates

21

vCenter Server Host PowerTools for VMware Appliance

VASA 8443


vCenter Server vCenter Single Sign-On 7444

2.2 Host PowerTools for VMware installation instructions

2.2.1 AboutThe installation of Host PowerTools for VMware allows you to access the InfiniBox from within the vCenter client. The installation comprises two main steps:

1. Configuring the vCenter runtime settings

2. Deploying the OVA template

2.2.2 vCenter Runtime Settings configuration vCenter Runtime Settings should be configured according to VMware best practices.

• The "vCenter Server managed address" should be configured accordingly.

The vCenter Runtime Settings are required for correct operation of Host PowerTools for VMware as a vSphere extension.

2.2.3 Deploying the OVA template1. Download the installation file as explained in Download site for the installation file.

2. Open the vCenter client and select File > Deploy OVF Template from the menu.

3. On the Source pane, browse to the installation file that you downloaded onStep 1 above.Click Next.

4. Review the details on the OVF Template Details pane and click Next.5. Review the Name and Location of Host PowerTools for VMware. Click Next.6. Select a host, or cluster on which the template will be deployed.7. Select between thick and thin provisioning formats, all supported by INFINIDAT.

Following the installation of Host PowerTools for VMware, there is a need to prepare the host / cluster. For instructions see: ESXi hosts and clusters readiness

https://repo.infinidat.com/home/main-stable#host-power-tools-for-vmware-ng



8. Set the networking properties(leave blank if DHCP is used):

a. Default gateway. This is the IP address for the Host PowerTools for VMware appliance.

b. DNS.The IP address of the DNS server.

c. Network1 IP Address.The appliance IP address.

d. Network1 Mask.Network subnet mask.

9. Click Next on the Service Binding screen.

10. Review a summary of the deployment settings and click Finish.The template is deployed.Note that there is a script that runs after the deployment. You can verify that the script has finished by clicking Launch Virtual Machine Console. The screen should look like this:

11. Close the vCenter client and open it again to allow the INFINIDAT plug-in to be loaded.

12. On the either of the following levels: VC, Cluster, ESX, Folder, vm, Datastore:Click the INFINIDAT tab.

Initially, the message onscreen is: "Cluster / datacenter not ready to work with InfiniBox".Run the Prepare command.

2.2.4 When using vCenter Server in Linked ModeHost PowerTools for VMware should be deployed on each of the linked vCenter severs environment.

The Host.Configuration.Storage partition configuration privileges are required to see the tab



2.3 Upgrading Host PowerTools for VMware

2.3.1 AboutHost PowerTools for VMware provides a built-in tool for upgrades.

• The tools leverages VMware's native Update Manager and is accessible using a web browser directly

from Host PowerTools for VMware.

• Number of upgrading methods are available as described below.

Backing up the Host PowerTools for VMware appliance

Prior to the upgrade, it is advised to back up the Host PowerTools for VMware VM.

There is no direct upgrade path from a previous version to version 5.3 (or later versions)• You can migrate your data to version 5.3 from version 5.2.1.

• For more information, see Upgrading to Host PowerTools for VMware 5.3 (or later) from a previous

version



2.3.2 Accessing the upgrade tool viewDetermining Host PowerTools for VMware IP address

1. Open vCenter UI and locate the Host PowerTools for VMware virtual machine.

2. On the Summary tab, the virtual machine IP Address is presented.

3. On a browser, access the following URL:

• https://<HPTVM IP>:5480

• Note: The connection is open for HTTPS only.

• In our example:

• https://172.16.86.23:5480/

• Use the following credentials:

• User: root

• Password: nfinidat1

2.3.3 Upgrading via the internet1. Access the Upgrade Tool, the screen opens:

https://172.16.86.23:5480/



2. Click the Update tab.Your current Host PowerTools version is displayed onscreen.

3. Click Check Updates.Details of the available update are displayed on the screen.

4. Click Install Updates.The available update is installed.

5. If required, reboot Host PowerTools for VMware.

6. Refresh existing vCenter UI views.

The appliance is upgraded.

2.3.4 Manual Upgrade - Providing an upgrade file1. Go to the repository site (the link is available here: Download site for the installation file).

a. Select Host PowerTools for VMware on the navigation tree.

b. Click on Other versions and platforms.

https://repo.infinidat.com/home/main-stable#host-power-tools-for-vmware



c. Select the file that ends with UPDATE_ISO and download it.

2. Mount the UPDATE ֹ_ISO file as a CD/DVD device on the Host PowerTools for VMware VM.

3. Go to the Upgrade Tool view as explained above.

a. Click on Updates, then on Settings tab and select the CD ROM Updates option.

b. Upload the file and click Save.

4. Click the Status tab.Your current Host PowerTools version is displayed onscreen.

5. Click Check Updates.Details of the available update are displayed on the screen.

6. Click Install Updates.The available update is installed.

7. Reboot Host PowerTools for VMware.

The appliance is upgraded.

2.3.5 Using a specified repository for the upgrade files1. Install the INFINIDAT Application Repository.

See: Application Repository for a link to the relevant Application Repository documentation.Populate the Application Repository with the HPT-VM upgrade package.

https://support.infinidat.com/hc/en-us/articles/203095701-Application-Repository



2. Point the Host PowerTools for VMware appliance to fetch the package from the Application Repository.Copy the Repository URL and replace repo.infinidat.com with the new repo address.

2.3.6 Troubleshooting following upgradesIf issues are encountered following an upgrade, it might be required to:

• Log-out and re-login the vCenter UI.

• Clearing the browser cache.

• Restarting the vSphere web client UI:

• Flash in case of vCenter 5.5, 6.0 and 6.5

• HTML5 in case of vCenter 6.5 or later.

http://repo.infinidat.com/



2.4 Uninstalling Host PowerTools for VMware

2.4.1 Uninstalling Procedure1. Power-off the appliance.

2. On the Inventory panel, right-click tn the Host PowerTools for VMware virtual machine and select

either Remove from inventory or Delete from disk from the Host pop-up menu.

a. Remove from inventory - this option does not delete the virtual appliance from the disk

b. Delete from disk - this option deletes the virtual appliance from the disk

3. Unregister the Host PowerTools extension from the vCenter. For instructions see the section

below.

4. Manually clean the VASA Provider's IP from the Storage Providers screen. For instructions see the

section below.

5. Restart the vSphere web client.

• For instruction, follow the steps in the relevant VMware KB articles:

i. Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services

(2109887)

ii. How to stop, start, or restart vCenter Server Appliance services (2054085)

iii. How to stop, start, or restart vCenter Server services (1003895)

2.4.2 Unregistering Host PowerTools extension from vCenterWhen the Host Power Tool VMware appliance is powered off:

1. Open the vCenter Extension Manager via the vCenter MOB URL "https://<vcenter_name_or_IP>/

mob/?moid=ExtensionManager"

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109887


https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2054085




2. Unregister the extension "com.infinidat.powertools", using the method "UnregisterExtension"



3. Make sure that the unregister extension invoke ended successfully, and that the

"com.infinidat.powertools" is not listed anymore.

2.4.3 Re-registering Host PowerTools1. Power on the Host Power Tool VMware appliance.

2. Wait for the appliance to complete boot.

3. Host Power Tool VMware should be re-registered.

• Validate by opening the vcenter extension manager via the vcenter mob url "https://

<vcenter_name_or_IP>/mob/?moid=ExtensionManager" and check that the "com.infinidat.powertools"

was re-registered.

2.4.4 Removing the VASA provider 1. Login to the vCenter and select the vCenter object.

2. Choose Configure.

3. Select Storage Providers.

4. From the list select the storage provider named "com.infinidat.powertools".

5. Press Remove.



2.5 Changing the Host PowerTools IP settingsYou can change the IP settings that were determined during Host PowerTools installation.

1. Access the Host PowerTools for VMware Upgrade Tool as explained here: Upgrading Host PowerTools for VMware.

2. Click the Network tab and then the Address tab.3. Change the value of the IPv4 Address Type field from DCHP to Static.

The Network Address Settings screen opens.

4. Change the IP Address and netmask.Click Save Settings. The new IP settings are saved.

5. Restart the Host PowerTools VM appliance.


PREPARING THE ESXI HOSTS – 21

3 Preparing the ESXi hosts

3.1 ESXi hosts and clusters readiness

3.1.1 AboutThe Host Readiness Check validates that a selected host or an entire cluster (all the hosts that a cluster contains) are set with the InfiniBox best practices for vSphere.

• For a list of what the readiness check contain, see: List of items being checked by Host PowerTools for

VMware

3.1.2 Prepare a host or clusterIn order to prepare a host or cluster on the first time:

1. On vSphere Client, select the desired ESXi host or cluster object.

2. Locate the INFINIDAT View. For instruction see: Locating the INFINIDAT View

3. If the host / cluster is not already prepared, the Prepare Host/Cluster button will appear in the

top bar of the INFINIDAT View.

4. Click the Prepare Host/Cluster button.

The MPIO policy settings apply only to InfiniBox volumes. They do not affect volumes of other storage vendors.

https://wiki.infinidat.com/display/kb/List+of+items+being+checked+by+Host+PowerTools+for+VMware

https://wiki.infinidat.com/display/kb/List+of+items+being+checked+by+Host+PowerTools+for+VMware



5. Cluster Readiness screen opens, Press the Check / Fix button to indicate whether the Cluster is

ready.

3.1.3 Re-running the readiness checkTo ensure that a host or cluster is ready:


2. Access the INFINIDAT View. For instruction see: Locating the INFINIDAT View

3. Click the More Options icon, located on the top bar and select the Check Host/Cluster

Readiness option.

4. Cluster Readiness screen opens, Press the Check / Fix button to indicate whether the Cluster is

ready.

Note

Re-checking for host readiness is required In the following cases:

• Whenever you connect the host to a new InfiniBox system, you need to verify that the host is ready to work

with it.

• When you convert a host between FC and iSCSI (or vice versa)



3.2 Setting up iSCSI hosts via Host PowerTools for VMware

3.2.1 AboutHost PowerTools for VMware supports hosts that are connected to InfiniBox either via FC or iSCSI.

3.2.2 Setting up an iSCSI service on InfiniBoxSee InfiniBox best practices for setting up iSCSI services on the InfiniBox best practices page

3.2.3 Connecting to InfiniBox using iSCSI 1. On Host PowerTools for VMware main screen, set the protocol type to iSCSI on the slider at the

top-right of the screen.

2. From the menu at the top-right of the screen, select Check Host Readiness.

This may require a restart of the host.

3. Once the system passes the host readiness successfully, open the same menu, select Connect to

iSCSI system.

NoteHost PowerTools automatically identifies the connected InfiniBox systems for hosts that are connected via FC.

https://wiki.infinidat.com/display/TW/InfiniBox+best+practices+guides



The Connect to iSCSI system screen opens.

4. Type the name of the InfiniBox system. Click Continue.

5. On the Authentication Required screen, enter the InfiniBox user and password. Check whether

to remember these credentials and whether to use the credentials for all connected InfiniBox

systems. Click OK. You are returned to the Connect to iSCSI system screen.

6. Select an iSCSI network space from the drop-down list. Select an authentication method. Host

PowerTools for VMware negotiates the user and secret with InfiniBox.

Click Continue. You are returned to the Host PowerTools for VMware main screen.

7. The InfiniBox system is visible on the screen.

You can now start working with the InfiniBox system (provision, backup, restore, map, etc.).

3.3 Registering ESXi hosts and clusters

3.3.1 AboutRegistering the ESXi hosts / clusters on InfiniBox is required in order to enable storage provisioning & management.

• Prior to the registering process, all ESXi hosts should be properly connect (via FC or iSCSI) to the InfiniBox

system.



3.3.2 Registering a new host / cluster1. In vSphere Web client select the desired host or cluster.

2. Locate Host PowerTools for VMware INFINIDAT View. Follow the instructions here: Locating the

INFINIDAT View

• For each storage system, Host PowerTools displays its name, serial number, version, available operations and a list of mapped volumes. In the screenshot above, the only available operation is Register Host. The message on screen explains that no volumes can be created on the InfiniBox from within the vCenter Server, as long as it is not registered to InfiniBox.Register the host using your InfiniBox credentials. The credentials are stored on the appliance and are unique per vCenter user.The registration grants the user with provisioning privileges.

3. Click Register Host / Cluster.

Authentication Required screen opens.

4. Enter the following information:

a. User name - Enter the user name of InfiniBox.



b. Password - Enter the password of InfiniBox.

c. Remember these credentials - Check in order to allow Host PowerTools to remember

your access information.

d. Use these credentials for all systems - Check in order to allow Host PowerTools to use

the same credentials on all InfiniBox.

5. Click OK.

The InfiniBox system is now registered and available for use.

3.4 Adding new ESXi hosts to a registered cluster

3.4.1 AboutWhen adding a new host to an already registered cluster, the cluster should be re-registered.

Instructions

1. Connect the new host to the InfiniBox system(s) that the other hosts in the cluster are also

connected to.

• Do not register it yet.

2. In vSphere Client add the host to the desired vSphere cluster.

3. Select the vSphere cluster object.

4. Locate Host PowerTools for VMware INFINIDAT View. Follow the instructions here: Locating the

INFINIDAT View

5. The following massage appears: "Cluster is not ready to work with InfiniBox". Press the Prepare

Cluster button.

• InfiniBox best practices settings will be applied to the new host.

6. Refresh the System List by pressing the Refresh Page option on the top right "more options"

menu.

7. Re-register the cluster by pressing the Re-registration button.

3.5 Moving ESXi host between clustersFollow the instructions on: Moving VMware ESXi host between vSphere Clusters

https://wiki.infinidat.com/display/kb/Moving+VMware+ESXi+host+between+vSphere+Clusters


STORAGE MANAGMENT USING HOST POWERTOOLS FOR VMWARE – 27

4 Storage managment using Host PowerTools for VMware

4.1 Provisioning storage to vSphere

4.1.1 AboutProvisioning storage to the host is done by creating a volume on a specific capacity pool and mapping it to the host or cluster.

• You can either map an existing volume or create a new volume.

• Host PowerTools also automates the datastore creation. (optional)

This task performs the following actions:

1. Creates a volume in InfiniBox.

2. Maps it to the select host or cluster.

3. Initiates a storage HBA rescan.

4. Creates a datastore over the volume. (optional)

4.1.2 Creation a datastore In order to create a new datastore:

1. In vSphere Web client select the desired host or cluster.

2. Locate the INFINIDAT view. Follow the instructions here: Locating the INFINIDAT View.

3. Click Create.• The available operations are Map and Create, as you can either map an existing volume, or create

new volume(s).

4. The Create Volume screen opens.



5. Enter the following information:

a. Volume name - A default volume name is displayed on the screen. You may provide

another name.

b. Size - Set a size for the volume. Select the unit between GB and TB.

c. Thin - Check to create a thin-provisioned volume.

If this checkbox is left unchecked, the volume will be thick-provisioned.

d. Pool - Select a pool to associate the volume with. Only pools that are available to the user

are displayed.

Note that the available space on the storage system is indicated.

e. Create Series - Set the number of volumes that will be created

• If more that a single volume is created, the volume name that was entered above will serve as

a prefix to the name of the volume series.

• More information about creating a series of volumes is available on InfiniBox

documentation: Creating a volume

f. LUN - automatically allocated unless set by the user

g. Create datastore - Check in order to create a datastore for the volume.

• Uncheck If you prefer to create the datastore later on, or if the provisioned space will be used

for another purpose, such as Raw Device Mapping (RDM), disks, or existing datastore extent.

h. Set device name to volume name - Set the volume name to have the name of the

VMware container of virtual machines.

https://wiki.infinidat.com/display/DOC40/Creating+a+volume



6. Click Continue.

The Create Volume screen displays the operations that are about to take place.

7. Click Start.

The progress of the volume creation process is indicated on the screen.

8. Click Done.

The volume is created and is available in the volumes table.

9. If a datastore was created, it is ready for use.



4.1.3 Virtual machines considerations

4.2 Viewing mapped volumes on Host Powertools for VMware

4.2.1 Instructions1. In vSphere Web Client select the desired host or cluster object.

2. Locate the INFINIDAT view. Follow the instructions here: Locating the INFINIDAT View

3. For each discovered InfiniBox system, a list of volumes that are mapped to the selected host or

cluster is presented.

The volumes are displayed along with the following information:

• Datastore Name - The name of the datastore that uses the LUN.

• Volume Name - The name of the volume on the InfiniBox.

• Size - The storage space that was allocated to the volume when it was created.

• # Paths - The number of paths that are available from the datastore to the volume.

• LUN - Logical Unit Number. A unique identifier of the volume that is mapped to the cluster.

• Device Name - The VMware container of virtual machines. If the volume was not created by Host

PowerTools, the device name and the volume name are not identical.

• More Option icon - The More Options icon is available for each volume.

These actions are described in the following sections of this chapter.

4.3 Mapping an existing volume to vSphere

4.3.1 AboutThis operation maps a volume that already exists in InfiniBox. Typically, the volume was created from the InfiniBox GUI, or CLI.

4.3.2 Instructions1. In vSphere Web client select the desired host or cluster object.

2. Locate the INFINIDAT view. For instructions see: Locating the INFINIDAT View

NoteFor optimal performance, It's recommended to use Lazy-zeroed thick provisioning for all hard disks. (rather than thin)



3. Click the Map button on the desired InfiniBox system.

The Map Volume screen opens.

4. Search for the volume name.

5. Select a volume and click Done.

6. The volume is mapped and added to the volumes table.

• If a VMFS is discovered on the volume it will be mounted as a datastore.

4.4 Creating a datastore on an existing volumeThis operation creates a datastore over an InfiniBox volume. Typically, the volume was created from the InfiniBox GUI, or CLI.

4.4.1 Instructions1. In case the volume is not mapped, map the volume to the desired host or cluster. Follow the

instructions here: Mapping an existing volume to vSphere2. In vSphere Web client select a host or cluster.

3. Locate the INFINIDAT view. Follow the instructions here: Locating the INFINIDAT view.

4. locate the desired volume In the volume table on-which the datastore will be created.

5. In the Actions menu select Create datastore.



A datastore is created on the volume.

4.5 Renaming the device name to the volume name

4.5.1 InstructionsTo rename a device to match it's volume name:

1. In vSphere Web client select a host or cluster, which the desired device is mapped to.


3. Locate the desired device In the volume table.

4. In the Actions menu select Rename.



5. Make sure the Rename Device is checked and click OK.

The device name changes to the volume name.

4.6 Resizing datastores and volumes

4.6.1 AboutThis task performs the following actions:

• Resizes a selected volume.

• Initiates a storage HBA rescan.

• Extends the datastore that resides on the selected volume. (in case a datastore exists)

Note that VMware has certain limitations to datastore size, according to the VMFS type and product version. Refer to VMware documentation for obtaining the maximum datastore size that is applicable for your environment.

4.6.2 Instructions1. In vSphere Web client select the desired host or cluster, to which the desired volume to resize is

mapped.


3. Locate the desired volume in the volume table.



4. Select Resize from the Actions list.

Resize Volume screen opens.

5. Set the new size.

Click OK and then Done.

The volume is resized.

4.7 Unmap datastores and volumes

4.7.1 AboutThis operation deletes the mapping between a volume and a vSphere host or cluster.

This task performs the following actions:

• Unmount the VMFS, (If a datastore exists)

• Detach SCSI LUN.

• Delete the volume mapping on InfiniBox.

• Rescan HBAs

4.7.2 Instructions1. In vSphere Web client select the desired host or cluster, to which the desired volume to unmap

is currently mapped.


Warning Prior to delete the mapping, it is required to migrate all running virtual machines to another datastore, or to remove the Raw Device Mapping.



3. Select the desired volume from the table.

4. Select Unmap from the Actions list.

The volume is removed from the table and vCenter is updated that the device is permanently

disconnected.

When viewed from the InfiniBox GUI, the value of the Has Mapping field of the volume is

changed to NO.

4.8 Reclaiming freed space

4.8.1 AboutThis operation reclaims space that was freed (upon VM deletion, or VM migration), making it available for reuse.

• The operation is available for volumes that:

• Are thin.

• Have a datastore.

4.8.2 InstructionsIn order to reclaim the freed space:

1. In vSphere Web client select the desired host or cluster.


3. Locate the the desired datastore in the table.

4. Select Reclaim Space from the Actions list.

The space reclamation process is initiated for the selected volume.


BACKING UP VIRTUAL MACHINES – 36

5 Backing up virtual machines

5.1 How to backup virtual machinesINFINIDAT uses the storage terminology for a backup: the snapshot. The snapshot reflects the content of the volume – and the datastore – at a certain point-in-time.

INFINIDAT utilizes an advanced snapshot mechanism that allows for creating an extremely scalable number of snapshots for a virtual machine with no performance penalty.

The INFINIDAT Host PowerTools for VMware snapshot consistency process includes the following steps:

1. Creation of VM level snapshot

2. Creation a storage level snapshot

3. Deleting the VM level snapshot

5.1.1 Virtual disk consolidationWhen creating a VM level snapshot, the original VMDK file gets into R/O mode, and, at the same time, a new delta file is created for all the new writes.

• Whenever the VM level snapshot is deleted the delta file needs to be consolidated into the VMDK file (and

set the VMDK back to R/W).

• As this consolidation takes time and might affect performance, HPT-VM allows the user to skip this

consolidation by only deleting the VMware snapshot without consolidating the VMDK delta file.

• However, the user still has to consolidate the delta file, but the consolidation can be scheduled to be

run later, when the system is less busy.

5.1.2 InstructionsWhen taking a snapshot of a VM, a snapshot of the underlying InfiniBox volume is taken which includes all the data residing on its related datastore.

1. Select a datastore or a virtual machine and open its INFINIDAT tab.

Click Create Snapshot.



The Create Snapshot screen opens.

2. Fill in the following information:

a. Snapshot name

b. Description - Add optional text here.

c. Perform VMware consistency snapshot - Creates a consistent snapshot by performing

Quiesce.

d. Consolidate virtual disk - Consolidates the virtual disk now. If unchecked, the disk

consolidation will take place later, when the system is less busy.

e. Auto generate snapshot volume name - Uncheck this box to manually set the snapshot

volume name within InfiniBox.

3. Click Done.

The snapshot is created.

The snapshot is visible on screen along with its properties.



The snapshot volume is visible on the InfiniBox GUI or InfiniShell as well.

5.2 Modifying the snapshot name and descriptionYou can modify the name and description of the snapshot to allow for better searching of a specific snapshot.

1. Click on a snapshot and select Edit from the Actions menu.

The Edit Snapshot screen opens.

2. Modify the snapshot name and description.

Click Done.

5.3 Restoring from a backupRestoring a VM will recover a selected VM from a snapshot that was taken earlier.

The restore process performs the following operations:

1. Create a child snapshot of the InfiniBox snapshot which contains the VM-backup to recover.

2. Map the InfiniBox child snapshot to a selected ESXi host.



3. Initiate storage HBA rescan to discover the new mapping.

4. Mount the datastore which resides on the InfiniBox child snapshot.

5. Recover only the selected VM(s) from the restored datastore to a selected target datastore.

6. Unmount the datastore, unmap the InfiniBox child snapshot and delete it.

7. Perform rescan again to make sure the mapping is updated.

5.3.1 Instructions1. Click on a snapshot and select Restore from the Actions menu.

The Restore Snapshot screen opens.

2. Select either of the following:



a. Leave the Restored VM Name field as is – The restored volume is created with the

following name:

<vm_name>-restore.

b. Select a Target Host.

c. Select a Target Datastore

d. Select a Target Folder

3. Click Done.

The VM is restored.

5.4 Exposing a VM from snapshot

5.4.1 AboutExposing a VM from snapshot is a faster way to make the backed-up VM available to the datacenter.

• The Expose operation separates the need to copy (restore) the VM's data from the backup snapshot to

another datastore.

• The data of the VM that needed to be recovered is available almost instantly.



5.4.2 Exposing a VM from snapshot1. Click on a snapshot and select Expose from the Actions menu.

Expose Snapshot screen opens.

2. Fill the VM name, select the target host and the target folder. Click Done.

The snapshot is exposed. The virtual machine, volume and datastore names are displayed on

screen.



The exposed snapshot is also available from the navigation tree.

5.5 Deleting a snapshot1. Locate the desired snapshot and select Delete from the Actions list.

2. Approve the message on the screen.

Result:

• The snapshot is deleted from HPT-VM.

• In case of deleting a snapshot group, the snapshots of the other VMs in the selected group will be

deleted as well.

• The InfiniBox snapshot volume which contains the VM-backup is deleted from InfiniBox.



5.6 Restoring the VM from the Snapshot CatalogIn addition to the option to restore the vm from within the vm, there is an option to look for the snapshot in the Snapshot Catalog, saving the need to open the vm UI.

5.6.1 To access the Snapshot CatalogFrom the vSphere web client home page, click the INFINIDAT Snapshots icon.The Snapshots Catalog opens on the screen.

5.6.2 To restore a vm from a snapshot using the Snapshot Catalog1. Search or browse a vm.

2. Select the snapshot you would like to restore the vm from.

3. Click the Restore button that is available from the action menu that is available to the right of the

vm catalog entry.

The vm is restored.

Other actions that are available from the Snapshot Catalog

It is possible to:

• Edit the snapshot name and description

• Expose the vm (see more details here: Exposing a VM from snapshot)

• Delete the snapshot

• View the volume information

5.6.3 First time upgradeUpon the first upgrade to a Host PowerTools version that features the Snapshot Catalog:

• Connect to InfiniBox via the host or cluster view in order to refresh the connection to the InfiniBox system.

• Note that without this refresh, the snapshot will be visible but no action will be available


HOST POWERTOOLS FOR VMWARE APPENDICES – 44

6 Host PowerTools for VMware appendices

6.1 Host PowerTools for VMware administrative tasks

6.1.1 Metadata syncThis command synchronizes the host metadata as it is displayed on InfiniBox.


2. Locate the INFINIDATView. For instruction see: Locating the INFINIDAT View

3. Press the top bar right menu button.

4. Select Sync Metadata.

6.1.2 RescanThis command searches for storage sub-systems and creates block devices for newly found sub-systems and deletes block devices for LUNs that are no longer accessible.


2. Locate the INFINIDATView. For instruction see: Locating the INFINIDAT View


4. Select Rescan All.

*This command does not have an output.

6.1.3 Collecting logsThis command creates an archived tar.gz file that includes information that is relevant for troubleshooting.

To collect HPTVM logs:


2. Locate the INFINIDAT View. For instruction see: Locating the INFINIDAT View


4. Select Collect Diagnostic.

6.1.4 Troubleshooting VMware Web Client issuesFor more information see: Troubleshooting Host PowerTools for VMware.

https://support.infinidat.com/hc/en-us/articles/202319412-Troubleshooting-guide-for-Host-PowerTools-for-VMware



6.2 Appendix: Viewing volumes and hosts on the InfiniBox GUI

6.2.1 AboutINFINIDAT provides several management consoles that provide access and visibility into the storage system.

• Once a volume is creed, it is also visible directly through the InfiniBox GUI.

6.2.2 Viewing a volume on the GUI1. Open the InfiniBox GUI from a browser.

The typical URL is http://<system name>.<your domain>.

For example: http://box-cl005.lab.il.infinidat.com.

2. And the menu on the left, click on the Volumes & FS icon.

The volumes view opens on screen.

3. Click on a volume.

The volume view opens on screen.

6.3 Upgrading to Host PowerTools for VMware 5.3 (or later) from a previous version

6.3.1 AboutHost PowerTools for VMware version 5.3 or later contains an updated operating system (Ubuntu 18.04) and other infrastructure related updates. As a result, there is no automated and direct upgrade process from previous versions (which are based on previous Ubuntu releases).In order to upgrade to Host PowerTools for VMware 5.3 or later, users need to deploy the new Host PowerTools for VMware 5.3 and migrate the data from the older running instance.This guide specifies the migration process to Host PowerTools for VMware 5.3 or later while preserving the data from the existing Host PowerTools for VMware instance - snapshots database and configuration.

• Host PowerTools for VMware version 5.3 or later appliance is pre-configured with 2 vCPU and 10GB Hard

disk.

Do not deploy a new Host PowerTools for VMware 5.3 (or later) before performing the steps described in below.

http://box-cl005.lab.il.infinidat.com



Prerequisites

• A vCenter login with the appropriate permissions to deploy a new virtual machine.

• An instance of Host PowerTools for VMware 5.2.1 which will be migrated to a new Host PowerTools for

VMware 5.3 or later.

• If you are running an older Host PowerTools for VMware release, first upgrade to 5.2.1.

• It is advised to backup the existing Host PowerTools for VMware instance.

Supported upgrade paths

From / To 5.3.1

5.2.1

6.3.2 Migration Process1. Login to the existing Host PowerTools for VMware instance.

2. Navigate to the INFINIDAT Snapshots view screen:



3. Click the More Options menu on the view header and select Import / Export. The following

screen appears:

4. Click Export.

• Host PowerTools for VMware will export its data to a file (generating the file may take a few minutes).

• Save the file on the local machine.

5. Shutdown the existing Host PowerTools for VMware instance.

• Make sure the Host PowerTools for VMware virtual machine will not restart at a later time.

6. Deploy the new Host PowerTools for VMware 5.3 or later and power-on.

7. Navigate to the INFINIDAT Snapshots view screen.

8. Click the More Options menu on the view header and select Import / Export. • The Import / Export screen appears:

9. Click Select File.

• Browse and select the file that was generated previously on the old Host PowerTools for VMware

instance.

Do not power-on the old PowerTools for VMware virtual machineDO NOT power-on the old Host PowerTools for VMware virtual machine after the new 5.3 or later instance is deployed; it will override the new Host PowerTools for VMware instance configuration.

Do not take any snapshots using the new Host PowerTools for VMware instance before completing the migration process steps.



10. Click Upload.

• Upon completion, the following message appears:

11. The data has been migrated and the new Host PowerTools for VMware instance is now ready for

use (take new snapshots, etc.).

12. The old Host PowerTools for VMware virtual machine should be deleted from the vCenter

server.


ACTIVE-ACTIVE REPLICATION WITH VSPHERE – 49

7 Active-Active replication with vSphere

7.1 Preparing ESXi hosts when using Non-uniform connectivity

7.1.1 AboutWhen using using Non-uniform connectivity for Active-Active volumes on a vSphere environment it is required to set the ESXi hosts objects on InfiniBox to “ESXi” type.

7.1.2 New hosts or clustersWhen registering hosts or clusters using Host PowerTools for VMware versions 5.0 - 5.3.1, the hosts objects are automatically created as "ESXi" type.

• HPTVM versions greater than 5.3.1 will no longer set the InfiniBox hosts objects to "ESXi" type during

registration.

7.1.3 Existing hosts or clusters When configuring Active-Active volumes using Non-uniform connectivity for existing vSphere hosts or clusters it is required to ensure that all the are set as "ESXi" type.

Setting existing hosts or cluster to "ESXi" Type

Settings an entire cluster to "ESXi" type

Host PowerTools for VMware allows to set an entire cluster (all the cluster's hosts) to the ESXi type at once.

1. On vSphere Client, select the desired ESXi cluster object.

2. Access the INFINIDAT view. For instruction see: Locating the INFINIDAT View

NoteEnsure that the host / cluster is ready by running the Host / Cluster readiness. For instructions see: ESXi hosts and clusters readiness

Due to new recommendations, setting the ESXi hosts objects on InfiniBox to “ESXi” type is not required for Active-Active volumes when configured with Unifrom connectivity.

When using Host PowerTools for VMware versions 5.0 - 5.3.1 for Uniform configuration, make sure the ESXi hosts are set to the "Default" host type on InfiniBox using InfiniShell commands.



3. On the desired system click the More Options icon and select Host Type.

4. Click the Check button.

5. If all hosts are not set to ESXi type, a warning will appear. Click the Fix button to set all hosts to

the "ESXi" type.

• If all hosts are set as "ESXi" type, the green mark will appear.

Settings a specific host to "ESXi" type

1. On vSphere Client, select the desired ESXi host object.

2. Access the INFINIDAT view. For instruction see: Locating the INFINIDAT View

3. On the desired system click the More Options icon and select Settings.

4. Click the "Set to ESXi" button.

• For hosts that are already set as "ESXi" type, the "Set to ESXi" button will be un-clickable.

7.2 Settings Optimized/Non-optimized ESXi hosts

7.2.1 AboutHost PowerTools for VMware can be used to view and manage the ESXi hosts Optimized/Non-optimized ALUA states.

ALUA

ALUA is a standard used for identifying paths prioritization between the storage and hosts, and enables the initiators to query the target about path attributes, such as the paths ALUA state.



7.2.2 Supported Versions • ALUA management is supported with Host PowerTools for VMware v5 or later.

• InfiniBox ESXi host objects Active ALUA state can be displayed or changed for each connected

InfiniBox system.

• InfiniBox: InfiniBox hosts ALUA management is supported with InfiniBox version 5 or later.

7.2.3 InfiniBox Host ALUA statesInfiniBox allows to set the Active ALUA state (optimized/non-optimized) on the host object level. (storage side)

• Active/Optimized: the optimal paths to serve I/O for the LUN.

• Active/Non-Optimized: performing I/O to the LUN is less optimal using these paths.

By default, InfiniBox hosts are created as optimized. (InfiniBox will set the paths ALUA state of all the volume to are mapped to that host to "Active/Optimized")

• Settings the host Active ALUA state to "Non-optimized" applies only to the Active-Active volumes that are

mapped to the host.

• The paths ALUA state of volumes that are not undergoing Active-Active replication is always "Active/

Optimized".

7.2.4 Setting hosts to Optimized/Non-optimizedHost PowerTools allows to set the Active ALUA state of ESXi hosts to “Optimized” or “Non-optimized” on each connected system.

Note:

• When changing the ALUA state, it might take an additional short time for the operating system to discover

the change.

• vSphere might override the ALUA state that is set by InfiniBox in some scenarios.

• Typically, if an ESXi host sees only "Non-optimized" paths to a specific LUN, it will set these paths internally

to "Optimized".

• Available only for InfiniBox version 5.0 or later and using Host PowerTools for VMware 5.0 or later.

• The default checked radio button presents the current state.

Instructions

1. On vSphere Client, select the desired ESXi host object.

2. Access the INFINIDAT view. For instruction see: Locating the INFINIDAT view

3. On the desired system click the More Options icon and select Settings.

4. Under "Host paths ALUA state", select the desired state.



7.3 Viewing Active-Active volumes and datastores

7.3.1 AboutHost PowerTools for VMware automatically discovers Active-Active volumes and datastores.

• Whenever Active-Active volume is discovered, a dedicated table with Active-Active related information

("Active/Active Volumes" table) will appear at the top of the INFINIDAT view at the hosts and cluster vSphere

objects.

• Active-Active volumes are marked on each system volume list.

• Both Active-Active peers can appear on the volume list of each system. (in case both peers

are mapped)

• A pair of Active-Active volumes (both peers) will have the same device name and mount point.

Note

An Active-Active volume can be mapped to a host through one or both of the peers

• Each mapped peer will appear also in its system volumes list.

• If both peers are mapped, they will have the same specifications: Device name, datastore and size.

• Number of paths are depended on the connection to each of the systems.

• LUN (ID) is depended on the mapping. It is recommended to map both peers with the same LUN.

• The volume name of the peer can be different between the systems.

7.3.2 "Active/Active Volumes" tableThe "Active-Active Volumes" table provides the following information:

Settings a host to 'Non-optimized' on a specific system is recommended only if the host is mapped to active-active volumes where there is a better connection to the volumes via the other system.



• The device name.

• Datastore name (if created).

• Information about each peer system, presented under "System A/B" columns.

• System name.

• When hovering, the LUN ID appears.

• LUN's paths ALUA state.

• Number of paths to each system.

Note

• "System A" column will present the system with the lower S/N.

• If only one peer is mapped, it will be presented on the "System A" column.

• Complete information is available only for mapped peers.

• Number of paths to each system and LUN ID information is available only with the host object view.

7.3.3 Viewing Active-Active volumes and datastores1. In vSphere Web client select the desired host or cluster.


3. Main screen appears.

• The "ACTIVE / ACTIVE Volumes" table appears whenever an Active-Active volume is discovered.

• Active-Active volumes are labeled with "ACTIVE/ACTIVE" in each system volume list.



7.4 Snapshots for Active-Active virtual machines

7.4.1 AboutHost PowerTools for VMware allows to create snapshots and to perform other related operations on Active-Active virtual machines.

• Virtual Machines can be housed on a datastore which resides on an Active-Active volume. (a volumes that is

undergoing Active-Active replication)

• These VMs are referred as "Active-Active (A-A) Virtual Machines (VMs)".

• A datastore which resides on an Active-Active volume is referred as "Active-Active datastore".

InfiniBox and snapshots of Active-Active volumes

Snapshots of Active-Active volumes are individual to each peer.



• Snapshots cannot be replicated between the systems.

• Snapshots can be created only on synchronized peers. (the Active-Active replica state of the peer is

"Synchronized").

7.4.2 Creating Snapshots on Active-Active VMsA host that is running an Active-Active VM can access its datastore in a uniform or a non-uniform manner.

• The host access type determines if a snapshot can be created on both peers or only on one of them.

Uniform

In case of a uniform host access, a snapshot can be taken on both or one of the peers.

• The "Snapshot both Active-Active peers" checkbox will appear in the Create Snapshot modal.

• Checked by default.

Note: in case Host PowerTools for VMware cannot access one of the peers, the "Snapshot both Active-Active peers" checkbox will be grayed-out and a snapshot can be created only on the accessible peer.



Creating a snapshot on both peers

In case the "Snapshot both Active-Active peers" checkbox is left checked, Host PowerTools for VMware will create a snapshot on both peers of the underline Active-Active volume. (on both systems)

• Two snapshots will be registered and appear in the VM's snapshot list.

Note

Both peers must be synchronized.

• In case one of the peers is not synchronized, a snapshot will not be created on any of the peers - the

operation will fail.



Creating a snapshot on a specific peer

In order to create a snapshot only on a specific peer, clear the "Snapshot both Active-Active peers" checkbox.

• A system drop list will appear to allow to choose only the desired system.

In order to have a consistent and identical snapshot on both peers, "Perform VMware consistency snapshot" must be used.

• As the snapshot on each peer is individual and created sequentially, non-consistent snapshots

might not be identical between the peers.



Non-uniform

In case of a non-uniform host access, a snapshot can be created only on the accessible peer.

• A snapshot can be created only on the underling Active-Active volume (peer) that is mapped to the host

which runs the VM.

• The "Snapshot both Active-Active peers" checkbox will appear grayed-out in the Create Snapshot modal.

7.4.3 Creating Snapshots on Active-Active datastoreThe flow of creating snapshots on Active-Active datastores (through the datastore view) is similar to Active-Active VMs.

• If the cluster can access both peers, a snapshot can be taken as with the uniform manner.



7.4.4 Creating Snapshots at the Folder levelWhen creating a snapshot at the folder level (through the folder view) and the folder contains Active-Active VMs, Host PowerTools tries to create a snapshot on all accessible peers.

7.5 Other operations on Active-Active datastores

7.5.1 AboutThe following section include information about different Host PowerTools operations with Active-Active volumes.

Resize

Resize of Active-Active datastores is not supported.

Unmap

• In order to completely unmap an Active-Active datastore when both peers are mapped, both peers should

be unmapped.

• It is supported to unmap only one Active-Active datastore peer.

• When unmapping an active-active datastore peer:

• The VMFS will be unmounted only if the other peer is not mapped.

host powertools for vmware - infinidat.zendesk.com1.1 what is infinidat host powertools for vmware...

Documents