Purpose	Use the age-fileset command to create a simplified age-based fileset for the current volume.
Mode	gbl-ns-vol
Security Level	storage-engineer or crypto-officer
Syntax	age-fileset name no age-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	This command creates a fileset that is only usable in the current volume. To create a global fileset, usable from any namespace or volume, use policy-age-fileset in gbl mode. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-ns-vol-fs-age mode, where you use several commands to define the fileset. You must use the select-files (...-fs-age) command to choose files older than (and/or newer than) 1 hour, 2 days, 20 minutes, or some other interval; this establishes the age. To determine whether the age is based on the last time the files were accessed or the last time they were modified, use the last command. An age fileset selects its files each time a rule uses it. The rules assigned schedule controls when it uses the fileset; each time the rules schedule fires, it assesses every files age from that moment. That is, one hour old or one day old is measured at the moment that the rule runs. The schedule (gbl-ns-vol-plc) command assigns a schedule to a file-placement rule, and the schedule (gbl-ns-vol-shdwcp) command assigns one to a shadow-copy rule.
Sample	bstnA(gbl-ns-vol[medarcv~/rcrds])# age-fileset 24hrs This will create a new policy object.   Create object '24hrs'? [yes/no] yes bstnA(gbl-ns-vol-fs-age[medarcv~/rcrds~24hrs])# ... defines the 24hrs fileset.
Related Commands	policy-age-fileset select-files (...-fs-age) last schedule (gbl-ns-vol-plc) schedule (gbl-ns-vol-shdwcp)

Purpose	** Deprecated ** Use the every command to determine the how frequently the current age fileset re-selects its files. Use no every to select files only when a policy rule (such as a place-rule or a shadow-copy-rule) invokes the fileset.
Modes	gbl-fs-age gbl-ns-vol-fs-age
Security Role(s)	storage-engineer or crypto-officer
Syntax	every count {minutes|hours|days|weeks|months|quarters|years} every {sunday|monday|tuesday| ... |saturday} no every   count (1-2,147,483,647) is the number of minutes, hours, days, etc. between file selections. For example, every 2 minutes or every 5 minutes. minutes| ... years is a required choice. sunday| ... saturday causes the fileset select its files weekly, on the given day of the week.
Default(s)	None; select files whenever the fileset is used by a policy rule (such as a place-rule or a shadow-copy-rule).
Guidelines	This command is deprecated in favor of controlling age selection from the rules schedule. Consider instead using the schedule (gbl-ns-vol-plc) command (for a file-placement rule) or the schedule (gbl-ns-vol-shdwcp) command (for a shadow-copy rule). These assign a schedule to the rule. Every time the assigned schedule fires, the rule reassesses the age-based fileset from the scheduled time. For example, if the schedule fires on 11/12, a month-old file is one that was modified before 10/12; if the schedule fires again in 11/13, a month-old file is one that was modified before 10/13. This command creates a different schedule for file assessment. To continue the example, all month-old files may remain the ones modified before 10/12 for a long time, as determined by the algorithm described below. In most-all cases, it is more intuitive to let the rules schedule determine all file selections.
Guidelines: File-Selection Behavior	This command determines how frequently the policy engine selects files for the current age fileset. At each interval, the policy engine re-selects its files based on the current time. For example, consider a fileset with files older than 1 week that selects its files every 1 day: 1. Saturday: select all files that were modified before last Saturday. 2. Sunday: select all files that were modified before last Sunday. 3. Monday: select files modified before last Monday. 4. ... If the same fileset was evaluated every 2 days, the progression would look like this: 1. Saturday: select all files that were modified before last Saturday. 2. (Sunday: do nothing; keep the selection of all files that were modified before last Saturday.) 3. Monday: select files modified before last Monday. 4. ... The time of day when the files are selected is the start time for the fileset. This is either the time of day when the fileset is invoked by a rule or the fixed time/date set with the start command. The no every command resets this command and start at the same time: it makes the fileset select its files whenever a rule invokes the fileset.
Samples	bstnA(gbl-fs-age[hourOld])# every 1 hours sets an hourly selection interval.   bstnA(gbl-fs-age[sixMonths])# no every reverts to the default; select files whenever the rule runs (as controlled by its schedule). This is considered a best practice.
Related Commands	age-fileset start

