Filter
Top Products
Cluster
Resource:
Disk E
Cluster
Resource:
File Share
Eng1
E:\eng1
Cluster
Resource:
Network
Name
Fileserver1
Cluster
Resource:
IP Address
172.18.1.99
Cluster Group
FS1Eng
Node 1
Cluster
Resource:
Disk F
Cluster
Resource:
File Share
Mar1
F:\Mar1
Cluster
Resource:
File Share
Mar4
G:\Mar4
Cluster
Resource:
Network
Name
Fileserver2
Cluster
Resource:
IP Address
172.18.1.98
Cluster
Resource:
Disk G
Cluster Group
FS1Market
Node 2
E:\eng1
E:\eng2
E:\eng3
F:\Mar1
F:\Mar2
F:\Mar3
Raidsets 1-3 Raidsets 4-5 Raidsets 6
G:\Mar4
G:\Mar5
G:\Mar6
Cluster Resource
Physical Disk E
Cluster Resource
Physical Disk F
Cluster Resource
Physical Disk G
Basic
Disk E:
Basic
Disk F:
Basic
Disk G:
Physical Disks 1-4 Physical Disks 9-12 Physical Disks 13-16 Physical Disks 20-23
1
4
2
3
5
Figure 57 C luster concepts diagram
Sequence of events for cluster resources
The seq
uence of events in the diagram includes:
1. Physical disks are combined into R A ID arrays and LUNs.
2. LUNS are designated as basic disks, formatted, and assigned a drive letter via Disk Manager.
3. Physical Disk resources are created for each basic disk inside Cluster Administrator.
4. Dire
ctories and folders are created on assigned drives.
5. Clus
ter components (virtual servers, file shares) a re created, organized in groups, and placed within
the
folders using Cluster Administrator exclusively.
Hierarchyofclusterresourcecomponents
The cluster components are referred to as resources and are placed together in groups. Groups are the
basic unit of failover between nodes. Resources do not fail over individually, rather they fail over with
the group in which they are contained.
In Figure 57 it is depicted as follows:
120
Cluster administration