Dell EqualLogic PS6210XS EqualLogic Group Manager Administrator s Guide PS Ser - Page 216

Create Default Data Reduction Properties, About NAS Data Reduction Schedules

Page 216 highlights

This value must be in the range of 30 to 365 days if compression is enabled. If compression is disabled, the range is 5 to 365 days. By default, this value is 30 days. • In Modify Time, enter a value. After modifying the modify time, click the Save icon to save the changes. The modify time is the minimum number of days that must pass since the file was last modified before the file is eligible for data reduction. This value must be in the range of 30 to 365 days if compression is enabled. If compression is disabled, the range is 5 to 365 days. By default, this value is 30 days. 4. Click OK to save your changes. 5. Click the Save all changes icon to save your changes. NOTE: The status of the filter is listed as File filters....disabled if the ignore-filters option was set through the CLI. If the status is File filters...disabled, any filters that have been configured through the GUI (or CLI) for Access Time or Modify Time have been disabled and all files are candidates for data reduction. Specifying the ignorefilters flag enables data reduction on a container with archive data without waiting for the minimum Access Time/ Modify Time data-reduction policy. Dell recommends that you not use this setting on containers with live data. That is, you should use this setting only on containers with archive data. Create Default Data Reduction Properties NOTE: To enable or disable data reduction properties at a cluster level, you must have group administrator (grpadmin) privileges. To set default data reduction properties at a NAS cluster level: 1. Click Group, expand Group Configuration, and select a NAS cluster. 2. Click the Data Reduction tab. 3. In the Default Data Reduction Policy panel, type or select the necessary data. About NAS Data Reduction Schedules Data reduction occurs as a scheduled activity. A data reduction schedule is defined at the NAS cluster level and controls when data reduction is run on all the containers that have data reduction enabled. You can define multiple data reduction schedules at the NAS cluster level. If two or more data reduction schedules overlap, data reduction begins when the first schedule begins running and ends when the last schedule completes running. You can define up to a total of 1024 schedules on each NAS cluster. This total includes all defined data reduction, NAS, snapshot, and replication schedules. You can configure a data reduction schedule to define the days and times that data reduction begins and ends. If you do not change the default data reduction schedule settings, data reduction will run every day, starting at midnight and running until 6:00 a.m. When you define a data reduction schedule: • Specify start times and end times in a 12-hour format (such as, 3:30PM, 7AM). • Schedule data reduction during off-peak hours to avoid potential performance impact. When multiple containers have data reduction enabled, data reduction processes qualified files for a fixed amount of time starting with the first container. Processing continues on qualified files within the next container, and so on, until data reduction processes all qualified files on each of the enabled containers. If data reduction does not complete on all the enabled containers when the schedule ends, data reduction continues to process the remaining data when the schedule next runs. NOTE: To avoid any potential performance impact from running a data reduction process, define a schedule to run data reduction during off-peak hours. For example: Data reduction is enabled to run on the two containers, NAS_A and NAS_B, of a NAS cluster that is managed by one controller. When the schedule finishes running, if data reduction is being performed on container NAS_B, when the data reduction schedule begins running the next time, data reduction begins running on container NAS_B. When data reduction completes on NAS_B, the data reduction service begins running on container NAS_A. 216 NAS Container Operations

  • 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
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355

This value must be in the range of 30 to 365 days if compression is enabled. If compression is disabled, the range is 5 to
365 days. By default, this value is 30 days.
In
Modify Time
, enter a value. After modifying the modify time, click the Save icon to save the changes. The modify time is
the minimum number of days that must pass since the
file
was last
modified
before the
file
is eligible for data reduction. This
value must be in the range of 30 to 365 days if compression is enabled. If compression is disabled, the range is 5 to 365
days. By default, this value is 30 days.
4.
Click
OK
to save your changes.
5.
Click the Save all changes icon to save your changes.
NOTE: The status of the
filter
is listed as
File filters….disabled
if the
ignore-filters
option was set through the
CLI. If the status is
File filters…disabled
, any
filters
that have been
configured
through the GUI (or CLI) for
Access Time or Modify Time have been disabled and all
files
are candidates for data reduction. Specifying the
ignore-
filters
flag
enables data reduction on a container with archive data without waiting for the minimum Access Time/
Modify Time data-reduction policy. Dell recommends that you not use this setting on containers with live data. That is,
you should use this setting only on containers with archive data.
Create Default Data Reduction Properties
NOTE: To enable or disable data reduction properties at a cluster level, you must have group administrator (grpadmin)
privileges.
To set default data reduction properties at a NAS cluster level:
1.
Click
Group
, expand
Group
Configuration
, and select a NAS cluster.
2.
Click the
Data Reduction
tab.
3.
In the
Default Data Reduction Policy
panel, type or select the necessary data.
About NAS Data Reduction Schedules
Data reduction occurs as a scheduled activity. A data reduction schedule is
defined
at the NAS cluster level and controls when data
reduction is run on all the containers that have data reduction enabled.
You can
define
multiple data reduction schedules at the NAS cluster level. If two or more data reduction schedules overlap, data
reduction begins when the
first
schedule begins running and ends when the last schedule completes running. You can
define
up to a
total of 1024 schedules on each NAS cluster. This total includes all
defined
data reduction, NAS, snapshot, and replication schedules.
You can
configure
a data reduction schedule to
define
the days and times that data reduction begins and ends. If you do not change
the default data reduction schedule settings, data reduction will run every day, starting at midnight and running until 6:00 a.m.
When you
define
a data reduction schedule:
Specify start times and end times in a 12-hour format (such as, 3:30PM, 7AM).
Schedule data reduction during
off-peak
hours to avoid potential performance impact.
When multiple containers have data reduction enabled, data reduction processes
qualified
files
for a
fixed
amount of time starting
with the
first
container. Processing continues on
qualified
files
within the next container, and so on, until data reduction processes all
qualified
files
on each of the enabled containers. If data reduction does not complete on all the enabled containers when the
schedule ends, data reduction continues to process the remaining data when the schedule next runs.
NOTE: To avoid any potential performance impact from running a data reduction process,
define
a schedule to run data
reduction during
off-peak
hours.
For example:
Data reduction is enabled to run on the two containers, NAS_A and NAS_B, of a NAS cluster that is managed by one controller.
When the schedule
finishes
running, if data reduction is being performed on container NAS_B, when the data reduction schedule
begins running the next time, data reduction begins running on container NAS_B. When data reduction completes on NAS_B, the
data reduction service begins running on container NAS_A.
216
NAS Container Operations