HPE StoreVirtual Storage Application Aware Snapshot Manager Deployment Guide Abstract This guide contains instructions for installing and deploying the StoreVirtual Application Aware Snapshot Manager to simplify the task of managing credentials and creating snapshots for the HPE StoreVirtual solution by using a single application. For the latest version of this guide, see the Hewlett Packard Enterprise website http://www.hpe.com/support/storevirtualmanuals. Part Number: AX686-10091 Published: September 2018 Edition: 8
Contents Using the Application Aware Snapshot Manager... 4 Application Aware Snapshot Manager and VMware...4 Application Aware Snapshot Manager and Windows... 4 Using controlling IP addresses... 5 Using VSS snapshots... 5 Installing the Application Aware Snapshot Manager...6 Installing on Windows Server...6 Application Aware Snapshot Manager upgrade...7 Setting management group credentials... 7 Using the New Management Group Credentials window...8 Using the Credentials Wizard...8 Setting or changing default credentials...10 Configuring preferences...10 Configuring the snapshot backup type...10 Enabling support logs...10 Copying volume server assignments to snapshots for third-party VSS snapshots... 11 Configuring VMware snapshot options...11 Deleting a management group or default credentials from the console...12 Troubleshooting the Application Aware Snapshot Manager... 12 Event log applications... 16 Support and other resources...17 Accessing Hewlett Packard Enterprise Support... 17 Accessing updates...17 Websites... 18 Customer self repair...18 Remote support... 18 Documentation feedback... 19 2
Using the Application Aware Snapshot Manager Use StoreVirtual Application Aware Snapshot Manager to create application-managed snapshots in Windows and VMware environments. In Windows environments, the HPE StoreVirtual VSS provider is leveraged to quiesce VSS-aware applications before creating the snapshot. In VMware environments, the StoreVirtual Application Aware Snapshot Manager communicates with VMware Virtual Center Server to create VMware snapshots of virtual machines whose datastores reside on LeftHand OS volumes. Both one-time and scheduled snapshots are supported. NOTE: Application-managed snapshots is the term used in the StoreVirtual Centralized Management Console to designate snapshots that are taken using the Application Aware Snapshot Manager. Application Aware Snapshot Manager must be installed on each server running a backup application to create application-managed snapshots of a direct attached volume. This guide provides general information about installing and running the Application Aware Snapshot Manager with StoreVirtual Storage. Detailed information about creating and using application-managed snapshots is available in the HPE StoreVirtual Storage User Guide or HPE StoreVirtual Storage Online Help. The HPE StoreVirtual LeftHand OS Command Line Interface User Guide contains commands for scripting the application-managed snapshots. You can find detailed information on the Microsoft web site about using the Volume Shadow Copy Service. Application Aware Snapshot Manager and VMware When hosting VMware virtual machines on LeftHand OS volumes, the Application Aware Snapshot Manager creates volume snapshots that contain quiesced virtual machines. The resulting volume snapshots contain the virtual machine and its applications and its VMware snapshot. Mounting the application-managed snapshot allows the VMware snapshot manager to see the VMware snapshot in its history. Rolling back to the application-managed snapshot restores the virtual machine and its applications to a known and viable state. Requirements To use the Application Aware Snapshot Manager in VMware environments, the vsphere servers must be managed by VMware vcenter. The Application Aware Snapshot Manager must be installed on the vcenter server that manages all other vsphere servers connected to the LeftHand OS volumes. The IP address of the vcenter server must be configured as the controlling server in the CMC for all vsphere servers for which application-managed snapshots are to be taken. The Application Aware Snapshot Manager only supports single-volume datastores. That is, application-managed snapshots cannot be taken of volumes that are part of a datastore that spans multiple volumes. For information about the latest versions of VMware vcenter supported by the Application Aware Snapshot Manager, see the HPE Single Point of Connectivity Knowledge (SPOCK) website: www.hpe.com/storage/spock Application Aware Snapshot Manager and Windows The Application Aware Snapshot Manager quiesces applications and takes snapshots of single volumes and Microsoft Windows Cluster Shared Volumes (CSV), or snapshot sets. 4 Using the Application Aware Snapshot Manager
For more information, including the latest versions of Microsoft Windows Server supported by the Application Aware Snapshot Manager, see the SPOCK website: www.hpe.com/storage/spock IMPORTANT: Microsoft.NET Framework 3.5 or later is required to be on the system before installing the Application Aware Snapshot Manager. Using controlling IP addresses If you are using application-managed snapshots, you must assign a controlling server IP address to each server you create in the CMC. The IP address to use depends on your application type and environment. For Windows Failover Clusters, there will typically be more than one LeftHand OS server associated with the cluster. For this environment, enter a controlling IP address for each of the LeftHand OS servers in the Windows Failover Cluster. The following table describes which IP address should be entered in the controlling server IP address field for the LeftHand OS server. Table 1: Requirements for controlling IP addresses Application environment IP address to use Note VMware vcenter server IP address. Required Window Volume Shadow Copy Service (VSS) Windows Failover Cluster Environment SCVMM 1 Required for VSS: Physical IP address of the server hosting the VSS Provider. Physical IP address of each server hosting a VSS Provider in the Windows Failover Cluster. Since there is likely more than one LeftHand OS server in a Windows Failover Cluster, enter one physical IP address (as just described) in each of the related LeftHand OS server dialogs. Physical IP address of each server created by SCVMM. Generally required 1 Required Required For pre-10.0 versions of LeftHand OS software when status updates are needed. If the application-managed snapshot was created by a client other than the current instance of the CMC (for example, the CLI, a schedule, etc.) and status updates are desired. For Fibre channel connection types. Using VSS snapshots The Application Aware Snapshot Manager uses the VSS Provider to create an application-quiesced snapshot on the StoreVirtual Storage SAN. The VSS Provider is the LeftHand plug-in for the Microsoft VSS (Volume Shadow Copy Service) framework. Transportable snapshots Using the Application Aware Snapshot Manager 5
VSS snapshots can be used as transportable snapshots; that is, they can be mounted on a different server for restore or copy to tape. The VSS snapshot is usually called a managed snapshot this indicates that the snap has been created using AASM. A PIT snapshot is a Point In Time snapshot created by the SAN. It does not include the blocks that are in flight (changed) in memory of the computers writing to the volumes; thus, the snapshot may not be a recoverable image of the application. Deleting transportable snapshots To cleanly delete a transportable snapshot from the system, use the requestor application to perform the deletion. Installing the Application Aware Snapshot Manager To download the Application Aware Snapshot Manager software, go to the StoreVirtual downloads page at: http://www.hpe.com/info/storevirtualdownloads The default port used for the CIM connection is 5989. If you plan to use a different port, have the port number of the CIM connection ready for use during the installation. The ports used for LeftHand OS operations are listed in the LeftHand OS TCP and UDP port usage chapter of the HPE StoreVirtual Storage User Guide or HPE StoreVirtual Storage Online Help. Installing on Windows Server Procedure 1. Locate the application executable and double-click it to begin. The files are extracted to your system and the Setup Wizard opens. 2. Click Next to start the Setup Wizard. 3. Accept the terms of the license agreement and click Next. 4. Choose the installation location for the software or accept the default location and click Next. 5. Enter the port number for the CIM server connection or accept the default port number and click Next. 6. Click Install to continue the installation. 7. During installation, an important message displays with the requirement to set management group credentials. 8. Click Next when you have finished reading the message. 9. Click Finish to complete the installation. 10. After installation is complete, you must add credentials for management groups. See Setting management group credentials for instructions. 11. If you are using VMware integrations, you must also configure VMware integration credentials. See Configuring VMware snapshot options for instructions. Uninstall the Application Aware Snapshot Manager using Start > Control Panel > Programs and Features. 6 Using the Application Aware Snapshot Manager
Application Aware Snapshot Manager upgrade After you upgrade the Application Aware Snapshot Manager (which also includes an upgrade for the Authentication Console), management group credentials that were previously set are retained. Setting management group credentials Authenticating management groups on the SAN using management group credentials is required for using the Application Aware Snapshot Manager. Configure default credentials for multiple management groups that use the same credentials (user name and password). When you work with a management group that does not have unique credentials defined, the default credentials are used for authentication. For instructions to configure default credentials, see Setting or changing default credentials. Configure individual credentials for management groups that use unique credentials. For instructions, see Using the New Management Group Credentials window and Using the Credentials Wizard. Authentication is typically a one-time process. Update the authentication only if you changed any of the following: IP addresses of storage systems User name and password for logging in to storage systems The credentials required for using the Application Aware Snapshot Manager are: Management group name Management group user name and password IMPORTANT: The user must have full administrator privileges on the SAN. Use one of the following methods to set individual management group credentials: New Management Group Credentials window Enables you to add or change credentials for a specific management group, and test that the credentials are valid. Credentials Wizard Discovers all management groups on the network and enables you to add or change credentials for all discovered management groups, and test that the credentials are valid. CLI commands cachecredentials and clearcredentials. For more information, see the HPE StoreVirtual LeftHand OS Command Line Interface User Guide. TIP: When you add credentials in Application Aware Snapshot Manager, Recovery Manager, or the CLI, the credentials are saved and shared by all three tools. For example, if you previously added credentials in Recovery Manager, you do not need to add the credentials in the Application Aware Snapshot Manager. Using the Application Aware Snapshot Manager 7
Using the New Management Group Credentials window Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > New Management Group Credentials from the menu bar. 3. In the Management Group Properties window: a. In Management group, enter a valid management group. TIP: If you previously entered default credentials for your management groups, you can select Use default credentials. The default user name and password are automatically entered and you can skip to step e. If you do not make this selection, continue with the next step. b. In User name, enter the user name for the management group. This user must have full administrator privileges on the SAN. c. In Password, enter the password for the user. d. In Confirm Password, re-enter the password for the user. e. To verify that the specified user has full administrator privileges on the SAN, click Test. f. In the Test window, enter either an IP address associated with a storage system in the management group, or the virtual IP addresses (VIPs) of the clusters in the management group. If entering multiple IP addresses, use semicolons (;) to separate them in the list. NOTE: Be sure to click Save to retain your IP addresses so you do not have to re-enter them again. TIP: Hewlett Packard Enterprise recommends that you enter the VIPs. Entering the VIPs ensures that Application Aware Snapshot Manager continues to display management group information if a storage system in the management group is inaccessible. g. In the Test window, click OK. If the test is successful, a corresponding message appears in the Management Group Properties window. If the test fails, verify the correct credentials for that management group in the CMC and try again. 4. Click OK to finish and add the credentials to the StoreVirtual credentials cache. Using the Credentials Wizard IMPORTANT: The Authentication Console application operates as a plug-in for the Microsoft Management Console (MMC). For the Credentials Wizard to discover the management groups, you must configure the firewall to allow the MMC to send and receive UDP traffic on port 27491. 8 Using the Application Aware Snapshot Manager
Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > Credentials Wizard from the menu bar. 3. The Credentials Wizard displays a window for each of the discovered management groups. 4. Do one of the following: a. Use the default credentials by selecting Use default credentials. NOTE: If Use default credentials is disabled, then default credentials have not been defined. Default credentials can be added by canceling the Credentials Wizard and selecting Action > New Default Credentials from the menu bar. b. Enter the user name and password, and confirm the password. 5. Click Test. 6. In the Test window, enter either an IP address associated with a storage system in the management group, or the virtual IP addresses (VIPs) of the clusters in the management group. If entering multiple IP addresses, use semicolons (;) to separate them in the list. NOTE: Be sure to click Save to retain your IP addresses so you do not have to re-enter them again. TIP: Hewlett Packard Enterprise recommends that you enter the VIPs. Entering the VIPs ensures that Application Aware Snapshot Manager continues to display management group information if a storage system in the management group is inaccessible. 7. In the Test window, click OK. 8. If the test is successful, a corresponding message is displayed under the Test button on the Credentials Wizard window. 9. If the test fails, verify the correct credentials for that management group in the CMC and try again. 10. If default credentials are used to test the login and the test is successful, the default user name and password become the credentials used by this management group, provided that you commit the wizard changes at the summary screen. 11. After testing the credentials, do one of the following: To commit changes if you are finished, click Done. To set credentials for the next management group, click Next. NOTE: If you do not want to set credentials for a particular management group, you can click Skip. 12. When you click Done, the Credential Wizard Summary window displays the status for all management groups that were tested. 13. To finish and add the credentials to the StoreVirtual credentials cache, click OK. Using the Application Aware Snapshot Manager 9
Setting or changing default credentials If you use the same credentials (user name and password) for multiple management groups, use default credentials for these management groups. Additionally, when you are working with a management group that does not have unique credentials defined, the default credentials are used for authentication. Use the New Default Credentials window to set default credentials or to change the current default credentials. Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > New Default Credentials from the menu bar. 3. Enter the user name and password, and confirm the password. 4. Click OK to save the default credentials. Configuring preferences In LeftHand OS version 11.0 or later, use the Authentication Console Preferences window to configure these Application Aware Snapshot Manager preferences: Configuring the snapshot backup type Enabling support logs Copying volume server assignments to snapshots for third-party VSS snapshots NOTE: If this is a new installation of Application Aware Snapshot Manager, the support logs directory will be C:\ProgramData\HPEStoreVirtualSupportLogs\. Configuring the snapshot backup type Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > Preferences from the menu bar. 3. Specify the snapshot backup type. 4. Click OK. Enabling support logs You can enable support logs on the client OS to debug problems with the Application Aware Snapshot Manager. After you change the configuration, you are prompted to restart the StoreVirtual VSS CIM Server and StoreVirtual VSS Provider services. Any changes you make are detected only after the restart. If you do not restart immediately, the changes are detected the next time the services are restarted. 10 Using the Application Aware Snapshot Manager
Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > Preferences from the menu bar. 3. Select Enable support logs. 4. Specify the Support logs directory. 5. Select the Max log file size. 6. Click OK. Your changes are saved and you are prompted to restart. 7. If you want your changes to take effect immediately, Click Yes. If you do not want the changes to take effect immediately, click No. Copying volume server assignments to snapshots for third-party VSS snapshots You can copy volume server assignments to snapshots for third-party VSS snapshots. When a third-party backup application creates an application-managed snapshot of volumes attached to the server, the snapshots inherit the server assignments defined for the volume. Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > Preferences from the menu bar. 3. Select Copy volume server assignments to snapshots for 3rd party VSS snapshots. 4. Click OK. Configuring VMware snapshot options Prerequisites To use the options in this task, VMware and the Application Aware Snapshot Manager must be installed on the same server. Procedure 1. Open the Authentication Console from the Start > Programs > HPE > HPE StoreVirtual > Authentication Console menu. 2. Select Action > VMware Integration Options from the menu bar. The VMware Integration Options menu item is available only if VMware and the Application Aware Snapshot Manager are installed on the same server. 3. In the VMware Snapshot Options window, select or set the options you want to use. 4. Click OK. Using the Application Aware Snapshot Manager 11
Deleting a management group or default credentials from the console Procedure 1. In the right pane, select the management group or default credentials to delete. 2. Right-click and select Delete. Troubleshooting the Application Aware Snapshot Manager Cause The Application Aware Snapshot Manager VSS Provider runs as an NT service. You can view both the Volume Shadow Copy service and the VSS Provider service in the Computer Management window under Services and Applications > Services. Table 2: Application Aware Snapshot Manager Issues and solutions Issue Restarting the VSS Provider service. When creating an application-managed snapshot of a cluster shared volume, an error message displays on the passive server. Solution The VSS Provider service starts automatically. If you check in the Services list and it is not started, you can start it manually. If you have a Hyper-V configuration with cluster shared volumes, you may see the following error when an application aware managed snapshot is taken on one of the cluster shared volumes. Cluster Shared Volume 'Volume3' ('CSV3') is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network through the node that owns the volume. This may result in degraded performance. If redirected access is turned on for this volume, please turn it off. If redirected access is turned off, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished. The error indicates that the volume is no longer accessible, but the volume is in a passive state on that particular node (and active on the other node). The snapshot is taken successfully. You can ignore this message. Table Continued 12 Using the Application Aware Snapshot Manager
Issue An error occurs when an application-managed snapshot is created during NIC failover on an application server. Snapshots fail with the following error: Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine. After creating an application-managed snapshot on a VMware volume, the event log may include an error message such as: Failed to create application managed snapshot. or Failed to create snapshot for one or more VMs. Solution If an application-managed snapshot is created while a NIC failover is in progress on an application server, the following error may display in the Windows event log: App-Managed SS Failed: Could not get list of volumes on server Wait until the NIC failover has completed. Application-managed snapshots should then resume successfully. When taking application-managed snapshots via the CMC or the CLI on a volume that contains a large number of virtual machines, some virtual machines may fail due to a failure to quiesce. The culprit could either be the VMware tools sync driver or MS VSS. The failure is not reported in the CMC as the CMC is not currently logging VM quiesce failures. For more information, see the VMware KB article: http://kb.vmware.com/selfservice/microsites/ search.do? language=en_us&cmd=displaykc&externalid= 101819 The process of creating an application-managed snapshot on a VMware volume consists of the following steps: 1. Snapshots of all virtual machine volumes on the VMware volume are created. 2. The application-managed snapshot is created. 3. The intermediate virtual machine snapshots (in step 1) are deleted. If a virtual machine is busy when the virtual machine snapshots are being created, the VMware API may time out. The application-managed snapshot is still created, but the intermediate virtual machine snapshots are not deleted. The virtual machine snapshot manager will indicate that the virtual machine snapshots were created, but will not display an indication that they were deleted. To resolve this issue, you must manually delete the intermediate virtual machine snapshots. Table Continued Using the Application Aware Snapshot Manager 13
Issue If you have a failover cluster configuration using Windows Server 2012 servers and an applicationmanaged snapshot is taken on a volume, the following error message may display in the Windows Application log on the cluster server that does not own the volume: Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. Application-managed snapshots do not work on SMB file shares presented by a Windows Failover Cluster. It is possible for scheduled application-managed snapshots to fail if the application server is overloaded and unable to quiesce the application. RDM volumes and application-managed snapshot support. Solution This message can be ignored. The snapshot was take successfully on the cluster server where the volume resides. With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot is taken on an SMB file share that is presented by a Windows Failover Cluster. The snapshot appears as if it is a managed snapshot, but because SQL Server was not quiesced, it is not a true managed snapshot. To resolve this issue, ensure that scheduled snapshots are set to times where there is less activity on the application server. Creating application-managed snapshots of volumes that are attached to VMware virtual machines (VM) as a Raw Device Mapping (RDM) in virtual compatibility mode do not result in snapshots on StoreVirtual Storage. When using StoreVirtual Application Aware Snapshot Manager to create a snapshot of a VMFS data store that contains VMs using RDM disk resources, VMware takes a snapshot of the RDMs and maintains changes to these RDMs in the same VMFS data store. You can locate files representing the snapshot of a RDM by browsing to the VM s location on VMFS data store. RDMs in physical compatibility mode are not supported with StoreVirtual. Table Continued 14 Using the Application Aware Snapshot Manager
Issue Creating application-managed snapshots for VMware virtual machines may cause significant delays in the snapshot process. Solution To resolve this issue, you can disable memory snapshots by adding a key to the Registry Editor: 1. Open the Registry Editor and go to the path HKLM\Software\HP\P4000\Client Settings\1.0. If this path does not exist, you can create it. 2. Create a string value called VMMemorySnapshot and set it to false (VMMemorySnapshot=false). The following error message displays when you attempt managed snapshots of associated volumes from different management groups: Cannot create an application-managed snapshot because an associated volume cannot be reached. The associated volume may be in another management group, which is an unsupported configuration. Make sure all associated volumes are in the same management group and try again. Application-managed snapshots do not work on SMB file shares presented by a Windows Failover Cluster. NOTE: This solution only applies if you are running version 10.0 or 10.5. In version 11.0, there is a Snapshot the virtual machine's memory option on the VMware Snapshot Options window. To disable memory snapshots, ensure that this option is not selected. For more information, see Configuring VMware snapshot options. The Centralized Management Console (CMC) does not support managed snapshots of associated volumes from different management groups. Do not attempt this type of snapshot. With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot is taken on an SMB file share that is presented by a Windows Failover Cluster. The snapshot appears as if it is a managed snapshot, but because SQL Server was not quiesced, it is not a true managed snapshot. Table Continued Using the Application Aware Snapshot Manager 15
Issue An Active Directory user with read-only permissions can pass the Authentication Console credentials test, but application-managed snapshots will fail. An application-managed snapshot cannot be taken when Symantec BackUp Exec is simultaneously running on the server where the volumes are mounted. Solution The Application Aware Snapshot Manager Authentication Console does not differentiate between read-only users and those who have authorization to create snapshots. The LeftHand OS will deny the Application Aware Snapshot Manager the right to create snapshots on behalf of a read-only user; therefore, snapshots are not taken. To resolve this issue, enter an Active Directory user with administrator capabilities into the Authentication Console. If this issue occurs, the CMC will indicate that a point-in-time snapshot should be taken. When Symantec BackUp Exec has completed the backup, you can successfully take an applicationmanaged snapshot. As a best practice, ensure that application-managed snapshots are not scheduled or taken at the same time a backup is being performed. Event log applications The event log reports issues with the VSS Provider, the iscsi initiator, and Volume Shadow Copy. Open the event log to view messages about those applications. 16 Using the Application Aware Snapshot Manager
Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/ assistance To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:www.hpe.com/support/hpesc Information to collect Technical support registration number (if applicable) Product name, model or version, 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. Review your product documentation to identify the recommended software update method. To download product updates, go to either of the following: Hewlett Packard Enterprise Support Center Get connected with updates page:www.hpe.com/support/e-updates Software Depot website:www.hpe.com/support/softwaredepot To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page:www.hpe.com/support/accesstosupportmaterials Support and other resources 17
IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Websites Website Hewlett Packard Enterprise Information Library Hewlett Packard Enterprise Support Center Contact Hewlett Packard Enterprise Worldwide Subscription Service/Support Alerts Software Depot Customer Self Repair Insight Remote Support Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix Storage products Storage Information Library Storage white papers and analyst reports Storage partner and store locator Link www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs www.hpe.com/storage/spock www.hpe.com/info/storage www.hpe.com/info/storage/docs www.hpe.com/storage/whitepapers www.hpe.com/service_locator Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR. For more information about CSR, contact your local service provider or go to the CSR website: www.hpe.com/support/selfrepair Remote support Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support. For more information and device support details, go to the following website: 18 Support and other resources
www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Support and other resources 19