HP XP Cluster Extension Software Administrator Guide

HP XP Cluster Extension Software Administrator Guide
HP XP Cluster Extension Software
Administrator Guide
Abstract
This guide contains instructions for configuring and troubleshooting HP XP Cluster Extension Software in Windows environment
with HP XP disk arrays. The intended audience has independent knowledge of XP disk arrays and related array software.
Previous versions of this product were called HP StorageWorks XP Cluster Extension.
HP Part Number: 5697-3251
Published: June 2014
Edition: Sixth
© Copyright 2014 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. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Contents
1 HP XP Cluster Extension features...................................................................6
Integration into cluster software...................................................................................................6
Enhanced disaster tolerance......................................................................................................6
Automated monitoring and redirecting of Continuous Access pairs..................................................6
Rolling disaster protection..........................................................................................................6
Command-line interface (CLI).....................................................................................................6
Fast Failback using Continuous Access........................................................................................7
HP XP Cluster Extension configurations........................................................................................7
One-to-one configurations.....................................................................................................7
Consolidated-site configuration..............................................................................................8
Supported Continuous Access configurations and fence levels....................................................8
HP XP Cluster Extension server configurations..........................................................................9
Planning for HP XP Cluster Extension...........................................................................................9
Before configuring HP XP Cluster Extension resources................................................................9
Cluster setup considerations..................................................................................................9
Node Majority quorum clusters (MSFC)..............................................................................9
Cluster Shared Volume for Windows Server 2012/2012 R2..................................................9
Setting up RAID Manager...................................................................................................11
Creating RAID Manager command devices......................................................................11
Configuring RAID Manager command devices..................................................................11
In-band and out-of-band communication......................................................................11
Command device authentication.................................................................................11
Creating RAID Manager instances..................................................................................11
Creating RAID Manager device/copy groups...................................................................12
Network considerations.................................................................................................12
Starting and stopping the RAID Manager instances...........................................................12
Test takeover function.....................................................................................................12
2 Configuring HP XP Cluster Extension...........................................................14
Integrating HP XP Cluster Extension with MSFC...........................................................................14
Configuring HP XP Cluster Extension.........................................................................................14
Starting the HP XP Cluster Extension configuration tool............................................................14
Defining HP XP Cluster Extension configuration information using the GUI.................................15
Defining HP XP Cluster Extension configuration information using the CLI...................................17
Importing and exporting configuration information.................................................................19
Exporting configuration settings using the GUI..................................................................19
Exporting configuration settings using the CLI....................................................................19
Importing configuration settings using the GUI..................................................................19
Importing configuration settings using the CLI....................................................................19
Adding an HP XP Cluster Extension resource..............................................................................19
Adding an HP XP Cluster Extension resource using the Failover Cluster Management GUI (Windows
Server 2008/2008 R2/2012/2012 R2)...............................................................................20
Adding an HP XP Cluster Extension resource using the Microsoft CLI cluster commands...............20
Adding an HP XP Cluster Extension resource using the Microsoft Failover Cluster PowerShell
Cmdlets............................................................................................................................20
Changing an HP XP Cluster Extension resource name..................................................................21
Changing an HP XP Cluster Extension resource name (Windows Server 2008/2008
R2/2012/2012 R2)............................................................................................................21
Configuring HP XP Cluster Extension resources............................................................................21
Setting Microsoft cluster-specific resource and service or application properties..........................22
Setting HP XP Cluster Extension-specific resource properties.....................................................25
Contents
3
Setting HP XP Cluster Extension resource properties using the GUI (Windows Server 2008/2008
R2/2012/2012 R2, Server Core, and Hyper-V Server)........................................................25
Using Failover Cluster Management to set resource properties (Windows Server 2008/2008
R2/2012/2012 R2)..................................................................................................25
Using Failover Cluster Management to set resource properties of a CLX resource on which
a CSV disk is dependant (Windows Server 2012/2012 R2)...........................................26
Using the resource configuration tool to set resource properties (Server Core and Hyper-V
Server)....................................................................................................................27
Configuring RAID Manager instance numbers for RAID Manager service.........................28
Configuring the RAID Manager device/copy group details............................................28
Configuring RAID Manager device/copy group advanced properties..............................28
Configuring server data center assignments.................................................................30
Changing failover and failback behavior.....................................................................30
Activating the pair/resync monitor..............................................................................30
Configuring takeover actions......................................................................................31
Configuring Rolling Disaster Protection .......................................................................32
Setting HP XP Cluster Extension resource properties using the MMC.....................................32
Setting HP XP Cluster Extension—specific resource properties using the CLI...........................33
Setting HP XP Cluster Extension resource properties using the Microsoft Failover PowerShell
Cmdlets.......................................................................................................................34
Setting HP XP Cluster Extension properties using a UCF......................................................34
Adding dependencies on HP XP Cluster Extension resource..........................................................34
Adding dependencies using Failover Cluster Management (Windows Server 2008/2008
R2/2012/2012 R2)............................................................................................................35
Adding dependencies using the CLI.....................................................................................35
Adding dependencies using the PowerShell...........................................................................36
Configuration of XP CLX for CSV disk on Windows Server 2012/2012 R2......................................36
Disaster-tolerant configuration example using a file share.............................................................36
Managing HP XP Cluster Extension resources.............................................................................39
Bringing a resource online..................................................................................................39
Taking a resource offline.....................................................................................................40
Deleting a resource............................................................................................................40
Using Hyper-V Live Migration with HP XP Cluster Extension...........................................................41
Timing considerations for MSFC...............................................................................................41
Bouncing service or application................................................................................................42
Administration........................................................................................................................42
Remote management of HP XP Cluster Extension resources in a cluster (Windows Server
2008/2008 R2/2012/2012 R2).........................................................................................43
System resources................................................................................................................43
Logs.................................................................................................................................44
Hyper-V Live Migration log entries........................................................................................44
Virtual Machine Management hosted on a Cluster Shared Volume on Windows Server 2012/2012
R2...................................................................................................................................44
3 HP XP Cluster Extension and CLI.................................................................47
Configuring the CLI.................................................................................................................47
Creating the Continuous Access environment and configuring RAID Manager............................47
Timing considerations.........................................................................................................47
Restrictions for customized HP XP Cluster Extension implementations..........................................48
Creating and configuring the user configuration file................................................................48
CLI commands.......................................................................................................................49
clxrun...............................................................................................................................49
clxchkmon.........................................................................................................................50
Displaying resources......................................................................................................50
Removing resources.......................................................................................................50
4
Contents
Stopping the pair/resync monitor....................................................................................50
Cluster Extension Cmdlets for CSV and Virtual Machine Management...........................................52
4 HP XP Cluster Extension recovery procedures...............................................62
XP disk pair states..................................................................................................................62
Recovery sequence.................................................................................................................63
5 User configuration file and HP XP Cluster Extension objects............................64
User configuration file location.................................................................................................64
File structure......................................................................................................................64
Specifying object values.....................................................................................................65
COMMON objects.................................................................................................................66
APPLICATION objects .............................................................................................................67
APPLICATION objects.........................................................................................................67
Basic configuration example....................................................................................................75
6 Advanced HP XP Cluster Extension configuration..........................................77
Configuring the HP XP Cluster Extension for HP XP Continuous Access 3DC environment..................77
Implementing rolling disaster protection.....................................................................................79
Using RAID Manager with rolling disaster protection..............................................................79
Setting HP XP Cluster Extension objects to enable rolling disaster protection...............................80
Setting automatic recovery for rolling disaster protection.........................................................80
Using the pair/resync monitor with rolling disaster protection..................................................80
Restoring server operation for rolling disaster protection..........................................................80
Monitoring and resynchronizing device/copy groups..................................................................81
Enabling write access regardless of disk pair state......................................................................82
Executing programs before and after an HP XP Cluster Extension takeover.....................................82
Arguments........................................................................................................................83
Pre-executable return codes.................................................................................................83
Post-executable return codes................................................................................................84
7 Troubleshooting........................................................................................85
HP XP Cluster Extension log files...............................................................................................85
Start errors.............................................................................................................................85
Failover error handling............................................................................................................85
MSFC-specific error handling...................................................................................................86
Resource start errors...........................................................................................................86
Failover errors...................................................................................................................86
Using the Domain user account (Windows Server 2008/2008 R2/2012/2012 R2 only)............87
Pair/resync monitor messages in event log.................................................................................88
8 Support and other resources......................................................................89
Contacting HP........................................................................................................................89
Subscription service............................................................................................................89
Related information.................................................................................................................89
White papers....................................................................................................................90
HP websites......................................................................................................................90
Typographic conventions.........................................................................................................90
Documentation feedback.........................................................................................................91
Glossary....................................................................................................92
Index.........................................................................................................94
Contents
5
1 HP XP Cluster Extension features
HP XP Cluster Extension Software monitors XP Continuous Access disk pairs and enables automatic
access to remote data copies when clustered applications become unavailable locally. HP XP
Cluster Extension integrates with popular cluster software to ensure that consistent and concurrent
data copies on HP disk arrays can be accessed when needed.
Integration into cluster software
HP XP Cluster Extension integrates with Microsoft Failover Cluster (MSFC).
Integrating HP XP Cluster Extension with cluster software allows you to manage a disk array as if
it were a disk or volume group of the clustered application.
For supported cluster software versions, see the HP SPOCK website: http://www.hp.com/storage/
spock.
Enhanced disaster tolerance
The Continuous Access software copies valuable data to a remote data center so that you can
restore application service after a local server, storage, or data center failure. Disk arrays with
Continuous Access can change mirroring direction, swapping the primary/secondary relationship
of disk pairs almost instantaneously if the application must access the secondary disk. This feature
ensures that the failback process is as fast as the failover process. If the links between your primary
and secondary disk arrays are broken, each array maintains a bitmap table to synchronize the
changes when the links become available again.
Because cluster software requires the application service to have read/write access to data disks
and because the secondary volume of a Continuous Access disk pair is normally read-only, the
failover process using cluster software alone typically involves manual intervention. With HP XP
Cluster Extension Software, manual intervention is required only if the current disk array states and
user settings conflict with the rules stored in the HP XP Cluster Extension database.
Automated monitoring and redirecting of Continuous Access pairs
HP XP Cluster Extension monitors the health of the Continuous Access links between your arrays.
When it detects a lost and later re-established link, it automatically resynchronizes the suspended
disk pairs, ensuring that the most current data is available on either site. For information on
configuring resynchronization parameters, see “Monitoring and resynchronizing device/copy
groups” (page 81).
Rolling disaster protection
A rolling disaster is a catastrophic event that affects the remote site after an outage at the local
site. In a rolling disaster, data stored on remote disks can be entirely lost during a recovery attempt.
To ensure the survival of critical data during a resynchronization/restore operation, XP Business
Copy pairs can be associated with the local data disks. HP XP Cluster Extension recovers
automatically, provided that a local Business Copy mirror can be suspended.
Although the local copy can be out of date, it represents the best starting point for the recovery.
HP XP Cluster Extension also resumes local Business Copy mirrors automatically, if specified, to
allow the local site to keep an up-to-date image of the primary data. To implement rolling disaster
protection, see “Implementing rolling disaster protection” (page 79).
Command-line interface (CLI)
HP XP Cluster Extension Software provides a CLI to enable disaster tolerance without cluster software.
The CLI is convenient if you use in-house software to migrate application services from one system
6
HP XP Cluster Extension features
to another or if you want HP XP Cluster Extension to check disk states to make sure you can
automatically start an application service on the local disk array.
Fast Failback using Continuous Access
HP XP Cluster Extension supports the RAID Manager Fast Failback feature. This feature allows the
Continuous Access software to automatically redirect the mirroring direction of a disk pair even if
the remote RAID Manager instance is not available. This ensures the fastest possible recovery to
the original site in case of an application service failover at the alternate site.
HP XP Cluster Extension configurations
HP XP Cluster Extension is an array-based solution. It requires at least two XP disk arrays with the
Continuous Access software providing remote mirroring. HP XP Cluster Extension connects the disk
array software with the cluster software, and uses the cluster software to react to system hardware
and application failures.
Servers are members of the same cluster dispersed over two or more sites.
HP XP Cluster Extension supports one-to-one and consolidated-site configurations.
One-to-one configurations
In one-to-one (1:1) configurations, cluster host nodes are split between two geographically separate
data centers and use redundant, diversely routed network connections for intra-cluster
communications. For an example of a one-to-one configuration, see “One-to-one (1:1) configuration”
(page 7). These links must be as reliable as possible to prevent false failover operations or
split-brain situations.
Figure 1 One-to-one (1:1) configuration
Each cluster host node needs redundant FC or SCSI I/O paths to the disk array. Individual hosts
cannot be connected to both the primary (P-VOL) and the secondary (S-VOL) copy of the application
disk set.
Fast Failback using Continuous Access
7
HP recommends a minimum of two cluster host nodes per site. This allows for a preferred local
failover in case of a system failure. Local failover operations are faster than a remote failover
between disk arrays because the mirroring direction of the disks does not need to be changed.
HP XP Cluster Extension can be deployed in environments where several clusters use the same pair
of disk arrays. Although XP disk arrays can be mirrored in various configurations, HP XP Cluster
Extension does not support multiple disk arrays as both primary and secondary disk arrays. HP
XP Cluster Extension supports configurations where two or more disk arrays use one remote disk
array in a logical one-to-one configuration.
CAUTION: HP XP Cluster Extension can operate with only one system at each site, with a single
I/O path between the server system and the disk array and a single link in each direction between
disk arrays.
However, those configurations are not considered highly available, nor are they disaster tolerant.
HP XP Cluster Extension configurations with single points of failure are not supported by HP.
Consolidated-site configuration
In consolidated-site configurations, a single disk array in the secondary (remote) data center is
connected to up to four other primary disk arrays. For an example of a consolidated-site
configuration, see “Consolidated-site configuration” (page 8). The restrictions outlined in
“One-to-one configurations” (page 7) also apply to consolidated configurations. HP XP Cluster
Extension does not support configurations in which the application service's data disk set is spread
over two or more disk arrays.
Figure 2 Consolidated-site configuration
Supported Continuous Access configurations and fence levels
The Continuous Access software offers three modes of replication:
•
Synchronous replication
•
Asynchronous replication
•
Journal replication
For the replication modes supported by specific versions of HP XP Cluster Extension, see the HP
SPOCK website: http://www.hp.com/storage/spock. For information about synchronous and
asynchronous replication modes, see the Continuous Access documentation. For information about
journal replication, see the Continuous Access Journal documentation.
The Continuous Access fence level is used to configure the remote replication feature of an XP disk
array based on your requirements for application service availability, data concurrency, and
8
HP XP Cluster Extension features
replication performance. HP XP Cluster Extension supports all Continuous Access fence levels:
NEVER, DATA, and JOURNAL.
HP XP Cluster Extension is supported with the Continuous Access Software in the configurations
described in the HP SAN Design Reference Guide Volume 1 to 5, available at http://www.hp.com/
go/sdgmanuals.
HP XP Cluster Extension server configurations
The ideal cluster configuration for HP XP Cluster Extension consists of at least four servers (two at
each site) and separate redundant communications links for cluster heartbeats, client access, and
the Continuous Access Software. Installing communications interfaces in pairs allows failover and
prevents single points of failure (SPOFs). Using four servers provides faster recovery from a system
failure by allowing local application services to fail over to a local cluster system instead of the
remote system. On the remote site, HP recommends that two systems be available in case one
system experiences a hardware or power failure. In addition to at least four servers, the Node
Majority quorum configuration requires an additional node per cluster, located at a third site so
that whenever a disaster affects either the local or remote site, the other site together with the added
node would have a majority. In a Node Majority quorum with File Share Witness configuration,
the, file share should be located at the third site.
HP XP Cluster Extension allows you to configure the failover behavior so that the application service
startup is stopped if no remote cluster members can be reached. The default configuration of HP
XP Cluster Extension expects the cluster software to deal with the split-brain syndrome.
Planning for HP XP Cluster Extension
Before configuring HP XP Cluster Extension resources
Before configuring HP XP Cluster Extension resources for the CLI implementation , review the HP
XP Cluster Extension objects in the UCF.cfg file. For more information about HP XP Cluster Extension
objects, see “User configuration file and HP XP Cluster Extension objects” (page 64).
Cluster setup considerations
For cluster setup considerations, see the following sections:
Node Majority quorum clusters (MSFC)
In an Node Majority quorum cluster, the cluster service is allowed to start or run only if it has access
to the majority of the configured nodes.
This means that losing half the nodes in a 2-, 4-, 6-, or 8-node cluster or losing the communication
links with 50% of the nodes on each site forces every node to terminate the cluster services because
none of them have access to a majority of the configured nodes.
Therefore, a geographically dispersed Node Majority quorum-based cluster requires an additional
node per cluster located at a third site so that whenever a disaster affects either the local or remote
site, the other site together with the added node has a majority.
NOTE: HP XP Cluster Extension does not support quorum configuration which includes disk
witness. Please see Microsoft documentation for more details on quorum configuration.
Cluster Shared Volume for Windows Server 2012/2012 R2
The Cluster Shared Volume feature of Microsoft Failover Cluster allows all the nodes in a cluster
to directly access the same volume, without changing ownership of the disk resource. Because of
this feature, all the nodes in a cluster can use the same volume to simultaneously host active virtual
machines. CSV manages storage access differently compared to regular clustered disks. A CSV
volume is a shared disk containing NTFS partitions. CSV allows you to store multiple VHDs on a
single LUN and run the associated VMs on any cluster node in read-write mode. This makes the
Planning for HP XP Cluster Extension
9
failover operation quicker. CSV also enables quicker live migration that allows you to move a
running VM from one node to another node with zero downtime.
As disk ownership does not change when a VM moves from one to another node, the process
becomes quicker and safer. This allows the client nodes to stay connected while the VM is moved
to another node in the cluster. The CSV disk resource that is owned by a cluster node is known as
a coordinator node. The VMs hosted on the CSV disk can be owned by either the coordinator
node or any other node in the cluster. When a disk is in the available storage group, it can be
converted to a CSV. When a CSV disk is created in the Failover Cluster, a role is internally created
by the failover cluster which is hidden, and is visible through the cluster.exe command output
or through the PowerShell Cmdlet output, and not in the Failover Cluster GUI. Only CSV disk is
shown on the Failover Cluster GUI. The name of the CSV role is in the form of a GUID. For every
highly available VM that is created on the CSV, a VM role is created in the Failover Cluster that
is independent of the CSV role. Figure 3 (page 10) shows two virtual machines created on a single
CSV Disk. For each virtual machine, a role is created.
In a multi-site storage array replicated environment, CSV disks are replicated to the remote
datacenter using the array based remote replication feature. VMs residing in the CSV disk can run
on any cluster nodes (physical servers). In case of a disaster in the primary datacenter, CSV disks
must be brought online in the secondary datacenter. Ensure that you check the CLX disaster recovery
rules, and then carry out the storage failover before the cluster brings the CSV disk online. In a
disaster scenario, CLX swaps the replication direction and performs the storage failover
automatically, adding failover capabilities for the CSV disks in the clustering environment.
Figure 3 Failover cluster manager
HP XP Cluster Extension supports CSV as well as non-CSV disks on Windows Server 2012/2012
R2. The configuration of CSV disk for CLX is similar to the configuration of normal disk for CLX
support. Because the CSV role is hidden and not seen in Failover Cluster GUI, CLX has provided
PowerShell Cmdlets to configure Cluster Extension XP resource for the CSV disk. For information
10
HP XP Cluster Extension features
about configuring CSV disk for CLX, see “Cluster Extension Cmdlets for CSV and Virtual Machine
Management” (page 52).
Setting up RAID Manager
In addition to the cluster software it integrates with, HP XP Cluster Extension depends on RAID
Manager. Before configuring HP XP Cluster Extension, verify that RAID Manager is installed and
configured, and that the host and disk array systems are properly configured as described in the
following topics.
Creating RAID Manager command devices
To control Continuous Access mirrored disks from a clustered server, install RAID Manager on the
server and configure a special disk, called a command device. The command device must not be
an MSFC resource, cannot be paired, and is assigned to a 36 MB or greater CVS volume. The
command device is identified by CM appended to the emulation type.
RAID Manager command devices can be accessed by redundant paths. HP recommends redundant
paths to prevent HP XP Cluster Extension from aborting if one path to the command device is
missing. See the RAID Manager documentation for more information.
Configuring RAID Manager command devices
In-band and out-of-band communication
Previous versions of HP XP Cluster Extension used in-band communication through the FC link to
communicate with XP arrays. HP XP Cluster Extension supports in-band communication through the
FC link and out-of-band communication through the IP link. Out-of-band communication is supported
only with XP arrays and XP RAID Manager.
When out-of-band communication is used, HP XP Cluster Extension must be configured to use
command device authentication.
When in-band communication is used, command device authentication must be configured only
if the command device user authentication property is enabled. No authentication credentials are
required if the user authentication property is disabled.
When command device authentication is configured, HP XP Cluster Extension logs in to a command
device in order to perform RAID Manager replication and provisioning commands.
Command device authentication
HP XP Cluster Extension supports command device user authentication for physical and virtual
command devices on XP disk arrays. When you enable command device user authentication, you
must add the command device credentials to HP XP Cluster Extension as part of the HP XP Cluster
Extension configuration procedure.
NOTE: HP recommends using the same user name and password for all command devices
configured in a single HORCM file. For more information, see the RAID Manager documentation.
Creating RAID Manager instances
HP XP Cluster Extension requires at least one instance of RAID Manager. HP XP Cluster Extension
starts the configured RAID Manager instance if it is not running. However, if the RAID Manager
instance cannot be started or returns an error, HP XP Cluster Extension can switch to an alternate
RAID Manager instance.
•
Ensure that the path to the RAID Manager binary files is included in the PATH environment
variable.
•
Create a RAID Manager instance to control pair operations and to gather disk array status
information. Because HP XP Cluster Extension switches to the next available instance when a
current instance becomes unavailable, HP recommends that you create several RAID Manager
Planning for HP XP Cluster Extension
11
instances to provide redundancy. Bear in mind, however, that the RAID Manager instance
numbers used for the RaidManagerInstances object must be the same among all servers using
HP XP Cluster Extension.
•
HP recommends that the RAID Manager instances be running at all times to provide the fastest
failover capability. HP XP Cluster Extension provides scripts to include the RAID Manager
startup procedure in the system startup file . See “Starting and stopping the RAID Manager
instances” (page 12) for more information. HP XP Cluster Extension starts the configured RAID
Manager instances if it cannot find any running instance.
Creating RAID Manager device/copy groups
A device/copy group is the unit in which the failover/failback operation is performed. A device/
copy group can contain several volume groups.
Configure a single device/copy group for a failover cluster group (MSFC) . This device/copy
group must include all disks being used for the application service.
The RAID Manager configuration file (horcmX.conf) is used to map device/copy groups to the
internal disk array disks. A device/copy group is the common unit for failover operations initiated
from the server side.
Network considerations
Because RAID Manager is essential to HP XP Cluster Extension, HP recommends that you use the
heartbeat network (a private network) for RAID Manager communications. Alternative network
paths are highly recommended. Configure the networks, RAID Manager uses for each device/
copy group in the HORCM_INST part of the RAID Manager configuration file.
Starting and stopping the RAID Manager instances
Start the RAID Manager instances for HP XP Cluster Extension at system boot time to provide the
fastest access to disk status information.
HP XP Cluster Extension provides a service to integrate the RAID Manager instance startup into the
system startup process. This feature reduces resource group failover times because the HP XP Cluster
Extension resource does not need to start the RAID Manager instances. If the system cannot
automatically start and monitor RAID Manager instances, you can start and stop RAID Manager
with the following commands:
horcmstart instance_numbers
horcmshutdown instance_numbers
Starting RAID Manager without specifying an instance number will start instance 0 with the
associated horcm.conf file. For this reason, zero (0) is not recommended as an instance number
for a HP XP Cluster Extension RAID Manager instance.
Test takeover function
After configuring RAID Manager for the device/copy groups used by HP XP Cluster Extension,
verify that each device fails over correctly from each server in the cluster. The device/copy group
must be in PAIR state.
CAUTION: RAID Manager keeps configuration data of the disk array in system memory. Therefore,
you must stop and restart RAID Manager instances on all servers if a configuration change is
applied to any disk array.
To test the correct failover and failback behavior, log in to each server used with HP XP Cluster
Extension and invoke the following commands if the local disk is the secondary (S-VOL) disk:
set HORCMINST=instance_number
pairdisplay –g device_group_name –fx –CLI
12
HP XP Cluster Extension features
horctakeover –g device_group_name –t timeout
The output of the pairdisplay command indicates whether the local disk is the secondary (S-VOL)
disk and if so, the horctakeover command shows a SWAP-takeover as a result. If pairdisplay
shows the local disk as the primary (P-VOL) disk, log in to a system connected to the secondary
(S-VOL) disk and invoke the horctakeover command there. If the horctakeover command
does not result in a SWAP-takeover, see “Recovery sequence” (page 63) to resolve the issue.
The –t option of the horctakeover command is used only for fence level ASYNC (both Async
and Journal).
Planning for HP XP Cluster Extension
13
2 Configuring HP XP Cluster Extension
After installing HP XP Cluster Extension, use the configuration tool to define the setup configuration.
After you configure HP XP Cluster Extension, use Failover Cluster Management (Windows Server
2008/2008 R2/2012/2012 R2), or cluster commands in the CLI, or Microsoft Failover Cluster
PowerShell Cmdlets to add and configure resources.
For information about how to install HP XP Cluster Extension, see the HP XP Cluster Extension
Software Installation Guide.
Integrating HP XP Cluster Extension with MSFC
To integrate HP XP Cluster Extension with MSFC:
1. Add a HP XP Cluster Extension resource.
For instructions, see “Adding an HP XP Cluster Extension resource” (page 19).
2.
Configure the HP XP Cluster Extension resource.
For more information, see “Configuring HP XP Cluster Extension resources” (page 21).
3.
Add dependencies on the HP XP Cluster Extension resource.
For instructions, see “Adding dependencies on HP XP Cluster Extension resource” (page 34).
Configuring HP XP Cluster Extension
After installation, you must define the setup configuration using the HP XP Cluster Extension
configuration tool, and then copy the configuration information to all of the cluster nodes that use
HP XP Cluster Extension.
You can configure HP XP Cluster Extension with the GUI or the CLI. Use the following instructions
for the GUI. For instructions on performing HP XP Cluster Extension configuration tasks with the
CLI, see “Defining HP XP Cluster Extension configuration information using the CLI” (page 17).
Starting the HP XP Cluster Extension configuration tool
To start the HP XP Cluster Extension configuration tool:
•
For Windows Server 2008/2008 R2: Double-click the HP XP CLX Configuration icon on the
desktop, or select Start→All Programs→Hewlett-Packard→HP XP CLX Configuration Tool→HP
XP CLX Configuration Tool.
For Windows Server 2012/2012 R2: Double-click the HP XP CLX Configuration Tool icon on
the desktop, or select Start→All Apps→Hewlett-Packard→HP XP CLX Configuration Tool.
•
For Server Core or Hyper-V Server: Open a command window and enter CLXXPCONFIG -I.
The XP CLX Configuration Tool window appears.
14
Configuring HP XP Cluster Extension
NOTE: The service name clxmonitor is appended with the text “(not configured)” unless the
port number is configured in the configuration tool.
Defining HP XP Cluster Extension configuration information using the GUI
1.
2.
Open the configuration tool. For instructions, see “Starting the HP XP Cluster Extension
configuration tool” (page 14).
The pair/resync monitor monitors the disk pair status if the ResyncMonitor attribute is set to
YES, and resynchronizes disk pairs if the ResyncMonitorAutoRecover attribute is set to YES.
By default, the pair/resync monitor uses port 5307.
To use a port other than 5307, enter the desired port number in the Port box. The range of
available ports is 1024 through 65535. The pair/resync monitor port value must be the same
on all cluster nodes.
Configuring HP XP Cluster Extension
15
3.
Specify the RAID Manager instances that define the device/copy groups you want to manage
with HP XP Cluster Extension. For more information about HP XP Cluster Extension and RAID
Manager, see “Setting up RAID Manager” (page 11).
a. Click Add in the RAID Manager Instance Configuration section to open the Add RAID
Manager instances window.
b.
4.
Select the RAID Manager instances to use, and then click OK.
For configurations with XP arrays and RAID Manager version 1.24.15 or later only, use the
following steps to configure RAID Manager command device authentication:
NOTE: Command device authentication is not supported with XP arrays or versions of RAID
Manager earlier than 1.24.15.
a.
Click Command Dev Auth in the RAID Manager Instance Configuration section.
The Command Device Authentication dialog box appears.
b.
c.
Select a XP array.
Enter the user name and password associated with a RAID Manager command device.
NOTE: You must enter credentials if command device user authentication is enabled
for at least one command device in a HORCM file associated with the selected array
and HP XP Cluster Extension.
d.
e.
f.
Click Login. When the user authentication operation is verified, the configured user is
listed in the Logged in users box.
Repeat this procedure for additional sets of credentials and arrays.
Click OK to save the configuration and close the Command Device Authentication window.
WARNING! Do not run the RAID Manager RAIDCOM LOGOUT command after logging in
to a P9500 command device and bringing the related resource online. If you run this command,
the HP XP Cluster Extension pair/resync monitor functionality might behave unexpectedly.
16
Configuring HP XP Cluster Extension
5.
Specify the servers that are possible owners for the HP XP Cluster Extension-managed disks.
A server is a possible owner of a disk if it is capable of managing the disk when failover
occurs.
a. Click Add in the Server Configuration section to display the Add Servers window.
b.
Select the servers that are possible owners of the HP XP Cluster Extension-managed disks,
and then click OK.
NOTE: See the Failover Cluster Management (Windows Server 2008/2008 R2/2012/
2012 R2) documentation for more information about possible owners.
6.
Click OK to save the information and close the configuration tool. The configuration information
is saved to the clxcfg file.
NOTE: HP XP Cluster Extension provides a RAID Manager service, which automatically starts
RAID Manager instances at system boot time. This feature reduces resource group and service
and application failover times because the HP XP Cluster Extension resource does not need
to start the RAID Manager instances. When you click Apply or OK in the configuration tool,
the RAID Manager service is started.
7.
Use the procedures in “Importing and exporting configuration information” (page 19) to copy
the clxcfg file to the other cluster nodes.
Defining HP XP Cluster Extension configuration information using the CLI
You can configure HP XP Cluster Extension with the CLI command CLXXPCONFIG. Enter
CLXXPCONFIG -?, CLXXPCONFIG /?, or CLXXPCONFIG /help to view usage information.
1. Enter CLXXPCONFIG -I to open the configuration tool.
Configuring HP XP Cluster Extension
17
2.
The pair/resync monitor monitors the disk pair status if the ResyncMonitor attribute is set to
YES, and resynchronizes disk pairs if the ResyncMonitorAutoRecover attribute is set to YES.
By default, the pair/resync monitor uses port 5307.
To change the pair/resync monitor port, enter CLXXPCONFIG PRM /PORT=value, where
value is the port number you want to use.
NOTE:
3.
To view the pair/resync monitor port, enter CLXXPCONFIG PRM.
Specify the RAID Manager instances that define the device/copy groups you want to manage
with HP XP Cluster Extension. For more information about HP XP Cluster Extension and RAID
Manager, see “Setting up RAID Manager” (page 11).
•
To view the available instances, enter CLXXPCONFIG RM.
•
To add a RAID Manager instance, enter CLXXPCONFIG RM /ADDVAL=value, where
value is the RAID Manager instance you want to add. For example:
Enter CLXXPCONFIG RM /ADDVAL=101 to add RAID Manager instance number 101.
•
To remove a RAID Manager instance, enter CLXXPCONFIG RM /REMOVEVAL=value,
where value is the RAID Manager instance you want to remove. For example:
Enter CLXXPCONFIG RM /REMOVEVAL=101 to remove RAID Manager instance number
101.
NOTE: HP XP Cluster Extension provides a RAID Manager service, which automatically starts
RAID Manager instances at system boot time. This feature reduces resource group and service
or application failover times because the HP XP Cluster Extension resource does not need to
start the RAID Manager instances. Adding or removing RAID Manager instances will start or
restart the RAID Manager service.
4.
For configurations with XP arrays and XP RAID Manager only, use the following command to
configure RAID Manager command device authentication:
CLXXPCONFIG CMD_DEV_CONFIG /DKC=DKCNumber Options
Where DKCNumber is the disk controller/array serial number, and the available options are:
•
LOGIN /USER=User Name: The user name.
•
/PASSWORD=Password: The password.
IMPORTANT: The configured RAID Manager instance associated with the selected DKC
number must be running when you use this command. For instructions on starting a RAID
Manager instance, see “Starting and stopping the RAID Manager instances” (page 12).
TIP: Enter the following command to view the configured arrays and users:
CLXXPCONFIG CMD_DEV_CONFIG
5.
18
Specify the servers that are possible owners for the HP XP Cluster Extension-managed disks.
A server is a possible owner of a disk if it is capable of managing the disk when failover
occurs.
•
To determine whether cluster nodes have been configured for HP XP Cluster Extension,
enter CLXXPCONFIG SERVER.
•
To add a server, enter CLXXPCONFIG SERVER /ADD /NAME=servername, where
servername is the server to add.
•
To remove a server, enter CLXXPCONFIG SERVER /REMOVE /NAME=servername,
where servername is the server to remove.
Configuring HP XP Cluster Extension
6.
Use the procedures in “Importing and exporting configuration information” (page 19) to copy
the configuration information to the other cluster nodes.
Importing and exporting configuration information
The import feature allows you to define the setup configuration using an existing configuration file.
The export feature allows you to save a copy of an existing configuration file.
Use the import and export features to copy the HP XP Cluster Extension configuration file (clxcfg)
from one cluster node to another.
Exporting configuration settings using the GUI
1.
Open the configuration tool.
For instructions, see “Starting the HP XP Cluster Extension configuration tool” (page 14).
2.
3.
4.
Click Export.
When prompted, choose a save location, enter a file name, and then click Save.
Click OK to save and close the configuration tool.
Exporting configuration settings using the CLI
1.
2.
Open a command window.
Enter CLXXPCONFIG EXPORT /FILE=filepath, where filepath specifies the save
location and file name.
Importing configuration settings using the GUI
1.
Open the configuration tool.
For instructions, see “Starting the HP XP Cluster Extension configuration tool” (page 14).
2.
3.
4.
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 CLXXPCONFIG IMPORT /FILE=filepath, where filepath specifies the file location
and name.
Adding an HP XP Cluster Extension resource
IMPORTANT: In Failover Cluster Management for Windows Server 2012/2012 R2, the term
services and applications for resource groups is changed to roles. In this guide, the term services
and applications refers to roles for Windows Server 2012/2012 R2 and services and applications
for Windows Server 2008/2008 R2.
To use HP XP Cluster Extension, you must add an HP XP Cluster Extension resource. Use one of the
following procedures to add a resource:
•
For Windows Server 2008/2008 R2/2012/2012 R2, use the Failover Cluster Management
GUI, or cluster commands in the CLI, or PowerShell Cmdlets.
For instructions, see “Adding an HP XP Cluster Extension resource using the Failover Cluster
Management GUI (Windows Server 2008/2008 R2/2012/2012 R2)” (page 20) or “Adding
an HP XP Cluster Extension resource using the Microsoft CLI cluster commands” (page 20) or
Adding an HP XP Cluster Extension resource
19
“Adding an HP XP Cluster Extension resource using the Microsoft Failover Cluster PowerShell
Cmdlets” (page 20)
•
For Server Core or Hyper-V Server, use the Failover Cluster Management GUI on the remote
management station, or cluster commands in the CLI, or Microsoft Failover Cluster PowerShell
Cmdlets.
HP XP Cluster Extension resource names and service and application names must consist of only
one word. The pair/resync monitor cannot interface with a resource or a service and application
that has space characters in its name.
CAUTION: Do not use the following characters in HP XP Cluster Extension resource names: \ /
: * ? " < > |. Using these characters might affect the creation of the resourcename.online
file, which is used for the HP XP Cluster Extension resource health check mechanism. If the file
creation fails and the pair/resync monitor is not configured, the cluster will report a failed state
for the HP XP Cluster Extension resource.
Adding an HP XP Cluster Extension resource using the Failover Cluster Management
GUI (Windows Server 2008/2008 R2/2012/2012 R2)
Use the procedure in this section to add a resource using the Failover Cluster Management GUI.
For instructions on using the CLI, see “Adding an HP XP Cluster Extension resource using the
Microsoft CLI cluster commands” (page 20).
1. Add a service or application in the Failover Cluster Management GUI, as described in your
Microsoft documentation.
2. Right-click the service or application and select Add a resource→More resources→Add Cluster
Extension XP.
NOTE: This step is applicable for creating CLX resources for non-CSV disks on Windows Server
2008/2008 R2/2012/2012 R2. Using Failover Cluster Management GUI, CLX resource cannot
be added for the CSV disk. For more information about configuring CLX resource for CSV disk on
Windows Server 2012/2012 R2, see “Configuration of XP CLX for CSV disk on Windows Server
2012/2012 R2” (page 36) .
Adding an HP XP Cluster Extension resource using the Microsoft CLI cluster commands
Use the following command to add HP XP Cluster Extension resource:
cluster resource resource_name /create /group:service_or_application_name
/type:"Cluster Extension XP"
Example
This command adds an HP XP Cluster Extension resource called clx_fileshare to the
CLX_SHARE service or application.
cluster resource clx_fileshare /create /group:CLX_SHARE /type:"Cluster
Extension XP"
Alternatively, you can use the following Powershell Cmdlet to add HP XP Cluster Extension Resource:
Add-ClusterResource -Name clx_fileshare -ResourceType "Cluster Extension
XP" -Group CLX_SHARE
Adding an HP XP Cluster Extension resource using the Microsoft Failover Cluster
PowerShell Cmdlets
NOTE: If the Failover Cluster feature is enabled on Windows Server 2012/2012 R2 Server
Core, then the Failover Cluster PowerShell interface is not enabled by default. You must explicitly
enable this feature to use the PowerShell Cmdlets.
20
Configuring HP XP Cluster Extension
Use the following command to add an HP XP Cluster Extension resource:
Add-ClusterResource -Name "resource_name" -Group
“service_or_application_name” -ResourceType "Cluster Extension XP"
Example:
This command adds an HP XP Cluster Extension resource called clx_fileshare to the
CLX_SHARE service or application.
Add-ClusterResource -Name "clx_fileshare" -Group “CLX_SHARE”
-ResourceType "Cluster Extension XP"
Changing an HP XP Cluster Extension resource name
When changing resource names, observe the following rules:
•
Do not change an HP XP Cluster Extension resource name when the resource is online and
the pair/resync monitor is enabled for the resource. Changing the name when the resource
is online might cause problems with the pair/resync monitor functionality.
Changing the resource name is allowed when a resource is offline, or when a resource is
online and the pair/resync monitor is disabled.
•
HP XP Cluster Extension resource names and service and application names must consist of
only one word. The pair/resync monitor cannot interface with a resource or a service and
application that has space characters in its name.
•
Do not use the following characters in HP XP Cluster Extension resource names: \ / : * ?
" < > |. Using these characters might affect the creation of the resourcename.online
file, which is used for the HP XP Cluster Extension resource health check mechanism. If the file
creation fails and the pair/resync monitor is not configured, the cluster will report a failed
state for the HP XP Cluster Extension resource.
Changing an HP XP Cluster Extension resource name (Windows Server 2008/2008
R2/2012/2012 R2)
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 to run the Failover Cluster Management GUI from
a remote node or use cluster commands in the CLI to change the resource name. See “Setting HP
XP Cluster Extension—specific resource properties using the CLI” (page 33) for instructions.
1. Open Failover Cluster Management.
2. Open the resource Properties window and click the General tab.
3. Enter a new name in the Resource Name field.
4. Click OK to save your changes and close the window.
Configuring HP XP Cluster Extension resources
HP XP Cluster Extension resource properties are configured using Failover Cluster Management
(Windows Server 2008/2008 R2/2012/2012 R2), or cluster commands in the CLI, or Powershell
Cmdlets.
•
For information about MSFC and Microsoft Failover Cluster Service properties that affect HP
XP Cluster Extension, see “Setting Microsoft cluster-specific resource and service or application
properties” (page 22).
•
For information about HP XP Cluster Extension-specific properties, see “Setting HP XP Cluster
Extension-specific resource properties” (page 25).
Before configuring HP XP Cluster Extension resources, review the objects described in “User
configuration file and HP XP Cluster Extension objects” (page 64).
Changing an HP XP Cluster Extension resource name
21
NOTE: For the storage disks, you do not have to configure resources of type "Cluster Extension
XP for VM Management". You must configure only resources of type "Cluster Extension XP".
When configuring HP XP Cluster Extension resources, note the following:
•
If the Failover Cluster Management GUI is used to configure an HP XP Cluster Extension
resource, configuring the resource using a user configuration file (UCF) is not required.
•
If the resource is not configured to use the pair/resync monitor, HP XP Cluster Extension creates
a file called resource_name.online in the directory specified by the ApplicationDir
resource property.
If the resource is taken offline, this file will be removed, or the device/copy group associated
with the service or application will be removed from the pair/resync monitor list, if the
pair/resync monitor is configured for that resource. If the device/copy group is the last
monitored disk pair, and you take the resource offline, the pair/resync monitor will be stopped.
•
Windows Server 2008 only: If an HP XP Cluster Extension resource is not configured, the
resource icon in the Failover Cluster Management GUI shows the message “not configured”
next to the resource status.
•
The HP XP Cluster Extension resource must be the first resource for all disk resources in the
dependency list of a resource cluster group.
•
If you have an application in a cluster that uses more than one physical disk from the same
device/copy group, configure a single HP XP Cluster Extension resource, and ensure that all
of the application disks depend on that resource. If the disks are split into different device/
copy groups, you must configure multiple HP XP Cluster Extension resources since an HP XP
Cluster Extension resource operates at the device-group level.
•
The PendingTimeout value must be greater than the ResyncWaitTimeout value.
•
The PendingTimeout must be greater than twice the wait time of all remote RAID Manager
instances multiplied by the number of remote systems. Otherwise, the HP XP Cluster Extension
resource will fail to go online if there is a complete remote data center failure.
tonline > nremote systems x 2 x tWT
where:
tonline = resource online timeout
nremote systems = number of remote systems configured to run RAID Manager instances
tWT = wait time until remote error will be reported by local RAID Manager instance
If a post-executable is specified, the PendingTimeout must be greater than the number of remote
systems multiplied by three times tWT.
•
When a copy group is used in the RAID Manager configuration file, the copy group name is
listed in the resource configuration tool XP device/copy group menu.
Setting Microsoft cluster-specific resource and service or application properties
Microsoft allows you to set specific failover parameter and threshold values for a service or
application, as well as for a resource. Some of these values must be changed for HP XP Cluster
Extension to enable manual recovery actions in case of a disaster.
To set Microsoft cluster-specific resource properties:
22
•
For Windows Server 2008/2008 R2/2012/2012 R2, 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.
Configuring HP XP Cluster Extension
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.
HP XP Cluster Extension requirements for Failover Cluster Management resource properties are
described in “Setting resource properties and values in the GUI” (page 23). If there is no required
value for a property, the valid and/or default values are specified. Set these properties in the
resource properties window or the CLI. If you use the CLI, use the following command:
cluster.exe resource ResourceName /prop PropertyName="PropertyValue".
Powershell Cmdlets can also be used instead of cluster.exe. Use the following command:
Get-ClusterResource "Resource_name" | Set-ClusterParameter -Name
"property_name" -Value "value_to_set"
For more information about setting resource properties, see your Microsoft documentation.
Table 1 Setting resource properties and values in the GUI
Property
Format
Description
Value
Thorough Resource Health
Check Interval (Windows
Server 2008/2008
R2/2012/2012 R2)
Integer
Used to poll “Alive” state for the resource.
Decreasing this value allows faster
resource failure detection but also
consumes more system resources.
Windows Server 2008/2008
R2/2012/2012 R2 GUI:
01:00 mm:ss (Default)
Used to poll “Alive” state for the resource.
Decreasing this value allows for faster
resource failure detection but also
consumes more system resources.
Windows Server 2008/2008
R2/2012/2012 R2 GUI:
00:05 mm:ss (Default)
CLI: 60000 milliseconds
Set this value in the Advanced Policies
(Default)
tab of the resource properties window in
Failover Cluster Management.
IsAlivePollInterval (CLI)
Basic Resource Health Check Integer
Interval (Windows Server
2008/2008 R2/2012/2012
R2)
LooksAlivePollInterval (CLI)
If a resource fails, attempt
restart on current node –
Maximum restarts in the
specified period (Windows
Server 2008/2008
R2/2012/2012 R2)
Integer
Windows Server 2008/2008
Set this value in the Advanced Policies
R2/2012/2012 R2 CLI: 5000
tab of the resource properties window in milliseconds (Default)
Failover Cluster Management.
Defines whether a resource can be
0 (Required)
automatically restarted after it has failed.
Set this value in the Policies tab of the
resource properties window in Failover
Cluster Management
RestartThreshold (CLI)
If restart is unsuccessful, fail Integer
over all resources in this
service or application
(Windows Server
2008/2008 R2/2012/2012
R2)
Defines whether resources will be failed
over if a restart is unsuccessful.
Set this value in the Policies tab of the
resource properties window in Failover
Cluster Management.
Windows Server 2008/2008
R2/2012/2012 R2: Check
(Required)
CLI: 2 restart and
affect the group
(Required)
RestartAction (CLI)
If a resource fails, attempt
restart on current node –
Period for restarts (Windows
Server 2008/2008
R2/2012/2012 R2)
Integer
Determines the amount of time for restart. Windows Server 2008/2008
R2/2012/2012 R2: 15:00
Set this value in the Policies tab of the
mm:ss (Default)
resource properties window in Failover
Cluster Management.
Configuring HP XP Cluster Extension resources
23
Table 1 Setting resource properties and values in the GUI (continued)
Property
Format
Description
RestartPeriod (CLI)
Pending timeout (GUI)
Value
CLI: 900000 milliseconds
(Default)
Integer
PendingTimeout (CLI)
Used to specify the timeout for status
resolution. For more information, see
“Timing considerations for MSFC”
(page 41).
Set this value in the Policies tab of the
resource properties window in Failover
Cluster Management.
Windows Server 2008/2008
R2/2012/2012 R2: 03:00
mm:ss
CLI: 180000 milliseconds
(Default)
HP XP Cluster Extension requirements for service or application properties are described in “Service
or application properties and values” (page 24). If no specific value is required, the default value
is listed. Set these values in the Failover tab of the service or application properties window
(Windows Server 2008/2008 R2/2012/2012 R2) or in the CLI. For more information about
setting service or application properties, see your Microsoft documentation.
TIP: To change the properties in “Service or application properties and values” (page 24) with
the CLI, use the following command: cluster group groupname /prop
propertyname="propertyvalue".
Powershell Cmdlets can also be used instead of cluster.exe. Use the following command:
Get-ClusterResource "Resource_name" | Set-ClusterParameter -Name
"property_name" -Value "vale_to_set"
For more information, see Microsoft documentation.
Table 2 Service or application properties and values
Property
Format
GUI: Failback (Prevent
Integer
failback or Allow failback)
CLI: AutoFailbackType
GUI: Period
String
CLI: FailoverPeriod
GUI: Maximum failures in Integer
the specified period
(Windows Server
2008/2008 R2/2012/
2012 R2)
CLI: FailoverThreshold
Description
Value
Prevents automatic fail back of a service or application
to its primary system. Transfer the service or
application back manually after the failure has been
recovered. This allows for recovery of all possible
failure sources and pair resynchronization (if
necessary) while the application service is still running.
GUI: Prevent
failback
Configuring HP XP Cluster Extension
(required)
Determines the time (in hours) over which the cluster 6 (Default)
service attempts to fail over a service or application.
See “Timing considerations for MSFC” (page 41) for
more information.
Determines the number of failover attempts. The default
value allows the cluster service to transfer the service
or application to each system once in case of
subsequent system failure. Due to the nature of this
parameter, it is possible that the service or application
automatically restarts on a system several times if all
cluster systems are not members of the cluster at that
time.
If this value is set to a number higher than the current
number of clustered systems for the cluster group, the
service or application will continue to restart until
either the FailoverThreshold value or the FailoverPeriod
timeout value is reached.
24
CLI: 0
Windows Server
2008/2008
R2/2012/2012
R2: Number of
nodes in the cluster
minus 1.
Setting HP XP Cluster Extension-specific resource properties
Changes to resource properties take effect when the resource is brought online again. For instructions
on changing resource properties, see the following:
•
GUI: “Setting HP XP Cluster Extension resource properties using the GUI (Windows Server
2008/2008 R2/2012/2012 R2, Server Core, and Hyper-V Server)” (page 25)
•
MMC: “Setting HP XP Cluster Extension resource properties using the MMC” (page 32)
•
CLI: “Setting HP XP Cluster Extension—specific resource properties using the CLI” (page 33)
•
PowerShell Cmdlets: “Setting HP XP Cluster Extension resource properties using the Microsoft
Failover PowerShell Cmdlets” (page 34)
•
UCF: “Setting HP XP Cluster Extension properties using a UCF” (page 34)
Setting HP XP Cluster Extension resource properties using the GUI (Windows Server 2008/2008
R2/2012/2012 R2, Server Core, and Hyper-V Server)
This section describes the procedures for setting HP XP Cluster Extension resource properties with
a GUI. You can perform these procedures through the resource configuration utility using the
Failover Cluster Management GUI or the standalone resource configuration tool. For instructions
on using the two GUI options, see the following:
•
“Using Failover Cluster Management to set resource properties (Windows Server 2008/2008
R2/2012/2012 R2)” (page 25)
•
“Using the resource configuration tool to set resource properties (Server Core and Hyper-V
Server)” (page 27)
TIP: For information on managing HP XP Cluster Extension resources from a remote management
station through the MMC, see “Setting HP XP Cluster Extension resource properties using the MMC”
(page 32).
Using Failover Cluster Management to set resource properties (Windows Server 2008/2008
R2/2012/2012 R2)
For Windows Server 2008/2008 R2/2012/2012 R2, use the Failover Cluster Management GUI
to set resource properties.
1. Open Failover Cluster Management.
2. Double-click the HP XP Cluster Extension resource in the summary pane to open the Properties
window.
3. Click the HP XP CLX Settings tab.
4. Make the necessary parameter changes, and then click OK.
Configuring HP XP Cluster Extension resources
25
Using Failover Cluster Management to set resource properties of a CLX resource on which a CSV
disk is dependant (Windows Server 2012/2012 R2)
In the case of a CSV disk, it is possible to create a CLX resource in the CSV group, and make the
CSV disk dependent on the CLX resource. For information about configuring CSV disk for CLX,
see “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 52). After
creating the CLX resource in the CSV group, the CLX resource is not displayed on the Windows
Server 2012/2012 R2 Failover Cluster Manager GUI.
In the Failover Cluster Manager GUI, only the CSV disk is visible, but not the role in which the CSV
disk exists.
A CLX resource can be created in the CSV role. Note that it will not be visible in the Failover Cluster
Manager GUI.
To set the parameters of the CLX resource on which the CSV disk is dependent, the CLX parameters
are populated in the physical disk resource properties page under HP XP CLX Settings.
To set the resource properties of a CLX resource on which a CSV disk is dependant for Windows
Server 2012/2012 R2, use the Failover Cluster Management GUI and perform the following steps:
1. Open Failover Cluster Management.
2. Double-click the CSV disk in the summary pane to open the Properties window.
3. Click the HP XP CLX Settings tab.
4. Modify the parameters as required, and then click OK.
26
Configuring HP XP Cluster Extension
NOTE: In the case of a CSV disk, the HP XP CLX Settings tab in the properties window is visible
only if that CSV disk is dependant on a "Cluster Extension XP" resource.
Alternatively, you can use HP XP Resource Configuration Tool (ClxXPResConfig.exe) to configure
the CLX resource on which the CSV is dependent.
Using the resource configuration tool to set resource properties (Server Core and Hyper-V Server)
For Server Core or Hyper-V Server, use the HP XP Cluster Extension resource configuration tool to
set resource properties. 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.
•
You cannot use the resource configuration tool to add or delete a resource.
•
You can use the tool to configure multiple resources at one time. This saves time because you
can switch resources from the tool menu.
•
The resource configuration tool is recommended for Hyper-V and Server Core environments
because the properties you enter are validated. When you configure HP XP Cluster Extension
resource properties from a remote management station or through the CLI, the properties you
enter are not validated.
To use the resource configuration tool:
1. Open a command window and enter ClxXpResConfig.exe.
2. Select the resource you want to change in the XP CLX resource menu.
3. Make the necessary parameter changes, and then click OK.
Configuring HP XP Cluster Extension resources
27
Configuring RAID Manager instance numbers for RAID Manager service
To configure RAID Manager instance numbers from the Failover Cluster Management HP XP CLX
Settings tab or the resource configuration tool:
1. To add an instance:
a. Click Add to open the Add RAID Manager instances window.
b. Select one or more instances and click OK.
2.
3.
To remove an instance, select it and click Remove.
Click OK to save your changes and close the window.
Configuring the RAID Manager device/copy group details
To configure RAID Manager device/copy group details from the Failover Cluster Management HP
XP CLX Settings tab or the resource configuration tool:
1. Select a value in the XP device/copy group menu.
2. Click OK to save your changes and close the window.
Configuring RAID Manager device/copy group advanced properties
The HP XP CLX Settings tab of the HP XP Cluster Extension resource offers basic settings and is
used to enter environment data, such as RAID Manager instances. The more advanced settings
can be accessed through additional buttons in the HP XP CLX Settings tab.
28
Configuring HP XP Cluster Extension
To configure RAID Manager advanced properties from the Failover Cluster Management HP XP
CLX Settings tab or the resource configuration tool:
1. Click the Advanced button to open the Advanced Fence Level Failover Behavior window. The
available settings in this window depend on the fence level used with your device/copy
groups.
2.
3.
•
For the DATA fence level, you can update the Data lose mirror and DATA lose data center
values. See “DataLoseDataCenter” (page 71) and “DataLoseMirror” (page 72) for more
information about these values.
•
For the ASYNC fence level, you can update the ASYNC takeover timeout value. See
“AsyncTakeoverTimeout” (page 69) for more information about this value.
•
For the journal fence level, you can update the Journal data currency on S-VOL and
ASYNC takeover timeout values. See “JournalDataCurrency” (page 73) and
“AsyncTakeoverTimeout” (page 69) for more information about these values.
Update the settings as needed, and then click OK to close the window.
Click OK to save your changes and close the window.
Configuring HP XP Cluster Extension resources
29
Notes
•
After a device/copy group is configured in the resource configuration utility, do not change
the device/copy group name or swap the name with another device/copy group name in
the HORCM file. If you do this, restart the HORCM manager instance and reconfigure the HP
XP Cluster Extension resource.
•
Do not use HORCM commands to change the device/copy group property for a device/copy
group that is configured for an HP XP Cluster Extension resource. If you do this, the changed
property is not reflected immediately in the HP XP CLX Settings tab. To work around this
situation, re-select the device/copy group from the XP device/copy group menu in the HP XP
CLX Settings tab.
Configuring server data center assignments
To configure server data center assignments from the Failover Cluster Management HP XP CLX
Settings tab or the resource configuration tool:
1. To remove a data center assignment, select the assignment, and then click Remove.
2. To modify a data center assignment, select the assignment, and then click Modify. Enter the
new Data center name in the Modify Node in Data Center List window, and then click OK.
3. To add a data center assignment, click Add. Select a host and a data center, and then click
OK.
4. Click OK to save your changes and close the window.
Changing failover and failback behavior
To configure failover and failback behavior from the Failover Cluster Management HP XP CLX
Settings tab or the resource configuration tool:
1. Click Failover/Failback to display the Failover/Failback window.
2.
3.
Update the ApplicationStartup and AutoRecover values as needed, and then click OK.
Click OK to save your changes and close the Properties window or Resource Configuration
tool.
Activating the pair/resync monitor
The pair/resync monitor detects and responds to suspended Continuous Access links if the
ResyncMonitor object is set to YES. If the ResyncMonitorAutoRecover object is set to YES, automatic
disk pair resynchronization is also activated.
When the resource is taken offline, the monitor is stopped for the RAID Manager device/copy
group used for this resource.
30
Configuring HP XP Cluster Extension
CAUTION:
If a resource cannot be taken offline manually, and goes into a failed state, the cluster administrator
must disable monitoring of the device/copy group for this resource. To avoid data corruption, this
task must be part of the recovery procedure when HP XP Cluster Extension is deployed in an MSFC
environment. See “Stopping the pair/resync monitor” (page 50).
You must ensure that the pair/resync monitor does not monitor and resynchronize the disk pair
(device/copy group) from both disk array sites.
To activate the pair/resync monitor from the Failover Cluster Management HP XP CLX Settings tab
or the resource configuration tool:
1. Click Pair ResyncMon to open the Pair/Resync Monitor Properties window.
2.
3.
4.
5.
6.
Select the Use pair/resync monitor check box to set the ResyncMonitor object to YES.
Select the Pair/resync monitor autoRecovery check box to set the ResyncMonitorAutoRecover
object is to YES.
If you want to change the monitoring interval (ResyncMonitorInterval), enter a value in the
Monitor interval box.
Click OK to save your changes and close the Pair/Resync Monitor Properties window.
Click OK to save your changes and close the Properties window or Resource Configuration
tool.
TIP: You can activate ResyncMonitor from the Microsoft CLI. For example, if your HP XP Cluster
Extension resource is clx_fileshare, enter the following command: C:\>cluster resource
clx_fileshare /privprop ResyncMonitor=yes.
Configuring takeover actions
Pre-executables and post-executables can be defined to be executed before or after HP XP Cluster
Extension invokes its takeover functions.
To configure takeover actions from the Failover Cluster Management HP XP CLX Settings tab or
the resource configuration tool:
1. Click Pre/Post Exec to display the Pre/Post Executable Properties window.
Configuring HP XP Cluster Extension resources
31
2.
Update the PreExecScript, PostExecScript, and PostExecCheck values as needed, and then
click OK.
When configuring pre/post takeover executable paths, enter the full path to the script. If a
script fails, the HP XP Cluster Extension resource will fail.
3.
Click OK to save your changes and close the Properties window or Resource Configuration
tool.
Configuring Rolling Disaster Protection
To configure rolling disaster protection from the Failover Cluster Management HP XP CLX Settings
tab or the resource configuration tool:
1. Click Rolling Disaster to display the Rolling Disaster Protection window.
2.
Add mirror units to each data center:
a. Click Add MU # to DC A.
b. Select mirror units from the list, and click OK.
c. Repeat the previous steps for Data Center B.
3.
Update the BCResyncEnabledA, BCResyncEnabledB,BCResyncMuListA, and BCResyncMuListB
values as needed, and then click OK.
Click OK to save your changes and close the Properties window or Resource Configuration
tool.
4.
NOTE: For more information, see “Setting HP XP Cluster Extension objects to enable rolling
disaster protection” (page 80).
Setting HP XP 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.
NOTE: When you configure HP XP Cluster Extension resource properties from a remote
management station through the MMC, which uses the standard Microsoft Properties tab, the
properties you enter are not validated, so you must enter the property values accurately, and verify
them against the HP XP Cluster Extension documentation.
When you use this option, you will see the default Microsoft properties page instead of the HP XP
Cluster Extension HP XP CLX Settings tab. For more information about using the MMC, see “Remote
management of HP XP Cluster Extension resources in a cluster (Windows Server 2008/2008
R2/2012/2012 R2)” (page 43) and your Microsoft documentation.
32
Configuring HP XP Cluster Extension
Setting HP XP Cluster Extension—specific resource properties using the CLI
The cluster commands in this section can be used with Windows Server 2008/2008 R2/2012/
2012 R2, Server Core, or Hyper-V Server.
The MSFC default properties for a resource can be changed using the following command: cluster
resource resource_name /privprop [object_name=value|"value1 value2 ..."].
NOTE: When you configure HP XP Cluster Extension resource properties using the CLI, the
properties you enter are not validated, so you must enter the property values accurately, and verify
them against the HP XP Cluster Extension documentation.
You can display all attributes of the HP XP Cluster Extension resource clx_fileshare with the
following command:
cluster resource clx_fileshare /privprop
The following example changes the FenceLevel property for the resource clx_fileshare:
C:\>cluster resource clx_fileshare /privprop FenceLevel=data
The following example changes the RAID Manager instance used for the resource clx_fileshare
from 10 to 99, and then adds instance 22 to provide redundancy:
C:\>cluster resource clx_fileshare /privprop RaidManagerInstances="99 22"
The following example changes the name of the resource xp Cluster Extension resource1
to xp Cluster Extension resource2:
cluster resource "XP Cluster Extension resource1" /ren:"XP Cluster
Extension resource2"
Configuring HP XP Cluster Extension resources
33
Powershell Cmdlets can also be used instead of cluster.exe to perform the same tasks. For
more information, see Microsoft documentation.
Setting HP XP Cluster Extension resource properties using the Microsoft Failover PowerShell Cmdlets
The cluster commands described in this section can be used with Windows Server 2008/2008
R2/2012/2012 R2, Server Core, or Hyper-V Server. You can change the Windows cluster default
properties for a resource by using the following command:
Get-ClusterResource "resource_name" | Set-ClusterParameter -Name
"property_name" -Value "value_to_set"
NOTE: When you configure HP XP Cluster Extension resource properties using the PowerShell,
the properties that you enter are not validated. Ensure that you enter the correct property values
and verify them against the HP XP Cluster Extension documentation.
The following example sets the ApplicationStartup property for the resource test_clxxp
to FASTFAILBACK
Get-ClusterResource "test_clxxp" | Set-ClusterParameter -Name
"ApplicationStartup" -Value FASTFAILBACK
For more information about the available properties, see “User configuration file and HP XP Cluster
Extension objects” (page 64)
Setting HP XP Cluster Extension properties using a UCF
You can use a UCF to configure certain HP XP Cluster Extension properties.
Properties that you can configure in a UCF include:
•
LogLevel
•
ClusterNotifyCheckTime
•
ClusterNotifyWaitTime
•
LocalDCLMForNonPAIRDG
•
StatusRefreshInterval
IMPORTANT:
If you plan to use the default values for these properties, no UCF is required.
To configure properties using a UCF:
1. Take the HP XP Cluster Extension resource offline.
2. Open the sample UCF.cfg file located in %HPCLX_PATH%\sample.
3. Update the file with the property values you want to use.
For more information on the available properties, see “User configuration file and HP XP
Cluster Extension objects” (page 64).
4.
5.
Save the file and copy it to the following directory on all cluster nodes: %HPCLX_PATH%\
conf.
Bring the HP XP Cluster Extension resource online.
Adding dependencies on HP XP Cluster Extension resource
HP XP Cluster Extension Software must be the first resource in the resource chain of a MSFC service
or application. All resources that depend on the disk resource, such as a file share, and all disk
resources (physical disks), must be configured for dependency on the HP XP Cluster Extension
resource.
34
Configuring HP XP Cluster Extension
When adding dependencies:
•
For Windows Server 2008/2008 R2/2012/2012 R2, use the Failover Cluster Management
GUI, cluster commands in the CLI, PowerShell Cmdlets, or the MMC for remote management.
•
For Server Core or Hyper-V Server, use cluster commands in the CLI, PowerShell Cmdlets, or
the MMC.
Adding dependencies using Failover Cluster Management (Windows Server
2008/2008 R2/2012/2012 R2)
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. Select a service or application that has HP XP Cluster Extension resource.
3. Double-click a disk in the summary pane.
4. Click the Dependencies tab, and then click Insert.
5. Select the HP XP Cluster Extension resource in the Resource menu.
6.
Click OK to add the selected dependency.
Adding dependencies using the CLI
The cluster commands in this section can be used with Windows Server 2008/2008 R2/2012/
2012 R2, Server Core, or Hyper-V Server.
To add a dependency on HP XP Cluster Extension resource using the CLI, use the following
command:
cluster resource physical_disk_resource
/adddependency:Cluster_Extension_XP_resource
The following command adds a dependency on the HP XP Cluster Extension clx_fileshare
resource to the physical disk resource Disk_32b_00b:
Adding dependencies on HP XP Cluster Extension resource
35
cluster resource Disk_32b_00b /adddependency:clx_fileshare
Powershell Cmdlets can also be used instead of cluster.exe to add dependencies. For more
information, see Microsoft documentation.
Adding dependencies using the PowerShell
1.
To add dependency on an HP XP Cluster Extension resource using the PowerShell, use the
following command:
Add-ClusterResourceDependency -Resource <Name_of_the_disk_resource>
– Provider <CLXXP_Resource_Name>
2.
The following command adds a dependency on the HP XP Cluster Extension clx_fileshare
resource to the physical disk resource Disk_32b_00b:
Add-ClusterResourceDependency -Resource “Disk_32b_00b”-Provider
clx_fileshare
Configuration of XP CLX for CSV disk on Windows Server 2012/2012
R2
Configuration of CLX resource for the CSV disk is a two-step process. This is almost similar to the
configuration of CLX for non-CSV disk.
•
Creation of CLX resource in the CSV Role
The CSV disk resides in its own role in the Failover Cluster. The CSV disk is visible in the
Failover Cluster Manager GUI, but the role in which the CSV disk resides is not visible. Because
of this restriction, you will not be able to create a CLX resource in the CSV role to manage
the CSV disk using Failover Cluster Manager GUI.
To overcome this limitation, CLX provides PowerShell Cmdlets to create CLX resource in the
CSV role and set the dependency of the CSV disk on the CLX resource. For more information,
see “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 52).
•
Setting the private properties for the CLX resource
After creating the CLX resource in the CSV role and setting the dependency of CSV disk on
the CLX resource, the private properties of the CLX resource must be configured. Because the
CSV role is not visible in the Failover Cluster Manager GUI, the CLX resource created in the
CSV role is also not visible in the Failover Cluster Manager GUI. For information about setting
the private properties of CLX resource created in the CSV role, see “ Using Failover Cluster
Management to set resource properties of a CLX resource on which a CSV disk is dependant
(Windows Server 2012/2012 R2)” (page 26) .
After completing these two steps, the CLX is ready to manage the CSV disks.
Disaster-tolerant configuration example using a file share
The following example describes a configuration in which:
36
•
Your environment consists of four systems (host1_DCA, host2_DCA, host3_DCB and
host4_DCB).
•
Your environment includes two disk arrays with serial numbers 35014 and 35013.
•
You have configured clxfileshare as a device/copy group in the RAID Manager
c:\windows\horcm101.conf file and in the c:\windows\horcm102.conf file.
•
A pre-executable clxpre.exe will be invoked by HP XP Cluster Extension.
•
You use the default failover behavior for the cluster group.
•
The resource CLX_FILESHARE is part of the service group CLX_SHARE and must be brought
online before the physical disk resource Disk_32b_00b.
Configuring HP XP Cluster Extension
“Service or application example (quorum service control disks not shown)” (page 37) illustrates
failover options and shows a second cluster group CLX_IIS. “CLX_FILESHARE resource sample”
(page 37) is a sample CLX_FILESHARE resource screen shot, and “ HP XP Cluster Extension resource
tree for CLX_SHARE” (page 38) is an example of the resource tree for service or application
CLX_SHARE.
Figure 4 Service or application example (quorum service control disks not shown)
Figure 5 CLX_FILESHARE resource sample
Disaster-tolerant configuration example using a file share
37
Figure 6 HP XP Cluster Extension resource tree for CLX_SHARE
HP XP 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 XP Cluster Extension resource and can be brought online only when the HP XP Cluster
Extension resource is already online. Independent of this resource tree, the network card will be
configured with the CLX_SHARE service or application's (resource group's) IP address and network
name.
If all those resources have been brought online, the file share can be started.
To configure the HP XP Cluster Extension resource according to the configuration in “ HP XP Cluster
Extension resource tree for CLX_SHARE” (page 38):
1. Log in to the host3_DCB system with the Administrator account.
2. Create the file share service or application with all previously mentioned resources and its
dependencies, except the HP XP Cluster Extension resource on host3_DCB.
3. Create a new resource of type Cluster Extension XP and add systems host2_DCA, host3_DCB,
and host4_DCB to its possible owners.
4. Change the restart behavior of the HP XP Cluster Extension resource so that the resource can
be restarted and so that the restart affects the group. Set the number of restarts to 0.
5. Edit the resource properties, including the following information:
6.
7.
8.
•
RAID Manager instances
•
RAID Manager device/copy group details
•
Server data center assignments
Click the Pre/Post Exec button and add clxpre.exe with its full path. (The clxpre.exe
program is an example. It is not included in the HP XP Cluster Extension product.)
Add a dependency on the HP XP Cluster Extension resource CLX_FILESHARE to the physical
disk resource Disk_32b_00b.
Check the cluster service, group, and resource settings with the following commands:
C:\>cluster group CLX_SHARE /prop
C:\>cluster resource CLX_FILESHARE /prop
38
Configuring HP XP Cluster Extension
9.
For Windows Server 2008/2008 R2/2012/2012 R2, enable the HP XP Cluster Extension
resource property If restart is unsuccessful, fail over all resources in this service or application.
This value is set in the Policies tab in the Failover Cluster Management Properties window.
If you are using the CLI to set resource properties, the equivalent command is cluster res
CLX_FILESHARE /prop RestartAction=0.
10. Bring the service or application online on host3_DCB by using the Failover Cluster
Management GUI or the following cluster command in the CLI:
C:\>cluster group CLX_SHARE /online:host3_DCB
11. Verify that the HP XP Cluster Extension resource and all other CLX_SHARE application resources
are brought online:
C:\>cluster group CLX_SHARE
12. Take the service or application offline, and verify that all resources are stopped:
C:\>cluster group CLX_SHARE /offline
C:\>cluster group CLX_SHARE
13. Bring the service or application online again and verify that all resources are available:
C:\>cluster group CLX_SHARE /online:host3_DCB
C:\>cluster group CLX_SHARE
14. Check the cluster service settings of system host4_DCB, and the group and resource settings.
15. Move the service or application to system host4_DCB and verify that all resources are
available:
C:\>cluster group CLX_SHARE /moveto:host4_DCB
C:\>cluster group CLX_SHARE
16. Check the cluster service settings of system host2_DCA, and the group and resource settings.
17. Move the service or application to system host2_DCA and verify that all resources are
available:
C:\>cluster group CLX_SHARE /moveto:host2_DCA
C:\>cluster group CLX_SHARE
18. Check the cluster service settings of system host1_DCA, and the group and resource settings.
19. Take the service or application offline, and verify that all resources are stopped:
C:\>cluster group CLX_SHARE /offline
C:\>cluster group CLX_SHARE
20. Change the HP XP Cluster Extension resource to be able to restart on another system:
C:\>cluster resource CLX_FILESHARE /prop RestartAction=2
C:\>cluster resource CLX_FILESHARE /prop
Managing HP XP Cluster Extension resources
You can manage resources by bringing them online and offline, or by deleting them.
Bringing a resource online
Resources are usually brought online automatically when the service or application is brought
online. You might need to move the service or application to the node where you want to bring
the resource online.
Managing HP XP Cluster Extension resources
39
When bringing resources online:
•
For Windows Server 2008/2008 R2/2012/2012 R2, use the 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.
When taking resources offline:
•
For Windows Server 2008/2008 R2/2012/2012 R2, use the Failover Cluster GUI, or Cluster
CLI or MMC, 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.
Deleting a resource
Deleting a running resource causes the resource and its dependents to go offline.
CAUTION: Deleting a running HP XP Cluster Extension resource does not remove the
resource_name.online file and does not remove the device/copy group from the list of
monitored device/copy groups if the pair/resync monitor is used to monitor the Continuous Access
Software link. Therefore, the device/copy group must be deleted from the list of monitored device/
copy groups manually using the clxchkmon command after deleting the HP XP Cluster Extension
resource. See “Stopping the pair/resync monitor” (page 50).
CAUTION:
Failure to delete the monitored device/copy group from the list of monitored groups can cause
data corruption if the ResyncMonitorAutoRecover attribute is set to YES.
When deleting resources:
•
For Windows Server 2008/2008 R2/2012/2012 R2, use the 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.
Perform the following steps to delete a CLX resource using the PowerShell Cmdlets:
1. Take the required service and application group or role offline. This takes all the resources in
that group offline.
2. Remove the cluster disk dependency on the CLX resource.
Remove-ClusterResourceDependency: Removes a dependency between two resources
in a clustered role within a failover cluster.
Example: Remove-ClusterResourceDependency –Resource “Cluster Disk 1”
–provider “CLX_XP_Cluster Disk 1”
3.
Remove the cluster resource
Remove-ClusterResource: This Cmdlet deletes the Cluster resource from the Failover
Cluster.
Example: Remove-ClusterResource -Name “CLX_XP_Cluster Disk 1”
Perform the following steps to delete a CLX resource using the Failover Cluster Command Line
Interface (cluster.exe):
1. Take the required service and application group or role offline. This takes all the resources in
that group offline.
40
Configuring HP XP Cluster Extension
2.
Remove the cluster disk dependency on the CLX resource.
Cluster.exe resource <Disk Name> /REMOVEDEP:<CLX Resource Name>
Example: cluster resource "Cluster Disk 1" /removedep:"CLX_XP_Cluster
Disk 1”
3.
Remove the cluster resource
Cluster.exe resource <DiskName> /delete
Example: cluster resource " CLX_XP_Cluster Disk 1" /delete
For more information on deleting resources, see your Microsoft documentation.
Using Hyper-V Live Migration with HP XP 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.
HP XP Cluster Extension has the capability of discovering unfavorable storage-level conditions for
performing live migration. In response to these conditions, HP XP Cluster Extension stops or cancels
the live migration process and informs you. This is accomplished with no VM downtime. For
example, if live migration is initiated while VM data residing on the storage arrays is still merging
and not in sync, HP XP Cluster Extension proactively cancels the live migration and informs you to
wait until the merge is in progress. Without this feature, live migration might fail or the VM might
come online in the remote data center with inconsistent data.
The HP XP Cluster Extension StatusRefreshInterval property, which you can configure in a UCF for
each application, specifies the time interval between consecutive array status gathering operations
before the live migration to the target cluster node occurs. By adjusting this property, you can
increase the probability of getting the correct XP array status to ensure a successful live migration.
The default StatusRefreshInterval value is 300 seconds. For more information about configuring
this property, see “Setting HP XP Cluster Extension properties using a UCF” (page 34).
HP XP Cluster Extension cancels live migration operations within the local data center when the
device/copy group is not in PAIR status. Use the LocalDCLMForNonPAIRDG property, which can
be configured in a UCF for each application, to change the setting to allow live migration to occur
within the local data center even if the device/copy group is not in PAIR status.
Hyper-V Live Migration is supported with HP XP Cluster Extension for Windows Server 2008 R2
and Windows Server 2012/2012 R2 using only the synchronous fence levels DATA and NEVER.
The asynchronous and journal fence levels are not supported.
Using Hyper-V Live Migration with Cluster Shared Volumes is supported with HP XP Cluster Extension.
TIP: For more information about using Hyper-V Live Migration with HP XP Cluster Extension, see
the white paper Live Migration across data centers and disaster tolerant virtualization architecture
with HP Cluster Extension and Microsoft Hyper-VTM on the white papers website: www.hp.com/
storage/whitepapers.
Timing considerations for MSFC
HP XP Cluster Extension gives priority to disk array operations over cluster software operations. If
HP XP Cluster Extension invokes a disk pair resynchronization operation or gathers information
about the remote disk array, HP XP Cluster Extension waits until the requested status information
is reported. This ensures the priority of data integrity over cluster software failover processes. This
behavior can lead to failed HP XP Cluster Extension resources as described below:
•
HP XP Cluster Extension uses RAID Manager instances to communicate with the remote disk
array. Depending on the setting of the RAID Manager instance timeout parameter and the
Using Hyper-V Live Migration with HP XP Cluster Extension
41
number of remote instances, the online operation could time out. This can occur if the local
RAID Manager instance cannot reach the remote RAID Manager instance.
•
HP XP Cluster Extension tries to resynchronize disk pairs and waits until the RAID Manager
device/copy group is in PAIR state if the ApplicationStartup resource property is set to
RESYNCWAIT. RAID Manager and the XP fully support delta resynchronization; however, the
delta between the primary and secondary disks could be large enough for the copy process
to exceed the resource PendingTimeout value.
•
The ResyncWaitTimeout object can cause HP XP Cluster Extension resources to fail if its value
is higher than the resource PendingTimeout value.
•
If running in fence level ASYNC, the default value of AsyncTakeoverTimeout can cause the
resource to fail because its value exceeds the resource PendingTimeout value. The takeover
process for fence level ASYNC can take much longer when slow communications links are in
place.
To prevent takeover commands from being terminated by the resource PendingTimeout, measure
the time required to copy the installed disk array cache and adjust the resource PendingTimeout
value. When measuring the copy time, measure only the slowest link used for Continuous
Access Software. This ensures that the disk array cache can be transferred from the remote
disk array, even in the event of a single surviving replication link between the disk arrays.
In general, because the failover environment is dispersed into two (or more) data centers, the
failover time cannot be expected to be the same as that in a single data center with a single shared
disk device. Therefore, the following values of the HP XP Cluster Extension resource and the service
and application using that resource must be adjusted, based on failover tests performed to verify
the proper configuration setup: FailoverPeriod, RestartPeriod, PendingTimeout, LookAlive, and
IsAlive.
In addition, the service or application's FailoverPeriod value must be higher than the resource’s
RestartPeriod value, and both must be higher than the resource’s PendingTimeout value.
MSFC provides two parameters to adjust state change recognition/resolution:
•
IsAlive
•
LookAlive
HP XP Cluster Extension automatically calls the IsAlive function whenever the cluster service calls
the LookAlive function. Therefore, both functions must be set to the same value.
Bouncing service or application
HP XP Cluster Extension will alternate (start and fail) between local nodes if the ApplicationStartup
property has been set to FASTFAILBACK and no remote system is available until the service or
application restart limit has been reached. For more information, see “ApplicationStartup” (page 68).
The FastFailbackEnabled property is not used by the HP XP Cluster Extension integration with
MSFC.
Administration
HP XP Cluster Extension administration includes remote management of resources and monitoring
of system resources and logs.
42
Configuring HP XP Cluster Extension
Remote management of HP XP Cluster Extension resources in a cluster (Windows
Server 2008/2008 R2/2012/2012 R2)
You can use the MMC with Failover Cluster Management to manage clusters and configure HP
XP Cluster Extension resources. Note the following when configuring HP XP Cluster Extension
resources by using the MMC from a remote management station:
•
When you use the MMC to remotely configure HP XP Cluster Extension resource properties
in a Server Core or Hyper-V Server cluster node, the Failover Cluster Management GUI on
the remote management station displays the standard Microsoft Properties tab instead of the
customized HP XP Cluster Extension HP XP CLX Settings tab. For more information about the
Properties tab, see “Setting HP XP Cluster Extension resource properties using the MMC”
(page 32).
•
When you install HP XP Cluster Extension into a Windows Server 2008/2008 R2/2012/
2012 R2 environment, the resource extension DLL is registered by default, which prevents you
from configuring HP XP Cluster Extension resource from a remote management station. If you
need to remotely configure HP XP Cluster Extension resource in a Windows Server 2008/2008
R2/2012/2012 R2-based cluster, unregister clxmscsex.dll from the cluster node, which
allows you to configure the HP XP Cluster Extension resource using the standard Microsoft
Properties tab. Use the command cluster /UNREGADMINEXT:clxmscsex.dll to unregister
the DLL.
Powershell Cmdlets can also be used instead of cluster.exe to unregister clxmscsex.dll.
For more information, see Microsoft documentation.
CAUTION: Configuring HP XP Cluster Extension resources using the MMC from a remote
management station is supported using only the standard Microsoft Properties tab. Do not try
to use the customized HP XP Cluster Extension HP XP CLX Settings tab for this purpose.
•
If you see the customized HP XP Cluster Extension HP XP CLX Settings tab when you try to
configure HP XP Cluster Extension resource from a remote management station using the MMC,
you must unregister clxmscsex.dll from the cluster node. Use the command cluster
/UNREGADMINEXT:clxmscsex.dll to unregister the DLL. Unregistering the DLL allows you
to configure the resource using the standard Microsoft Properties tab. This situation might
occur if you have a cluster with both Server Core or Hyper-V Server and Windows Server
2008/2008 R2/2012/2012 R2 cluster nodes.
Powershell Cmdlets can also be used instead of cluster.exe to unregister clxmscsex.dll.
For more information, see Microsoft documentation.
•
When you configure HP XP Cluster Extension resource properties from a remote management
station through the MMC, which uses the standard Microsoft Properties tab, the properties
you enter are not validated, so you must enter the property values accurately, and verify them
against the HP XP Cluster Extension documentation.
•
On Windows Server 2012/2012 R2 Failover Cluster, you cannot use the MMC to remotely
configure the CLX resource on which the CSV disk is dependent. On a Windows 2012/2012
R2 Server Core system, you must use the XP Resource Configuration Tool
(ClxXpResConfig.exe) to configure the CLX resource for the CSV disk. On a non-server
core Windows Server 2012/2012 R2 system, you can use the CLX resource configuration
utility integrated with the CSV cluster resource in the Failover Cluster, or use the XP Resource
Configuration Tool (ClxXpResConfig.exe) to configure the CLX resource for the CSV disk.
System resources
Monitor the system resources on a regular basis as part of Windows administration. If any system
resource usage by the cluster service is reaching maximum levels, stop and then restart the cluster
Administration
43
service. This action automatically fails over the resources and resets system resources. See the
MSFC documentation for information about how to stop a cluster service.
An alternate method is to manually move all resources to another node in the cluster before stopping
the cluster service. After all resources are successfully moved to another node, stop and then restart
the cluster service; then, manually move back all resources.
Logs
If the HP XP Cluster Extension log files need to be cleared and reset (for example, to reduce disk
space usage), you can delete the files. HP XP Cluster Extension automatically creates new log files.
NOTE: When VM management functionality is used on a Windows Server 2012/2012 R2
system, the logs for this feature is created in the same location. The name of the file is
VMClxMscs.log.
TIP:
Archive the log files before deleting them.
Hyper-V Live Migration log entries
In the HP XP Cluster Extension log file (clxmscs.log), live migration messages include the prefix
CLX_LM to help you differentiate live migration issues from HP XP 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.
[10/12/09 20:13:02][2136][CLX_LM: CLXVMDISK04-App01][INFO] CLX started
gathering VM "Virtual Machine VM04" specific storage information.
Virtual Machine Management hosted on a Cluster Shared Volume on Windows Server
2012/2012 R2
Cluster Shared Volumes on Windows Server 2012/2012 R2 support virtualized workloads to
create virtual machines on Cluster Shared Volumes in the Failover Cluster Manager. These VMs
are highly available as they are managed by the Failover Cluster.
CSV disk resource can be owned by one cluster node whereas, highly available VMs that are
created on the CSV disk can either be owned by the same cluster node or by a different cluster
node. The node that owns the CSV disk resource is known as the co-ordinator node. In a multi-site
storage array replicated environment, clustering of nodes is distributed across the datacenter. For
non-CSV disks, the application role such as VM role contains the application resource, disk resource,
and the CLX resource together. That is, in whichever cluster node the disk resource is online, the
application resource such as VM resource will also be online. Therefore, the entire application
role containing the application resource, disk resource, and the CLX resource together will be
owned by a cluster node. The CSV feature ensures that the CSV disk can be owned by any cluster
node and highly available VMs that are created on the CSV disk running either on the same cluster
node, or on a cluster node different from that of the CSV.
If the highly available VMs are running on a cluster node that is in a different datacenter, the VMs
run in the redirected-access mode. This is because, the replicated disk in the datacenter where
VMs are running is presented to the cluster node as read-only on the storage array. This indicates
that, in the CSV disk, the I/O operations of the VMs is carried over the IP network to the coordinator
node in the other datacenter. The coordinator node ensures that the I/O is committed to the disk.
Because of this reason, VMs might incur a performance penalty especially if the distance between
the datacenter is long. The CLX VM management feature is applicable in such a scenario.
The CLX for VM management ensures that the highly available VMs and the co-ordinated node of
the CSV disk are always running in the cluster nodes of the same datacenter.
44
Configuring HP XP Cluster Extension
NOTE: The cluster resource type “Cluster Extension XP for VM Management” supports VM
management in a cluster. This resource type is available only on Windows Server 2012/2012
R2 and Windows Server 2012/2012 R2 Server Core.
If you do not need VMs running on a CSV disk that is in the redirected access mode, you must
configure resources of type "Cluster Extension XP for VM Management" in the corresponding VM
role.
To configure CLX feature for VM Management functionality for a highly available VM created on
a CSV disk, perform the following steps:
1. Create a CSV disk in the Failover Cluster Manager. The newly created CSV disk must be
managed by the CLX to do storage failover.
NOTE:
GUI.
2.
3.
4.
5.
The CSV role in which the CSV disk is residing is not visible in the Failover Cluster
Create a Cluster Extension XP cluster resource in the hidden CSV role using PowerShell Cmdlet.
For more information, see “Cluster Extension Cmdlets for CSV and Virtual Machine
Management” (page 52)
After the Cluster Extension XP resource is created in the CSV role, configure the CLX Resource
private properties. See “ Using Failover Cluster Management to set resource properties of a
CLX resource on which a CSV disk is dependant (Windows Server 2012/2012 R2)” (page 26)
Create highly available VM on CSV disk. The steps are similar to the steps for creating highly
available VMs on a normal disk.
After the highly available VM is created on the CSV disk, configure the CLX feature for the
VM management functionality for that VM. You can do this either by using PowerShell Cmdlet
or manual steps.
To enable a VM for VM Management functionality, perform the following steps:
Using PowerShell Cmdlet
CLX provides PowerShell Cmdlet to enable all the VMs, which are created on a CSV disk, for VM
management functionality. If you want only specific set of VMs to have the VM management
functionality, manually enable a specific VM for VM management functionality. For more information,
see “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 52).
Manual Steps
If you want only specific set of VMs of a CSV disk to have VM management functionality, perform
the following steps:
1. Create a cluster resource of resource type “Cluster Extension XP for VM Management” in the
VM Role.
NOTE:
The corresponding CSV is dependant on CLX.
Example: Using the PowerShell
Add-ClusterResource -Name VM_MGMT_Res -Group VM4_2k12 -ResourceType
"Cluster Extension XP for VM Management"
2.
Set the dependency of VM configuration resource on the newly created resource of resource
type “Cluster Extension XP for VM Management”.
Example: Using the PowerShell
Add-ClusterResourceDependency -Resource VM_MGMT_Res -Provider
“Virtual Machine Configuration VM4_2k12”
The configuration is complete and the VM role is enabled with VM management functionality.
Administration
45
Behavior of VM Management functionality in various disaster scenarios
This section describes various disaster scenarios and how the VM management functionality behaves
in such scenarios:
•
CSV disk owning cluster node and the VM owning cluster node are in different datacenter and
the VM Role is offline:
When you try to bring the VM role online, the online operation fails because the owner nodes
of the respective resource are running in different datacenters. When a resource fails on the
cluster node, the role behaves according to the cluster role failover policies.
•
CSV disk owner node and the VM owner node are in same datacenter and the VM Role is
offline:
When you try to bring the VM role online, the online operation succeeds because the owner
nodes of the respective resource are running in the same datacenter.
•
The cluster node that owns the CSV disk fails, or the CSV disk fails and the CSV disk moves to
a node in the same datacenter, or the CSV disk is moved manually to a node in the same
datacenter:
In this scenario, because 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
of the VMs.
•
The cluster node that owns the CSV disk fails, or the CSV disk fails and the CSV disk moves to
a node in the remote datacenter, or the CSV disk is moved manually to a node in the remote
datacenter:
In this scenario, all the VMs that are configured with CLX feature for VM management wait
for the CSV disk to come online on a cluster node in the remote datacenter. Because the CSV
disk is moved to a node in the remote datacenter, all the VMs that are running in the respective
cluster nodes in the primary datacenter will be live migrated by CLX to cluster nodes in the
remote datacenter. Every role has next preferred node property. Selection of the target node
for the live migration is based on how the next preferred owner property has been set for the
VM role.
Preferred Owners is not set: In this scenario, the next preferred owner node is selected randomly
among the cluster nodes present in the remote datacenter. The selected cluster node must be
up. If not, search will continue until a cluster node is found in the remote datacenter.
Preferred Owners is partially set: In this scenario, cluster nodes that are not part of the next
preferred owner node property are added to the list in the order of NodeID. Next preferred
owner that is in the same datacenter as the datacenter where CSV disk is owned is selected
from that list. The selected cluster node must be up. If not, search continues in the list until a
cluster node is found in the remote datacenter.
Preferred Owners is completely set: Because all the cluster nodes are part of the next preferred
owner node property list, the next preferred owner node is selected from this list. The selected
cluster node must be up and must be in the same datacenter as the datacenter where the CSV
disk is owned. If not, search continues in the list until a cluster node is found in the remote
datacenter.
•
When VM owning node goes down and the VM moves to a node in the remote datacenter:
In this scenario, the VM fails to come online on the remote datacenter and the cluster tries to
bring it online on a node in the local datacenter.
•
When VM owning node goes down and the VM moves to the next preferred node in the same
datacenter:
In this scenario, the VM tries to come online on the next preferred node in the same datacenter.
46
Configuring HP XP Cluster Extension
3 HP XP Cluster Extension and CLI
HP XP Cluster Extension allows integration into almost any cluster software for commercial Windows
operating systems. Use the clxrun command to check proper functionality of HP XP Cluster
Extension prior to integration with the cluster software.
The CLI also allows integration of the Continuous Access software. For information on supported
platforms, see the HP SPOCK website: http://www.hp.com/storage/spock.
Configuring the CLI
Using the HP XP Cluster Extension CLI requires the following configuration steps:
1. Create the Continuous Access environment.
2. Create the RAID Manager configuration file.
3. Configure command device authentication.
When the HP XP Cluster Extension CLI is used with virtual command device and/or command
device authentication enabled, use the HP XP Cluster Extension configuration tool CLI to
configure the authentication credentials.
For instructions, see “Defining HP XP Cluster Extension configuration information using the
CLI” (page 17).
4.
Create and configure the user configuration file.
Creating the Continuous Access environment and configuring RAID Manager
HP support personnel are trained and authorized to set up the Continuous Access software. You
can, however, configure and change the disk pairs and RAID Manager instances using LUN
Manager, Command View XP, XP Remote Web Console, XP Remote Web Console, Command
View Advanced Edition, and RAID Manager.
Timing considerations
HP XP Cluster Extension is designed to prioritize disk array operations over application service
startup operations. If HP XP Cluster Extension invokes disk pair resynchronization operations or
gathers information about the remote disk array, HP XP Cluster Extension waits until the requested
status information is reported. This prioritizes data integrity over application service startup and
failover behavior.
Because the takeover timing depends on the configuration of your RAID Manager environment
and the settings in UCF.cfg, these considerations must be evaluated:
•
HP XP Cluster Extension uses RAID Manager instances to communicate with the remote disk
array. Depending on the settings of the RAID Manager instance timeout parameter and the
number of remote instances, the online operation could time out. This can also happen if
clxrun is used in a script or called by another program and the local RAID Manager instance
cannot reach the remote RAID Manager instance. See “Setting up RAID Manager” (page 11)
for more information.
•
If the ApplicationStartup attribute is set to RESYNCWAIT, HP XP Cluster Extension tries to
resynchronize disk pairs and waits until the RAID Manager device/copy group is in PAIR
state. In some versions of RAID Manager and the array microcode, a full resynchronization
is done. Depending on the amount of data to be transferred, it could take hours to
Configuring the CLI
47
resynchronize. If this is the case, clxrun may take some time to complete. Do not stop
clxrun; use it to check the status of the associated RAID Manager device/copy groups.
Even if the RAID Manager version and the array firmware version allow a delta
resynchronization, the amount of delta data to be transferred between the primary and the
secondary could be long enough for the copy process to take a while.
•
If running in fence level ASYNC, the default value of the AsyncTakeoverTimeout is set to a
very high number. This is done because the takeover process for fence level ASYNC can take
much longer when slow communications links are in place; adjust this value after measuring
the Continuous Access Software environment. See “AsyncTakeoverTimeout” (page 69) for
more details.
To prevent premature termination of the takeover commands by the takeover timeout, measure
the time to copy the installed XP disk array cache and adjust the resource online timeout
interval according to the measured copy time. Use only the slowest link Continuous Access
Software link to measure the copy time. This ensures that the disk array cache can be transferred
from the remote disk array, even in the event of a single surviving replication link between the
disk arrays.
In general, because the failover environment is dispersed into two (or more) data centers, the
failover time cannot be expected to be the same as it would be in a single data center with a single
shared disk device.
Restrictions for customized HP XP Cluster Extension implementations
The following are some restrictions that apply when using the HP XP Cluster Extension CLI:
•
The HP XP Cluster Extension CLI call clxrun must be invoked before the associated disk
resources are activated.
•
Associated disk resources must not be activated on any other system. If other disk resources
are activated, HP XP Cluster Extension may remove write-access rights for those disk devices
(putting them in read-only mode).
Creating and configuring the user configuration file
The CLI expects as an argument the name configured as the APPLICATION tag value. You do not
need to specify the SearchObject object.
The following is an example of a customized user configuration file when using clxrun:
# This is the XP Cluster Extension User Configuration File (UCF.cfg).
# The COMMON tag specifies the configuration for the
# XP Cluster Extension core environment
#
COMMON
LogLevel
info
#show disk state info in the logs
# The APPLICATION tag specifies the configuration for the
# XP Cluster Extension failover behavior
APPLICATION
sap
#the application service
DeviceGroup
sapdg
#RM dev group for the app service
RaidManagerInstances 22 90
#RM instance number for dev group
XPSerialNumbers 34001 34005
#local and remote array Serial Numbers
DC_A_Hosts
eserv1 eserv2
#data center A hostnames
DC_B_Hosts
eserv3 eserv4
#data center B hostnames
FenceLevel
data
#FenceLevel changed from default
APPLICATION
netscape
#the application service
DeviceGroup
netscapedg
#RM dev group for the app service
RaidManagerInstances 22 90
#RM instance number for dev group
XPSerialNumbers 34001 34005
#local and remote array Serial Numbers
DC_A_Hosts
eserv1 eserv2
#data center A hostnames
DC_B_Hosts
eserv3 eserv4
#data center B hostnames
48
HP XP Cluster Extension and CLI
CLI commands
This section describes the following CLI commands:
•
“clxrun” (page 49)
•
“clxchkmon” (page 50)
clxrun
Check disk set
Description
clxrun can be used to manually prepare the application service's disk set before an existing
application service start procedure is invoked. When using clxrun, the status of the associated
RAID Manager device/copy group is checked to ensure that access to the disk set will occur under
data consistency and concurrency situations only.
clxrun must be invoked before the application service disk set can be activated; it is considered
an online-only program. However, the CLI features provide the same disaster tolerance features
as the integrated versions of HP XP Cluster Extension.
NOTE:
Execution of clxrun does not start the pair/resync monitor.
Syntax
clxrun [-version] [-forceflag] app_name
Arguments
–version
Displays the HP XP Cluster Extension version
–forceflag
Forces startup
app_name
The application name configured in the user configuration file (UCF.cfg)
The clxrun program expects only one parameter as the default setting. This parameter is used
to uniquely identify the application service in the APPLICATION section of the user configuration
file.
clxrun first checks for the –forceflag option. When using clxrun, it is not necessary to create
an application_name.forceflag file. This option, however, must be specified first if used.
CAUTION:
The forceflag option is implemented as an emergency switch to manually activate your disk
set. If the forceflag option has been specified, HP XP Cluster Extension will not check any
consistency or concurrency rules before activating the disk set.
Return codes
clxrun exits with one of the following return codes:
0
OK
Application service can be started.
1
ERROR_GLOBAL
Application service should not start on any system in either site on either disk array.
2
ERROR_DC
Application service should not start on any system in the local site on the local disk array.
3
ERROR_LOCAL
Application service should not start on this system.
CLI commands
49
Example 1
# clxrun sap
Example 1 is based on the assumption that you have defined an APPLICATION tag named sap
in the UCF.cfg file and you have specified all necessary objects, including the DeviceGroup
object, to map the disk set to the application service sap. HP XP Cluster Extension will check the
disk set mapped to the application service sap, run the necessary takeover procedure and return
one of the return codes mentioned in the return code table.
Example 2
# clxrun -forceflag sap
Example 2 is based on the assumption that you have defined an APPLICATION tag named sap
in the UCF.cfg file and you have specified all necessary objects, including the DeviceGroup
object, to map the disk set to the application service sap. HP XP Cluster Extension will check the
disk set mapped to the application service sap, and run the necessary takeover procedure to
enable read/write access to the disk set.
clxchkmon
Pair/resync monitor access program
Description
The clxchkmon utility program allows starting and stopping of the resynchronization features and
queries to gather state information of the monitored device/copy groups.
To update or remove a specific resource, use clxchkmon –n resource_name –g
device/copy_group. If –clx is not specified, the command is applied only to non-XP Cluster
Extension resources.
To update all non-XP Cluster Extension resources, use clxchkmon –t. To update HP XP Cluster
Extension resources, use clxchkmon –clx –t.
Displaying resources
The following command displays all resources:
clxchkmon –show
The following command displays HP XP Cluster Extension resources only:
clxchkmon –clx –show
Removing resources
The following command removes only non-XP Cluster Extension resources:
clxchkmon –remove
The following command removes all HP XP Cluster Extension resources:
clxchkmon –clx –remove
Stopping the pair/resync monitor
The pair/resync monitor is stopped when all resources are removed from monitoring.
1. To check whether the pair/resync monitor is running, execute the following command:
clxchkmon –show
50
HP XP Cluster Extension and CLI
2.
Select the application and device/copy group combination you want to remove from the
pair/resync monitor and remove it with the following command:
clxchkmon -n [[application_name] | [resource_group_name] |
[resource_name]] -g device/copy_group_name –remove
where
application_name|resource_group_name|resource_name is the resource name
(as defined by the APPLICATION tag in the UCF.cfg file) of the HP XP Cluster Extension
resource and should match the clxchkmon output. If the –clx option is not specified, the
command is executed only for non-XP Cluster Extension resources.
CAUTION:
If you respond Y (yes) to remove the combination, the resource will be removed from the list of
resources to be monitored in the pair/resync monitor. If this is not an emergency removal attempt
and the HP XP Cluster Extension resource is online, the previous procedure will lead to a failed
resource, which will take all dependent resources offline and eventually force your application
offline.
Do not use this command to take your HP XP Cluster Extension resources offline.
Syntax
clxchkmon [-clx] [-s host name] [-n resource_name —g device_group] [[[-t
monitor_interval] | [-autorecover mode] | [-remove [-force]] | [-show]
| [-pid] | [-stopsrv] | [-log [[error] | [warning] | [info] | [trace]]]]]
[-p port number]
where:
-s hostname
Specifies the name of a host.
–n resource_name
Specifies the resource (application) name as used in HP XP Cluster
Extension.
–g device_group
Specifies a RAID Manager device/copy group name.
–t monitor_interval Specifies interval in seconds to update registered monitor resources.
–autorecover mode Specify YES to enable autorecovery, or NO to disable autorecovery for
registered monitor resource.
–clx
Executes the command only for HP XP Cluster Extension resources.
–remove
Removes the resource from the monitor list.
–force
Disables user confirmation to remove resource.
–show
Displays monitored resources.
—pid
Returns the process ID of the pair/resync monitor.
–stopsrv
Stops the pair/resync monitor socket server.
–log
Sets the log level for the pair/resync monitor.
–p port_number
Specifies the port number to be used.
Return codes
clxchkmon exits with one of the following return codes:
0
Successful, or device/copy group is in PAIR state.
1
Device/copy group is not in PAIR state.
2
Resource/device/copy group is not registered with the pair/resync monitor.
3
Pair/resync monitor (clxchkd) is not running.
4
Device/copy group's pair status is pending.
CLI commands
51
10
Pair/resync monitor internal error.
11
Invalid argument to pair/resync monitor.
12
Pair/resync monitor received signal (control-c) interrupt.
13
Unknown status for device/copy group.
14
No port number is specified in services file for clxmonitor.
16
Invalid use of the –clx option on a non-XP Cluster Extension resource or HP XP Cluster
Extension resource specified without the –clx option.
100
RAID Manager error.
Related information
For more information, see “Monitoring and resynchronizing device/copy groups” (page 81).
Cluster Extension Cmdlets for CSV and Virtual Machine Management
CLX supports the following PowerShell Cmdlets to perform various operations:
•
Add-CSVDependencyOnCLXXP
•
Add-VMDependencyOnCLXXP
•
Get-VMOnClusterSharedVolumeListForCLXXP
As part of the CLX installation, these Cmdlets are registered on every node in the cluster. Before
running any of these Cmdlets, you must load the Snap-In in every PowerShell session. To load the
Snap-In, CLX provides a PowerShell script file AddClxXpCmdletsSnapIn.ps1 which is located
at <CLX Install Directory>\bin.
You must run this script to load the PowerShell Snap-In. After loading the Snap-In, you must run
the supported Cmdlets to perform the various required operations. These Cmdlets are available
till the PowerShell session exists. At the end of the session, the Snap-In is unloaded and these
Cmdlets are not available.
The CLX PowerShell Snap-In can also be unloaded by running the PowerShell script
RemoveClxXpCmdletsSnapIn.ps1 located at <CLX Install Directory>\bin directory.
NAME:
Add-CSVDependencyOnCLXXP
SYNOPSIS:
Adds a cluster resource of type "Cluster Extension XP" 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. Dependency of CSV on CLX ensures that a CSV comes
online only after CLX resource has come online.
SYNTAX:
Add-CSVDependencyOnCLXXP [-CSVDiskName <String>] [<CommonParameters>]
DESCRIPTION:
This cmdlet creates a resource of type "Cluster Extension XP" to the list of resources and makes the
given cluster shared volume dependent on this cluster resource. Cluster resource of type "Cluster
Extension XP" is also called “CLX resource” interchangeably.
The cmdlet first tries to find out if there is already a cluster resource of type "Cluster Extension XP"
in the CSV group (role) to which the CSV belongs.
If there is no resource of type "Cluster Extension XP" in the corresponding CSV group, the cmdlet
first creates a resource of type "Cluster Extension XP" in the CSV group and then makes the CSV
52
HP XP Cluster Extension and CLI
resource in the CSV group dependent on the newly created resource of type "Cluster Extension
XP".
If CLX resource already exists in the given CSV role, then the cmdlet verifies whether CSV is already
dependent on the resource of type "Cluster Extension XP". If the CSV is already dependent on the
CLX resource, then the cmdlet moves to the next CSV (if you have not specified any particular CSV).
In the absence of dependency on the existing CLX resource, the cmdlet creates a dependency of
CSV resource in the CSV group on resource of type "Cluster Extension XP".
Because of this configuration, whenever CSV role is brought online, resource of type "Cluster
Extension XP" is the first resource to come online and then the dependent CSV disk comes online.
This ensures that CLX resource can do all the necessary storage related status gathering and failover
operations before CSV disk can come online.
PARAMETERS:
-CSVDiskName <String>
Specifies the cluster shared volume name which will be made dependent on resource of type
"Cluster Extension XP”.
Required?
false
Position?
named
Default value
Accept pipeline input?
false
Accept wildcard characters?
false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction,
ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable.
For more information, see about_CommonParameters ((http://go.microsoft.com/fwlink/?
LinkID=113216)
INPUTS:
Does not accept input objects.
OUTPUTS:
Does not return object.
NOTES:
CSV resource must 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-CSVDependencyOnCLXXP
This command first finds out all the cluster shared volumes in the cluster. After getting all such CSVs,
it tries to make each CSV dependent on resource of type "Cluster Extension XP".
If CSV is already dependent on "Cluster Extension XP", then the cmdlet moves to the next CSV in
the cluster.
However, if there is no existing dependency on "Cluster Extension XP" but resource of this type is
existing in the corresponding CSV group, CSV resource is made dependent on the existing "Cluster
Extension XP" type resource. If it is not present, a new resource of type "Cluster Extension XP" is
created and the CSV resource is made dependent on it.
Cluster Extension Cmdlets for CSV and Virtual Machine Management
53
While creating the dependency, CSV resource must be offline, otherwise the dependency is not
created.
PS C:> Add-CSVDependencyOnCLXXP
Logs will be generated with default "info" log level. For changing the
logging level, configure LogLevel parameter in UCF.cfg file at file
location: C:\Program Files\Hewlett-Packard\Cluster Extension XP\conf\
UCF.cfg
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Add-CSVDependencyOnCLXXP
All CSV in the cluster will be made dependent on CLX XP. Continue? [Y]
Yes [N] No [S] Suspend [?] Help (default is "Y"): y
Starting with the steps to create and add dependency of cluster shared
volume(s) on "Cluster Extension XP"
TOTAL CLUSTER SHARED VOLUME(S) IN THE CLUSTER: 6
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_864e7b5e-c46f-4611-b046-29470bd4bd07" in CSV Owner Group:
"864e7b5e-c46f-4611-b046-29470bd4bd07"
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 1" in CSV Owner Group:
"864e7b5e-c46f-4611-b046-29470bd4bd07"
Created the resource "CLX_XP_Cluster Disk 1" in CSV Owner Group:
"864e7b5e-c46f-4611-b046-29470bd4bd07"
Added the dependency of CSV: "Cluster Disk 1" on "Cluster Extension XP"
type resource: "CLX_XP_Cluster Disk 1"
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 2" in CSV Owner Group:
"0f145465-1186-4bbb-b9e2-2fde4cb1127d"
Created the resource "CLX_XP_Cluster Disk 2" in CSV Owner Group:
"0f145465-1186-4bbb-b9e2-2fde4cb1127d"
Added the dependency of CSV: "Cluster Disk 2" on "Cluster Extension XP"
type resource: "CLX_XP_Cluster Disk 2"
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 3" in CSV Owner Group:
"a71654bf-6c77-42c1-95dd-025ea8c4f225"
Created the resource "CLX_XP_Cluster Disk 3" in CSV Owner Group:
"a71654bf-6c77-42c1-95dd-025ea8c4f225"
Added the dependency of CSV: "Cluster Disk 3" on "Cluster Extension XP"
type resource: "CLX_XP_Cluster Disk 3"
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 4" in CSV Owner Group:
"618ab9b8-53d2-49a1-a18d-a27912a46adb"
Created the resource "CLX_XP_Cluster Disk 4" in CSV Owner Group:
"618ab9b8-53d2-49a1-a18d-a27912a46adb"
Cannot add the dependency of CSV: "Cluster Disk 4" on "Cluster Extension
XP" type resource: "CLX_XP_Cluster Disk 4" as the resource is online
54
HP XP Cluster Extension and CLI
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 5" in CSV Owner Group:
"b3efe970-e107-4510-829a-14d30eaedbec"
Created the resource "CLX_XP_Cluster Disk 5" in CSV Owner Group:
"b3efe970-e107-4510-829a-14d30eaedbec"
Cannot add the dependency of CSV: "Cluster Disk 5" on "Cluster Extension
XP" type resource: "CLX_XP_Cluster Disk 5" as the resource is online
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 6" in CSV Owner Group:
"d2bdcccf-6afc-4c96-a38f-cf6eb2f8e8d7"
Created the resource "CLX_XP_Cluster Disk 6" in CSV Owner Group:
"d2bdcccf-6afc-4c96-a38f-cf6eb2f8e8d7"
Cannot add the dependency of CSV: "Cluster Disk 6" on "Cluster Extension
XP" type resource: "CLX_XP_Cluster Disk 6" as the resource is online
Cluster Shared Volume Name
CLX XP Resource Name
Cluster Disk 1
CLX_XP_Cluster Disk 1
Cluster Disk 2
CLX_XP_Cluster Disk 2
Cluster Disk 3
CLX_XP_Cluster Disk 3
TOTAL CLUSTER SHARED VOLUMES IN THE CLUSTER FOR WHICH CLX XP DEPENDENCY
ADDED: 3
Example 2
C:\PS>Add-CSVDependencyOnCLXXP -CSVDiskName "Cluster Disk 1"
This command tries to make CSV "Cluster Disk 1" dependent on resource of type "Cluster Extension
XP".
If CSV is already dependent on "Cluster Extension XP", then the cmdlet does not do anything.
However, if there is no existing dependency on "Cluster Extension XP" but resource of this type is
existing in the corresponding CSV group, CSV resource is made dependent on the existing "Cluster
Extension XP" type resource. If it is not present, a new resource of type "Cluster Extension XP" is
created and CSV resource is made dependent on it.
While creating the dependency, CSV resource must be offline, else dependency is not created.
PS C:> Add-CSVDependencyOnCLXXP -CSVDiskName "Cluster Disk 1"
Logs will be generated with default "info" log level. For changing the
logging level, configure LogLevel parameter in UCF.cfg file at file
location: C:\Program Files\Hewlett-Packard\Cluster Extension XP\conf\
UCF.cfg
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Add-CSVDependencyOnCLXXP
CSV: Cluster Disk 1 will be made dependent on CLX XP. Continue? [Y] Yes
[N] No [S] Suspend [?] Help (default is "Y"): y
Starting with the steps to create and add dependency of cluster shared
volume(s) on "Cluster Extension XP"
Resource of type "Cluster Extension XP" to be created with Name:
"CLX_XP_Cluster Disk 1" in CSV Owner Group:
"864e7b5e-c46f-4611-b046-29470bd4bd07"
Cluster Extension Cmdlets for CSV and Virtual Machine Management
55
Created the resource "CLX_XP_Cluster Disk 1" in CSV Owner Group:
"864e7b5e-c46f-4611-b046-29470bd4bd07"
Added the dependency of CSV: "Cluster Disk 1" on "Cluster Extension XP"
type resource: "CLX_XP_Cluster Disk 1"
Cluster Shared Volume Name
CLX XP Resource Name
Cluster Disk 1
CLX_XP_Cluster Disk 1
TOTAL CLUSTER SHARED VOLUMES IN THE CLUSTER FOR WHICH CLX XP DEPENDENCY
ADDED: 1
RELATED LINKS:
http://www.hp.com/go/clx
Name:
Add-VMDependencyOnCLXXP
SYNOPSIS:
Adds a resource of type "Cluster Extension XP for VM Management" to the list of resources on
which a particular "Virtual Machine Configuration" type of resource depends, using AND as the
connector, within a Failover Cluster. Existing dependencies remain in the list. Dependency of VM
configuration on CLX ensures that a virtual machine comes online only after CLX resource has come
online.
SYNTAX:
Add-VMDependencyOnCLXXP [-CSVDiskName <String>] [<CommonParameters>]
Description:
This cmdlet creates a dependency of "Virtual Machine Configuration" that is residing on a cluster
shared volume onto a resource of type "Cluster Extension XP for VM Management."
The cmdlet first tries to find out if there is already a resource of type "Cluster Extension XP for VM
Management" in a VM role.
If it is existing, the cmdlet verifies whether "Virtual Machine Configuration" resource in the VM
role is already dependent on the resource of type "Cluster Extension XP for VM Management". If
the "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 XP for VM Management".
If there is no resource of type "Cluster Extension XP for VM Management" in the VM role, then the
cmdlet first creates a resource of type "Cluster Extension XP for VM Management" in the VM role
and then makes the "Virtual Machine Configuration" resource in the VM role dependent on the
newly created resource of type "Cluster Extension XP for VM Management".
A virtual machine configuration resource is brought online after the "Cluster Extension XP for VM
Management" type resource that it depends on comes online. Similarly, virtual machine configuration
resource is taken offline before the "Cluster Extension XP for VM Management" type resource that
it depends on goes offline.
PARAMETERS:
-CSVDiskName <String>
Specifies the cluster shared volume name for which all the virtual machines residing on it are made
dependent on resource of type "Cluster Extension XP for VM Management".
56
Required?
false
Position?
named
HP XP Cluster Extension and CLI
Default value
Accept pipeline input?
false
Accept wildcard characters?
false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction,
ErrorVariable, WarningAction, WarningVariable, OutBuffer and OutVariable.
For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?
LinkID=113216).
INPUTS:
Does not accept input object.
OUTPUTS:
Does not return object.
NOTES:
The VM roles created using Failover Cluster Manager GUI are supported.
"Virtual Machine Configuration" resource must be offline while trying to add the dependency.
If a VM is residing on a CSV which is not dependent on resource of type "Cluster Extension XP",
then an error is thrown and no further operations are performed on that VM.
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-VMDependencyOnCLXXP
This command first finds out all the virtual machine configuration resources that are residing on all
the cluster shared volumes. After getting all virtual machine configurations, it tries to make each
virtual machine configuration dependent on resource of type "Cluster Extension XP for VM
Management".
If virtual machine configuration is already dependent on "Cluster Extension XP 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 XP 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 XP for VM Management" type resource. If it is
not present, a new resource of type "Cluster Extension XP for VM Management" is created and
virtual machine configuration resource is made dependent on it.
While creating the dependency, the virtual machine configuration resource must be offline, otherwise
the dependency is not created.
If a virtual machine configuration is residing on a cluster shared volume which is not dependent
on resource of type "Cluster Extension XP", then an error is thrown and no further operations are
performed on that VM.
PS C:\> Add-VMDependencyOnCLXXP
Logs will be generated with default "info" log level. For changing the
logging level, configure LogLevel parameter in UCF.cfg file at file
location: C:\Program Files\Hewlett-Packard\Cluster Extension XP\conf\
UCF.cfg
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Cluster Extension Cmdlets for CSV and Virtual Machine Management
57
Add-VMDependencyOnCLXXP
All VM residing in cluster will be made dependent on CLX XP. Continue?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
Starting with the steps to create and add dependency of virtual machines
residing on CSV on "Cluster Extension XP for VM Management".
TOTAL VIRTUAL MACHINE(S) IN THE CLUSTER: 1
VM role: "New Virtual Machine" is present on cluster shared volume :
"Cluster Disk 1" which is not dependent on resource of type "Cluster
Extension XP". Ensure that cluster shared volume is made dependent on
"Cluster Extension XP" before doing further operations.
Resource of type "Cluster Extension XP for VM Management" to be created
with Name: "CLX_XP_New Virtual Machine" in virtual machine role "New
Virtual Machine"
Created the resource "CLX_XP_New Virtual Machine" in virtual machine
role: "New Virtual Machine"
Added the dependency of Virtual Machine Configuration in VM Role New
Virtual Machine" on "Cluster Extension XP for VM Management" type
resource: "CLX_XP_New Virtual Machine"
Virtual Machine Role
CLX Resource Name
New Virtual Machine
CLX_XP_New Virtual Machine
Total virtual machines in the cluster residing on CSV: 1
TOTAL VIRTUAL MACHINES IN THE CLUSTER FOR WHICH CLX XP DEPENDENCY ADDED:
1
Example 2
C:\PS>Add-VMDependencyOnCLXXP -CSVDiskName "Cluster Disk 1"
This command first finds out all the virtual machine configurations that are residing on the cluster
shared volume "Cluster Disk 1". After getting all virtual machine configurations on the provided
cluster shared volume, it tries to make each virtual machine configuration resource dependent on
resource of type "Cluster Extension XP for VM Management".
If the virtual machine configuration is already dependent on "Cluster Extension XP for VM
Management", then the cmdlet moves to the next virtual machine configuration on the provided
CSV.
However, if there is no existing dependency on "Cluster Extension XP 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 XP for VM Management" type resource. If it is
not present, a new resource of type "Cluster Extension XP for VM Management" is created and
virtual machine configuration resource is made dependent on it.
While creating the dependency, the virtual machine configuration resource must be offline, otherwise
the dependency is not created.
If a virtual machine configuration is residing on a cluster shared volume that is not dependent on
resource of type "Cluster Extension XP", then an error is thrown and no further operations are
performed on that VM.
PS C:\> Add-VMDependencyOnCLXXP -CSVDiskName "Cluster Disk 1
Logs will be generated with default "info" log level. For changing the
logging level, configure LogLevel parameter in file UCF.cfg at file
location: C:\Program Files\Hewlett-Packard\Cluster Extension XP\conf\
UCF.cfg
58
HP XP Cluster Extension and CLI
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Add-VMDependencyOnCLXXP
All VM residing on CSV: Cluster Disk 1 will be made dependent on CLX
XP. Continue? [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
Starting with the steps to create and add dependency of virtual machines
residing on CSV on "Cluster Extension XP for VM Management".
TOTAL VIRTUAL MACHINE(S) IN THE CLUSTER: 1
Resource of type "Cluster Extension XP for VM Management" to be created
with Name: "CLX_XP_New Virtual Machine" in virtual machine role "New
Virtual Machine"
Created the resource "CLX_XP_New Virtual Machine" in virtual machine
role: "New Virtual Machine"
Added the dependency of Virtual Machine Configuration in VM Role New
Virtual Machine" on "Cluster Extension XP for VM Management" type
resource: "CLX_XP_New Virtual Machine"
Virtual Machine Role
CLX Resource Name
New Virtual Machine
CLX_XP_New Virtual Machine
Total virtual machines in the cluster residing on CSV: 1
TOTAL VIRTUAL MACHINES IN THE CLUSTER FOR WHICH CLX XP DEPENDENCY ADDED:
1
RELATED LINKS:
http://www.hp.com/go/clx
NAME:
Get-VMOnClusterSharedVolumeListForCLXXP
SYNOPSIS:
Gets the list of virtual machines which reside on a cluster shared volume.
SYNTAX:
Get-VMOnClusterSharedVolumeListForCLXXP [-CSVDiskName <String>
[<CommonParameters>]
DESCRIPTION:
This cmdlet gets the list of all virtual machines that reside on a CSV. If the CSV name is specified,
then the virtual machines that reside on that particular CSV are only listed. However, if CSV name
is not specified, then all the virtual machines that are residing on a CSV are listed with their
corresponding CSV names.
PARAMETERS:
-CSVDiskName <String>
Specifies the cluster shared volume name for which all the virtual machines will be listed.
Required?
false
Position?
named
Default value
Accept pipeline input?
false
Accept wildcard characters?
false
Cluster Extension Cmdlets for CSV and Virtual Machine Management
59
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,ErrorAction,
ErrorVariable, WarningAction, WarningVariable,OutBuffer and OutVariable.
For more information, see about_CommonParameters http://go.microsoft.com/fwlink/?
LinkID=113216
INPUTS:
Does not accept input object.
OUTPUTS:
Does not return object.
NOTES:
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>Get-VMOnClusterSharedVolumeListForCLXXP
In this example, the cmdlet lists all the virtual machines that reside on a cluster shared volume.
PS C:\> Get-VMOnClusterSharedVolumeListForCLXXP
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Starting with the steps to get virtual machines on cluster shared volumes
in the cluster.
Getting the virtual machine(s) created on all cluster shared volumes
in the cluster.
Virtual Machine Role
Cluster Shared Volume Name
New Virtual Machine
Cluster Disk 1
Total virtual machines in the cluster on cluster shared volumes: 1
Total virtual machines in the cluster: 1
Example 2
C:\PS>Get-VMOnClusterSharedVolumeListForCLXXP -CSVDiskName "Cluster
Disk 1"
In this example, the cmdlet lists all the virtual machines that reside on CSV "Cluster Disk 1"
PS C:\> Get-VMOnClusterSharedVolumeListForCLXXP -CSVDiskName "Cluster
Disk 1"
Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension
XP\log\CLXCmdlet.log
Starting with the steps to get virtual machines on cluster shared volumes
in the cluster.
Getting the virtual machine(s) created on CSV: Cluster Disk 1
Virtual Machine Role
Cluster Shared Volume Name
New Virtual Machine
Cluster Disk 1
Total virtual machines in the cluster on the provided cluster shared
volume: 1
Total virtual machines in the cluster: 1
60
HP XP Cluster Extension and CLI
RELATED LINKS:
http://www.hp.com/go/clx
Cluster Extension Cmdlets for CSV and Virtual Machine Management
61
4 HP XP Cluster Extension recovery procedures
XP disk pair states
“Disk pair states” (page 62) provides basic disk pair state information. The disk pair state transition
process is complex; see the Continuous Access and Continuous Access Journal documentation for
more information.
Table 3 Disk pair states
State
Description
P-VOL
The primary (master) disk of a disk pair
S-VOL
The secondary (slave) disk of a disk pair
SMPL
A disk with no pair affinity to any other disk
(This could be shown in pairdisplay outputs for your Continuous Access Software disk if you
accidentally exported the Business Copy environment variable HORCC_MRCF. In such a case,
the MU number field will not be empty.)
PAIR
The disk is either a primary disk or a secondary disk. If both (P-VOL and S-VOL) disks are in PAIR
state, Continuous Access Software updates the secondary disk based on the primary disk.
If you see only one disk in PAIR state (while the second disk is in another state), one of the following
has occurred:
• The pair affinity on only one site of the disk pair was deleted.
• A takeover command has been invoked on the secondary site, while no data has been written
to the primary site and the Continuous Access link was down.
• A takeover command has been invoked on the primary site with the fence level configured to
DATA to release the fenced disk, while the Continuous Access link was down. (The secondary
disk would stay in PAIR state.)
PSUS
The pair affinity has been manually suspended or a takeover operation has been invoked on the
secondary site with the fence level configured to NEVER. (In this case, the secondary disk would
have the state SSUS-SSWS.)
SSUS
The pair affinity has been manually suspended or a takeover operation has been invoked on the
secondary site. In this case, the secondary disk would have the state SSWS if you invoke
pairdisplay with the –fc option. In fence level ASYNC, the disk could also show PFUL or
PFUS when using the –fc option.
SSUS SSWS
Only the secondary disk could show SSUS. With the –fc option of pairdisplay, you can
check whether somebody manually suspended the pair or a takeover command had been invoked.
A prior takeover command is indicated by the SSWS state. In this case, the secondary disk is
mandatory and a resynchronization can be done only from the S-VOL site.
PSUE
The disk is in a failure mode. Either the Continuous Access link is down, or the disk must be
replaced.
PDUB
The disk is in a failure mode. Either the Continuous Access link is down, or the disk must be
replaced. This is a special state of PSUE. If you have configured several disks into a LUSE
configuration, where several LDEVS are combined to create an extended size disk and one or
more disks are in an error condition, this state will be shown.
PFUL
This state is used to indicate that a threshold of the side file area in the disk array cache has been
reached. This state can be seen with fence level ASYNC only. See the Continuous Access
documentation for more information.
PFUS
This state is used to indicate that the side file is full and the disk array was not able to transfer
the cache content to the remote disk array for a certain time. The disk pair has been suspended
to continue processing host I/O. This state can be seen with fence level ASYNC only. See the
Continuous Access documentation for more information.
62
HP XP Cluster Extension recovery procedures
Recovery sequence
To recover from a server or Continuous Access link failure:
1. Start the RAID Manager instances on both local and remote servers:
set HORCMINST=instance_number
HORCMSTART instance_number
2.
Gather general pair status information:
pairdisplay –g device_group
3.
Display the pair status information after a failed swap-takeover (the S-VOL state is SSWS):
pairdisplay –g device_group –fc
4.
To recover from these states, invoke the following command from the S-VOL side:
pairresync –swaps –c 15 –g device_group
If the pair needs to be used on the old primary side, the following commands must be invoked
from the primary side:
pairresync –swapp –c 15 –g device_group
horctakeover –g device_group
5.
Display the pair status information after a P-VOL takeover (local P-VOL PSUS; remote S-VOL
PAIR):
pairdisplay –g device_group –fc
To recover from these states, invoke the following command from the P-VOL side:
pairresync –c 15 –g device_group
CAUTION:
The application must be shut down and the file systems unmounted before a fenced disk in
fence level DATA can be set in read/write mode again. After the P-VOL takeover, the file
system must be checked before it can be mounted. Any other recovery procedure could lead
to unrecoverable file systems.
•
If a horctakeover command results in S-VOL, or P-VOL becomes SMPL and none of
the disks in the device/copy group has been written to, you can recover from the situation
by splitting the remaining P-VOL or S-VOL to SMPL:
pairsplit [[-S] | [-R]] -g device_group
After splitting the pair, the pair can be re-created without copying its content using:
paircreate -nocopy –c 15 -f fence_level -g device_group -v [[r] |
[l]]
•
If a horctakeover command results in S-VOL, or P-VOL becomes SMPL and data was
written to one of the disks in the device/copy group, you can recover from the situation
by splitting the remaining P-VOL or S-VOL to SMPL:
pairsplit [[-S] | [-R]] -g device_group
After being split, the pair can be re-created with a full copy using:
paircreate –c 15 -f fence_level -g device_group -v [[r] | [l]]
To ensure that a certain pair state has been established, invoke the event wait command:
pairevtwait -g device_group -t time_to_wait -s pair_state
Recovery sequence
63
5 User configuration file and HP XP Cluster Extension objects
Objects (also called properties in this document) define the disk array environment and
failover/failback behavior. Information comes directly from the cluster software, indirectly from the
disk array through RAID Manager, and from a configuration file created by users. This file describes
the dependencies between application services and RAID Manager device/copy groups in one
file for all application services in the cluster.
The user configuration file provides customized and default values for supported parameters. You
can specify all customizable HP XP Cluster Extension objects in the file, and a copy must exist on
all nodes using HP XP Cluster Extension. HP XP Cluster Extension uses the information objects to
match current disk states and configuration parameters and to invoke actions, including preparing
disks to be activated or stopping the application startup.
User configuration file location
The user configuration file is placed in the configuration directory
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\conf.
For more information, see:
•
“Basic configuration example” (page 75)
•
“Creating and configuring the user configuration file” (page 48)
MSFC
HP XP Cluster Extension integration with MSFC does not require a user configuration file when the
standard environment for HP XP Cluster Extension is used. The HP XP Cluster Extension objects that
are integrated with MSFC can be configured as resource-specific properties in the cluster software.
For more information, see “Configuring HP XP Cluster Extension resources” (page 21).
File structure
The configuration file consists of a COMMON section and an APPLICATION section. These sections
are distinguished by control tags. HP XP Cluster Extension uses the following objects as control
tags:
•
COMMON
•
APPLICATION
Objects have one of the following formats:
tag
A definition of an object; for example, COMMON or APPLICATION
integer
A number; for example, a timeout value
string
A name, which can include alphabetic and numeric characters and underscores; for example, an
application startup value
list
A list of space-separated strings, for example, a list of host names (lists of numbers are stored as lists
of strings)
Text that is a comment starts with the pound (#) symbol and continues until the end of the line.
Comments can start on a new line or be part of a line specifying an object.
64
User configuration file and HP XP Cluster Extension objects
Specifying object values
When using the default configuration, you must provide values for the following objects:
•
DeviceGroup: A RAID Manager device/copy group
•
DC_A_Hosts: A list of the cluster nodes in data center A
•
DC_B_Hosts: A list of the cluster nodes in data center B
•
RaidManagerInstances: A list of RAID Manager instances that HP XP Cluster Extension can
use to communicate with the disk array
•
XPSerialNumbers: The serial numbers of the primary and secondary disk arrays
You do not need to change the default settings unless you want to change the degree of protection
for your paired disks. If you change an object, you may need to change additional related objects.
For example, if you change the FenceLevel object to DATA, you might need to change the
DataLoseMirror object.
Objects are supported according to the requirements or capabilities of the cluster software, as
shown in “Cluster software supported objects” (page 65).
Table 4 Cluster software supported objects
System
Object
CLI
MSFC
COMMON
•
•
LogDir
•
•
LogLevel
•
•
SearchObject
•
APPLICATION
•
•
ApplicationDir
•
•
ApplicationStartup
•
•
AsyncTakeoverTimeout
•
•
AutoRecover
•
•
BCEnabledA
•
•
BCEnabledB
•
•
BCMuListA
•
•
BCMuListB
•
•
BCResyncEnabledA
•
•
BCResyncEnabledB
•
•
BCResyncMuListA
•
•
BCResyncMuListB
•
•
DataLoseDataCenter
•
•
DataLoseMirror
•
•
DC_A_Hosts
•
•
ClusterNotifyCheckTime
ClusterNotifyWaitTime
User configuration file location
65
Table 4 Cluster software supported objects (continued)
System
Object
CLI
MSFC
DC_B_Hosts
•
•
DeviceGroup
•
•
FenceLevel
•
•
Filesystems
•
•
JournalDataCurrency
•
•
PostExecCheck
•
•
PostExecScript
•
•
PreExecScript
•
•
RaidManagerInstances
•
•
FastFailbackEnabled
LocalDCLMForNonPAIRDG
ResyncMonitor
•
ResyncMonitorAutoRecover
•
ResyncMonitorInterval
•
ResyncWaitTimeout
•
•
Vgs
•
•
XPSerialNumbers
•
•
StatusRefreshInterval
• Supported
COMMON objects
The COMMON section is used to set the environment of HP XP Cluster Extension.
The COMMON tag can appear in the configuration file only once. The COMMON object does
not require any value.
Objects of the type COMMON can appear only one time. Those objects must be placed after the
COMMON tag in the configuration file.
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
66
Format
String
Description
(Optional) Defines the path to the HP XP Cluster Extension log file.
Default
value
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log
User configuration file and HP XP Cluster Extension objects
LogLevel
Format
String
Description
(Optional) Defines the logging level used by HP XP Cluster Extension.
Valid values
error: Logs only error messages for events that are unrecoverable.
warning: Logs error messages and warning messages for events that are
recoverable.
info (default): Logs error messages, warning messages, and additional information,
such as disk status.
debug: Logs error messages, warning messages, info messages, and messages that
report on execution status; useful for troubleshooting.
NOTE: This behavior is observed only for VM Management functionality. If the LogLevel is
changed, then the cluster service must be restarted on that specific cluster node to reflect the
modified LogLevel.
APPLICATION objects
The APPLICATION section defines the failover and failback behavior of HP XP Cluster Extension
for each application service. APPLICATION is a multitag that can appear in the configuration file
for each application service using HP XP 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 the COMMON
objects, the APPLICATION objects have predefined default values.
HP XP Cluster Extension uses the following rules to define objects:
•
If you use the default value, you do not have to specify the object.
•
HP XP Cluster Extension uses objects depending on the setting of other objects. For example,
if you set the FenceLevel object to DATA, HP XP Cluster Extension uses the values specified for
the DataLoseMirror or DataLoseDataCenter object. However, these objects are ignored if the
FenceLevel object is set to NEVER.
•
The pre-execution and post-execution functions in HP XP Cluster Extension are not processed
if the associated object values are empty. (This is the default setting.)
When setting APPLICATION object values:
•
Use a user configuration file for the CLI.
•
Use the Failover Cluster Management GUI (Windows Server 2008/2008 R2/2012/2012
R2) for MSFC.
APPLICATION objects
This section describes the available APPLICATION objects for HP XP Cluster Extension.
APPLICATION
Format
Tag
Description
Distinguishes between general and application-specific objects. Specify the name
of the application service. The format of its value is equivalent to a string value.
ApplicationDir
Format
String
Description
Specifies the directory where HP XP Cluster Extension searches for application-specific
files, such as the force flag or online file.
APPLICATION objects
67
If ApplicationDir is set to a nonexistent drive and PairResyncMonitor is not enabled,
HP XP Cluster Extension is unable to create the online file and cannot put the resource
online.
Windows
If ApplicationDir is not set, HP XP Cluster Extension uses the local %HPCLX_PATH%
values as defined in the registry.
Default
values
%HPCLX_PATH%
Files
resource_name.forceflag
resource_name.online
If specified in a user configuration file, resource_name is the value of the
APPLICATION tag; otherwise, resource_name is the value of the HP XP Cluster
Extension resource name.
ApplicationStartup
Format
String
Description
(Optional) Specifies where a cluster group should be brought online.
The ApplicationStartup object can be customized to determine whether an application
service starts locally or is transferred back to the remote data center (if possible) to
start immediately without waiting for resynchronization. This object is used only if
an application service has already been transferred to the secondary site and no
recovery procedure has been applied to the disk set (the disk pair has not been
recovered and is not in PAIR state). This process is considered a failback attempt
without prior disk pair recovery.
HP XP Cluster Extension can detect the most current copy of your data based on the
disk state information. If HP XP Cluster Extension detects that the remote disk array
has the most current data, it orders a resynchronization of the local disk from the
remote disk, or it stops the startup process to enable the cluster software to fail back
to the remote disk array.
If a resynchronization is ordered, HP XP Cluster Extension monitors the progress of
the copy process. If the application service was running on a secondary disk array
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.
MSFC
If the ApplicationStartup resource property is set to FASTFAILBACK and the
FailoverThreshold value is set to a number higher than the current number of clustered
systems for the service or application, the service or application will restart on
configured nodes until one of the following conditions is met:
•
The resource is brought online in the remote data center.
•
The resource failed because the FailoverThreshold value has been reached.
•
The resource failed because the FailoverPeriod timeout value has been reached.
CAUTION: Disable subsequent automated failover procedures for recovery failback
operations.
Valid values
FASTFAILBACK (default)
The cluster group is brought online in the remote data center (if possible) without
waiting for resynchronization. The application startup process is stopped locally and
68
User configuration file and HP XP Cluster Extension objects
HP XP Cluster Extension reports a data center error. Depending on the cluster
software, the application service cannot start on any system in the local data center,
and the cluster software transfers the application service back to the remote data
center. Use this value to provide the highest level of application service availability.
Depending on the value configured for the AutoRecover object, HP XP Cluster
Extension attempts to update the former primary disk based on the secondary disk
and swaps the personalities of the disk pair so that the local disk will become the
primary disk.
In a two-node cluster, this process does not work because the target failback system
is not available. In this case, the application service must be started manually, or
the ApplicationStartup object must be set to RESYNCWAIT.
In an HP XP Cluster Extension for MSFC integration, HP XP Cluster Extension can
detect when there is no target failback system available in the remote data center.
In this case, HP XP Cluster Extension behaves as if the ApplicationStartup resource
property is set to RESYNCWAIT.
RESYNCWAIT
The online local cluster group must wait until the disk status is PAIR. HP XP Cluster
Extension initiates a resynchronization of the local disk based on the remote disk.
The copy process is monitored; if no copy progress is made after a monitoring
interval expires, the copy process is considered failed and HP XP Cluster Extension
returns a global error. If RESYNCWAIT has been specified for the ApplicationStartup
object, the ResyncWaitTimeout object must be specified, in case HP XP Cluster
Extension should wait for resynchronization changes for more or less than 90
seconds, which is the default.
AsyncTakeoverTimeout
Format
Integer
Description
(Optional) Specifies the horctakeover command timeout in seconds. Must be
adjusted based on disk mirroring link speed.
This object is used only if the FenceLevel object value is ASYNC.
The takeover operation for fence level ASYNC (Continuous Access) offers the option
to stop the data transfer process after a specified time value. This is used to allow
access to the remote copy if the data transfer process is stopped due to a Continuous
Access link failure. All data that has been copied up to the moment the timeout value
is reached is consistent and available to access at the secondary site.
CAUTION: Measure or calculate the full disk array cache copy time to use the
gathered information for the AsyncTakeoverTimeout object. After a takeover command
has been invoked, the Continuous Access software copies the side file area residing
in the disk array cache to the site where the takeover command has been issued
(the secondary disks). The side file area cannot exceed the installed cache size. The
maximum time for the AsyncTakeoverTimeout object is the time to fully copy the
amount of cache size data. The takeover timeout value is used to terminate the copy
process to provide access to the secondary disks; for example, if all links or the
primary disk array are unavailable to copy the side file area. The copy time depends
on the performance of the Continuous Access Software link between your sites. The
takeover or resynchronization operation could take longer than the timeout value
for application service startup in the cluster software. The application service startup
might fail in this case. However, the takeover or resynchronization command will
continue in the background.
APPLICATION objects
69
Default
value
3600
AutoRecover
Format
String
Description
(Optional) Recovers a suspended or deleted disk pair when the resource is brought
online at application service startup time.
If the AutoRecover object is set to YES, HP XP Cluster Extension will try to
resynchronize the remote disk at application startup time. HP XP Cluster Extension
will ignore the return code of the resynchronization command and allow access to
the disk ensuring highest application availability.
If the resynchronization attempt fails, HP XP Cluster Extension will not fail. The internal
logic will first apply the concurrency and consistency rules to allow access to the
disk set.
If you configure fence level DATA for the device/copy group and set the FenceLevel
object to DATA, the AutoRecover object will change HP XP Cluster Extension's
behavior. HP XP Cluster Extension will attempt to re-establish the PAIR state and wait
for the PAIR state before it allows access to the disk. If the resynchronization or
takeover process fails, HP XP Cluster Extension returns a global error.
Valid values
YES (default)
NO
BCEnabledA
Format
String
Description
(Optional) Enables rolling disaster protection for data center A.
Valid values
YES
NO (default)
BCEnabledB
Format
String
Description
(Optional) Enables rolling disaster protection for data center B.
Valid values
YES
NO (default)
BCMuListA
Format
List
Description
(Optional) Space-separated list defines the MU number of the Business Copy disk
pairs in data center A.
BCMuListB
Format
List
Description
(Optional) Space-separated list defines the MU number of the Business Copy disk
pairs in data center B.
BCResyncEnabledA
70
Format
String
Description
(Optional) Enables automatic resynchronization of Business Copy disk pairs in data
center A. The automatic resynchronization function is supported only when the split
User configuration file and HP XP Cluster Extension objects
Business Copy pair is located in the same data center where HP XP Cluster Extension
is started.
Valid values
YES
NO (default)
BCResyncEnabledB
Format
String
Description
(Optional) Enables automatic resynchronization of Business Copy disk pairs in data
center B. The automatic resynchronization function is supported only when the split
Business Copy pair is located in the same data center where HP XP Cluster Extension
is started.
Valid values
YES
NO (default)
BCResyncMuListA
Format
List
Description
(Optional) Space-separated list defines the MU number of the Business Copy disk
pairs in data center A.
BCResyncMuListB
Format
List
Description
(Optional) Space-separated list defines the MU number of the Business Copy disk
pairs in data center B.
ClusterNotifyCheckTime
Format
Integer
Description
Specifies how often HP XP 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 XP Cluster Extension will monitor for VM live
migration state changes.
Default
value
5 seconds
DataLoseDataCenter
Format
String
Description
(Optional) Specifies whether a resource should be brought online while the disk pair
is (or will be) suspended or deleted and there is no connection (Continuous Access
and IP network) to the remote data center.
Used only if the FenceLevel object value is DATA.
RAID Manager is able to access its remote peer to invoke takeover actions for
Continuous Access device/copy groups. It is also able to invoke a swap-takeover
operation of the device/copy group from the secondary site. If no configured remote
RAID Manager instance replies to a request of the local RAID Manager instance
(remote status EX_ENORMT), all network connections between the local and the
APPLICATION objects
71
remote data center are considered DOWN. If the swap-takeover operation leads
to a suspended state for the device/copy group, the Continuous Access links are
considered DOWN.
Because redundant networks and Continuous Access links are necessary to build a
disaster-tolerant environment, this situation can be considered as a data center
failure. The DataLoseDataCenter object is used to allow/prohibit automatic
application service startup in this particular case.
The combination of setting the DataLoseMirror object to YES and the
DataLoseDataCenter object to NO are contradictory.
Valid values
YES (default)
NO
DataLoseMirror
Format
String
Description
(Optional) Specifies whether a resource should be brought online while the disk pair
is suspended or deleted.
Used only if the FenceLevel object value is DATA and local and remote disk status
information can be gathered. If the remote disk state information is not available
(remote state EX_ENORMT), the setting of the DataLoseDataCenter object will be
used.
Depending on the value configured for the AutoRecover object, HP XP Cluster
Extension will attempt to recover the PAIR state for the device/copy group. HP XP
Cluster Extension waits until the PAIR state has been established. If this operation
fails, HP XP Cluster Extension returns a global error. Because the DATA fence level
ensures no loss of concurrency, manual intervention is required to recover the PAIR
state. The PAIR state must be re-established for all disks in the device/copy group
before you can start the application service.
The combination of setting the DataLoseMirror object to YES and the
DataLoseDataCenter object to NO are contradictory.
Valid values
YES
NO (default)
DC_A_Hosts (Required)
Format
List
Description
This space-separated list defines the cluster nodes in data center A.
DC_B_Hosts (Required)
Format
List
Description
This space-separated list defines the cluster nodes in data center B.
DeviceGroup (Required)
Format
String
Description
RAID Manager device/copy group, containing the application service disk set.
Files
\winnt\horcmX.conf %system_root%\horcmX.conf
where X is the RAID Manager instance number.
FenceLevel
Format
72
String
User configuration file and HP XP Cluster Extension objects
Description
(Optional) The FenceLevel object specifies the fence level configured for the device/
copy group. HP XP Cluster Extension checks whether the current fence level reported
by the disk array is the same as the configured (expected) fence level. This object
is also used to make sure your configurations are supported based on consistency
considerations. Different failover and recovery procedures are used for different
fence levels.
If you change the FenceLevel object value, also review the values of these objects:
DataLoseMirror, DataLoseDataCenter, and AsyncTakeoverTimeout.
Valid values
DATA
NEVER (default)
ASYNC (This is for Journal fence level).
Format
List
Description
Space-separated list of file systems.
JournalDataCurrency
Format
String
Description
(Optional) Specifies whether a resource should be brought online while there could
still potentially be a large amount of data on P-VOL Journal that cannot be transmitted
to the secondary site due to the Continuous Access link being down.
Used only if the FenceLevel object value is ASYNC and the local device is an S-VOL.
HP XP Cluster Extension checks whether the current Continuous Access link status is
>0 using the minimum active paths (MINAP) value returned by the RAID Manager
pairvolchk command. If the minimum active paths equals 0, this indicates that
the Continuous Access link is unavailable and that any data still located in the
primary journal will not be replicated to the secondary volume. If JournalDataCurrency
is set to YES then HP XP Cluster Extension will not perform the takeover operation
and will not allow the application to access the data.
Valid values
YES (default)
NO
LocalDCLMForNonPAIRDG
Format
String
Description
Specifies whether a live migration operation within the local data center is
allowed when the device/copy group is not in PAIR state.
Set this property to YES to allow live migration operations in the local data
center when the device/copy group is not in PAIR state, the latest data is in
the local data center, and the HP XP Cluster Extension resource can come
online.
For example, if the device/copy group state is PVOL_COPY in the local data
center and SVOL_COPY in the remote data center, setting this property to YES
allows you to perform live migration to nodes within the local data center.
Set this property to NO if you want to cancel live migration operations within
the local data center when the device/copy group is not in PAIR state.
APPLICATION objects
73
NOTE: Configure this parameter for each HP XP Cluster Extension resource
associated with the VM cluster resource and the corresponding application
cluster resource in the UCF file. If the VM group contains more than one HP
XP Cluster Extension resource, and you want to use this parameter, you must
set this parameter to the same value for each HP XP Cluster Extension resource.
If you do not set the parameter to the same value, this parameter will default
to a value of NO.
Valid values
YES
NO (default)
PostExecCheck
Format
String
Description
(Optional) The PostExecCheck object is used to configure HP XP Cluster Extension
to gather disk pair status information after the takeover procedure. This information
is 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 XP status information. The arguments passed to the post-executable
include only the local disk status if the PostExecCheck object is set to NO. See “Setting
up RAID Manager” (page 11).
Valid values
YES
NO (default)
PostExecScript
Format
String
Description
(Optional) Specifies an executable with its full path name to be invoked after the
takeover action or failover procedure.
PreExecScript
Format
String
Description
(Optional) Specifies an executable with its full path name to be invoked before
the takeover action or failover procedure.
RaidManagerInstances (Required)
Format
List
Description
A space-separated list of RAID Manager instances that HP XP Cluster Extension can
use to communicate with the disk array. The instance numbers must be the same
among all cluster systems. HP XP Cluster Extension can alternate between the specified
instances.
Files
%systemroot%\horcmX.conf
where X is the RAID Manager instance number.
ResyncMonitor
Format
String
Description
(Optional) Starts the pair/resync monitor to monitor the disk pair status and
resynchronize disk pairs if the ResyncMonitorAutoRecover attribute is set to YES.
Valid values
YES
NO (default)
74
User configuration file and HP XP Cluster Extension objects
ResyncMonitorAutoRecover
Format
String
Description
(Optional) Automatically recovers disk pairs states if the disk pairs are monitored
by the pair/resync monitor.
Valid values
YES
NO (default)
ResyncMonitorInterval
Format
Integer
Description
(Optional) Specifies the monitor interval (in seconds) that the pair/resync monitor
checks the disk pair status.
Default
value
60
ResyncWaitTimeout
Format
Integer
Description
(Optional) Specifies the timeout value (in seconds) for a disk pair resynchronization.
It may take some time to resynchronize disks. The timer times out if there is no change
in the percentage value of the copy status for the device/copy group in the specified
time interval. The timeout value is used if the ApplicationStartup object is set to
RESYNCWAIT.
Default
value
90
StatusRefreshInterval
Format
Integer
Description
Specifies how often HP XP Cluster Extension will gather disk array information.
Default
value
300 seconds
XPSerialNumbers (Required)
Format
List
Description
A space-separated list of at least two serial numbers must be specified: the serial
numbers of the primary and secondary disk arrays. HP XP Cluster Extension checks
whether the local disk array is contained in this list. Serial numbers of the disk arrays
of the connected cluster nodes (at least two).
Basic configuration example
The following is an example of a UCF.cfg file:
#This is the XP Cluster Extension User Configuration File (UCF.cfg).
#The COMMON tag specifies the configuration for the
#XP Cluster Extension core environment
COMMON
LogLevel
info
#default (not necessary)
APPLICATION
sap
#the application service
Vgs
sapdatavg saptmpvg
#the volume groups (not necessary)
Filesystems
/sapdata /saptmp
#the filesystems
DeviceGroup
sapdg
#RM dev group for the app service
RaidManagerInstances 22
#RM instance number for dev group
DC_A_Hosts
host1a host2a
#Data center A
Basic configuration example
75
DC_B_Hosts
76
host3b host4b
User configuration file and HP XP Cluster Extension objects
#Data center B
6 Advanced HP XP Cluster Extension configuration
This chapter describes advanced HP XP Cluster Extension configuration procedures.
Configuring the HP XP Cluster Extension for HP XP Continuous Access 3DC
environment
XP Cluster Extension supports XP Continuous Access 3DC multi-target with delta resync configuration.
Figure 7 (page 77) shows the sample XP Continuous Access 3DC multi-target with delta resync
configuration.
Figure 7 XP Continuous Access 3DC multi-target with delta resync configuration
Perfom the following steps to configure the CLX DR solution:
1. Configure an XP CLX resource with device group between the primary and the secondary
data center. For example, create a CLX resource for the device group DG12 shown in Figure 7
(page 77). See “Configuring HP XP Cluster Extension resources” (page 21) for information
on CLX resource configuration. This configuration is similar to the CLX resource configuration
for 2DC environment between the primary and the secondary datacenters. This step is already
performed if CLX is configured in the 2DC environment and then the configuration is extended
to the 3DC environment.
2. Copy the ucf.cfg file located in %HPCLX_PATH%\sample to %HPCLX_PATH%\conf
directory.
Configuring the HP XP Cluster Extension for HP XP Continuous Access 3DC environment
77
3.
Open the ucf.cfg and make the following entries:
#Sample 3DC configuration
APPLICATION CLX_RESOURCE_NAME
# package/service/cluster group
test_application/CLX resource name
Enable3DC yes
# Enable 3DC : yes|no
DC1-DC3DeviceGroup DG13
# Raid manager device group between DC1 and DC3
DC2-DC3DeviceGroup DG23
# Raid manager device group between DC2 and DC3
DC1-DC2MUNumber 0
# Raid manager mirror unit number used for device group
between DC1 and DC2
DC1-DC3MUNumber 1
# Raid manager mirror unit number used for device group
between DC1 and DC3
DC2-DC3MUNumber 2
# Raid manager mirror unit number used for device group
between DC2 and DC3
3DCSyncPreference 0
# 3DC configuration preference. 0 : Multi-Target , 1 : Multi-Hop, 2:
Multi-Target with better CLX resource online time.
#3DCResynWaitTimeout
# The number of seconds CLXRUN should wait to initiate the data resync
to third data center.
Where,
Application: Name of the CLX resource name for which 3DC needs to be enabled.
Enable3DC: If the value is yes then 3DC will be enabled for this application, otherwise 3DC
operation will be disabled.
DC1-DC3DeviceGroup: Name of the RAID manager CAJ device group between the primary
and the secondary data center.
DC2-DC3DeviceGroup: Name of the RAID manager CAJ device group between the secondary
and the remote data center.
DC1-DC2MUNumber: RAID manager mirror unit number used for the CA-Sync
DC1-DC2DeviceGroup.
DC1-DC3MUNumber: RAID manager mirror unit number used for the CAJ
DC1-DC3DeviceGroup.
DC2-DC3MUNumber: RAID manager mirror unit number used for the CAJ
DC2-DC3DeviceGroup.
3DCSyncPreference: This flag allows you to set your preferred 3DC configuration on
application failover.
If 3DCSyncPreference is set to 1, multi-hop configuration is given preference. But after
application failover, if multi-target configuration is maintained, then this configuration is not
changed to multi hop configuration even though the 3DCSyncPreference is set to 1.
If 3DCSyncPreference is set to 2, multi-target configuration is given preference. This option
is preferred instead of 0. However, if full resync is initiated to the third datacenter during
application movement across the data centers, then 3DCSyncPreference value must be
selected as 0.
If 3DCSyncPreference is set to 0, multi-target configuration is given preference. If you select
this option, ensure that Pending timeout (For the CLX resource in MSFC) is greater than
or equal to 180 seconds.
If 3DCSyncPreference parameter is not configured, CLX assigns 0 as the default value.
If CLX is unable to keep the preferred configuration due to reasons such as CA link failure
and so on, it shifts to the non preferred configuration.
78
Advanced HP XP Cluster Extension configuration
If you have to change the default 3DCSyncPreference, add this parameter with appropriate
value under the application tag in ucf.cfg file.
For example, if you make the following configuration in ucf.cfg, then preference is given
to multi-hop configuration.
3DCSyncPreference 1
, 1 : Multi-Hop
#3DC configuration preference. 0 : Multi-Target
NOTE: For CLX resource configuration that is integrated with the MS failover cluster, the
configuration is done through CLX configuration tool and the CLX resource configuration tool as
explained in Step 1. For 3DC configuration only, the UCF needs to be configured as explained
in Step 3.
For clxrun utility that is a non clustered CLI component of CLX (as mentioned in “clxrun” (page 49)),
all CLX configurations are done using the UCF file. For 3DC configuration also, UCF needs to be
configured as explained in Step 3. For clxrun utility, CLX provides an extra parameter called
3DCResyncWaitTimeout that can be configured to a value in the UCF.
3DCResyncWaitTimeout: Number of seconds that clxrun must wait while trying to initiate the
data resync to the remote data center. If the clxrun fails to initiate the data sync operation to the
third datacenter by this time, then you need to initiate the data resync operation to the third data
center manually. If this parameter is not configured, then CLX makes only one attempt to sync the
data to the third data center.
For information on CLX 3DC solution configuration, see HP XP Cluster Extension Disaster Recovery
solution for XP CA 3DC multi-target with Delta resync configuration whitepaper at www.hp.com/
storage/whitepapers or https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=CLX .
Implementing rolling disaster protection
To implement rolling disaster protection, create Business Copy disk pairs for the local Continuous
Access disks.
•
Create the Business Copy disk pairs using the paircreate command with the –m noread
option. This option ensures that Business Copy disks are unavailable to other services and
reserved for rolling disaster protection only.
•
Map the Business Copy S-VOLs to a backup server, not to the local cluster node. When HP
XP Cluster Extension suspends the Business Copy pairs, they become available to the local
server, which could result in duplicated volumes, disk group IDs, or signatures.
CAUTION: You must ensure that at least one Business Copy disk pair is in PAIR state. If rolling
disaster protection is enabled and none of the Continuous Access mirrored disk pairs have a
Business Copy disk pair that is in PAIR state, HP XP Cluster Extension returns a global error, and
you will not be able to activate the application service.
You can use forceflag to start the application service. See “Enabling write access regardless
of disk pair state” (page 82). In this case, HP XP Cluster Extension disables rolling disaster protection.
Using RAID Manager with rolling disaster protection
Rolling disaster protection does not require that you define Business Copy disk pairs in the RAID
Manager horcmX.conf files. HP XP Cluster Extension uses the MU number to monitor and control
associated Business Copy pairs. You must create a RAID Manager configuration file to control the
Business Copy disk pairs that are outside HP XP Cluster Extension control.
HP XP Cluster Extension Software cannot suspend Business Copy disk pairs on the remote disk
array in the remote data center if the RAID Manager instance in the remote data center is not
running or not reachable.
Implementing rolling disaster protection
79
Setting HP XP Cluster Extension objects to enable rolling disaster protection
To enable rolling disaster protection with Business Copy, set the BCEnabledA and BCEnabledB
objects for data centers A and B. When these objects are set to YES, rolling disaster protection is
enabled and HP XP Cluster Extension checks whether the configured Business Copy disk pairs are
in PAIR state. Before initiating the resynchronization operation, HP XP Cluster Extension suspends
specified Business Copy disk pairs that are in PAIR state. For information on setting HP XP Cluster
Extension objects, see “User configuration file and HP XP Cluster Extension objects” (page 64).
When using rolling disaster protection, note the following:
•
If the BCEnabledA and BCEnabledB objects are set to YES, you must configure specific Business
Copy disk pairs using MU numbers. The MU number defines one of the many disk pair
relationships you can create with Business Copy disk pairs. You can specify as many MU
numbers as the Business Copy software supports. Disk pair MU numbers are specified by the
BCMuListA and BCMuListB objects for data centers A and B.
•
To enable resynchronization of Business Copy disk pairs that have been split by HP XP Cluster
Extension, use the BCResyncEnabledA and BCResyncEnabledB objects for data centers A and
B.
•
HP XP Cluster Extension maintains a list of all associated Business Copy disk pairs that were
in PAIR state before a resynchronization attempt. If pairs were suspended, HP XP Cluster
Extension automatically resynchronizes those disk pairs after the Continuous Access remote
mirrored disk pairs have been paired. This feature supports automatic resynchronization of
locally split Business Copy disk pairs only. You must specify MU numbers for resynchronization
by using the BCResyncMuListA and BCResyncMuListB objects for data centers A and B.
Setting automatic recovery for rolling disaster protection
If the AutoRecover object is set to YES, HP XP Cluster Extension automatically resynchronizes the
Continuous Access disk pairs to update the remote disks. If rolling disaster protection is also enabled,
it suspends the Business Copy disk pair that is attached to the remote Continuous Access disk.
If the remote RAID Manager instance is not running or cannot be reached, the remote Business
Copy disk pair cannot be suspended. If this occurs, HP XP Cluster Extension continues the application
service activation without automatic resynchronization of the Continuous Access disk pair and
without the suspending of the Business Copy disk pair. In this case, the Continuous Access disk
pair must be recovered manually.
Using the pair/resync monitor with rolling disaster protection
If the ResyncMonitor object is set to YES, the pair/resync monitor does not use Business Copy pairs
to recover suspended or failed Continuous Access disk pairs.
To protect the remote volume of an out-of-sync Continuous Access disk pair against rolling disasters,
use the pair/resync monitor's default settings. Resynchronize the Continuous Access disk pair
manually after splitting off the Business Copy disk pair.
Restoring server operation for rolling disaster protection
Rolling disaster protection automatically recovers the PAIR state of the Continuous Access disk pair
of an application service. Before you fail over (or fail back) an application service from one data
center to the other, you must restore the server operation. After you restart the server, also start the
RAID Manager instance used to manage the Continuous Access disk pairs on those servers. This
enables rolling disaster protection to work correctly during a recovery failover/failback operation.
“Disaster-tolerant configuration with rolling disaster protection” (page 81) depicts a fully configured
HP XP Cluster Extension environment that uses rolling disaster protection. The Business Copy disk
pairs are specified as 0 in the HP XP Cluster Extension BCMuListA and BCMuListB objects. See
“APPLICATION objects ” (page 67) for more information about these objects.
80
Advanced HP XP Cluster Extension configuration
Figure 8 Disaster-tolerant configuration with rolling disaster protection
Monitoring and resynchronizing device/copy groups
The pair/resync monitor can either only monitor or both monitor and resynchronize the state of
the RAID Manager device/copy group for an application service.
CAUTION: If the application service stops, the cluster software or your customized solution must
be able to stop the monitoring or resynchronization utility. Without this ability, the use of the
pair/resync monitor is not supported. HP recommends that you disable application service failover
during a disk pair recovery (resynchronization). When the pair/resync monitor is enabled, HP XP
Cluster Extension takes immediate action to recover any reported suspended disk pair. If, at any
time, the resynchronization process is running on both disk array sites, data corruption might occur.
Turn the pair/resync monitor (clxchkd) on or off using the ResyncMonitor object. For information
on setting HP XP Cluster Extension objects, see “User configuration file and HP XP Cluster Extension
objects” (page 64).
Monitoring and resynchronizing device/copy groups
81
If the ResyncMonitorAutoRecover object is set to YES, the monitor tries to resynchronize the remote
disk based on the local disk. Resynchronization occurs only if the disks are in a P-VOL/S-VOL or
S-VOL/P-VOL relationship. If one or both disk pairs are in the SMPL state or the device/copy group
state is mixed, automatic resynchronization is not attempted. The ResyncMonitorAutoRecover object
set to YES is supported only if the minimum disk array firmware version is 01-11-xx (XP512/XP48)
or 21.01.xx (XP128/XP1024), and the minimum RAID Manager version is 01.04.00.
The monitor interval is specified with the ResyncMonitorInterval object. Do not set the monitor
interval below the RAID Manager timeout parameter (HORCM_MON in the horcmX.conf file).
If the link for the device/copy group is broken, the pair/resync monitor notifies you by using the
Event Log . The monitor recognizes a broken link only when data is to be written to disk; otherwise,
the data is the same on the primary and secondary disk, and the device/copy group state is
reported as PAIR.
Enabling write access regardless of disk pair state
The force flag forces HP XP Cluster Extension to skip the internal logic and enables write access
to the local volume, regardless of the disk pair state. This flag can be set when you are sure that
the local volume contains the latest data, even though a previous application service startup process
failed because HP XP Cluster Extension discovered a disk pair status that could not be handled
automatically.
To use the force flag:
1. Ensure that the application service is not running.
2. Create a file called application_name.forceflag in the directory specified by the
ApplicationDir object.
3. Start the application service. HP XP Cluster Extension removes the forceflag file after
detecting it.
You cannot use the force flag if the local disk state is S-VOL_COPY, which indicates that a copy
operation is in progress. When a copy operation is in progress, a disk cannot be activated, and
HP XP Cluster Extension returns a global error.
Using the force flag does not enable the automatic recovery features of HP XP Cluster Extension.
After using the force flag, you must recover the suspended or broken disk pairs using RAID Manager
commands as described in “Recovery sequence” (page 63).
Executing programs before and after an HP XP Cluster Extension takeover
HP XP Cluster Extension can invoke other programs, such as Perl scripts, before or after an HP XP
Cluster Extension takeover. These programs can be any executable, and must be able to provide
return codes to HP XP Cluster Extension. If the programs add significant execution time to the
application service startup, the timeout values for the startup must be adjusted in the cluster software.
HP XP Cluster Extension transfers information as command-line arguments to the pre-execution and
post-execution programs. Pre-executables and post-executables must be specified by full path in
the PreExecScript and PostExecScript objects. If no executable is specified (empty value for the
object), no preprocessing or postprocessing, is done.
The pre-executable and post-executable path names can include spaces and environment variables.
The environment variables will be expanded to form the full path name for the executable.
To use Perl scripting with MSFC, the Perl script must be called from a Windows batch file; therefore,
two scripts are needed: the calling batch file and the called Perl script.
In the following example, c:\tmp\preExec.bat is the calling batch file, and
c:\tmp\preExec.pl is the called Perl script:
Windows batch file: c:\tmp\preExec.bat
@echo off
c:\perl\bin\perl.exe c:\tmp\preExec.pl %3 %4 %5
exit /B %ERRORLEVEL%
82
Advanced HP XP Cluster Extension configuration
Arguments
The
1.
2.
3.
following arguments are transferred to the scripts in this order:
Name
RaidManagerInstances
DeviceGroup
The device and/or copy group names.
4.
local device/copy group state (check)
Pre-executable status before failover and post-executable status after failover
5.
local device/copy group state (display)
Pre-executable status before failover and post-executable status after failover
IMPORTANT:
6.
An empty string is returned if parameter #5 is not SSWS, PSUE, or PDUB.
remote device/copy group state (check)
Pre-executable status before failover and post-executable status after failover
7.
remote device/copy group state (display)
Pre-executable status before failover and post-executable status after failover
IMPORTANT:
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
An empty string is returned if parameter #7 is not SSWS, PSUE, or PDUB.
current fence level
disk array serial numbers (local)
reserved
reserved
disk array firmware version (local)
RAID Manager version (local)
application directory path (ApplicationDir object)
log file location (LogDir object)
DC_A_Hosts node names
DC_B_Hosts node names
Pre-executable return codes
Pre-executables must give a return code. These return codes determine whether a takeover function
must be called.
0
PRE_OK_TAKEOVER
Pre-executable OK and takeover action allowed.
1
PRE_ERROR_GLOBAL
Pre-executable failed; no takeover; stop application service cluster-wide.
2
PRE_ERROR_DC
Pre-executable failed; no takeover; stop application service in this data center.
3
PRE_ERROR_LOCAL
Pre-executable failed; no takeover; stop application service on this system.
4
PRE_ERROR_TAKEOVER
Pre-executable failed; takeover action allowed.
5
PRE_OK_NOTKVR_NOPST
Executing programs before and after an HP XP Cluster Extension takeover
83
Pre-executable ok; no takeover; no post-exec.
CAUTION:
If the pre-execution program returns 1, 2, 3, or 5, a post-executable will not be executed. If a
takeover function fails, the post-executable will not be executed.
Post-executable return codes
Post-executables must give a return code. These return codes determine whether the application is
stopped.
0
POST_OK
Post-executable OK; continue.
1
POST_ERROR_GLOBAL
Post-executable failed; stop application service cluster-wide.
2
POST_ERROR_DC
Post-executable failed; stop application service in this data center.
3
POST_ERROR_LOCAL
Post-executable failed; stop application service on this system.
4
POST_ERROR_CONTINUE
Post-executable failed; continue without error.
84
Advanced HP XP Cluster Extension configuration
7 Troubleshooting
To troubleshoot problems with HP XP Cluster Extension, you must understand Continuous Access
environments. Many issues can be attributed to incompatible disk pair states. See the Continuous
Access and RAID Manager documentation before assuming that a problem has been caused by
HP XP Cluster Extension.
CAUTION:
HP XP Cluster Extension cannot handle device/copy group states automatically and correctly when
they result from manual manipulations. HP XP Cluster Extension will try to automatically recover
suspended RAID Manager device/copy group states if the AutoRecover object is set to YES.
However, if the recovery procedure experiences a problem, HP XP Cluster Extension will not stop
unless fence level DATA is used or the ApplicationStartup object is set to RESYNCWAIT. Therefore,
ensure that the device/copy group PAIR state has been recovered before the next failure occurs.
Always disable automatic application service failover when resynchronizing disk pairs. A failure
of the resynchronization source while resynchronizing can lead to unrecoverable data on the
resynchronization target. The resynchronization process does not copy data in transactional order.
For more information, see “Implementing rolling disaster protection” (page 79).
HP XP Cluster Extension log files
HP XP Cluster Extension provides log messages to the cluster software as well as to the HP XP
Cluster Extension log file. The HP XP Cluster Extension log file includes disk status information.
•
The HP XP Cluster Extension log file is located in
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
•
For the configuration tool, the clxcfg.log file resides in:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
•
For VM Management on Windows Server 2012/2012 R2 only, the VMClxMscs.log file
resides in:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
•
For CLX cmdlet logs, the CLXCmdlet.log file resides in:
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\
If the log file needs to be cleared and reset, for example, to reduce disk space usage, archive the
log file and then delete it. A new log file is generated automatically.
For information about log levels, see “LogLevel” (page 67).
Start errors
Start errors can occur when the path to the RAID Manager binaries has not been set in the PATH
environment variable. If a user configuration file is not found in the correct directory location, HP
XP Cluster Extension returns a local error.
Failover error handling
HP XP Cluster Extension automatically fails over if the system on which the application is running
becomes unavailable. This also means that if a problem with the disk array state occurs, an
application startup process will be stopped. The behavior of HP XP Cluster Extension is highly
configurable.
Depending on the customer setting, HP XP Cluster Extension is used to prevent applications from
starting automatically under the wrong conditions. Therefore, HP XP Cluster Extension will return
HP XP Cluster Extension log files
85
local, data center-wide, or even cluster-wide errors to prevent accidental access to the disk array
disk set.
HP XP Cluster Extension provides the following error return codes for failover operations:
local error
Prohibits an application service startup on the local system. This can be caused
by the inability of HP XP Cluster Extension to enable disk access, or
misconfiguration of the disk array environment.
data center error
Prohibits an application service startup on any system in the local data center.
This error is returned if the disk state indicates that it makes no sense to allow
any other system connected to the same disk array to access the disks.
global error
A global error is returned if the configuration or the disk state does not allow
an automatic application service startup process. In such cases, manual
intervention is required.
When HP XP Cluster Extension is integrated, an error message string and integer value are
displayed. For the CLI, a return code is displayed. For more information, see “CLI commands”
(page 49).
MSFC-specific error handling
HP XP Cluster Extension related messages are logged by MSFC to the following locations:
•
cluster.log in the location "%windir%\Cluster\Reports"
•
The HP XP Cluster Extension log file is named clxmscs.log.
•
The HP XP Cluster Extension configuration tool log resides in the
%ProgramFiles%\Hewlett-Packard\Cluster Extension XP\log\ directory.
Resource start errors
MSFC configurations do not require a UCF.cfg file if the default COMMON objects are used
(recommended).
MSFC will fail the HP XP Cluster Extension resource on the local system if the clxpcf file is not
present. If the program is in a very early state of processing, the operation might fail and HP XP
Cluster Extension will not show the resource name in the error message.
Failover errors
HP XP Cluster Extension's integration with MSFC returns a local error and fails the resource if a
configuration error occurs. This could be a problem with the RAID Manager instance configuration
or an error, which will probably require starting the resource group on another system.
HP XP Cluster Extension resources return a data center error and fail the resource if the disk array
status indicates that the problem experienced locally would not be solved on another system
connected to the same disk array. This means all systems specified in the DC_A_Hosts resource
property or the DC_B_Hosts resource property would fail to bring the resource group online.
Depending on the resource group and resource property values, the resource tries to start on
different nodes several times. If the remote data center is down, this would look like the resource
group is alternating between the surviving systems. This happens until the previously mentioned
resource and resource group property values are reached or you disable the restarting of the
resource. This could be also the case if the ApplicationStartup resource property has been set to
FASTFAILBACK.
If a disk array state has been discovered that does not allow bringing the resource group online
on any system in the cluster, a cluster error would be reported and the resource would fail on all
systems. This could lead to the same behavior as described for an HP XP Cluster Extension data
center error.
86
Troubleshooting
Examples of such a state could be a SMPL state on both primary and secondary disks, a suspended
(PSUS/SSUS) state on either site, or a state mismatch in the device/copy group for this resource
group. None of the previously mentioned scenarios will allow automatic recovery because the HP
XP Cluster Extension resource cannot decide which copy of the data is the most current copy. In
those cases, a storage or cluster administrator must investigate what happened to the environment.
In any case, restarting a failed resource group without investigating the problem is not
recommended. A failed HP XP Cluster Extension resource indicates the need to check the status of
the disk pair on each copy and decide whether it is safe to continue or not.
“Incompatible disk pair state ” (page 87) shows examples of an incompatible disk pair state shown
in the clxmscs.log file. The same messages can be found in the MSFC cluster log file if the
HP XP Cluster Extension LogLevel object is set to INFO.
TIP:
Use a UCF.cfg file to set the LogLevel object.
Figure 9 Incompatible disk pair state
Figure 10 CLX logs for incompatible disk pair state
Using the Domain user account (Windows Server 2008/2008 R2/2012/2012 R2
only)
When using the Domain user account to manage the cluster, modifying HORCM files might not be
possible, and HP XP Cluster Extension tools might not run as expected. If you experience any of
these issues, turn off UAC.
To turn off UAC, select Control panel→User Accounts, and click Turn User Account Control on or
off. Clear the User Account Control (UAC) to help protect your computer check box. This might
resolve the issue and allow you to use the HP XP Cluster Extension tools with the Domain user
account.
MSFC-specific error handling
87
Pair/resync monitor messages in event log
Using the pair/resync monitor will cause a message in the system log file of your operating system
(for any non-PAIR state of the device/copy group being monitored). Those messages might indicate
the following:
•
The RAID Manager instance is not running or cannot be used to gather device/copy group
state information.
•
The device/copy group is not in the PAIR state.
This could be caused by Continuous Access link failures or manual manipulation of the disk pair
state.
TIP:
Recover the PAIR state immediately, because replication of your data is not possible.
Check monitored disk pairs by invoking the following command from the command line:
clxchkmon –n application_name –g device_group –show
TIP: Disable application service failover for the time of the disk pair recovery (resynchronization).
HP XP Cluster Extension's logic is based on the assumption that if the monitor is enabled, immediate
action will be taken to recover a suspended disk pair.
Problem
Resource XYZ: XP Cluster Extension: device group XYZ is not in PAIR
state.
This message appears even though the device/copy group is in PAIR state.
Solution
If you are using the pair/resync monitor, the ResyncMonitorInterval must be less than or equal to
the resource monitor interval for the HP XP Cluster Extension resource to prevent erroneous logging.
The ResyncMonitorInterval in HP XP Cluster Extension defines when the pair/resync monitor checks
the actual device/copy group state. This state will be valid and shown until the next update
(ResyncMonitorInterval) occurs. If the actual XP disk pair state changes between two
ResyncMonitorInterval(s), the PAIR state shown by the pair/resync monitor will not be correct.
The resource monitor checks the status of the HP XP Cluster Extension resource at the resource
monitor interval of the cluster software. The HP XP Cluster Extension resource reports the status of
the device/copy group at that interval based on the current state in the pair/resync monitor.
If the ResyncMonitorInterval is set to a higher value than the resource monitor interval for the HP
XP Cluster Extension resource, the pair/resync monitor will update the device/copy group state
less often.
However, the HP XP Cluster Extension resource logs messages only if the device/copy group is
not in PAIR state or if a RAID Manager error occurred (for example, if RAID Manager is not running).
Example
Set the HP XP Cluster Extension agent's MonitorInterval attribute to 60 seconds (the default value);
then set the HP XP Cluster Extension resource ResyncMonitorInterval attribute to less than 60 seconds.
88
Troubleshooting
8 Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
•
Product model names and numbers
•
Technical support registration number (if applicable)
•
Product serial numbers
•
Error messages
•
Operating system type and revision level
•
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/e-updates
After registering, you will receive e-mail notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
The following documents and websites provide related information:
•
HP XP Cluster Extension Software Installation Guide
•
HP P9000 RAID Manager User Guide
•
HP StorageWorks P9000 Continuous Access Synchronous User Guide
•
HP StorageWorks P9000 Business Copy User Guide
•
HP XP P9000 RAID Manager Installation and Configuration Guide
•
HP StorageWorks Continuous Access Software User Guide (title varies depending on XP array
model)
•
HP XP Continuous Access Software Journal User Guide (title varies depending on XP array
model)
•
HP StorageWorks Business Copy Software User Guide (title varies depending on XP array
model)
•
HP SAN Design Reference Guide Volume 1 to 5
You can find these documents on the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
In the Storage section, click Storage Software, and then select your product.
Contacting HP
89
White papers
The following white papers are available at www.hp.com/storage/whitepapers:
•
Live Migration across data centers and disaster tolerant virtualization architecture with HP
StorageWorks Cluster Extension and Microsoft Hyper-VTM
•
HP XP Cluster Extension solution for HP XP Continuous Access 3DC environment
•
Considerations in HP XP Cluster Extension configurations to stop automatic XP CA disk pair
resynchronization when CA link is suspended
•
Implementing HP StorageWorks Cluster Extension for Windows in a VMware Virtual Machine
•
Migrating HP StorageWorks Cluster Extension Quorum Filter Service Implementations to
Microsoft Majority Node Set Quorum Configurations
HP websites
For additional information, see the following HP websites:
•
http://www.hp.com
•
http://www.hp.com/go/storage
•
http://www.hp.com/service_locator
•
http://www.hp.com/support/manuals
•
Single Point of Connectivity Knowledge (SPOCK)
•
www.hp.com/storage/whitepapers
•
http://docs.hp.com/en/ha.html
Typographic conventions
Table 5 Document conventions
Convention
Element
Blue text: Table 5 (page 90)
Cross-reference links
Blue, bold, underlined text
email addresses
Blue, underlined text: http://www.hp.com
Website addresses
Bold text
• Keys that are pressed
• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as menu
and list items, buttons, tabs, and check boxes
Italic text
Text emphasis
Monospace text
• File and directory names
• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text
• Code variables
• Command variables
Monospace, bold text
WARNING!
90
Emphasized monospace text
Indicates that failure to follow directions could result in bodily harm or death.
Support and other resources
CAUTION:
IMPORTANT:
NOTE:
TIP:
Indicates that failure to follow directions could result in damage to equipment or data.
Provides clarifying information or specific instructions.
Provides additional information.
Provides helpful hints and shortcuts.
Documentation feedback
HP 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@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.
Documentation feedback
91
Glossary
CHA
Channel adapter. A device that provides the interface between the array and the external host
system. Occasionally, this term is used synonymously with the term channel host interface processor
(CHIP).
CLI
Command-line interface. An interface comprised of various commands which are used to control
operating system responses.
command device
A volume in the disk array that accepts Continuous Access, Business Copy, or XP for Business
Continuity Manager control operations, which are then executed by the array.
CU
Control unit.
CVS
Custom volume size. CVS devices (OPEN-x CVS) are custom volumes configured using array
management software to be smaller than normal fixed-size OPEN system volumes. Synonymous
with volume size customization (VSC). OPEN-V is a CVS-based volume.
DKC
Disk controller.
DLL
Dynamic-link library.
DSM
Device Specific Module.
failover
Disconnecting a failed unit or path and replacing it with an alternative unit or path to continue
functioning.
FC
Fibre Channel. A network technology primarily used for storage networks.
fence level
A method of setting rejection of XP Continuous Access write I/O requests from the host according
to the condition of mirroring consistency.
GUI
Graphical user interface.
GUID
Globally unique identifier.
HBA
Host bus adapter.
heartbeat
A periodic synchronization signal issued by cluster software or hardware to indicate that a node
is an active member of the cluster.
LD, LDEV
Logical device. An LDEV is created when a RAID group is carved into pieces according to the
selected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9). The number of resulting LDEVs
depends on the selected emulation mode. The term LDEV is also known as term volume.
LU
Logical unit.
LUN
Logical unit number. A LUN results from mapping a logical unit number, port ID, and LDEV ID to
a RAID group. The size of the LUN is determined by the emulation mode of the LDEV and the
number of LDEVs associated with the LUN.
LUSE
Logical Unit Size Expansion. The LUSE feature is available when the HP StorageWorks LUN
Manager product is installed, and allows a LUN, normally associated with only a single LDEV,
to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access
a single large pool of storage.
LVM
Logical Volume Manager.
MINAP
Minimum active paths.
MMC
Microsoft Management Console.
MNS
Majority node set.
MSFC
Microsoft Failover Cluster.
MU
Mirror unit.
NIC
Network interface card. A device that handles communication between a device and other devices
on a network.
P-VOL
Primary volume.
path
A path is created by associating a port, a target, and a LUN ID with one or more LDEVs. Also
known as a LUN.
92
Glossary
PCF
Product Configuration File.
port
A physical connection that allows data to pass between a host and a disk array.
primary site
The data center location that owns the cluster group (quorum resource).
PSUS
Pair suspended-split.
quorum
In MSFC, a cluster resource that has been configured to control the cluster, maintaining essential
cluster data and recovery information. In the event of a node failure, the quorum acts as a
tie-breaker and is transferred to a surviving node to ensure that data remains consistent within
the cluster.
RAID
Redundant array of independent disks.
S-VOL
Secondary or remote volume. The copy volume that receives the data from the primary volume.
SCSI
Small Computer Systems Interface. A standard, intelligent parallel interface for attaching peripheral
devices to computers, based on a device-independent protocol.
secondary site
The data center location with the mirror copy of the quorum disk pair.
SMIT
System Manager Information Tool.
SMPL
Simplex.
split-brain
syndrome
A state of data corruption that can occur if a cluster is re-formed as subclusters of nodes at each
site, and each subcluster assumes authority, starting the same set of applications and modifying
the same data.
SPOCK
Single Point of Connectivity Knowledge website. SPOCK is the primary portal used to obtain
detailed information about supported HP storage product configurations.
SPOF
Single point of failure.
SVP
Service processor. A computer built into a disk array. The SVP, used only by an HP service
representative, provides a direct interface to the disk array.
TMSCSI
Target mode SCSI.
UAC
User account control.
UCF
User configuration file.
VM
Virtual Machine.
volume
On the XP array, a volume is a uniquely identified virtual storage device composed of a control
unit (CU) component and a logical device (LDEV) component separated by a colon. For example
00:00 and 01:00 are two uniquely identified volumes; one is identified as CU = 00 and LDEV
= 00, and the other as CU = 01 and LDEV = 00; they are two unique separate virtual storage
devices within the array.
VSC
Volume size customization. Also known as CVS.
93
Index
A
Adding dependencies
using PowerShell, 36
APPLICATION section
description, 67
application service failover, 88
ApplicationDir object
description, 67
ApplicationStartup object
description, 68
AsyncTakeoverTimeout object
description, 69
AutoFailbackType
description, 24
automatic recovery, 85
AutoRecover object
description, 70
rolling disaster protection, 80
B
Basic Resource Health Check Interval
description, 23
BCEnabledA object
description, 70
BCEnabledB object
description, 70
BCMuListA object
description, 70
BCMuListB object
description, 70
BCResyncEnabledA object
description, 70
BCResyncEnabledB object
description, 71
BCResyncMuListA object
description, 71
BCResyncMuListB object
description, 71
Business Copy
rolling disaster protection, 79
C
CLI
HP XP Cluster Extension, 6
Cluster Extension Cmdlets, 52
Cluster setup considerations
Cluster Shared Volume, 9
cluster software
integration with HP XP Cluster Extension, 6
ClusterNotifyCheckTime
description, 71
UCF requirement, 34
ClusterNotifyWaitTime
description, 71
UCF requirement, 34
94
Index
COMMON section
description, 66
configuration
consolidated site, 8
Microsoft Failover Cluster, 14
one to one, 7
configuration information
exporting, 19
importing, 19
contacting HP, 89
Continuous Access
configurations, 8
fast failback, 7
fence levels, 8
pairs, 6
conventions
document, 90
text symbols, 90
D
DataLoseDataCenter object
description, 71
DataLoseMirror object
description, 72
DC_A_Hosts object
description, 72
DC_B_Hosts object
description, 72
dependencies
adding (CLI), 35
adding (Windows Server 2008/2008 R2/2012/2012
R2), 35
DeviceGroup object
description, 72
disaster tolerance, 6
disk pairs
Continuous Access, 6
document
conventions, 90
related documentation, 89
documentation
HP website, 89
providing feedback on, 91
E
error return codes
failover, 85
exporting
configuration information, 19
F
FailoverPeriod
description, 24
FailoverThreshold
description, 24
fast failback
Continuous Access, 7
FASTFAILBACK value
description, 68
features
HP XP Cluster Extension, 6
fence levels
Continuous Access, 8
FenceLevel object
description, 72
files
event log, 88
force flag, 82
Filesystems object
description, 73
force flag
file, 82
forceflag option, 49
G
group names
Microsoft Failover Cluster, 20, 21
H
help
obtaining, 89
HP
technical support, 89
HP XP
Cluster Extension, 64
HP XP Cluster Extension
CLI, 6
cluster software, 6
configurations
consolidated-site, 8
one-to-one, 7
configuring with Microsoft Failover Cluster, 14
dependency on RAID Manager, 11
environments, 9
features, 6
Hyper-V Live Migration, 41, 44
log files
Microsoft Failover Cluster, 42
MSFC, 44
LogDir object
description, 66
LogLevel
UCF requirement, 34
LogLevel object
description, 67
LooksAlivePollInterval
description, 23
M
majority node set
Microsoft Failover Cluster, 9
MergeCheckInterval
UCF requirement, 34
Microsoft Failover Cluster
adding dependencies, 34
administration, 42, 44
changing resource names, 21
configuration example, 36
configuration XP, 64
configuring RAID Manager advanced properties, 28
configuring RAID Manager device/copy group details,
28
configuring RAID Manager instances, 28
data center assignments, 30
group names, 20, 21
integration with HP XP Cluster Extension, 14
majority node set, 9
resource names, 20, 21
Microsoft Management Console, 23
mounting a file system, 63
N
names
changing (Microsoft Failover Cluster), 21
network considerations
RAID Manager, 12
I
O
importing
configuration information, 19
instances
starting and stopping, 12
IsAlivePollInterval
description, 23
objects
APPLICATION section, 67
COMMON section, 66
J
JournalDataCurrency object
description, 73
L
live migration, 34, 41, 44
LocalDCLMForNonPAIRDG
description, 73
log file
location, 85
P
pair/resync monitor
configuring for Microsoft Failover Cluster, 15
integration with Microsoft Failover Cluster, 30
invoking, 81
port, 15, 18
troubleshooting, 88
PendingTimeout
description, 24
post-execution programs
invoking, 82
return codes, 84
PostExecCheck object
95
description, 74
PostExecScript object
description, 74
pre-execution programs
invoking, 82
return codes, 83
PreExecScript object
description, 74
programs
post-execution, 82
pre-execution, 82
R
RAID Manager, 11
command device authentication, 11, 15, 18
communication
in-band, 11
out-of-band, 11
creating instances, 11
device/copy groups, 12
network considerations, 12
rolling disaster protection, 79
setting up, 11
starting and stopping instances, 12
testing failover and failback, 12
RaidManagerInstances object
description, 74
recommendations
log files, 44
recovering PAIR state, 88
recovery
disk pair states, 62
procedures, 62
sequence, 63
recovery procedure, 31
related documentation, 89
remote management, 23, 32, 43
removing a combination, 51
resource names
Microsoft Failover Cluster, 20, 21
Resource properties
using Microsoft Failover PowerShell Cmdlets, 34
resources
adding for Microsoft Failover Cluster, 19
adding for Windows Server 2008/2008 R2, 20
adding with the CLI, 20
bringing online, 39
changing properties for Microsoft Failover Cluster, 25
configuring for Microsoft Failover Cluster, 21
deleting for MSFC, 40
Microsoft Failover Cluster, 21
properties (CLI), 33
properties (UCF), 34
taking offline, 40
Response to resource failure
description, 23
RestartAction
description, 23
RestartPeriod
96
Index
description, 24
RestartThreshold
description, 23
ResyncMonitor object
description, 74
rolling disaster protection, 80
ResyncMonitorAutoRecover attribute, 40
ResyncMonitorAutoRecover object
description, 75
ResyncMonitorInterval object
description, 75
RESYNCWAIT value
description, 69
ResyncWaitTimeout object
description, 75
return codes
post-execution, 84
pre-executable, 83
rolling disaster protection, 6
automatic recovery, 80
configuration with Business Copy , 79
pair/resync monitor, 80
restoring server operation, 80
setting in user configuration file, 80
S
server
restoring operation, 80
service or application
bouncing, 42
starting
errors, 85
StatusRefreshInterval
description, 75
UCF requirement, 34
Subscriber's Choice, HP, 89
symbols in text, 90
T
takeover function failure, 84
technical support
HP, 89
text symbols, 90
Thorough Resource Health Check Interval
description, 23
timing
Microsoft Failover Cluster considerations, 41
troubleshooting
HP XP Cluster Extension problems, 85
typographic conventions, 90
U
user configuraiton file
LocalDCLMForNonPAIRDG, 73
user configuration file
APPLICATION section, 67
ApplicationDir object, 67
ApplicationStartup object, 68
AsyncTakeoverTimeout object, 69
AutoRecover object, 70
BCEnabledA object, 70
BCMuListA object, 70
BCMuListB object, 70
BCResyncEnabledA object, 70
BCResyncEnabledB object, 71
BCResyncMuListA object, 71
BCResyncMuListB object, 71
COMMON section, 66
DataLoseDataCenter object, 71
DataLoseMirror object, 72
DC_A_Hosts object, 72
DC_B_Hosts object, 72
DeviceGroup object, 72
FASTFAILBACK value, 68
FenceLevel object, 72
Filesystems object, 73
JournalDataCurrency object, 73
LogDir object, 66
LogLevel object, 67
object formats, 64
objects, 64
PostExecCheck object, 74
PostExecScript object, 74
PreExecScript object, 74
RaidManagerInstances object, 74
ResyncMonitor object, 74
ResyncMonitorAutoRecover object, 75
ResyncMonitorInterval object, 75
RESYNCWAIT value, 69
ResyncWaitTimeout object, 75
sample, 75
specifying object values, 65
structure, 64
XPSerialNumbers object, 75
W
websites
HP , 90
HP Subscriber's Choice for Business, 89
product manuals, 89
X
XPSerialNumbers object
description, 75
97
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising