Documentum : Moving Content Files via Migration Policy (3/3)

Hello,

After, the posts Documentum : Moving Content Files via Administration Method MIGRATE_CONTENT (1/3) and Documentum : Moving Content Files via Records Migration Job (2/3) concerning respectively the content’s migration via MIGRATE_CONTENT administration method and via Records Migration Job, I propose to focus on content’s migration via Migration Policy.
 
Reminder, Content Server supports three ways to move content files:

• 1. MIGRATE_CONTENT administration method
• 2. Records migration job
• 3. Migration Policy (need of Documentum Content Storage Services license)

3. MIGRATION POLICY (JOB)
 

The content migration policies needs Content Storage Services license and are implemented as jobs. These jobs automate the movement of content files from one storage area to another by:

• specify the target storage area which wil store the selected content files
• specify the selection criteria for the content to be moved
• specify how many content files you want to move in one execution
• specify the maximum number of files to move in one execution

Content Storage Services / Centera
In addition to the standard services described above, Content Server also offers the following optionally licensed functionalities. It is possible to add an optional storage policy engine via Content Storage Services (CSS) to automate storage allocation and migration based on policies. For example, frequently accessed content can be stored in a high-performance storage environment while rarely accessed content can be migrated to a more economical storage environment based on configured policies.

• Content Services for EMC Centera (CSEC) adds support for Centera storage for guaranteed retention and immutability. Centera storage is suitable for storing large amounts of infrequently changing data that needs to be retained for a specific period.
   
• Content Storage Services (CSS) enables the use of content storage and migration policies, which automate the assignment of content to various storage areas. CSS can be used for optimizing the use of storage infrastructure in the enterprise. CSS also provides features for content compression and de-duplication.
  In DA, under “Store Management / Migration Policies”:
  
Store Management:
+ Storage
+ Assignment Policies
+ Migration Policies


 
 
The procedure of creation is detailed from page 322 in the “Administrator Version 7.2 User Guide” http://www.emc.com/collateral/TechnicalDocument/docu57878.pdf, however, you would find below several important points:

• The selection of objects for migration is possible via:
  • the selection criteria in the rules section of migration policy job to migrate documents from one store to another,
  • OR selection of migrating objects older than months based on creation date, modify date or access date of the document,
  • OR specification of a DQL predicate that could be a valid where clause to migrate specific objects:
    
DQL query selection / Move content objects only(dmr_content)
WHERE : any parent_id IN (SELECT r_object_id from my_document (ALL) WHERE any r_aspect_name = 'my_aspect_java') AND storage_id NOT IN (select r_object_id from dm_ca_store where name='centera_store_no_retention')


   

• The migration policy job does not update the r_modify_date and r_modifier fields of target objects type with the dm_query based on dm_document
   
• The migration policy job moves also the renditions of content.
   
• Migration policies are jobs that execute the MIGRATE_CONTENT administration method. The Records policy jobs use the system Administration method dm_MoveContent.
   

Here, an example of execution report available in :

SELECT * FROM dm_sysobject WHERE folder('/Temp/Jobs/My_ArchivingMigrationPolicy') ORDER BY r_creation_date DESC;


Best regards,

Huseyin