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

Establishing Directory Quotas, New Directory Quota Wizard

Page 149 highlights

Folder, Printer, and Share Management The Directory Quota feature includes the following components: ■ Active and passive space limits on directories ■ Best practice storage resource management policies ■ A severe alarm threshold ■ A warning alarm threshold ■ Auto discovery of drives ■ Customized messages ■ Alarms sent to the event log ■ Alarms sent to the user ■ Storage reports that can be sent to an intranet Web site ■ Custom script support The directory quota set on the system partition always has a passive limit and uses device size (capacity). If the system does not have sufficient quota to write files, it may fail. Also, if the system partition does not have enough space to write temporary files during boot, the system may not restart. Avoid this by using caution when placing quotas on the system directories. Directory quotas use each file's allocation size to determine how much space is used. The allocation size is slightly larger than the actual space used as displayed by Windows Explorer and other Windows programs for the data in a file. This discrepancy may cause some confusion, but the Directory Quota feature is correctly charging the user for the amount of disk space actually consumed to store a file. Large cluster sizes on file allocation table (FAT) file systems may add to the confusion because the entire cluster is always allocated, regardless of the file size. NTFS file systems store very small files in the index file and typically have more reasonable cluster sizes. Because of the differences in the amount of storage requested for a file extension operation and the amount actually allocated by Windows Storage Server 2003 for that extension, the user may be allowed to exceed his quota by as much as one cluster. For example, assume the user has a quota of 100 KB and has used 96 KB on a file system with a cluster size of 8 KB. The user creates a file of 1 KB. Windows Storage Server 2003 requests 1024 bytes be allocated for the file. Since this is less than the remaining quota for the user, the operation is allowed to continue. However, if the cluster size is 8 KB, Windows Storage Server 2003 will actually allocate 8 KB for the file. The user has now used 104 KB, and while this is allowed, future attempts to create or extend files will fail. Establishing Directory Quotas Directory quotas are established in a two part fashion. First a policy is defined using the policies selection from the Directories Policy Page. After a policy is established it can be assigned to a particular directory via the WebUI "New Directory Quota Wizard". By default there are a number of predefined policies, these policies include: ■ 100 MB Limit ■ 500 MB Limit ■ Best Practices Report ■ Default ■ Monitor Directory ■ Partition Alert NAS 4000s and 9000s Administration Guide 149

  • 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

Folder, Printer, and Share Management
149
NAS 4000s and 9000s Administration Guide
The Directory Quota feature includes the following components:
Active and passive space limits on directories
Best practice storage resource management policies
A severe alarm threshold
A warning alarm threshold
Auto discovery of drives
Customized messages
Alarms sent to the event log
Alarms sent to the user
Storage reports that can be sent to an intranet Web site
Custom script support
The directory quota set on the system partition always has a passive limit and uses device size
(capacity). If the system does not have sufficient quota to write files, it may fail. Also, if the
system partition does not have enough space to write temporary files during boot, the system
may not restart. Avoid this by using caution when placing quotas on the system directories.
Directory quotas use each file's allocation size to determine how much space is used. The
allocation size is slightly larger than the actual space used as displayed by Windows Explorer
and other Windows programs for the data in a file. This discrepancy may cause some
confusion, but the Directory Quota feature is correctly charging the user for the amount of disk
space actually consumed to store a file. Large cluster sizes on file allocation table (FAT) file
systems may add to the confusion because the entire cluster is always allocated, regardless of
the file size. NTFS file systems store very small files in the index file and typically have more
reasonable cluster sizes.
Because of the differences in the amount of storage requested for a file extension operation
and the amount actually allocated by Windows Storage Server 2003 for that extension, the user
may be allowed to exceed his quota by as much as one cluster. For example, assume the user
has a quota of 100 KB and has used 96 KB on a file system with a cluster size of 8 KB. The
user creates a file of 1 KB. Windows Storage Server 2003 requests 1024 bytes be allocated for
the file. Since this is less than the remaining quota for the user, the operation is allowed to
continue. However, if the cluster size is 8 KB, Windows Storage Server 2003 will actually
allocate 8 KB for the file. The user has now used 104 KB, and while this is allowed, future
attempts to create or extend files will fail.
Establishing Directory Quotas
Directory quotas are established in a two part fashion. First a policy is defined using the
policies selection from the Directories Policy Page. After a policy is established it can be
assigned to a particular directory via the WebUI
“New Directory Quota Wizard”
. By default
there are a number of predefined policies, these policies include:
100 MB Limit
500 MB Limit
Best Practices Report
Default
Monitor Directory
Partition Alert