Migration jobs

A migration job specifies which files to migrate and whether to leave a stub file on the originating file system.

You can specify the files to migrate by using the HSM for Windows client GUI or the HSM for Windows client dsmclc.exe command.

With the HSM for Windows client GUI, you can browse local file systems. You can exclude or include parts of the directory structure in a migration job. For each selection, filters can be applied to include or exclude files. The inclusion or exclusion can be based on file criteria:

File type
File size
File creation date
File modification date
File access date

Each migration job is stored in an XML structured job file. The actual migration can be scheduled by using any standard scheduler, or it can be started manually from a Command Prompt window. In addition, the HSM for Windows client administrator can start a migration job directly from the HSM for Windows client GUI.

When you decide what files to include in a migration job, consider both the frequency of use of the files and the recall speed. Although most file recall is not noticed by users, network bandwidth, storage repository speed, and file size all determine the file recall speed.

A migration job file can be shared among computers with similar configurations, and can be shared among nodes in a cluster. If some directory structure of two computers is the same, you can use without modification a migration job that specifies the common directory structure on both computers.