Vous êtes sur la page 1sur 6

New Features of SAP Cluster

Resource Type DLL for Microsoft


Failover Cluster

Applies to:
SAP NetWeaver 04 and higher running in a Microsoft Failover Cluster environment.

Summary
This document describes the changes and new features included in the SAP Cluster Resource Type DLL
(saprc.dll and saprcex.dll).
Author: Bernd Kuespert
Company: SAP AG
Created on: 10 October 2012
Updated on: 13 June 2013

Author Bio
Bernd Kuespert is working in the Microsoft Platforms Department as a Senior Developer for SAP AG and is
responsible for Update and Upgrade Procedures on Windows and Windows Failover Clustering for SAP
systems based on SAP NetWeaver.

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
1

New Features of SAP Cluster Resource Type DLL for Microsoft Failover Cluster

Table of Contents
The SAP Cluster Resource DLL ......................................................................................................................... 3
Changes in SAP Cluster Resource Type DLL .................................................................................................... 3
Prerequisites ................................................................................................................................................... 3
Introducing the Maintenance Mode Flag ......................................................................................................... 3
Steps to Perform Before an Upgrade ........................................................................................................................... 4
Steps to Perform After an Upgrade .............................................................................................................................. 4
Check the Availability of the Maintenance Flag............................................................................................................ 4

Communication Interface ................................................................................................................................ 5


Related Content .................................................................................................................................................. 5
Copyright............................................................................................................................................................. 6

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
2

New Features of SAP Cluster Resource Type DLL for Microsoft Failover Cluster

The SAP Cluster Resource DLL


In a Microsoft Failover Cluster, every third-party Resource Type implementation has to use its own set of
resource DLLs including the coding to properly interoperate with the cluster service. After the DLLs have
been registered in the Microsoft Failover Cluster, the Resource Control Manager and the Resource Host
Subsystem (RHS) that are part of the cluster service can maintain and monitor the state of the resource
(online, offline, failed, etc.) and execute some actions (move, failover, and failback).
A Resource DLL provides the important IsAlive and LooksAlive checks, which are both executed by the
Resource Monitor.
The IsAlive function checks by default every 60 seconds (configurable through the isAlivePollInterval
property), whether the resource works properly.
The LooksAlive function works more precisely than the IsAlive function. The LooksAlive function checks by
default every 5 seconds (configurable through the LooksAlivePollInterval property), whether a resource is
available for use.
The timeout value specifies how many seconds the Failover Cluster Service waits until it acknowledges that
the resource failed.
In addition, resources have common properties, owned by every instance of a cluster object and special
private properties, owned by an individual instance of a cluster object.

Changes in SAP Cluster Resource Type DLL


The new version of the SAP Cluster Resource Type DLL contains the following enhancements and fixes. For
a description of how to update the SAP Resource Type DLL, see SAP Knowledgebase Article 1596496.
The new version of the SAP Resource Type DLL is downward-compatible to older SAP Kernel versions.
Prerequisites
To be able to use the new features, you have to install an SAP Kernel with the following minimum patch
level:

Kernel Version

Patch level

SAP Kernel 6.40 for SAP Web AS 6.40

PL 387

SAP Kernel 7.20 for SAP NetWeaver 7.x

PL 102

For more information about how to install a new SAP Kernel, see SAP Note 1636252.
Introducing the Maintenance Mode Flag
So far it was mandatory to misconfigure the SAP Instance Resource with a non-existing SAP system number
to prevent an unwanted failover of the SAP cluster group during an upgrade as described in the upgrade
documentation.
With the new version of the SAP Cluster Resource DLL, this misconfiguration is no longer required. You only
have to set MaintenanceMode to 1. You can set or unset the flag as a private property of an SAP Instance
Resource by using the and the Properties menu of an SAP Instance Resource in the Failover Cluster
Manager, the command line tool cluster.exe, or PowerShell (as of Windows Server 2008 R2).
On Windows Server 2008 R2, the PowerShell cluster commands are only available after the import of the
module FailoverClusters (import-module failoverclusters). To get an overview of all cmdlets of the
module, you can use the command: get-command -module failoverclusters.

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
3

