HP StorageWorks P4000 G2 User Manual
Download Operation & user’s manual of HP StorageWorks P4000 G2 Gateway for Free or View it Online on All-Guides.com.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
Load balancing
The creation of separate cluster groups for each virtual server provides more flexibility in balancing
the processing load on the cluster between the two nodes. Each cluster group can be assigned to a
cluster node using the preferred owner parameter. For example, if there are two cluster groups, the
cluster could be set up to have the first cluster group owned by Node A and the second cluster group
owned by Node B. This allows the network load to be handled by both devices simultaneously. If
only one cluster group exists, it can only be owned by one node and the other node would not serve
any network traffic.
File share resource planning issues
CIFS and NFS are cluster-aware protocols that support the Active/Active cluster model, allowing
resources to be distributed and processed on both nodes at the same time. For example, some NFS
file share resources can be assigned to a group owned by a virtual server for Node A and additional
NFS file share resources can be assigned to a group owned by a virtual server for Node B.
Configuring file shares as cluster resources provides for high availability of file shares. Because the
resources are placed into groups with a virtual server, ownership of the files can easily move from
one node to the other, as circumstances require. If the cluster node owning the group of file shares
should be shut down or fail, the other node in the cluster will begin sharing the directories until the
original owner node is brought back on line. At that time, ownership of the group and its resources
can be brought back to the original owner node.
Resource planning
1. Create a cluster group for each node in the cluster with an IP address resource and a network
name resource.
Cluster resource groups are used to balance the processing load on the servers. Distribute
ownership of the groups between the virtual servers.
2. For NFS environments, configure the NFS server.
NFS-specific procedures include entering audit and file lock information as well as setting up
client groups and user name mappings. These procedures are not unique to a clustered deployment
and are detailed in the Microsoft Services for NFS section within the “Other network file and
print services” chapter. Changes to NFS setup information are automatically replicated to all
nodes in a cluster.
3. Create the file share resources.
4. Assign ownership of the file share resources to resource groups.
a. Divide ownership of the file share resources between the resource groups, which are in turn
distributed between the virtual servers, for effective load balancing.
b. Verify that the physical disk resource for this file share is also included in this group.
c. Verify that the resources are dependent on the virtual servers and physical disk resources
from which the file share was created.
Permissions and access rights on share resources
File share and NFS Share permissions must be managed using the Failover Cluster Management tool
and not through the individual shares on the file system themselves via Windows Explorer. Administering
them through Failover Cluster Management allows permissions to migrate from one node to other. In
contrast, permissions established using Explorer are lost if the share is failed or taken offline.
Cluster administration44