The MIGRATE_CONTENT administration method migrates content files from one storage area to another.
The MIGRATE_CONTENT method requires superuser privileges to migrate:
Single content objects.
Single sysobjects.
Sets of content objects qualified by a DQL predicate against dmr_content.
Set of content objects qualified by a DQL predicate against dm_sysobject or its subtypes.
All content in a file store.
Use the MIGRATE_CONTENT administration method to move content from file stores, retention type stores, blob stores, and distributed stores to file stores, retention type stores, and distributed stores. Documentum Administrator 6.5 SP2 and later supports migration from external stores. You cannot move files to a blob store. The storage areas can be online, offline, or read-only.
Before running MIGRATE_CONTENT:
Ensure that all objects to be migrated are checked in to the repository. If you migrate any checked-out objects, check-in fails because of mismatched versions.
Ensure that the file store to which you migrate objects has sufficient disk space for the migration.
Before you migrate a file store, use the SET_STORAGE_STATE administration method to mark it READ-ONLY. If the source file store has associated full-text indexes, the target file store must also have full-text indexes. Documentum Administrator does not allow you to select a target file store without full-text indexes.
The MIGRATE_CONTENT method returns an integer indicating the number of objects migrated successfully.
Regardless of the mode in which MIGRATE_CONTENT is run, the original content file can be removed or left in the source file store. If you do not have the file removed, you must specify the path to a log file that logs the path of the source content file. Those files can be removed at another time using Dmfilescan.
To migrate a single object:
Navigate to Administration > Job Management > Administration Methods.
The system displays the Administration Methods list page.
Click MIGRATE_CONTENT.
The system displays the Parameters page.
Specify the parameters for moving the single object, as described in Table 7.13.
Click Run.
Table 7.13. Parameters for moving a single object
| Field | Description |
|---|---|
| Migrate | Select A single object from the drop-down list. |
| Content | Click Select Object, then select an object type from the Select From drop-down list. Specify a limiting Where clause, or leave the Where field blank to select from all objects in the repository. To display all object versions, select the Use all versions checkbox and then click Go. Select the objects to migrate and click Add. Select Remove the original source to remove the original content file. The Remove the original source option cannot be edited, if the selected object belongs to an external store. |
| Path | Click Select Path and select a location on the server file system for the log file path. |
| Target | Select a target file store from the drop-down list. |
| Source Direct Access | Specifies whether the content files in the source store can be directly accessed through a full file path. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Migrate With | Specifies whether the source content is copied or moved to the target store during migration. Direct Move is applicable to file stores only. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Update Only | This option is used only in conjunction with the Direct Copy or Direct Move option. When selected, move or copy commands are written to the log file specified in the Command File Name field. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Command File Name | A string that specifies a file path to a log file. This option is only available if the Source is an external store and the Target is either a file store or a ca store and if the Update Only option is selected. |
To migrate all content files in a file store:
Navigate to Administration > Job Management > Administration Methods.
The system displays the Administration Methods list page.
Click MIGRATE_CONTENT.
The system displays the Parameters page.
Specify the parameters for moving the content, as described in Table 7.14.
Click Run.
Table 7.14. Parameters for moving all content in a store
| Field | Description |
|---|---|
| Migrate | Select All content in a filestore from the drop-down list. |
| Source | Select a source file store from the Source drop-down list. Select Remove the original source to remove the original content file. The Remove the original source option cannot be edited, if the selected object belongs to an external store. |
| Path | Click Select Path and select a location on the server file system for the log file path |
| Target | Select a target file store from the drop-down list. |
| Maximum | Specifies the maximum number of objects to migrate. The default is to migrate all objects. |
| Batch Size | Specifies the number of objects migrated in a single transaction. The default value is 500. Multiple transactions are run until the maximum number of objects to migrate is reached. |
| Content Migration Threads | Specifies the number of internal sessions used to execute the method. The default value is 0, indicating that the migration executes sequentially. The value cannot exceed the Maximum Content Migration Threads value in the server configuration object. This option is only available if a Content Storage Services license is enabled on the Content Server. |
| Source Direct Access | Specifies whether the content files in the source store can be directly accessed through a full file path. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Migrate With | Specifies whether the source content is copied or moved to the target store during migration. Direct Move is applicable to file stores only. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Update Only | This option is used only in conjunction with the Direct Copy or Direct Move option. When selected, move or copy commands are written to the log file specified in the Command File Name field. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Command File Name | A string that specifies a file path to a log file. This option is only available if the Source is an external store and the Target is either a file store or a ca store and if the Update Only option is selected. |
To migrate objects selected by a query:
Navigate to Administration > Job Management > Administration Methods.
The system displays the Administration Methods list page.
Click MIGRATE_CONTENT.
The system displays the Parameters page.
Specify the parameters for moving the content, as described in Table 7.15.
Click Run.
Table 7.15. Parameters for moving content selected by a query
| Field | Description |
|---|---|
| Migrate | Select All content satisfying a query from the drop-down list. |
| Select Object Type to Migrate | Specify the object type to migrate. If you select dm_sysobject or it’s subtype, click Select to access the Choose a type page to select a subtype of dm_sysobject. |
| Select r_object_id from dmr_content where | Specify the DQL query. Select Remove the original source to remove the original content file. The Remove the original source option cannot be edited, if the selected object belongs to an external store. |
| Path | Click Select Path and select a location on the server file system for the log file path |
| Target | Select a target file store from the drop-down list. |
| Maximum | Specifies the maximum number of objects to migrate. The default is to migrate all objects. |
| Batch Size | Specifies the number of objects migrated in a single transaction. The default value is 500. Multiple transactions are run until the maximum number of objects to migrate is reached. |
| Content Migration Threads | Specifies the number of internal sessions used to execute the method. The default value is 0, indicating that the migration executes sequentially. The value cannot exceed the Maximum Content Migration Threads value in the server configuration object. This option is only available if a Content Storage Services license is enabled on the Content Server. |
| Source Direct Access | Specifies whether the content files in the source store can be directly accessed through a full file path. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Migrate With | Specifies whether the source content is copied or moved to the target store during migration. Direct Move is applicable to file stores only. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Update Only | This option is used only in conjunction with the Direct Copy or Direct Move option. When selected, move or copy commands are written to the log file specified in the Command File Name field. This option is only available if the Source is an external store and the Target is either a file store or a ca store. |
| Command File Name | A string that specifies a file path to a log file. This option is only available if the Source is an external store and the Target is either a file store or a ca store and if the Update Only option is selected. |
If the MIGRATE_CONTENT method fails with an error, the entire batch transaction is rolled back. If the destination has content files that were created from the successful migrations within the batch, you can clean up those files running the Dmfilescan job, as described in Dmfilescan (dm_DMfilescan).