Adaptec 5325301638 Administration Guide - Page 61

SnapTrees & Security Models, SnapTree Functionality

Page 61 highlights

SnapTrees & Security Models SnapTrees & Security Models Directories created at the root of a Snap Server volume are assigned one of two security models: Windows or UNIX. The security model determines the file-level security scheme that will apply to files, folders, and subdirectories within the toplevel directory. This security-based directory structure is referred to as a SnapTree. • Creating a SnapTree Directory - SnapTree directories are created either from the Security > SnapTree screens in the Administration Tool or from a client machine. Using the SnapTree screens, you can assign either security model at creation time. (The default is Windows.) Directories created from a client adopt the security model of its parent volume or SnapTree directory. Tip A SnapTree directory can also be created and a security model assigned in the course of creating a share. • Toggling Security Models - The security model applied to a volume or SnapTree directory can be changed only from the Security > SnapTree screens. Caution Do not use spaces in naming a directory that is to serve as a share point. The GuardianOS will recognize the directory, but it will not be available for use as a mount point. Instead, use the underscore character to separate terms in a directory name. SnapTree Functionality Function Description SnapTree Directory Ownership Security Model Inheritance Toggling Security Models Mixing SnapTrees Default ownership differs according to the method used to create the SnapTree directory: • From the client - The logged-on user will be the user owner of the directory, and the logged-on user's primary group will be the group owner of the directory. • From the Administration Tool - The user owner of the SnapTree will be the admin account, and the group owner will be admin group (admingrp). A volume is assigned a security model, and new directories created at the root of the volume default to that security model. Files and directories created below a SnapTree directory default to its security model. You can change the security model for an individual volume, an individual SnapTree, or for a volume and all the SnapTrees it contains. You can create SnapTrees of different security models on the same volume. Chapter 6 Share and File Access 47

  • 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

SnapTrees & Security Models
Chapter 6
Share and File Access
47
SnapTrees & Security Models
Directories created at the root of a Snap Server volume are assigned one of two
security models: Windows or UNIX. The security model determines the file-level
security scheme that will apply to files, folders, and subdirectories within the top-
level directory. This security-based directory structure is referred to as a SnapTree.
Creating a SnapTree Directory —
SnapTree directories are created either from the
Security > SnapTree
screens in the Administration Tool or from a client machine.
Using the SnapTree screens, you can assign either security model at creation
time. (The default is Windows.) Directories created from a client adopt the
security model of its parent volume or SnapTree directory.
Tip
A SnapTree directory can also be created and a security model assigned in
the course of creating a share.
Toggling Security Models —
The security model applied to a volume or SnapTree
directory can be changed only from the
Security > SnapTree
screens.
Caution
Do not use spaces in naming a directory that is to serve as a share point.
The GuardianOS will recognize the directory, but it will not be available for use as a
mount point. Instead, use the underscore character to separate terms in a directory
name.
SnapTree Functionality
Function
Description
SnapTree Directory Ownership
Default ownership differs according to the method used
to create the SnapTree directory:
From the client —
The logged-on user will be the
user owner of the directory, and the logged-on user’s
primary group will be the group owner of the
directory.
From the Administration Tool
— The user owner
of the SnapTree will be the admin account, and the
group owner will be admin group (admingrp).
Security Model Inheritance
A volume is assigned a security model, and new
directories created at the root of the volume default to
that security model. Files and directories created below
a SnapTree directory default to its security model.
Toggling Security Models
You can change the security model for an individual
volume, an individual SnapTree, or for a volume and all
the SnapTrees it contains.
Mixing SnapTrees
You can create SnapTrees of different security models
on the same volume.