The examples in this section can help you understand how to configure policy rules to achieve your desired outcome for moving data in a pair:
In this example, the filter identifies files with sizes of at least 10 megabytes. All files that meet this file size criterion are moved in a specified direction, such as from primary to secondary. The file access and modification times and file patterns are not considered.
Table 9-5 Policy to Move All Files Larger than 10 Megabytes
Option |
Setting |
---|---|
Direction |
Primary to secondary |
File size |
|
Last accessed |
Not selected. |
Last modified |
Not selected. |
File patterns |
Not selected. |
File types |
Not selected. |
File owners |
Not selected. |
In this example, the filter identifies files with sizes of at least 10 megabytes and with a file extension of .mp3. Only the files that meet both the size and extension criteria are moved in the specified direction, such as from primary to secondary. The file access and modification times are not considered.
Table 9-6 Policy to Move All MP3 Files Larger than 10 Megabytes
Option |
Setting |
---|---|
Direction |
Primary to secondary |
File size |
|
Last accessed |
Not selected. |
Last modified |
Not selected. |
File patterns |
|
File types |
Not selected. |
File owners |
Not selected. |
In this example, the filter identifies files with sizes of at least 10 megabytes, with a Last Modified setting that is at least 6 months ago, and with a file extension of .mp3. Only the files that meet all three criteria are moved in a specified direction, such as from primary to secondary. The file modification times are not considered.
Table 9-7 Policy to Move All MP3 Files Larger than 10 Megabytes That Were Last Modified More than 6 Months Ago
Option |
Setting |
---|---|
Direction |
Primary to secondary |
File size |
|
Last accessed |
Not selected. |
Last modified |
|
File patterns |
|
File types |
Not selected. |
File owners |
Not selected. |
In this example, the filter identifies all files with any extension and moves them in the specified direction, such as from primary to secondary. All files are moved because there are no other filters to be considered.
Table 9-8 Policy to Move All Files
Option |
Setting |
---|---|
Direction |
Primary to secondary |
File size |
Not selected. |
Last accessed |
Not selected. |
Last modified |
Not selected. |
File patterns |
|
File types |
Not selected. |
File owners |
Not selected. |
In this example, assume that you want to keep recently modified files on the faster storage where the primary path resides. You separate the files in a pair based on the file Last Modified dates, with recently modified files on the primary path and the static files on the secondary path. As noted elsewhere, files are served to users directly from whichever location the file resides when the file is accessed via the network share on the primary path. If a file is modified on the secondary path, its Last Modified date changes, but it is not automatically moved back to the primary path.
To achieve the goal, you set up one policy to move static files from the primary path to the secondary path, and one policy to recently modified files from the secondary path to the primary path.
In this policy, specify a direction of primary to secondary, and a last modified date of greater than 1 year. Run this policy monthly (or at a preferred frequency) during non-peak hours (such as Sunday at 12:00 a.m. until complete) to locate and move static files to the secondary path.
Table 9-9 Policy to Move Files That Were Last Modified More than 1 Year Ago from Primary to Secondary
Option |
Setting |
---|---|
Direction |
Primary to secondary |
File size |
Not selected. |
Last accessed |
Not selected. |
Last modified |
|
File patterns |
Not selected. |
File types |
Not selected. |
File owners |
Not selected. |
In this policy, specify a direction of secondary to primary, and a last modified date of less than 1 week. Run this policy weekly during non-peak hours (such as Sunday at 12:00 a.m. until complete) to move recently modified files back to the primary path.
Table 9-10 Policy to Move Files That Were Last Modified Less than 1 Week Ago from Secondary to Primary
Option |
Setting |
---|---|
Direction |
Secondary to primary |
File size |
Not selected. |
Last accessed |
Not selected. |
Last modified |
|
File patterns |
Not selected. |
File types |
Not selected. |
File owners |
Not selected. |
In this example, suppose that you have existing storage and you want to move all files to a newer, faster storage disk. You do not plan to keep the existing storage after the move.
To achieve the goal, you set up a pair where the primary path is on the new disk, and the secondary path is on the old disk. The network share is configured (or reconfigured) for the primary path, which gives users access to all of the files via the merged view while DynamicFS migrates the files in off-peak hours.
You set up a policy with *.* (Move all files) in the filter option, and specify a direction of secondary to primary. This moves files with and without file extensions. Run the policy nightly during non-peak hours (such as at 12:00 a.m. for 4 hours). After all of the files have been moved to the primary location, the pair can be unlinked.
Table 9-11 Policy to Move All Files from Older to Newer Storage
Option |
Setting |
---|---|
Direction |
Secondary to primary |
File size |
Not selected. |
Last accessed |
Not selected. |
Last modified |
Not selected. |
File patterns |
|
File types |
Not selected. |
File owners |
Not selected. |