Purpose	Use the filename-fileset command to create a name-based fileset for the current namespace volume. Use the no form of the command to delete a name-based fileset.
Mode	gbl-ns-vol
Security Role(s)	storage-engineer or crypto-officer
Syntax	filename-fileset name no filename-fileset name   name (1-1024 characters) is a required name that you assign to the fileset.
Default(s)	None
Guidelines	This command creates a fileset that is only usable in the current volume. To create a global fileset, usable from any namespace or volume, use policy-filename-fileset in gbl mode. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-ns-vol-fs-name mode where you can define the fileset by choosing file names (with name), one or more directory paths within the volume, and/or an option to match files recursively (recurse). By default, a new file-name fileset matches all files in the volumes root directory, but not below it.
Samples	bstnA(gbl-ns-vol[ns~/])# filename-fileset logs This will create a new policy object.   Create object 'logs'? [yes/no] yes creates a name-based fileset, logs.   bstnA(gbl-ns-vol[ns~/])# no filename-fileset logs deletes a name-based fileset, logs.
Related Commands	policy-filename-fileset name path recurse

Purpose	Use the filesize-fileset command to create a size-based fileset for the current volume.
Mode	gbl-ns-vol
Security Level	storage-engineer or crypto-officer
Syntax	filesize-fileset name no filesize-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	This command creates a fileset that is only usable in the current volume. To create a global fileset, usable from any namespace or volume, use policy-filesize-fileset in gbl mode. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-ns-vol-fs-filesize mode, where you use the select-files (...-fs-filesize) command to choose the size range for the filesets files.
Sample	bstnA(gbl-ns-vol[medarcv~/rcrds])# filesize-fileset big This will create a new policy object.   Create object 'big'? [yes/no] yes bstnA(gbl-ns-vol-fs-filesize[medarcv~/rcrds~big])# ... defines the big fileset.
Related Commands	policy-filesize-fileset select-files (...-fs-filesize)

Purpose	Use the from fileset command to include a component fileset into the current union or intersection fileset. Use the no from command to remove a component fileset from the current fileset.
Modes	gbl-fs-isect gbl-ns-vol-fs-isect gbl-fs-union gbl-ns-vol-fs-union
Security Role(s)	storage-engineer or crypto-officer
Syntax	[no] from fileset fileset-name no from [all]   fileset-name (1-1024 characters) is the name of an existing source fileset. all (optional) removes all source filesets from the union or intersection fileset.
Default(s)	None
Guidelines	This command pulls other filesets into the current, compound fileset. The no from all command removes all source filesets at once.
Samples	bstnA(gbl-fs-union[bulky])# from fileset fm_pdf bstnA(gbl-fs-union[bulky])# from fileset veryLarge adds two filesets to a union fileset named bulky. (The bulky fileset is defined in gbl-fs-union mode, so you can use it in any volume.)   prtlndA(gbl-ns-vol-fs-union[nemed~/acctShdw~test])# no from all removes all source filesets from a union fileset named test. (The test fileset is defined within the /acctShdw volume, so it is limited to rules in that volume.)
Related Commands	policy-intersection-fileset intersection-fileset policy-union-fileset union-fileset

Purpose	Use the intersection-fileset command to create an intersection fileset in the current namespace volume. An intersection fileset contains all files that are common to all of its source filesets. Use the no form of the command to delete the intersection fileset.
Mode	gbl-ns-vol
Security Role(s)	storage-engineer or crypto-officer
Syntax	intersection-fileset name no intersection-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	This command creates a fileset that is only usable in the current volume. To create a global-intersection fileset, usable from any namespace or volume, use policy-intersection-fileset in gbl mode. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) An intersection fileset contains files that are common to two or more source filesets. This command places you in gbl-ns-vol-fs-isect mode; from there, use the from fileset (gbl-...-fs-...) command to identify each source fileset.
Samples	bstnA(gbl-ns-vol[ns~/vol])# intersection-fileset xmlViaFtp This will create a new policy object.   Create object 'xmlViaFtp'? [yes/no] yes bstnA(gbl-ns-vol-fs-isect[ns~/vol~xmlViaFtp])# creates an intersection fileset.   bstnA(gbl-ns-vol[archives~/etc])# no intersection-fileset isectTst removes an intersection fileset.
Related Commands	policy-intersection-fileset from fileset (gbl-...-fs-...)

