Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Purpose
The Failover Cluster APIs are provided by failover clustering on Windows Server. Developers can use the Failover Cluster APIs to do these tasks:
- Define software and hardware component types to manage on a failover cluster.
- Run clustering tasks that increase the scalability and availability of the application.
- Monitor and control failover clusters.
In this section
-
A summary of changes to the Failover Cluster APIs.
-
Overview and architecture:
Conceptual documentation that includes overview information and describes the architecture of the Failover Cluster APIs.
This section includes information about:
- Failover clusters
- Application types
- API components
-
Programming tasks and guidance:
Task oriented documentation that describes how to use the Failover Cluster APIs.
This section includes information about:
- IDE setup info
- Choosing an application type
- Determining the programming elements to implement
- Using the APIs to complete tasks
- Programming conventions
- Programming examples
-
Reference documentation:
Reference documentation that describes the programming elements of the Failover Cluster APIs.
This section includes reference information about:
- The Failover Cluster API
- The Failover Cluster Automation Server
- The Failover Cluster Configuration API
-
A glossary that describes the terms used in this documentation.
Additional resources
For more external information about the technologies used by the Failover Cluster APIs, refer to the following resources:
Information | Resource |
---|---|
Installing, configuring, and administering a failover cluster |
|
The clustering concept, common clustering models, and the history and current state of clustering technology |
|
Component Object Model (COM) programming and automation |
|
Supporting Unicode in your applications |
|
Scripting |
|
Synchronization objects, asynchronous event notifications, reentrancy, services, and thread and process management |
|
Related topics