New Features of SAP Cluster Resource Type DLL for Microsoft Failover Cluster

Be aware that when there is more than one Resource of resource type SAP Resource in a cluster group, you
must set the property of every single resource.
If the Maintenance Mode flag of the SAP Instance Resource is set, the SAP MMC or sapcontrol no longer
use the cluster interface when starting and stopping an SAP instance.
Steps to Perform Before an Upgrade
You have to perform the following steps on the Failover Cluster before starting an update or upgrade of an
SAP system:
1. Stop the Instance and the Service Resource.

Using cluster.exe:
cluster res "SAP <SID> <SYS#> Instance" /offline
cluster res "SAP <SID> <SYS#> Service" /offline

Using PowerShell
stop-clusterresource SAP <SID> <SYS#> Instance
stop-clusterresource SAP <SID> <SYS#> Service

2. Set the Maintenance Mode in the Properties of the SAP Instance Resource:
Using cluster.exe:
cluster res "SAP <SID> <SYS#> Instance" /priv MaintenanceMode=1

Using PowerShell:
Get-ClusterResource "SAP <SID> <SYS#> Instance" | set-clusterparameter
MaintenanceMode value 1

3. Leave both SAP Cluster Resources offline. Do not start them again at this point in time. Otherwise
the cluster fails over in the event of a restart of the SAP Instance resource.
Steps to Perform After an Upgrade
After the upgrade, disable Maintenance Mode and start both SAP Cluster Resources (Service and
Instance Resource) again.

Using cluster.exe:
cluster res "SAP <SID> <SYS#> Instance" /priv MaintenanceMode=0
cluster res "SAP <SID> <SYS#> Service" /online
cluster res "SAP <SID> <SYS#> Instance" /online

Using PowerShell:
Get-ClusterResource "SAP <SID> <SYS#> Instance" | set-clusterparameter
MaintenanceMode value 0
start-clusterresource SAP <SID> <SYS#> Service
start-clusterresource SAP <SID> <SYS#> Instance

Check the Availability of the Maintenance Flag


Check whether the SAP Instance Resource supports the Maintenance Flag.

Using cluster.exe:
Cluster.exe resource SAP <SID> <SYS#> Instance /priv

Using PowerShell:

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
4

New Features of SAP Cluster Resource Type DLL for Microsoft Failover Cluster

Get-ClusterResource "SAP <SID> <SYS#> Instance" | Get-ClusterParameter

The list of private properties returned should include the MaintenanceMode property (output of
cluster.exe):

Listing private properties for 'SAP <SID> <SYS#> Instance':


T
-S
S
D
D
D
D
D
D
D
S

Resource
-------------------SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance
SAP OQ7 00 Instance

Name
-----------------------------SAPSystemName
SAPSystem
SAPPendingWait
AccepableYellowTime
WaitBeforePoll
Trace
MinGoodProcesses
EnableInterfaceCaching
ServiceControl
MaintenanceMode

Value
----------------------<SID>
<SYS#>
300 (0x12c)
300 (0x12c)
10 (0xa)
0 (0x0)
1 (0x1)
0 (0x0)
1 (0x1)
0

Communication Interface
We had several issues in the past where already existing cluster resources faced a failover during the
installation of other SAP components (SAP MMC, second or third instance in a cluster). The reason for this
was that every time a SAP start service is registered, the DCOM type library is unregistered, replaced, and
registered again.
When the resource monitor performs an IsAlive or LooksAlive check on the resource during this action, the
DCOM connect fails and the resource monitor initiates a failover of the SAP Cluster Group.
Switching the communication interface between SAP service and resource monitor from DCOM to SOAP
based on named pipes prevents this behavior.

Related Content
SAP KBA 1596496 - How to update the SAP Resource Type DLLs for the Cluster Resource Monitor
SAP Note 1654694 - Processes are not stopped during failover of the SAP group
SAP Note 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
5

New Features of SAP Cluster Resource Type DLL for Microsoft Failover Cluster

Copyright
Copyright 2013 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Oracle Corporation.
JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP COMMUNITY NETWORK


2013 SAP AG

scn.sap.com
6