HP 3PAR StoreServ Cluster Extension Software Administrator Guide Abstract This guide contains detailed instructions for configuring and troubleshooting HP 3PAR StoreServ Cluster Extension Software in Microsoft Windows environments. The intended audience has independent knowledge of related software and of the HP 3PAR StoreServ Storage and its software.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP 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. The information contained herein is subject to change without notice.
Contents 1 HP 3PAR StoreServ Cluster Extension features.................................................6 Integration into cluster software (Graphical user interface)..............................................................6 CLI for easy integration..............................................................................................................6 Disaster tolerance through geographical dispersion.......................................................................
Setting HP 3PAR StoreServ Cluster Extension-specific resource properties........................................29 Setting HP 3PAR StoreServ Cluster Extension resource properties using the GUI..........................30 Using Failover Cluster Management to set resource properties.............................................30 Using Failover Cluster Management to set resource properties of a CLX resource on which a CSV disk is dependant (Windows Server 2012)..................................................
Pre-execution and post-execution programs................................................................................69 Pre-execution return codes...................................................................................................70 Post-execution return codes..................................................................................................70 5 Troubleshooting........................................................................................71 Logs...................
1 HP 3PAR StoreServ Cluster Extension features HP 3PAR StoreServ Cluster Extension offers protection against application downtime due to a fault, failure, or site disaster by extending a local cluster between data centers over metropolitan distance. HP 3PAR StoreServ Cluster Extension reinstates critical applications at a remote site within minutes of an adverse event, integrating your open-system clustering software and HP 3PAR Remote Copy to automate failover and failback between sites.
Figure 1 Physical replication using HP 3PAR Remote Copy HP 3PAR Remote Copy-mirrored disks have a read/write-enabled primary (local) disk and a read-only secondary (remote) disk. Current cluster software products cannot distinguish between read-only and write-enabled disks, and cannot enable disk access if the disk is not write-enabled during the server boot process.
Fully Automatic Failover and Failback Automated failover and failback reduces the complexity involved in a disaster recovery situation. It is protection against the risk of downtime, whether planned or unplanned.
1-to-1 configuration When setting up a one-to-one configuration (see Figure 2 (page 10)), consider the following: • Cluster nodes are split between two or more geographically dispersed data center sites and use redundant, diversely routed network connections for intra-cluster communications. Those links must be as reliable as possible to prevent false failover operations or split-brain situations.
Figure 2 1-to-1 configuration N-to-1 and 1-to-N configurations NOTE: The restrictions outlined in “1-to-1 configuration” (page 9) also apply to N-to-1 configurations. When setting up an N-to-1 or 1-to-N configuration (see Figure 3 (page 11)), consider the following: 10 • HP 3PAR StoreServ Cluster Extension uses the unit of Remote Copy volume groups as the failover unit.
Figure 3 N-to-1 and 1-to-N configuration Processes and components For Windows Clustering (MSFC), HP 3PAR StoreServ Cluster Extension is shipped as a resource DLL. The installation of HP 3PAR StoreServ Cluster Extension also includes a CLI for custom HP 3PAR Remote Copy integration. Customized solutions for failover application services must implement HP 3PAR StoreServ Cluster Extension through the CLX CLI (clx3PARrun.exe) prior to the disk activation procedure on the server.
Figure 4 Relationship of primary versus secondary volume groups on primary and backup storage servers Remote Copy pairs Remote Copy configurations are based on the relationship between a storage system pair, also known as the Remote Copy pair. Within this pair, the primary storage system is the system that holds the volumes that are copied to a backup or secondary storage system, also known as a remote storage system.
Synchronous replication Using synchronous mode, all write requests from the server are first transferred to the remote storage system. After each I/O has been mirrored in the cache area of the remote storage system, it is acknowledged to the local storage system. The write request is then acknowledged to the server. User configuration file HP 3PAR StoreServ Cluster Extension provides a user configuration file to customize failover behavior.
Node Majority quorum in Windows Clustering The Node Majority resource ensures that the cluster's configuration data is stored locally on the nodes and that it is kept consistent across the different disks. This allows cluster topologies where the nodes do not need shared access to a quorum disk. (Number of nodes in the cluster/2) +1 This ensures that more than 50% of the nodes will have an up-to-date copy of the configuration information.
Cluster Shared Volume for Windows Server 2012 Cluster Shared Volume is a feature of Microsoft Failover Cluster which allows all nodes in the cluster with the ability to directly access the same volume without changing ownership of the disk resource. The result of the feature is that all nodes in a cluster can use the same volume to host actively running Virtual Machines at the same time. CSV manages storage access differently than regular clustered disks.
3PAR StoreServ Cluster Extension supports CSV disk on Windows Server 2012 in addition to non CSV disk support. Configuration of CSV disk for CLX is similar to configuration of normal disk for CLX support. Since the CSV role is hidden and not seen in Failover Cluster GUI, CLX has provided PowerShell Cmdlets to configure Cluster Extension 3PAR resource for the CSV disk. See “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 60) on how to configure CSV disk for CLX.
2 Configuring HP 3PAR StoreServ Cluster Extension After installing HP 3PAR StoreServ Cluster Extension, use the configuration tool to define the HP 3PAR StoreServ Cluster Extension setup configuration. Use Failover Cluster Management (Windows Server 2008/2008 R2/2012), or cluster commands in the CLI or Microsoft Failover Cluster PowerShell Cmdlets to add and configure resources. Integrating HP 3PAR StoreServ Cluster Extension with MSFC To integrate HP 3PAR StoreServ Cluster Extension with MSFC: 1.
IMPORTANT: User Account Control (UAC) is a feature in Windows Server 2008 onwards, that can help prevent unauthorized changes to your computer. UAC prevents unauthorized changes by requesting for permission or an administrator password before performing actions that can affect your computer's operation or that change system settings that affect other users. For more information on UAC, see http://windows.microsoft.com/en-US/windows-vista/ What-is-User-Account-Control .
Defining the HP 3PAR StoreServ configuration information using the GUI To define configuration information using the GUI: 1. Open the configuration tool. For instructions, see “Starting the HP 3PAR StoreServ Cluster Extension Configuration Tool” (page 18) 2. Click Add in the Array Configuration section to open the Add Array dialog box.
3. 4. Enter the Array Network Name. If you have a password file, click Browse to select the password file. If you don’t have a password file, select I don’t have a password file radio button and click Generate to open HP 3PAR StoreServ password file generator dialog box.
Provide the required information and click Generate to generate a new HP 3PAR StoreServ password file for the given array. 5. • User: HP 3PAR user • Password: HP 3PAR password for the given user. • Password file name: The name of the password file that will be generated on clicking Generate button. This is an optional parameter; the default value will be _.pwd. • Password file path: The windows directory where the HP 3PAR StoreServ password file needs to be created.
8. Select the servers that are possible owners of the HP 3PAR StoreServ Cluster Extension-managed disks, and click OK. NOTE: See the Microsoft Windows Clustering documentation for more information about possible owners. 9. Click OK. You will be prompted to confirm if you want to automatically copy the configuration file on all the cluster nodes used by Cluster Extension. a. 22 If you select Yes, the configuration information is automatically copied to all cluster nodes used by Cluster Extension.
NOTE: You must create or copy the array password file on all cluster nodes used by Cluster Extension. Ensure that the appropriate path is reflected in the configuration information of each node. During configuration, you will be prompted to confirm if you want to copy the configuration file on all cluster nodes. If you choose to copy the HP 3PAR StoreServ Cluster Extension configuration file automatically, the same password file location is retained on all cluster nodes.
Importing configuration settings using the GUI 1. 2. 3. 4. 5. Open the configuration tool. For instructions, see “Starting the HP 3PAR StoreServ Cluster Extension Configuration Tool” (page 18). Click Import. When prompted, choose the configuration file, and then click Open. Click OK to save and close the configuration tool. Importing configuration settings using the CLI 1. 2. Open a command window. Enter clx3PARconfig IMPORT /FILE=filepath, where filepath specifies the file location and name.
1. 2. Add a service or application in the Failover Cluster Management GUI, as described in your Microsoft documentation. Right-click the service or application and select Add a resource > More resources > Add Cluster Extension 3PAR. NOTE: This step is applicable for creating CLX resources for non CSV disks on Windows Server 2008/2008 R2/2012. Using Failover Cluster Management GUI, we cannot add CLX resource for the CSV disk.
Changing a HP 3PAR StoreServ Cluster Extension resource name This section describes how to change a HP 3PAR StoreServ Cluster Extension resource name. In this procedure, you use the Failover Cluster Management GUI to change a resource name. For Server Core or Hyper-V Server, use the MMC or Powershell Cmdlets to run the Failover Cluster Management GUI from a remote node or use cluster commands in the CLI to change the resource name.
To set Microsoft cluster-specific resource properties: • For Windows Server 2008/2008 R2/2012, use the Failover Cluster Management GUI or cluster commands in the CLI or use PowerShell Cmdlets. • For Server Core or Hyper-V Server, use cluster commands in the CLI or use PowerShell Cmdlets. TIP: You can use the GUI option for Server Core or Hyper-V Server by using the MMC to manage a cluster remotely. For more information about using the MMC, see your Microsoft documentation.
Table 1 Setting resource properties and values in the GUI (continued) Property Format Description Value properties window in Failover Cluster Management. If restart is unsuccessful, fail Integer over all resources in this service or application RestartAction (CLI) If a resource fails, attempt restart on current node – Period for restarts Integer Determines the amount of time for restart. Set this value in the Policies tab of the resource properties window in Failover Cluster Management.
Table 2 Service or application properties and values Property Format Description Value GUI: Failback (Prevent failback or Allow failback) Integer Prevents automatic failback of a service or application to its primary system. Transfer the service or application back manually after the failure has been recovered. This allows recovery of all possible failure sources and pair resynchronization (if necessary) while the application service is still running.
Setting HP 3PAR StoreServ Cluster Extension resource properties using the GUI This section describes the procedures for setting HP 3PAR StoreServ Cluster Extension resource properties with a GUI. You can perform these procedures through the resource configuration utility using the cluster software GUI Failover Cluster Management or the standalone resource configuration utility in Server Core or Hyper-V Server.
Using Failover Cluster Management to set resource properties of a CLX resource on which a CSV disk is dependant (Windows Server 2012) In case of a CSV disk, it is possible to create a CLX resource in the CSV group and make CSV disk dependent on the CLX resource. After creating the CLX resource in the CSV group, the CLX resource does not appear in the Windows Server 2012 Failover Cluster Manager GUI. In the Failover Cluster Manager GUI, only CSV disk is visible, but not the role in which CSV disk exists.
Alternatively, you can also use HP 3PAR StoreServ Resource Configuration Tool (Clx3PARResConfig.exe) to configure the CLX resource on which the CSV is dependent. Using the resource configuration tool to set resource properties To set CLX resource properties, you can also use the HP 3PAR StoreServ Cluster Extension resource configuration tool. When using the resource configuration tool: • You must run the tool on a Server Core or Hyper-V cluster node. You cannot run the tool on a remote management station.
Configuring cluster node data center assignments To configure cluster node data center assignments from the cluster software Parameters tab or the resource configuration tool: 1. To add a cluster node: a. Click Add to open the Add Server Data center Assignment window. b. c. d. 2. 3. 4. Select a cluster node from the Pre-Configured host list. Assign the cluster node to a data center selected from the Data center list. Click OK to save and close the window.
3. 4. To modify a storage system, select the storage system, and then click Modify. Click Apply to finish your modifications and keep the window open, or click OK to save your changes and then close the Properties window. Selecting a volume group Use the cluster software Parameters tab or the resource configuration tool to select the Remote Copy volume group containing the disk that will be managed by the HP 3PAR StoreServ Cluster Extension resource. 1. Click Browse. 2. 3.
Use this dialog box to configure the Remote Copy volume group behavior. 2. 3. • The settings in the Replication link up scenario section affect the failover behavior when the HP 3PAR Remote Copy link is up. • The settings in the Replication link down scenario section affect the failover behavior when the HP 3PAR Remote Copy link is down. Select RESYNCWAIT or FASTFAILBACK for the ApplicationStartup behavior. If you selected RESYNCWAIT in Step 2, set the RESYNCWAIT timeout value. • 4. 5. 6. 7.
2. 3. Update the PreExecScript, PostExecScript, and PostExecCheck values as needed, and then click OK. Click Apply to finish your modifications and leave the Properties window open, or click OK to save your changes and close the window. Setting HP 3PAR StoreServ Cluster Extension resource properties using the MMC If you are using Server Core or Hyper-V Server, you can manage a cluster remotely by using the MMC to run Failover Cluster Management.
cluster resource "3PAR Cluster Extension resource1" /ren:"3PAR Cluster Extension resource2" Setting HP 3PAR StoreServ Cluster Extension resource properties using the Microsoft Failover PowerShell Cmdlets The cluster commands in this section can be used with Windows Server 2008/2008 R2/2012, Server Core, or Hyper-V Server.
To add dependencies: • Use the Failover Cluster Management GUI, cluster commands in the CLI, or the MMC for remote management. • For Server Core or Hyper-V Server, use cluster commands in the CLI or the MMC. Adding dependencies using Failover Cluster Management You can add dependencies with the GUI on a local node or by using the MMC to run the Failover Cluster Management application. 1. Open Failover Cluster Management. 2.
The following command adds a dependency on the HP 3PAR StoreServ Cluster Extension clx_fileshare resource to the physical disk resource Disk_32b_00b: cluster resource Disk_32b_00b /adddependency:clx_fileshare Adding dependencies using the PowerShell 1. To add dependency on a HP 3PAR StoreServ Cluster Extension resource using the PowerShell, use the following command: Add-ClusterResourceDependency -Resource – Provider 2.
Figure 5 Service or application example Figure 6 Resource tree for service or application CLX_SHARE HP 3PAR StoreServ Cluster Extension is configured as a single resource to enable read/write access to the physical disk resource used for the CLX_SHARE cluster group. The physical disk resource depends on the HP 3PAR StoreServ Cluster Extension resource and can be brought online only when the HP 3PAR StoreServ Cluster Extension resource is already online.
1. 2. 3. 4. 5. 6. 7. 8. Log in to the host3_DCB system with the Administrator account. Create the file share service or application with all previously mentioned resources and its dependencies, except the HP 3PAR StoreServ Cluster Extension resource on host3_DCB. Create a new resource of type HP 3PAR StoreServ Cluster Extension and add systems host2_DCA, host3_DCB and host4_DCB to its possible owners.
To bring resources online: • Use Failover Cluster GUI or Cluster CLI or Microsoft PowerShell Cmdlets. • For Server Core or Hyper-V Server, use the CLI or the MMC or Microsoft PowerShell Cmdlets. For more information on using this command, see your Microsoft documentation. Taking a resource offline Resources are usually taken offline automatically when the service or application is taken offline. Taking a resource offline causes resources that depend on that resource to go offline.
Using Hyper-V Live Migration with HP 3PAR StoreServ Cluster Extension Live migration is a managed failover of VM resources. Live migration should be performed when all of the solution constituents are in a healthy state, all the servers and systems are running, and all the links are up. Ensure that the underlying infrastructure is in a healthy state before performing live migration.
PendingTimeout value. Microsoft Cluster provides two properties to adjust state change recognition or resolution: • IsAlive • LookAlive NOTE: For Windows Server 2008/2008 R2/2012, the IsAlive and LookAlive properties are replaced by the Thorough Resource Health Check Interval and Basic Resource Health Check Interval properties.
about the Parameters tab, see “Setting HP 3PAR StoreServ Cluster Extension resource properties using the MMC ” (page 36). • When you install HP 3PAR StoreServ Cluster Extension into a Windows Server 2008/2008 R2/2012 environment, the resource extension DLL is registered by default, which prevents you from configuring a HP 3PAR StoreServ Cluster Extension resource from a remote management station.
TIP: Archive the log files before deleting them. Hyper-V Live Migration log entries In the HP 3PAR StoreServ Cluster Extension log file (clxmscs.log), live migration messages include the prefix CLX_LM to help you differentiate live migration issues from HP 3PAR StoreServ Cluster Extension log messages. For example: [10/12/09 20:13:02][2136][CLX_LM: CLXVMDISK04-App01][INFO] CLX detected that Live Migration for VM "Virtual Machine VM04" has begun.
2. 3. 4. 5. To create a Cluster Extension 3PAR cluster resource in the hidden CSV role, CLX has provided PowerShell Cmdlet to perform the required operation. For more information, see “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 60) Once the Cluster Extension 3PAR resource is created in the CSV role, configure the CLX Resource private properties.
3. The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves to a node in the same datacenter or CSV disk is moved manually to a node in the same datacenter: In this scenario, since the CSV disk is moved to a node in the same datacenter, all the VMs continue to run on their respective cluster nodes. There will not be any change in the ownership for the VMs. 4.
3 User configuration file and HP 3PAR StoreServ Cluster Extension objects Objects (also called properties in this document) define the HP 3PAR StoreServ Storage environment and failover/failback behavior. You can customize HP 3PAR StoreServ Cluster Extension objects in the user configuration file or in the cluster software. User configuration file For the CLI implementation of HP 3PAR StoreServ Cluster Extension, the user configuration file UCF.
Specifying object values You do not need to change the default settings unless you want to change the degree of protection for your Remote Copy volume group members. If you change an object, you may need to change additional objects as well. For example, if RESYNCWAIT has been specified for the ApplicationStartup object, the ResyncWaitTimeout object must be specified. Objects are supported according to the requirements or capabilities of the cluster software, as indicated in Table 3 (page 50).
If the default values fit your environment, there is no need to specify them in the file. COMMON Format Tag Description Distinguishes between general (common) and application-specific objects. LogDir Format String Description (Optional) Defines the path to the HP 3PAR StoreServ Cluster Extension log file. Default value %ProgramFiles%\Hewlett-Packard\Cluster Extension 3PAR\log LogLevel Format String Description (Optional) Defines the logging level used by HP 3PAR StoreServ Cluster Extension.
The APPLICATION object requires the name of the application service as its value. The objects specified after an APPLICATION tag must appear only once per application. As with COMMON objects, APPLICATION objects have predefined default values. HP 3PAR StoreServ Cluster Extension uses the following rules to define objects: • If you use the default value, you do not need to specify the object.
If a resynchronization is ordered, HP 3PAR StoreServ Cluster Extension monitors the progress of the copy process. If the application service was running on a secondary HP 3PAR StoreServ Storage without a replication link, a large number of records may need to be copied. If the copy process takes longer than the configured application startup timeout value, the application startup will fail.
Description Specifies how often HP 3PAR StoreServ Cluster Extension will check for VM live migration state changes. Default value 10 seconds ClusterNotifyWaitTime Format Integer Description Specifies the amount of time that HP 3PAR StoreServ Cluster Extension will monitor for VM live migration state changes. Default value 5 seconds DC_A_Hosts (Required) Format List Description This space-separated list defines the cluster nodes in data center A.
procedure. That information will be passed to the post-executable. In case of a remote data center failure, it could be time consuming to gather that information, especially if your post-executable does not need any Remote Copy volume group status information. The arguments passed to the post-executable will include only the local disk status if the PostExecCheck object is set to NO.
If a HP 3PAR Remote Copy link goes down, and the resource is moved to the remote data center: Valid values • Setting this value to YES means that, regardless of whether or not the data is current in the remote data center, the resource will come online. • Setting this value to NO means that the resource will not come online on the remote data center since data might not be current.
4 CLI commands and utilities Using its CLI and command-line utilities, HP 3PAR StoreServ Cluster Extension can be integrated with almost any cluster software.
# clx3PARrun -forceflag my-exchange Related information • clx3PARrun expects only the app_name parameter, which uniquely identifies an application service in the APPLICATION section of the user configuration file. • To force a Remote Copy volume group failover, use the –forceflag option. CAUTION: The forceflag option is an emergency switch used to manually activate your virtual volume.
For detailed procedures, see the HP 3PAR InForm Management Console User Guide or the HP 3PAR InForm CLI Administrator’s Manual. Installing HP 3PAR Command Line Interface (CLI) HP 3PAR StoreServ Cluster Extension communicates with the HP 3PAR StoreServ Storage using the HP 3PAR Command Line Interface (CLI). Ensure that you install the supported version of HP 3PAR Command Line Interface (CLI) on a host where clx3PARrun can be used.
HP 3PAR StoreServ Storage and the settings in the UCF.cfg file, you must evaluate the following considerations: • HP 3PAR StoreServ Cluster Extension uses HP 3PAR Command Line Interface (CLI) to communicate with the HP 3PAR StoreServ Storage, depending on the settings of HP 3PAR command timeout property, and the number of Remote Copy volume groups managed by HP 3PAR StoreServ Storage, the online operation could time out.
Another way to unload the CLX PowerShell Snap-In is to run the PowerShell script RemoveClx3PARCmdletsSnapIn.ps1 located at \bin directory. NAME: Add-CSVDependencyOnCLX3PAR SYNOPSIS: Adds a cluster resource of type "Cluster Extension 3PAR" to the list of resources and makes the given cluster shared volume dependent on this cluster resource (CLX resource), using AND as the connector, within a Failover Cluster. Existing dependencies will remain in the list.
Does not accept input objects. OUTPUTS: Does not return object. NOTES: CSV resource has to be offline while trying to add the dependency. The Confirm parameter and the Force switch parameter are provided. The cmdlet performs the operations irrespective of the storage array type of CSV. Online help for the cmdlet is not supported. Example 1 C:\PS>Add-CSVDependencyOnCLX3PAR This command first finds out all the cluster shared volumes in the cluster.
Created the resource "CLX_3PAR_Cluster Disk 2" in CSV Owner Group: "0f145465-1186-4bbb-b9e2-2fde4cb1127d" Added the dependency of CSV: "Cluster Disk 2" on "Cluster Extension 3PAR" type resource: "CLX_3PAR_Cluster Disk 2" Resource of type "Cluster Extension 3PAR" to be created with Name: "CLX_3PAR_Cluster Disk 3" in CSV Owner Group: "a71654bf-6c77-42c1-95dd-025ea8c4f225" Created the resource "CLX_3PAR_Cluster Disk 3" in CSV Owner Group: "a71654bf-6c77-42c1-95dd-025ea8c4f225" Added the dependency of CSV: "Clu
"Cluster Extension 3PAR" type resource. If it is not present, a new resource of type "Cluster Extension 3PAR" is created and CSV resource is made dependent on it. While creating the dependency, CSV resource should be offline, else dependency is not created. PS C:> Add-CSVDependencyOnCLX3PAR -CSVDiskName "Cluster Disk 1" Logs will be generated with default "info" log level. For changing the logging level, configure LogLevel parameter in UCF.
"Virtual Machine Configuration" resource is already dependent on the CLX resource, the cmdlet moves to the next VM configuration on a CSV. In the absence of dependency on the existing CLX resource the cmdlet creates a dependency of "Virtual Machine Configuration" resource in the VM role on resource of type "Cluster Extension 3PAR for VM Management".
If virtual machine configuration is already dependent on "Cluster Extension 3PAR for VM Management", then the cmdlet moves to the next virtual machine configuration on a CSV. However if there is no existing dependency on "Cluster Extension 3PAR for VM Management" but resource of this type is already existing in the VM role, virtual machine configuration resource is made dependent on the existing "Cluster Extension 3PAR for VM Management" type resource.
cluster shared volume, it tries to make each virtual machine configuration resource dependent on resource of type "Cluster Extension 3PAR for VM Management". If virtual machine configuration is already dependent on "Cluster Extension 3PAR for VM Management", then the cmdlet moves to the next virtual machine configuration on the provided CSV.
SYNOPSIS: Gets the list of virtual machines which reside on a cluster shared volume. SYNTAX: Get-VMOnClusterSharedVolumeListForCLX3PAR [-CSVDiskName [] DESCRIPTION: This cmdlet tries to get the list of all virtual machines which reside on a CSV. If the CSV name is specified, then the virtual machines which reside on that particular CSV are only listed.
Total virtual machines in the cluster on cluster shared volumes: 1 Total virtual machines in the cluster: 1 Example 2 C:\PS>Get-VMOnClusterSharedVolumeListForCLX3PAR -CSVDiskName "Cluster Disk 1" In this example, the cmdlet lists all the virtual machines which reside on CSV "Cluster Disk 1" PS C:\> Get-VMOnClusterSharedVolumeListForCLX3PAR -CSVDiskName "Cluster Disk 1" Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension 3PAR\log\CLXCmdlet.
14. 15. 16. 17. Remote Copy volume group virtual volume status AutoRecover Application directory path (ApplicationDir object) Log file location (LogDir object) Pre-executables and post-executables must supply a return code. The return code is used to determine whether a failover function is called. Pre-execution return codes Pre-execution return code Text Description 0 PRE_OK_TAKEOVER Pre-executable OK and failover action allowed.
5 Troubleshooting To troubleshoot problems with HP 3PAR StoreServ Cluster Extension, one must understand HP 3PAR Remote Copy environments. See the Remote Copy User's Guide for more information on Remote Copy configuration and volume group states. See the HP 3PAR StoreServ Cluster Extension log for any cluster specific information. However, it always keeps its own log files in its default log location.
HP 3PAR StoreServ Cluster Extension logs The logging module of HP 3PAR StoreServ Cluster Extension provides log messages to the cluster software and to the HP 3PAR StoreServ Cluster Extension log file. The HP 3PAR StoreServ Cluster Extension log file includes Remote copy volume group status information. By default, the HP 3PAR StoreServ Cluster Extension log file is located in the %ProgramFiles%\ Hewlett-Packard\Cluster Extension 3PAR\log\ directory.
In the current example, the state of the local Remote Copy (RC) group is “primary” (virtual volumes having read/write access) and the state of the remote RC group is “secondary” (virtual volumes having read-only access). The RC link status is UP and the replication status is started. Line 30: The status of the Cluster Extension takeover action. Line 31: The encoded Cluster Extension execution path. Line 32: Online status of Cluster Extension resources. Line 33: Creating .
Error return codes Description start the Remote Copy replication using HP 3PAR StoreServ Management GUI or CLI when required. Replication I/O starting error Replication I/O between the primary and secondary Remote Copy volume group is started. Use HP 3PAR StoreServ Management GUI or CLI to check if the replication status is started or not. You can manually start the Remote Copy replication using HP 3PAR StoreServ Management GUI or CLI when required.
Failover error handling Windows Cluster automatically fails over resource groups if the system where resource group is running on becomes unavailable. This is part of the cluster functionality. Also, this means that if a problem occurs with the HP 3PAR StoreServ Storage, a resource group online process will be stopped. The behavior of HP 3PAR StoreServ Cluster Extension is highly configurable.
Later, when the power outage in the primary datacenter is corrected and the storage array is brought back online, the status of the remote copy volume group goes to the failsafe status. At this time, if we failback the corresponding cluster application role from the secondary datacenter to one of the hosts in the primary datacenter, then the physical disk resources may fail to come online even though CLX resource has come online successfully.
Resource disk failure when HP 3PAR StoreServ Cluster Extension is online In a cluster resource group, if the Cluster Extension resource is online but dependent disk resource is failing: • Ensure that the fibre channel connectivity between the servers and the storage systems is up and running. • Verify that the disk resource is dependent to the Cluster Extension resource.
Continuing to write changes despite a broken link leads to a loss of synchronization between primary and secondary Remote Copy volume groups. The no_fail_wrt_on_err policy is used when you would rather keep the applications that are writing the data running, even when the Remote Copy has failed and become out of sync. After the error that caused the broken link is resolved, you must manually restart the Remote Copy operation between the members of the Remote Copy pair to bring the Remote Copy in sync again.
StoreServ CLX Setting tab will not be visible, if the CSV disk dependency on the CLX resource is not set. HP 3PAR StoreServ Storage DNS resolution If the HP 3PAR CLI command takes more than 4 seconds to respond, check if the DNS look up is fast. If the DNS look up is slow, contact the system administrator to change the DNS settings. You can also speed up the DNS look up by adding the HP 3PAR StoreServ Storage to the local failover cluster node DNS mapping file.
6 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Typographic conventions Table 4 Document conventions Convention Element Blue text: Table 4 (page 81) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
Glossary 3PAR Remote Copy A product that allows you to copy virtual volumes from one HP 3PAR StoreServ Storage to another. CLI Command-line interface. An interface comprised of various commands which are used to control operating system responses. cluster A group of controller nodes connected via the same storage server backplane. The nodes in a cluster operate as a unified system, separate from any other clusters that may share the same service processor. CLX Cluster Extension.
Index Symbols 3PAR Cluster Extension Integration, 6 Processes and components, 11 3PAR Remote Copy, 11 Volume groups, 12 3PAR StoreServ Cluster Extension Features, 6 A Adding HP 3PAR StoreServ Cluster Extension resource, 24 Adding dependencies using CLI, 38 using Failover Cluster Management, 38 using PowerShell, 39 Administration, 44 APPLICATION objects, 51 ApplicationDir description, 52 ApplicationStartup description, 52 AutoFailbackType Description, 29 B Basic Resource Health Check Interval Description,
description, 51 Hyper-V Live Migration, 43 Hyper-V Live Migration log enteries, 46 I Importing Configuration information, 23 Integration CLI, 6 with cluster software, 6 IsAlivePollInterval Description, 27 L Live migration, 43, 46 LogDir description, 51 LogLevel description, 51 UCF requirement, 37 LooksAlivePollInterval Description, 27 M Microsoft Management Console, 27 Mirrored disks Automated redirection, 7 P PendingTimeout Description, 28 Post-execution programs, 69 Return codes, 70 PostExecCheck desc
W Websites HP , 80 Product manuals, 80 85
