Introduction to migrating volume data

After defining the data to be migrated, you can migrate the data to the specified location. Migrating data involves previewing the migration results, marking the files for migration, and then migrating the data. Previewing migration results allows you to sort your volume files based on specified migration policies and review the list of files to be migrated. Use the preview functionality to run what if scenarios to assess the impact of a specific migration policy before implementing the migration. For example, if you change the last access date of a migration policy from 90 days to 200 days, you can easily determine how much more data will be moved between tiers or volumes by running a preview. You can print the result or save the results to a file. When you are satisfied with the migration results, you can mark the files for migration and migrate the files. Note For better performance, mark files for migration using the mark_for_migrate utility rather than the Mark for Migration button in the Volume Management application. You can run this utility overnight using a Windows at command or running a Linux cron job. Migration methods differ depending on whether you are migrating data from a volume management (VM) migration policy or a hierarchical storage management (HSM) migration policy. VM migration policies can be migrated using one of the following methods: FMS-based migration uses the FSC process to migrate files from the source volume to the destination volume. This method does not require a third-party migration tool and works without additional configuration. Basic migration loosely couples 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. Note Before using this method, your third-party migration tool must be configured to work with Teamcenter. Tip Before migrating VM migration policies, use the review_volumes utility to delete unreferenced files. HSM migration policies can be migrated using one of the following methods: Basic migration loosely couples 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. Tip Before migrating VM migration policies, use the review_volumes utility to delete unreferenced files. API-based migration tightly couples 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 the Business Modeler IDE. Use the HSM_migrate_files_msg operation (under HSM_Policy business objects) in the Business Modeler IDE.