Purpose	Use the last command to set the type of timestamp to use for age-based grouping: last-accessed time or last-modified time.
Modes	gbl-fs-age gbl-ns-vol-fs-age
Security Role(s)	storage-engineer or crypto-officer
Syntax	last {accessed | modified}   accessed | modified is a required choice: accessed is the last-accessed (read) time. modified is the last-modified (written) time.
Default(s)	last modified
Guidelines	The last-accessed time is the time that the file was last read. The last-modified time is the time that the file was last written.
Sample	bstnA(gbl-ns-vol-fs-age[ns~/vol~weeklyHttpLogs])# last accessed sets last-accessed times.
Related Commands	age-fileset

Purpose	Use the name command to select a file name or names for the current name-based fileset. Use no name to erase the selection, thereby matching any file name.
Modes	gbl-fs-name gbl-ns-vol-fs-name
Security Role(s)	storage-engineer or crypto-officer
Syntax	name exact [not] file-name [ignore-case]   name match [not] wild-card-string [ignore-case]   name regexp [not] regular-expression [ignore-case] no name     not (optional) negates the match; this causes the fileset to include all files in the filesets path except any files that match. exact file-name (1-1024 characters) is an exact file name to match. ignore-case (optional) tells the rule to match files without paying attention to case (for example, name exact index.html ignore-case matches index.html and Index.HTML). match wild-card-string (1-1024 characters) uses a wild-card pattern to match multiple file names. See the Guidelines below for your wildcard options. regexp regular-expression (1-1024 characters) uses a more-complex match pattern, based on the ICU standard for regular expressions. This also requires the quotation marks. See the Guidelines below for regular-expression syntax.
Default(s)	match every file in the filesets path
Guidelines	You can use the path command (for example, path exact /var/log) to select a particular directory. You can optionally use the recurse to descend from a path into its subdirectories. The no form of this command makes the fileset match all files in the filesets path(s).
Guidelines: Wildcard-String Options	The wild-card-string uses the following Unix-like shell conventions: * is any string of 0 (zero) or more characters, including an empty string. ? is any single character, or no character. [...] matches any one of the enclosed characters. For example, [xyz] matches x, y, or z. [a-z] matches any character in the sorted range, a through z. [^...] or [!...] matches any character that is not enclosed. For example, [!xyz] matches any character except x, y, or z.
Guidelines: Regular Expressions	The regular-expression syntax follows IBMs ICU conventions. You can use this expression to be extremely specific about your match criteria. At a high level, these are the conventions for ICU regular expressions: .* matches any string, including the null string. .? matches any single character, or no character. [...] matches any one of the enclosed characters. [a-z] matches any character in the sorted range, a through z. [^...] matches any character that is not enclosed. \d matches any digit, 1-9. \s matches any white-space character. \ matches the next character, even if that character is a special character (for example, \? is a literal ?; it is not interpreted). ^... and ...$ match the beginnings and ends of lines, respectively. expression1 | expression2 matches both expressions. For more details, refer to Regular Expression Syntax of the ARX® CLI Storage-Management Guide. Also, you can search the World-Wide Web for instructions on ICU regular expressions.
Samples	bstnA(gbl-fs-name[xmlFiles])# name match *.xml* matches all files with .xml in their names (such as addresses.xml and testData.xmllint.output).   bstnA(gbl-fs-name[xmlFiles])# name regexp \.xml$ matches all files whose names end with .xml (that is, addresses.xml matches but testData.xmllint.output does not).   bstnA(gbl-fs-name[noHTML])# name match not .htm? matches all files except those with .htm or .htmx (where x could be any single character) in their names.   bstnA(gbl-fs-name[httpLogs])# no name matches all files in this filesets path.
Related Commands	policy-filename-fileset filename-fileset path recurse

