Intelligent Migration
- Andrea Harvey
On This Page
Overview
Intelligent migration is a crucial step in planning an efficient migration. DryvIQ scans your locations and provides an analysis of your content. Based on that analysis, you can make informed decisions about what content needs to be moved and where it needs to be moved. DryvIQ then transfers the content you tag to the specified location. You’ll know where the content is when you need to access it, and most importantly, you'll know it is secure. This page walks you through the individual pieces used in your intelligent migration. Intelligent migration involves the following processes:
Creating the user and group maps (if applicable) for the platform combinations that will be used.
Creating User and Group Maps
If you plan to use user or group maps for intelligent migration jobs, you need to create one user or group map for each source and destination combination that you will use. You must create these maps before running the intelligent migration job.
You cannot assign a mapping document to the intelligent migration job when specifying the permission preservation for the job. Instead, mapping policies for intelligent migration jobs are automatically assigned to child jobs based on their source and destination platforms. If there are no matching maps, no mapping will be used. If multiple matching maps exist, DryvIQ will not create the child job. An error will be present on the parent job noting that multiple maps are unsupported.
Creating an Intelligent Migration Job
The first step in your intelligent migration is to create an “Intelligent Migration” job. This job type creates a parent job that generates child jobs for each location used for content scans, which serves as the source locations for the job. The destination is the location you specify when creating the job--where you want to move the files you add to the intelligent migration. The child jobs will inherit the settings from the parent job.
Selecting the Job Type
When creating the job, select Intelligent migration as the job type. The Transfer direction will default to Transfer in one direction from Source to Destination since this is the only transfer direction available for intelligent migration. As with other job types, you can specify job behavior on subsequent pages.
Adding Locations to the Intelligent Migration Job
The Locations page for an intelligent migration job only provides an option to select the destination connection. The source connections used for an intelligent migration are based on the data sources assigned to content scans. You can only choose one destination location. If you need to move items to multiple locations, you must create separate intelligent migration jobs for each destination location you want to use. Impersonation (Run as user) is available for connections supporting this feature, and you can specify the specific path.
Disabled Job Features for Intelligent Migration Jobs
Because an intelligent migration job involves content from multiple source locations, certain job features are unavailable because they do not apply to intelligent migrations or because it is impossible to account for the various platform combinations properly.
Job Policies
New Items: Intelligent migration only supports Transfer the new items.
Deleted Items: Intelligent migration only supports Ignore items deleted from Source.
Advanced Job Options
Filtering: Filtering is not supported in intelligent migration because it does not apply since items are assigned to the jobs manually or based on saved views.
Metadata Mapping: Metadata mapping is unavailable when creating an intelligent migration job. Since multiple source locations are used for an intelligent migration, it is impossible to map metadata correctly.
User and Group Maps for Permission Preservation: You cannot assign a mapping document to the intelligent migration job when specifying the permission preservation for the job. Instead, mapping policies for intelligent migration jobs are automatically assigned to child jobs based on their source and destination platforms. If there are no matching maps, no mapping will be used. If multiple matching maps exist, DryvIQ will not create the child job. An error will be present on the parent job noting that multiple maps are unsupported.
Adding Items to an Intelligent Migration Job
DryvIQ provides multiple ways to add items to an Intelligent Migration job depending on how automated you want the process to be for your migration. You can add items manually or create a saved view to automatically add items to an intelligent migration job. If preferred, you can use a combination of both methods.
Manually Adding Items to an Intelligent Migration Job
You can add items to an intelligent migration job from the Content page.
Select Content in the left navigation menu to go to the Content page.
Select the items you want to add to an intelligent migration job.
Click the Assign to a migration button at the page's bottom.
A modal appears and displays the available intelligent migration jobs. Click the job associated with the location where you want to move the item(s) and click Save.
You will receive confirmation that DryvIQ added the items to the selected job. Click OK to acknowledge this message.
In the Content grid, the Migration Plan column will display the name of the intelligent migration job assigned, and the Migration Stage will be “Assigned.”
DryvIQ will move the items as part of the next job run. At that time, the Migration Stage will be “Completed.”
Adding Items to an Intelligent Migration Job Using a Saved View
If you prefer a more automated process, you create a saved view or use an existing saved view to add files to an intelligent migration. The process converts the saved view into a “migrated view.” A specialized job runs every five minutes that checks the “migrated views” and assigns any new items to the corresponding intelligent migration job.
Select Content in the left navigation menu to go to the Content page.
Create a public saved view that includes all the criteria you want to use to identify the items you wish to add to a specific intelligent migration job. If the public saved view already exists, you can skip this step.
Select My saved views.
Click Public if the public saved views are not displayed.
Click Migrate view next to the saved view you want to use for the intelligent migration job.
A modal appears and displays the available intelligent migration jobs. Click the job associated with the location where you want to move the item(s) identified by the saved view and click Save.
You will receive confirmation that DryvIQ added the items to the selected job. Click OK to acknowledge this message.
DryvIQ removes the view from the Public saved views list and adds it to the Migrated views list.
An item can only belong to one intelligent migration job. When an item has a status of “Assigned,” you can assign it to a different migration plan, which removes the item from the original migration plan. Once an item has a status of “Completed,” you cannot change the migration plan. If an item is added to multiple intelligent migration jobs (manually or through a migrated view), DryvIq will migrate it using the intelligent migration job to which it was first assigned.
Viewing Items Assigned to an Intelligent Migration
The Migration Plan column on the Content page displays the intelligent migration job to which the item is assigned. This column updates as you add items to jobs.
Filtering Content for Intelligent Migration Jobs
When viewing the content, you can use the Migration Plans filter to list all the intelligent migration jobs that have items assigned to them. You can view just these items by selecting a job, or you can view all items not assigned to an intelligent migration job by selecting the Unassigned option.
Viewing the Toolbox Details
When you select a file in the Content list, the Toolbox opens on the right side of the screen. Files assigned to a migration plan will have an additional Intelligent migration section at the bottom of the file Toolbox. This section displays all the information relevant to the file's migration.
Migration stage: The status will be “Assigned” for files added to a migration plan but not yet migrated and “Completed” for files DryvIQ has migrated. This status is the same status displayed in the Migration stage column.
Parent plan: This is the migration plan (intelligent migration job) to which the file was assigned. Clicking the plan name will take you to the Overview report for the job.
Child job: This is the child job that migrated the file. Clicking the job name will take you to the job overview report.
Path: This is the destination path for the intelligent migration job. (The path in the Location section at the top of the Toolbox displays the file's source location.)
Item status: This identifies the file’s migration status.
Transferred on: This lists the date and time DryvIQ finished migrating the file.
Viewing Child Jobs for an Intelligent Migration Job
DryvIQ creates a child job for each location used by a content scan. The scan locations are the source locations for the child jobs, and the destination is the connection selected when creating the intelligent migration job. You can view these jobs on the Child jobs page for the intelligent migration job. Like all jobs, you can click a child job in the list to drill into the reporting for just that child job. The intelligent migration child jobs are named using the convention of “Monitor location | Source Platform (source location) → Intelligent Migration Job Name.” (Refer to the image below for examples.) This name format displays on all pages where you can view the jobs.
