Adaptec 5325301656 Administration Guide - Page 96

Components and Options, SnapTrees, NFS Share Access

Page 96 highlights

Components and Options SnapTrees SnapTrees are directories that can be configured for the Windows/Mixed or UNIX security model. SnapTrees make a specific directory structure follow the rules of the specified security model, which indicates which file permission personality will be present on files by default, and whether that personality can be changed by users when changing permissions. All top level volume directories, as well as all directories inside the first level of a volume, are considered SnapTrees. For more information, see "SnapTrees and Security Models" on page 84. NFS Share Access When controlling share access for NFS clients, administrators can limit client access to the shares independently of share level permissions that apply to other protocols. Access is controlled on a per-share basis. To set the NFS access, select a share on the Shares page and click NFS Access. Changes made on this screen affect the NFS "exports" file within GuardianOS. Caution If there are multiple shares to the same directory on the disk, and those shares permit access via NFS, they must all have the same NFS export configuration. This is enforced when configuring NFS access to the overlapping shares. Components and Options Shares are created and share access is granted using the Administration Tool. Filelevel permissions are configured from a Windows or UNIX/Linux workstation. The following table summarizes the components, options, and tools available for setting up share and file security on Snap Servers. Component Options Security Models (SnapTrees) Volumes and directories created in the root of a volume have one of two security models: Windows/Mixed or UNIX. The security model determines the rules regarding which security personality will be present on files and directories created by the various protocols and clients, and whether the personality of files and directories can be changed by changing permissions. These directories are referred to as SnapTrees, and their security models can be configured from the Security > SnapTrees screen. 82 Snap Server Administrator Guide

  • 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

Components and Options
82
Snap Server Administrator Guide
SnapTrees
SnapTrees are directories that can be configured for the Windows/Mixed or UNIX
security model. SnapTrees make a specific directory structure follow the rules of the
specified security model, which indicates which file permission personality will be
present on files by default, and whether that personality can be changed by users
when changing permissions. All top level volume directories, as well as all
directories inside the first level of a volume, are considered SnapTrees. For more
information, see “SnapTrees and Security Models” on page 84.
NFS Share Access
When controlling share access for NFS clients, administrators can limit
client access
to the shares independently of share level permissions that apply to other protocols.
Access is controlled on a per-share basis. To set the NFS access, select a share on the
Shares page and click
NFS Access
. Changes made on this screen affect the NFS
“exports” file within GuardianOS.
Caution
If there are multiple shares to the same directory on the disk, and those
shares permit access via NFS, they must all have the same NFS export
configuration. This is enforced when configuring NFS access to the overlapping
shares.
Components and Options
Shares are created and share access is granted using the Administration Tool. File-
level permissions are configured from a Windows or UNIX/Linux workstation. The
following table summarizes the components, options, and tools available for setting
up share and file security on Snap Servers.
Component
Options
Security Models
(SnapTrees)
Volumes and directories created in the root of a volume have one of two
security models: Windows/Mixed or UNIX. The security model
determines the rules regarding which security personality will be present
on files and directories created by the various protocols and clients, and
whether the personality of files and directories can be changed by
changing permissions. These directories are referred to as SnapTrees,
and their security models can be configured from the
Security >
SnapTrees
screen.