Purpose	Some back-end CIFS servers use Hierarchical Storage Management (HSM) systems to archive file data on a remote server. A small portion of the file remains on the CIFS server while the bulk of the file is stored remotely. The small, local file has an offline attribute set. Whenever a client (such as the ARX) accesses the file, the HSM restores the full file contents to the CIFS server. A large-scale file migration could restore a large number of offline files all at once, possibly enough to run out of disk space on the back-end CIFS server. You can use the offline command to choose files based on the setting for their offline attribute. You can then exclude files with a raised offline attribute from a place-rule migration.
Mode	gbl-fs-cifs-attr
Security Role(s)	storage-engineer or crypto-officer
Syntax	offline {set | not-set | ignore} no offline   set | not-set | ignore is a required choice: set indicates that files in this fileset are all offline. We do not generally recommend migrating files (see place-rule) with the offline attribute set. The files behavior is dependent on the back-end file server and the HSM; they may or may not restore the full file first. Additionally, assuming that the migration causes the file to be restored first, the change in the file may trigger a higher-priority rule and cancel the migration. not-set matches only files that are online. ignore matches all files, no matter how the offline attribute is set. no offline is equivalent to offline ignore.
Default(s)	no offline
Guidelines	The offline attribute indicates whether or not the file has the bulk of its data stored on a remote server. Use this command in a policy-cifs-attributes-fileset to select all files in a volume based on this attribute setting.
Sample	bstnA(gbl-fs-cifs-attr[online])# offline not-set selects files whose offline attribute is lowered. These files are at full size on the back-end CIFS server.
Related Commands	policy-cifs-attributes-fileset

Purpose	Use the path command to choose one or more directories for the current named-based fileset. This allows you to narrow the fileset scope to one or more directories inside the namespace volume. Only matching files from this directory are included in the fileset. Use no path to revert to the default path.
Modes	gbl-fs-name gbl-ns-vol-fs-name
Security Role(s)	storage-engineer or crypto-officer
Syntax	path exact [not] dir-path [ignore-case]   path match [not] wild-card-string [ignore-case]   path regexp [not] regular-expression [ignore-case] no path     not (optional) negates the match; this causes the fileset to search all paths in the volume except any paths that match. dir-path (1-1024 characters) is an exact path to match. ignore-case (optional) tells the rule to match paths without paying attention to case (for example, path exact /src ignore-case matches /src and /SRC). match wild-card-string (1-1024 characters) uses wild cards to match multiple paths. See the Guidelines below for your wildcard options. regexp regular-expression (1-1024 characters) uses a more-complex match pattern, based on the ICU standard for regular expressions. This also requires the quotation marks. See the Guidelines below for regular-expression syntax.
Default(s)	/ (but no subdirectories) in the volume that uses this fileset.
Guidelines	This command specifies one or more directories for a name-based fileset. Only files in these directories are eligible for inclusion in this fileset. Use the name command to choose the files themselves. By default, this does not recurse; use the recurse command to include all matching subdirectories in the fileset, too. Note that the match and regexp options often create a recursive effect: for example, the path match /var/* command matches /var/, /var/log/, /var/log/httpd/, /var/www/, and any other subdirectory under /var/. The path exact dir-path syntax identifies a single directory, and does not require a full volume scan. All other options (including not and ignore-case) may match multiple directories, so they require more time for a full scan.
Guidelines: Wildcard-String Options	The wild-card-string uses the following Unix-like shell conventions: * is any string of 0 (zero) or more characters, including an empty string. ? is any single character.
Note: The * and the ? match any character, including a / (the Unix delimiter for directories). Therefore, path match /home/*/bin matches /home/juser/bin/ as well as /home/jrandom/misc/bin/.
	[...] matches any one of the enclosed characters. For example, [xyz] matches x, y, or z. [a-z] matches any character in the sorted range, a through z. [^...] or [!...] matches any character that is not enclosed. For example, [!xyz] matches any character except x, y, or z.
Guidelines: Regular Expressions	The regular-expression syntax follows IBMs ICU conventions. You can use this expression to be extremely specific about your match criteria. At a high level, these are the conventions for ICU regular expressions: .* matches any string, including the null string. .? matches any single character. [...] matches any one of the enclosed characters. [a-z] matches any character in the sorted range, a through z. [^...] matches any character that is not enclosed. \d matches any digit, 1-9. \s matches any white-space character. \ matches the next character, even if that character is a special character (for example, \? is a literal ?; it is not interpreted). ^... and ...$ match the beginnings and ends of lines, respectively. expression1 | expression2 matches both expressions. For more details, refer to Regular Expression Syntax of the ARX® CLI Storage-Management Guide. Also, you can search the World-Wide Web for instructions on ICU regular expressions.
Samples	bstnA(gbl-ns-vol-fs-name[ns~/vol~logs])# path exact /var/http/log sets the current fileset to contain files in /var/http/log.   bstnA(gbl-fs-name[httpLogs])# path match /log ignore-case includes any directories with /log in their paths, in any case, such as /var/log and /home/juser/log, or /LOG.   bstnA(gbl-fs-name[noHid])# path regexp not /\.[^\.] includes all directories unless their names start with . followed by some other character.   bstnA(gbl-fs-name[xslfiles])# no path sets the current fileset to contain files in the volumes root, /.
Related Commands	policy-filename-fileset filename-fileset name recurse

