Migration policies in the Volume Management application

Migration policies are displayed in the Policies tree in the left pane of the application. They define the data to be migrated. You can create volume management (VM) migration policies and hierarchical storage management (HSM) migration policies. Create migration policies in the Definition pane by defining the migration options and metadata query options to be applied to a given migration policy. Migration options differ depending on the type of migration policy being defined. Options for VM migration policies focus on source and destination volumes. Options for HSM migration policies center around purging methods and third-party storage locations. Use the saved query options to further define the data to be migrated. Both HSM and VM migration policy options allow you to specify criteria using standard Teamcenter saved queries. You can define the queries using standard saved queries for items, item revisions, or datasets. Following are the types of migration policies: VM migration policies Use VM migration policies to migrate and consolidate Teamcenter volume files. Migration options for this method focus on selecting a source and destination volume. You can then either select certain types of data to be migrated, choose to migrate data when specified volume watermark levels are reached, or choose to migrate all files. These migration policies do not necessarily require a third-party HSM system. You can use VM migration policies to emulate HSM functionality without the use of third-party storage systems by migrating infrequently used Teamcenter files off of source volumes and on to destination volumes. The pending file sets defined by VM migration policies are migrated using File Management System (FMS). Alternatively, VM migration policies can be used to loosely couple your third-party migration tool with Teamcenter. Pending migration file sets (VM_Migration files) are exported to a valid operating system directory, either in text or XML format. The third-party migration tool reads the exported file to perform the migration. HSM migration policies Use HSM migration policies to move lower priority files to third-party storage systems. Files stored on secondary and tertiary tiers can be read-accessed without moving them to the highest level. HSM migration requires third-party HSM tool integration and configuration with Teamcenter. Note Read-access from secondary and tertiary tiers is not supported by certain third-party storage systems or certain hardware platforms. For example, the IBM Tivoli HSM product does not provide read-through capability, and the EMC DiskXtender HSM product only provides read-through capability on Windows. In such situations, you must set the HSM_read_thru_supported preference to false and use reverse migration to return files to the primary tier for read access. Migration options for this method include selecting purge options and third-party storage locations. Define the type of data to be migrated by selecting additional migration options (such as re-filed files and checked out objects). Further define data to be migrated by applying saved queries. This method requires that your site implements third-party HSM systems. The HSM migration policies provide the following types of storage strategies: Online primary tier storage Data is stored on third-party HSM software compatible disk media such as simple Windows or Linux SAN attached disks. This is the primary, direct, volume storage location. Near-line secondary tier storage Data is stored on third-party HSM software compatible disk media that can be either simple Windows or Linux SAN attached disks or complex network access storage (NAS) systems from HP, EMC Celerra or NetApp NearStore. Offline tertiary tier Data is stored on third-party HSM software compatible devices such as EMC Centera, WORM drives, Juke Box, and tape drives. HSM pending file sets can be migrated by loosely coupling third-party HSM storage systems with Teamcenter. Pending migration file sets (HSM_Migration files) are exported to a valid operating system directory, either in text or XML format. The HSM storage systems read the exported file to perform the migration. Alternatively, you can tightly couple third-party HSM storage systems with Teamcenter. Pending migration file sets are routed through API (user exit) calls to the HSM storage systems. This method allows you to replace the base user exit extension with a custom extension using Business Modeler IDE. Active and inactive migration policies Active migration policies are displayed under the Policies tree in full color. Only active migration policies can be selected for evaluation and migration. Migration policies are made active at the time they are defined. Inactive policies are grayed out in the Policies tree. Make a migration policy inactive to prevent future evaluations and migrations.