Keywords

Data Migrator Administration Guide for Hitachi NAS Platform

Version
14.9.x
Audience
anonymous
Part Number
MK-92HNAS005-32

The following table describes the keywords and their related values that can be used to build rule statements. Each keyword can be defined in the rule with an INCLUDE or EXCLUDE statement to indicate how the keyword values are to be applied.

Keyword

Value(s)
FILENAME

Names and types of files contained in the rule. Separate multiple names by commas. FILENAME values may start or end with a “*” wildcard character to indicate all files starting/finishing with specific characters.

Usage:

FILENAME will often be used with an INCLUDE statement to ensure that non-essential files are migrated to secondary storage. It can also be used with an EXCLUDE statement to prevent specific important data sets from being migrated.

For example:

<FILENAME *.mp3,*.txt,*filename, filename*>

PATH Specifies literal paths to which a rule applies. Values must be full paths, starting with a forward slash (/). Separate multiple paths by commas. PATH values may end with a “*” wildcard character to indicate all subdirectories under the specified path.

Usage:

When used in an INCLUDE statement, PATH specifies directories to migrate. This is useful when migrating less-critical directories such as temp or home directories. When used in an EXCLUDE statement, directories can be excluded from migration, leaving all the files within on primary storage.

For example:

<PATH /temp/*,/home*,/other/dir*>

USERNAME

Specifies user names to which a rule applies. Values must be valid Windows or UNIX user names. Separate multiple names by commas.

Usage:

When used in an INCLUDE statement, USERNAME specifies the user name of file owners whose files are to be migrated. This is useful when migrating files owned by a particular user. When used in an EXCLUDE statement, users can be excluded from migration, leaving all the files owned by the specified user(s) on primary storage.

Windows user names are specified in the form domain\username.
Note: Backslashes in user names should not be escaped (double backslashes are not required).

For example: jjames, myco\smithr, myco\wsmith

Note: The USERNAME keyword is not supported for cloud data migration rules.
FILE_SIZE_OVER

Identifies a subset of files in a rule with sizes crossing an upper threshold. The threshold value is appended to the keyword and defined by the threshold size in B, KB, MB, or GB.

Usage:

This will likely be used with INCLUDE statements to ensure files of very large sizes are migrated to secondary storage.

For example:

<FILE_SIZE_OVER 4GB>

FILE_SIZE_UNDER

Identifies a subset of files in a rule with sizes crossing a lower threshold. The threshold value is appended to the keyword and is defined by the threshold size in B, KB, MB, or GB.

Usage:

This will usually be used in an EXCLUDE statement to ensure that very small files are not migrated en masse. Migrating small files that take up little space provides minimal value in extending the efficiency of primary storage.

For example:

<FILE_SIZE_UNDER 10KB>

OLDER_THAN

Identifies files that were created more than a specified number of days in the past (files older than x days). The value is appended to the keyword and defines the number of days within which the activity has occurred from the current date and time

Usage:

Used primarily in INCLUDE statements to ensure that older files are migrated.

For example:

<OLDER_THAN 28>

NEWER_THAN

Identifies files that were created less than a specified number of days in the past (files newer than x days). The value is appended to the keyword and defines the number of days within which the activity has occurred from the current date and time.

Usage:

Used primarily in EXCLUDE statements to ensure that newer files are not migrated.

For example:

<NEWER_THAN 14>

INACTIVE_OVER

Identifies files that have not been accessed within a specific number of days. A file’s last access time is updated whenever the file is read or modified. The value is appended to the keyword and defines the number of days of inactivity from the current date and time.

Usage:

Used primarily in INCLUDE statements to ensure that older, less frequently used files are migrated.

For example:

<INACTIVE_OVER 21>

ACTIVE_WITHIN

Identifies files accessed within a specific number of previous days. A file’s last access time is updated whenever the file is read or modified. The value is appended to the keyword and defines the number of days of inactivity from the current date and time.

Usage:

Used primarily in EXCLUDE statements to prevent actively used files from being migrated.

For example:

<ACTIVE_WITHIN 30>

UNCHANGED_OVER

Identifies files not modified within a specific number of previous days. A file’s modification time is updated whenever the file’s contents have been changed. The value is appended to the keyword and defines the number of days of inactivity from the current date and time.

Usage:

Used primarily in INCLUDE statements to ensure that older, less frequently used files are migrated.

For example:

<UNCHANGED_OVER 14>

CHANGED_SINCE

Identifies files modified within a specific number of previous days. A file’s last access time is updated whenever the file’s contents have been changed. The value is appended to the keyword and defines the number of days of inactivity from the current date and time.

Usage:

Used primarily in EXCLUDE statements to prevent actively used files from being migrated.

For example:

<CHANGED_SINCE 7>