Administrator Guide

Table Of Contents
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 le was last modied before the le 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 lter is listed as File filters….disabled if the ignore-lters option was set through the
CLI. If the status is File filters…disabled, any lters that have been congured through the GUI (or CLI) for
Access Time or Modify Time have been disabled and all les are candidates for data reduction. Specifying the ignore-
filters ag 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 Conguration, 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 dened at the NAS cluster level and controls when data
reduction is run on all the containers that have data reduction enabled.
You can dene multiple data reduction schedules at the NAS cluster level. If two or more data reduction schedules overlap, data
reduction begins when the rst schedule begins running and ends when the last schedule completes running. You can dene up to a
total of 1024 schedules on each NAS cluster. This total includes all dened data reduction, NAS, snapshot, and replication schedules.
You can congure a data reduction schedule to dene 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 dene a data reduction schedule:
Specify start times and end times in a 12-hour format (such as, 3:30PM, 7AM).
Schedule data reduction during o-peak hours to avoid potential performance impact.
When multiple containers have data reduction enabled, data reduction processes qualied les for a xed amount of time starting
with the rst container. Processing continues on qualied les within the next container, and so on, until data reduction processes all
qualied les 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, dene a schedule to run data
reduction during o-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 nishes 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