Be able to create a Migration Queue where a migration job will start only when the previous one is completed.
Example: SG Job 1 Starts > SG Job 1 Completes > SG Job 2 Starts > SG Job 2 Completes > SG Job 3 Starts > SG Job 3 Completes > and so on.
Can we schedule migrations that start when another finishes (dependent)? Not with PowerShell, but with the current UI.
Neil Howell commented
When migrating large Network Drives, I have found that we need to break up sections into different Teams or Sites depending on the original permission structure.
To avoid throttling and guessing how long a job may take to run (and needing to stop and re-run scheduled jobs to avoid throttling), using a job dependency required to finish before the scheduled job starts would be beneficial.
Thank you for Woody's comment of using Powershell and the -WaitForImportCompletion command as I didn't know this (So I have learnt something for the day), however this also needs a visual implementation for the multi-select of folders to push to different jobs when you don't know the exact details of the folders beforehand.
Woody Windischman commented
If you're doing your migration with a PowerShell script and a list of targets, you can simply add the -WaitForImportCompletion parameter to your command line, and your loop will wait for each job to finish before the next iteration starts.
It would be nice if we could schedule a task (especialy for larger copy operations) to start it "when the previous job is done" (so one task after the other).
Now we have to guess how long a task may take and schedule the next one a bit later. Doing them simultaniously often lead to SharePoint throttling issues.
Love scheduled tasks but it would be handy to group tasks together that commence (sequentially) ay a given time.
When one task completes, the next starts. This would allow the fastest migration time i.e. avoiding having down time between tasks or worse having 2 or more tasks running concurrently potentially causing throttling of tasks.
Sadly no. Currently, migrations cannot be scheduled in order to start when the previous one is completed.
Yes, please add this as a feature/option, perhaps as a job option. This would go a long way towards preventing job overlap, O365 throttling and PC resource issues.
I posed this question back on May 29th.
We know that we can schedule migration jobs from within Sharegate. However, is there any way to serialize migrations jobs so that we can start one job and then when that one is finished, the next one starts and so on such as the following?
SG Job 1 Starts > SG Job 1 Completes > SG Job 2 Starts > SG Job 2 Completes > SG Job 3 Starts > SG Job 3 Completes > and so on.
We're trying to migrate a lot of sites in a short period of time, so it's important to reduce time wasted between migrations. When scheduling multiple migrations, there's no way to know how long each one will take to complete so you have to completely guess when to start each migration. If you schedule them to start too soon, you'll have multiple migrations running at once (increasing the chances of getting throttled). Schedule them too late and you've wasted a lot of time. It would be super helpful to have an option to automatically start the next scheduled migration immediately when each one finishes. It would also be good if it could prevent a migration from starting while another one is running. Thank you!
Let's be able to bulk import via powershell schduling. Also, lets figure out a way to bulk update schedules? Chould we even do like a incrmental timer seting where it start at a time then you put in 1 min or 10 min increments. So each task goes 1-10 min after the next scheduled task?
I often have to queue multiple migrations one after the other, I have to do it through Powershell, but if I may suggest, adding an option to the GUI that allows you to schedule a migration task (or any task) at the end of a running task rather than a specific time, it would be an excellent feature. It would be really easy to automate Inventory capacities that (unless I'm mistaken) cannot be performed through Powershell.
Thank you !
When scheduling migrations in ShareGate Desktop, Is there a setting that one can’t start without the other finishing?
Currently, we run or schedule multiple jobs but we have no control if one job is finished before the next starts. If jobs overlap we quickly run into O365 throttling issues. I'd love it if we could queue jobs when using the GUI. That is, when one job is running and we add another job, we get the option to start immediately (just like it is today), or start as soon as the previous job is done (ensuring we only have one running job at a time). With Powershell we already have that if we have multiple Copy-Content operations in a row (it will stay on the first job until completed or only remote processing remains). Now we just need that option for the GUI as well!
It would be helpful if I could queue up migrations to run after a previous migration has completed. For example, we may have higher priority folders to migrate from a file share, so I want those to run first. But once they're done, I'd like a second migration to start which moves the remaining lower-priority folders from the file share. This would save me from having to log in on a weekend to check on the status of a migration and then start the second part. Ideally we could chain multiple of these together (for example, if there were a third set of folders that I want to migrate once the second set is done). For performance reasons, I don't necessarily want 3 separate migrations running at the same time though.