Purpose	Use the policy-age-fileset command to create an age-based fileset for any volume.
Mode	gbl
Security Level	storage-engineer or crypto-officer
Syntax	policy-age-fileset name no policy-age-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-fs-age mode, where you use several commands to define the fileset. You must use the select-files (...-fs-age) command to choose files older than (and/or newer than) 1 hour, 2 days, 20 minutes, or some other interval; this establishes the age. To determine whether the age is based on the last time the files were accessed or the last time they were modified, use the last command. An age fileset selects its files each time a rule uses it; you can alter this by setting a regular schedule for file selection. The optional every (...-fs-age) command sets the frequency of these file selections; by the time a rule invokes the fileset, its files are already selected based on an earlier, scheduled time. You can use the start command to set a start date (and time) for this fixed schedule (for example, start the every 10 minutes schedule at noon on January 1st). These commands are deprecated, however, in favor of letting the rules schedule determine file-selection schedule. This type of fileset is available to all namespaces and volumes. To create a similar fileset in a single volume, use age-fileset in gbl-ns-vol mode. You cannot remove this global fileset if any volume or rule uses it.
Samples	bstnA(gbl)# policy-age-fileset weekOld This will create a new policy object.   Create object 'weekOld'? [yes/no] yes bstnA(gbl-fs-age[weekOld])# ... defines the weekOld fileset. Any volume can use this age-based fileset.   bstnA(gbl)# no policy-age-fileset lastMonth bstnA(gbl)# ... removes an age fileset, lastMonth.
Related Commands	select-files (...-fs-age) last every (...-fs-age) start age-fileset

Purpose	Use the policy-cifs-attributes-fileset command to create a fileset based on CIFS attributes. Some CIFS attributes can be important for file migrations, such as the offline attribute. The offline attribute indicates that the files full content is on a remote server, and would need to be fully restored before accessing it for migration. You can use this fileset to select files with particular CIFS attributes and carefully manage their migration.
Mode	gbl
Security Level	storage-engineer or crypto-officer
Syntax	policy-cifs-attributes-fileset name no policy-cifs-attributes-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-fs-cifs-attr mode, where you use the offline command to choose files based on the setting for their CIFS offline attribute. If a file has its CIFS offline bit set, the file has been reduced to a stub with most of its contents archived on another server. The CIFS filer first recovers the full contents of the file if the ARX migrates it. This can fill the CIFS filers disk if it occurs for too many files at once. You can use this fileset to identify all files with this CIFS attribute and migrate them (or avoid migrating them) accordingly. The offline setting is the only supported CIFS attribute in a CIFS-attribute fileset. This type of fileset is available to all namespaces and volumes that support CIFS. This does not apply to an NFS-only namespace, and there is no analogous command in gbl-ns-vol mode. You can combine this fileset with others using policy-union-fileset and policy-intersection-fileset. For example, to select all files with the offline attribute unset and in a particular directory, you can define the particular directory in a policy-filename-fileset, define a set of online files with this command (policy cifs-attributes-fileset) and offline not-set, join the two filesets in an policy-intersection-fileset, and use the intersection fileset in the from (gbl-ns-vol-plc) command of a place-rule. You cannot remove this global fileset if any rule uses it.
Guidelines: Place Rules with this Fileset May Need Schedules	The policy engine only finds the offline-file attribute during a scheduled scan of the volumes back-end filers. There are no inline (client-driven) events that indicate that the attribute changed. Therefore, any place-rule that uses this fileset only assesses the attribute once unless it has a schedule (gbl-ns-vol-plc).
Samples	bstnA(gbl)# policy-cifs-attributes-fileset online   This will create a new policy object.   Create object 'online'? [yes/no] yes bstnA(gbl-fs-cifs-attr[online])# ... defines the online fileset. Any volume can use this attribute-based fileset.   bstnA(gbl)# no policy-filesize-fileset offline_not_set bstnA(gbl)# ... removes an attribute-based fileset, offline_not_set.
Related Commands	offline

