1. Home
  2. Getting Started
  3. How to Leverage the Power of the Weekend

How to Leverage the Power of the Weekend


What to Know When Running a Transfer Job Over the Weekend


While it can be really tempting to start your migration Friday night, you should never run a job for the first time over the weekend, especially if it is critical. To make sure there are no surprises on Saturday night, we recommend that you move your data incrementally: starting with an initial bulk data transfer, followed by subsequent delta synchronizations up until your cut-over date (or weekend) where you would run one final delta job. If you have questions about this guide or want to ask for migration advice, the Cloud FastPath Support team will be available to help you 8am-8pm EST, Monday-Friday.


Delta Migration Steps


With proper preparation, the final migration delta occurring over a weekend should only require pushing a button, as you are running something that you have already run before. The best way to make sure your final migration sync completes over the weekend is to move the majority of your data prior to the weekend. The following sequence is recommended:

  1. Run an Analysis job on your source data, especially if you are running a very large migration. The Analysis report will detail what data you have and help you determine how best to run your migration.
  2. Run a Simulation  to see what the actual data transfer would be like, and how long it would take, but it does not transfer any actual data. Simulation will also allow you to anticipate many issues such as insufficient permissions, unprovisioned target users, or inadequate bandwidth. 
  3. Run an initial Data Only Transfer job. This will move the bulk of the data but will not transfer permissions yet.
  4. Repeat Data Only syncs leading up to the cutover window at regular intervals. This will begin to give you a predictable job run time. Nightly syncs may not be necessary if there’s not a lot of data that is updating.  A few trial syncs will help you optimize the frequency of the syncs.
  5. Using the data from the second and subsequent syncs, you’ll be able to know a good estimate of how long the syncs take and so you can determine if the jobs can run within the cutover time period. Additionally, you can split the job(s) into smaller jobs until you are comfortable with the run time. Cloud FastPath generally recommends that syncs run within twelve hours to easily run within the weekend, accommodate any last-minute users who load their accounts, and allow time to address any final issues with the actual migration or the business side of the cutover.
  6. When the cutover period starts (potentially on the weekend), do a final sync with Apply ACLs enabled. The majority of your data has already been moved, it has been synced and updated periodically, so the final step is just running it one more time and applying permissions. 


Running repeat syncs will also give you notice of any errors (e.g., path too long, locked files, unprovisioned accounts) and enable you to remediate the errors before the weekend cutover, even on data that did not exist when the initial simulation was run. 


Updated on April 30, 2020

Related Articles