On This Page
Overview
Intelligent migration is a crucial step in planning an efficient migration. DryvIQ Discover 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 Migrate 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 the content 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. These maps need to be created before you run 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 there are multiple matching maps, the child job will not be created, and an error will be present on the parent job noting that multiple maps are not supported.
Creating an Intelligent Migration Job
The first step in your intelligent migration is to create an “Intelligent Migration” job in DryvIQ Migrate. This creates a parent job that generates child jobs for each location in Discover, which serve 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 will be able to 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 will be based on the data sources assigned in Discover. You can only select one destination location. If you need to move items to multiple locations, you will need to create separate intelligent migration jobs for each destination location you want to use. Impersonation (Run as user) is available for connections that support this feature, and you can specify the specific path to use.
Disabled Job Features for Intelligent Migration Jobs
Because an intelligent migration job involves content from multiple source locations, certain job features are disabled (unavailable) because they do not apply to an intelligent migration or because there is no way to properly account for the various platform combinations.
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 not available when creating an intelligent migration job. Since there are multiple source locations used for intelligent migration, there is no way to properly map metadata.
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 there are multiple matching maps, the child job will not be created, and an error will be present on the parent job noting that multiple maps are not supported.
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 you can create a saved view that can be used 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 as you view the Discover results.
Go to the Discover Results page.
Select items in the grid you want to add to an intelligent migration job.
Click the Assign to a migration button that appears at the bottom of the page.
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 the items were added to the selected job. Click OK to acknowledge this message.
In the Results grid, the Migration Plan column will display the name of the assigned intelligent migration job, and the Migration Stage will be “Assigned.”
The items will be moved 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
You can create a saved view or use an exiting saved view to add files to an intelligent migration job if you prefer to use a more automated process for adding items. This turns 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.
Go to the Discover Results page.
Create a public saved view that includes all the criteria you want to use to identify the items that should be used to add items 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 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 the items were added to the selected job. Click OK to acknowledge this message.
The view is removed from the Public saved views list and added 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. This 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), the item will be migrated by the intelligent migration job to which it was first assigned.
Viewing Items Assigned to an Intelligent Migration
The Migration Plan column in the Discover Results grid displays the intelligent migration job to which the item is assigned. This column updates as items are added to jobs.
Filtering Results for Intelligent Migration Jobs
When viewing the Discover results, you can use the Migration Plans filter to list all the intelligent migration jobs that have items assigned to them. You can choose to view just these items by selecting a job, or you can use the Unassigned option to view all items that are not assigned to an intelligent migration job.
Viewing Child Jobs for an Intelligent Migration Job
A child job for each location added in Discover is created for an intelligent migration job. The Discover locations are the source locations for the job, 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 following naming convention: “Monitor location | Source Platform (source location) → Intelligent Migration Job Name.” (Refer to the image below for examples.) This name format is displayed on all pages where you can view the jobs.
