Configuring migration policy rules

Rules can be standard rules, created by making choices from drop-down lists, or they can be custom rules, which use DQL predicates. Custom rules can select content to be migrated only from dm_sysobject and dmr_content objects. SysObject subtypes are not supported.

Specify the migration policy rules, as described in Table 11.16.

Table 11.16. Migration policy Rules tab properties

Field	Description
Selected Objects
Simple selection	Creates a migration rule based on preset values, such as format, creation date, modification date, access date, or size.
Move objects where	Specifies which objects to move. Select one of the criteria from the drop-down list, as follows: format: Migrates objects of a particular format. Click Select and then select the correct format. created: Migrates objects according to creation date. modified: Migrates objects according to their modification date. accessed: Migrates objects according to the date they were last accessed. size: Migrates objects according to their size in bytes. Enter the number of bytes. For the created, modified and accessed operands, the number of days is always in relation to the date the job is scheduled to run. Valid operands are: Exactly: Migrates objects modified exactly the number of days before. More than: Migrates objects modified more than the number of days before. Less than: Migrates objects modified less than the number of days before.
Renditions to include	Specifies whether to migrate Primary or Secondary renditions or both. The rendition option is only available in conjunction with the created, modified, or accessed selection criteria.
DQL query selection	Creates a migration rule based on a DQL query. Custom rules can select content to be migrated from dm_sysobject, its subtypes, and dmr_content objects.
Move specified type	Select to migrate the content associated with SysObjects (dm_sysobject) and its subtypes. When selected, you must also select to migrate primary or secondary renditions, or both.
Move content objects only	Select to migrate the content associated with content objects (dmr_content).
Where	Type a rule into the text box. Specify a DQL predicate and whether the predicate runs against content associated with SysObjects, its subtypes, or content objects.
Renditions to include	If you selected Move specified types, select to migrate Primary or Secondary renditions or both.
Move options
Target Store	The destination storage area to which the content files migrate. Select a store from the drop-down list. The list includes file stores and retention stores (EMC Centera and NetApp SnapLock).
Batch Size	The number of content files to include in a single transaction during the migration operation. The default value is 500.
Maximum Count	The maximum number of content files to transfer. To specify an unlimited number of documents, type a zero [`0`] or leave the field blank.
Content Migration Threads	The number of internal sessions to use to execute the migration policy. The default value is 0, indicating that migration executes sequentially. This field displays only if you have a Content Storage Services license and the license is enabled on the Content Server. The Content Migration Threads value cannot exceed the Maximum Content Migration Threads value in the server configuration object (dm_server_config).