Purpose	Use the policy-filename-fileset command to create a name-based fileset for any volume. Use the no form of the command to delete a name-based fileset.
Mode	gbl
Security Role(s)	storage-engineer or crypto-officer
Syntax	policy-filename-fileset name no policy-filename-fileset name   name (1-1024 characters) is a required name that you assign to the fileset.
Default(s)	None
Guidelines	The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This command places you in gbl-fs-name mode where you can define the fileset by choosing file names (with name), one or more directory paths within the volume, and/or an option to descend into matching directories recursively (recurse). By default, a new file-name fileset matches all files in the volumes root directory, but not below it. This type of fileset is available to all namespaces and volumes. To create a similar fileset in a single volume, use filename-fileset in gbl-ns-vol mode. You cannot remove this global fileset if any volume or rule uses it.
Samples	bstnA(gbl)# policy-filename-fileset logs This will create a new policy object.   Create object 'logs'? [yes/no] yes creates a name-based fileset, logs.   bstnA(gbl)# no policy-filename-fileset logs deletes a name-based fileset.
Related Commands	name path recurse filename-fileset

Purpose	Use the policy-filesize-fileset command to create a size-based fileset for any volume.
Mode	gbl
Security Level	storage-engineer or crypto-officer
Syntax	policy-filesize-fileset name no policy-filesize-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-fs-filesize mode, where you use the select-files (...-fs-filesize) command to choose files larger-than (and/or smaller-than) a size of your choosing. This type of fileset is available to all namespaces and volumes. To create a similar fileset in a single volume, use filesize-fileset in gbl-ns-vol mode. You cannot remove this global fileset if any volume or rule uses it.
Samples	bstnA(gbl)# policy-filesize-fileset midsize This will create a new policy object.   Create object 'midsize'? [yes/no] yes bstnA(gbl-fs-filesize[midsize])# ... defines the midsize fileset. Any volume can use this size-based fileset.   bstnA(gbl)# no policy-filesize-fileset 1_to_4_gig bstnA(gbl)# ... removes a filesize fileset, 1_to_4_gig.
Related Commands	select-files (...-fs-filesize) filesize-fileset

Purpose	Use the policy-intersection-fileset command to create an intersection fileset. An intersection fileset contains all files that are common to all of its source filesets. Use the no form of the command to delete the intersection fileset.
Mode	gbl
Security Role(s)	storage-engineer or crypto-officer
Syntax	policy-intersection-fileset name no policy-intersection-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) An intersection fileset contains files that are common to two or more source filesets. This command places you in gbl-fs-isect mode; from there, use the from fileset (gbl-...-fs-...) command to identify each source fileset. This command creates a fileset that is available to all namespaces and volumes. To create a similar fileset in a single volume, use intersection-fileset in gbl-ns-vol mode. You cannot remove this global fileset if any volume or rule uses it.
Samples	bstnA(gbl)# policy-intersection-fileset xmlViaFtp This will create a new policy object.   Create object 'xmlViaFtp'? [yes/no] yes bstnA(gbl-fs-isect[xmlViaFtp])# creates an intersection fileset.   bstnA(gbl)# no policy-intersection-fileset isectTst removes an intersection fileset.
Related Commands	from fileset (gbl-...-fs-...) intersection-fileset

Purpose	Use the policy-union-fileset command to create a union fileset. A union fileset is the union of two or more component filesets. Use the no form of the command to remove the union fileset.
Mode	gbl
Security Role(s)	storage-engineer or crypto-officer
Syntax	policy-union-fileset name no policy-union-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	A union fileset joins two or more source filesets into one. If a file belongs in any of the source filesets, it is also included in the union fileset. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-fs-union mode; from there, use the from fileset (gbl-...-fs-...) command to identify each source fileset. This command creates a fileset that is available to all namespaces and volumes. To create a similar fileset in a single volume, use union-fileset in gbl-ns-vol mode. You cannot remove this global fileset if any volume or rule uses it.
Sample	bstnA(gbl)# policy-union-fileset allLogs This will create a new policy object.   Create object 'allLogs'? [yes/no] yes bstnA(gbl-fs-union[allLogs])# creates a union fileset.
Related Commands	from fileset (gbl-...-fs-...) union-fileset

