Windows Server Failover Cluster

Windows Server Failover Cluster is an Active Passive Cluster based on Windows Server.

Basic Terminology

The following definitions apply to the Windows Server Failover Cluster:

Node

A physical server that is part of a Cluster
All the nodes in a cluster must be configured when the “Is Cluster”’ field in the application configuration wizard is checked.

Server Name

a logical layer on top of the Node layer
Shares in a Cluster belong to a Server Name, which is the name used when shares in the cluster are accessed. A Server Name (discovered automatically, as part of the crawling task) is active on only one Node at a time.

File Share Scoping

shares located on a cluster node can only be through the Server Name – not through the cluster node name in which they are currently active.

 

The example below is used in Section Resource Tree Structure:

There is a cluster application in File Access Manager, called ClusterApp.

ClusterApp consists of node1 and node2.

ServerName1 is currently active in node1, while ServerName2 is currently active in node2.

ServerName1 has one share: Share1 (\\ServerName1\Share1).

“Share1” is mapped to physical path “E:\folder1”

ServerName2 consists of Share2 and Share3 (\\ServerName2\Share2 and \\ServerName2\Share3).

“Share2” is mapped to physical path “E:\folder2”

“Share3” is mapped to physical path “E:\folder2\folder3”

Windows Failover Cluster Share Scoping

File Access Manager supports Windows Failover Cluster Share Scoping.

The Server Names and their corresponding shares are discovered as part of the crawl task, and the business resource tree is built with the Server Names at the first level.