HPE StoreVirtual 3200 Application Aware Snapshot Manager User Guide Abstract The StoreVirtual Application Aware Snapshot Manager simplifies the tasks of managing credentials and creating snapshots for the HPE StoreVirtual solution by using a single application. This guide contains instructions for installing and deploying the StoreVirtual Application Aware Snapshot Manager. For the latest version of this guide, see the StoreVirtual 3200 documentation on the Storage Information Library at http://www.hpe.com/info/sv3200- docs. Part Number: 865543-002 Published: November 2017 Edition: 1
Contents Application Aware Snapshot Manager...5 Application Aware Snapshot Manager and VMware...5 Application Aware Snapshot Manager and Windows... 6 Controlling IP address...6 VSS snapshots... 7 Application Aware Snapshot Manager Installation...7 Installing on Windows Server...8 Installing Application Aware Snapshot Manager on VMware...9 Application Aware Snapshot Manager upgrade...10 Management group credentials... 10 Creating credentials with the New Management Group Credentials window...11 Creating credentials with the Credentials Wizard... 12 Setting or changing default credentials...14 Preferences configuration... 15 Configuring the snapshot backup type...16 Enabling support logs...16 Copying volume server assignments to snapshots for third-party VSS snapshots... 17 Configuring VMware snapshot options... 17 VMware Snapshot options... 18 Deleting a management group or default credentials from the console...18 Troubleshoot the Application Aware Snapshot Manager... 18 VSS Provider service is not running...18 Error message when creating an application-managed snapshot of a cluster shared volume...19 Error message when creating application-managed snapshot during NIC failover... 19 Snapshots fail with error...19 Error creating snapshot on VMware volume... 20 Error message when creating application-managed snapshot in Windows Server 2012 failover cluster... 20 Application-managed snapshots do not work when SQL Server not quiesced...21 Scheduled application-managed snapshots might fail... 21 Snapshots are not created when using AASM...21 Application-managed snapshots might experience delays in VMware vsphere... 22 Error message when attempting snapshots of volumes from different management groups... 22 Read-only Active Directory user causes application-managed snapshots to fail... 23 Cannot take application-managed snapshot when running Symantec BackUp Exec...23 Event log applications... 23 Websites... 24 Support and other resources...25 Accessing Hewlett Packard Enterprise Support... 25 Accessing updates...25 Customer self repair...26 Remote support... 26 Warranty information...26 Regulatory information...27 2 Contents
Documentation feedback... 27 Contents 3
Copyright 2016, 2017 Hewlett Packard Enterprise Development LP
Application Aware Snapshot Manager Use StoreVirtual Application Aware Snapshot Manager (AASM) 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 StoreVirtual OS volumes. Both one-time and scheduled snapshots are supported. This guide provides general information about installing and running the Application Aware Snapshot Manager with StoreVirtual Storage. More snapshot information is available: Details for creating and using application-managed snapshots are available in the HPE StoreVirtual 3200 Management Console User Guide or the HPE StoreVirtual 3200 Management Console Online Help. Commands for scripting the application-managed snapshots are in the HPE StoreVirtual 3200 Software CLI Reference Guide. Details for using the Volume Shadow Copy Service are on the Microsoft website. NOTE: Application-managed snapshots is the term used in the StoreVirtual 3200 Management Console to designate snapshots that are taken using the Application Aware Snapshot Manager. Application Aware Snapshot Manager and VMware When hosting VMware virtual machines on StoreVirtual 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 The requirements for Application Aware Snapshot Manager and VMware include: Using VMware vcenter to manage the vsphere servers. In VMware vsphere versions 6.0 and greater, vcenter can be installed as an appliance on a Linux-based server. When using a vcenter appliance, the Application Aware Snapshot Manager must be installed on a Windows Server. The Authentication Console is then used to configure AASM to point at the IP address of the vcenter appliance. When using VMware vcenter on a Windows Server, AASM can be installed on the same Windows server and will then work locally with the vcenter. Installing the Application Aware Snapshot Manager on the vcenter server that manages all other vsphere servers that are connected to the StoreVirtual OS volumes. Application Aware Snapshot Manager 5
Configuring the vcenter server (using the IP address) as the controlling server in the Management Console for all vsphere servers that are taking application-managed snapshots. Using single-volume datastores only. Application-managed snapshots cannot be taken of volumes that are part of a datastore that spans multiple volumes. Supported versions of VMware vsphere The Application Aware Snapshot Manager is supported with VMware vsphere versions 6.0 and 6.5. Application Aware Snapshot Manager and Windows The Application Aware Snapshot Manager quiesces applications and takes snapshots of single volumes and of Microsoft Windows Cluster Shared Volumes (CSV), or snapshot sets. Requirements Install Microsoft.NET Framework 3.5 or later on the system before installing the Application Aware Snapshot Manager. Supported versions of Microsoft Windows Server The Application Aware Snapshot Manager supports the following versions of Microsoft Windows Server: Windows Server 2012 R2 Windows Server 2016 Controlling IP address If you are using application-managed snapshots, you must assign a controlling server IP address to each server you create in the SVMC. The IP address to use depends on your application type and environment. For Windows Failover Clusters, there will typically be more than one StoreVirtual OS server associated with the cluster. For this environment, enter a controlling IP address for each of the StoreVirtual OS servers in the Windows Failover Cluster. Requirements for controlling IP addresses describes which IP address to enter in the controlling server IP address field for the StoreVirtual OS server. 6 Application Aware Snapshot Manager and Windows
Table 1: Requirements for controlling IP addresses Application environment IP address Requirement VMware vcenter server IP address Required Windows Server The IP address of the Windows server hosting the Application Aware Snapshot Manager. If you are using Windows Server Failover Cluster, you must: Install the Application Aware Snapshot Manager on each server in the cluster. In the Microsoft Management Console, create a corresponding server in a server cluster with its IP address as the controlling IP address. Required VSS snapshots The Application Aware Snapshot Manager uses the VSS Provider to create an application-quiesced snapshot on the HPE StoreVirtual SAN. The VSS Provider is the StoreVirtual plug-in for the Microsoft VSS (Volume Shadow Copy Service) framework. Transportable snapshots VSS snapshots can be used as transportable snapshots; that is, they can be mounted on a different server for restoring or copying to tape. The VSS snapshot is called a managed snapshot. A managed snapshot is a snap that has been created using the AASM. A point-in-time (PIT) snapshot is created by the SAN. A PIT snapshot does not include the blocks that are in flight (changed) in the memory of the computers writing to the volumes. Therefore, the snapshot may not be a recoverable image of the application. Deleting transportable snapshots To delete a transportable snapshot from the system cleanly, use the requestor application to perform the deletion. Application Aware Snapshot Manager Installation Requirement Application Aware Snapshot Manager must be installed on each server running a backup application to create application-managed snapshots of a direct-attached volume. Download the software Download the Application Aware Snapshot Manager software, from the HPE StoreVirtual 3200 software download page at: https://h20566.www2.hpe.com/hpsc/swd/public/detail?switemid=co-182468-1 VSS snapshots 7
Ports 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 StoreVirtual OS operations are listed in the StoreVirtual OS TCP and UDP port usage chapter of the HPE StoreVirtual 3200 Management Console User Guide. Installing on Windows Server After installing the software, you must configure credentials: Add credentials for management groups. If you are using VMware integrations, you must also configure VMware integration credentials. If you must uninstall the Application Aware Snapshot Manager, use Start > Control Panel > Programs and Features. 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. Start the Setup Wizard, click Next. 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, the message Reminder to set management group credentials opens, describing requirement to set management group credentials. 8 Installing on Windows Server
Figure 1: Reminder to set management group credentials 8. Click Next when you have finished reading the message. 9. Click Finish to complete the installation. Installing Application Aware Snapshot Manager on VMware Application Aware Snapshot Manager works only on Windows systems. You can install Application Aware Snapshot Manager on either of the following: Windows server or server cluster with vcenter installed Windows server or server cluster pointing to a vcenter appliance installed on a Linux-based server Procedure 1. Copy the installer to the desktop. 2. Run the installer and accept all default selections. 3. Open the Authentication Console after the installation completes. 4. Select Action > VMware Intergration Options. 5. Configure the snapshot options and enter your vcenter credentials in the VCenter Services Login box as shown in VMware Snapshot Options. For a local vcenter, you can leave the IP address blank, but ensure that the HTTPS port is 443. For a remote or an appliance vcenter, you must enter the IP address of the vcenter appliance. Ensure that the HTTPS port is 443. Installing Application Aware Snapshot Manager on VMware 9
Figure 2: VMware Snapshot Options 6. Verify that the configuration works by clicking Test. 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. Management group credentials To use the Application Aware Snapshot Manager, management group credentials must be used to authenticate management groups on the SAN. There are two types of credentials: Default Credentials - 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. Individual Credentials - Configure individual credentials for management groups that use unique credentials. Authentication Authentication is typically a one-time process. You only update the authentication if you changed either of the following: 10 Application Aware Snapshot Manager upgrade
IP addresses of storage systems User name and password for logging in to storage systems Required credentials for using The credentials required for using the Application Aware Snapshot Manager are: Management group name Management group user name and password. The user must have full administrator privileges on the SAN. Configuration methods 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. You can also test that the credentials are valid. CLI commands Two commands are available for credentials: cachecredentials and clearcredentials For more information, see the HPE StoreVirtual 3200 Software CLI Reference Guide. TIP: When you add credentials in Application Aware Snapshot Manager, Recovery Manager, or the CLI, all three tools save and share the credentials. For example, if you previously added credentials in Recovery Manager, you do not need to add the credentials in the Application Aware Snapshot Manager. Creating credentials with 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. Enter a valid Management group in the Management Group Properties window. 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 continue to the testing step. If you do not make this selection, continue with the next step. 4. Enter a user name for the management group. This user must have full administrator privileges on the SAN. 5. Enter the Password for the user. Creating credentials with the New Management Group Credentials window 11
6. Re-enter the password for the user. 7. Verify that the specified user has full administer privileges. a. Click Test. b. 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. TIP: Hewlett Packard Enterprise recommends that you enter the VIPs. Entering the VIPs ensure that Application Aware Snapshot Manager continues to display management group information if a storage system in the management group is inaccessible. c. Save your IP addresses so you do not have to enter them again. Click Save. 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 Management Console and try again. 8. Finish and add the credentials to the StoreVirtual credentials cache. Click OK. Creating credentials with the Credentials Wizard Prerequisites 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. 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. The Credentials Wizard displays a window for each of the discovered management groups. as shown in Opening the Credentials Wizard. 12 Creating credentials with the Credentials Wizard
Figure 3: Opening the Credentials Wizard 3. Use this table to determine the correct step for your installation: IF you want to use... the default credentials THEN do the following... Select Use default credentials. If Use default credentials is disabled, then default credentials have not been defined. Add default credentials as follows: a. Cancel the Credentials Wizard. b. Select Action > New Default Credentials from the menu bar. individual credentials Enter the user name, password, and confirm the password. 4. Verify the credentials: Application Aware Snapshot Manager 13
a. Click Test. The Test window is displayed. b. 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. TIP: Hewlett Packard Enterprise recommends that you enter the VIPs. Entering the VIPs ensure that Application Aware Snapshot Manager continues to display management group information if a storage system in the management group is inaccessible. c. Retain your IP addresses so you do not have to re-enter them. Click Save. d. Click OK. If the test is successful, a corresponding message is displayed under the Test button on the Credentials Wizard window. 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 if you commit the wizard changes at the summary screen. If the test fails, verify the correct credentials for that management group in the Management Console and try again. 5. After testing the credentials, do one of the following: IF you... are finished entering credentials THEN do the following... a. Click Done and commit the changes. When you click Done, the Credential Wizard Summary window displays the status for all management groups that were tested. b. Continue with the next step. want to set credentials for the next management group a. Click Next. b. Repeat steps 3-5 for the next management group. If you do not want to enter credentials for a specific management group, click Skip. 6. Finish and add the credentials to the StoreVirtual credentials cache. Click OK. 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. 14 Setting or changing 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. Preferences configuration 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 Figure 4: Preferences window Preferences configuration 15
NOTE: Although the Preferences window shows HPStoreVirtualSupportLogs as the log directory, it will actually display as HPEStoreVirtualSupportLogs (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. Snapshot backup types There are four snapshot backup types: Full backup All files, regardless of whether they have been marked as backed up or not, are saved. Full backup is the default backup type and schema, and all writers support it. Incremental backup Files created or changed since the last full or incremental backup are saved. Files are marked as having been backed up. A requester can implement this type of backup on a particular writer only if it supports the VSS_BS_INCREMENTAL schema. If a requester's backup type is VSS_BT_INCREMENTAL and a particular writer's backup schema does not support that backup type, the requester always performs a full backup (VSS_BT_FULL) on that writer's data. Differential backup Files created or changed since the last full backup are saved. Files are not marked as having been backed up. A requester can implement this type of backup on a particular writer only if it supports the VSS_BS_DIFFERENTIAL schema. If a requester's backup type is VSS_BT_DIFFERENTIAL and a particular writer's backup schema does not support that backup type, the requester will always perform a full backup (VSS_BT_FULL) on that writer's data. Copy backup with no history update Files on disk will be copied to a backup medium regardless of the state of each file's backup history, and the backup history will not be updated. A requester can implement this type of backup on a particular writer only if it supports the VSS_BS_COPY schema. If a requester's backup type is VSS_BT_COPY and a particular writer's backup schema does not support that type of backup, the requester will always perform a full backup (VSS_BT_FULL) on that writer's data. 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. 16 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. 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. Copying volume server assignments to snapshots for third-party VSS snapshots 17
VMware Snapshot options Configurable options You can configure the following options with the VMware Snapshot Options window: Snapshot the virtual machine's memory Create a snapshot of the virtual machine's memory - This option is enabled by default. Creating application-managed snapshots for VMware virtual machines may cause significant delays in the snapshot process. To avoid this issue, clear the check box for the Snapshot the virtual machine's memory option. Quiesce the guest file system Quiesces the guest OS during the creation of the VMware snapshot. Configure the Virtual Center Services HTTPS port number The HTTPS port is the port number on the Virtual Center Server that connects with vsphere hosts. The default port number is 443, but this port number can be changed if the VMware setting is changed. Configure a set of Virtual Center credentials Adds the Virtual Center credentials (user and password) to the StoreVirtual credentials cache. The credentials are used by Application Aware Snapshot Manager to interact with the Virtual Center server. When the VMware Virtual Center credentials are in the StoreVirtual credentials cache, these credentials are used for all login connections between Application Aware Snapshot Manager and Virtual Center. When the VMware Virtual Center credentials are not in the StoreVirtual credentials cache, the service credentials are used. Test the Virtual Center login's user name and password Validates the connection to the Virtual Center Server using the specified HTTPS port number, user name, and password. 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. Troubleshoot the Application Aware Snapshot Manager 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. VSS Provider service is not running Symptom The VSS Provider service is not running. 18 VMware Snapshot options
Action The VSS Provider service starts automatically. If you check in the Services list and it is not started, you can start it manually. Error message when creating an application-managed snapshot of a cluster shared volume Symptom 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. Cause 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). Action The snapshot is taken successfully. You can ignore this message. Error message when creating application-managed snapshot during NIC failover Symptom 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 Action Wait until the NIC failover has completed. Application-managed snapshots should then resume successfully. Snapshots fail with error Symptom 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. Error message when creating an application-managed snapshot of a cluster shared volume 19
Cause When taking application managed snapshots via the management console 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 management console as the management console is not currently logging VM quiesce failures Action For more information, see the VMware KB article: http://kb.vmware.com/selfservice/microsites/search.do? language=en_us&cmd=displaykc&externalid=1018194 Error creating snapshot on VMware volume Symptom 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. Cause 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. Action Manually delete the intermediate virtual machine snapshots. Error message when creating application-managed snapshot in Windows Server 2012 failover cluster Symptom 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. 20 Error creating snapshot on VMware volume
Action This message can be ignored. The snapshot was take successfully on the cluster server where the volume resides. Application-managed snapshots do not work when SQL Server not quiesced Symptom Application-managed snapshots do not work on SMB file shares presented by a Windows Failover Cluster. Cause With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot is taken on a Windows Failover Cluster SMB file share. The snapshot appears as if it is a managed snapshot, but because SQL Server was not quiesced, it is not a true managed snapshot. Action There is no workaround for this issue. Scheduled application-managed snapshots might fail Symptom Scheduled application-managed snapshots might fail. Cause If the application server is overloaded, it may be unable to quiesce the application. Action Ensure that scheduled snapshots are set to times where there is less activity on the application server. Snapshots are not created when using AASM Symptom No snapshots are created on StoreVirtual storage when using StoreVirtual Application Aware Snapshot Manager. Cause Creating application-managed snapshots does not result in snapshots on StoreVirtual Storage in the following configuration: StoreVirtual volumes that are attached to VMware virtual machines (VM) as a Raw Device Mapping (RDM) in virtual compatibility mode When using AASM to create a snapshot of a VMFS data store that contains VMs using RDM disk resources, vsphere takes a snapshot of the RDMs and maintains changes to these RDMs in the same VMFS data store. Application-managed snapshots do not work when SQL Server not quiesced 21
Action RDMs in physical compatibility mode are not supported with StoreVirtual. Application-managed snapshots might experience delays in VMware vsphere Symptom Creating application-managed snapshots for VMware virtual machines might cause significant delays in the snapshot process. Solution 1 Cause Taking a snapshot in the vsphere Client captures the entire state of the virtual machine at the time the snapshot is taken. By default, capturing the entire state includes a memory snapshot, which makes the snapshot operation take longer to complete. Disabling memory snapshots on VMWare virtual machines when creating application-managed snapshots improves snapshot performance. Action If you are running version 10.0 or 10.5, 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). Solution 2 Action 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. See VMware Snapshot options for more information. Error message when attempting snapshots of volumes from different management groups Symptom When attempting to take application-managed snapshots of volumes from different management groups, the following error message displays: 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. Cause The Management Console does not support managed snapshots of associated volumes from different management groups. 22 Application-managed snapshots might experience delays in VMware vsphere
Action Do not attempt this type of snapshot. Read-only Active Directory user causes application-managed snapshots to fail Symptom An Active Directory user with read-only permissions can pass the Authentication Console credentials test, but application-managed snapshots will fail. Cause The Application Aware Snapshot Manager Authentication Console does not differentiate between readonly users and users who have authorization to create snapshots. The StoreVirtual 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. Action Enter an Active Directory user with administrator permissions into the Authentication Console. Cannot take application-managed snapshot when running Symantec BackUp Exec Symptom The Management Console indicates that a point-in-time snapshot should be taken when attempting to take an application-managed snapshot. Cause An application-managed snapshot cannot be taken when Symantec BackUp Exec is simultaneously running on the server where the volumes are mounted. Action 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. Read-only Active Directory user causes application-managed snapshots to fail 23
Websites General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/eil Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix www.hpe.com/storage/spock Storage white papers and analyst reports www.hpe.com/storage/whitepapers For additional websites, see Support and other resources. StoreVirtual 3200 websites StoreVirtual 3200 documentation (Storage Information Library) http://www.hpe.com/info/sv3200-docs StoreVirtual 3200 documentation (HPESC) http://www.hpe.com/info/storevirtual3200manuals 24 Websites
Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: http://www.hpe.com/assistance To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: http://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: Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc Hewlett Packard Enterprise Support Center: Software downloads www.hpe.com/support/downloads Software Depot www.hpe.com/support/softwaredepot To subscribe to enewsletters and alerts: www.hpe.com/support/e-updates To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: Support and other resources 25
www.hpe.com/support/accesstosupportmaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements. 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: http://www.hpe.com/support/selfrepair Remote support Remote support is available with supported devices as part of your warranty 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. If your product includes additional remote support details, use search to locate that information. Remote support and Proactive Care information HPE Get Connected www.hpe.com/services/getconnected HPE Proactive Care services www.hpe.com/services/proactivecare HPE Proactive Care service: Supported products list www.hpe.com/services/proactivecaresupportedproducts HPE Proactive Care advanced service: Supported products list www.hpe.com/services/proactivecareadvancedsupportedproducts Proactive Care customer information Proactive Care central www.hpe.com/services/proactivecarecentral Proactive Care service activation www.hpe.com/services/proactivecarecentralgetstarted Warranty information To view the warranty for your product or to view the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products reference document, go to the Enterprise Safety and Compliance website: www.hpe.com/support/safety-compliance-enterpriseproducts 26 Customer self repair
Additional warranty information HPE ProLiant and x86 Servers and Options www.hpe.com/support/proliantservers-warranties HPE Enterprise Servers www.hpe.com/support/enterpriseservers-warranties HPE Storage Products www.hpe.com/support/storage-warranties HPE Networking Products www.hpe.com/support/networking-warranties Regulatory information To view the regulatory information for your product, view the Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center: www.hpe.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). A chemical information report for this product can be found at: www.hpe.com/info/reach For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see: www.hpe.com/info/ecodata For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see: www.hpe.com/info/environment 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. Regulatory information 27