When performing multiple task migrations with different priority the tool does not continue to perform migration son medium o low priority task.
When you submit a migration task, On-Demand Migration places all objects to be migrated into a queue for that asset, confirms available capacity, and then intelligently selects objects from the queue by processing objects with the highest priority first, using a first-in-first-out approach within that priority.
How do I assign priorities?
When submitting a migration task, you have the option to assign priority levels in the Schedule step of the migration wizard, to help control which objects will be processed from the asset task queue first.
How does first-in-first-out (FIFO) work?
When you submit a new migration task, objects are placed at the end of the asset queue for their assigned priority, meaning that tasks previously submitted with the same priority will be processed first.
As On Demand Migration completes a migration job, it will immediately start processing the next available job by selecting objects from the beginning of the highest priority queue.
This respects the FIFO approach while still ensuring that higher priority tasks are always processed before those with lower priorities.
What is an example scenario?
Let’s imagine that a migration operator submits five OneDrive migration tasks throughout the day, with a mixture of priorities, in the order of Task A, Task B, Task C, Task D, and Task E.
If there is available capacity to process all the objects when each task is submitted, the migrations states of all tasks will immediately switch to Migrating and all five tasks will process concurrently with no queue management required.
However, if the available capacity for OneDrive migrations is at its maximum limit when the tasks are submitted, On Demand Migration will place the objects in the OneDrive queue and then process the tasks in order of priority and FIFO as capacity becomes available.
