HP StorageWorks 9000s NAS 4000s and 9000s Administration Guide - Page 217

Permissions and Access Rights on Share Resources, NFS Cluster Specific Issues

Page 217 highlights

Cluster Administration 4. Create the file share resources. In a clustered environment, file shares are created as a type of cluster resource. Creating cluster resources and file shares is documented later in this chapter. 5. Assign ownership of the file share resources to the resource groups. a. Divide ownership of the file share resource between the resource groups, which are in turn distributed between the virtual servers, for effective load balancing. b. Make sure that the physical disk resource for this file share is also included in this group. c. Make sure 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 via the Cluster Administrator tool versus the individual shares on the file system themselves via Windows Explorer. Administering them through the Cluster Administrator tool allows the permissions to migrate from one node to other. In addition, permissions established using Explorer will be lost once the share is failed or taken offline. To access the permissions, see "Setting Permissions for a SMB File Share" and "Setting Permissions for an NFS Share." NFS Cluster Specific Issues In addition to the user name mapping best practices outlined in the "Microsoft Services for NFS" chapter, there are additional recommendations. For convenience, all suggestions are listed below: ■ Back up user and group mappings To avoid loss of complex advanced mappings in the case of a system failure, back up the mappings whenever the mappings have been edited or new mappings have been added. ■ Map consistently Groups that are mapped to each other should contain the same users and the members of the groups should be properly mapped to each other to ensure proper file access. ■ Map properly - Valid UNIX users should be mapped to valid Windows users. - Valid UNIX groups should be mapped to valid Windows groups. - Mapped Windows user must have the Access this computer from the Network privilege or the mapping will be squashed. - The mapped Windows user must have an active password, or the mapping will be squashed. ■ In a clustered deployment, create user name mappings using domain user accounts. Because the security identifiers of local accounts are recognized only by the local server, other nodes in the cluster will not be able to resolve those accounts during a failover. Do not create mappings using local user and group accounts. ■ In a clustered deployment, administer user name mapping on a computer that belongs to a trusted domain. If NFS administration tasks are performed on a computer that belongs to a domain that is not trusted by the domain of the cluster, the changes are not properly replicated among the nodes in the cluster. NAS 4000s and 9000s Administration Guide 217

  • 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
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

Cluster Administration
217
NAS 4000s and 9000s Administration Guide
4.
Create the file share resources.
In a clustered environment, file shares are created as a type of cluster resource. Creating
cluster resources and file shares is documented later in this chapter.
5.
Assign ownership of the file share resources to the resource groups.
a.
Divide ownership of the file share resource between the resource groups, which are in
turn distributed between the virtual servers, for effective load balancing.
b.
Make sure that the physical disk resource for this file share is also included in this
group.
c.
Make sure 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 via the Cluster Administrator tool
versus the individual shares on the file system themselves via Windows Explorer.
Administering them through the Cluster Administrator tool allows the permissions to migrate
from one node to other. In addition, permissions established using Explorer will be lost once
the share is failed or taken offline. To access the permissions, see “Setting Permissions for a
SMB File Share” and “Setting Permissions for an NFS Share.”
NFS Cluster Specific Issues
In addition to the user name mapping best practices outlined in the “Microsoft Services for
NFS” chapter, there are additional recommendations.
For convenience, all suggestions are listed below:
Back up user and group mappings
To avoid loss of complex advanced mappings in the case of a system failure, back up the
mappings whenever the mappings have been edited or new mappings have been added.
Map consistently
Groups that are mapped to each other should contain the same users and the members of
the groups should be properly mapped to each other to ensure proper file access.
Map properly
Valid UNIX users should be mapped to valid Windows users.
Valid UNIX groups should be mapped to valid Windows groups.
Mapped Windows user must have the
Access this computer from the Network
privilege
or the mapping will be squashed.
The mapped Windows user must have an active password, or the mapping will be
squashed.
In a clustered deployment, create user name mappings using domain user accounts.
Because the security identifiers of local accounts are recognized only by the local server,
other nodes in the cluster will not be able to resolve those accounts during a failover. Do
not create mappings using local user and group accounts.
In a clustered deployment, administer user name mapping on a computer that belongs to a
trusted domain.
If NFS administration tasks are performed on a computer that belongs to a domain that is
not trusted by the domain of the cluster, the changes are not properly replicated among the
nodes in the cluster.