Running a migration task, Additional rule examples – HP StoreAll Storage User Manual

Page 185

Advertising
background image

Additional rule examples

The following rule migrates all files from Tier2 to Tier1:

name="*"

The following rule migrates all files in the subtree beneath the path. The path is relative to the
mountpoint of the file system.

path=testdata2

The next example migrates all mpeg4 files in the subtree. A logical “and” operator combines the
rules:

path=testdata4 and name="*mpeg4"

The next example narrows the scope of the rule to files owned by users in a specific group. Note
the use of parentheses.

gname=users and (path=testdata4 and name="*mpeg4")

For more examples and detailed information about creating rules, see

“Writing tiering rules”

(page 191)

.

Running a migration task

Migrating files from one tier to another must be initiated manually. Migration tasks cannot be
scheduled to run using X9000 commands. Once started, a migration task passes once through
the filesystem then stops. It is possible to use external job control software to run a migration task
on a schedule if required.

Only one migration task can run on a file system at any time. The task is not restarted on failure,
and cannot be paused and later resumed. However, a migration task can be started when a server
is in the InFailover state.

To start a migration task from the GUI, select the file system from the Filesystems panel and then
select Data Tiering in the lower Navigator. Click New on the Task Summary panel. The counters
on the panel are updated periodically while the task is running.

If necessary, click Stop to stop the data tiering task. There is no pause/resume function. When the
task is complete, it appears on the GUI under Inactive Tasks for the file system. You can check the
exit status there.

Running a migration task 185

Advertising