Purpose	Use the recurse command to include all subdirectories in the current file-name fileset. Use no recurse to include only files in the top directory.
Modes	gbl-fs-name gbl-ns-vol-fs-name
Security Role(s)	storage-engineer or crypto-officer
Syntax	recurse no recurse
Default(s)	no recurse
Guidelines	Use this command to set or unset recursion. If recursion is set, the file-name fileset selects directories and/or files below the root directory. The path command chooses directory paths, and the name command chooses files. If you use recurse in a fileset without any path or name specification, this selects all files in the volume.
Sample	bstnA(gbl-fs-name[logs])# recurse includes files in all subdirectories.
Related Commands	policy-filename-fileset filename-fileset name path

Purpose	A size-based fileset chooses a group of files based on their sizes. Use the select-files command to choose the sizes for the current fileset.
Modes	gbl-fs-filesize gbl-ns-vol-fs-filesize
Security Level	storage-engineer or crypto-officer
Syntax	select-files {larger-than-or-equal-to | smaller-than} size[k|M|G|T] no select-files {larger-than-or-equal-to | smaller-than}   larger-than-or-equal-to | smaller-than is a required choice. This determines whether the selected files are larger or smaller than the size that follows. size is the size in bytes, KiloBytes, MegaBytes, or whatever units you specify (see below). k|M|G|T (optional) specifies units; k for KiloBytes (1024 bytes), M for MegaBytes (1024*1024 bytes), G for GigaBytes (1024*1024*1024), and T for TeraBytes (1024*1024*1024*1024). Do not put any space between the size number and this unit (for example, 100k is valid but 100 k is not). The default is bytes.
Default(s)	None
Guidelines	The select-files command is the only required step in configuring a size-based fileset. You can use this command twice to define a size range (for example, to select files larger than 50 MegaBytes but smaller than 1 Gigabyte). The CLI rejects a select-files command that contradicts an existing select-files command: you cannot select files smaller-than 1 MegaByte if you have already selected files larger-than or equal-to 2 GigaBytes.
Sample	bstnA(gbl-ns-vol-fs-filesize[midsize])# select-files larger-than-or-equal-to 20M bstnA(gbl-ns-vol-fs-filesize[midsize])# select-files smaller-than 50M selects all files that are between 20 and 50 MegaBytes.
Related Commands	policy-filesize-fileset filesize-fileset

Purpose	An age-based fileset chooses a single group of files based on time stamps: those newer or older than a certain interval (such as older than 1 day) or between two intervals (for example, newer than 2 weeks and older than 1 day). Use the select-files command to set the selection criteria.
Modes	gbl-fs-age gbl-ns-vol-fs-age
Security Level	storage-engineer or crypto-officer
Syntax	select-files {older-than | newer-than} interval {minutes | hours | days | weeks | months | quarters | years}   no select-files {older-than | newer-than}     older-than | newer-than is a required choice. This determines whether the selected files are older or newer than the time interval that follows. interval (1-2,147,483,647) is the number of minutes, hours, days, etc., that selected files are older than or newer than. minutes | ... years is a required choice.
Default(s)	None
Guidelines	The select-files command is the only required step in configuring an age-based fileset. Without any selection criteria, the fileset includes all files. You can use this command twice to define an age range (for example, to select files older than 1 week but newer than 1 year). The CLI rejects a select-files command that contradicts an existing select-files command: you cannot select files newer than 6 hours if you have already selected files older than 3 weeks. Each file has two time stamps: last-accessed time and last-modified time. This command measures against the time stamp selected with the last command. By default, this selects from every file in the current managed volume. To limit the files to those in some other fileset (for example, to choose only from a filename-fileset containing .wmv files), use the from fileset (gbl-...-fs-...) command. By default, the policy engine runs this file selection whenever it is invoked by another rule (such as a place-rule or a shadow-copy-rule). For example, if the fileset is composed of files newer than 1 month and a file-placement rule uses it on September 30, it includes all files modified since August 31. If the file-placement rule runs again on October 5, the fileset re-selects its files: at this point, it holds all files modified since September 5, 1 month before October 5. You can use the every (...-fs-age) command to make the file re-selections happen at a fixed rate (for example, every 2 days).
Sample	bstnA(gbl-ns-vol-fs-age[ns~/vol~24hrs])# select-files older-than 24 hours identifies all files that are older than 24 hours in the age-based fileset.
Related Commands	policy-age-fileset age-fileset

