Simplivity HA Configuration Guide

Hewlett PackardEnterprise HPE OmniStack for vSphere Administration Guide Abstract This document describes administration procedures for HPE OmniStack for vSphere. Part number: P00118-001 Published: September 2017 © 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. 2 Contents Chapter 1: Introduction to HPE OmniStack......................................... 8 HPE OmniStack........................................................................................................................... 8 About HPE OmniStack architecture....................................................................................8 Network security..................................................................................................................9 About integration with vCenter Server................................................................................9 HPE SimpliVity Plug-in for vSphere Web Client......................................................................... 10 HPE SimpliVity Plug-in requirements............................................................................... 11 Install HPE SimpliVity Plug-in on Windows Server.......................................................... 12 Install HPE SimpliVity Plug-in on vCenter Server Appliance............................................15 Uninstall HPE SimpliVity Plug-in from Windows Server................................................... 16 Uninstall HPE SimpliVity Plug-in from vCenter Server Appliance.................................... 17 Enable HPE SimpliVity Plug-in experimental features on Windows Server......................18 Disable HPE SimpliVity Plug-in experimental features from Windows Server..................19 Enable HPE SimpliVity Plug-in experimental features on vCenter Server Appliance....... 19 Disable HPE SimpliVity Plug-in experimental features from vCenter Server Appliance........................................................................................................................20 Chapter 2: HPE SimpliVity Federation................................................ 22 HPE SimpliVity federations......................................................................................................... 22 Federation security...................................................................................................................... 23 Federations in vCenter Server Linked Mode.............................................................................. 23 Consistent time in a federation................................................................................................... 24 Federation events and alarms.................................................................................................... 25 Network configurations in a federation....................................................................................... 25 Change the IP address on a standard host..................................................................... 25 Network Interface Card (NIC) teaming....................................................................................... 26 Configure NIC teaming on vSwitch standard port groups................................................ 26 Configure NIC teaming on VDS distributed port groups...................................................27 Restart the Arbiter....................................................................................................................... 27 Virtual object details in an HPE SimpliVity federation................................................................ 28 View the HPE SimpliVity Home tab..................................................................................28 View the Topology tab...................................................................................................... 29 View the Throughput tab...................................................................................................29 View the Backup Consumption tab...................................................................................30 View the About tab........................................................................................................... 30 View clusters in a federation............................................................................................ 30 View hosts in a federation................................................................................................ 31 View datastores in a federation........................................................................................ 31 Contents 3 .............................................................................................................................. 36 Clusters........................................................................................................................................................ 39 Monitor cluster capacity................................................................32 View VM templates in a federation.............. 44 View virtual machines related to a cluster..............................................................32 View backup policies in a federation............................................................................................................................49 Calculating the memory reservation for the Admission Control Policy....................................................................................................................................................................................... 51 Cluster time zones...............................................................55 View a host in a cluster......................... 32 Chapter 3: Datacenters..............................................................................................................36 Create a cluster................................ 56 View host summary details............................................................................................................................................................................................................................................55 Host deployment.....................................................41 Objects related to a cluster................................................................................... 38 Remove a host from a cluster........37 Add a host to a cluster.............................................................................................................................................. 58 Reset the boot drive................................................................ 34 HPE SimpliVity datacenters...................................................................................................44 Intelligent Workload Optimizer.................................................... 45 Intelligent Workload Optimizer best practices.................................................................. 56 View host hardware details........................................................................................................................................................................................................................................55 HPE OmniStack hosts.... 40 View cluster performance...........................................52 Cluster removal........................................ 59 Contents 4 ............................................. View virtual machines in a federation.......................... 34 Chapter 4: Clusters...........43 View HPE OmniStack hosts related to a cluster.......................................................................... 52 Stretched clusters........................................................................................................................................................................................................................ 44 Intelligent Workload Optimizer requirements............... 38 View cluster summary details................................................................................................................................... 54 Chapter 5: Hosts................................................................................. 49 Enabling vSphere HA on a cluster..................................58 Host removal................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. 57 Remove a host from a Federation........ 58 Remove host from a federation........ 34 Create a datacenter......................................................... 46 vSphere HA configuration for a cluster with HPE OmniStack hosts................................................................................................................ 43 View datastores related to a cluster......................................................................................45 About managing HPE SimpliVity groups and rules........................................................... 39 Cluster capacity chart key....................................................................................................................................................................... ............................................................................................................. 64 Determine the IP address to use for standard ESXi host storage traffic..67 Chapter 7: Virtual machines.....................................................................................................71 View virtual machines associated with a host or datastore....................................................................................................................... 75 Delete virtual machines................................. 67 Resize a datastore..................................................................... 72 Move virtual machines (experimental)....................................................................................................... 64 Configure advanced settings on a standard ESXi host................... 64 HPE SimpliVity datastores and standard ESXi hosts...........................................79 Chapter 9: Backups..........................................................................................80 Backup planning......................................................................... 63 Share SimpliVity datastores with standard ESXi hosts................................................................................................................................................................................................................................................... 67 Delete a datastore.......................................................................... 74 Format the NTFS Volumes on Virtual Machines................................................................................................................................................................................................................................... 65 Edit the host file for standard ESXi hosts...69 Create virtual machines............................................................................................ 80 Application-consistent backups.......... Start up an HPE OmniStack host..................................... 73 Save credentials for VSS......................................................................................................... 60 Shut down one or more Virtual Controllers............................................................................................................................................................................................................................................................................................................................................................................... 77 Create virtual machine templates...................................................................................................69 HPE SimpliVity virtual machines.................................................. 61 Chapter 6: Datastores........................................................................................................................................................................................................................................................... 62 View datastore summary details............................................ 62 HPE SimpliVity datastores...............................................70 View virtual machine summary details.........................71 Move virtual machines................................ 74 Register virtual machines after an HPE OmniStack power failure............. 71 Clone virtual machines................................................................................................. 81 Contents 5 ............................................66 Access to datastores for standard ESXi hosts in a federation.......................................................................................... 69 View virtual machine performance.................................................................................................................................................................. 77 Clone virtual machine templates................ 66 Enable or disable HPE SimpliVity datastore sharing...................................................77 HPE SimpliVity virtual machine templates...............................................78 Move virtual machine templates..................................................................76 Chapter 8: Virtual machine templates.......................................................................................................................................................... 62 Create a datastore....... 78 Delete virtual machine templates............. 78 Move virtual machine templates (experimental)... ......... 113 Restore files from a backup.................................................................................... 85 Back up manually.........................................116 Restore an entire virtual machine................... 112 Create a new virtual machine or VM template from a backup................................ 130 HPE SimpliVity Alarms...................................................................................117 Revert shadow copy volumes using PowerShell script................ 121 Restore backups when the Hypervisor Management Service is down...........122 Restoring a backup to a new virtual machine when the Hypervisor Management System is down................................................................................................................................................................................................................................................................................................................ 89 Search for backups............................................................................................................................................................................................................128 Chapter 11: HPE SimpliVity alarms..................................... 84 Disaster protected backups.................................................................. 123 Chapter 10: Troubleshooting............................................................................................................................................................................................................................................................................................................ 126 Host issues...............114 About restoring VSS backups............ 126 Cluster issues............................................................................................................. 126 Virtual machine issues........................................................................................................................................................................................................................................ 99 Backup searches............. 83 Database backup strategies.......................................................................................134 Contents 6 ........................................................................................ 112 Replace a virtual machine or VM template with a backup.......................................................... 86 Back up with a policy............ 132 Alarms and HPE OmniStack hosts................................................................................................................................. 128 Miscellaneous issues............................................................................................................... 102 Restore HPE SimpliVity backups................................................................112 Backups restorations............................................................................................ 82 Database backup types............................................................................................................................................84 Options for protecting and recovering data..................................................117 Revert shadow volumes using diskshadow utility............................................89 HPE SimpliVity backup policies..................................................................................................... Guidelines for using Microsoft Volume Shadow Copy Service (VSS).................................... 119 Restore individual files.................................................................................................. 102 Manage backups......................................................................................................................................................................................................................................... 127 Backup issues.................................................................................................................................. 130 HPE SimpliVity-specific alarms........................................................................................................ 130 Pre-configured alarms....................................... 83 Database recovery types..............................................................99 Manage backups......................................122 Restore a virtual machine from a backup when Hypervisor Management System is down................86 Manual backups................................................................................................................................................................................... ........................................................................................................................................................................................................... 154 HPE SimpliVity terminology.......................................... 150 Create a Support Capture file................................................153 Remote support.................................138 Prerequisites for installing the Hewlett Packard Enterprise VAAI-NAS plug-in..........................138 HPE SimpliVity VAAI-NAS plug-in...................................................................................................143 Chapter 13: Deploy vCenter Server on an HPE OmniStack host.. 152 Customer self repair...........................................154 Documentation feedback.......................................................................Chapter 12: VAAI-NAS overview........................................................................................140 Configure the HPE SimpliVity VAAI-NAS plug-in.........153 Warranty information............................................................................................... 142 Verify VAAI-NAS plug-in installation using CLI commands.... 152 Support and other resources................................................................................................................................. 147 Linked Mode deployment..........150 OmniWatch. 152 Accessing Hewlett Packard Enterprise Support............................................................................................................................................................................. 152 Accessing updates.................................................... 145 Install vCenter Server on a virtual machine.................................................................................................................................................................148 Chapter 14: Support.................................................................................................................................................................................................................................................................................................................................... 148 Linked Mode deployment and VMware software.......................................................................................................................................................................... 146 Configure and deploy the HPE OmniStack host for use with vCenter Server................ 153 Regulatory information............................................................151 Appendix A: Support and other resources....................................141 Verify VAAI-NAS plug-in installation using vSphere Web Client options.............................. 138 Install the HPE SimpliVity VAAI-NAS plug-in on an HPE OmniStackhost......................142 Uninstall the HPE SimpliVity VAAI NAS plug-in VIB................................................................................150 Phone Home............................ 139 Install the HPE SimpliVity VAAI-NAS plug-in on a standard host...................................... 145 vCenter Server deployment on an HPE OmniStack host........................................................................156 Contents 7 ....................... 146 Upload the vCenter Server to the HPE OmniStack host.................................... see the HPE OmniStack for vSphere Deployment Guide. NOTE: If your cluster includes standard hosts that use Hewlett Packard Enterprise datastores. see the Hardware Installation and Maintenance Guide for your platform. you can manually install the Hewlett Packard Enterprise VAAI-NAS plug-in on those hosts. As capacity and performance needs increase. For more information on deploying hosts. Other networks might also be available based on VMware best practices. About HPE OmniStack architecture You create an HPE SimpliVity federation by connecting two or more HPE OmniStack hosts to a vCenter Server cluster. For more information on HPE OmniStack servers. storage and other resources to the HPE SimpliVity federation. Each host provides computing. This network of hosts is called a Hewlett Packard Enterprise federation. SimpliVity recommends that you deploy at least two HPE OmniStack hosts within a cluster. you can manage them and their related virtual objects using HPE SimpliVity Plug-in for vSphere Web Client. You also need to install the plug-in after upgrading the HPE OmniStack software in a deployed HPE OmniStack host if you want to continue using the VAAI-NAS plug-in. The plug-in improves performance and frees up memory when cloning virtual machines. It provides: • High availability • Scalability • Efficient disaster protection • Global unified management Each HPE OmniStack host comes with this installed software: • HPE OmniStack • Storage APIs for Array Integration (VAAI)-network-attached storage (NAS) plug-in To enable key functionality such as high availability. See this guide for details on installing the VAAI-NAS plug-in. Once you deploy HPE OmniStack hosts. A federation uses these networks: • Storage network—For data storage traffic.Chapter 1: Introduction to HPE OmniStack This section contains the following topics: • HPE OmniStack • HPE SimpliVity Plug-in for vSphere Web Client HPE OmniStack HPE OmniStack is a converged server and storage solution optimized for the VMware vSphere environment. • Management network—For management access to the federation. • federation network—For Virtual Controller communication within a federation cluster. you can add more HPE OmniStack hosts without disruption to users. dynamic resource sharing. and efficient data movement. Chapter 1: Introduction to HPE OmniStack 8 . But.After configuring the federation. you can restart its virtual machines from a functioning HPE OmniStack host. You can also use the vSphere HA cluster feature to have virtual machine failover occur automatically. For more information about the CLI commands. the network can be secured by using point to point IPsec VPNs between the sites. You then create virtual machines to read and write data and store the backups in a federation datastore. all VM data is written simultaneously to two HPE OmniStack hosts within the local cluster. including clusters. However. To achieve VM high availability. When you create a datastore in a cluster. the virtual machine continues to operate normally without requiring a restart. or when restoring a backup on HPE OmniStack hosts. You deploy HPE OmniStack hosts using Deployment Manager as described in the HPE OmniStack for vSphere Deployment Guide. HPE OmniStack hosts. datastores. The virtual machine data is deduplicated and compressed throughout its life- cycle. You manage the HPE OmniStack hosts using HPE SimpliVity options in HPE SimpliVity Plug- in for vSphere Web Client or vSphere options. The Arbiter agent facilitates communication between the HPE OmniStack hosts in the federation and enables failover and recovery operations. or you can add the HPE OmniStack hosts to a cluster in a different datacenter. About integration with vCenter Server You use the following HPE SimpliVity software to manage HPE OmniStack hosts in a federation: • Arbiter running on vCenter Server or another Windows computer outside the Federation. You can add them to the same cluster to increase the capacity of the cluster. you manage the objects associated with a federation. For example. one local and one remote) enables you to back up virtual machines to a remote location for disaster tolerance. a standard host can use an HPE SimpliVity datastore in a cluster outside the one it resides in. but able to communicate with the hosts. if an HPE OmniStack host containing virtual machine data. see the HPE OmniStack for vSphere Command Reference Guide. Intelligent virtual machine placement optimizes the location of highly available virtual machine data within the Data Virtualization Platform to ensure optimal performance for virtual machine workloads across all HPE OmniStack hosts. Communications between the HPE OmniStack hosts should be restricted to the specific IP addresses and TCP/ UDP ports used by the systems. but not the actual virtual machine fails. Using clusters in two different datacenters (for example. Intelligent virtual machine placement occurs automatically when creating or cloning a virtual machine. These datastores are shared by and accessible to all HPE OmniStack hosts in the cluster. To access the interactive REST Chapter 1: Introduction to HPE OmniStack 9 . your access to the datastore is limited to the hosts (HPE OmniStack hosts) in that cluster. In most cases. you can use the HPE SimpliVity command line interface (CLI) and the HPE OmniStack REST API to manage a federation instead of vSphere Web Client. • HPE SimpliVity vSphere Plug-in installed on the computer with vCenter Server. Any changes you make using the CLI or REST API appear in vSphere Web Client. If you need more capacity or performance. Most organizations already have point to point VPNs in place to secure site to site traffic and can utilize this same protection to also secure the HPE OmniStack traffic over the network. If an HPE OmniStack host running virtual machines fails. you create datastores in it. Some tasks include procedures to use the CLI in this Help.) Network security HPE OmniStack hosts use standard TCP/IP network technologies to communicate with each other. Alternatively. an HPE OmniStack host can use an HPE SimpliVity datastore within the same cluster. you can add more HPE OmniStack hosts with no disruption to users. and virtual machines the same way that you manage similar objects in vSphere Web Client. (However. Follow best practices for secure network communications (such as the use of firewalls and VPNs) to secure the communication between HPE OmniStack hosts as well as between the HPE OmniStack hosts and vCenter. it cannot use an HPE SimpliVity datastore from a different cluster. When the network connecting the systems is considered untrusted/public (such as a a WAN connection over the Internet to a remote office). Once you install HPE SimpliVity Plug-in. Then. click HPE SimpliVity federation from the Home tab.API documentation. you can access the HPE SimpliVity objects through the navigation pane just as you do with standard vSphere inventory objects. It needs to remain dedicated to its original HPE OmniStack host. you can access links to manage HPE SimpliVity clusters. see the "Enable HPE SimpliVity Plug-in experimental features" topic for your operating system. For example. you can create a configuration properties file in the vsphere- client directory and set a new property to true to enable it (or false to disable it). you can log into either version of the vSphere hypervisor and see the available experimental features under the All HPE SimpliVity Experimental Actions menu. Once enabled. Do not use any vSphere options on an Virtual Controller unless a Hewlett Packard Enterprise procedure includes them or Hewlett Packard Enterprise Customer Support (http:// www. you should not move a Virtual Controller to one.hpe. To access the HPE SimpliVity objects in vCenter Web Client 6.0 or 6. hosts. (You cannot see this menu unless it contains one or more experimental features. deploy your HPE OmniStack hosts. The main features in HPE SimpliVity Plug-in for vSphere Web Client allow you to: • Move virtual machines • Restore virtual machines • Perform manual or policy backups of virtual machines or virtual machine templates • Copy backups • Restore files NOTE: If you want to view the latest HPE SimpliVity Plug-in experimental features available for vSphere Web Client (Flash version) or vSphere Client (HTML version).com/support/hpesc) instructs you to use them. and set up your virtual environment. Caution: Each HPE OmniStack host has a dedicated virtual machine called the Virtual Controller that runs the HPE OmniStack software. although you can move virtual machines to resource pools in a federation. backup policies. The HPE OmniStack host Virtual Controller now uses TLS-class certificate validation to verify that vCenter has a valid and current certificate before establishing a connection to the vCenter services. If the Virtual Controller is unable to validate the certificate. navigate to https://[Virtual Controller IP address]/api/index. in a web browser. obtain the IP address of a Virtual Controller in the federation that you want to manage.) For more details on activating the experimental features. and virtual machines. For example.5. This opens the objects in the inventory panel and opens the following tabs: • HPE SimpliVity Home: Provides links to main tasks and Help • Topology: Displays a diagram of the connected clusters in the Federation • Throughput: Shows the backup throughput speed between clusters • Backup Consumption: Shows how much space the daily and projected backups consume Chapter 1: Introduction to HPE OmniStack 10 . it denies a connection and generates a log message. HPE SimpliVity Plug-in for vSphere Web Client The HPE SimpliVity Plug-in for vSphere Web Client application (HPE SimpliVity Plug-in) allows you to manage your HPE SimpliVity virtual inventory objects across the entire HPE SimpliVity federation using HPE SimpliVity features.html. datastores. Some tabs also include HPE SimpliVity subtabs. the VMware Clone option on a SimpliVity virtual machine).• About: Provides details on the software and Support details You can identify HPE SimpliVity tabs and options by looking for the HPE SimpliVity label or logo. 64-bit. click the Actions gear ( ) icon from the top of the tab or panel and select All HPE SimpliVity Actions. vSphere Web Client cannot expand the list of virtual machines in the tree view panel if it contains more than 100 virtual machines for vCenter Web Client 6. You may need to scroll to the right of the tab to locate the HPE SimpliVity subtabs or click the down arrows and scroll to the bottom of the drop-down menu to find the HPE SimpliVity option.0 or 6.0 or 6.5 (with vSphere Web Client or vSphere Client) • VMware vCenter Server Appliance 6.5. see the VMware Knowledge Base article. For details on setting up Enhanced Link Mode.5. see the VMware vSphere documentation. optimized to run vCenter Server) Chapter 1: Introduction to HPE OmniStack 11 . HPE SimpliVity Plug-in requirements Supported software HPE SimpliVity Plug-in for vSphere Web Client supports the following: Item Description Software • VMware vSphere 6. To access HPE SimpliVity menu options. Or. For more information. Operating System • Windows Server 2008 R2 or Windows Server 2012 R2 or 2016 (64-bit) • VMware vCenter Server Appliance (a preconfigured Linux virtual machine. right-click an inventory object listed in the appropriate table to access the Actions menu. If you want to access the Inventory Trees view.0 or 6. However.0 or 6.5 or with vCenter Server Appliance 6.5 (with vSphere Web Client or vSphere Client) NOTE: HPE SimpliVity Plug-in supports Enhanced Link Mode with vCenter Server 6. However. For vSphere Client (HTML5). select a virtual object from the Navigator panel and click Actions > All HPE SimpliVity Actions. • VMware vCenter Server 6. you can.0 or 6. you can only access a limited number of options.0 or 6.5. You cannot access all the SimpliVity options available through vSphere Web Client at this time. NOTE: The HPE SimpliVity procedures describe how to access objects from the Inventory Lists view. If you use VMware options on HPE SimpliVity objects (for example. you may need to refresh your screen before you can see the updated information in the SimpliVity tabs or see the SimpliVity menu options in the Actions menu. you must install the same version of HPE SimpliVity Plug-in for vSphere Web Client on each server running vCenter Server to access the HPE SimpliVity options. 2. see the VMware documentation. This application plugs into the existing vSphere Web Client interface. log out of vSphere Client and log back in after upgrading the hypervisor on a host. 9 (64-bit only). You must also enter administrator credentials during the installation process to successfully register it.x.Item Description Browsers Windows: • Internet Explorer 8. the HPE SimpliVity options may no longer function as expected. Procedure overview To manage HPE SimpliVity virtual objects in vSphere Web Client. some options may not appear in the All HPE SimpliVity Actions drop-down list. Download the executable (HPESimpliVity-Plug-in-for-vSphere-Web-Client-windows-x. and 10 • Mozilla Firefox (latest available) • Google Chrome (latest available) Macintosh or Linux: • Mozilla Firefox (latest available) • Google Chrome (latest available) Configuration requirements For details on hardware requirements and how to use Enhanced Linked Mode with multiple vCenter Servers or vCenter Server Appliance systems. Procedure 1. For example. Log on to the Windows computer that has VMware vSphere with vCenter Server using administrator privileges. Install HPE SimpliVity Plug-in on Windows Server Before you begin If you have an earlier version of HPE SimpliVity Plug-in for vSphere Web Client installed. If you plan to use Enhanced Linked Mode. Chapter 1: Introduction to HPE OmniStack 12 . Hypervisor upgrade requirements If you upgrade the ESXi version of your previously deployed OmniStack hosts after you installed HPE SimpliVity Plug-in for vSphere Web Client on vSphere. you must install HPE SimpliVity Plug-in for vSphere Web Client on the vCenter Server that you plan to access.exe) and double-click it to open the Setup wizard. remove it before you install a later version.x. To ensure all the options function as expected. For more details on upgrading your hypervisor. see the VMware vSphere documentation. Click Next to open the License Agreement 4. Select I accept the agreement and click Next to open the Installation Directory screen.3. Chapter 1: Introduction to HPE OmniStack 13 . 5. Specify the directory you want to use for the plug-in. The default location is C:\Program Files\Hewlett Packard Enterprise\HPESimpliVityPluginForVSphereWebClient. Then click Next to open the VMware vCenter Credentials screen. 6. Enter your vSphere administrator credentials in the User Name and Password fields. In the E-mail field, enter the email address of an administrator responsible for HPE SimpliVity Plug-in for vSphere Web Client so this person can receive alerts. Then click Next. 7. Click Next when ready to install. 8. Wait while the Setup wizard installs the application. The progression bar shows the progress. When done, click Next to finish the installation. Chapter 1: Introduction to HPE OmniStack 14 9. Review the steps to log out of vSphere Web Client (if logged in) to ensure that you can see the HPE SimpliVity Plug-in options the next time you access vSphere Web Client. If you do not need to log out of vSphere Web Client, select Launch VMware vSphere Web Client. Then click Finish. Install HPE SimpliVity Plug-in on vCenter Server Appliance Before you begin If you have an earlier version of HPE SimpliVity Plug-in for vSphere Web Client installed, remove it before you install a later version. Procedure overview To manage HPE SimpliVity virtual objects in vSphere Web Client, you must install HPE SimpliVity Plug-in for vSphere Web Client on the vCenter Server that you plan to access. This application plugs into the existing vSphere Web Client interface. You must also enter administrator credentials during the installation process to successfully register it. If you plan to use Enhanced Linked Mode, you must install the same version of HPE SimpliVity Plug-in for vSphere Web Client on each server running vCenter Server to access the HPE SimpliVity options. Procedure 1. Open a command line to log on to vCenter Server Appliance using root privileges. For example, run PuTTY to specify the host IP address you need to access. Then log in as root and enter the root password when prompted. 2. If you do not see the bash prompt (#), enter one of the following (depending on your version of vSphere): Chapter 1: Introduction to HPE OmniStack 15 • For vSphere 6.0: shell.set --enable True Then enter: shell • For vSphere 6.5: shell 3. Place the HPE SimpliVity Plug-in for vSphere Web Client application file (for example, HPE-SimpliVity-Plug-in-for-vSphere-Web-Client-linux-x64-x.x.x.run) on the Linux virtual machine. You may want to use shell commands scp, curl, or wget to access the file to run the installer. NOTE: To access a secure file transfer protocol (sftp), enter: chsh -s /bin/bash root 4. Set the executable bit by entering: chmod +x <HPE-SimpliVity-Plug-in-for-vSphere-Web-Client-linux-x.x.x.run> 5. Enter the following to run the installer: ./<HPE-SimpliVity-Plug-in-for-vSphere-Web-Client.x.x.x.run> The installer opens with a prompt to read the License Agreement. 6. Press Enter to scroll through the License Agreement and read it. 7. When prompted to accept the agreement, enter y to continue the installation and open the prompt to specify the directory for the HPE SimpliVity Plug-in. 8. Press to Enter to accept the default path for the installer or specifiy another path and then press Enter. This opens the VMware vCenter Credentials prompt. 9. Enter your vSphere administrator credentials in the User Name and Password fields. In the E-mail field, enter the e-mail address of an administrator responsible for HPE SimpliVity Plug-in for vSphere Web Client so this person can receive alerts. 10. Enter y when prompted to continue the installation 11. Wait while the Setup program installs the application. When done, you see a "Finish" message. 12. Review the steps to log out of vSphere Web Client (if logged in) to ensure that you can see the HPE SimpliVity Plug-in options the next time you access vSphere Web Client. If you do not need to log out of vSphere Web Client, log in with the administrator credentials you used during the installation process. Uninstall HPE SimpliVity Plug-in from Windows Server Before you begin Before uninstalling the HPE SimpliVity Plug-in for vSphere Web Client, make sure you have administrator privileges to access the system. Procedure 1. From the Start menu, click Control Panel > Programs > Uninstall a program. 2. From the list of installed programs, double-click HPE SimpliVity Plug-in for vSphere Web Client. Chapter 1: Introduction to HPE OmniStack 16 x.simplivity. browse to the following folder and delete the com. Uninstall HPE SimpliVity Plug-in from vCenter Server Appliance Procedure overview You can remove the HPE SimpliVity Plug-in for vSphere Web Client from vCenter Server Appliance at any time.web-client-x. Remove the package file from Windows Server Procedure overview Uninstalling the HPE SimpliVity Plug-in does not remove the package files from the computer with vSphere Web Client. click Next. Procedure 1.x.simplivity.simplivity. Stop VMware vSphere Web Client service (for vSphere 6.web-client-x. Click OK to close the information window.simplivity. 2.x and C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\vc-packages\ vsphere-client-serenity\com. If you do not see the bash prompt (#). Procedure 1.web-client-x.web-client-x.x. The server does not use these files.x folder: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\ vsphere-client-serenity\com.5).0.x.x • If you use vCenter Server 6. browse to the following folders to delete the com.3.0) or VMware Service Lifecycle Manager service (for vSphere 6.5). 2.x folder from both directories: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\ vsphere-client-serenity\com.0: shell. run PuTTY to specify the host IP address you need to access. Do one of the following: • If you use vCenter Server 6. but you may want to delete them to remove unnecessary files from your computer. Click Yes to confirm that you want to delete the plug-in.set --enable True Chapter 1: Introduction to HPE OmniStack 17 . 5. 4.5. Wait while the installer removes the software. When finished. Restart VMware vSphere Web Client service (for vSphere 6. enter one of the following (depending on your version of vSphere): • For vSphere 6.web-client-x.simplivity. Then log in as root and enter the root password when prompted.x 3.x. Open a command prompt to log in to vCenter Server Appliance using root privileges.0) or VMware Service Lifecycle Manager service (for vSphere 6. For example. Restart vsphere-client services.x folder from both directories: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.x. starting.5: shell 3. For details. Press Enter when prompted. Enter y to continue.simplivity. you can view the experimental features by creating a properties file and adding a property. Then. 5.5. you can see the available options under the All HPE SimpliVity Experimental Actions menu.x. You see an "uninstall status complete" message when done.simplivity.simplivity* • If you use vCenter Server Appliance 6. Enter the following command with your appropriate path information. Enable HPE SimpliVity Plug-in experimental features on Windows Server Before you begin After you install HPE SimpliVity Plug-in for vSphere Web Client. You see a message to confirm the uninstall process. The server does not use these files.x. see this VMware Knowledge Base article: Stopping. Chapter 1: Introduction to HPE OmniStack 18 ./uninstall 4. 6. Wait while the Setup program removes the application.x/ . For example: cd /opt/Hewlett Packard Enterprise/HPESimpliVityPluginForVSphereWebClient-x. Procedure 1. but you may want to delete them to remove unnecessary files from your computer. Do one of the following: • If you use vCenter Server Appliance 6. Stop vsphere-client services. browse to the following folder and delete the com.simplivity* and /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.x folder: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com. when you log into the vSphere hypervisor (Flash).web-client-x. 2.web-client-x. Then enter: shell • For vSphere 6. browse to the following folders to delete the com.0. or restarting VMware vCenter Server Appliance services.simplivity* 3. Remove the package file from vCenter Appliance Procedure overview Uninstalling the HPE SimpliVity Plug-in does not remove the package files from vCenter Server Appliance. Procedure overview If you plan to use Enhanced Linked Mode.simplivity.experimental=false 3. Procedure overview Chapter 1: Introduction to HPE OmniStack 19 . you can no longer access the All HPE SimpliVity Experimental Actions menu to access the experimental features. 2. 7. (Click Start and enter the following at the Search programs and files prompt: services.properties file and change the experimental value to false as shown (all lowercase): com. when you log into the vSphere hypervisor (Flash).common.simplivity. right-click and select New > Text Document.5).client. you must create a properties file and set the experimental property on every vCenter Server in the Linked Mode configuration. Procedure 1. 4. Save the file.0. 4. you can view the experimental features by creating a properties file and adding a property.properties and remove the . Right-click a virtual machine and select All HPE SimpliVity Experimental Actions to see the experimental features (for example. Then. Disable HPE SimpliVity Plug-in experimental features from Windows Server Before you begin You can disable the experimental features in HPE SimpliVity Plug-in. Restart vSphere Client services. 2.client.simplivity. Right-click vSphere Web Client Service (for 6. Enable HPE SimpliVity Plug-in experimental features on vCenter Server Appliance Before you begin After you install HPE SimpliVity Plug-in for vSphere Web Client.x) or VMware Service Lifecycle Manager (for 6. you can see the available options under the All HPE SimpliVity Experimental Actions menu. Open Windows Explorer and browse to: %VMWARE_CFG_DIR%\vsphere-client (C:\ProgramData\VMware \vCenterServer\cfg\vsphere-client).client. Log on to the Windows computer that has HPE SimpliVity Plug-in for vSphere Web Client using administrator privileges. Log into vSphere Web Client (Flash) or vSphere Client (HTML5) and access click HPE SimpliVity Federation from the Home tab to access the SimpliVity virtual objects.experimental=true 5. If you do not see a file named com.simplivity. Procedure 1. Open the file and add the following line (all lowercase): com. Name the file com. Open Windows Explorer and browse to: %VMWARE_CFG_DIR%\vsphere-client (C:\ProgramData\VMware \vCenterServer\cfg\vsphere-client).txt extension.msc and press Enter. 3.simplivity. Restart vSphere Client services. Back Up Virtual Machine). 6.common. Save the file.properties. Open the com. Once disabled. Open the vshere-client folder. common. Then log in as root and enter the root password when prompted.properties chmod 644 com. For example.simplivity. Restart vSphere Client services by entering the following command: service-control --stop vsphere-client service-control --start vsphere-client 8. For example: -rw------.client. Procedure 1. you must create a properties file and set the experimental property on every vCenter Server in the Linked Mode configuration. Check that the permissions and user owner of the configuration file in /etc/vmware/vsphere-client match webclient.1 vsphere-client root 40 Mar 3 14:57 com.simplivity.client.client. Open a command line to log on to vCenter Server Appliance using root privileges. enter one of the following (depending on your version of vSphere): • For vSphere 6. Back Up Virtual Machine).0: shell.5: shell 3.properties file and add the following line: com.set --enable True Then enter: shell • For vSphere 6. If you do not see the bash prompt (#).simplivity.properties 5.If you plan to use Enhanced Linked Mode. Run the following commands: cd /etc/vmware/vsphere-client/ touch com.properties.simplivity. run PuTTY to specify the host IP address you need to access.client.simplivity. 7. 2.client.properties chown vsphere-client com.simplivity. Disable HPE SimpliVity Plug-in experimental features from vCenter Server Appliance Before you begin Chapter 1: Introduction to HPE OmniStack 20 .experimental=true 6. Right-click a virtual machine and select All HPE SimpliVity Experimental Actions to see the experimental features (for example. Log into vSphere Web Client (Flash) or vSphere Client (HTML5) and access click HPE SimpliVity Federation from the Home tab to access the SimpliVity virtual objects.properties -rw------. Save the file.properties 4. Edit the com.1 vsphere-client users 4541 Mar 3 15:42 webclient. Open a command prompt to log in to vCenter Server Appliance using root privileges.simplivity. run PuTTY to specify the host IP address you need to access. If you do not see the bash prompt (#). Procedure 1. For example.You can disable the experimental features in HPE SimpliVity Plug-in.common.client.client.simplivity.properties file: cd /etc/vmware/vsphere-client/com. 2. 6.experimental=false 5.simplivity. Then log in as root and enter the root password when prompted. enter one of the following (depending on your version of vSphere): • For vSphere 6.client. Enter the following command to restart vSphere Client services: services-control --stop vsphere-clientservice-control --start vsphere Chapter 1: Introduction to HPE OmniStack 21 .properties file and change the experimental value to false as shown: com.0: shell.simplivity. Once disabled. Edit the com. you can no longer access the All HPE SimpliVity Experimental Actions menu to access the experimental features.5: shell 3.properties 4. Save the file.set --enable True Then enter: shell • For vSphere 6. Enter the following commmand to locate the com. Support contact information. • Topology: Shows cluster connections in a federation. backup policies. Each HPE OmniStack host also has a dedicated virtual machine called the Virtual Controller. and a link to open the HPE SimpliVity Plug-in for vSphere Web Client Help. For example. datacenters with other HPE OmniStack hosts) Chapter 2: HPE SimpliVity Federation 22 . A ROBO topology allows one main cluster (for example. • Backup Consumption: Shows how much space the backups consume on a daily basis and the projected rate of consumption for the steady-state of the federation based on the current policy settings. You can manage all the objects through menu options and tabs. search backups. version. and share data. you see these tabs when you click the HPE SimpliVity federation icon: • HPE SimpliVity Home: Includes options to create objects. The objects associated with the HPE OmniStack hosts appear in vSphere Web Client under an HPE SimpliVity federation. you see a visual of how you set up the network configuration of your vCenter Servers. hosts. you can use one of the following configurations in an HPE SimpliVity federation: • Full mesh • Remote Office/Remote Branch (ROBO) A full mesh topology allows every HPE OmniStack host in every cluster in the network to communicate with each other. and virtual machines. a cluster with HPE OmniStack hosts at the company headquarters) to communicate with other clusters (for example. For example. When you view the topology of your federation. HPE OmniStack hosts include HPE OmniStack technology that uses deduplication and compression to efficiently store.Chapter 2: HPE SimpliVity Federation This section contains the following topics: • HPE SimpliVity federations • Federation security • Federations in vCenter Server Linked Mode • Consistent time in a federation • Federation events and alarms • Network configurations in a federation • Network Interface Card (NIC) teaming • Restart the Arbiter • Virtual object details in an HPE SimpliVity federation HPE SimpliVity federations An HPE SimpliVity federation uses at least two HPE OmniStack hosts. The Virtual Controller runs the HPE OmniStack software. This configuration can help if the HPE OmniStack hosts in one cluster fail because you can direct traffic to other HPE OmniStack hosts in other clusters in the network. datastores. manage. The objects include clusters. and trademark information. • Throughput: Provides the current backup throughput speeds between clusters. • About: Shows the product name. To manually create. a cluster on a spoke can only connect to the main cluster on the hub. you can only access the virtual objects (clusters. All the clusters can communicate with the main. For more information on using HPE OmniStack hosts in a ROBO environment. but they cannot communicate with each other through the separate networks. A Linked Mode environment can contain only a single federation. centralized cluster. • Restore a virtual machine from a backup stored on an HPE OmniStack host in a different vCenter Server instead of the vCenter Server of the virtual machine host. This feature enables you to: • Create a remote virtual machine backup in a different vCenter Server. the clusters on the spokes can only communicate with the cluster at the hub. see the HPE SimpliVity Unified Protected Remote Office Solution. See the vSphere Datacenter Administration Guide for detailed information about vCenter Server security. and roles (sets of privileges) to control access to resources in vCenter Server. NOTE: The privileges and roles assigned on a standard ESXi host are separate from the privileges and roles assigned in vCenter Server. when you perform certain actions. backup policies. But. You cannot use the HPE SimpliVity Plug-in to manage the federation if you connect to a standard ESXi host. For example. The combination of user name and password authenticates a user for access and the assigned privileges authorize the user to perform specific tasks. backups) available in the source cluster or in the cluster of the main hub. Changes that you make to the Windows domain or Active Directory are reflected in vCenter Server. use the tools that manage your Windows domain or Active Directory environment. The federation requires specific VMware accounts and privileges as described in the HPE OmniStack for vSphere Deployment Guide. or copying a backup to another cluster. groups. Federation security Federation security is based on the access control system for the vCenter Server where the federation resides. such as moving a virtual machine. Therefore.through a separate wide area network (WAN) or a local area network (LAN) connection. Authorized users for vCenter Server can be users included in the Windows® domain list referenced by vCenter Server or local Windows users on vCenter Server. See the vCenter Server and Host Management document for more information. remove. NOTE: If you use a ROBO configuration. restoring a virtual machine or file from a backup. These access controls apply to the federation objects. in addition to all other objects in vCenter Server. A user is an individual authorized to log in to a host or vCenter Server. or modify vCenter Server users. This configuration is also known as "hub and spoke" because the HPE OmniStack hosts in the main cluster ("hub") can communicate with all the HPE OmniStack hosts in the extended clusters ("spokes"). Federations in vCenter Server Linked Mode HPE SimpliVity federations support VMware vCenter Servers in Linked Mode and enable access to HPE SimpliVity and VMware virtual objects across all HPE OmniStack hosts. datastores. Chapter 2: HPE SimpliVity Federation 23 . you set up users. virtual machines. The permissions defined for these users apply whenever a user connects to vCenter Server. For example. use only: Fedadmin@MyLab51 To deploy HPE OmniStack hosts in a vCenter Server in Linked Mode. you must update the NTP configuration for each HPE OmniStack host. you specify the AD domain as part of the user name: ◦ MyLab51\Fedadminpassword ◦ Fedadmin@MyLab51 • Using OVF Tool. creating backup policy rules. see the HPE OmniStack for vSphere Deployment Guide. indicate the following when: • Logging into vCenter. or moving virtual machines.conf. there is a risk that you might specify the wrong cluster when performing operations such as creating manual backups. configure NTP on each HPE OmniStack host and make sure it matches the NTP configuration the vCenter Server uses. you must set the following: • In /etc/ntp. set maxdist 30 • In /etc/likewise/lsassd. If NTP time drifts by several seconds. This mode requires Active Directory (AD) for server authentication. For example. do not use identical names for datacenters when you use vCenter Linked Mode. you must include the AD domain in the login credentials. If the NTP configuration used by vCenter Server changes.conf make sure that sync-system-time = no Chapter 2: HPE SimpliVity Federation 24 . specify credentials using this format: vi://MyLab51%5cFedadmin:password • Logging into the Virtual Controller using SSH to access the svtcli account. Consistent time in a federation To ensure consistent time in a federation. VMware allows you to assign identical names to clusters that are contained by different vCenters.• Move virtual machines between clusters contained by an HPE OmniStack host in a different vCenter Server. Caution: To avoid selecting a cluster in the wrong datacenter when you perform certain tasks. HPE OmniStack storage capacity might be misreported. specify the domain: ◦ MyLab51\Fedadminpassword ◦ Fedadmin@MyLab51 • Using the svt-session-start CLI command. With vCenter Server in Linked Mode. To manage your federation in Linked Mode. you need appropriate single sign-on accounts with appropriate credentials for all vCenter Servers in linked mode. if the AD server name is MyLab51 and the administrative account is Fedadmin. but in the same HPE SimpliVity federation." In particular. go to the VMware knowledge base site and search for "Synchronizing ESXi/ESX time with a Microsoft Domain Controller (1035833). Because HPE SimpliVity operations often require that you specify a cluster as a destination. In this environment. Make the datacenter names unique and meaningful. If you decide to use an internal NTP server. NOTE: It is important to maintain consistent time in a federation so that communication between HPE OmniStack hosts is properly synchronized. you need to install vCenter Single Sign- On (SSO) using multi-site mode. Contact Hewlett Packard Enterprise Customer Support (http://www. you must update your federation to recognize the new IP address. This will be a carefully scheduled operation. Storage. You can use vSphere alarms to monitor HPE SimpliVity federation and HPE OmniStack events and alarms. • Moving the VMware cluster to a different network. • HPE OmniStack Host IP address and subnet netmask. Procedure overview This operation causes shared datastores to be unavailable for a short time. Procedure 1. If you do not need to add a new VMkernel NIC.com/support/hpesc) if you need to change IP addresses in HPE OmniStack IP address pools and subnet masks used by all HPE OmniStack hosts in a federation. Before you begin Ensure you know the shared datastore name(s) and the standard ESXi host name. including: • vCenter Server IP address and subnet netmask.com is not in the list of email recipients you add to vCenter alarms. but it does not support Management Information Base (MIB). click it. Network configurations in a federation Changing IP addresses is most likely to arise during a cluster reorganization or upgrade. and click the Summary tab. You can also locate warning messages in the Alarms portlet or browse to the virtual object. skip to step 2 on page 26. Warnings appear with yellow exclamation point icons. To automatically send messages to specific administrators about events and issues that might help them diagnose and correct issues. You can also click Acknowledge or Reset to Green to clear some warnings. probably involving federation down time. including subnet netmask changes. Change the IP address on a standard host If you change the IP address on a standard ESXi host. You might also need to change the IP address of standard ESXi hosts that access your federation.Federation events and alarms Events and alarms help you monitor normal operations and also identify problems before they disrupt service. or Management IP addresses and subnet netmasks.hpe. • Moving one HPE OmniStack host from a federation to a different network. NOTE: Ensure that support@simplivity. • HPE OmniStack federation. Federation events and alarms are logged in vCenter Server and appear in the Recent Tasks and Alarms portlet windows as they do for vSphere events and alarms. Typical reasons for changing HPE OmniStack host IP addresses are: • Network changes that affect the entire cluster. Complete this step if you need to add a new VMkernel NIC with the new IP address: Chapter 2: HPE SimpliVity Federation 25 . Click the Networking subtab. do these substeps to modify the vSwitch: a) Change the IP address for the NIC. Then click the pencil icon to open the Edit Settings dialog box. Click Hosts to open the Objects tab. Network Interface Card (NIC) teaming After you deploy HPE OmniStack hosts to a cluster. 2. you must uplink two or more adapters to a virtual switch. You can also find details on the VMware Knowledge Base site (https://kb. 6. From vSphere Web Client Home. 5. 3. c) Delete the original VMkernel NIC with the old IP address (optional). you can configure NIC teaming to do the following: • Increase network capacity for the virtual switch hosting the team. 3. • Provide passive failover if the hardware fails or it loses power. Click Teaming and failover. 4. a) Add the VMkernel NIC with the new IP address for the standard ESXi host. d) Run svt-datastore-share for each shared HPE SimpliVity datastore to confirm that the old IP address is no longer valid and remove stale NFS exports for that NIC.com) and do a search on "NIC teaming in ESXi and ESX." Configure NIC teaming on vSwitch standard port groups Procedure 1. Select the following settings (if not selected already): Option Description Load balancing Route based on the originating virtual port Network failover detection Link status only Notify switches Yes Failback Yes Chapter 2: HPE SimpliVity Federation 26 . 7.vmware. For more details on configuring NIC teaming for a standard vSwitch or a vSphere Distributed Switch (VDS). To use NIC teaming. b) Create NFS exports for the new VMkernel NIC using the svt-datastore-share command for each shared Hewlett Packard Enterprise datastore. Click the name of the switch from the Switch column. This removes stale NFS exports and creates new NFS exports that use the new IP. Right-click the host and click Settings. 2. click HPE SimpliVity Federation. see the following topics. Verify that the standard ESXi host can access the share by checking that the host mounted the datastore. b) Run svt-datastore-share for each shared Hewlett Packard Enterprise datastore to ensure that the system recognizes the new IP address and removes the old IP address. If you do not need to add a new VMkernel NIC. If the Arbiter stops running. expand the dvSwitch to display the distributed port groups. 12.8. Right-click a distributed port group and select Edit Settings. Click OK. 3. one 10 GbE vmnic must be an Active adapter. Repeat this procedure for the second vSwitch. Click Teaming and failover. 7. 5. NOTE: Never restart the Arbiter for any reason other than resolving problems. 2. Click OK. In the inventory panel. NOTE: For direct-connect 10 GbE configurations only. Click OK. Restart the Arbiter Procedure overview The Arbiter resolves synchronization and other issues that could occur between HPE OmniStack hosts within a cluster. while the other 10 GbE vmnic is a Standby adapter. From vSphere Web Client Home. Click the pencil icon to check the settings for all the port groups in the vSwitch. 11. 10. Procedure Chapter 2: HPE SimpliVity Federation 27 . 9. 4. The Arbiter must be installed and running on the computer with vCenter Server or another computer that the HPE OmniStack hosts can access. Verify that the vmnics are listed under Active adapters. Repeat these steps for each distributed port group. The Arbiter runs as a Windows service. click Networking. an alarm appears in the federation and you must restart the Arbiter in Windows services. Select the following settings (if not selected already): Option Description Load balancing Route based on the originating virtual port Network failover detection Link status only Notify switches Yes Failback Yes 6. Your federation cannot communicate properly when the Arbiter is not running. Configure NIC teaming on VDS distributed port groups Procedure 1. click HPE SimpliVity Federation. For example. NOTE: You cannot filter or find items in the Size or Creation Time columns. Then drag it to the location you want in the chart. 4. Then scroll to the bottom of the page and click the down arrow of the Copy ( ) icon on the right. click Select Columns. and HPE SimpliVity objects in a federation. • To move portlets (small panels of information in a tab). show. click the Filter down arrow. • To move columns. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking Home > vCenter Inventory Lists and expanding the HPE SimpliVity section. When you access the Objects tab for an inventory object. you do not need to select rows. 5. Just select Copy All. (To select more than one item. Virtual object details in an HPE SimpliVity federation You can access HPE SimpliVity tabs to view details on the topology. or copy items. Chapter 2: HPE SimpliVity Federation 28 . click a column header and hold down the cursor to select the whole column. Click Start and then OK to close the properties dialog. It also contains a link to open the HPE SimpliVity Plug-in for vSphere Web Client Help. Click the Windows Start button and run services. right-click a column header and select the appropriate option. You can customize the table data a number of different ways. 2. hold down the Ctrl key as you click rows. If you want to select all the items. and lock columns or hide and show the toolbar. throughput. 3. • To copy an item. and click OK. Close the Services window. you see a list of details in a table. View the HPE SimpliVity Home tab Procedure overview The HPE SimpliVity Home tab provides an overview on the HPE SimpliVity software and virtual objects. click the far right corner of a column header and toggle the list up or down by clicking the arrow icon. size. Then drag it to the location you want in the tab. select one or more items from the table. backup consumption. click the down arrow and choose Highlight All to search all the columns or choose Select Columns and select the columns you want to search. To refine your search. • To list information in ascending or descending order. Select the Extended tab in the Services window and look for the Arbiter. Select Copy to Clipboard Selected Items Only. find.msc. click the header of a portlet and hold down the cursor to select the whole portlet. • To hide. To open the HPE SimpliVity Home tab: • From vSphere Web Client Home. you can add or remove columns and filter. • To filter items.1. Double-click the Arbiter entry to open its properties dialog. • To find an item. select or clear an item. Enter the appropriate information and click Enter. scroll to the bottom of the page and click the Find binoculars ( ) icon in the left corner. Create backup policies. including those in a Remote Office/Branch Office (ROBO) configuration. • Number of virtual machines and virtual machine templates. The table maintains throughput for completed backups until you navigate to a different view.) 3. you see links to perform key tasks. 3. For example. You can then click on cluster names to navigate to that cluster. 4. Create virtual machines. click HPE SimpliVity Federation. You can adjust the refresh rate. (HPE OmniStack hosts must reside in one or more clusters per datacenter. Click Topology to open the Topology tab. click HPE SimpliVity Federation. If any earlier versions of HPE OmniStack hosts reside in a datacenter. From vSphere Web Client Home. select it from the Find a cluster drop-down list. • To find a cluster. 2. • To zoom out. you can see all the clusters in your federation. It opens with a table that lists backups between clusters in the federation that have a throughput greater than zero. Do any of the following. you see links to create a backup policy and datastore.At the bottom of the Home tab. This displays all clusters in the federation. To get started creating an HPE SimpliVity federation: Procedure 1. The view only shows backup throughput entries when the bytes sent from the source cluster to the destination cluster exceed zero (0). you must remove them and redeploy them to the appropriate cluster. Create a cluster for the HPE OmniStack hosts. Procedure 1. You can also click HPE SimpliVity Plug-in Help (or any question mark in an HPE SimpliVity dialog box) for details on the procedures. Procedure 1. 5. • Number of hosts. click the name of the cluster. Each cluster lists the following details: • Cluster name. slide it to the left. Chapter 2: HPE SimpliVity Federation 29 . • To zoom in. View the Topology tab When you open the Topology tab. 2. Click the Throughput tab. View the Throughput tab Procedure overview The Throughput tab shows the current backup throughput speeds between clusters. 2. depending on how you need to navigate the screen: • To navigate to a cluster. Deploy HPE OmniStack hosts to one or more clusters in a datacenter. From vSphere Web Client Home. Create a datastore. slide the zoom bar to the right. • Backup Throughput: The speed of the current process. If the throughput does not change or drops to zero during a refresh cycle. Auto- Refresh turns off automatically after 30 minutes. edit a policy for a datastore. virtual machine. From vSphere Web Client Home. build. Procedure 1. View the About tab Procedure overview You can access information on the HPE SimpliVity Plug-in for vSphere Web Client version and access links to Support through the About tab. NOTE: Double-click a cluster name in the table to navigate to the Getting Started tab (or the last tab you accessed). The table includes the following information: • Source Cluster: The cluster originating the backup. If you notice that the daily or predicted steady-state consumption values come close to the capacity threshold (yellow or red zone). 2. click HPE SimpliVity Federation. For example. From vSphere Web Client Home. and trademark and patent information. adjust your backup policies. or 60 seconds in the Refresh Interval drop-down list. 30. 15. Procedure overview The Backup Consumption tab shows the percentage of daily backups created and stored and how much room you have left to add more. version. or virtual machine template and change the frequency and retention time to reduce the number of backups. Disable or enable automatic updates by clicking Auto Refresh On. View the Backup Consumption tab An HPE SimpliVity federation can create and store a maximum number of backups. Hewlett Packard Enterprise Support email address and Web site. • Destination Cluster: The destination cluster. • Last Updated: The time of the backup throughput value collection. 3. View clusters in a federation Chapter 2: HPE SimpliVity Federation 30 . The predicted steady-state shows the estimated percentage of backups the current policies can create and store in the Federation and how much room you have left before reaching the limit. Click the About tab to see details on the product name. These columns only update when there are new throughput values greater than zero to report. Procedure 1. This opens to the Manage tab. 2. Click the Backup Consumption tab. click HPE SimpliVity Federation. the "Last Updated" and "Backup Throughput" columns remain unchanged. You can also adjust the refresh time interval by selecting a time interval of 5. HPE OmniStack version (appears Mixed during an upgrade). 2. or removed). Click Clusters to open the Objects tab. Virtual Controller shutdown status. creation time. Procedure 1. click HPE SimpliVity Federation. you can see the cluster name. size. Procedure 1. Click Hosts to open the Objects tab. cluster name. and Management. you can see the host name (IP address). For example. you can see the datastore name. Virtual Controller Name. Arbiter IP address. right-click a cluster and select All HPE SimpliVity Actions. and upgrade status. time zone. For example. amount of free space. total capacity. faulty. suspected. HPE OmniStack version (appears Mixed during an upgrade or if hosts use different versions). managed. vCenter Server IP address. click HPE SimpliVity Federation. and Federation network IP addresses. Procedure 1. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. View datastores in a federation Procedure overview You can view all the datastores in a federation and review details about them from one tab. From vSphere Web Client Home. Virtual Controller state (alive. click HPE SimpliVity Federation. View hosts in a federation Procedure overview You can access all the HPE OmniStack hosts in a federation and review details about them from one tab. datacenter. From vSphere Web Client Home. For example. Storage.Procedure overview You can view all the clusters in a federation and view details about them from one tab. vCenter Server IP address. To access HPE OmniStack host options. and datacenter. datacenter name. Chapter 2: HPE SimpliVity Federation 31 . used space. To access HPE SimpliVity cluster options. assigned backup policy. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. and upgrade status. cluster. From vSphere Web Client Home. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. Arbiter status (Connected or Not Connected). 2. right-click a host and select All HPE SimpliVity Actions. application. click HPE SimpliVity Federation. 2. storage HA status. For example. right-click a virtual machine template and select All HPE SimpliVity Actions. and save the credentials to the virtual machine using an application-consistent policy to use VSS. right-click a virtual machine and select All HPE SimpliVity Actions. View virtual machines in a federation Procedure overview You can view all the virtual machines in a federation and review details about them from one tab. For example.2. valid or invalid credentials because you must use a supported operating system. unknown fault. right-click a datastore and select All HPE SimpliVity Actions. datastore name. amount of memory available. you can see the virtual machine template name. View VM templates in a federation Procedure overview You can view all the virtual machine templates in a federation and review details about them from one tab. Chapter 2: HPE SimpliVity Federation 32 . (You do not see a Backup Policies object listed under the vCenter Home Inventory Trees or Inventory Lists. storage HA status. click HPE SimpliVity Federation. Click Virtual Machines to open the Objects tab. amount of memory used. For example. capable. datacenter name. you can see the virtual machine name. From vSphere Web Client Home. assigned policy. vCenter Server IP address. Procedure 1. and application- aware status. For example. datastore name. To access Hewlett Packard Enterprise virtual machine template options. and datacenter name. View backup policies in a federation Procedure overview HPE SimpliVity Plug-in lists Backup Policies as an object in the vSphere Web Client Inventory panel. amount of memory available. Procedure 1. 2. vCenter Server IP address. cluster name.) You can view all the backup policies in a federation and review details about them from one tab. click HPE SimpliVity Federation. Procedure 1. cluster name. To access Hewlett Packard Enterprise virtual machine options. From vSphere Web Client Home. assigned policy. From vSphere Web Client Home. Click Datastores to open the Objects tab. amount of memory used. this column may show: unknown. you can see the backup policy name and number of rules in a policy. To access HPE SimpliVity datastore options. Application-aware status refers to the ability to use the Microsoft Volume Shadow Copy Service (VSS) method to create application-consistent backups. Click VM Templates to open the Objects tab. Chapter 2: HPE SimpliVity Federation 33 . To access Hewlett Packard Enterprise backup policy options. Click Backup Policies to open the Objects tab. right-click a backup policy and select All HPE SimpliVity Actions. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. 2. But. (HPE OmniStack hosts must reside in one or more clusters per datacenter. OmniStack hosts must reside in one or more clusters per datacenter. You must meet the appropriate requirements to use long-distance vMotion (for example. Once you add HPE OmniStack hosts to a cluster. you can see the cluster listed under the SimpliVity Federation section in the inventory panel (and through the vSphere Cluster option). see the VMware vSphere documentation. Chapter 3: Datacenters 34 . you can still create a datacenter using vSphere options and use it to contain clusters with HPE OmniStack hosts. Once you move the virtual machines. the virtual machine uses the policy assigned to that datastore. • SimpliVity Move Virtual Machine to change the datastore for a virtual machine with it powered off. They cannot reside outside a cluster. HPE SimpliVity Plug-in does not include a Datacenter object. You can access Hewlett Packard Enterprise options through the Hewlett Packard Enterprise objects (Backup Policies. For more information on vSphere Web Client features and privileges. Hosts. Clusters. backups. you must redeploy it as described in the HPE OmniStack for vSphere Deployment Guide.) You can then create and manage virtual machines. Create a datacenter Procedure overview You use vSphere Web Client options to create a datacenter. backup policies. If you need to move HPE OmniStack hosts from a datacenter to a cluster in the datacenter. You must also have sufficient permissions to create a datacenter object. you can use: • vSphere vMotion to move powered-on virtual machines to HPE OmniStack hosts in the same cluster to OmniStack hosts across long distances (such as a cluster in a datacenter in another continent) with minimal impact to performance. they use the datastore and policy used by the new cluster. Virtual Machines. A federation can contain multiple datacenters with multiple clusters. Before you deploy your HPE OmniStack hosts. If you change the datastore. NOTE: You can use long-distance vMotion to move powered-on virtual machines from a cluster of OmniStack hosts within one datacenter to a cluster of OmniStack hosts in another datacenter. an Enterprise Plus license for the vCenter Server). • vSphere Storage vMotion to change the datastore for a virtual machine with it powered on. You can choose a datacenter located within the same vCenter Server or another one (if using Linked Mode). Object have limited interaction with each other across different clusters in different datacenters. VM Templates. and datastores in the cluster. see the VMware documentation. For more details. For example.Chapter 3: Datacenters This section contains the following topics: • HPE SimpliVity datacenters • Create a datacenter HPE SimpliVity datacenters A datacenter functions as a container for inventory objects (such as HPE OmniStack hosts and virtual machines). create a cluster in a datacenter. and Datastores). such as selecting datacenters for backup policies or when managing multiple vCenter Servers in Linked Mode. click vCenter Servers. Chapter 3: Datacenters 35 . right-click the datacenter with the duplicate name and click Rename from the vSphere list. *. 2. But. 3. 5. \. Unique names makes it easier to select the correct datacenter when performing specific tasks. click vCenter Inventory Lists or Global Inventory Lists (depending on your version of vSphere). :. It is not considered a SimpliVity object. Under Resources. The datacenter appears under the vSphere section of the inventory panel. You see all the datacenters in a HPE SimpliVity federation once they all have unique names. To rename a datacenter. an HPE SimpliVity federation may show the number "4" for four datacenters. Right-click the vCenter server where you want the datacenter and click New Datacenter. You must create a cluster and deploy your HPE OmniStack hosts to it to access HPE SimpliVity options. you only see three datacenters listed because two datacenters have the same name. From vSphere Web Client Home. enter a unique name for the datacenter. see the HPE OmniStack for vSphere Deployment Guide. The Datacenter object reflects the new number of datacenters in the inventory. ?). Do not use symbols or special characters in the name (for example. For more information on deploying hosts to a cluster. NOTE: You cannot see all the datacenters in an HPE SimpliVity federation unless they have unique names. ".Procedure 1. In the Datacenter name field. Click OK. For example. 4. when you click Datacenters. /. From the cluster. For example. IWO works with vSphere DRS to move virtual machines closer to their data source (host with the source virtual machine). But. Once a cluster includes HPE OmniStack hosts. The cluster can contain one to eight HPE OmniStack hosts and unlimited standard ESXi hosts that may or may not share an HPE SimpliVity datastore. the standard ESXi hosts must share a HPE SimpliVity datastore with an HPE OmniStack host in the cluster for IWO to include them in the load balancing process. For example. This improves load balancing efficiency. However. This means that all the hosts in the cluster need to share the same HPE SimpliVity datastore to duplicate the data in the datastore across the attached hosts.Chapter 4: Clusters This section contains the following topics: • Clusters • Create a cluster • Add a host to a cluster • Remove a host from a cluster • View cluster summary details • Monitor cluster capacity • View cluster performance • Objects related to a cluster • Intelligent Workload Optimizer • vSphere HA configuration for a cluster with HPE OmniStack hosts • Cluster time zones • Stretched clusters • Cluster removal Clusters Clusters allow you to share resources between hosts and associated virtual machines. Do not move HPE OmniStack hosts to other clusters within the same datacenter or SimpliVity options do not function as expected. if you use vSphere Distributed Resource Scheduler (DRS) with HPE OmniStack hosts in a cluster. and lowers latency. you need at least two HPE OmniStack hosts to create an HPE SimpliVity federation. Chapter 4: Clusters 36 . a cluster that uses Intelligent Workload Optimizer can include three to eight HPE OmniStack hosts and unlimited standard ESXi hosts. HPE OmniStack hosts cannot reside outside the cluster or in other clusters in the same datacenter--even if the datacenter has multiple clusters. it functions differently than a standard vCenter cluster. you should also use HPE SimpliVity Intelligent Workload Optimizer (IWO). A standard cluster functions as a distributed computing system that has processing power and memory. you can access HPE SimpliVity options and all the vSphere cluster options. HPE OmniStack hosts must reside in one or more clusters per datacenter. share data. reduces the number of hops to read and write data. the virtual machines lose HA compliance and the datastore is no longer accessible to the virtual machines that used to reside on the host you moved. A cluster with HPE OmniStack hosts requires a shared storage system. and ensure High Availability (HA) for continuous operation. For example. 2.Inventory. you can turn on DRS and vSphere High Availability (HA). 4. Enter a meaningful and unique name for the cluster to easily identify it. From vSphere Web Client Home. you can create a cluster. or application failures. DPM is an optional feature of vSphere DRS that optimizes power. Before you begin • You must also have privileges to create and modify a cluster (Host. • Leave vSphere Distributed Power Management (DPM) off. the Virtual Controller appears disabled.Inventory. see the HPE OmniStack for vSphere Deployment Guide. Chapter 4: Clusters 37 . it could shut down the Virtual Controllers to save power. Clusters can share resources between hosts and associated virtual machines. However. 3. HPE OmniStack hosts cannot reside outside the cluster for SimpliVity options to function as expected. This is deliberate because the Virtual Controller cannot move off an HPE OmniStack host.Modify Cluster). You can turn on vSphere HA once you have more than one HPE OmniStack host deployed (or moved) to the cluster. It is a dedicated virtual machine that runs the HPE OmniStack software. do not turn on vSphere HA. click Datacenters. For more information on vSphere privileges. Under Resources. This allows DRS to automatically place virtual machines on hosts when they power on and automatically migrates virtual machines to different hosts to optimize resources. For example. NOTE: If you need to create a datacenter. Create a cluster After you create a datacenter through vSphere options.) An HPE OmniStack host cannot function without the Virtual Controller. Deploy HPE OmniStack hosts to the cluster using Hewlett Packard Enterprise Deployment Manager or move them from a datacenter to the cluster. 5. if you review the virtual machine Automation Level status through the DRS VM Overrides option. (Each HPE OmniStack host has a Virtual Controller. leave the default of Fully Automated at the Automation Level field. Then follow the prompts to select the vSphere cluster features you want to use.Create Cluster and Host. NOTE: You can use vSphere HA to protect against host. You can also use VMware Enhanced vMotion Compatibility (EMS) or Swapfile Location. But. Right-click the datacenter where you want the cluster and click New Cluster. right-click the vCenter server where you want the datacenter and click New Datacenter. If you use vSphere DRS. if you do not have any HPE OmniStack hosts deployed to the cluster yet. click vCenter Inventory Lists or Global Inventory Lists (depending on your version of vSphere). But. Procedure 1. For more information on deploying hosts. if you use it. • The datacenter must contain all the HPE OmniStack hosts in one or more clusters (up to eight per cluster). virtual machine. see the VMware vSphere documentation.Best practices: • Leave Intelligent Workload Optimizer enabled whenever you use vSphere DRS. Then enter a unique name. see the HPE OmniStack for vSphere Deployment Guide. Chapter 4: Clusters 38 . you must remove them from the federation and redeploy them. To shut down the virtual machines. Procedure 1. right-click a virtual machine and select Power > Power Off. or Host.Maintain). Right-click the host you want to remove and click All HPE SimpliVity Actions > Shut Down Virtual Controller.x. To migrate a virtual machine. • If you want to move an HPE OmniStack host from a cluster to cluster in another datacenter. For details on deploying hosts. The Virtual Controller runs the HPE OmniStack software and appears with "VC" in the name. • Migrate all running virtual machines. see the VMware documentation. 5. see the VMware documentation. 4.Add a host to a cluster If you need to add HPE OmniStack hosts to a cluster. Intelligent Workload Optimizer removes any existing Hewlett Packard Enterprise (svt) groups and rules from DRS and stops creating new Hewlett Packard Enterprise groups and rules. For more information on using the vSphere Move To option. click Host and Clusters.Move Host. change the /etc/host file so it references another HPE OmniStack host in the cluster.) Remove a host from a cluster You can remove an HPE OmniStack host from a cluster at any time. For more information on DRS. you can use vSphere Move options to move an HPE OmniStack host or a standard ESXi host to a cluster within a datacenter before you start using OmniStack 3. Do one of the following: • Power off all running virtual machines. • If the cluster uses vSphere DRS with Intelligent Workload Optimizer and the host removal process leaves the cluster with less than three HPE OmniStack hosts. except the Virtual Controller. Then follow the prompts to change the host or datastore.Remove Host from Cluster. Before you begin • You must also have privileges to remove a host from a cluster (Host. The host you move them to must share at least one datastore. For more information on vSphere features and privileges. Right click the host you want to remove from the cluster and click Maintenance Mode > Enter Maintenance Mode. Click Yes to confirm the shutdown process. 3.5. If the cluster uses vSphere DRS.x hosts from a cluster to another cluster in the same or a different datacenter.Inventory. Host. you must deploy them directly to the cluster. • Drag and drop the virtual machines to another host in the cluster if you use vSphere vMotion. Click OK to confirm Maintenance mode. From vSphere Web Client Home. (To move previously deployed hosts with 3.6. it may reject the Maintenance Mode request if it violates a mandatory (must run on hosts in group) DRS rule. 2. you need to right-click the virtual machine and select Migrate. If you need to move 3.6.x versions of HPE OmniStack or earlier.Inventory.Inventory. you must remove it and redeploy it as described in the HPE OmniStack for vSphere Deployment Guide. If a standard ESXi host shares the datastore of an HPE OmniStack host you want to remove. see the VMware documentation. Chapter 4: Clusters 39 . 2.5. Tags. Click Clusters to open the Objects tab with a list of all the clusters in the federation. unused (free). View cluster summary details Procedure overview You can view the summary information of a cluster and access the HPE SimpliVity portlet details. Procedure 1. the HPE SimpliVity portlet shows the total cluster capacity. Procedure 1. Click Clusters to open the Objects tab. see the VMWare vSphere documentation. space saved from deduplication and compression. Double-click the name of the cluster that you want to view. click Hewlett Packard Enterprise federation. click Monitor Capacity. You see a summary of the total number of processors and vMotion migrations. The right-side of the tab lists the free and used space and capacity for CPU. Click the Summary tab. Click Yes when prompted to confirm the removal. and storage. memory. number of virtual machines in the cluster. Cluster Consumers. click HPE SimpliVity Federation. capacity used.) For details the vSphere portlets. For example. This opens the Monitor tab where you can click the HPE SimpliVity Capacity subtab to view the capacity image. deduplication and compression ratios. Use these options if the virtual machines are taking too long to reach storage HA compliance and you want to stop the shut down or force it to continue. and status of Arbiter (connected or not connected). From vSphere Web Client Home. NOTE: To see a graphical representation of the logical and physical capacity of the cluster. Right-click the host you want to remove and click Remove from Inventory. and used space. You also see the vSphere Cluster Resources. NOTE: Once you start the shutdown. storage efficiency. and Related Objects portlets above the Hewlett Packard Enterprise portlet. you also see Custom Attributes and Update Manager Compliance portlets. This lists all clusters in the federation. 7. two additional options become active: Cancel Virtual Controller Shutdown and Force Virtual Controller Shutdown. (If you use vSphere 6. Monitor cluster capacity Procedure overview You can monitor the storage space for a cluster to determine the capacity. From vSphere Web Client Home. 3. 2. 4. 6. (You can also double-click the name of the cluster . Cluster capacity chart key Use this reference as a guide to the HPE SimpliVity Capacity chart. dlick the Monitor tab (if necessary).) The tab opens with an image similar to the one shown.3. Capacity panel label Description Logical Capacity Perceived storage space of a cluster before deduplication and compression occurs. and click the SimpliVity Capacity subtab. Physical Capacity Actual bits of data stored on physical drives (HDD or SSD) in an HPE SimpliVity cluster. Right-click the cluster you want to view and click All HPE SimpliVity Actions > View Capacity. Chapter 4: Clusters 40 . HPE SimpliVity Efficiency Storage efficiency ratio. calculated from the deduplication and compression ratios. Deduplication and Compression Data deduplication and compression ratios. Total Cluster Physical Capacity Shows the following in MB. and by local and remote backups. Used Capacity Used storage space appears in light green ( ) inside the ring.Capacity panel label Description Logical Capacity ring and color legend Shows the following capacity information inside the ring: • Virtual Machine Data: Amount of logical space consumed by virtual machines appears in purple ( ). It shows the total value of logical space consumed by virtual machines. • Total physical capacity for the cluster. Savings Physical space saved as a result of storage efficiency. It represents the data deduplication and compression ratios. virtual machine clones. • Free (available) physical space shown in light gray ( ). View cluster performance Chapter 4: Clusters 41 . GB or TB) and the size expressed as a percentage of the total amount of logical data stored. Data Stored Logical data stored appears in light green ( ). GB. or TB: • Used total physical capacity shown in light green ( ). The legend provides both the size (MB. • Local Backups: Amount of logical space consumed by the virtual machine backup hosted on the datastores in this cluster appears in orange ( ). • Remote Backups: Amount of logical space consumed by virtual machine backups hosted for remote clusters appears in dark green ( ). Click the SimpliVity Performance subtab. The IOPS chart shows the number of input (read)/output (write) operations per second. Click to toggle to Auto Refresh Off to stop refreshing the tab information. Procedure 1. you see a screen similar to this: 4. and latency. hosts. Click Clusters. The Throughput chart shows the total amount of disk I/O usage for clusters. And the Latency chart shows the average time it takes to reply to a storage request in milliseconds (ms). NOTE: You can also double-click the name of the cluster you want to view. From vSphere Web Client Home. For example. 2. click HPE SimpliVity Federation. Right-click the cluster you want to view and click All HPE SimpliVity Actions > View Performance.Procedure overview You can monitor the performance for a cluster to determine the current or past throughput. Leave the Auto Refresh On button set to automatically refresh the performance information at the set time interval. and latency read and write values. and virtual machines in the datacenter in megabytes per second (MB/s). You see the Hewlett Packard Enterprise Performance tab open with an image that shows three charts with the read and write values for the throughput. 3. Chapter 4: Clusters 42 . IOPS. input/output operations per second (IOPS). Click the Monitor tab (if necessary). months. network IP addresses. Click Close Top Contributors when done. write. in progress. View HPE OmniStack hosts related to a cluster Procedure overview You can view all the HPE OmniStack hosts in a cluster. the charts appear empty. Or. you can click the Clusters ( ) icon from the HPE SimpliVity federation section of the inventory list to locate the cluster and find the related objects. click Open Top Contributors. hours. Procedure 1. 6. It includes details on the name and read. To automatically navigate to the virtual machine tabs to get more details or perform actions on a virtual machine. It lists all the clusters in the federation. 11. click 1 minute (1m). 3. For example. 1 week (1w). To see the virtual machines with the most reads and writes in a cluster at a given time. Move your cursor over any of the three graphs to bring up a tracking point (thin vertical line across all three charts) at the time you want to review. Slide the scroll bar above the charts to the left or right to see a precise moment of performance on the charts in minutes. or Latency chart to see the chart populate with a list of the top virtual machine contributors at the time and date set for the chart you clicked. and upgrade status (success. 2. For example. click federation. A panel slides open to the left of the charts ready to populate the list with details on the virtual machines. 9. HPE OmniStack version. 1 month (1m). slide the time range bar all the way to the right. you can select a view that shows you details on the HPE OmniStack hosts. To see the current Read and Write data again. Click Clusters to open the Objects tab. weeks. To change the order from descending to ascending. 12. IOPS. days. click a virtual machine name in the list. click the column label. 15. Objects related to a cluster If you need to review information on the number of hosts. select the time you want to refresh the performance information in intervals of 5. you can click the tab on the right to expand or contract the chart width. you can leave the default of 1 day (1d). From the Top Contributors field. You may want to review this information before you make changes to a host or remove it from a cluster. 13. Select the date range of performance you want to review from the preset links at the top right of the panel. From vSphere Web Client Home. or 1 year (1y). or years. Chapter 4: Clusters 43 . or failed). And. or virtual machines in a cluster. 8. You can also manually refresh the data by clicking the Refresh spinner icon ( icon. At Refresh Interval. If no data was collected for the selected time range. you can see details on the host name. you can toggle the value up or down to see 1-50 top contributors. For example. The Top Contributor list defaults to showing the top 10 virtual machines. Click a data point on the Throughput. and total read and write values for each virtual machine. 30 or 60 seconds. Virtual Controller name and state (alive or down). 7.5. datastores. 1 hour (1h). 10. Double-click the row with the cluster you need to access. It lists all the clusters in the federation. 3. From vSphere Web Client Home. From vSphere Web Client Home. size. Click Clusters to open the Objects tab. 2. (Or. You may want to review this information before you make changes to the datastore or remove it from a cluster. 5. 5. The application defaults to the Getting Started tab or the last tab you accessed. Double-click the row with the cluster you need to access. 4. 4. 3. View datastores related to a cluster Procedure overview You can view all the HPE SimpliVity datastores in a cluster. Chapter 4: Clusters 44 . creation time. you can see details on the datastore name. 4. Click Clusters to open the Objects tab. Click Related Objects. View virtual machines related to a cluster Procedure overview You can view a virtual machine inventory to see a list of all virtual machines in a cluster. 2.) You see a list of hosts in the cluster you selected. Scroll to the right to click the HPE SimpliVity Virtual Machines subtab. Scroll to the right of the subtabs and click HPE SimpliVity Datastores. Or. and vCenter Server IP address. Double-click the cluster you want to view. Intelligent Workload Optimizer HPE SimpliVity Intelligent Workload Optimizer (IWO) works with the vSphere Distributed Resource Scheduler™ (DRS) cluster feature. It makes load balancing of your CPU and memory resources more efficient and lowers latency by doing the following: • Collects the storage usage information of the virtual machines on each host in the cluster that uses a Hewlett Packard Enterprise datastore. 5. For example. Scroll to the right of the subtabs and click SimpliVity Hosts. click the down arrows and select HPE SimpliVity Datastores from the drop-down menu. click HPE SimpliVity Federation. Procedure 1. Click the Related Objects tab. click the down arrows and select Hewlett Packard Enterprise Hosts from the drop-down list. Procedure 1. click HPE SimpliVity Federation. You see a list of datastores in the cluster. assigned backup policy. Click the Related Objects tab. Intelligent Workload Optimizer requirements Intelligent Workload Optimizer (IWO) works with vSphere Distributed Resource Scheduler (DRS) to ensure efficient load balancing for the hosts.) • vSphere DRS is turned on for the cluster with the HPE OmniStack hosts. IWO includes the standard ESXi hosts that use a SimpliVity datastore in the DRS groups and rules. IWO requires the following conditions to start creating cluster groups and affinity rules in DRS: • HPE SimpliVity Intelligent Workload Optimizer feature is enabled (default). You can check the IWO setting through the Intelligent Workload Optimizer commands as described in the HPE OmniStack for vSphere Command Reference Guide. if you deploy an HPE OmniStack host to a cluster that contains other HPE OmniStack hosts. cluster host groups. IWO defaults to the setting used by the cluster. • Cluster must contain a minimum of three and a maximum of eight HPE OmniStack hosts. For example. DRS makes a best effort to optimize according to IWO settings. NOTE: When moving a host to a different cluster you must fully remove the host from the federation. outside the cluster. Intelligent Workload Optimizer best practices Before you move all your HPE OmniStack hosts into a cluster to use Intelligent Workload Optimizer (IWO) with vSphere Distributed Resource Scheduler (DRS). A one or two-host cluster automatically accesses data efficiently and does not need affinity rules. enable Enhanced vMotion Compatibility (EVC) to ensure CPU compatibility for vMotion. IWO is disabled in both the old and the new cluster. and affinity rules in DRS that bring the virtual machines closer to the host with the source virtual machine. or in other clusters. For more details on licenses. You can include up to eight HPE OmniStack hosts in cluster. But. review the following best practices: • Do not enable vSphere Distributed Power Management (DPM) to ensure that it cannot shut down the HPE OmniStack Virtual Controller on a host after load balancing occurs. Clusters with the HPE OmniStack hosts can also contain standard ESXi hosts. You can also include standard ESXi hosts as long as they share a Hewlett Packard Enterprise datastore with another HPE OmniStack host in the cluster. When you first deploy an HPE OmniStack host. For more details. then redeploy it to the new cluster. but they must use an HPE SimpliVity datastore by sharing it with another HPE OmniStack host in the cluster. • Datacenter contains all the HPE OmniStack hosts in one or more clusters. if you changed the setting from enabled to disabled.• Automatically creates cluster virtual machine groups. Chapter 4: Clusters 45 . A cluster must contain three HPE OmniStack hosts to start creating cluster groups and affinity rules in DRS. As long as the cluster has a minimum of three HPE OmniStack hosts. NOTE: If you plan to use vSphere DRS for a cluster of HPE OmniStack hosts. No HPE OmniStack hosts reside outside a cluster. (Standard ESXi hosts can reside in the same cluster. leave HPE SimpliVity Intelligent Workload Optimizer set to the default of enabled to ensure that virtual machines can access data efficiently. see the VMware Knowledge Base and search for the "Enhanced vMotion Compatibility (EVC) processor support" article. see the VMware documentation. • If the cluster contains hosts with different CPU generations. You must have an Enterprise or Enterprise Plus license to use vSphere DRS. the HPE OmniStack host joining the cluster takes on the disabled IWO setting. but in some high load environments DRS will ignore IWO. This can result in VMs being run on a node other than their primary or secondary storage nodes. If you simply move the host to a new cluster. the IWO setting defaults to enabled. (See the VMware vSphere documentation for details on hardware requirements. • Cluster can contain up to 800 virtual machines. For example." An HPE SimpliVity VM group name starts with svtv and an HPE SimpliVity host group starts with svth. and affinity rules in DRS. For example. host groups. the HPE SimpliVity virtual machine and host groups look like this in DRS: HPE SimpliVity rules start with svtr. For example.) About managing HPE SimpliVity groups and rules If a cluster uses Intelligent Workload Optimizer (IWO) with vSphere Distributed Resource Scheduler (DRS). a cluster with three HPE OmniStack hosts creates up to three SimpliVity host groups. server-based and VDI workloads) into separate datacenters. IWO adds it to the appropriate virtual machine group to improve the load balancing efficiency.• Separate workloads (for example. each host can run a workload of up to 100 virtual machines (approximately) • Minimum memory requirements depend on your vCenter Server configuration. You access the HPE SimpliVity groups and rules created by IWO as you would any group or rule in DRS (by right- clicking the vSphere cluster icon and clicking the Settings option). All the groups and rules created by IWO start with "svt. And. IWO updates the groups or rules by removing it. if you delete a virtual machine. and rules for those groups. if you create a virtual machine. Both are followed by the Global Unique Identifier (GUID) of the HPE OmniStack hosts or the standard ESXi host that shares an HPE SimpliVity datastore. IWO automatically creates HPE SimpliVity virtual machine groups. corresponding virtual machine groups. System events trigger when IWO creates HPE SimpliVity groups and rules. The number of groups and rules it creates depends on the number of hosts and virtual machines in the cluster. The groups use the same GUID of the hosts listed in the rule as shown in this example of HPE SimpliVity rules in DRS: Chapter 4: Clusters 46 . IWO creates Virtual Machines to Hosts affinity rules that use a "Should run on hosts in group" specification. These rules influence DRS so it can migrate virtual machines to the defined hosts. For example, if you need to review or edit a rule, you can see the field to set the specification between the VM Group and Host Group fields as shown: NOTE: If the cluster exceeds a vSphere-defined CPU or memory limit, DRS ignores the "Should run on hosts in group" rules list and uses a different load balancing calculation to prevent an overload. If using a different load balancing Chapter 4: Clusters 47 calculation does not prevent the overload, DRS can start to shut down virtual machines. To avoid an overload, do not exceed the maximum of 800 virtual machines that run a workload of 100 per HPE OmniStack host in a cluster. If you remove an HPE OmniStack host or a standard ESXi host that shares an HPE SimpliVity datastore from a cluster with four to eight HPE OmniStack hosts, vSphere DRS automatically removes the groups and rules that included that host. If that occurs, HPE OmniStack recognizes that a copy of the virtual machines no longer exists and makes a second copy of the data on an available host in the cluster. IWO then updates the groups and rules in DRS. You can override or remove HPE SimpliVity rules in DRS. But, you cannot rename HPE SimpliVity groups and rules. If you edit the name of a HPE SimpliVity group or rule, IWO recreates the group or rule with the original name. For details on overriding rules, see "Override HPE SimpliVity rules in DRS." To remove HPE SimpliVity groups and rules from DRS, see the HPE OmniStack for vSphere Command Reference Guide. Override HPE SimpliVity rules in DRS Intelligent Workload Optimizer (IWO) creates HPE SimpliVity groups and rules in DRS that use a "should run on" specification for the rules it creates. Procedure overview If you want the standard vSphere DRS rules to override the HPE SimpliVity rules, you can do the following in DRS: • Add the new rule you want to use for a cluster • Set the specification for the rule to Must run on hosts in group. For example, you may want the virtual machines to move to different hosts than what the HPE SimpliVity rules dictate. Procedure 1. From vSphere Web Client Home, click vCenter Inventory Lists or Global Inventory Lists (depending on your version of vSphere). 2. Under Resources, click Clusters to open the Objects tab. Click the cluster you need to modify and click Actions > Settings to open the Manage tab to the Settings subtab. (For vSphere 6.5, right click the cluster and click Settings to open the Configure tab.) 3. To check if DRS is turned on, click vSphere DRS under Services. 4. If you need to create new virtual machine or host groups, click VM/Host Groups under Configuration, click Add under VM/Host Groups, and enter the appropriate field information to add a new virtual machine or host group (or both). Then click OK. 5. Under Configuration, click VM/Host Rules. 6. Click Add under VM/Host Rules to create another DRS rule. 7. In the Name field, enter a name for the rule. Then select Enable Rule. 8. Select Virtual Machines to Hosts from the Type drop-down menu. 9. Select the virtual machine group from the VM Group drop-down list. 10. Select Must run on hosts in group from the drop-down list of the next field. If the "must" rules overload an HPE OmniStack host, DRS could power down virtual machines—including the Virtual Controller. Do not create groups that consist of more than 100 virtual machines per host to prevent an overload. Chapter 4: Clusters 48 11. Select the host group from the Host Group drop-down list. 12. Click OK. vSphere HA configuration for a cluster with HPE OmniStack hosts You use vSphere HA (High Availability) to ensure that CPU and memory resources on all systems in a cluster are reserved to support an HA environment. If one or more HPE OmniStack hosts in a cluster becomes unavailable, their virtual machines fail over to the available systems in the cluster. You need to reserve a percentage of CPU and memory resources on all systems to support virtual machine failover during an HA event. In the following example, an HPE OmniStack host, with a red X, in a cluster of four systems has become unavailable. Virtual machines have failed over from the unavailable system to the available systems in the cluster. vSphere guarantees that there is enough memory reserved on each of the available systems to serve the failed over virtual machines through the Admission Control Policy. NOTE: All systems in the cluster have the same memory configuration. Calculating the memory reservation for the Admission Control Policy Procedure overview When enabling vSphere HA (High Availability) on a cluster in vSphere Web Client, you configure the Admission Control Policy, which specifies the percentage of CPU and memory to reserve on all systems in the cluster to support HA. You can accept the default CPU percentage, but you need to calculate the memory percentage to include specific requirements. Procedure 1. Use the vSphere Web Client to collect the following memory information for the cluster where you want to enable vSphere HA: • Total memory capacity of the cluster: Chapter 4: Clusters 49 In the example screen, you click Hosts and Clusters in the vSphere Web Client inventory list, expand the datacenter, click the cluster icon, then select the Summary tab. The total memory capacity appears under Memory. In the example, the total memory capacity for the Netherlands_Cluster is 1023.57 GB (1048135.68 MB). • Memory reservation for the Virtual Controller. In the example screen, Netherlands_Cluster contains four OmniStack hosts. To access this information in vSphere Web Client, click Hosts and Clusters, expand the datacenter, click the cluster, and then click the Related Objects tab. To see the Virtual Controllers, click the Virtual Machines subtab. The reserved memory for the Virtual Controller in the example screen is 58,628 MB. 2. Use the following formula to calculate the percentage of cluster memory to reserve for the Admission Control Policy: For example: a. Multiply the memory reserved for the Virtual Controller by the total number of systems in the cluster to get the total cluster memory reserved for all Virtual Controllers. For example, 58,628 MB x 4 = 234512 MB. Chapter 4: Clusters 50 Under Services. For the value in F. Click Admission Control to open the failover capacity options. click vSphere HA or vSphere Availablity (depending on your version of vSphere). NOTE: Since the Virtual Controller does not fail over during an HA event. click Edit to open the Edit Cluster Settings dialog box. right-click the cluster icon that contains the OmniStack hosts. Enabling vSphere HA on a cluster Before you begin You have determined the memory reservation percentage to specify for the Admission Control Policy. 2. For example. If you need to turn it on. 1 / 4 = . 6. Divide the total available memory for the cluster by the total memory capacity for the cluster. 1048135. If on. Enter the memory percentage value that you calculated. For example. c. Divide 1 by the number of systems in the cluster. 5. Multiply the value from E by 100 to convert to a percentage. Multiply the value from C by the value from D.8 x . (For details on calculating memory. 7. 813623. 4. You now have the percentage of reserved memory to specify for the Admission Control Policy when enabling vSphere HA on a cluster. see "Calculating the Memory Reservation for the Admission Control Policy" topic. Chapter 4: Clusters 51 . . Click Settings to open the Manage or Configure tab (depending on your version of vSphere).) Do not change the default value for CPU. Procedure overview You enable vSphere HA (High Availability) on a cluster to allow virtual machine (VM) failover during an HA event. never round down. Then select Turn on vSphere HA and click OK. For example. In the inventory list in vSphere Web Client. Select Define failover capacity by reserving a percentage of cluster resources or Define failover capacity by Cluster resource percentage (depending on your version of vSphere) in the Admission Control panel. you see vSphere HA is Turned ON. 0.2 f. such as a system in the cluster becoming unavailable. Click OK to save the values and return to the Manage (or Configure) tab.68 MB /1048135.68 MB. to the next whole number. 8. b. Procedure 1. For example. always round up. Subtract the total cluster memory reserved for all Virtual Controllers from the total memory capacity for the cluster to get the total available memory for the cluster. 1 is the maximum number of HPE OmniStack hosts that the cluster can tolerate becoming unavailable. you need to subtract the memory reserved for all Virtual Controllers to determine the total available memory for the cluster.25 e.8% would round up to 19%.8 d.25 = .68 MB .234512 MB = 813623.2 x 100 = 20% NOTE: The Admission Control Policy requires whole percentage values only. 3.68 MB = 0. For example. 18. For example. This means that when a Virtual Controller goes down (for upgrade. About Stretched Clusters Prior to the Stretched Cluster functionality. You can set the time zone of a cluster to your local time through the svt-timezone-set CLI command. another one in the same datacenter takes over data services and allows all hosts to continue servicing virtual machines.m.m. a datacenter with two or more HPE OmniStack hosts would use the HPE SimpliVity Storage High Availability solution. For example. which are physically co-located collections of hosts that you define as being likely to fail together due to external forces. Cluster time zones The default Cluster Time Zone value is set to Coordinated Universal Time (UTC). all stretched cluster and availability zone management is done through the svt-zone command line commands in the HPE OmniStack for vSphere Command Reference Guide. For more information on the svt-timezone-set command. which is equivalent to 1 a. the vSphere HA agent installs automatically on each OmniStack host.m. PST (or 2 a.m. consider a cluster located in San Francisco (UTC/GMT -8 hours for Pacific Standard Time [PST] or -7 hours during Pacific Daylight Time [PDT]) in the summer). see the HPE OmniStack for vSphere Command Reference Guide. service. where service continues even with multiple HPE OmniStack host failures across a rack. (0900) to 6 p. or even an entire site. Chapter 4: Clusters 52 . Stretched clusters Stretched Clusters allow the creation of availability zones for more protection than standard HPE SimpliVity High Availability. you can expect the following behavior for policy backups: • Daily backups occur at midnight UTC. so applications will go down temporarily.m. NOTE: Currently. lab. NOTE: Virtual machines running in a failed zone are restarted in the other zone.m.m. PDT). the policy takes hourly backups from 9 a. When you set the cluster time zone. you will not lose access to data following the loss of a zone. Stretched clusters provide even more protection. it applies the same time setting across all HPE OmniStack hosts included in that federation cluster. (1800) UTC. or error). Assume that this cluster contains a policy with a rule that backs up a virtual machine hourly between the hours of 9:00 a. and 6:00 p. If the cluster has not previously used vSphere HA. A federation applies the cluster time to a backup policy. to 11 a. This is provided through the use of Availability Zones. the basis for the 24-hour time zone system. • Start and stop times specified in backup policy rules take effect at UTC. If you do not set the cluster time zone to your local time. and leveraging a third site arbiter. By configuring an equal number of hosts within two availability zones. to 10 a. If you do not set the time zone to (America/Los_Angeles). There is no support in the HPE SimpliVity Plug-in for vSphere Web Client.m. In this configuration. HPE OmniStack hosts in Zone1 fail due to a disastrous event. Virtual machines (vm1. and vm4) are deployed as depicted.About Availability Zones In the following figure. it becomes effective and does affect the running system. VMware HA will restart vm1 and vm2 on the surviving HPE OmniStack hosts of availability zone Zone2. the service continues to be provided even if one of the availability zones fails. This is demonstrated in the figure below. Configuration Modes There are two configuration modes that are used with availability zones: • Planned — Certain commands are used to change one host-zone assignment at a time. Planned zone assignments have no impact on the running system. because the HPE OmniStack hosts in the remaining availability zone will provide failover. As a result. Host1 and Host2 are assigned to availability zone Zone1. the realization of these changes needs to happen at the same time. configured within stretched cluster Cluster1. vm2. As you can see. There are two availability zones. As depicted. • Effective — When planned configuration for zoning is realized. you can see stretched cluster Cluster1 within the datacenter Datacenter1. vm3. and Host3 and Host4 are assigned to availability zone Zone2. Chapter 4: Clusters 53 . however. Zone1 and Zone2. When you remove an HPE OmniStack host from a federation. edit the appropriate rules in your policies and change the cluster from the one you want to delete to another cluster or delete the rule (if no longer needed). Otherwise. make sure that the network settings are appropriate. you can delete the Virtual Controller from disk. and deploy the OmniStack host. you can then remove the empty cluster using the vSphere Delete option. The process of removing a cluster does not check for active virtual machines and datastores. you cannot join it back into the same federation unless: • The host is in a healthy state and at an appropriate compatibility level to rejoin the federation. you can remove individual OmniStack hosts from a federation as described in Remove host from a federation on page 58 or by using the svt-federation-remove CLI command without the cluster option. In this case. Any data associated with active virtual machines is permanently deleted. If you remove all the hosts in the cluster. NOTE: If your policies include rules that specify the cluster you want to delete. contact Customer Support. see the HPE OmniStack for vSphere Deployment Guide. you can remove all the unhealthy hosts from that cluster at once by using the svt-federation-removeCLI command with the datacenter and cluster options as described in the HPE OmniStack for vSphere Command Reference Guide.Cluster removal If there are no healthy HPE OmniStack hosts in a cluster. you may see an "unknown failure domain" message in your log files. Chapter 4: Clusters 54 . For information on deploying an HPE OmniStack host. To avoid this. For information on restoring a host to the factory defaults. • The host was restored to factory defaults and re-deployed as a new HPE OmniStack host in the Federation. For details on deploying hosts.Chapter 5: Hosts This section contains the following topics: • HPE OmniStack hosts • Host deployment • View a host in a cluster • View host summary details • View host hardware details • Remove a host from a Federation • Start up an HPE OmniStack host • Shut down one or more Virtual Controllers HPE OmniStack hosts An HPE OmniStack host has a dedicated virtual machine called the Virtual Controller. For example. The objects associated with the HPE OmniStack hosts appear in vSphere Web Client under an HPE SimpliVity federation. and share data. Adding an HPE OmniStack host to a federation increases the resources available to virtual machines and does not disrupt virtual machine availability or service levels. manage. You can also remove an HPE OmniStack host from the federation at any time. The objects include clusters. this can decrease the resources available to virtual machines. datastores. But. see the HPE OmniStack for vSphere Deployment Guide. In vSphere Web Client. and virtual machines. You can add or replace HPE OmniStack hosts without causing: • Downtime for local or remote sites • Disruption to local or remote backups • Modifications to backup policies for local or remote sites • Changes to IP addresses in remote sites Chapter 5: Hosts 55 . Host deployment You add an HPE OmniStack host to a federation by deploying it through Deployment Manager as described in the HPE OmniStack for vSphere Deployment Guide. unlike traditional ESXi hosts. If an HPE OmniStack host fails or you need to temporarily swap it out for hardware upgrades. The Virtual Controller runs the HPE OmniStack software. But. hosts. each host has HPE SimpliVity technology that uses deduplication and compression to efficiently store. An HPE SimpliVity federation uses at least two HPE OmniStack hosts to ensure high availability. HPE OmniStack hosts appear as ESXi hosts. you reduce the data protection and resource redundancy—especially when you cannot create remote backups. if you remove an HPE OmniStack host from a federation and leave only one HPE OmniStack host. backup policies. you can replace it with another HPE OmniStack host. • Verify that the network is functioning correctly by selecting the cluster from the list of datacenters under datacenter Objects tab. cluster where it resides. suspected. Click Clusters to open the Objects tab. unknown (host not found. HPE OmniStack version (appears Mixed during an upgrade). warning (operation errors or failover). Procedure 1. You can also access tabs to view summary information. choose the least busy work time to add an HPE OmniStack host. critical error. or failover).NOTE: If any of the HPE OmniStack hosts in the federation are not available (offline) when you add a new host. manage alarms and search backups. or error (stopped functioning). Virtual Controller shutdown status. From vSphere Web Client Home. For example. View a host in a cluster Procedure overview You can view HPE OmniStack hosts in a cluster and access tabs to view HPE SimpliVity details on it. 2. When adding (or deploying) HPE OmniStack hosts to a cluster: • A system must be new (newly received from Hewlett Packard Enterprise or its partners) or restored (restored to factory default settings) before you can add it to a federation. Or. In a federation with many HPE SimpliVity datastores. or removed). click the double down arrows and scroll down to HPE SimpliVity Virtual Machines. serial number. Storage and Federation network IP addresses. NOTE: To view Hewlett Packard Enterprise virtual machines for a host. and hardware status. View host summary details Procedure overview You can view the summary information about a host and access the HPE SimpliVity portlet details. Configured systems (such as those with backup policies or configured mail servers) cannot join the federation. you can see details about the host model. and clicking the HPE SimpliVity Hosts subtab to review the state of the objects. this delay may last for many seconds or even minutes. 4. Virtual Controller name and state (alive. Then scroll to the right to click the HPE SimpliVity Hosts subtab. Procedure Chapter 5: Hosts 56 . and access HPE SimpliVity virtual machines. Federation IP address. the creation of mount points and NFS exports gets delayed until the resources hosted by the unavailable host fail over. managed. faulty. Management. and upgrade status. you can see the host name (IP address). • To avoid resource conflicts. The status can appear as: healthy. HPE OmniStack software version. 3. For example. click HPE SimpliVity Federation. datacenter name. Double-click the row with the cluster that contains the hosts you want to view. select the host and click the HPE SimpliVity Virtual Machines subtab. monitor the data capacity. Click the Related Objects or More Objects tab (depending on your version of vSphere). clicking the Related Objects tab. licensing. model. see the VMWare vSphere documentation. Click Hosts to open the Objects tab. You see a summary of the host hardware. fault tolerance. vendor. Fault Tolerance. But if the life value falls below 10% or shows as "Warn. click HPE SimpliVity Federation. related objects. Double-click the row with the host you want to view. For example. NOTE: For details on the Hardware. and hardware status. you may see a status that shows the percentage of life left or a label of Healthy. For example. Depending on the model of the drive. 2. serial number. Click Hosts to open the Objects tab." you see a message to replace it now and you can no longer write to it. it has a lot of use left. 5. critical error. HPE OmniStack software version. and the Hewlett Packard Enterprise portlet. configuration. For details on replacing a drive. Warning. or failover) For a solid-state drive (SSD). see the Hardware Installation and Maintenance Guide for your platform. From vSphere Web Client Home. 2. you can see details about the host components (HPE OmniStack Accelerator and storage adapter). Procedure 1. Optional: To see more details on the hardware. Configuration. or Critical. 3. If the life value falls below 5% or shows as "Critical. click HPE SimpliVity Federation. 4. click Hardware Information. and Tags portlets.1. View host hardware details Procedure overview You can view details on the hardware inventory for an HPE OmniStack host. Click the Summary tab. tags." you see a message in the Alarms portlet to order a new drive to replace it. you also see details on the life remaining in the Status column. The status can appear as one of the following: • Healthy • Initializing • Rebuilding (after replacing a solid-state drive [SSD] or hard disk drive [HDD]) • Warning (operation errors or failover) • Degraded (functioning at reduced level) • Enabled (on) or Disabled (off) • Missing • Offline • Failed • Unconfigured • Unknown (host not found. if the drive shows 90% or a "Healthy" life status. Chapter 5: Hosts 57 . From vSphere Web Client Home. if you use vSphere Distributed Resource Scheduler (DRS) and HPE SimpliVity Intelligent Workload Optimizer. 3. Depending on the circumstances. the host still exists in vCenter Server. Before you begin Before you begin: • Verify that standard ESXi hosts are not sharing the datastore used by the HPE OmniStack host that you want to remove. Procedure overview NOTE: You can redeploy an HPE OmniStack host back into the same federation as long as a cluster in the federation contains at least one other HPE OmniStack host. click the Monitor tab. From vSphere Web Client Home. However. If you need to remove a host from a federation. the removed host no longer appears in any HPE SimpliVity (svt) groups or rules in DRS. you need to reset the boot drive on the host you removed. Remove host from a federation You can remove an HPE OmniStack host from a federation at any time. you may want to remove it to redeploy it within the same federation or a different one. However. If you want to keep sharing the datastore. Procedure 1. Or. you must change the /etc/hosts file for every standard ESXi host so that it references a different HPE OmniStack host in the same federation datacenter. For example. and then click the HPE SimpliVity Hardware subtab to access the hardware details. Right-click the host you want to view and select All HPE SimpliVity Actions > View Hardware. • Verify that all HPE OmniStack hosts in the federation are in a healthy state and all virtual machines are storage HA compliant (synchronized). if you click Hosts and Clusters from the vSphere Web Client Home tab. Chapter 5: Hosts 58 . NOTE: You can also double-click the row with the host you want to view. it still exists in vCenter Server.3. • When you remove an HPE OmniStack host from the federation. Click Hosts to open the Objects tab. To redeploy an HPE OmniStack host to the same federation or a different one. Remove a host from a Federation Host removal You may want to permanently remove an HPE OmniStack host from a federation if you do not need it. • Move the virtual machines from the host you want to remove to an available HPE OmniStack host. you may want to remove it permanently or redeploy it within the same federation or a different one. you see the host listed under a cluster object. 2. Right-click the row with the HPE OmniStack host you want to remove and click All HPE SimpliVity Actions > Remove from federation. For more information on changing the /etc/hosts file. you cannot see it in the federation again unless you redeploy it. You can then use HPE OmniStack Deployment Manager to redeploy it to the appropriate federation. see the VMware vSphere Help. click HPE SimpliVity Federation. 7. If you want to redeploy the HPE OmniStack host (for CN-series platform). 5. 8. see the Hardware Installation and Maintenance Guide for your platform. For details on deploying Cisco UCS or Lenovo platforms. Click Yes. In the Hewlett Packard Enterprise Installer screen. Chapter 5: Hosts 59 . deallocate the IP addresses assigned to the host using the svt-ippool-deallocate command. it could result in data loss if the virtual machines moving to another host are not in storage HA (High Availability) compliance. select Reset System (warm boot). For more information. In the Power menu. To view the IP addresses assigned to an HPE OmniStack host. this option forces them to fail over to available HPE OmniStack hosts in the federation. 3. follow the steps to reset the boot before you redeploy it. see the Hardware Installation and Maintenance Guide for your platform. Click OK in the Next Boot message. use the svt-ip-assignments- show command. Procedure 1. For more information. 2. 2. you can reset the boot drive. 6. This returns the IP addresses to the HPE OmniStack IP address pools and ensures that the IP addresses are available for future deployments. NOTE: This procedure resets the boot drive on a removed HPE OmniStack host to redeploy it. select BIOS Boot Manager from the Next Boot menu. This displays the HPE SimpliVity Installer screen. see the Hardware Installation and Maintenance Guide for your platform and the HPE OmniStack for vSphere Deployment Guide. Configure the remote Web-based management interface for your platform. If virtual machines remain on the host. 9.4. Reset the boot drive Before you begin Perform these tasks before you reset the boot drive on an HPE OmniStack host: 1. However. If you deployed the HPE OmniStack host with IP addresses allocated in HPE OmniStack IP address pools. Resetting the boot drive allows you to redeploy the host within the same federation or a different one. Deallocating IP addresses in use by another HPE OmniStack host may cause the federation to stop working properly and virtual machine data may be unavailable. Click Yes again to confirm that you want to remove the HPE OmniStack host from the federation. For details on what to do before deploying Cisco UCS or Lenovo platforms. Optional: Select Force removal (may cause data loss) to force the removal process if the host is unresponsive. Connect an Ethernet cable from the Windows computer to the Ethernet management port on the rear of the HPE OmniStack host. Remove the IP addresses assigned to the HPE OmniStack host using the svt-ippool-remove command. Connect to the remote Web-based management interface and launch the Virtual Console. Procedure overview Once you remove an HPE OmniStack host from a federation. 3. see the HPE OmniStack Command Reference. Ensure that you deallocate IP addresses on the correct host. Chapter 5: Hosts 60 . NOTE: If you temporarily changed any tasks to facilitate the shutdown. click the Related Objects or More Objects tab (depending on your version of vSphere).) 5. Do one of the following to power on the HPE OmniStack host: • Use your remote management IPMI (Intelligent Platform Management Interface) system to access the Power option. Log in to vCenter Server through vSphere Web Client. If you previously shut down the computer with vCenter Server. 4. use Windows services (services. NOTE: If SD Card: Internal Dual SD does not appear in the BIOS Boot Menu screen. Start up an HPE OmniStack host Procedure overview If you previously shut down an HPE OmniStack host. Procedure 1.com/support/hpesc). and then click the HPE SimpliVity Hosts subtab. power on the virtual machines manually. Wait for the Virtual Controller to power on. make sure that the host is in the same physical state and that no cables were disconnected or devices removed. Select SD Card: Internal Dual SD and press Enter. 3. You can see the state of the Virtual Controller for each OmniStack host in the cluster (for example. Enter your BIOS password. If you need to start it. reconfigure these tasks for normal operation. The HPE OmniStack host reboots and receives a new IP address. select BIOS Boot Menu. 6. • Manually press the Power button of the physical hardware in the datacenter. Do not proceed until all HPE OmniStack hosts are responding and there are no unacknowledged alarms or errors.4. Verify the federation status through the cluster in vSphere Web Client. (The Virtual Controller should automatically power on before any guest virtual machines. 2. you can redeploy it using Deployment Manager.msc) to access Arbiter through the Extended tab to start it. For more information on deploying an HPE OmniStack host. Click OK in the Power Control message. 9. In the GNU GRUB screen. Alive). verify that the Arbiter service started. 5. Otherwise. for example on Windows Server.hpe. In the Boot Manager Main Menu. click Clusters. Once you reset the boot drive on the host you removed. use the arrow key to select Deploy and press Enter. 7. Wait for all the virtual machines to power on (if set to power on automatically). For example. click HPE SimpliVity Federation from the Home tab. double-click a cluster. Select * Hard drive C: to open the device selection menu. see the HPE OmniStack for vSphere Deployment Guide. 8. contact Customer Support (http://www. 6. if prompted. Right-click the row with the HPE OmniStack host you want to shut down and click All HPE SimpliVity Actions > Shut Down Virtual Controller. and shut down the Virtual Controller on each host using HPE SimpliVity options. Chapter 5: Hosts 61 . Click Yes to confirm the shut down of the Virtual Controller on the host. Click Yes when prompted to confirm the forced shutdown to avoid the HA compliance check and continue the shutdown. 6. 7. Then right-click the row with the next HPE OmniStack host you want to shut down and click All HPE SimpliVity Actions > Force Virtual Controller Shut Down. 2. Power off all the guest virtual machines on the host you want to shut down using the vSphere Shut Down Guest and Power Off options. shut down all the guest virtual machines on the hosts (or move them off the host). Before you begin Before you shut down a Virtual Controller on an HPE OmniStack host: • Verify there are no pending tasks. From vSphere Web Client Home. Procedure 1. • Ensure that the virtual machines are in HA compliance. repeat steps 1-3. But. 4. Force Virtual Controller Shut Down Forces the Virtual Controller to shut down at any time during the task before it achieves HA compliance. do not shut down the Virtual Controller. use the HPE SimpliVity Move Virtual Machines option after shutting them down. If you do not want to shut down the virtual machines to move them. use vSphere vMotion or vSphere Storage vMotion options as described in the VMware documentation. NOTE: If you want to move the virtual machines. You can make data unavailable by forcing a Virtual Controller to shut down. Optional: If you want to continue to shut down more hosts in the Federation. Click Hosts to open the Objects tab. you select one of the following options from the All HPE SimpliVity Actions menu: Option Description Cancel Virtual Controller Shut Down Cancels the shut down at any point before the completion of the task (before HA compliance). 5. you need to first ensure the virtual machines are in HA compliance. click HPE SimpliVity Federation. Optional: If the virtual machines are taking too long to reach storage HA compliance and you want to stop the shutdown or force it to continue.Shut down one or more Virtual Controllers To safely shut down HPE OmniStack hosts. 3. • Copy files to (or create files in) the root directory of a datastore. For example. The new policy acts as the default backup policy for the datastore. An HPE SimpliVity datastore has the following attributes: • Name • Default backup policy for new virtual machines created in the datastore • Size Some vSphere Web Client options can prevent the datastore from functioning properly. Do not use this datastore for virtual machines or attempt to modify it or you could cause the HPE OmniStack host to fail or not function correctly. You can use other vSphere Web Client options to complete certain tasks (such as Power On and Reboot) if the HPE SimpliVity documentation directs you to use them. Create a datastore Before you begin Create a backup policy if you do not have any for the datastore. When the datastore has more backup policies. It is not the default policy if you created at least one other backup Chapter 6: Datastores 62 . NOTE: When you first create a datastore. You must create a folder or use an existing folder. • Unmount an HPE SimpliVity datastore. HPE OmniStack automatically creates an empty backup policy called Fixed Default Backup Policy.Chapter 6: Datastores This section contains the following topics: • HPE SimpliVity datastores • Create a datastore • View datastore summary details • Share SimpliVity datastores with standard ESXi hosts • Access to datastores for standard ESXi hosts in a federation • Resize a datastore • Delete a datastore HPE SimpliVity datastores HPE SimpliVity datastores provide resources to virtual machines that HPE OmniStack hosts and standard hosts can access. NOTE: An HPE OmniStack host contains a small local datastore initially named datastore-<serial number of OmniStack> that contains the Virtual Controller. You cannot change it. you can select another one (if necessary). do not perform the following tasks: • Move HPE OmniStack hosts between datacenters using the drag and drop method. monitor the data capacity. Do not use this datastore for virtual machines or attempt to modify it or the HPE OmniStack host could fail to function correctly. The list includes names of the datacenter and vCenter Server where the cluster resides. In the Size field. specify the datastore size (1 GB to 1. The application assigns that policy to new virtual machines created in the datastore. For example. Do not use the following special characters in the datastore name: /. select the backup policy for the datastore from the drop-down list. Click Datastores. Procedure overview You need to create at least one datastore for each cluster to hold virtual machine files. This opens a list of datastores in the federation. \. Caution: An HPE OmniStack host contains a small local datastore initially named "datastore-<serial number of OmniStack host>" that contains the Virtual Controller.024 TB) and select the unit of measurement (GB or TB).policy in the Federation before creating the datastore. manage alarms and search backups. Select the cluster where you want the datastore to reside from the Cluster drop-down list. [. Enter a unique name for the datastore in the New Datastore Name field (up to 42 characters). For example. Procedure 1. You can access tabs to view HPE SimpliVity details on any datastore in a federation. In the Backup Policy field. NOTE: You can also click Datastores to open the Objects tab and click the Create Datastore icon ( ). and free capacity. ]. 2. You can create more backup policies at any time and change the policy that the datastore uses. you can see details on the default backup policy. click HPE SimpliVity Federation. You see the new datastore appear in the Objects tab list. you can access tabs to view summary information. stored capacity. Click OK. click Create Datastore from the Basic Tasks section. Chapter 6: Datastores 63 . %. 5. View datastore summary details Procedure overview You can access HPE SimpliVity datastores in a federation and review summary information about an individual datastore from the Summary tab. From vSphere Web Client Home. Procedure 1. 4. 7. and access Hewlett Packard Enterprise virtual machines. 6. 3. From the Hewlett Packard Enterprise Home tab. click HPE SimpliVity Federation. This opens the Create Datastore dialog box. From vSphere Web Client Home. 2. NOTE: Click Create to create a new backup policy and add one or more rules. Unique names makes it easier to select the correct datastore when performing specific tasks or when managing multiple vCenter Servers in Linked Mode. See the following sections for details on each task. For example.3. you must know the network IP address of the HPE OmniStack host you plan to use to share the datastore. (If you use vSphere 6. Configure advanced settings on the standard ESXi host.5. you also see Related Objects and Custom Attributes portlets. NOTE: For details on using vSphere vMotion and vSphere Storage vMotion to migrate virtual machines off a standard ESXi host. Chapter 6: Datastores 64 . click Change Policy. For example: • If you use the switched method for the 10 GbE storage network. 2. Hewlett Packard Enterprise recommends you use this network because it provides higher bandwidth and failover capability. When you allow your standard ESXi host access to an HPE SimpliVity datastore. Double-click the name of the datastore you want to view. Share SimpliVity datastores with standard ESXi hosts HPE SimpliVity datastores and standard ESXi hosts You can share HPE SimpliVity datastores with standard ESXi hosts. • Use vSphere Storage vMotion to migrate virtual machines to a federation datastore with no disruption to users. Optional: To change the policy used by the datastore. the HPE OmniStack host provides two potential paths: • Storage Network IP address (recommended for failover) • Management Network IP address Your network also impacts the IP address you use. Task order To allow a standard ESXi host access to an HPE SimpliVity datastore. Determine the IP address to use for standard ESXi host storage traffic Procedure overview You need to specify the data transfer IP address that you want to use for the standard ESXi host storage traffic. 3. see the VMware vSphere documentation.) 5. you must complete the following tasks in this order: 1. Click the Summary tab. and a SimpliVity portlet. Tags. Determine the IP address for the storage traffic. Enable SimpliVity datastore sharing. The Summary tab has Details. To do this. use the Storage Network IP address of the HPE OmniStack host. you can: • Use vSphere vMotion to migrate virtual machines that run on a standard ESXi host to another host in the federation with no disruption to users. This section describes the required configuration NET and NFS settings for standard ESXi hosts. Modify the /etc/hosts file on the standard ESXi host. 4. 4. click HPE SimpliVity Federation. this network has no failover capability. From vSphere Web Client Home.• If you use the direct-connect method for the 10 GbE storage network. From the Advanced System Settings table. click Hosts. Procedure 1. click vCenter Inventory Lists or Global Inventory Lists (depending on your version of vSphere). Right-click the standard ESXi host you want include and select Settings. and click OK: • Net.5 hosts. From vSphere Web Client Home. Chapter 6: Datastores 65 . Configure advanced settings on a standard ESXi host Procedure overview To enable standard ESXi host access to a federation datastore. 3. NOTE: The standard ESXi host can reside in the same cluster as the HPE OmniStack host and datastore you plan to use or in another cluster within the same datacenter. click Advanced System Settings. change the value.MaxVolumes = 256 • SunRPC. Under System. 4. change the following settings to the values shown (one at a time). 2. 5. you must configure some advanced settings.MaxQueueDepth = 128 NOTE: These changes apply to ESXi 6.MaxConnPerIP = 128 • NFS.TcpipHeapSize = 32 • NFS. 3. However. Click Hosts in the navigation menu to view all the hosts in the Hewlett Packard Enterprise federation. You can view the management and storage network IP addresses in the table under the Mgmt IP and Storage IP columns. Configure the NET and NFS settings as described in "Configure advanced settings on a standard ESXi host. see the network information in the Hardware Installation and Maintenance Guide for your platform or the HPE OmniStack for vSphere Deployment Guide.TcpipHeapMax = 1536 • Net. Procedure 1. select the item from the Name column. To change the value. specify the Management Network IP address of the HPE OmniStack host. click the pencil icon ( ) or Edit (depending on your version of vSphere). Under Resources." Next steps For more information on defining the IP addresses for a federation.0 or 6. 2. You need to enter this address when you edit the host file for the standard ESXi host (located in /etc/hosts) as described in the "Edit the host file for standard ESXi hosts" topic. Write down the management or storage network IP address of the HPE OmniStack host that you plan to use to share the datastore. 4. . you cannot disable datastore sharing.nnn... Click OK. 2.) 4. Edit the host file for standard ESXi hosts Procedure overview After you determine the IP address for storage traffic and configure the advanced settings. (If you see a virtual machine count for the host. NOTE: If you misconfigure the host file. Check that you entered the IP address correctly if you see this error. Chapter 6: Datastores 66 .cube... 3. Do one of the following: • To allow the hosts to share data with a Hewlett Packard Enterprise datastore.. Restart the standard ESXi host to apply the changes. configure the NET and NFS settings. However. you can enable datastore sharing for the appropriate standard ESXi host through the HPE SimpliVity datastore object.. you cannot disable sharing for standard ESXi hosts with virtual machines... Do not restart the standard ESXi host. Enable or disable HPE SimpliVity datastore sharing Procedure overview After you determine the IP address for storage traffic. • To prevent hosts from sharing data with an HPE SimpliVity datastore...nnn.io where nnn. select the checkbox next to the appropriate host in the Shared column.nnn.. and edit the host file... NOTE: You can also disable datastore sharing.nnn is the storage or management IP address you previously documented.nnn.. you see the following error when you attempt to enable datastore access: .. you can edit the host file. 2. Edit the /etc/hosts file to include a line similar to the following: nnn. Continue to the Enabling or Disabling HPE SimpliVity Datastore Sharing" procedure to enable (or disable) sharing.nnn omni... Procedure 1.. Browse to HPE SimpliVity Federation > Datastores.6. clear the checkbox next to the appropriate hosts.ERROR [26]: Platform integration exception. Right-click the datastore you want to share and click All HPE SimpliVity Actions > Manage Standard ESXi Hosts to open the Manage Standard ESXi Hosts dialog box. Procedure 1. Access to datastores for standard ESXi hosts in a federation A standard host can exist in your vCenter Server environment in addition to HPE OmniStack hosts. (A standard host is any host that is not a HPE SimpliVity HPE OmniStack host.) If your vCenter contains such ESXi hosts, you can enable them to access the federation datastores. This allows you to use VMware vSphere vMotion and Storage vMotion to migrate virtual machines running on a standard host to another host in the federation with no disruption to users (as long as the virtual machine guest operating system is supported by HPE SimpliVity). If your cluster includes standard hosts that use HPE SimpliVity datastores, you can manually install the HPE SimpliVity vStorage API for Array Integration (VAAI)-Network Attached Storage (NAS) plug-in on those hosts. The plug-in improves performance and frees up memory when cloning virtual machines. Resize a datastore Procedure overview You may want to change the storage capacity of your federation datastore to accommodate the amount of data you need to store. When you resize a federation datastore, the virtual machines can remain running. Do not resize a datastore unless all of the HPE OmniStack hosts that use that datastore are in a healthy state. When you attempt to resize a datastore with one or more faulty HPE OmniStack hosts, the operation cannot complete Procedure 1. From vSphere Web Client Home, click HPE SimpliVity Federation. 2. Click Datastores to open the Objects tab. 3. Right-click the datastore you want to resize and click All HPE SimpliVity Actions > Online Resize. The Resize Datastore dialog box opens listing the datastore name, amount of space used, and the current capacity. 4. In the New Capacity field, enter a value larger or smaller than the current value (1 GB to 1024 TB). Then select the unit of measurement (GB or TB). NOTE: You cannot set the datastore size to a value that is less than the logical space needed for the existing virtual machines. For example, if the Used field shows a size of 150 GB, you cannot set the New Capacity to 100 GB. 5. Click OK. Delete a datastore Procedure overview When you delete a federation datastore, migrate or remove the virtual machines before you delete the datastore they use. You can also use the HPE SimpliVity Move Virtual Machine option to move a virtual machine to another cluster or datastore. You do not have to delete the virtual machine backups before you migrate or remove the virtual machine. Chapter 6: Datastores 67 If the Management network for a host is disconnected, you cannot delete the datastore. After you reconnect the network or it comes back up on its own, you can successfully delete the datastore. For more details on checking the Management network status, click Hosts from the vSphere Web Client inventory panel, double-click the host you want to check, click the Manage tab, and then the Networking subtab. NOTE: If you use the vSphere High Availability (HA) cluster option with datastore heart-beating, vSphere can put a heartbeat file on any datastore. The heartbeat monitors hosts and virtual machines when the management network fails. If you attempt to delete a cluster datastore with the heartbeat file, HPE SimpliVity cannot delete it and you see a vSphere Web Client "platform integration exception" error. You must select another datastore through the vSphere HA Datastore Heartbeating setting or disable vSphere HA to delete the datastore. For more information on using vSphere HA, see the VMware documentation. Procedure 1. From vSphere Web Client Home, click HPE SimpliVity Federation. 2. Click Datastores to open the Objects tab. 3. Right-click the datastore you want to delete and click All HPE SimpliVity Actions > Delete Datastore. 4. Click Yes to confirm that you want to delete the datastore and remove all associated data. It might take several seconds to update the datastore and storage space information, but the storage space is available immediately. Chapter 6: Datastores 68 Chapter 7: Virtual machines This section contains the following topics: • HPE SimpliVity virtual machines • Create virtual machines • View virtual machine performance • View virtual machine summary details • View virtual machines associated with a host or datastore • Clone virtual machines • Move virtual machines • Move virtual machines (experimental) • Save credentials for VSS • Format the NTFS Volumes on Virtual Machines • Register virtual machines after an HPE OmniStack power failure • Delete virtual machines HPE SimpliVity virtual machines When virtual machines run on an HPE OmniStack host and use an HPE SimpliVity datastore, you can use HPE SimpliVity options to clone or move virtual machines from one cluster or datastore and set the backup policy for them. You use vSphere Web Client options to create HPE SimpliVity virtual machines. Some known VMware limitations are: • After cloning or moving a virtual machine or restoring an HPE SimpliVity virtual machine backup between different datastores, the cloned, moved, or restored virtual machine appears to be attached to both datastores. (You can observe the two datastores for a virtual machine through the Related Objects portlet in the virtual machine Summary tab.) When you power on the cloned, moved, or restored virtual machine, the duplicate datastore issue resolves itself. • You can create a virtual machine with a fixed MAC address. However, if you perform a clone, move, or restore backup operation on a virtual machine with a fixed MAC address, the cloned, moved, or restored virtual machine has a duplicate MAC address. For more information, see "Changing the MAC address of a hosted virtual machine" in the VMware Knowledge Base. For details on vSphere Web Client options, see the VMware vSphere documentation. Create virtual machines In an HPE SimpliVity federation, you must specify a datastore to contain virtual machines. You create a virtual machine through the New Virtual Machine wizard in vSphere Web Client. For example, you can right-click the HPE OmniStack host in the federation and select New Virtual Machine from the list of Web Client options. Once created, you can use HPE SimpliVity options to backup, clone, or move a virtual machine in a federation. (For details on vSphere Web Client options, see the vSphere Web Client documentation.) Chapter 7: Virtual machines 69 • Know what datastore you want to specify for the virtual machine.Before you begin To ensure that you can create a virtual machine in a federation. Click Hosts to open the Objects tab. right-click the virtual machine. Click Virtual Machines. Watch for the virtual machine creation messages in the Recent Tasks panel. you may need to enter the guest operating system or virtual machine version. select All HPE SimpliVity Actions > Set Backup Policy. Click Finish when you complete the creation process. For example. From vSphere Web Client Home. Click Next. 3. If you need to use a different policy. View virtual machine performance You can access HPE SimpliVity virtual machines in a federation and review performance information about an individual virtual machine from the Monitor tab. 7. 2. Procedure 1. and select another policy from the Backup Policy drop-down list. For example. This can impact the availability of all the datastores in a federation. 6. Right-click the HPE OmniStack host where you want to add the virtual machine and select New Virtual Machine or New Virtual Machine > New Virtual Machine (depending on your version of vSphere). NOTE: Avoid placing the virtual machine in the datastore that contains the Virtual Controller because it can cause the datastore hosting the Virtual Controller to run out of space. Chapter 7: Virtual machines 70 . 5. click HPE SimpliVity Federation. 3. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. Procedure 1. 2. Right-click the virtual machine you want to view and click All HPE SimpliVity Actions > View Performance. From vSphere Web Client Home. 8. depending on the type of configuration you choose. Select the creation type. click HPE SimpliVity Federation. Check that the datastore default backup policy is adequate for the virtual machine. • Have a naming strategy in place to identify the virtual machines in the application easily. verify that you: • Have appropriate privileges to create a typical or custom virtual machine as described in the vSphere Virtual Machine Administration guide. Allocate space privilege on the destination datastore. 4. you must have the Datastore. Follow the prompts to select the remaining items and click Next. Then click Edit settings to open the first prompts in the wizard to enter a name and location. 2. and the name of the assigned backup policy. For example. Double-click the HPE OmniStack host or datastore you want to view. For vSphere 6. storage HA status. For vSphere 6. memory available. click HPE SimpliVity Federation. NOTE: You can also double-click the name of the virtual machine. you can see the virtual machine name. Clone virtual machines You can create a copy of an HPE SimpliVity virtual machine. The Summary tab has a collection of portlets. From vSphere Web Client Home. View virtual machine summary details You can access HPE SimpliVity virtual machines in a federation and review summary information about an individual virtual machine from the Summary tab. application-aware status (to use Microsoft Volume Shadow Copy Service [VSS]). you can see details on the available CPUs. 5.0. Click Virtual Machines. provisioned disk space. used and total capacity. storage HA status. For example. Procedure Chapter 7: Virtual machines 71 . 4. The cloned virutal machine aquires the policy assigned to the datastore. Procedure 1. click Monitor Performance. Optional: To see the performance values for the virtual machine. The HPE SimpliVity virtual machine summary information appears at the bottom of the tab. Procedure 1. 3. and latency. number of virtual hard disks. NOTE: You can also access HPE SimpliVity objects through the inventory panel by clicking vCenter Home and clicking on an item listed under the HPE SimpliVity section at the bottom of the panel. From vSphere Web Client Home. if necessary. Double-click the virtual machine you want to view. IOPS. 2. View virtual machines associated with a host or datastore You can view details on the virtual machines that reside on a particular host or datastore. datastore and cluster names. and click the HPE SimpliVity Performance subtab. You see the HPE SimpliVity Performance subtab open with a chart that shows the read and write values for the throughput. assigned backup policy.5. click the Related Topics tab and then the SimpliVity Virtual Machines subtab. used disk space. click HPE SimpliVity Federation. and vCenter Server IP address. 4. click the Monitor tab (if necessary). You can change the policy later through the Set Backup Policy option. Click the Summary tab. 3. click SimpliVity Virtual Machines Objects. Click Hosts or Datastores. backup policy. For more information on these features. From vSphere Web Client Home. for example. click Refresh ( ). click the information icon. Before you begin Use the vSphere Shut Down Guest option and then power off the virtual machine. the virtual machine must have a Windows Server 2008 R2. In addition. the only supported VSS-aware application is SQL Server 2012 R2 or later. click HPE SimpliVity Federation. Click Virtual Machines. Click Finish. The Clone Virtual Machine wizard opens with the current virtual machine name. In the Clone virtual machine name field. Chapter 7: Virtual machines 72 . click HPE SimpliVity Federation. NOTE: If you do not see the cloned virtual machine in the list of objects after the task completes.) To see more details on the other objects used by the virtual machine. see the VMware vSphere documentation. NOTE: For the clone process to use VSS. the process uses the default method of VMware snapshot to create the clone of the original virtual machine data. 2. Click Virtual Machines. If you select Application Consistent. select Microsoft VSS (Volume Shadow Copy Service). 2. leave the automatically generated name for the cloned virtual machine or enter a new name. Click Next. You can use the vSphere move options while the virtual machines remain powered on. Move virtual machines You may want to move an HPE SimpliVity virtual machine from one datastore to another. 6. 5. (The generated name consists of the original name with current date and time appended to it. Leave Crash consistent selected to create the clone from this type of backup (appropriate for virtual machines with nondatabase applications) or select Application Consistent to create the clone from an application-consistent backup (appropriate for virtual machines with database applications). 7. NOTE: You do not need to use the Shut Down Guest and Power Off vSphere options to use the vSphere vMotion or vSphere Storage vMotion options with virtual machines. Right-click the virtual machine you want to clone and click All HPE SimpliVity Actions > Clone Virtual Machine. if a datastore is running low on space and a particular virutal machine uses a lot of space. and the generated virtual machine name. From vSphere Web Client Home.1. You must also store your credentials to the virtual machine using the SimpliVity "Save Credentials for VSS" option. 3. 4. Procedure 1. 2012 R2. To use a faster method. or 2016 operating system and VMware Tools installed. Right-click the virtual machine you want to move and click All HPE SimpliVity Actions > Move Virtual Machine. 2. Before you begin Use the vSphere Shut Down Guest option to safely power off the virtual machine. NOTE: You can filter datastore names by entering a string in the Destination Datastore field. such as the amount of space it uses and the current datastore and policy. 4.3. 5. 4. You can use the vSphere move options while the virtual machines remain powered on. This may be useful if you have a large set of datastores. Click the information icon for details on the cluster. Click OK. Chapter 7: Virtual machines 73 . NOTE: You do not need to use the vSphere Shut Down Guest option to use the vSphere vMotion or vSphere Storage vMotion options with virtual machines. see the VMware vSphere documentation. 5. For example. If you want to rename the virtual machine. Right-click the virtual machine you want to move and click All HPE SimpliVity Experimental Actions > Move Virtual Machine. If you want to rename the virtual machine. for example. if a datastore is running low on space and a particular virutal machine uses a lot of space. Click Virtual Machines. Optional: The Virtual machine name field displays the current virtual machine name by default. enter the new name here. This may help you choose a datastore that can accommodate the size of the virtual machine you want to move. datacenter. and the vCenter Server. cluster. datacenter. enter the new name here. and vCenter Server it uses. You can also review the amount of free space available. 6. NOTE: You can review details on the virtual machine you selected. Select the datastore for the virtual machine from the Datastore drop-down menu. Move virtual machines (experimental) You may want to move an HPE SimpliVity virtual machine from one datastore to another. click HPE SimpliVity Federation. Select the datastore that you want to send the virtual machine to from the Destination Datastore menu. the policy. NOTE: You can search for a particular datastore name in the Search field. Procedure 1. typing 2GB in the field limits the listing to datastores with names that begin with 2GB. For more information on these features. From vSphere Web Client Home. 3. Optional: The New VM Name field displays the current virtual machine name by default. and vCenter Server. you cannot create application-consistent backups with VSS until you save the credentials to the virtual machine. click Refresh ( ). the virtual machine must use a Windows Server 2008 R2. 16. you see an alert in vSphere Web Client. However. 3. in some instances the HPE OmniStack will fail to respond. Make sure you select the Application Consistent and Microsoft VSS options through the Advanced tab when you create a policy rule or edit one to create application-consistent backups. (You can also check the status of the credentials through the virtual machine Summary tab by looking for the Application-Aware Status details. In the User Name and Password fields. Click OK. Format the NTFS Volumes on Virtual Machines Procedure overview When formatting NTFS volumes on Windows virtual machines. The HPE OmniStack might return to normal operation after a short time. when cloning a virtual machine you may Chapter 7: Virtual machines 74 . Right-click the virtual machine you want to save credentials for and click All HPE SimpliVity Actions > Save Credentials for VSS. For the best performance on HPE OmniStack hosts. (The privileges allow access to VSS. VMware allows you to over-allocate memory for virtual machines. and 2016. NOTE: If the virtual machine is powered off. 2012. you see a message that OmniStack saves the credentials to verify them when the virtual machine powers on.) If you do not want to save the validated credentials at that time. click HPE SimpliVity Federation. you need to save the updated credentials again. 32.) 5. Save credentials for VSS You must save the guest credentials to a virtual machine if you want to create application-consistent backups with Microsoft Volume Shadow Copy Service (VSS). 2012 R2. or 64 KB). NOTE: To use VSS with OmniStack. For example. If the credentials fail. you can click Cancel. Click Virtual Machines. And. From vSphere Web Client Home. However. or 2016 operating system and have VMware Tools installed. the allocation unit size (cluster size) defaults to 4 KB. 4. In addition. Procedure 1. This can cause virtual machines to use memory needed for the Virtual Controller and cause the HPE OmniStack to stop responding. 6. OmniStack stores the credentials securely and only uses them to access VSS. you need to format Windows NTFS volumes to an allocation size of any multiple of 8 K up to 64 KB (for example. VSS coordinates the actions between applications to create a consistent shadow copy of the data and simplify the restore process. if you change them later. NOTE: If you do not see the virtual machine moved from the original list of objects after the task completes. the supported VSS-aware applications are SQL Server 2008 R2. enter the user name and password for the guest account that has administrator privileges. 2. enabling you to correct the over-allocation problem. 2014. active format fs=ntfs label=”System” quick create partition primary size =N NOTE: This is the boot volume of size N. format fs=ntfs label=OS_8k quick unit=8192 assign exit 4. Run the following commands to create the partitions: diskpart select disk 0 create partition primary size=100 NOTE: This is the system volume and will be formatted with a cluster size <= 4 KB. use Windows Disk Management to format the disk. formatted with the 8 KB cluster size. • The primary HPE OmniStack host for a non-HA compliant VM is offline. Boot from the Windows installation media. Chapter 7: Virtual machines 75 . Procedure 1.see that the memory allocated to clones exceeds the available physical memory when powered on. Register virtual machines after an HPE OmniStack power failure Procedure overview If both the primary and secondary HPE OmniStack hosts for a virtual machine go offline while a virtual machine is out of Storage HA compliance. specifying an 8 KB allocation size. Therefore. the VM might remain inaccessible even after you set all HPE OmniStack hosts back online. Complete the setup. deploying the Windows operating system to the second partition (not the 100 MB primary partition). 2. This problem is dependent on the timing of system outages and one of the following: • The primary and secondary HPE OmniStack hosts for an HA compliant virtual machine are offline. NOTE: If you add NTFS VMDKs at a later time. The example uses an arbitrary size of 100 MB. if an HPE OmniStack fails to correct itself. 3. Press Shift+F10 at the first setup screen to open a command prompt. restart the HPE OmniStack and correct the memory over-allocation before restarting virtual machines. However. Procedure 1. To resolve this. Chapter 7: Virtual machines 76 . 3. • Delete from Disk: Removes the virtual machine and all the files associated with it. 3. 6. In vSphere Web Client. you can restore the virtual machine. click HPE SimpliVity Federation. 5. For vSphere 6. data might be unavailable as long as the virtual machine is inaccessible.0. Right-click the . But. Delete virtual machines When you delete a virtual machine. click HPE SimpliVity Virtual Machines Objects. you must register the virtual machines again. increasing storage space in the datastore. Procedure 1. From vSphere Web Client Home. click the Related Objects tab and then the HPE SimpliVity Virtual Machines subtab. click HPE SimpliVity Federation. 8. there is no loss of data. 7. Double-click the folder for the virtual machine you just removed from inventory to expand it. but retains its files. Click the Manage tab and click the Files subtab. NOTE: The amount of storage space reclaimed by the deletion might take several minutes to appear in the storage capacity displays. Double-click the datastore with the inaccessible virtual machine. 4. Repeat these steps for each inaccessible virtual machine that you need to register.vmx file for the previously inaccessible virtual machine that you removed from the inventory and select Register VM. then click Datastores. Right-click the virtual machine you want to delete and select one of the following vSphere Web Client options: • Remove from Inventory: Removes the virtual machine from the vSphere inventory. When prompted to confirm. You can restore the virtual machine to the inventory. Right-click the inaccessible virtual machine and select Remove from Inventory. 2. if you have backups of the virtual machine. the federation keeps the virtual machine backups. Click Virtual Machines.If this occurs.5. For vSphere 6. click Yes. 2. 6. To access the all the VM templates in vCenter Server ( HPE SimpliVity VM templates and VMware VM templates). HPE SimpliVity VM templates include the virtual machine disk settings from its . Procedure 1. 5. Watch for the virtual machine template creation messages in the Recent Tasks panel. Or. clone a template to template. click Home > vCenter Inventory Lists > VM Templates in Folders. click HPE SimpliVity Federation. 2. Procedure overview Once you convert a virtual machine to a template. You can also backup an HPE SimpliVity VM template instead of a virtual machine to create a long term backup of a virtual machine. You can also clone a virtual machine to a template.vmx (configuration) file. Like standard VMware VM templates. Right-click the virtual machine you want to convert to a template and click Actions > Power Off. or convert a virtual machine using the vSphere New Virtual Machine option through a host. Chapter 8: Virtual machine templates 77 . Click Virtual Machines to open the Objects tab. From vSphere Web Client Home. 4. you can use the VM template backup to create and deploy consistent copies of virtual machines across a company. 3. You can access the new VM template through the Home > HPE SimpliVity Federation > VM Templates. Create virtual machine templates An HPE SimpliVity virtual machine (VM) template is a model copy of an HPE SimpliVity virtual machine that you can use to clone more virtual machines. Templates save you time and help you avoid errors when configuring settings to create new virtual machines. you can use HPE SimpliVity options to back it up in a federation.Chapter 8: Virtual machine templates This section contains the following topics: • HPE SimpliVity virtual machine templates • Create virtual machine templates • Clone virtual machine templates • Move virtual machine templates • Move virtual machine templates (experimental) • Delete virtual machine templates HPE SimpliVity virtual machine templates An HPE SimpliVity virtual machine (VM) template is a model copy of an HPE SimpliVity virtual machine that you can use to clone more virtual machines. Click Yes when prompt to convert the virtual machine. Right-click the virtual machine you powered off and click Template > Convert to Template. if a datastore is running low on space and a particular virutal machine template uses a lot of space. Move virtual machine templates You may find it useful to move HPE SimpliVity VM templates from one datastore to another. 2. Click VM Templates. 5. 4. If you want to rename the template. Select the datastore that you want to send the template to from the Destination Datastore menu. backup policy. Click VM Templates to open the Objects tab.) To see more details on the other objects used by the virtual machine template. 3. 5. for example.Clone virtual machine templates You can create a copy of an HPE SimpliVity virtual machine template. NOTE: If you do not see the cloned virtual machine template in the list of objects after the task completes. (The generated name consists of the original name with current date and time appended to it. Move virtual machine templates (experimental) You may want to move an HPE SimpliVity virtual machine template from one datastore to another. Click Finish. Procedure Chapter 8: Virtual machine templates 78 . and the generated virtual machine template name. leave the automatically generated name for the cloned virtual machine template or enter a new name. Procedure 1. From vSphere Web Client Home. 3. for example. From vSphere Web Client Home. For example. In the Clone virtual machine template name field. 4. Procedure 1. Right-click the virtual machine template you want to clone and click All HPE SimpliVity Actions > Clone VM Template. click HPE SimpliVity Federation. enter the new name here. click the information icon. Right-click the virtual machine you want to move and click All HPE SimpliVity Actions > Move VM Template. if a datastore is running low on space. click HPE SimpliVity Federation. Optional: The New VM Template Name field displays the current virtual machine name by default. This may be useful if you have a large set of datastores. click Refresh ( ). The Clone Virtual Machine Template wizard opens with the current virtual machine template name. 2. typing 2GB in the field limits the listing to datastores with names that begin with 2GB. NOTE: You can filter datastore names by entering a string in the Destination Datastore field. datacenter. 2. enter the new name here. the federation keeps the virtual machine template backups. Delete virtual machine templates When you delete a virtual machine template. 5. From vSphere Web Client Home. 3. such as the amount of space it uses and the current datastore and policy. • Delete from Disk: Removes the virtual machine template and all the files associated with it. Click VM Templates. 6. Right-click the virtual machine template you want to move and click All HPE SimpliVity Experimental Actions > Move VM Template. Click the information icon for details on the cluster. NOTE: You can search for a particular datastore name in the Search field. datacenter. click HPE SimpliVity Federation.1. 2. 4. increasing storage space in the datastore. Optional: The VM template name field displays the current virtual machine template name by default. if you have backups of the virtual machine template. NOTE: The amount of storage space reclaimed by the deletion might take several minutes to appear in the storage capacity displays. and vCenter Server. This may help you choose a datastore that can accommodate the size of the virtual machine template you want to move. cluster. You can restore the virtual machine template to the inventory. 3. However. click HPE SimpliVity Federation. you can restore it. the policy. NOTE: If you do not see the virtual machine template moved from the original list of objects after the task completes. and the vCenter Server. click Refresh ( ). Select the datastore for the virtual machine template from the Datastore drop-down menu. You can also review the amount of free space available. NOTE: You can review details on the virtual machine template you selected. and vCenter Server it uses. Procedure 1. Right-click the virtual machine template you want to delete and select one of the following vSphere Web Client options: • Remove from Inventory: Removes the virtual machine template from the vSphere inventory. From vSphere Web Client Home. Click VM Templates. Click OK. but retains its files. Chapter 8: Virtual machine templates 79 . If you want to rename the virtual machine template. add rules to create a mix of local and remote backups. Chapter 9: Backups 80 . • Manually create a backup at the current point in time. You should also consider the following: • Backup policy rules: A backup policy can contain a large number of rules. you can specify a retention time for a set number of minutes. Use the HPE SimpliVity user interface from a central location to create or update backup policies for thousands of virtual machines across dozens of sites in less than one minute (approximately). An HPE SimpliVity federation can contain thousands of virtual machine backups.Chapter 9: Backups This section contains the following topics: • Backup planning • Application-consistent backups • Disaster protected backups • Back up manually • Back up with a policy • Search for backups • Manage backups • Restore HPE SimpliVity backups • Restore backups when the Hypervisor Management Service is down Backup planning A virtual machine backup represents the contents of a virtual machine at the point in time a backup is created. create a mix of backups that are. They are not deleted automatically. months. In addition. Balance the backup schedule to ensure reliable virtual machine performance. and years when you create the backup policies or backups. but not recommended for normal production use. filter. For an HPE SimpliVity backup. Plan your virtual machine backup schedule and the retention time for backups carefully. For a comprehensive virtual machine backup strategy. Retain only the most recent snapshot on a virtual machine. Snapshots consume a significant amount of disk space and a virtual machine with several existing snapshots can cause backup failures. days. The maximum retention period is 20 years. You can lock the automatic backup for it to never expire or have it automatically delete aging backups according to the rules of the policy. You can easily search. and are not. • VMware snapshots: VMware snapshots are supported. hours. or restore files and folders on a Windows guest virtual machine. You can create a backup of an HPE SimpliVity virtual machine in two ways: • Automatically create backups on a regular basis by using a backup policy that contains one or more policy rules. You can restore an existing virtual machine. application consistent. Manual backups default to a state of never expires to preserve the backups until you manually delete them. and sort backups at any time. The default retention time for backup policies must have a time set to automatically create and retain backups. create a new virtual machine. You can also assign policies to individual virtual machines and tailor the policy rules to best protect the virtual machine. you can use one of the following methods: • VMware snapshot (default for Application Consistent option) • Microsoft Volume Shadow Copy Service (VSS) If you use application-consistent backups in a policy. If you plan to use snapshots to create the backup. It preserves the state of the virtual machine and includes all the data at a specific point in time. VSS oversees the process and ensures it takes 10 to 60 seconds to complete. For example. If you select the VSS method instead of the default snapshot method. However. HPE OmniStack creates crash-consistent backups. if the application is experiencing moderate to high rates of I/O. For example. You can create application-consistent backups when you back up virtual machines manually or with a policy. this backup process could take many hours and impact performance. or 2016 operating system and VMware Tools installed. In addition. These backups capture all the virtual machine data at one time and work well for standard applications. HPE OmniStack uses the VMware snapshot method by default. However. When you select the Application Consistent option for a backup policy rule. NOTE: If you do not choose to create application-consistent backups. • Save the credentials to the virtual machines that use the policy using the SimpliVity "Save Credentials for VSS" option. you must: • Use a virtual machine that has a Windows Server 2008 R2.• Backup and restore locations: HPE SimpliVity restricts backup and restore locations to directly connected clusters only. the backup allows the pending I/O operations to finish before committing them to the database. in a hub and spoke architecture. This type of backup captures the contents of the memory and any pending writes that occurred during the backup process. You can also use different methods to create application-consistent backups. • Select the Microsoft VSS option for application-consistent backups when you create or edit a policy rule using SimpliVity options. You cannot use a mix of application-conisistent methods (if you choose to include application-consistent rules). To use VSS with HPE OmniStack. it resumes writes against the application. Chapter 9: Backups 81 . to ensure that the backup includes all the data at a specific point in time. clusters on the spokes connect to the cluster in the hub and not to the clusters on the other spokes. you can create an application-consistent backup. VSS uses application-specific writers to freeze the application and database and ensures that all the data transferring from one file to another is captured and consistent. You cannot use VSS. the supported VSS-aware application is SQL Server 2008 R2 or later. but not to clusters on one of the other spokes. plan the backups when the hosts are not busy to reduce any performance impact. one method may take longer than the other. just select the Application Consistent option when you manually back up a virtual machine or when you create or edit a policy. NOTE: If you want to clone a virtual machine. However. To use VMware snapshots with HPE OmniStack. These types of backups work well for database applications because they do not require extra work to restore files (such as journaling forward to ensure you have all the data). all rules in the policy must use the same method. Application-consistent backups An application-consistent backup is a backup of application data that allows the application to achieve a quiescent and consistent state. 2012 R2. a cluster on one of the spokes can complete backups and restore to the cluster in the hub. you can only use the default method (snapshot). Therefore. it can save time when creating the backup. Once VSS creates a shadow copy and the application is in a consistent state. truncation is not performed as part of the Application Aware backups using Microsoft VSS. ◦ HPE OmniStack host added to the federation. SQL Server manages the transaction logs. 2014 and 2016 are supported VSS applications.Use these guidelines when creating policies with rules that use the Application Consistent setting (with the default or VSS method): • Do not schedule the backups during HPE OmniStack software upgrades. you must run the svt-vm-backup- params-set command to support VSS-based backups. and log truncation is not required. ◦ vSphere Storage VMotion. keep the following guidelines in mind: • SQL Server 2008 R2. Chapter 9: Backups 82 . • A virtual machine's guest credentials are maintained for the following use cases: ◦ Initial set or subsequent reset of VSS guest credentials using the svt-vm-backup-params-set command. When Microsoft SQL Server is configured with the Simple recovery model. ◦ HPE SimpliVity Clone. You can then create rules to back up each group at different times to reduce the number of simultaneous backups. ◦ HPE SimpliVity Restore. 2012. • All current published HPE SimpliVity limitations with regard to scale apply for VSS backups. • When Microsoft SQL Server is configured with either the Full or Bulk-Logged recovery model log. • Create a combination of application-consistent and crash-consistent backups to local and remote clusters. The transaction logs must be managed manually. ◦ vSphere Clone. ◦ HPE SimpliVity Move. • Do not schedule the backups at the same time as any third-party database backups. otherwise. 2012 R2. • Windows Server 2008 R2. or with a third party backup solution. • If you have a large number of virtual machines. Guidelines for using Microsoft Volume Shadow Copy Service (VSS) When you create a backup that uses Microsoft Volume Shadow Copy Service (VSS). you must configure its guest credentials. and 2016 are supported VSS operating systems. After you restore a virtual machine using one of these methods. you can create separate policies to separate the virtual machines into smaller groups. After you create or make configuration changes to a virtual machine. • A successful VSS backup requires the following two conditions on the virtual machine: ◦ The virtual machine must be powered on. • All limitations for VSS published by Microsoft apply. the transaction logs will continue to grow unbounded and the virtual machine may run out of space. • A virtual machine's guest credentials are NOT maintained for the following use cases: ◦ HPE SimpliVity Restore to a new virtual machine. See SimpliVity How To: 11953 How to Configure a Guest VM for VSS Backup for information pertaining to the depth of configuration required for administrator and non-administrator user accounts. • The credentials you provide should be for a user added to the local machine's administrator group. all the tracking data is removed.you do not need to use SQL backups. • Use of invalid credentials passed to svt-vm-backup-params-set may count against the virtual machine's account lockout policy. and Bulk logged: 1. As such. Database (full) backup makes a copy of the all database files.0 or later must be installed and running on the guest virtual machine. log backups copy the transactions found in the transaction log. You can use a VSS backup to restore the same way you would restore using a full or differential backup. and databases using the Simple recovery model are referred to as being in auto-truncate mode. however. the system takes full database backups. the transaction log file is not auto-truncated during CHECKPOINT operations. 2. If a portion changes. You still need to use full backups and transaction log backups in order to perform point in time recovery. whenever a checkpoint operation occurs. 1. In the simple recovery mode. Full. Database recovery types There are three SQL Server database recovery types: Simple. Later. UPDATE and DELETE operations. Database backup types There are three basic types of database backups: Database (full). This means all INSERT. and a small portion of the transaction log necessary to recover the database from the full backup. You should discontinue the use of these scripts on any virtual machine on which you enable the VSS-integrated backups solution. the FULL recovery model supports restoring a database to any point in time within an available log backup and. it is marked as modified. and Log backups. which requires more I/O operations and are more disruptive to database applications than VSS backups. Instead. In the Full recovery model. right up to the time of the last committed transaction before the failure occurred. the space in any inactive portions of the log file becomes available for reuse.ps1 script. you can simply use SimpliVity VSS backups . This is referred to as a point in time recovery. This process of making log space available for reuse is known as truncation. it marks all copied transactions as no longer required so that log space can be reused. all operations are fully logged in the transaction log file. only the modified portions are copied to the backup file. • SQL server must be properly installed with Microsoft VSS integration. Differential backup makes a copy of the modified portions of the database files since the last full database backup. in conjunction with this feature is prohibited. unlike in SIMPLE model. Furthermore. Differential. After the backup copies the transactions. The Simple recovery model is the easiest to manage. you cannot restore a log backup after restoring a VSS backup. available via SimpliVity How To: 4041 How to Back Up and Restore Application Consistent Snapshots of SQL and Exchange Databases. When a differential backup is performed. and so an unbroken series of log records can be captured in log backup files. as well as the full details for all rows inserted during a bulk data load or index creation operations. In the Simple recovery mode. assuming a tail log backup can be made. 3. when a full database backup is performed. differential backups and file backups. Chapter 9: Backups 83 . and to truncate the transaction logs. If you're using the simple recovery model. • Use of the SimpliVItyBackup. ◦ VMware Tools associated with vSphere version 6. It does this by tracking all the portions of the database. 2. The one backup that is not part of the simple recovery type is transaction log backup. Log backups do not copy the database files. however. • Remote cluster backup: The backup is stored in a cluster that is different from the one where the virtual machine resides. It operates in a very similar manner to the Full model. From a backup and restore point of view. occasionally means as frequently as needed. you can schedule daily backups every night or every weekend of all system databases. read only. Each database being managed should have its own approved backup plan. Sometimes the information stored in a database is so valuable that you want to back up the information very often. This is the simplest backup strategy. the DBA schedules one full backup and multiple Log backups. Full & Log Backup. and to truncate the transaction logs. but bulk operations are not logged. system databases or databases not requiring a point in time recovery. in case of failure. and Log Backups. between full backups. Identify your disaster recovery goals to ensure that your business runs in the event of a disaster. Use the Full Backup Simple Mode strategy only on development. Remote backups protect against a disaster that involves a complete loss of cluster hardware. and so on) are fully logged. This plan has the advantage of reducing the amount of lost information in case of total server collapse. However. 2. because you can schedule log backups more regularly than you can schedule full backups. For example. In the Full & Log Backup scenario. to minimize the impact of restoring too many log backups. except for logging bulk operations. you will have to restore every log backup since the last full backup. When using Full. Disaster protected backups A disaster recovery plan is critical to protecting virtual machine data against a complete disaster. For disaster protection. just as they would be in the Full recovery model. Inventory your current infrastructure and clearly define a Recovery Point Objective (RPO) and Recovery Time Objective (RTO). All standard operations (INSERT. DELETE. you schedule a Full Backup occasionally. In this case. Very often means as frequently as needed to minimize data loss exposure. The level of data protection depends on the specified destination cluster for the backup: • Local cluster backup: The backup is stored in the same cluster where the virtual machine resides. including requirements and strategy. You can use a VSS backup to restore the same way you would restore using a full or differential backup. 3. the Full – Differential – Log strategy may help. but enough to avoid differential backups from growing too much. and performs periodic Full Database backups using VSS. the DBA configures the database recovery model to simple. and Logs very often. consider the frequency of backup operations and the amount of data protection that a backup provides. which has implications for point-in-time restores. In this case. Bulk Logged is the least-frequently used recovery model. Chapter 9: Backups 84 . A local backup does not protect against a disaster that involves a catastrophic loss of cluster hardware. differential backups often. When you follow the Full Backup—Simple Mode strategy. to minimize the impact of a full backup. There are three basic database backup strategies: Full Backup—Simple Mode. you should perform a full backup after completing the bulk load operations because the transaction log backup does not include the bulk data. When planning a backup strategy. relying on backup logs is not feasible because. You still need to use full backups and transaction log backups in order to perform point in time recovery. the backup cluster must use hardware that is in a different physical location from the cluster with the virtual machines. Often means as frequently as needed. UPDATE. 1. you cannot restore a log backup after restoring a VSS backup. Database backup strategies Combining different backup types to meet the backup requirements of the backup plan is the backup strategy for a database. and Full – Differential – Log.3. stage. and the easiest to restore. using VSS minimizes the system impact and provides transaction consistency. Differential. Balance the backup schedule to ensure reliable virtual machine performance. The more frequent a virtual machine backup operation. For a comprehensive virtual machine backup strategy. more federation resources are consumed in storing and transferring backups. hours. including the time to restart key applications and establish full communications. Options for protecting and recovering data Consider these options when designing a backup strategy for virtual machines in a SimpliVity federation: Recovery point objective The recovery point objective (RPO) is the maximum amount of virtual machine data loss after an unplanned incident. However. such as a few minutes. the smaller the RPO. and years when you create backups and backup policies. The maximum retention period is 20 years. Data retention time For a federation virtual machine backup. with higher backup frequencies. add rules to create a mix of local and remote backups. in a hub and spoke architecture. clusters on the spokes connect to the hub cluster but not directly to the clusters out on Chapter 9: Backups 85 . the default retention time is to preserve backups until you manually delete them. Backup and restore locations HPE SimpliVity restricts backup and restore locations to directly connected clusters only. Recovery time objective The recovery time objective (RTO) is the length of time required to restore virtual machine availability if a failure occurs. more federation resources are consumed in storing and transferring backups. In addition. do not have a backup frequency interval set to a short duration. You can also assign policies to individual virtual machines and tailor the policy rules to best protect the virtual machine. days. To avoid exhausting federation resources within a short time and creating large data volumes. create a mix of backups that are. expressed as a length of time. months. Backup policy rules A backup policy can contain a large number of rules. Snapshots consume a significant amount of disk space and a virtual machine with several existing snapshots can cause backup failures. with higher backup frequencies. However. application consistent. The allowed frequency range for virtual machine backups is 10 minutes to 1024 days. The allowed frequency range for virtual machine backups is 10 minutes to 1024 days. The more frequent a virtual machine backup operation. Minimizing recovery time for a datacenter recovery is crucial for business continuity and disaster recovery solutions.The RPO is the maximum amount of virtual machine data loss after an unplanned incident. The RTO is the length of time required to restore virtual machine availability if a failure occurs. including the time to restart key applications and establish full communications. and are not. You can specify a retention time for x number of minutes. Retain only the most recent snapshot on a virtual machine. Plan your virtual machine backup schedule and the retention time for backups carefully. To avoid exhausting federation resources within a short time and creating large data volumes. expressed as a length of time. but snapshots are not recommended for normal production use. For example. the smaller the RPO. Snapshots VMware snapshots are supported. Minimizing recovery time for a cluster recovery is crucial for business continuity and disaster recovery solutions. such as a few minutes. do not have a backup frequency interval set to a short duration. 2012 R2. the OmniStack software includes a standard time stamp string as part of the default backup name. According to the standard.m. etc) DD Represents the two-digit day of the month (01 through 31) hh Represents two digits for hour (00 through 23. You specify the following information for a manual backup: • Backup name: Optional user-specified name for the backup. seconds. In this situation. In accordance with ISO Standard 8601. but not to a cluster on one of the other spokes. Back up virtual machine data manually Chapter 9: Backups 86 . if the virtual machines use Microsoft VSS on a Windows Server 2008 R2. and a time zone designator as illustrated in the following example: VM_name-YYYY-MM- DDThh:mm:ssTZD Variable Definition VM_name Represents the name of the virtual machine. plus hours. the backup name contains the complete date.the other spokes. YYYY Represents the four-digit year MM Represents the two-digit month (01=January. Remote clusters provide greater disaster protection if they are not in the same location as the virtual machine. Leave it unselected to create a crash-consistent backup. minutes. a default name will be chosen. you can create or update backup policies for thousands of VMs across dozens of sites in less than one minute. If not specified. Using the HPE SimpliVity user interface from a central location. the backup is automatically deleted.m./p. Or. you can create application consistent backups using VSS. Using this method can take hours. or 2016 operating system and you need to back up data for SQL Server 2008 R2 or later. on average. a cluster on one of the spokes can complete backups and restores to the cluster at the hub. a. not permitted) mm Represents two digits for minutes (00 through 59) ss Represents two digits for seconds (00 through 59) TZD Represents time zone designator (Z or +hh:mm or –hh:mm) NOTE: A "T" appears in the backup name and represents the beginning of the time element. • Application-Consistent: Back up application data with the contents of the memory and any pending writes using the default snapshot method to create an application-consistent backup. • Destination cluster: Name of the cluster where you want the backup to reside. Back up manually Manual backups You can create a manual backup of a federation virtual machine at any time. • Retention: The length of time to retain the backup. When the retention time expires. In the Backup Name field. From vSphere Web Client Home. 2. It defaults to the local cluster. The maximum is 20 years. 6. 4. NOTE: For the process to use VSS. Procedure 1. select Set Retention Period and set the number of minutes. 3. enter a name for the backup or leave it blank to generate an automatic name using the time zone of the cluster. Procedure 1. select the cluster where you want the backup to reside from the drop-down menu. the process uses the default VMware snapshot method to create the backup. 5. In the Destination Cluster field. 2012 R2. 4. hours. select Microsoft VSS (Volume Shadow Copy Service). Back up VM template data manually Procedure overview You can backup a virtual machine (VM) template manually if you do not want to use a policy to backup virtual machine template data automatically. 6. Click VM Templates to open the Objects tab. the virtual machine must have a Windows Server 2008 R2. Or. It defaults to the local cluster. months or years to retain the backup. In addition. the only supported VSS-aware application is SQL Server 2012 R2 or later. To use a faster method. Click OK. 5. 2. click HPE SimpliVity Federation. • Leave Application Consistent unselected or select it to back up data in a consistent state. Optional: Click Advanced to view the settings or do the following: Chapter 9: Backups 87 . click HPE SimpliVity Federation. You must also store your credentials to the virtual machine using the SimpliVity "Save Credentials for VSS" option. 7. enter a name for the backup or leave it blank to generate an automatic name using the time zone of the cluster. or 2016 operating system and VMware Tools installed. In the Destination Cluster field. days. weeks. select the cluster where you want the backup to reside from the drop-down menu. Right-click the virtual machine you want to back up and click All HPE SimpliVity Actions > Backup Virtual Machine. In the Backup Name field. Right-click the virtual machine you want to back up and click All HPE SimpliVity Actions > Backup VM Template. From vSphere Web Client Home. If selected. Click Virtual Machines to open the Objects tab. (Optional) Click Advanced to specify the following details: • Leave Retention set to Remain until I delete to keep the backup unless you delete it (never expires). 3.Procedure overview You can back up a virtual machine manually if you do not want to use a policy to backup virtual machine data automatically. 2. From vSphere Web Client Home. it captures virtual machine application data at once. This method takes 10 seconds or less. months or years to retain the backup. Click Next to set the backup type. Back up virtual machine data manually (experimental) Procedure overview You can back up a virtual machine manually instead of using a policy. This is a common type of backup. • Select Set date to set a date when you want the backup to expire (maximum 20 years). English date format. leave the default of the local cluster for the backup or select another cluster from the drop-down menu. Do one of the following: • Leave Never expires selected to keep the backup until you manually delete it. 8. It cannot convert the date to the local settings. For example. do one fo the following: • Leave VMware snapshot selected to create the backup using a VMware snapshot. Chapter 9: Backups 88 . By default. select Microsoft Volume Shadow Copy Service (VSS) to use VSS to create the backup. • Select Application consistent to back up data in a consistent state. Click OK. leave the field blank to generate an automatic name using the time zone of the cluster or enter a name for the backup. the date populates to two weeks after the current date. hours.S. Right-click the virtual machine you want to back up and click All HPE SimpliVity Experimental Actions > Back Up Virtual Machine. If you selected Application consistent. Click the calendar to select another date. (The maximum is 20 years. Skip to step 10. select Set Retention Period and set the number of minutes. Or. weeks. 7. 5. Do one of the following: • Leave Crash consistent selected to create a crash-consistent backup. NOTE: If you use Internet Explorer 10. In the Destination cluster field. However. days. 9.) The backup expires at midnight on the date you select. • If the virtual machine is supported. 6.) 7. these types of backups are good for database applications because they capture all the data in memory and all the transactions in process. In the Backup name field. 4. Procedure 1. You must also enter the user name and password to the virtual machine for the backup process to access VSS. Click Virtual Machines to open the Objects tab. this process may take an hour or more. unless you delete it). click HPE SimpliVity Federation. the calendar uses the U. (You can use the arrows to scroll forward or backward in months or years. 3. • Leave Retention set to Remain until I delete to keep the backup (never expires. In addition. Do one of the following: • Leave Never expires selected to keep the backup until you manually delete it.) The backup expires at midnight on the date you select. leave the field blank to generate an automatic name using the time zone of the cluster or enter a name for the backup. And. Back up with a policy HPE SimpliVity backup policies It is important to back up your data regularly. crash-consistent backups continue even when vCenter Server is down. Right-click the virtual machine template you want to back up and click All HPE SimpliVity Experimental Actions > Back Up Virtual Machine Template. Backup policies also enable you to create a mix of crash-consistent backups (created by default) and application-consistent backups (using the default VMware snapshot method or Microsoft Volume Shadow Copy Service [VSS] method). Procedure 1. Backup policies allow you to schedule backup operations for HPE OmniStack virtual machines. From vSphere Web Client Home. the calendar uses the U. English date format. In the Virtual machine template backup name field. Click Finish. 6. (You can use the arrows to scroll forward or backward in months or years. • Select Set date to set a date when you want the backup to expire (maximum 20 years). Click Finish. It cannot convert the date to the local settings. the only supported VSS- aware application is SQL Server 2012 R2 or later. 10. To schedule backup operations. with a policy. Click VM Templates to open the Objects tab. 2. 5. 7. In the Destination cluster field. click HPE SimpliVity Federation. A policy must have at least one rule to create backups. By default. NOTE: If you use Internet Explorer 10. 3.S. Back up virtual machine template data manually (experimental) Procedure overview You can back up a virtual machine template manually instead of using a policy. the virtual machine must have a Windows Server 2008 R2 or 2012 R2 operating system and VMware Tools installed. NOTE: To use VSS to create application-consistent backups. the date populates to two weeks after the current date. you create a backup policy and then add one or more rules to the policy. Click the calendar to select another date. A backup policy rule includes: • Backup schedule Chapter 9: Backups 89 . leave the default of the local cluster for the backup or select another cluster from the drop-down menu. 4. Create a backup policy Procedure overview You can create a backup policy to back up virtual machines. you can add some rules that are application consistent and some that are not. 2. If you have more than one backup policy for a datastore. • Click Backup Policies to open the Objects tab and click the Create Backup Policy icon [ ]. you must specify the default backup policy for new virtual machines created in the datastore. you add rules that define how you want to back up the virtual machines. If you delete or change a backup policy rule. After you create a virtual machine. you can select which one you want to use when you create the datastore. NOTE: Verify that the policy rules create backups at the correct local time. you can also create a manual backup of a virtual machine. Scheduled backups are assigned a name based on the timestamp when the backup started. the change applies only to new virtual machines created in the datastore. Although the number of rules is unlimited. Chapter 9: Backups 90 .• Destination cluster for the backups • Maximum number of backups to retain • Selection of application consistent or not (using the standard or VSS method) You can transmit backups to local and remote clusters for enhanced virtual machine data security. You can also specify backup policies for individual virtual machines. the policy preserves all backups previously created under that rule and they continue to consume storage space. When you create a backup policy. For a comprehensive virtual machine backup strategy. In addition. NOTE: If you have not created an HPE SimpliVity datastore yet. Any virtual machines that use that datastore use the default backup policy until you change it. you can add rules with a mix of local and remote backups. you can specify a different backup policy for the virtual machine. At any time. create a backup policy with a rule for the datastore you plan to create. When you create a datastore. and edit rules when needed. You must manually delete the preserved backups if you want to remove them. A backup policy must contain at least one rule before it can create backups. depending on how you want to open the Create a Backup Policy dialog box: • Click Create Backup Policy from the Basic Tasks section of the Hewlett Packard Enterprise Home tab. You can also assign policies to an individual virtual machine and tailor the policy rules to best protect it. This policy can act as the default policy for the datastore. If you change the default backup policy assigned to a datastore. NOTE: The HPE SimpliVity federation must contain at least one HPE OmniStack host before you can create a backup policy using these steps. On the Home page. HPE SimpliVity recommends no more than 30 rules in a policy. click HPE SimpliVity Federation. You can modify a backup policy and add. Procedure 1. delete. Do one of the following. hours. the policy uses the default VMware snapshot method to create the backup. In the Policy Name field. NOTE: For the policy to use VSS. If selected. 4. You can select one or more days. In addition. 29. The default end time is midnight (12:00 AM) based on the time zone set for the cluster. NOTE: The frequency of the backups applies to the server start and stop time period. set the time interval when backups are taken in minutes. specify the name for the new backup policy. To use a faster method. right-click the object you want to create a policy for. set a start time for the server to start the backups. and click All HPE SimpliVity Actions > Set Backup Policy. select Last Day of the Month. To select the local cluster of the vCenter Server. The backup frequency must be less than 24 hours (or 1440 minutes). Click Create Rule to open the Create Policy Rule dialog box. All year calculations use a 365-day year. Enter positive numbers only. hours. the appropriate virtual machines must have Windows Server 2008 R2 or 2012 R2 operating system and VMware Tools installed. View a backup policy for a virtual machine Procedure overview Chapter 9: Backups 91 . set an end time for the server to stop the backups. In the Retain Backups For field. 30. select the cluster where the backups reside from the drop-down menu. 6. 7. 9. In the Destination Cluster field. All month calculations use a 30-day month. • In the Days field. The default is all seven days. select one of the following: ◦ Days of the week: Days you want to create backups. or years. days. select Microsoft VSS (Volume Shadow Copy Service). For the last day of the month (28. The minimum frequency interval is 10 minutes. Then click Create. In the Frequency field. Enter positive numbers only. A default rule creates a backup every hour for the entire day. Then click Create. 3. set the retention time in minutes. 5. Click the date(s) you want. or 31). right-click the datastore you want to create a policy for. Click OK. • Click Virtual Machines or VM Templates. the only supported VSS-aware application is SQL Server 2012 R2 or later. weeks. • Leave Application Consistent unselected or select it to back up data in a consistent state. months. • In the Server Local Time Stop field. • Click Datastores. ◦ Days of the month: Days in the month that you want to create backups. You must also store your credentials to the appropriate virtual machine using the SimpliVity "Save Credentials for VSS" option. or days. and click All HPE SimpliVity Actions > Set Default Backup Policy. 8. (Optional) Click Advanced to specify the following details: • In the Server Local Time Start field. select <local>. • To review the number of rules. you can access the Summary tab to view summary information on the virtual machine and access the backup policy to edit it. 5. For example. used storage capacity. Click the HPE SimpliVity Virtual Machines subtab. Click Virtual Machines to open the Objects tab. You see details on the CPU. you may want to check which virtual machines use the policy. For example. click HPE SimpliVity Federation. click Edit. storage High Availability status. click the Summary tab. • To create a new backup policy rule. datastores. Click the Related Objects tab. 2. View virtual machines related to a backup policy Procedure overview You can view all the virtual machines associated with a backup policy. This opens a list of all the related virtual machines. • To access details on other virtual machines that use the policy (names. and virtual machines that use the policy. amount of provisioned and used memory. 7. click the link with the policy name. 3. clusters. 2. click HPE SimpliVity Federation. memory. Double-click the row with the virtual machine that has the backup policy you need to access. double-click the one you want to view. From vSphere Web Client Home. From vSphere Web Client Home. Procedure 1. 3. datastores. name of the datastore and cluster. Before you change a backup policy rule. and IP address of the vCenter Server. 4. total capacity available. and the backup policy name. number of virtual hard disks. provisioned status. View datastores related to a backup policy Procedure overview Chapter 9: Backups 92 . At the Backup Policy Name field. 6. storage HA status (yes/no/ synchronizing/unknown). Click the Summary tab. Scroll down to the HPE SimpliVity portlet. 5. and vCenter). Click the tab you need to access.You can view an HPE SimpliVity backup policy for a particular virtual machine and access different tabs to view details on it. name of the backup policy. Procedure 1. Click Backup Policies to open the Objects tab. It lists all the virtual machines in the federation. click the Related Objects tab. This opens to tabs for the policy you selected. It lists all the backup policies in the federation. storage High Availability [HA] status. edit a rule. or delete a rule. 4. you can see the virtual machine name. From the list of backup policies. Set the default backup policy for a datastore Procedure overview You can change the default backup policy used by a single datastore or for multiple datastores if you decide you want to use a different policy. Click the Related Objects tab. name of the backup policy the datastore uses. 5. To select non-adjacent items. Click Yes when prompted to confirm your selection. Click Datastores to open the Objects tab. From the Backup Policy field. click HPE SimpliVity Federation. Double-click the row with the backup policy that you need to access. you can create one by clicking Create to open the New Backup Policy dialog box. NOTE: To select a group of adjacent datastores. The list includes details on the datastore name. Procedure 1. you may want to check to see what datastores use it. It lists all the backup policies in the federation. 2. Once you enter a policy name and add at least one rule to create the policy. click OK. From vSphere Web Client Home. cluster for the datastore. and the vCenter Server IP address. However. before you change the rules in a policy. 3. 2. creation date and time. hold down the Shift key and click the first and last datastore. Right-click the datastore you want to update and click All HPE SimpliVity Actions > Set Default Backup Policy. size of the datastore. Set a backup policy for a virtual machine Procedure overview Chapter 9: Backups 93 . select a default policy from the drop-down list. Click Backup Policies to open the Objects tab. From vSphere Web Client Home. you can change the policy a virtual machine uses at any time. The application defaults to the Getting Started tab or the last tab you accessed. Click OK. 6. hold down the Ctrl (Control) key as you select datastores. Procedure 1. You see a list of datastores that use the backup policy you selected. 4. For example. 3. Any new virtual machines using the datastore start using the new policy after you apply your changes. Click the SimpliVity Datastores subtab. The Set Datastore Backup Policy dialog box opens with the new policy in the Backup Policy drop-down list. 4.You can view all the datastores that use a backup policy. Any existing virtual machines continue to use the previous policy. 5. If you do not see a backup policy you want to use. click HPE SimpliVity Federation. hold down the Ctrl (Control) key as you select virtual machines. click OK. From vSphere Web Client Home. Procedure 1. you can create one by clicking Create to open the Create Backup Policy dialog box. Review the bar chart to see the backup consumption level for the Federation on a daily basis and the predicted steady-state level. Once you enter a policy name and add at least one rule to create the policy. click HPE SimpliVity Federation. you see a chart with the consumption information. Click VM Templates to open the Objects tab. Right-click the VM Template you want to update and click All HPE SimpliVity Actions > Set Backup Policy. select it. 9. To set the virtual machines to that policy. 7. Click OK and do one of the following to proceed: • Repeat steps 3-8 to select fewer virtual machines or select another policy to reduce the number of backups. From vSphere Web Client Home. NOTE: To select a group of adjacent virtual machines. For example. 2. If the backups exceed the maximum amount allowed (for example. • Delete unnecessary backups and repeat this procedure again. hold down the Shift key and click the first and last virtual machine. Right-click the virtual machine you want to update and click All HPE SimpliVity Actions > Set Backup Policy. To select non-adjacent selections. Repeat steps 3-8. click HPE SimpliVity Federation. 5. Click Virtual Machines to open the Objects tab. 6. The Set Virtual Machine Backup Policy dialog box opens with the new policy in the Backup Policy drop-down list. Click OK. 8. Set a backup policy for a VM template Procedure overview You can replace an existing backup policy for a virtual machine (VM) Template if you decide you want to use a policy different than the one used by the datastore. 4. over 100%). • Click No to return to the Set Virtual Machine Backup Policy dialog box and make the appropriate changes. 3. Select the backup policy you want to apply from the Backup Policy drop-down menu. Chapter 9: Backups 94 . you may need to select fewer virtual machines or select another policy with a lower frequency and retention time. If you do not see a backup policy you want to use. Procedure 1. 3.You can replace an existing backup policy for a single HPE SimpliVity virtual machine or multiple virtual machines if you decide you want to use a policy different than the one used by the datastore. Click Yes when prompted to confirm your selection. Do one of the following: • Click Yes to set the policy for the selected virtual machines and keep the consumption levels within an acceptable range. 2. Click Yes when prompted to confirm your selection. 5. 6. click Virtual Machines to open the Objects tab. over 100%). • For the Virtual Machines view. click Backup Policies to open the Objects tab with a list of the names of the policies. click OK. Double-click the virtual machine row with the backup policy you want to edit. 8. select it. If the backups exceed the maximum amount allowed (for example. 7. you can create one by clicking Create to open the Create Backup Policy dialog box. Rename a backup policy Procedure overview Use the following steps to rename a backup. Do one of the following: • For the Backup Policies view. Procedure 1. 4. 4. Select the backup policy you want to apply from the Backup Policy drop-down menu. 2. hold down the Ctrl (Control) key as you select objects. To set the VM template to that policy. • Delete unnecessary backups and repeat this procedure again. click HPE SimpliVity Federation. you see a chart with the consumption information. 9. Once you enter a policy name and add at least one rule to create the policy. you may need to select fewer virtual machine templates or select another policy with a lower frequency and retention time. Click the Backup Policy Name link from the SimpliVity portlet. From the Actions menu. Click OK and do one of the following to proceed: • Repeat steps 3-8 to select fewer virtual machine templates or select another policy to reduce the number of backups. From vSphere Web Client Home. 3. NOTE: To select a group of adjacent VM templates. hold down the Shift key and click the first and last objects. Click OK. Repeat steps 3-8. Do one of the following: • Click Yes to set the policy for the selected templates and keep the consumption levels within an acceptable range. Enter the new policy name and click OK. If you do not see a backup policy you want to use. Review the bar chart to see the backup consumption level for the Federation on a daily basis and the predicted steady-state level. To select non-adjacent selections. select Rename Backup Policy. Results Chapter 9: Backups 95 . For example. • Click No to return to the Set Virtual Machine Template Backup Policy dialog box and make the appropriate changes. The Set Virtual Machine Backup Policy dialog box opens with the new policy in the Backup Policy drop-down list. Click the Summary tab and scroll down to the Hewlett Packard Enterprise portlet. In the Destination Cluster field. Click the date(s) you want. • For the Virtual Machines view. NOTE: The "Server Local Time" start and stop times control the time period when backups can start. or days. set a start time for the server to start the backups. Select the backup policy where you want to add a rule. The backup frequency must be less than 24 hours (or 1440 minutes). You can select or one or more days. the policy uses the default VMware snapshot method to create the backup. To select the local cluster of the vCenter Server. 12. Do one of the following: • For the Backup Policies view. Chapter 9: Backups 96 . Click the Backup Policy Name link. hours. when the total system backups reach 100%. In the Server Local Time Start field. 10. you cannot add a backup policy rule. click HPE SimpliVity Federation. select one of the following: • Days of the week: Days you want to create backups. The default start time is midnight (12:00 AM) based on the time zone set for the cluster. Add a backup policy rule Procedure overview You can add a rule to a backup policy at any time. The default end time is midnight (12:00 AM) based on the time zone set for the cluster. click Edit Backup Policy. This determines when HPE OmniStack automatically deletes the backups to create room for more backups. 2. A default rule creates a backup every hour for the entire day. Optional: Leave Application Consistent unselected or select it to back up data in a consistent state. select Microsoft VSS (Volume Shadow Copy Service). From the Actions menu. or 31). 30. months. 7. For the last day of the month (28. In the Server Local Time Stop field. Double-click the virtual machine with the backup policy to which you want to add a rule. Click the Summary tab and scroll down to the Hewlett Packard Enterprise portlet. In the Days field. 9. If selected. select <local>. 3. The default is all seven days. In the Frequency field. set the time interval when backups are taken in minutes. 29. click Virtual Machines to open the Objects tab. The minimum frequency interval is 10 minutes. or years. days. 6. hours. weeks. set a stop time for the server to stop the backups. • Days of the month: Days in the month that you want to create backups. 11.The backup policy list refreshes with the policy renamed. 5. select Last Day of the Month. set the retention time in minutes. click Backup Policies to open the Objects tab. The frequency of the backups applies to this time period. Procedure 1. 4. In the Retain Backups For field. select the cluster where the backups reside from the drop-down menu. However. Click Advanced to specify additional details or skip to the last step. Click Create Rule to open the Create Policy Rule dialog box. 8. To use a faster method. From vSphere Web Client Home. click Virtual Machines to open the Objects tab. click VM Templates to open the Objects tab. scroll down to the Hewlett Packard Enterprise portlet and click Backup Policy Name. • Click No to return to the Create Policy Rule dialog box and make the appropriate changes. 5. From the list of rules. 3. Click Edit Rule to open the Edit Policy Rule dialog box. the only supported VSS-aware application is SQL Server 2012 R2 or later. Repeat steps 5-15. over 100%). For example. if the backup schedule is currently set to Days of the week with Sunday (Sun) and Friday (Fri) selected. • For the Virtual Machines view. You must also store your credentials to the appropriate virtual machine using the SimpliVity "Save Credentials for VSS" option. Repeat steps 5-10. select the one you want to modify. If the backups exceed the maximum amount allowed (for example. Select the backup policy with the rule you want to edit. 15. Retain Backups For. Or. delete unnecessary backups and repeat this procedure again.) • For the VM Template view. Any changes you make apply to all the virtual machines that use that policy rule. For example. 6. 14. Right-click the virtual machine template with the policy you want to edit and click All HPE SimpliVity Actions > Edit Backup Policy. click Backup Policies to open the Objects tab. 13. Do one of the following: • For the Backup Policies view. Server Local Time Stop. Procedure 1. Review the bar chart to see the backup consumption level for the Federation on a daily basis and the predicted steady-state level. Then click OK again. If the backups do not exceed the limit. Do one of the following: • Click Yes to apply your changes if the policy edits keep the consumption levels within an acceptable range. or Days fields. NOTE: For the policy to use VSS. you can change the schedule to days of the month by selecting Days of the Month and clicking the dates on which you want backups to occur. click the Summary tab. Right-click the virtual machine with the policy you want to edit and click All HPE SimpliVity Actions > Edit Backup Policy. Chapter 9: Backups 97 . click HPE SimpliVity Federation. From vSphere Web Client Home. Click OK. OmniStack returns to the Edit Policy Rule dialog box. 4. (You can also double-click the virtual machine name. you can make changes at any time. you may need to lower the frequency and retention time. Edit a backup policy rule Procedure overview You can modify a rule in a backup policy as long as your total system backups do not exceed 100% of the maximum backup system limit. the appropriate virtual machines must have Windows Server 2008 R2 or 2012 R2 operating system and VMware Tools installed. 2. Modify the Frequency. or Destination Cluster field(s) as needed. You must modify the policy again to reduce the number of backups (such as decreasing the frequency or retention time). Optional: Click Advanced to modify the Server Local Time Start. In addition. Do one of the following to open the Edit Backup Policy dialog box: • From the Actions menu. 9. 8. the only supported VSS-aware application is SQL Server 2012 R2 or later. In addition. Repeat steps 5-10. • Click No to return to the Edit Policy Rule dialog box and make the appropriate changes. Review the bar chart to see the backup consumption level for the Federation on a daily basis and the predicted steady-state level. the appropriate virtual machines must have Windows Server 2008 R2 or 2012 R2 operating system and VMware Tools installed. Click the backup policy with the rule you want to delete. click Edit Backup Policy. click Edit. Or. 2. Delete a backup policy rule Procedure overview You can delete a rule from a backup policy at any time. the policy uses the default VMware snapshot method to create the backup. From vSphere Web Client Home. Click Yes when prompted. Click OK. If selected. If the backups exceed the maximum amount allowed (for example.7. over 100%). click HPE SimpliVity Federation. 5. you may need to lower the frequency and retention time. Click OK. Double-click the virtual machine row with the backup policy rule you want to delete. 3. Do one of the following: • Click Yes to apply your changes if the policy edits keep the consumption levels within an acceptable range. Hold the Shift key as you select rows if you want to select more than one rule. NOTE: For the policy to use VSS. click Virtual Machines to open the Objects tab. click Backup Policies to open the Objects tab. • From the Rules field. select Microsoft VSS (Volume Shadow Copy Service). delete unnecessary backups and repeat this procedure again. Select the rule you want to delete and click Delete Rule. Click the Backup Policy Name link. • For the Virtual Machines view. Click the Summary tab and scroll down to the HPE SimpliVity portlet. OmniStack returns to the Edit Policy Rule dialog box. 7. For example. Repeat steps 5-10. 6. To use a faster method. Procedure 1. Do one of the following: • For the Backup Policies view. 10. You must modify the policy again to reduce the number of backups (such as decreasing the frequency or retention time). Chapter 9: Backups 98 . You must also store your credentials to the appropriate virtual machine using the SimpliVity "Save Credentials for VSS" option. 4. Review the bar chart to see the backup consumption level for the Federation on a daily basis and the predicted steady-state level. Then click OK again. Optional: Leave Application Consistent unselected or select it to back up data in a consistent state. Repeat steps 4-8. OmniStack returns to the Edit Policy Rule dialog box. Chapter 9: Backups 99 . delete unnecessary backups and repeat this procedure again. • For the Virtual Machines view. Click Yes if you want to stop the backups for all the virtual machines using that backup policy." This policy is automatically created by HPE SimpliVity Plug-in. You must modify the policy again to reduce the number of backups (such as decreasing the frequency or retention time). You also cannot edit or delete the backup policy named "Fixed Default Backup Policy. Double-click the virtual machine row with the backup policy you want to delete. Repeat steps 5-10. Click the Backup Policy Name link. all virtual machine backups previously created under that policy remain and continue to consume storage space. Do one of the following: • Click Yes to apply your changes if the policy edits keep the consumption levels within an acceptable range. you see a message indicating that automated backups cannot continue without at least one rule. you can check the policy a datastore or virtual machine uses by clicking the object in the HPE SimpliVity federation section of the inventory panel and checking the backup policy listed in the Objects tab. If you do not want to create backups in a datastore that has one policy left. For example.8. you can delete all the rules from the last remaining policy instead. You can also search for backups from the HPE SimpliVity Home tab by selecting Search Backups under the Basic Tasks menu. Click Yes to confirm that you want to delete the selected policy. Click the Summary tab and scroll down to the HPE SimpliVity portlet. Select the backup policy you want to delete. Search for backups Backup searches You can search for manual or policy backups associated with any HPE SimpliVity cluster or virtual machine. click Virtual Machines to open the Objects tab. Do one of the following: • For the Backup Policies view. over 100%). you may need to lower the frequency and retention time. From vSphere Web Client Home. For example. NOTE: If you delete a backup policy. • Click No to return to the Delete Policy Rule dialog box and make the appropriate changes. 2. select Delete Backup Policy. You must manually delete the backups if you want to remove them. you select a cluster or virtual machine and click the HPE SimpliVity Search Backups subtab from the Manage tab. Procedure 1. click Backup Policies to open the Objects tab. Delete a backup policy Procedure overview You can delete a backup policy from a federation when no datastores or virtual machines use it. Or. 4. 3. If you deleted the last rule in the policy. It does not contain rules. If the backups exceed the maximum amount allowed (for example. To perform a search. You cannot delete the last remaining policy for a datastore. click HPE SimpliVity Federation. From the Actions menu. You can see Yes (Default [for snapshot method]). To remove a row of filters. • Unique Size Calculation Time: Time when HPE OmniStack calculated the unique size of the backup. • Sent Duration: Time (in hours. You cannot sort or filter items in this column. • Timestamp: Date and time for the backup to start (in MM/DD/YYYY and hours:minutes format). you may see fields that show the cluster equals Boston. Chapter 9: Backups 100 . or Queued. This includes any time spent in a queued state (for remote backups only). click HPE SimpliVity Federation. • VM State: State of the virtual machine (Active. minutes. Procedure 1. or Failed). click the plus icon ( ). You may want to refine your search to see a limited number of backups. Removed.) It may also include an active row of fields that you can use in your search. Degraded. or locked. or No (for crash- consistent backup). • Type: Created from a policy automatically. You can start the search and refresh the backup list by clicking Search Backups. Rebuilding. From vSphere Web Client Home. Cancelled. Search for backups through the HPE SimpliVity Home tab Procedure overview You can initiate a search for backups from the HPE SimpliVity Home tab or by selecting a Hewlett Packard Enterprise cluster or virtual machine and clicking the HPE SimpliVity Search Backups subtab from the Manage tab. • Sent Size: Size of the backup in physical bytes sent over the network (for remote backups only). you can see a status of New. You can create a search query to find thousands of backups. Or. For example. manually backed up. • Cluster: Name of the cluster where the datastore with the backup resides. (For example. you can use the field drop-down lists to define a different search criteria. or seconds [or all three]) that it took to send the data over the network (for remote backups only). • Backup Name: Name of the backup. You can then set the filters to customize your search. Saving. or Deleted). • Size: Size of the backup. but the screen only shows up to 500 backups at a time. • Unique Backup Size: Unique backup size (if greater than or equal to used). • Status: Current status (for example. Yes (VSS [for Microsoft Volume Shadow Copy Service]). • VM Template: Yes for VM template backups or No for virtual machine backups. • Application Consistent: Application consistent indicator for the backup type and the process used. • Expires: Date and time the backup expires. • Virtual Machine: Name of the virtual machine that had the data backed up. • Sent Completion: Date and total time for the backup to complete from start to finish (in MM/DD/YYYY and hours:minutes format). During the backup process. To add a new filter row. Protected.The HPE SimpliVity Search Backups tab opens with a row of inactive fields that show the object you selected. you can search on any of the items in this list and see them in a table: • Datastore: Name of datastore where the backup resides. click the minus icon ( ). Click Back to HPE SimpliVity Federation to return to the HPE SimpliVity Home tab. Starts with. Once you create and run a search query. From the HPE SimpliVity Home tab. click the minus icon [ ]. select one of the following from the drop-down list: • Cluster: Select Equals. Search for backups through a cluster or virtual machine Procedure overview You can search for a backup through a cluster or virtual machine and refine your search by selecting a search property option. In the active Select a property field (under Filters Applied).) NOTE: Click Search Backups whenever you change a property field to update the search and refresh the screen.2. (You can also double-click the object with the backup you need to access. such as Datastore or Timestamp. From vSphere Web Client Home. Leave the default or select another one from the drop-down list of hours (12:00 AM to 11:00 PM). This search criteria helps you quickly find the backups you need. • Datastore: Select Equals. The list refreshes with the criteria you specified. Chapter 9: Backups 101 . 3. In the Select a property field (under Filters Applied). (Use an asterisk as a wildcard character.) The HPE SimpliVity Search Backups subtab opens with information on the number of filters used to list the backups. Starts with. Click Search Backups. click Search Backups from the Basics Tasks section. Some options open additional fields for you to create a filter equation. or Contains from the drop-down list and type the letters of the name of the cluster you need to locate. the pane opens to that selection the next time the Search Backups task is initiated from the Home tab. Click the Manage tab and click the HPE SimpliVity Search Backups subtab. select a search parameter from the drop-down list. Then click the calendar icon and select a date. You also see inactive fields that show the object you selected. 5. 2.) • Application Consistent: Leave Equals and select Yes (Default) for VMware snapshot. After. The time field defaults to 12:00 AM. Right-click the cluster or virtual machine with the backup you need to access and click All HPE SimpliVity Actions > Search Backups.) • Expires (expiration date): Select Before. Optional: Click the plus icon ( ) to open a new Select a property field. 3. Yes (VSS) for Microsoft Volume Shadow Copy Service. 4. (To remove a property. 4. Click Clusters or Virtual Machines to open the Objects tab. and complete the search criteria based on your requirements. Procedure 1. This opens the Search Backups pane. You can add additional search criteria. or On from the drop-down list. or Contains from the drop-down list and type the letters of the name of the datastore you need to locate. or No for crash-consistent from the drop-down list. (Use an asterisk as a wildcard character. NOTE: The Search Backups pane initially opens with no filters or properties selected. click HPE SimpliVity Federation. 6. Then click the calendar icon and select a date. Manage backups Manage backups An HPE OmniStack host has a limited number of backups that it can create and store or transmit and receive from a cluster. MB. • Virtual Machine: Select Equals. (Use an asterisk as a wildcard character. Enter a number for the size and select KB. The time field defaults to 12:00 AM. • Unique Backup Size (size of the data processed and stored by the virtual machine): Select Greater than or Less than from the drop-down list. Degraded. • VM State: Leave Equals and select Active. or Contains from the drop-down list and type the letters of the name of the virtual machine you need to locate.) 5. Starts with. Removed from Inventory. • Name (backup name): Select Equals. GB. GB. Saving. or Delete from Disk from the drop-down list. MB. Deleted. • Type (backup type): Leave Equals and select Policy.000 • Maximum total backups: 250. Click Search Backups. Enter a number for the size and select KB. (Use an asterisk as a wildcard character. Failed. click the minus icon [ ]. Optional: Click the plus icon ( ) to open a new Select a property field. or TB from the drop-down list. The list refreshes with the criteria you specified. You can add additional search criteria by selecting it from the drop-down list. or Rebuilding from the drop-down list. (To remove a property. Starts with. MB. or TB from the drop-down list. Enter a number for the size and select KB. or TB from the drop-down list. • Size (backup size): Select Greater than or Less than from the drop-down list. • Status: Leave Equals and select New. Leave the default or select another one from the drop-down list of hours (12:00 AM to 11:00 PM). or Contains from the drop-down list and type the letters of the name of the backup you need to locate. The backup limits for an HPE OmniStack host are: • Simultaneous local backups: 100 • Simultaneous backups transmitted to another datacenter: 50 • Simultaneous backups received from another datacenter: 100 A SimpliVity Federation is also limited to a maximum amount of backups that it can create and store: • Maximum daily backups: 725. After. GB. or Locked from the drop-down list.) • Sent Size (physical bytes sent): Select Greater than or Less than from the drop-down list. 6. Protected. Queued. • Timestamp: Select Before. Manual.) NOTE: Click Search Backups whenever you change a property field to update the search and refresh the screen. Chapter 9: Backups 102 . Canceled.000 The daily limit is larger than the total limit because of policies that may use very low backup frequencies or short retention times (less than eight hours). or On from the drop-down list. or Rebuilding). • Timestamp and size of the backup. Queued. or Locked). Degraded. and you cannot modify or delete it. Saving. you also see the method used to create the backup ("Default" for VMware snapshot or "VSS" for Microsoft Volume Shadow Copy Service). • Bytes sent over the network. Deleted from disk). • Expiration date and time. Chapter 9: Backups 103 . you can reduce the number of backups created by modifying the backup policies and decreasing the frequency or retention time. • Status (New. To monitor the percentage of daily backups created and stored and see the percentage of projected steady- state backups the current policies can create and store in a Federation. 2. This policy has no rules. Click Clusters or Virtual Machines to open the Objects tab. • Virtual machine template indicator (Yes or No). • Unique backup (if greater than or equal to the used size) • Time when the unique size was calculated. The Hewlett Packard Enterprise Home tab also contains a Search Backups option to open the Search Backups tab. View backups Procedure overview You can view backups at any time. the new virtual machine can use it. Manual. and backup name. Protected. Canceled. access the Backup Consumption tab. You may also see: • Application consistent status (Yes or No). virtual machine. if you need to see details on the backups of a cluster or virtual machine.When you create the first datastore in a cluster. If necessary. From vSphere Web Client Home. if the datastore default policy prevents the backups from exceeding the limit. OmniStack can create more backups and you can assign different policies to new virtual machines. • Cluster name. NOTE: You can view up to 500 backups at a time. • Virtual machine state (Active. Failed. The Fixed Default Backup policy prevents the new virtual machine from creating more backups. If you create a new virtual machine and try to assign a policy to it that causes the backups to exceed the maximum daily or total number of backups allowed. If not. click HPE SimpliVity Federation. Some of the details you can see right away are the datastore. Once the backups do not exceed the limits. If Yes. For example. HPE OmniStack automatically assigns the datastore default policy or the Fixed Default Backup policy to the new virtual machine. Procedure 1. HPE OmniStack creates a default backup policy called the Fixed Default Backup policy. For example. the new virtual machine must use the Fixed Default Backup policy. you can search the Hewlett Packard Enterprise backups for those objects and find the backup you need. • Type (Policy. 5. Click the SimpliVity Search Backups subtab or link (depending on your version of vSphere). depending on how you want to search for a backup to open the Objects tab. The new name appears in the Backup Name column. Rename a backup Procedure overview Use the following steps to rename a backup. (To remove a property. click Search Backups. click the minus [-] button. Click the Manage or Configure tab (depending on your version of vSphere). NOTE: You can also view backups for a datastore by double-clicking the cluster containing the datastore. you can view backups for a datastore by creating a filter with a certain datastore name. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). 3. Select the row with the backup you want to rename. 3.) NOTE: Click Search Backups whenever you change a property field to update the search and refresh the screen. Optional: If you need to filter the backups listed. 7. Double-click the object (cluster or virtual machine) with the backup you need to access.) Once you set up your filters. 5. and then filtering the backups based on the datastore. Enter the new backup name and click OK. 6. 2. 4. Click Clusters or Virtual Machines. click the plus (+) button to open a Select a property field. Click Backup Actions > Rename Backup. (For example. 4. click HPE SimpliVity Federation. Select the property you want to use to set up filtering equations to search for backups. Click the Manage or Configure tab (depending on your version of vSphere). 9. click the plus (+) button to open a Select a property field. Select the property you want to use to set up filtering equations to search for backups. Optional: If you need to filter the backups listed. You also see inactive fields that show the cluster or virtual machine you selected. Rename a backup of a VM template Procedure overview Use the following steps to rename a backup of a virtual machine template. Double-click the object with the backup you need to access. Click Search Backups to refresh the view. Procedure 1. Procedure Chapter 9: Backups 104 . click Search Backups. 8. 10. clicking Manage > SimpliVity Search Backups. The list refreshes with the criteria you specified. The tab populates with information on the number of filters used to list the backups (up to 500 backups at a time). 6. Once you set up your filters. From vSphere Web Client Home. Click Backup Actions > Rename Backup. Chapter 9: Backups 105 . The countdown to delete it starts immediately after HPE OmniStack creates the backup. Click the Manage or Configure tab (depending on your version of vSphere). From vSphere Web Client Home. 10. Click OK. 7. click Search Backups. For example. 9. Ends with. (You can set a maximum time of 20 years. 7. From vSphere Web Client Home. Procedure 1. Double-click the cluster with the backup you need to access. Once you set up your filter. 11. 5. For example. Once you set up your filters. Click Clusters or Virtual Machines to open the Objects tab. Select the property you want to use to set up filtering equations to search for backups. enter a number and select Minutes. 6. 2. Click Clusters to open the Objects tab. This opens the Set Backup Retention Time dialog box. Hours. Enter the new backup name and click OK. you can enter all or part of the name of the template. Changing the retention time changes the lifetime of the backup and can make some backups delete automatically. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). or Contains and enter all or part of the VM template name. However. 6. Starts with. if the current retention time is three weeks and you change the retention time to two weeks. 9. When the retention time expires. you can select Virtual Machine from the property drop-down menu. click HPE SimpliVity Federation. click the plus (+) button to open a Select a property field. Set the retention time for a backup Procedure overview The retention time is the length of time to preserve a virtual machine backup.) 10. Optional: If you need to filter the backups listed to find the VM template backups . 3. Scroll to the right of the table to view the VM Template column. Weeks. Select the row with the backup you want to change.1. 8. Optional: If you need to filter the backups listed. The new name appears in the Backup Name column. Double-click the object with the backup you need to access. 4. 2. 4. Days. Months. The Expires column shows the current expiration date based on the creation timestamp and current retention time. Click the Manage or Configure tab (depending on your version of vSphere). Click Backup Actions > Set Retention Time. In the Retain Backups For field. You can change the retention time for one backup or more at any time. The column shows Yes to indicate a VM template backup or No for a virtual machine backup. It lists the backup name. click Search Backups. Select the row with the backup you want to rename. click HPE SimpliVity Federation. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). HPE OmniStack automatically deletes the backup. HPE OmniStack deletes the backup if it is already older than two weeks. or Years from the drop-down list. you see a prompt to cancel or confirm the deletion process. 8. 5. 3. select Equals. Click Search Backups to refresh the view. If you changed the time to a value that deletes the backup immediately. 4. 5. 2. Click Backup Actions > Lock Backup. when you lock a backup. Chapter 9: Backups 106 . Click OK to confirm the deletion process or Cancel to stop it. Lock a backup Procedure overview You can lock any policy (automatic) or manual backup that includes an expiration date to prevent it from being deleted. For example. Click the Refresh icon ( ) in the title bar to see the new Expires setting of Never for the backup you locked. This excludes it from getting deleted during the cleanup process. select it and click Backup Actions > Set Retention Time and assign a new time. This excludes it from getting deleted during the cleanup process. Once you set up your filters. you can rename the backup or restore files from it. select the backup from the Search Backups list and click Backup Actions > Lock Backup.) Lock a backup of a VM template Procedure overview You can lock any policy (automatic) or manual backup that includes an expiration date to prevent it from being deleted. Click Clusters or Virtual Machines to open the Objects tab. click the plus (+) button to open a Select a property field. You can still perform backup tasks on a locked backup. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). 7. 10. Optional: If you need to filter the backups listed. 3. Select the property you want to use to set up filtering equations to search for backups. 6. (The Timestamp shows the creation date and time. For example. if you set the retention time as seven days. you can lock it instead of changing the retention time. when you lock a backup. Double-click the object with the backup you need to access. 9. If you do not lock it. For example. From vSphere Web Client Home. the expiration date changes to Never. For example. NOTE: To unlock a backup. 8. the countdown to delete the backup within seven days starts right after HPE OmniStack creates the backup. Click Yes when prompted if you want to exclude the backup from the scheduled cleanup. This changes the Expires setting from Never to a set date. click Search Backups. The backup must have a date in the Expires column to lock it. you see the Set Backup Retention Time Confirmation dialog box. HPE OmniStack deletes it when the backup reaches its expiration date (retention time). NOTE: If you want to set a backup to never expire. click HPE SimpliVity Federation. the expiration date changes to Never. If you do not lock it. To lock a backup. HPE OmniStack deletes it when the backup reaches its expiration date (retention time). Procedure 1.11. Select the row with the backup you want to lock. Click the Manage or Configure tab (depending on your version of vSphere). Once you set up your filter. Click Yes when prompted if you want to exclude the backup from the scheduled cleanup. Click the Refresh icon ( ) in the title bar to see the new Expires setting of Never for the backup you locked. the countdown to delete the backup within seven days starts right after HPE OmniStack creates the backup. 4. select the backup you need. Click Clusters to open the Objects tab. Click Backup Actions > Lock Backup. 5. 6. For example. Ends with. click the plus (+) button to open a Select a property field. Procedure 1. For example. 9. Click the Manage or Configure tab (depending on your version of vSphere). For example. if you need printed details on the backup of a cluster or virtual machine. From vSphere Web Client Home. 10. 3. The backup must have a date in the Expires column to lock it. and use the Export Backups option to save the information in a spreadsheet format. Procedure 1. 8. Select the row with the backup you want to lock. you can search the HPE SimpliVity backups for any of those objects. 2. The column shows Yes to indicate a VM template backup or No for a virtual machine backup. This changes the Expires setting from Never to a set date. Starts with. From vSphere Web Client Home. or Contains and enter all or part of the VM template name. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). Optional: If you need to filter the backups listed to find the VM template backups . NOTE: To unlock a backup. Scroll to the right of the table to view the VM Template column.You can still perform backup tasks on a locked backup. click HPE SimpliVity Federation. Optional: If you need to filter the backups listed. you can rename the backup or restore files from it. 11. 4. Once you set up your filters. 7. select it and click Backup Actions > Set Retention Time and assign a new time. For example. Chapter 9: Backups 107 . select Equals. Double-click the object with the backup you need to access. (The Timestamp shows the creation date and time. 6. click HPE SimpliVity Federation. Click the Manage or Configure tab (depending on the your version of vSphere). click Search Backups.) Export a backup Procedure overview You can export backup information to a CSV file at any time. Click the HPE SimpliVity Search Backups subtab or link (depending on your versino of vSphere). click Search Backups. 5. 3. 2. Double-click the cluster with the backup you need to access. you can select Virtual Machine from the property drop-down menu. you can enter all or part of the name of the template. if you set the retention time as seven days. Select the property you want to use to set up filtering equations to search for backups. Click Clusters or Virtual Machines to open the Objects tab. The file includes the same backup information shown on the Search Backups screen (datastore. you can lock the local copy to preserve it from automatic deletion under the backup policy rules. Click Backup Actions > Export Backups. Check the vCenter IP address too in case the cluster uses a duplicate name. NOTE: HPE SimpliVity Plug-in saves the CSV file with a name that includes these details: SimpliVity_Backups_year_month_date_hour_minutes_seconds. Chapter 9: Backups 108 . 4. Optional: If you need to filter the backups listed. vCenter IP address. and creation time. 8. This opens the Copy Backup dialog box. 6. Select the row with the backup you want to export. Select the row with the backup you want to copy to another cluster. Copy a VM template backup to another cluster Procedure overview You can copy a backup of a virtual machine template to another cluster in the same vCenter or another vCenter with Linked Mode for additional protection. 8. Once you set up your filters. 10. 9. virtual machine name. NOTE: If you are copying the backup to preserve an additional copy. enter a word that appears in the cluster name or the vCenter IP address you need to find. current backup location. In the Destination Cluster field. Copy a backup to another cluster Procedure overview You can copy a backup to another cluster in the same vCenter or another vCenter (if using vCenter Linked Mode) for additional protection. click the cluster where you want to copy the backup. Click Backup Actions > Copy Backup. 3. NOTE: To use a filter to locate a cluster or vCenter. Click OK. Click Clusters or Virtual Machines to open the Objects tab. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). Double-click the object with the backup you need to access. 9. 7. Click the Manage or Configure tab (depending on your version of vSphere). 2. Browse to the location you where you want to export the file and click Save. and so on). Select the property you want to use to set up filtering equations to search for backups. click the plus (+) button to open a Select a property field. It lists the original virtual machine and datastore.7. click Search Backups. Procedure 1. click HPE SimpliVity Federation. backup name. 5. From vSphere Web Client Home. 3. For example. NOTE: To use a filter to locate a cluster or vCenter. Click Clusters or Virtual Machines to open the Objects tab. or Contains and enter all or part of the VM template name. Select the row with the backup you want to copy to another cluster. Click OK. Select the property you want to use to set up filtering equations to search for backups. 5. Check the vCenter IP address too in case the cluster uses a duplicate name. This opens the Copy Backup dialog box. click the plus (+) button to open a Select a property field. you may want to cancel another backup. 7. 9. click HPE SimpliVity Federation. Ends with. 8. if you notice the backups reaching the recommended limit of 250. Chapter 9: Backups 109 . 6. current backup location. 2. Procedure 1. enter a word that appears in the cluster name or the vCenter IP address you need to find. Then you can delete unnecessary backups before you continue to create more. backup name. 6. you can enter all or part of the name of the template. 2. you can lock the local copy to preserve it from automatic deletion under the backup policy rules. For example.NOTE: If you are copying the backup to preserve an additional copy. Click Backup Actions > Copy Backup. 5. From vSphere Web Client Home. click HPE SimpliVity Federation. Procedure 1. Scroll to the right of the table to view the VM Template column. Click Clusters to open the Objects tab. The column shows Yes to indicate a VM template backup or No for a virtual machine backup. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). Optional: If you need to filter the backups listed. Once you set up your filter. Optional: If you need to filter the backups listed to find the VM template backups . Once you set up your filters. It lists the original virtual machine and datastore. In the Destination Cluster field. and creation time. click Search Backups. Click the Manage or Configure tab (depending on your version of vSphere). From vSphere Web Client Home. you can select Virtual Machine from the property drop-down menu. Cancel a backup Procedure overview You can cancel a backup in process (in the New. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). click the cluster where you want to copy the backup. 3. Double-click the object with the backup you need to access. Click the Manage or Configure tab (depending on your version of vSphere).000 backups. 4. vCenter IP address. or Queued status). select Equals. Double-click the cluster with the backup you need to access. 11. Starts with. 4. click Search Backups. 10. Saving. hold down the Ctrl key and click individual rows. Therefore: Chapter 9: Backups 110 . Click the Manage or Configure tab (depending on your version of vSphere). click Search Backups. If you see the backup has a status of Saving. 3. The list refreshes and no longer shows the backups you deleted. but shares 90 GB with VMBackup-2 and the source virtual machine. For example. You then take another backup.7. Procedure 1. click the plus (+) button to open a Select a property field. 9. Delete a backup Procedure overview You can delete one or more backups at any time. Click Backup Actions > Delete Backups. the backup may complete the save process and remain stored. 8. Hewlett Packard Enterprise recommends storing 250. Click Yes when prompted. click HPE SimpliVity Federation. To select more than one item. you can delete unnecessary or expired backups to make room for new backups. 9. NOTE: If you attempt to delete a remote backup (for example. Select the row with the backup you want to cancel. 4. if you have a 100 GB virtual machine (the source virtual machine). This calculation indicates the amount of physical space recoverable if you decide to delete or move the backup.m. 6. cancel the Saving process first and then delete the backup. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). To refresh the screen and see the status of the backup change to Canceled. Select the row with the backup you want to delete. Click Yes when prompted. 2.m. VMBackup-2.000 backups or less for the best performance. at 12:00 p. 7. Double-click the object with the backup you need to access. VMBackup-1 has a logical size of 100 GB. click Search Backups. Optional: If you need to filter the backups listed. 8. hold down the Shift key to select a contiguous group of rows. Unique data in backups You can obtain an estimate of the amount of unique data in a virtual machine backup. Or. Once you set up your filters. a backup that resides in a cluster other than the local one) and the backup had a status of Saving. Click Clusters or Virtual Machines to open the Objects tab. Deleting unique data frees up physical space. For example. From vSphere Web Client Home. if you know you are running out of storage space. where you take VMBackup-1 at 10:00 p. 5. You then run the source virtual machine and 10 GB of data is modified in the data files. Click Backup Actions > Cancel Backups. NOTE: Recent virtual machine backups tend to contain a smaller amount of unique data compared to older backups. Select the property you want to use to set up filtering equations to search for backups. • Ensure the backup policy rules are creating an optimum number of backups. Also. reclaimed physical space is available within a few minutes of deleting an unwanted backup. • Manually calculate (or recalculate) the unique data size of an individual backup. with higher rates of I/0. However. You can also • Delete any unwanted virtual machines that are already removed from inventory. • VMBackup-2 has a logical size of 100 GB. because its data content is equivalent to the source virtual machine at that point in time. The value calculated for unique data is a close estimate of the actual on-disk value and is accurate only at the point-in-time that you initiate a calculation. On an active federation. The freed space might not be available immediately. Alternate methods of reclaiming physical space Deleting backups is only one of a number of methods of freeing up physical space. NOTE: In a new federation. you might have a large number of virtual machine backups that contain very little unique data. it can take some time before reclaimed space resolves any current cluster storage capacity alarm conditions such as:\ Hewlett Packard Enterprise Clust physical capacity is running low. Consequently. You must delete them manually. Backups created manually do not expire. but contains 0 (zero) bytes of unique data at 12:00 p. Usage: <Percent Used>%. • Move virtual machines to locations with more available resources. NOTE: Backups created with a policy use retention rules to expire.. The size and timestamp will show as never and unknown if the backup size has never been calculated for a specific virtual machine. corresponding to the 10 GB change in the source virtual machine between 10:00 p.m. • Delete any existing surplus virtual machines such as test virtual machines or clones. and 12:00 p. On a federation with typical or lower rates of I/O.m. such as deleting unwanted virtual machines from inventory. locating backups to delete might be less effective than other methods of reclaiming storage space. it might take some time for the reclaimed physical space to be represented in the Logical Capacity and Physical Capacity panels. • Clean up backups with a DELETED status while retaining the minimum required for recovery according to your recovery point objective. or for virtual machines recently added to an established federation. you should expect the value to be reasonably close to the amount of free physical space that you can reclaim by deleting the backup. You can: • View the most recently calculated unique size of an individual backup. • Reduce backups of current virtual machines to an optimum level. Calculate unique backup size Procedure overview Chapter 9: Backups 111 . The process of calculating unique data consumes system resources and might result in a noticeable decrease in I/O performance and slower federation response times. provided you do this within minutes of initiating a calculation. which also includes a timestamp of when the size estimate was calculated.• VMBackup-1 contains 10 GB of unique data.m. 8. Double-click the object with the backup you need to access. Click Backup Actions > Calculate Unique Backup Size. (You may need to click the Refresh icon [ ] at the top of the application. 3. click HPE SimpliVity Federation. 9. Create a new virtual machine or VM template from a backup Procedure 1. Click Clusters or Virtual Machines to open the Objects tab. Double-click the object with the backup you need to access. You see a prompt indicating that the calculation process can impact I/O. You can also see the date and time in the Unique Size Calculation Time column.You can calculate the unique size of a backup. 10. right-click the row and select Delete Backup. Click the Manage or Configure tab (depending on your version of vSphere). 3. Click Yes to confirm that you want to proceed with the calculation. Chapter 9: Backups 112 .) When the calculation finishes. 7. This helps you see how much free space you can recover if you decide to delete (or move) the backup. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). Once you set up your filters. Then select the row with the backup where you need to calculate the unique data. or VM Templates to open the Objects tab. Procedure 1. Optional: If you need to filter the backups listed. For example. Select the property you want to use to set up filtering equations to search for backups. click HPE SimpliVity Federation. 11. 4. • Replacing the data on an existing virtual machine or VM template with the data from another backup. Click the Refresh icon ( ) to update the list of backups. 5. Click the Manage or Configure tab (depending on your version of vSphere). From vSphere Web Client Home. Virtual Machines. From vSphere Web Client Home. 4. Restore HPE SimpliVity backups Backups restorations Restore a backup by: • Creating a new HPE SimpliVity virtual machine or VM template from a backup. you may want to do this to calculate the amount of unique data in a backup. Wait for the unique backup size and time of calculation appear with a Completed status in the Recent Tasks panel. scroll to the right of the Search Backups chart to view the value in the Unique Backup Size column. click the plus (+) button to open a Select a property field. 5. • Restoring one or more files or folders from a backup of a virtual machine and copying them to the same or a different virtual machine. click Search Backups. 2. If you want to delete the backup. Click Clusters. 6. 2. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). enter the name in the search field to access it. 12. click the plus ( ) button to open a Select a property field. In the New Virtual Machine Name or New VM Template Name field. Select the property you want to use to set up filtering equations to search for backups. Select the property you want to use to set up filtering equations to search for backups. datastore that contains the backup. 9. virtual machine that was backed up. click Search Backups. Select the row with the backup you want to use to replace the data on the virtual machine. Click Backup Actions > Restore Virtual Machine or Restore VM Template. 10. In the Destination Cluster field. Click Yes to confirm that you want to change the data on the selected virtual machine or template. and cluster for the datastore. Optional: If you need to filter the backups listed.6. Select Replace existing virtual machine or Replace existing VM Template to replace the data on the virtual machine or template you selected with the data from the backup you selected. original datastore that contains the backup. leave the current name or enter a new one (up to 80 characters). Optional: If you need to filter the backups listed. 4. 9. The list refreshes with the criteria you specified. original name of the virtual machine or template that was backed up. Replace a virtual machine or VM template with a backup Procedure 1. Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere). 5. If you do not see the datastore you need. leave the current cluster or select another one from the drop-down menu. 11. 3. Leave Create a new virtual machine or Create a new VM template selected to use the backup to create a new virtual machine or template. 6. (The virtual machine powers off during the restore process. Once you set up your filters click Search Backups. When you view a list of virtual machines or templates through the Objects tab. ]. [. From vSphere Web Client Home. 7. When done. time of backup. Double-click the object with the backup you need to access. The Restore dialog box opens with details on the history of the backup. click the HPE SimpliVity Search Backups subtab or link to see the backup listed for the virtual machine or template you selected. you see the new virtual machine or template in the list with the name you chose. Once you set up your filters. \. 11. Select the row with the backup you want to use to restore the virtual machine or template. It includes details on the backup name. and IP address of the vCenter Server. cluster for the datastore.) 12. 2. Chapter 9: Backups 113 . 8. Click Backup Actions > Restore Virtual Machine or Restore VM Template. 7. /. The Restore dialog box opens with details on the history of the backup. %) and use underscores or dashes between words instead of spaces. click the plus ( ) icon to open a Select a property field. Avoid special characters (for example. Click Clusters. Click OK. Virtual Machines. 10. click HPE SimpliVity Federation. or VM Template to open the Objects tab. It includes details on the backup name. 8. Click the Manage or Configure tab (depending on the your version of vSphere). time of backup. Click OK. browse to the last good version of the file. 2.Restore files from a backup You can restore files or folders (one or more) to a virtual machine associated with the backup. You must start the Restore Files wizard again. You cannot continue where you left off in the restoration process. the wizard appears in the Work In Progress panel until you click it again. • File and folder permissions are not preserved when the ISO image of the restored file appears on the target virtual machine. Chapter 9: Backups 114 . log out of vSphere Web Client. you can locate the backup for that virtual machine. or spanning for file systems. (The virtual machine must use a Windows operation system to restore files. From vSphere Web Client Home. and restore it. Optional: If you need to filter the backups listed. The end user (or administrator) can copy the restored file from the target virtual machine to a preferred location. You can then continue through the wizard. 6. The ISO image of restored content cannot contain files and folders on non-native NTFS partitions that use Windows RAID. • The restored image only remains on the target virtual machine as an ISO image on the DVD drive for 24 hours (based on the image creation timestamp). Click the HPE SimpliVity Search Backups subtab or link (depending on your version of vSphere).dll files. NOTE: In a ROBO environment. Procedure 1. Procedure overview If a file becomes corrupt on a virtual machine. if you minimize the Restore Files wizard. • Select files and folders on native NTFS partitions only. For more information. • Do not restore from Junction Point folders (folders acting as an alias or symbolic link to a directory). registry or . click HPE SimpliVity Federation. click the plus ( ) icon to open a Select a property field. Once you set up your filters click Search Backups. striping. 3. 5. However. refer to the third-party documentation for your applications or contact SimpliVity Customer Support. such as Self-certifying File System (SFS). Click the Manage or Configure tab (depending on your version of vSphere). The OmniStack software deletes it after that time. if the selected backup originated from a spoke. • If you minimize the Restore Files wizard to pause the restoration process. the Work In Progress panel appears empty. file level restore can only take place between the hub and spoke and not between spokes. you can only restore files to Windows virtual machines located in the hub cluster or in the cluster of the selected backup. and log back in. Select the property you want to use to set up filtering equations to search for backups. The restored file appears as an ISO image on the DVD drive of the target virtual machine. You can restore files to any Windows virtual machine in any SimpliVity cluster in the Federation if the selected backup originated from the hub. Double-click the virtual machine with the backup you need to access. But. This includes access masks and file ownership. Only the user authorized to access the target virtual machine (or an administrator) can access the restored content. Before you begin • The target VM for the restored files must be powered on. Click Virtual Machines to open the Objects tab.) 4. • Do not restore core Windows operating system files such as boot. Select the row with the backup that contains the files or folders you need to restore. NOTE: The Restore Wizard displays the total known size of selected files. Unmount the DVD with the ISO image. The user (or you) must copy the restored image to a preferred location within 24 hours. However. 13. Review the Source Information about the backup and the Target Information about the virtual machine receiving the restored files. The Restore Files wizard opens. 15. 14. Select the checkbox next to the file or folder you need to restore. the Destination Cluster field lists the cluster associated with the backup. datastore it uses. 9. not dynamic • Basic Master Boot Record (MBR) disks. change your selection before you continue to ensure the restore process succeeds. 12.) Click Next. Review the Size column to check the size of the files you selected. Expand the . Notify the end user that the restored files reside on the DVD drive as an ISO image on the target virtual machine.7. you see an error message to make another selection. OmniStack automatically unmounts it and deletes the ISO image from the Virtual Controller after 24 hours to ensure other restored files can reside on the virtual machine (if necessary). 16. Click Next to open the Select Destination screen. NOTE: By default. (You can only expand partitions with mountable files. It lists the virtual machine name. you do not see an error message if you select a folder that exceeds the limit. You can determine the total known size of a selected folder by opening the folder (and any subfolders) to the file level. provisioned space on the datastore. not dynamic Chapter 9: Backups 115 . You must do this before you restore files from the same backup or destination to successfully complete the next restoration process. You can monitor the progress through the Recent Tasks panel. Click Backup Actions > Restore Files. but not folders. 8. if you select a file that exceeds 32 GB. you see a list of available virtual machines appear in a table. Disk and partition configurations compatible with restoring individual files The following disk and partition configurations are compatible with File Level Restore. Click Finish.vmdk disc and then the NTFS Partition that contains the files and folders in the backup. NOTE: If you do not unmount the image. Select the virtual machine where you want to restore the files. 11. select the cluster where the target virtual machine resides from the drop- down list. but you can only restore up to 32 GB of content. There is no limit to the number of files and folders you can select. If necessary. and used space. In the Destination Cluster field. For example. (The restored file appears as an ISO image on the DVD drive of the virtual machine you select. In a ROBO configuration only clusters connected to the cluster that the backup is associated with are available from the drop-down list. Click Next to open the Select Files screen. NOTE: Wait until the restoration task finishes before attempting to restore another file. • Basic GUID Participation Table (GPT) disks. Once you select a cluster.) 10. This is volume specific. • Partitions used by Microsoft's Clustered Storage Spaces . • Microsoft Reserved Partitions. and ReFS partitions. • Do not attempt to restore the System Volume (C:\). 16K. Before you begin: When performing this procedure on a guest VM: • Microsoft Volume Shadow Copy Service (VSS) based backups. • When you enable deduplication on a Microsoft Windows 2012 server. Microsoft Windows does not need to convert the disk to a dynamic disk. About restoring VSS backups Microsoft Volume Shadow Copy Service (VSS) based backups are restored by first restoring the virtual machine to create a new VM and then identifying and reverting the shadow copy volumes or individual files. ◦ Mirrored. 4K. • Encrypted partitions. • EISA partitions. NOTE: Partitions can be expanded as long as there is empty space on the disk immediately after the partition. • FAT. and 64K block sizes • Partition sizes greater than 2 TB • Virtual disks with Change Block Tracking (CBT) enabled Disk and partition configurations that are NOT compatible with restoring individual files The following disk and partition configurations are NOT compatible with File Level Restore. File Level Restore will work for new backups. Chapter 9: Backups 116 . so File Level Restore only stops working on the volume that has the deduplication feature enabled. When the volume is no longer deduplicated. • Be sure to restore all non-c:\ volumes used by the SQL database. exFAT. ◦ Partitions expanded to non-contiguous seconds of disk. Verify that applications such as SQL Server as well as any applications writing to the SQL database are stopped. or RAID partitions. File Level Restore stops working. FAT32. Failing to do so leaves the database in an inconsistent state. Spanning.• Disks with multiple partitions • Primary partitions on MBR • Logical Drives on extended partitions on MBR • Compressed Volumes • New Technology File System (NTFS) partitions ◦ Including with non-default block sizes ◦ Explicitly tested with 1K. Striped. • Linux partitions are not officially supported and not well tested. but so sometimes work. • Dynamic Disks (either GPT or MBR). In this case. 8/3/2016 5:41 PM 9106 cmd_2016-08-03T21-41-33.ps1 C:\OmniStackBackup\backup_3e3f125c-b201-4002-baf4-fd41e6823217> diskshadow Microsoft DiskShadow version 1.ps1 PowerShell script. the backup directory is \OmniStackBackup\: cd c:\OmniStackBackup\backup_3e3f125c-b201-4002-baf4-fd41e6823217 2. In this example.0 Copyright (C) 2013 Microsoft Corporation On computer: WIN-0794DN22RK5. • Revert individual files by making the shadow copy visible as another drive and copying individual files from the shadow copy to the original volume. Procedure Restore the virtual machine using svt-backup-restore. • Identify the shadow copies to be restored.err -a--. Restore an entire virtual machine Procedure overview Restore an entire virtual machine using svt-backup-restore to create a new VM. 8/3/2016 5:41 PM 250 shadowcopy. Copy the name of the "cab" file for use in later steps: C:\OmniStackBackup\backup_3e3f125c-b201-4002-baf4-fd41e6823217> dir Directory: C:\OmniStackBackup\backup_3e3f125c-b201-4002-baf4-fd41e6823217 Mode LastWriteTime Length Name ---. The following example creates a new virtual machine with volumes that are in a post-quiesced state: svt-backup-restore --vm Win2k12 --datastore DS1 --backup NyBackup --name Restored_Win2k12A new VM Restored_Win2k12 Revert shadow volumes using diskshadow utility Use the diskshadow utility on the guest virtual machine to revert volumes. ---- -a--.cab -a--. 8/3/2016 5:41 PM 5319 shadowcopy. Procedure 1. 8/3/2016 6:05:21 PM Chapter 9: Backups 117 .This process includes the following tasks: • Restore an entire virtual machine using svt-backup-restore. 8/3/2016 5:41 PM 295057 2016-08-03_17-41-50_WIN-0794DN22RK5. -----.out -a--. Locate the backup information in its known location. 8/3/2016 5:41 PM 0 cmd_2016-08-03T21-41-33. ------------. • Revert the selected volumes using either the diskshadow utility or the revert.dsh -a--. The following example shows the E volume reverted using the shortcut %VSS_SHADOW_2%: Chapter 9: Backups 118 .Original count of shadow copies = 4 .3.Creation time: 8/3/2016 5:41:49 PM . Alias VSS_SHADOW_SET for value {b948cf13-a6c2-464e-89f9-a6f175cb3bef} set as an environment variable.Originating machine: WIN-0794DN22RK5 . Load the metadata file you identified in the previous step so that you can use the short cuts: DISKSHADOW> load metadata 2016-08-03_17-41-50_WIN-0794DN22RK5.Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5} .Original volume name: \\?\Volume{796f6e1a-5727-4140- acf7-9037c0b3f107}\ [F:\] . 4.Originating machine: WIN-0794DN22RK5 .Original volume name: \\?\Volume{dba16e9c-25ff-4c19-8a5d- a862cf0872d3}\ [E:\] . Identify the Volume Shadow Copies Available. * Shadow copy ID = {b63bcdc9-0f35-4d32-b773-088f1e3cc066} %VSS_SHADOW_2% .Attributes: No_Auto_Release Persistent Differential Number of shadow copies listed: 5 5. The output in the following example is truncated to show only one volume: DISKSHADOW> list shadows all Querying all shadow copies on the computer . Revert the volume using the shortcut.Attributes: No_Auto_Release Persistent Differential * Shadow copy ID = {6b8a3615-50b3-462e-a443-1a2e3bf34804} %VSS_SHADOW_3% ..Not exposed .Shadow copy device name: \\?\GLOBALROOT\Device \HarddiskVolumeShadowCopy3 .Creation time: 8/3/2016 5:41:49 PM .Shadow copy set: {b948cf13-a6c2-464e-89f9-a6f175cb3bef} %VSS_SHADOW_SET% ..Shadow copy device name: \\?\GLOBALROOT\Device \HarddiskVolumeShadowCopy4 .Not exposed .Service machine: WIN-0794DN22RK5 . Alias VSS_SHADOW_4 for value {633c6f9f-c968-490b-a0c0-dc24ec4f153c} set as an environment variable.cab Alias VSS_SHADOW_1 for value {f8a98281-7a21-4eec-8ee5-198b7ce78023} set as an environment variable.Shadow copy set: {b948cf13-a6c2-464e-89f9-a6f175cb3bef} %VSS_SHADOW_SET% .Service machine: WIN-0794DN22RK5 . Alias VSS_SHADOW_2 for value {b63bcdc9-0f35-4d32-b773-088f1e3cc066} set as an environment variable. Alias VSS_SHADOW_3 for value {6b8a3615-50b3-462e-a443-1a2e3bf34804} set as an environment variable.Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5} .Original count of shadow copies = 4 . . Prints out an error if a problem is found with the database.. list. revert. The revert script has five optional flags: version. Restart all applications once the restore completes.ps1 PowerShell script. Chapter 9: Backups 119 . • The VSS revert operation can only be performed once. If you have made changes to those volumes since the shadow copies were made. and cleanup. Revert shadow copy volumes using PowerShell script Procedure overview Use the revert. verify that applications such as SQL Server as well as any applications writing to the SQL database are stopped. WARNING: There are several things to consider before using the revert. those changes will be irretrievably lost. • Any databases stored on the system drive (typically the C: drive) will not be recovered as part of the reverting of the shadow copies. 6. Option Description -checkdb Runs DBCC CHECKDB on all databases for all instances on the local system.ps1 PowerShell script to revert shadow copy data after a backup has been restored. The list and cleanup switches can only be used when the revert is performed. checkdb. WARNING: Before reverting the volume. • All data stored on the volumes other than the system disk (volume) will be replaced with data from shadow copies when the volumes are reverted. The volume was successfully reverted to the shadow copy. DISKSHADOW> revert %VSS_SHADOW_2% -> %VSS_SHADOW_2% = {b63bcdc9-0f35-4d32-b773-088f1e3cc066} Reverting to shadow copy ID {b63bcdc9-0f35-4d32-b773-088f1e3cc066} on volume \\? \Volume{dba16e9c-25ff-4c19-8a5d-a862cf08 72d3}\ from provider {b5946137-7b9f-4925-af80-51abd60b20d5}. The shadow copy is deleted. Shadow copy attributes: [0x00420009]. and can’t be undone. All connections to the SQL server will be forcibly terminated. Repeat this for every volume for which you made a shadow copy except possibly c:\ and the unnamed partition. • All instances of SQL Server will be stopped before reverting the shadow copies. This may cause inconsistencies between databases on the system drive and databases on the volumes to be reverted. This can take a very long time for large databases. 7. If the VSS backup had to restart.CAB file used to find the list of shadows and all unused shadow copies that were found in the manifest file. -revert Discovers all the . The VSS backup process creates a subdirectory in the %SystemDrive%:\OmniStackBackup directory. use the diskshadow. The VSS copy replaces the original volume. The subdirectory is cleaned as part of the backup process. but will be present after a restore.CAB file is a file of files (similar to ZIP). normally highlighted in yellow. The . and the original volume is destroyed. and typically does not remain on a virtual machine. The revert. The diskshadow. To obtain a listing of all VSS shadows before running the script. The revert. one of which is a manifest file that has a list of all the volumes that comprise a VSS backup.exe utility to perform common operations.CAB files that were created when the VSS backup was performed.exe. to perform all the necessary VSS operations. You can manually run the diskshadow.exe utility subcommand delete shadows all. -version Reports the version of the script and exits PowerShell script to revert data disks Use the revert. This is similar to the VMware Snapshot revert operation. but they will not be reverted to a VSS consistent point in time. it replaces the original volume from which it was copied. such as: list all shadows (list shadows all). and removes it from the list of volumes to revert.CAB file as part of creating a VSS shadow copy. delete shadows (delete shadows all).exeutility sub- command list shadows all.ps1 script does the following: Chapter 9: Backups 120 .CAB files and selects the most recent one so that the most up-to-date VSS shadow copies are reverted. then that data is lost when it is replaced with the shadow copy. One of the system restrictions is that the system drive (typically the C: drive) cannot be replaced with its shadow. they are restored as part of the restoration process. -list Lists all available shadows after the revert of the shadows has completed.ps1 PowerShell script detects which drive is the system drive. read a cab file (load metadata).exe utility is also the utility that creates the . When a Volume Shadow copy is reverted. Reverts all drives found in the manifest EXCEPT for the system drive. deletes the . then it is possible that a subdirectory contains more than one . The subdirectory contains one or more .ps1 PowerShell script to revert the data disks after a Volume Shadow Copy Service (VSS) backup has been restored and the virtual machine has been started. To manually delete the VSS shadow copies. called diskshadow.Option Description -cleanup After reverting the shadow copies. and so on.ps1 PowerShell script uses a Windows utility. If you have databases on the System drive. -verbose PowerShell common parameter that enables additional output. use the diskshadow.CAB file. If the original volume contains new data that was added after the VSS copy was created. mount shadows read-only (expose). The revert. but for a Windows volume. If you set the -cleanup switch. you can delete it: DISKSHADOW> delete shadows ID %VSS_SHADOW_3% -> %VSS_SHADOW_3% = {6b8a3615-50b3-462e-a443-1a2e3bf34804} Deleting shadow copy {6b8a3615-50b3-462e-a443-1a2e3bf34804}. Chapter 9: Backups 121 . If there are remaining VSS shadow copies.CAB file and all unused VSS shadow copies found in the manifest... • Starts all instances of SQL Server. If there are no . • Reverts all drives found in the manifest EXCEPT for the system drive (typically the C: drive). • Selects the most recent .CAB file so that the most recent VSS shadow copies are reverted. use the expose command to make the shadow copy visible as another drive: DISKSHADOW> expose %VSS_SHADOW_3% q: -> %VSS_SHADOW_3% = {6b8a3615-50b3-462e-a443-1a2e3bf34804} The shadow copy was successfully exposed as q:\. This can take a very long time for large databases. The drive disappears but in this case. 2.CAB the Manifest.1. the script deletes the newest . 2. Restore individual files Restore individual files by making the shadow copy visible as another drive. If you set the -revert switch. If the script find a problem with a database. If you set the -list switch. you can manually delete them using the diskshadow. the script runs "DBCC CHECKDB” on all databases on all instances on the local system. Procedure 1. If you set the –checkdb switch. simply undo the previous "expose" operation: DISKSHADOW> unexpose q: Shadow copy ID {6b8a3615-50b3-462e-a443-1a2e3bf34804} is no longer exposed. Extracts from the . 3.CAB files in the %SystemDrive%:\OmniStackBackup directory and subdirectories. • Stops all instances of SQL Server. there will not be any remaining VSS shadow copies. the script: • Discovers all the . 1 shadow copy deleted. it prints out an error. The PowerShell revert script can be found in %SystemDrive%:\OmniStackBackups directory.CAB files found.xml which has the list of shadows and their volume name (drive letter). 3. the script lists all remaining VSS shadow copies it finds on the system.exe utility (subcommand delete shadows all). the script prints a message to that effect and stops. When done retrieving files. 4. A drive "q:\" appears in windows explorer which can be browsed and copied from. and then copying individual files from the shadow copy to the original volume. Once you identify the available shadow copies using DISKSHADOW> list shadows all from the previous steps. the shadow copy remains for future access. When you finish with the shadow copy. For most systems. svt-backup-restore --emergency --datastore datastore-name|GUID -- vm vm-name|GUID --backup backup-name|GUID --source datacenter-name|-- destination datacentername|GUID --emergency vm-name|GUID --home datastore- name|GUID --name vm-name|GUID NOTE: Keep the terminal window open.Restore backups when the Hypervisor Management Service is down Restoring a backup to a new virtual machine when the Hypervisor Management System is down Use this procedure to restore a virtual machine backup to a new virtual machine at any accessible cluster and datastore when the hypervisor is down. the ESXi web interface does not allow you to provide a different name to a virtual machine. Log in to the host where the new virtual machine resides. Before using this procedure. which may result in duplicate machine names. 2. Right-click the datastore that will contain the new virtual machine and select Browse Datastore. One solution is to right-click. Run the svt-backup-restore command with the --emergency switch to create the new virtual machine that will contain the restored backup.5. Before you begin An HPE SimpliVity CLI account (svtcli) password is required. 5.0 or earlier. svt-backup-show [--datastore datastore-name|GUID] --emergency [--vm vm- name|GUID] 3. When the hypervisor is not in an operational state. and cause confusion during the restoration process. Run the svt-backup-show command with the --emergency switch to determine the backup to restore on a new virtual machine. log in using the standalone vSphere client. use the svt- backup-restore command with the --emergency switch to restore a virtual machine backup to a new virtual machine. A CLI command is required later in this procedure. Open an SSH connection directly to the Virtual Controller of the host and log in to your HPE SimpliVity CLI (svtcli) account. 6. NOTE: During manual import. 4. a best practice is to determine the issues causing the hypervisor to be down and return the hypervisor to an operational state. Chapter 9: Backups 122 . log in using the ESXi web interface. and add a note that identifies the original virtual machine. Open the folder for the new virtual machine. Another solution is to rename the original virtual machine before you import it. • If you use VMware vSphere 6. Procedure 1. • If you use VMware vSphere 6. vmx file and select Add to Inventory. Click Next. c) Remove any orphaned virtual machines from all Hewlett Packard Enterprise hosts. NOTE: Remove virtual machines with (Orphaned) appended to the virtual machine name only. or host name when you re-add them. If vSphere Client triggers an alarm that a MAC address is not assigned to the new virtual machine. right-click the new virtual machine and select Edit Settings. This displays the new virtual machine in the vSphere Client inventory. e) Click the Hardware tab and the network adapter. Do not remove virtual machines with (Inaccessible) appended to the virtual machine name. or hosts that you added after the creation of the backup where the virtual machine was restored must be manually re-added to the hypervisor inventory. See the vSphereHelp for information about adding a datacenter. perform these steps: a) In vSphere Client. right-click the new virtual machine and select Power > Power On. Click OK. Specify the name and cluster location of the new virtual machine. See VMware KB article 1011468 for more information. g) Right-click the new virtual machine and select Power > Power On. This will replace the contents of the virtual machine with the contents that existed at the time the backup was created. cluster. Select the Hewlett Packard Enterprise host on which to run the new virtual machine. Click OK. d) In vSphere Client. c) Copy the MAC address. Click Finish to register the new virtual machine. perform the remaining steps. Before you begin Chapter 9: Backups 123 . 9. When you can log in to the HMS via vSphere Client. Use the same datacenter. or host. 11. b) Run the svt-emergency-hms-sync command to synchronize the HMS inventory with the configuration stored in the Hewlett Packard Enterprise federation. 12. NOTE: When you restore a virtual machine to a backup. cluster.7. Restore a virtual machine from a backup when Hypervisor Management System is down You can restore a virtual machine from a backup when the hypervisor is down to recover a virtual machine. 13. any new datacenters. right-click the old virtual machine that you specified in step 2 and select Edit Settings. then run the svt- emergency-hms-sync command. 8. complete the following steps: a) Wait for HMS to be fully operational. Right-click the . clusters. 10. In vSphere Client. Click Next. If you restored a virtual machine hosting the HMS. f) Select the Manual radio button and paste the MAC address of the old virtual machine into the MAC address field of the new virtual machine. b) Click the Hardware tab and the network adapter. clusters. Run the svt-vm-restore command with the --emergency switch to restore the virtual machine from a backup. perform the remaining steps. b) Run the svt-emergency-hms-sync command to synchronize the hypervisor inventory with the configuration stored in the HPE SimpliVity federation. svt-vm-restore --datastore datastore-name|GUID --vm vm-name|GUID -. Procedure 1. NOTE: Restoring a virtual machine deletes any data changes that occurred since you created the backup. or host name when you re-add them. c) Remove any orphaned virtual machines from all HPE OmniStack hosts. cluster. Chapter 9: Backups 124 . Run the svt-backup-show command with the --emergency switch to determine the backup from which to restore the virtual machine. This will replace the contents of the virtual machine with the contents that existed at the time the backup was created. log in to the Hewlett Packard Enterprise host on which the restored virtual machine resides. 4. Once it is in operational state. A CLI command is required later in this procedure. In vSphere Client. or hosts that you added after the creation of the backup to which the virtual machine was restored must be manually re-added to the hypervisor inventory. then run the svt-emergency- hms-sync command. Use the same datacenter. See VMware KB article 1011468 for more information. svt-backup-show [--datastore datastore-name|GUID] --emergency [--vm vm-name|GUID] 3. If you restored a virtual machine hosting the hypervisor.NOTE: Restoring a virtual machine deletes any data changes that occurred since you created the backup. • An HPE SimpliVity CLI account (svtcli) password is required. 5. Best practice before using this procedure is to determine the issues causing hypervisor to be down and return it to an operational state. See the vSphere Web Client help for information about adding a datacenter. cluster.backup backup-name|GUID NOTE: Keep the terminal window open. a) Wait for the hypervisor to be fully operational. any new datacenters. use the svt-vm-restore command to restore a virtual machine from a backup. 2. Open an SSH connection directly to the Virtual Controller of the host and log in to your CLI (svtcli) account. complete the following steps: NOTE: When you restore a virtual machine to a backup. • This procedure is only intended to restore a virtual machine from a backup when the hypervisor is down. or host. Procedure overview You can restore a virtual machine from a backup when the hypervisor is down to recover a virtual machine. When you can log in to it via vSphere Client. Right-click the restored virtual machine and select Power > Power On. 6. NOTE: Remove virtual machines with (Orphaned) appended to the virtual machine name only. Do not remove virtual machines with (Inaccessible) appended to the virtual machine name. Chapter 9: Backups 125 . You cannot use the Filter or Find options on the Provisioned. and click the Virtual Machines tab to list the virtual machines in a cluster. and click the HPE SimpliVity Virtual Machines subtab to list the virtual machines in the cluster. Used. double-click the cluster. those options do not function. when you try to use the Filter or Find options on the Provisioned. click the Related Objects tab. double-click the cluster. ensure that the server and client clocks are synchronized. you click HPE SimpliVity Federation > Clusters and can see all the clusters listed in the Objects tab.Chapter 10: Troubleshooting This section contains the following topics: • Cluster issues • Host issues • Virtual machine issues • Backup issues • Miscellaneous issues Cluster issues Cannot use certain options to customize the search in an HPE SimpliVity Virtual Machine table for a cluster From vSphere Web Client Home. You also see the old name when you click Home > HPE SimpliVity Federation > Hosts. You can then double-click a cluster. or Storage HA columns. Host issues Cannot see a Virtual Controller name change in the HPE SimpliVity Host table for a cluster You click Home > HPE SimpliVity Federation > Clusters. or Storage HA columns in the Hewlett Packard Enterprise Virtual Machines table for a cluster. Also. Solution No solution is available at this time. Solution Use the data range slider to expand the range of viewed data until the data comes into view. You see the new Virtual Controller name in the list for the vSphere Virtual Machine tab. No data is displayed in the HPE SimpliVity Performance view If no data was available during a particular data range or if the data range is set to one minute and the client and server clocks are more than one minute apart. You then right-click the virtual machine named OmniCubeVC and use the vSphere Rename option to rename it. For example. Chapter 10: Troubleshooting 126 . Used. and click the SimpliVity Hosts subtab. the data points in the server data when mapped to the client chart are not visible. However. you continue to see the old name appear in the Virtual Controller Name column when you click Home > SimpliVity Federation > Clusters. but you cannot see the new name in the Virtual Controller Name column for HPE OmniStack hosts. you notice that the object count in the tab and inventory panel show the same value as before you deleted the virtual machine. not a Hewlett Packard Enterprise Virtual Machines tab. but you saw an error appear in the Recent Tasks panel. try one of the following: • Right-click the inaccessible virtual machine and select Power On (if available) to start up the virtual machine. Chapter 10: Troubleshooting 127 . moving it to another datastore) and the action completed successfully. Solution You may see errors after performing tasks on virtual machines if another user in another session tried to perform an action on the same virtual machine while you were performing your action on it. The tab appears empty. the log files show a data source exception: no virtual machine objects found error. click Refresh ( ) to clear it. but does not the reduce the count You chose a virtual machine and selected Remove from Inventory to remove the virtual machine and retain its files or Delete from Disk to delete the virtual machine and all its files. a damaged disk. The default name of OmniCubeVC-<management IP address> helps you identify it as a unique part of an HPE OmniStack host. The Hewlett Packard Enterprise tab and options do not list the Virtual Controller as a virtual machine. After you complete the task. This vSphere option removes the virtual machine from inventory. To resolve this issue. Once the virtual machine is accessible (or removed).NOTE: The Virtual Controller is a virtual machine dedicated to the HPE OmniStack host. Virtual machine issues Cannot see any virtual machines listed in the Objects tab You clicked Virtual Machines from the HPE SimpliVity section of the vCenter Inventory Lists panel. • Right-click the inaccessible virtual machine and select Remove from Inventory. You can see all the other virtual machines listed in the inventory panel. but retains its files. If you see an error after successfully performing an action. Deleting a virtual machine removes it from the list in the Objects tab. but you cannot see any virtual machines listed in the Objects tab. The panel lists a virtual machine name in gray. from corrupt metadata. or invalid lock types). italic letters with (inaccessible) next to the name. It defaults to a name with OmniCubeVC-<management IP address>. Also. you can see all the virtual machines in the Objects tab. It runs the HPE OmniStack software. You can then restore the virtual machine to inventory by creating a new virtual machine from a backup. Solution Do not use the vSphere Rename option to change the name of the HPE OmniStack Virtual Controller. It does not decrease. Solution A virtual machine can become inaccessible due to a power outage or if the datastore becomes inaccessible (for example. Also. avoid performing tasks on virtual machines at the same time another user may try to access the same virtual machine (if possible). Performing an action on a virtual machine produces an error after it completes successfully You performed an HPE SimpliVity action on a virtual machine (for example. The Virtual Machines tab is a vSphere tab. Select Create new virtual machine instead and select another datastore from the Destination Datastore drop-down list. Sorting filtered backups based on unique backup size results in an incorrect sorting of the column Filtering backups on the basis of the unique backup size when some backup sizes are unknown results in an incorrect sorting of the column. you see an input string or a negative numbers error and could not create the rule. you saw an Unknown datastore message and could not replace the virtual machine with the backup. Solution No solution is available at this time. you clicked HPE SimpliVity Federation > Create Backup Policy to create a backup policy. If that does not adjust the count to the appropriate value. When you selected Backup Actions > Restore Virtual Machine and selected the Replace existing virtual machine option. After entering a name and clicking Create Rule. Solution The original datastore no longer exists. continue to perform other tasks and then click Refresh again. Solution Enter whole numbers in the Frequency and Retain Backups For fields to successfully create a backup policy rule. Miscellaneous issues Export List feature does not display provisioned nor used values with measurement units An Exported list of HPE SimpliVity virtual machines does not provide Provisioned and Used values with measurement units as they are displayed by VMware. Chapter 10: Troubleshooting 128 . you clicked HPE SimpliVity Federation > Virtual Machine (or Cluster). You cannot enter letters or negative numbers. See an error when replacing an existing virtual machine with a backup From vSphere Web Client Home. After selecting a cluster and clicking OK. Solution The column sorts correctly if all backup sizes are known. Sorting filtered backups based on unique size calculation time results in an incorrect sorting of the column Filtering backups on the basis of the unique size calculation results in an incorrect sorting of the column. Backup issues See an error when creating a backup policy rule From vSphere Web Client Home. you entered letters or negative numbers in the Frequency or Retain Backups For fields. and selected the backup to replace an existing virtual machine with a backup.Solution Click the Refresh icon ( ). searched for backups. you see All HPE SimpliVity Plug-in for vSphere Web Client Actions > No Actions Available. Solution You or another administrator may have powered off the virtual machines before shutting down the Virtual Controller of an OmniStack host. or datastores objects when they appear accessible You browsed to an HPE SimpliVity host. You see an "unable to locate a healthy OmniCube" message instead. you see the All HPE SimpliVity Plug-in for VMware Web Client option with SimpliVity features. For example. The correct HPE SimpliVity menu option appears under objects you can manage with HPE SimpliVity actions. When you try to use a feature (for example. ignore them. you cannot perform any HPE SimpliVity actions on it. Instead. You also cannot perform HPE SimpliVity actions on a standard ESXi host. See "All HPE SimpliVity Plug-in for vSphere Web Client Actions" option for unexpected virtual objects If you use vSphere Web Client 6.csv) of HPE SimpliVity virtual machines provides raw provisioned and used values with no units. and virtual machines you want to access and try the HPE SimpliVity actions again through the correct HPE SimpliVity menu. but the same All HPE SimpliVity Plug-in for vSphere Web Client Actions > No Actions Available options appear available. or datastores appear available when they are not.Solution An Exported list (. Providing the raw values in the . Chapter 10: Troubleshooting 129 . Virtual Controller. The corresponding values when viewed on the datastore related VM tab are displayed with units (for example GB). They should show the status as "unavailable" if powered off.0 or later. right- clicked the object and did not see the All HPE SimpliVity Actions option with SimpliVity features. Clone Virtual Machine or Edit Backup Policy). if you click Virtual Machines under vCenter Inventory Lists and right- click the Virtual Controller. vSphere Web Client automatically creates these options using the full name of the plug-in and adds them to the Actions drop-down menu by default. virtual machine. you see the All HPE SimpliVity Plug-in for vSphere Web Client Actions > No Actions Available options when you right-click certain objects under the vCenter Inventory List section in the inventory panel. You can power on the host. virtual machines. virtual machines. For example. If you do not power on the Virtual Controller and the virtual machines on the OmniStack host.csv output allows the user to perform calculations in the spreadsheet without first converting the numbers. view them through the vCenter inventory panel options or tabs. or datastore in an HPE SimpliVity federation. the action fails. the host. Because the Virtual Controller runs the HPE OmniStack software for the HPE OmniStack host. Cannot perform actions on hosts. you see All HPE SimpliVity Actions under the Actions menu or when you right-click HPE SimpliVity objects. Solution If you see the All HPE SimpliVity Plug-in for vSphere Web Client Actions > No Actions Available options. To check the status of the objects. NOTE: HPE SimpliVity recommends that you do not customize the threshold values for these pre-configured alarms. Pre-configured alarms Events and alarms help you monitor normal operations and identify problems before they disrupt service. The HPE OmniStack software supports two types of alarms: • VMware pre-configured alarms with default VMware threshold values for alarm triggers. configure Actions in vCenter for specific pre-configured alarms. Chapter 11: HPE SimpliVity alarms 130 . NOTE: HPE SimpliVity-specific alarms are triggered by HPE SimpliVity events and do not support configurable thresholds for triggers. As necessary. From vSphere Web Client Home. for example Host connection failure. (A Virtual Controller virtual machine contains "OmniStackVC" in the name). Click the Configure tab. so your experience monitoring conventional vSphere virtual machines with alarms is directly relevant to your monitoring HPE SimpliVity virtual machines and Virtual Controllers.Chapter 11: HPE SimpliVity alarms This section contains the following topics: • HPE SimpliVity Alarms HPE SimpliVity Alarms HPE OmniStack software is tightly integrated with vSphere Web Client. do the following: Procedure 1. 2. To view the VMware pre-configured alarms for the Virtual Controller. • HPE SimpliVity-specific alarms. 3. Click the row with the HPE OmniStack virtual controller for the host you need to view from the list of virtual machines. Browse pre-configured vCenter alarms Procedure overview Pre-configured alarms are available from the vCenter Server and propagate down the inventory hierarchy. HPE OmniStack does not support specific SNMP MIBs. Therefore. To the extent that HPE OmniStack hyperconverged platforms are implemented on VMware. NOTE: For monitoring. the pre-configured alarms available to all VMware VMs are the foundation for monitoring HPE SimpliVity VMs. click VMs and Templates. for example HPE Simplivity backup policy suspended. but does support basic vCenter SNMP services. an alarm defined for a virtual machine at the datacenter level applies to all the virtual machines in that datacenter. To monitor VM-level IO in your deployment. Click Alarm Definitions. Click the row with the HPE OmniStack virtual controller for the host you need to view from the list of virtual machines. so you could click any entry to display the vCenter Server level associated with that particular alarm. do the following: Procedure 1. The "defined in" link points to where the alarm is defined. the alarms on the HPE OmniStack Virtual Controller indicate that they are defined at the vCenter level. From vSphere Web Client Home. The following two alarms are useful examples of monitoring VM CPU and memory usage. Chapter 11: HPE SimpliVity alarms 131 . Alarm Warning Alert Description Virtual machine CPU Above 75% for 5 minutes Above 90% for 5 minutes Default alarm to monitor usage virtual machine CPU usage Virtual machine memory Above 85% for 10 minutes Above 95% for 10 minutes Default alarm to monitor usage virtual machine CPU usage IO alarms and VMware vRealize IO usage for a particular VM is not monitored thoroughly through pre-configured or HPE SimpliVity-specific alarms. 3. 4. View pre-configured alarms that have been triggered Procedure overview To view alarms that have been triggered. Click Triggered Alarms to display a table of triggered alarms for the selected inventory object. (A Virtual Controller virtual machine contains "OmniStackVC" in the name).4. 2. Settings for sample CPU and memory usage alarms HPE OmniStack uses VMware default values for thresholds all the pre-configured alarms. Click the Monitor tab. In this example. consider using VMware vRealize. click VMs and Templates. Enter the string "simplivity" (any character case) in the filter field. do the following: Procedure 1. 3. Call Support). virtual machines. click HPE SimpliVity Federation. • Almost all HPE SimpliVity-specific alarms are self-clearing. • HPE SimpliVity-specific alarms tend to be informational (HPE OmniStack Available Physical Capacity 20 Percent or Less) or suggestive of responses (Accelerator NVRAM persistence error. 2. Double-click the virtual machine with alarms you need to view. Click the Monitor tab. You see a list of SimpliVity alarms appear as shown in the example. View HPE SimpliVity-specific alarms Procedure overview To view alarms specific for HPE SimpliVity. Click Alarm Definitions. Click Virtual Machines to open the Objects tab. 4. datacenters. and vCenter services. Chapter 11: HPE SimpliVity alarms 132 . Observe the following about HPE SimpliVity-specific alarms: • HPE SimpliVity-specific alarms do not support configurable threshold values for triggers. From vSphere Web Client Home. 6. 5.HPE SimpliVity-specific alarms HPE SimpliVity-specific alarms monitor a variety of objects in the vSphere inventory: hosts (systems). event.simplivity.control.capacity.warning (Normal) HPE OmniStack physical capacity for Storage. you can set one or more of the following actions: • Send email(s) in response to an alarm being triggered. Typically.control. Chapter 11: HPE SimpliVity alarms 133 . you can configure the action(s) that vCenter takes when that alarm is triggered.phys.phys.node.phys.capacity. Without modifying the threshold values that trigger an alarm.node. verify the following: • Your vCenter Server is configured to generate SNMP email or trap notifications • The account that you are using has Alarms. some of the most useful monitor storage capacity.simplivity.event. there are 90 HPE SimpliVity-specific alarms.Create Alarm or Alarm. HPE OmniStack Available Physical com.event.node.phys.control.node. • Send an SNMP trap in response to an alarm being triggered.error (Alert) Capacity 10 Percent or Less com.control.control.warning (Normal) HPE OmniStack physical capacity for Storage. Configure actions for HPE SimpliVity-specific alarms Before you begin Before configuring an action for a HPE SimpliVity-specific alarm.simplivity. Alarm Events (Status) HPE OmniStack Available Physical com.capacity.tolerance (Normal) DESCRIPTION: Monitors for low com.within. Of those alarms.node.capacity.node.event.error (Alert) Capacity 20 Percent or Less com.within.simplivity.capacity.capacity.Results These top-level alarms can be modified only at this level. Settings for sample HPE SimpliVity-specific alarms As of this writing.phys.phys.simplivity.event.control.tolerance (Normal) DESCRIPTION: Monitors for low com.event.simplivity.Modify Alarm privileges Procedure overview Both pre-configured vCenter alarms and HPE SimpliVity-specific alarms support custom actions. 5. SNMP. The procedure to set a custom action for a particular alarm varies in detail by the version of vCenter that you have installed and how you have configured it. 3. Hosts or Virtual Machines to open the Objects tab. Alarms and HPE OmniStack hosts This section describes how to configure or to work with some of most popular alarms. Click a SimpliVity objects (for example. Select the row with the alarm you want details on. click HPE SimpliVity Federation. From vSphere Web Client Home. Click Alarm Definitions. 4. the steps are the same. Recommended Settings Type of Alarm Warning Condition Critical Condition Setting Rationale Setting CPU Alarm 90% for Omnicube virtual 100% for Omnicube virtual HPE OmniStack virtual controller VM controller VM controller CPU usage could reach 100% frequently Memory Alarm 85% 95% Keep vCenter defaults since the memory alarm values are appropriate for the Virtual Controller I/O Alarm None available by default None available by default Use vCenter or vRealize to monitor I/O performance Capacity Alarm Disable default vCenter Disable default vCenter Virtual Controller alarm if environment is alarm if environment is generates alarm for 100% 100% capacity usage and takes into account HPE SimpliVity objects (no HPE SimpliVity objects (no thin provisioning. Double-click the object with alarms you need to view. Click the Monitor tab. 6. 2. or command configuration options.• Run a script or command in response to an alarm being triggered. Procedure 1. Choose an action and click the Configuration column to display a list of email. Provide information for the appropriate action configuration and click OK. Chapter 11: HPE SimpliVity alarms 134 . then click the Actions drop-down arrow to view the list of available alarm actions. 7. At a high level. 8. other storage connected other storage connected to deduplication and to VMware ESXi) VMware ESXi) compression. for this alarm. From the vCenter Inventory List. Ensure that the “VM CPU usage” trigger type in the Alarm settings at the cluster level under the “Trigger tab” has “Trigger if all of the conditions are satisfied”selected. http://kb. Click the row with the Virtual Controller (virtual machine) for the host you need to view. click Virtual Machines. (A Virtual Controller is a virtual machine that contains "OmniStackVC" in the name because it contains the HPE OmniStack software. You may choose to modify this alarm by adding an “Action” field to get an email. CPU Performance alarms are pre-defined within vCenter for all virtual machines and apply to the HPE OmniStack host and its associated Virtual Controller. for 5 minutes. Definitions Type of Alarm Warning Condition Critical Condition Setting Action Setting Virtual Machine CPU CPU usage is above 75% CPU usage is above 90% No default actions are set Usage for 5 minutes. 5. Be mindful that you must choose the appropriate frequency for getting an email notification.) 3. Click the Monitor tab. Click Advanced to display CPU statistics similar to those displayed in the following figure.do? language=en_US&cmd=displayKC&externalId=1022292 Chapter 11: HPE SimpliVity alarms 135 . 2.com/selfservice/microsites/search. See the following VMware KB article for more details. You could also modify the “Reporting tab” to change the frequency of triggering an alert. Results Note that vCenter provides performance statistics as a rolling average. To get more specific statistics. Procedure 1. use the vRealize Operations Manager (Foundation version) formerly known as vCenter Operations Manager. Click the Performance tab to open it. 4.vmware.Monitoring CPU performance with CPU alarms Procedure overview You can monitor CPU performance for an HPE OmniStack host using vSphere options. you must create a folder structure for Virtual Controller VMs such that alarms are specific to those virtual machines only. Memory alarms You can monitor memory utilization for the Virtual Controller through vCenter or through the vRealize Operations Manager. Chapter 11: HPE SimpliVity alarms 136 . so there is no set value that can be suggested for an I/O alarm. the recommendation is to disable the existing alarm and create a new CPU alarm threshold with values for warning events as 90% and critical event at 100%. This alarm is set at the vCenter Server level. As a best practice. You may choose to modify this alarm by adding an “Action” field to get an email and by choosing the appropriate frequency for getting an email notification. you can create a new alarm with the desired frequency values. all VMs within that vCenter Server will be affected. Type of Alarm Warning Condition Critical Condition Setting Action Setting Virtual machine memory Memory usage is above Memory usage is above No default actions are set usage 85% for 10 minutes. If you determine that memory alarms are triggered at some incorrect frequency.This alarm is set at the vCenter Server level. 95% for 10 minutes for this alarm. Similar to CPU alarms. If you modify this alarm. This baseline varies from application to application. You could also modify the Reporting tab to change the frequency of triggering an alert. consider using the vRealize Operations Manager because it understands I/O patterns and can adapt to patterns of spikes without triggering alerts. The following figure shows different options available within vRealize Operations Manager to view performance metrics including Datastore I/O. Network usage and virtual disk I/O. Note that before creating a new alarm. You would first need to create a folder structure as mentioned above so that this alarm would apply only to Virtual Controller VMs. You may choose to create an alarm within vCenter to monitor the latency of your HPE SimpliVity Virtual Machine called “VM Max Total Disk Latency” alarm after your environment is stabilized to get a baseline. memory utilization alarms are pre-defined within vCenter with the default values shown in the following table. preserve the default values for the warning and critical condition fields of the Memory Alarm for Virtual Controller virtual machines. To the extent that Virtual Controller CPU usage could frequently reach 100%. so modifying it would affect the memory utilization alarm for all virtual machines within that vCenter Server. I/O alarms There are no pre-defined vCenter I/O alarms or HPE SimpliVity generated I/O alarms. If there are periods during which you expect to see routine I/O spikes. Datastore I/O can be monitored for a VM using vRealize Operations Manager. Depending on your environment and how HPE SimpliVity storage is used. Capacity alarms There is a pre-defined vCenter datastore usage alarm that monitors the percentage of disk space used on each datastore in your vSphere environment. In addition. For both the warning and the alert (event) a phone home event is triggered. Although you can adjust these thresholds for the needs of your environment. deduplication. the datastore alarm does not take into account HPE OmniStack capabilities such as thin provisioning. These thresholds may vary depending on the size of your datastores and how they are being used. The HPE SimpliVity alarm generates a warning within vCenter when the cluster has 20% or less physical space available and an alert is generated when the cluster has 10% or less physical space. If Phone Home is not required for the warning message. disable the vCenter datastore alarm since the HPE OmniStack host generates a capacity alarm when its physical capacity is running low. The following figure depicts the configuration for a trigger. this alarm can be changed to suit your environment to make it more aggressive or less aggressive. Chapter 11: HPE SimpliVity alarms 137 . compression. Customer Support can turn this switch off using Support commands. The default settings of the datastore usage alarm is to trigger a Warning when disk usage exceeds 75% and an Alert at 85%. If your environment is running HPE OmniStack hosts exclusively. it is a good practice to begin taking action as your datastore approaches 80% utilized. ) If you upgrade the HPE OmniStack software or have a standard host using an HPE SimpliVity datastore.Chapter 12: VAAI-NAS overview This section contains the following topics: • HPE SimpliVity VAAI-NAS plug-in • Prerequisites for installing the Hewlett Packard Enterprise VAAI-NAS plug-in • Install the HPE SimpliVity VAAI-NAS plug-in on an HPE OmniStackhost • Install the HPE SimpliVity VAAI-NAS plug-in on a standard host • Configure the HPE SimpliVity VAAI-NAS plug-in • Verify VAAI-NAS plug-in installation using vSphere Web Client options • Verify VAAI-NAS plug-in installation using CLI commands • Uninstall the HPE SimpliVity VAAI NAS plug-in VIB HPE SimpliVity VAAI-NAS plug-in The following topics contain details on how to install the vStorage API for Array Integration (VAAI)-Network Attached Storage (NAS) plug-in. Prerequisites for installing the Hewlett Packard Enterprise VAAI-NAS plug-in Prerequisites and considerations The following installation prerequisites and considerations apply for the Hewlett Packard Enterprise VAAI NAS plug-in: • You do not need to uninstall existing versions of the Hewlett Packard Enterprise VAAI NAS plug-in before installing an updated version. uninstall any VAAI NAS plug-ins from other vendors that might compete with the Hewlett Packard Enterprise plug-in. • A post-installation reboot is required for every host where you install the Hewlett Packard Enterprise VAAI NAS plug-in. It runs the OmniStack software. • Enable SSH on HPE OmniStack hosts and on the standard hosts that access Hewlett Packard Enterprise datastores. Chapter 12: VAAI-NAS overview 138 . • If standard hosts share the SimpliVity datastores. you must manually install it on the HPE OmniStack host you upgraded or the standard ESXi host that uses an HPE SimpliVity datastore. The VAAI-NAS plug-in comes installed on the Virtual Controller for each OmniStack host automatically. • Shut down or migrate the virtual machines off the hosts where you plan to install the VAAI-NAS plug-in. This reboot requires that you shut down or migrate any virtual machines running on the standard host. (The Virtual Controller is a virtual machine dedicated to an OmniStack host. This plug-in improves the performance of cloning operations by offloading storage operations from hosts to the HPE OmniStack Virtual Controller. NOTE: If you attempt to install the Hewlett Packard Enterprise VAAI NAS plug-in and you see the following error: [NoMatchError] No VIB matching VIB search specification 'simplivity-esx-n. log on to the first HPE OmniStack host as root. This procedure assumes that you already shut down or that you plan to migrate virtual machines.vib Where: • ip-address is the IP address of the Virtual Controller that is running on this OmniStack host.Install the HPE SimpliVity VAAI-NAS plug-in on an HPE OmniStackhost Procedure overview The VAAI-NAS plug-in improves cloning operations. • n.n. 2.n. • n. Use the correct revision for the version of ESXi installed on the host. but the OmniStack host was not rebooted. Chapter 12: VAAI-NAS overview 139 . 10. click Home > HPE SimpliVity Federation > Virtual Machines. Right-click the host again and click Power > Reboot. Procedure 1. Right-click the host again and click All HPE SimpliVity Actions > Shut Down Virtual Controller. In vSphere Web Client. 4. 6.x-nas- plugin'. it means that the plug-in was previously removed. You see a list of virtual machines appear. 9. During the installation. 11. Power up the virtual machines or migrate them back from their temporary location. Check that the Storage HA column shows "Yes" for the virtual machines. so at least one Virtual Controller must remain available at all times.nnn. In vSphere Web Client.x or 6. if you upgrade the HPE OmniStack software for a host. Right-click the host you want to access and click Maintenance Mode > Enter Maintenance Mode. Enter the following esxcli command: # esxcli software vib install --viburl=http://ip-address/vaai/simplivity-esx-n.x is the ESXi version (5. Reboot the host to correct the problem. 3. Right-click the OmniStack host and click Maintenance Mode > Exit Maintenance Mode. Using the terminal emulator.n. However. Click the Virtual Controller for the host you need to access and click the Summary tab to find the IP address and other details.nnn is the version string for the VAAI NAS plug-in. 7.x). Restart the Virtual Controller. you need to install the corresponding version of the HPE SimpliVity VAAI-NAS plug-in for the host to function as designed. You can find details on the Virtual Controller by clicking vCenter Inventory Lists > Virtual Machines in vSphere Web Client. click Home > HPE SimpliVity Federation > Hosts > . the installation package moves from the Virtual Controller to its HPE OmniStack host. 5.x-nas-plugin-n. Wait for the virtual machines to return to storage HA compliance (synchronize). It comes installed on the Virtual Controller of every HPE OmniStack host. Click Yes to confirm when prompted. 8.n. Install the HPE SimpliVity VAAI NAS plug-in VMware Installation Bundle (VIB) as described in this section. 7. but the system needs to be rebooted for the changes to be effective.3-1 VIBs Removed: VIBs Skipped: Install the HPE SimpliVity VAAI-NAS plug-in on a standard host Procedure overview If you want a standard ESXi host to use an HPE SimpliVity datastore. 2. log on to the first standard host as root. Reboot Required: true VIBs Installed: SimpliVity_bootbank_simplivity-esx-5.131. In vSphere Web Client. NOTE: If you attempt to install the Hewlett Packard Enterprise VAAI NAS plug-in and you see the following error: [NoMatchError] No VIB matching VIB search specification 'simplivity-esx-n.vib Installation Result Message: The update completed successfully. Example ~ # esxcli software vib install --viburl=http://100. Results The following is a sample of an installation. This procedure assumes that you already shut down or that you plan to migrate virtual machines. Check that the Storage HA column shows "Yes" for the virtual machines.x-nas-plugin_3. Using a terminal emulator. it means that the plug-in was previously removed. until you have installed the VIB on all the hosts. Repeat step 2 on page 139 through step 10 on page 139 for the next OmniStack host. it must share the datastore with an HPE OmniStack host.0.3.0. You see a list of virtual machines appear.x-nas- plugin'.11. Chapter 12: VAAI-NAS overview 140 . To ensure cloning operations offload storage operations from the host to the Virtual Controller.7. Install the Hewlett Packard Enterprise VAAI NAS plug-in VMware Installation Bundle (VIB) as described in this section.105/vaai/simplivity- esx-5. you must also install the VAAI-NAS plug-in on the standard ESXi host that uses an HPE SimpliVity datastore. so at least one Virtual Controller must remain available at all times.12. click Home > HPE SimpliVity Federation > Virtual Machines. During the installation. Reboot the host to correct the problem.x-nas-plugin- 3. but the standard ESXi host was not rebooted. Procedure 1. the installation package moves from the Virtual Controller to its HPE OmniStack host. nnn is the version string for the VAAI NAS plug-in. 6.7.n. Results The following is a sample of an installation. Repeat step 2 on page 140 through step 6 on page 141 for all standard hosts that share Hewlett Packard Enterprise datastores in the federation.105/vaai/simplivity- esx-5.x is the ESXi version (5. Reboot Required: true VIBs Installed: SimpliVity_bootbank_simplivity-esx-5. • n.x-nas-plugin_3. • n.11.x-nas-plugin-n.n.0. Enter the following esxcli command: # esxcli software vib install --viburl=http://ip-address/vaai/simplivity-esx-n.n.n. Make sure you use the appropriate VIB version. updated VIBs are copied to the Virtual Controller’s Web server in the vaai folder: (http://ip-address/vaai/simplivity-esx-5.vib).x-nas-plugin-3.x or 6. 7.7. You can find details on the Virtual Controller by clicking vCenter Inventory Lists Virtual Machines in vSphere Web Client. Use the correct revision for the version of ESXi installed on the host. depending on the ESXi version installed on the standard host. Right-click the OmniStack host and click Maintenance Mode > Exit Maintenance Mode. Right-click the standard ESXi host you want to access and click Maintenance Mode > Enter Maintenance Mode.nnn.3-1 VIBs Removed: VIBs Skipped: Configure the HPE SimpliVity VAAI-NAS plug-in Procedure overview Install the vSphere Installation Bundle (VIB) on federation HPE OmniStack hosts and on standard hosts that share HPE SimpliVity datastores.vib Installation Result Message: The update completed successfully.0.3. Click the Virtual Controller for the host you need to access and click the Summary tab to find the IP address and other details.vib Where: • ip-address is the IP address of the Virtual Controller where the VIB is located.7. 4. click Home > vCenter Inventory Lists > Hosts > .0. In vSphere Web Client.x-nas-plugin- 3.x).3. making the packages Chapter 12: VAAI-NAS overview 141 . Example ~ # esxcli software vib install --viburl=http://100. but the system needs to be rebooted for the changes to be effective. During the installation of an HPE OmniStack Software Upgrade package.3.x or 6. – n.131. 5.x is the ESXi version (5.x). vib for ESXi 6. use esxcli as described in this procedure.0. 3.3. NOTE: If the VAAI NAS VIB is delivered as a separate upgrade. Using a terminal emulator.io.x 32/64-bit • simplivity-esx-6. 4. 6.7.n.accessible for installation.so • /etc/vmware/firewall/svt-vaai-plugin-firewall.0 or 6. log in to a standard host as root. The Server field should show the root name as omni. Click the Manage or Monitor tab (depending on your version of vSphere).x-nas-plugin-3. The HPE SimpliVity VAAI NAS plug-in distribution includes two ESXi-specific packages. try installing the VAAI-NAS plug-in on the host again.so • /usr/lib/vmware/nas_plugins/lib64/libsvt-nas-vaai-plugin.xml Verify VAAI-NAS plug-in installation using vSphere Web Client options Procedure overview To verify that the HPE SimpliVity VAAI NAS plug-in is installed and functioning for a HPE SimpliVity datastore. You must manually install the VIBs on all standard hosts that share HPE SimpliVity datastores. Unknown or Not Supported shows).x-nas-plugin-3. Typically.cube.0.vib for ESXi 5.5 32/64-bit When installed. Procedure 1. Chapter 12: VAAI-NAS overview 142 . Click Device Backing.n.0. Hardware Acceleration should show as Supported on all hosts.8.nnn is replaced by a version string.5.3 as shown in the following examples: • simplivity-esx-5. Verify VAAI-NAS plug-in installation using CLI commands Procedure overview To verify that the HPE SimpliVity VAAI NAS plug-in is installed and functioning for an HPE SimpliVity datastore. such as 3. use vSphere Web Client options as follows: Procedure 1. the VIB is preinstalled on factory-shipped HPE OmniStack hosts. click Home > HPE SimpliVity Federation > Datastores > . In vSphere Web Client. and you do not need to install it. Double-click the datastore you use for the host with the newly installed VAAI-NAS plug-in. 5. If the datastore does not show the Hardware Acceleration as Supported on all hosts (for example. the files are located in the following ESXi system folders: • /usr/lib/vmware/nas_plugins/lib32/libsvt-nas-vaai-plugin. Click General and under Datastore Capabilities. The procedure assumes that SSH is enabled. Then click the Settings subtab or link (depending on your version of vSphere). you might need to install it manually on your HPE OmniStack hosts. where n.7. 2. Enter the following esxcli command: # esxcli storage nfs list 3. Determine the installed VIB version: ~ # esxcli software vib list | grep simplivity simplivity-esx-5. it means that the plug-in was previously removed. -----------------------. Reboot the host to correct the problem. Procedure 1. Using a terminal emulator. This might take some time because you must migrate or shut down active virtual machines. then the HPE SimpliVity VAAI NAS plug-in is not installed or not functioning correctly.x-nas-plugin Chapter 12: VAAI-NAS overview 143 .x-nas-plugin 3.cube.------- --------------------- 100 sml omni.x-nas- plugin'. Enter the following esxcli command: # esxcli software vib remove --vibname=simplivity-esx-5.cube.2.io /mnt/svtfs/0/110-sml-hr true true Supported englab2 omni. 4.0. but the HPE OmniStack host was not rebooted. Results The following is a sample VAAI verification: ~ # esxcli storage nfs list Volume Name Host Share Accessible Mounted Hardware Acceleration ----------. As for VIB installation. Try installing it on the host again.3-1 Hewlett Packard Enterprise VMwareAccepted 2015-09-09 3.cube. log on to the first host as root. Verify in the output that the value of Hardware Acceleration is Supported on all hosts. 2. a complete uninstallation requires that you reboot every OmniStack host and every standard host.cube. Upgrades do not require you to remove the plugin.-----------.7. NOTE: If you attempt to uninstall the HPE SimpliVity VAAI NAS plug-in and you see the following error: [NoMatchError] No VIB matching VIB search specification 'simplivity-esx-5. If the value is Not Supported. you do not uninstall the HPE SimpliVity VAAI NAS plug-in VIB unless instructed to do so by Customer Support. Look for active datastores where the root of the Device Backing name is omni. ---------.io.io /mnt/svtfs/0/wnglab2 true true Supported ~ # Uninstall the HPE SimpliVity VAAI NAS plug-in VIB Procedure overview Normally.io /mnt/svtfs/0/100sml true true Supported 110-sml-hr omni. 8. Repeat step 1 on page 143 through step 7 on page 144 until you uninstall the VIB from all hosts that need it removed. click HPE SimpliVity Federation > Hosts in vSphere Web Client. Results The following is a sample uninstall: ~ # esxcli software vib remove --vibname=simplivity-nas-plugin.3.8. but the system needs to be rebooted for the changes to be effective. 10.45 VIBs Skipped: Chapter 12: VAAI-NAS overview 144 .8. Reboot Required: true VIBs Installed: VIBs Removed: SimpliVity_bootbank_simplivity-nas-plugin_3. click Home > HPE SimpliVity Federation > Datastores > . Follow any host-specific procedures for restarting virtual machines.0. 9. Right-click the host again and click Power > Reboot. Right-click the host and click Maintenance Mode > Exit Maintenance Mode. Right-click the host you want to shut down and click All HPE SimpliVity Actions > Shut Down Virtual Controller. If removing the plug-in from an HPE OmniStack host. Double-click the datastore and click Manage > Settings > General to verify that Hardware Acceleration shows as Not Supported.4.0.45 Removal Result Message: The update completed successfully. Repeat step 1 on page 143 through step 8 on page 144 for the next host. until you have uninstalled the VIB from all the hosts that need it removed. To verify the software removal. 6. Power up the virtual machines (if powered off) or migrate them back from their temporary location. 11. 7. Right-click the host and click Maintenance Mode > Enter Maintenance Mode. 5. If you must replace the existing vCenter virtual machine. such as: adding or removing a vCenter Server. 2. restore the desired backup to a new virtual machine and then power off the vCenter virtual machine. adding or removing a Platform Services Controller (PSC) from a vSphere 6. 4. This procedure does not discuss the migration of an existing vCenter Server managing a Hewlett Packard Enterprise federation. Due to vCenter Server's internal use of an SQL based database.Chapter 13: Deploy vCenter Server on an HPE OmniStack host This section contains the following topics: • vCenter Server deployment on an HPE OmniStack host • Install vCenter Server on a virtual machine • Configure and deploy the HPE OmniStack host for use with vCenter Server • Upload the vCenter Server to the HPE OmniStack host • Linked Mode deployment vCenter Server deployment on an HPE OmniStack host For some deployment configurations. 5. you can choose to run the vCenter Server on an HPE SimpliVity datastore. This is especially important when you perform an action that creates a new instance of one or more virtual machines from a backup (such as when you restore to a clone or new virtual machine). 3. use an application-consistent backup as your policy type for Windows-based vCenter Server virtual machines. Similarly. or performing similar operations. or performing similar operations. you must log in to the HPE OmniStack host directly to turn the new vCenter virtual machine back on.0 Linked Mode environment. you should perform a manual backup every time you make virtualization infrastructure changes. • Using HPE SimpliVity Move to migrate a vCenter virtual machine is not allowed. adding or removing large numbers of guest virtual machines. If you do not perform backups when adding or modifying infrastructure components. then infrastructure changes will be missing from the restored backup. Chapter 13: Deploy vCenter Server on an HPE OmniStack host 145 . and you restore using a backup that was created before you added or modifying the components. This procedures describes how to deploy a new vCenter Server to a new HPE SimpliVity cluster. Perform a manual backup every time you make significant inventory changes. Installing the vCenter Server on the HPE OmniStack host is a process that consists of three main tasks: • Install vCenter Server on a virtual machine • Configure and deploy the HPE OmniStack host for use with vCenter Server • Upload the vCenter server to the HPE OmniStack host Technical limitations and recommended best practices when running the vCenter server on the HPE OmniStack host 1. DO NOT perform operations that require bringing the vCenter server offline. Once the vCenter virtual machine is powered off. such as: adding or removing an ESXi host. Do not power on two vCenter virtual machines that simultaneously manage the same inventory. 6. Next steps After you install the vCenter Server on a virtual machine. 2. After you deploy HPE OmniStack host. NOTE: When prompted to enter the vCenter IP address during the deployment process. separate from all of the other guest virtual machines. the HPE SimpliVity federation will go into a state of permanent data unavailability and will not be recoverable without data loss. use the same subnet to which you will deploy the HPE OmniStack hosts. the vCenter Server should reside on its own datastore. you must power on the virtual machine containing the PSC before you power on the other vCenter virtual machines in order for the virtual machines to authenticate. Install vCenter Server on the virtual machine. When using VMware vSphere 6. 3. 2. Chapter 13: Deploy vCenter Server on an HPE OmniStack host 146 . Install vCenter Server on a virtual machine Procedure overview This task describes how to install the vCenter Server on a virtual machine that resides on a laptop.0 for Linked Mode deployment. Procedure 1. Connect a laptop running VMware hypervisor software to the same network subnet to which you will deploy the HPE OmniStack hosts. Configure and deploy the HPE OmniStack host for use with vCenter Server Procedure overview This task describes how to configure and deploy an HPE OmniStack host to vCenter Server. use the IP address for the vCenter Server you configured earlier in this process. If the virtual machine running the Arbiter goes down. Using the VMware hypervisor software. install the virtual machine that will host the vCenter Server. The laptop must be running VMware Workstation or Workstation Pro hypervisor software. you must configure and deploy the HPE OmniStack host. WARNING: The Arbiter can never run on a virtual machine using HPE SimpliVity storage. Configure and deploy the HPE OmniStack hosts in your configuration using the HPE OmniStack Deployment Manager software. create a policy and datastore for the datacenter hosting the vCenter Server. When configuring virtual machine network settings. See the HPE OmniStack for vSphere Deployment Guide for more details. As a best practice. Procedure 1. This practice helps prevent the vCenter Server from running out of disk space. The virtual machine starts to upload. In VMware hypervisor software. Configurations with frequent virtualization infrastructure changes require a more aggressive backup rule. select VM > Manage > Upload. then click Finish. Similarly. Frequent backups help ensure changes are captured. Next steps After you configure and deploy the HPE OmniStack host. it is a good practice to perform a manual backup. then select Power > Power on. right-click on the virtual machine. NOTE: If using a PSC on a dedicated virtual machine. If you anticipate backing up the virtualization infrastructure much more frequently than other production virtual machines. When creating the backup policy for the vCenter Server. you can manage the HPE OmniStack federation. Chapter 13: Deploy vCenter Server on an HPE OmniStack host 147 .). etc. reconnect it using the Web Client. 8. If you make a significant change. such as adding or renaming an OmniCube. Upload the vCenter Server to the HPE OmniStack host Procedure overview This procedure describes how to upload the vCenter Server from the laptop to the HPE OmniStack host. 3. NOTE: It is important to regularly backup the vCenter Server. power it back on. NOTE: If the virtualization infrastructure contains a PSC. Now. perform a manual backup. enter the credentials for the ESXi host. 4. modifying or removing virtual machines. enter the ESXi host name for the HPE OmniStack host in the cluster where you created the datastore earlier in this process. When the virtual machine finishes uploading. When the Select A Destination Server wizard opens. 7. In the VMware hypervisor software. select the ESXi hostname for the HPE OmniStack host and the datastore you added earlier in this process. In Server name. you should only shut off the operating system of the PSC virtual machine after all of the other vCenter Server virtual machines have been shut down. keep in mind how frequently you make changes to the virtualization infrastructure (such as adding or removing hosts. you must power on the PSC virtual machine before you power on the vCenter Server virtual machines. Shut down the virtual machine running the vCenter Server. 6. 5. configurations with less frequent vCenter Server changes require a less aggressive policy. In the Username and Password fields. you must upload the vCenter Server onto the host. After the vCenter Server process initializes. 2. the backup includes your most recent changes. The Connect to Server Dialog appears. consider applying a different policy to the vCenter Server than you apply to the datastore. select File > Connect to Server. In the VMware hypervisor software. Procedure 1. Whenever you make a lot of changes to the vCenter Server. so that in the unlikely event you have to recover the vCenter Server. 4.0 between External Platform Services Controllers within a Site in a vSphere Domain. such as the Platform Services Controller (PSC). Due to enhanced capabilities. each of which require specific actions: • Restore one of many PSCs • Restore the only remaining PSC Restore one of many Platform Services Controllers (PSCs) using vSphere 6. A single client provides a centralized view of the managed zones. Decommission the failed PSC. For more information. Platform Services Controller (PSC) The Platform Services Controller (PSC) is a VMware component that allows you to configure single sign-on policies. see the VMware Knowledge Base article Using the cmsso command to unregister vCenter Server from Single Sign-On.0 Procedure overview Use this procedure to restore the only (or last remaining) instance of the PSC. there are two possible scenarios.Linked Mode deployment A Linked Mode deployment leverages functionality provided in VMware vSphere that allows you to group different components comprising the virtualization infrastructure into managed zones. Restore the Platform Services Controller (PSC) using vSphere 6. Procedure 1. and point them to a different PSC. You should configure the Linked Mode deployment as part of the VMware vCenter installation process. and revoke certificates. When recovering a failed PSC.5. rules. Linked Mode deployment and VMware software You can configure Linked Mode deployments using VMware vSphere 6. among other tasks. 3. Identify all the vCenter virtual machines that are pointing to the failed PSC. add certificate stores. and offers the capability to globally apply or share access privileges.0 or VMware vSphere 6.0 or 6. Power off the virtual machine containing the failed PSC. enabling servers to support an increased number of virtual machines. and license information across all of the shared components. 5. Install the replacement PSC. see the VMware Knowledge Base article Repointing the VMware vCenter Server 6. These managed zones can share resources and information.0 Procedure overview Use this procedure when one PSC has experienced failure and you must recover it. Procedure 1. For more information about Linked Mode. Identify all of the VMware virtual machines that you repointed earlier in this procedure and point them to the newly installed PSC. Hewlett Packard Enterprise recommends using vSphere 6. For more information.5 for Linked Mode deployments running vCenter on an HPE OmniStack host. and all of the other PSCs remain in the configuration. 2. the vSphere Documentation Center. Restore the virtual machine containing the PSC using the svt-backup-restore or svt-vm-restore as documented in the HPE OmniStack for vSphere Command Reference Guide Chapter 13: Deploy vCenter Server on an HPE OmniStack host 148 . Power on the restored virtual machine. Access the VMware Knowledge Base article Backing Up and Restoring All Platform Services Controller Instances.2. 3. Chapter 13: Deploy vCenter Server on an HPE OmniStack host 149 . SimpliVity changed the Phone Home feature. click Alarms > New Alarm Definition and follow the prompts. The OmniWatch feature comes enabled by default. free space. capacity levels exceeding thresholds. If necessary. server serial number. However. mail accounts. You can only use svt-support commands as described in the HPE OmniStack for vSphere Command Reference Guide. and Virtual Controller name. memory size). Under Settings. IP addresses or virtual machine data). and datastore details (name. You cannot configure Phone Home through SimpliVity options in vSphere Web Client. For example. You can disable and enable it again at any time through the svt-support-agent-control command. OmniWatch opens cases for alarms on drive failure. SimpliVity recommends that you use vSphere settings to set up SMTP server information. and OmniStack Accelerator alarms. click General > Edit > Mail. see the VMware documentation. It also contains details on the cluster. and alarm definitions.com/support/hpesc). For example.Chapter 14: Support This section contains the following topics: • Phone Home • OmniWatch • Create a Support Capture file Phone Home You can configure automatic support notification (Phone Home) to send messages to specific administrators about events and issues that may help them diagnose and correct them.5. For example. The report does not contain any user information (for example. disabling OmniWatch prevents critical proactive monitoring data from reaching Support. physical capacity. Instead of using Phone Home. Therefore you should make sure it stays within your secure enterprise intranet. To define alarms. configure it for each cluster in your federation. Phone Home can send a message with event details to the address you defined through Phone Home. The message is not encrypted. Chapter 14: Support 150 . Then add the SMTP server information and mail account. see the HPE OmniStack for vSphere Command Reference Guide. you can configure mail by clicking vCenter Server and the Manage tab. For more information on using the support-agent-control command.1. For more details on using vSphere Web Client options. Starting with OmniStack 3. You can also test OmniWatch connectivity and configure it to communicate with a proxy server as described in the SimpliVity knowledge base article "How to Configure and Verify OmniWatch Connectivity. it immediately opens a case that SimpliVity representatives can review to confirm the serverity. OmniWatch sends the reports to a SimpliVity server in the cloud over HTTPS using SSL encryption on port 443. contact Customer Support (http://www. If you use Phone Home. host." For more information on OmniWatch. the representative contacts you to provide assistance and resolve the issue as soon as possible. number of OmniStack hosts. Once a day. OmniWatch sends a report that includes information on the system status and significant events. If OmniWatch detects an alarm or critical error. if a significant event occurs in the federation.hpe. OmniWatch SimpliVity OmniWatch automatically monitors the health of each OmniStack host in your Federation to provide you with enhanced support. and day>" (for example. leave the selection of Save File and click OK. core files. you need to reauthenticate your identity by entering your vCenter Server account. click HPE SimpliVity Federation. When done (for all the listed hosts).Create a Support Capture file The Support Capture option provides a wizard to walk you through the process of gathering diagnostic data from one or more of your OmniStack hosts. For example. Chapter 14: Support 151 . and click All HPE SimpliVity Actions > Create Support Capture. Click Hosts. Procedure 1. clicking on the Download icon. From vSphere Web Client home. The Support Capture wizard minimizes to the Work in Progress portlet.tgz). Retrieve the Support Capture files (one at a time) by opening your default browser. 4. Click Create Support Capture to open the task and continue where you left off (even if you logged off and logged back on).10. 7. If you minimize the wizard before starting the creation process. 6. To see the status for all the hosts you selected. watch the progress bar at the bottom of the wizard. Support Capture files do not include user data or account information. Capture-10. Click Yes to proceed or No to cancel. a warning appears telling you that continuing with the process can impact performance. Send it to SimpliVity Support as instructed by your Support provider. Before you begin You can click the minimize arrow in the top-right corner of the wizard at any time during the Support Capture process. You can then send the file to your SimpliVity Support provider to troubleshoot the host issues. if you use Firefox. 11. The files use a .10--2016-03-27_19-59-37-MN. NOTE: If you select hosts that span more than one cluster. Save the file to a location you can remember. Enter your vCenter Server user name and password and click Next. right-click. Select one or more host from the Objects tab. click Next. 10. 9. and system status information that you can download to your default browser as a compressed file. For example. When complete for all hosts. 2. View the progress of the file creation for each host by watching the percentage in the progress bars. The data consists of log files. 3.10.TGZ extension and a name that starts with "Capture-<host IP address and year. Click Next to start creating the diagnostic files on the hosts you selected. and opening the folder with the Support Capture file. Click the link next to each host (one at a time) to download the diagnostic file to the Download directory of your default browser. you may need to complete other tasks while Support Capture creates the files. month. Use an account that has diagnostic privileges for the local vCenter Server and any connected vCenter Servers (if using Linked Mode or Enhanced Link Mode). 5. 8. Click Next to confirm the action on the selected hosts. click Finish. go to the Hewlett Packard Enterprise Support Center website: http://www.com/support/hpesc ◦ Hewlett Packard Enterprise Support Center: Software downloads http://www.com/assistance • To access documentation and support services.com/support/e-updates Appendix A: Support and other resources 152 . • To download product updates: ◦ Hewlett Packard Enterprise Support Center http://www. Review your product documentation to identify the recommended software update method.Appendix A: Support and other resources This section contains the following topics: • Support and other resources • HPE SimpliVity terminology • Documentation feedback Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance.hpe.hpe.com/support/softwaredepot • To subscribe to eNewsletters and alerts: http://www.hpe.hpe.hpe.com/support/downloads ◦ Software Depot http://www. model or version.com/support/hpesc Information to collect • Technical support registration number (if applicable) • Product name.hpe. and serial number • Operating system name and version • Firmware version • Error messages • Product-specific reports and logs • Add-on products or components • Third-party products or components Accessing updates • Some software products provide a mechanism for accessing software updates through the product interface. go to the Contact Hewlett Packard Enterprise Worldwide website: http://www. If your product includes additional remote support details. available at the Hewlett Packard Enterprise Support Center: http://www. You must have an HP Passport set up with relevant entitlements. use search to locate that information.com/services/proactivecarecentralgetstarted activation Warranty information To view the warranty for your product. secure submission of hardware event notifications to Hewlett Packard Enterprise.hpe. Remote support and Proactive Care information HPE Get Connected http://www. Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.com/services/proactivecareadvancedsupportedproducts service: Supported products list Proactive Care customer information Proactive Care central http://www.hpe. and Rack Products document. go to the Hewlett Packard Enterprise Support Center page titled "More Information on Access to Support Materials": http://www.hpe. For more information about CSR.com/services/proactivecarecentral Proactive Care service http://www.hpe. Networking.hpe. It provides intelligent event diagnosis. which will initiate a fast and accurate resolution based on your product's service level.hpe. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.com/support/Safety-Compliance-EnterpriseProducts Appendix A: Support and other resources 153 .hpe. Some parts do not qualify for CSR.hpe. contact your local service provider or go to the CSR website: http://www. it will be shipped directly to you so that you can install it at your convenience.com/support/AccessToSupportMaterials NOTE: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.• To view and update your entitlements. Storage. and automatic.com/support/selfrepair Remote support Remote support is available with supported devices as part of your warranty or contractual support agreement. Power.hpe. If a CSR part needs to be replaced. and to link your contracts and warranties with your profile. see the Safety and Compliance Information for Server.com/services/getconnected HPE Proactive Care services http://www.com/services/proactivecaresupportedproducts Supported products list HPE Proactive Care advanced http://www.com/services/proactivecare HPE Proactive Care service: http://www. see: http://www.com/support/Storage-Warranties HPE Networking Products http://www. if a cluster contains two HPE OmniStack hosts and one of those HPE OmniStack hosts loses connectivity with the cluster. Arbiter HPE OmniStack software that runs on the computer hosting the hypervisor management server or a different Windows computer that the HPE OmniStack hosts can access.hpe. and energy efficiency. Power.hpe.hpe. accelerated compression. It is required in every federation. (Note that an Arbiter must not run on any host within a cluster for which it is acting as a tie breaker.com/support/EnterpriseServers-Warranties HPE Storage Products http://www.) Appendix A: Support and other resources 154 . including company programs. Term Definition Accelerator A custom PCI card that provides non-volatile memory.hpe.com/support/ProLiantServers-Warranties and Options HPE Enterprise Servers http://www. The Arbiter provides the tie-breaking vote when a cluster contains an even number of HPE OmniStack hosts.com/support/Safety-Compliance-EnterpriseProducts Additional regulatory information Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). view the Safety and Compliance Information for Server. The Accelerator card communicates with the HPE OmniStack software.hpe. and cryptographic hashing.com/info/reach For Hewlett Packard Enterprise product environmental and safety information and compliance data. and Rack Products.Additional warranty information HPE ProLiant and x86 Servers http://www. Networking.hpe. A chemical information report for this product can be found at: http://www. including RoHS and REACH. For example. Storage.hpe.com/info/environment HPE SimpliVity terminology The following table contains HPE SimpliVity terms and definitions. the Arbiter acts as the tie breaker.com/support/Networking-Warranties Regulatory information To view the regulatory information for your product. product recycling.hpe. available at the Hewlett Packard Enterprise Support Center: http://www. see: http://www.com/info/ecodata For Hewlett Packard Enterprise environmental information. cluster A collection of HPE OmniStack hosts that share resources and provide high availability and load-balancing services. which runs the HPE OmniStack software. For more information. Multiple virtual machines can operate concurrently on the same (VM) physical host machine. HPE OmniStack host A host (server) containing an Accelerator card that communicates with the HPE OmniStack software and some supported virtualization software. refer to your hypervisor documentation. federation A collection of HPE OmniStack hosts managed in a single globally-unified management domain. and leveraging a third-site arbiter. HPE OmniStack The software running on the Virtual Controller.Term Definition Availability Zone Physically co-located collections of HPE OmniStack hosts. host A generic term referring to either an HPE OmniStack host or a standard host. If an Availability Zone goes offline. Virtual Controller A virtual machine dedicated to the HPE OmniStack host that runs the HPE OmniStack software. which you define as being likely to go offline together due to external forces. failure domain {internal} A collection of HPE OmniStack hosts that serve as potential high availability failover targets for each other for purposes of high availability and disaster recovery. to prevent data loss following the loss of a single Availability Zone. datastore A container for virtual machine files. software Intelligent Workload A feature that works with vSphere Distributed Resource Scheduler (DRS) to optimize Optimizer the location of virtual machines within a cluster. virtual machine A virtual computer environment that runs a guest operating system and associated application software. An OmniStack host uses a dedicated virtual machine called the Virtual Controller. OmniCube host See HPE OmniStack host. Appendix A: Support and other resources 155 . standard host A host with VMware ESXi host. including compute and storage resources. based on more sources of telemetry data (adding data location to CPU and memory usage) to intelligently configure (IWO) workloads. its peer ensures that host services continue. guest operating system The operating system that runs inside a virtual machine. Stretched Cluster An HPE SimpliVity configuration using an equal number of HPE OmniStack hosts within two Availability Zones. It does not contain HPE OmniStack software. For online help content. and publication date located on the front cover of the document. send any errors. edition. suggestions. or comments to Documentation Feedback (mailto:docsfeedback@hpe. and publication date located on the legal notices page. product version. To help us improve the documentation. part number.com). Appendix A: Support and other resources 156 . When submitting your feedback.Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. help edition. include the product name. include the document title.