Purpose	Use the show policy filesets command to view fileset configurations.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show policy filesets show policy filesets global-fileset fileset-name show policy filesets namespace namespace volume volume fileset fileset-name   global-fileset fileset-name (optional, 1-1024 characters) focuses the command on a single, global fileset. namespace namespace volume volume fileset fileset-name focuses on a single, volume-level fileset. namespace (1-30 characters) is the filesets namespace, volume (1-1024 characters) is the filesets volume path, and fileset-name (1-1024 characters) is the fileset..
Guidelines	If you do not enter a specific fileset, this command displays all filesets. The globally-defined filesets appear first, followed by a section for each namespace and volume. Each volume-level fileset (such as a age-fileset) appears with its volume. For each fileset, a single Configuration table shows all of the administratively-set parameters for the fileset. You can create or edit each fileset type with a separate command: Filename Fileset with policy-filename-fileset, Age Fileset with policy-age-fileset, Fileset Intersection with policy-intersection-fileset, or Fileset Union with policy-union-fileset.
	The remaining fields show the configuration parameters for the fileset, and the number of rules that use the fileset.
Samples	bstnA# show policy filesets shows all filesets. See Figure 26.1 for sample output.   bstnA# show policy filesets global-fileset veryLarge shows one globally-defined fileset, veryLarge. See Figure 26.2 on page 26-31 for sample output.   bstnA# show policy filesets namespace insur volume /claims fileset images shows a single fileset in the insur~/claims volume.
Related Commands	policy-filename-fileset policy-age-fileset policy-intersection-fileset policy-union-fileset

Purpose	** Deprecated ** For age-based filesets, use the start command to set a start time for grouping files. Use no start to select files each time a rule uses the fileset.
Modes	gbl-fs-age gbl-ns-vol-fs-age
Security Role(s)	storage-engineer or crypto-officer
Syntax	start [mm/dd/yyyy:HH:MM:SS] no start   mm/dd/yyyy sets a start date (for example, date 05/25/2003). HH:MM:SS sets a start time (for example, 06:00:00).
Default(s)	Whenever the fileset is used by a policy rule (such as a place-rule or a shadow-copy-rule).
Guidelines	This command is deprecated in favor of controlling age selection from the rules schedule. Consider instead using the schedule (gbl-ns-vol-plc) command (for a file-placement rule) or the schedule (gbl-ns-vol-shdwcp) command (for a shadow-copy rule). These assign a start time and a schedule to the rule. In most-all cases, it is more intuitive to let the rules schedule determine start times and file selections.
Guidelines: Effects on Time Calculations	This command sets a starting point for all age-based calculations. For example, if you have a fileset that re-evaluates every 7 days, this determines the starting point and the time of day for each evaluation (Mondays at 2AM, Fridays at 5PM, or some other day and time). The evaluation chooses files that belong in the fileset. By default, this occurs at the time the fileset is used by a rule. If you set a start date/time in the future, the fileset waits until that time to start grouping files.
Sample	bstnA(gbl-fs-age[monthOld])# start 05/06/2003:23:00:00 sets a start date of May 6, 2003, at 11PM.
Related Commands	age-fileset every (...-fs-age)

Purpose	Use the union-fileset command to create a union fileset in the current namespace volume. A union fileset is the union of two or more component filesets. Use the no form of the command to remove the union fileset.
Mode	gbl-ns-vol
Security Role(s)	storage-engineer or crypto-officer
Syntax	union-fileset name no union-fileset name   name (1-1024 characters) is the name you choose for the fileset.
Default(s)	None
Guidelines	A union fileset joins two or more source filesets into one. This command creates a fileset that is only usable in the current volume. To create a global-union fileset, usable from any namespace or volume, use policy-union-fileset in gbl mode. The CLI prompts for confirmation before creating a new fileset; enter yes to continue. (You can use terminal expert to eliminate confirmation prompts for creating new policy objects.) This places you in gbl-ns-vol-fs-union mode; from there, use the from fileset (gbl-...-fs-...) command to identify each source fileset.
Sample	bstnA(gbl-ns-vol[ns~/vol])# union-fileset allLogs This will create a new policy object.   Create object 'allLogs'? [yes/no] yes bstnA(gbl-ns-vol-fs-union[ns~/vol~allLogs])# creates a union fileset.
Related Commands	policy-union-fileset from fileset (gbl-...-fs-...)