Jobs that have Windows as a source should only use the scheduler to trigger one job to run at a time. This applies to both Date/Time and Job triggers. The Windows app is a single POP, and when the scheduler triggers a second job, it will ask the user if they want to run that second job on the same POP – and will wait to run that second job until the user responds. That prompt is there to prevent the first job from failing on Windows machines that have insufficient CPU/memory resources. If you are running two or more jobs concurrently via the scheduler on jobs that do not have the Windows app, make sure that you have enough concurrency to provide all of the POP instances needed. For example, if you are running a cloud to cloud migration and want to schedule two concurrent jobs, you will need to request concurrency for two jobs, with a total of 4 POP instances (cloud to cloud jobs need one POP instance for source, and a second one for the target).
At the end of this section are several practical uses for the scheduler.
Accessing and Using the Scheduler
- From the dashboard, find the job you want to schedule and click directly on the job name. Select Schedule from the Job metrics balloon:
- You can also access the scheduler by selecting the Schedule tab in the Job modal window:
- The Scheduler screen has three tabs:
- No Schedule, the default
- Date & Time Schedule
- Triggered by Another Job
If this tab is selected, the scheduler will be completely disabled, regardless of whether you have configured a Date/Time or Job Trigger.
Date & Time Schedule:
- Select whether you want the currently selected job to run as a normal transfer job, simulation or account mapping job from the Run Type menu.
- Enter the Date and Time at which you want your job to run.
- If you want to run your job on a regular basis, select the interval from the Repeat field. If Repeat is set to ‘None,’ the job will only run once, at the designated date and time.
Triggered by Another Job:
This enables you to schedule a job based on the outcome of either the current job or another one.
- Select the run type desired for the current job.
- Select the job that should provide the triggering event from the first dropdown, and then select the triggering event from the second dropdown
- Select a triggering event. The three triggering events are:
- Completes: the job transfers all files without errors and has a status of Complete on the dashboard.
- Does not complete: the job ends with a status Incomplete or Failed.
- Finishes: the job ends with a status of Complete, Complete with errors, Incomplete or Failed.
Note that a triggering job will not qualify as ‘finished’ if it is Stopped or if it fails to validate. A job that fails to validate will never reach a state of ‘started’ in the Event Log, and if it never starts, it can never finish.
Apply ACL vs. Data Only Mode in the Scheduler
The scheduler will run an APM simulation or transfer job in its current ACL state (Data Only or Apply ACL) at the time that the scheduler starts the job. You specify the ACL state for the job on the Run screen of the Map Flow wizard:
If the Data Only radio button is selected, the job run by the scheduler will not apply shares. If the Apply ACL radio button is selected, the job run by the scheduler will apply shares. Note that if you have previously run a job in Apply ACL mode, you can subsequently run it in Data Only mode simply by selecting the Data Only radio button. Data Only mode will not affect any shares that are already in place.
Practical Applications for the Scheduler
- Sequential Run: This is the most popular use of the scheduler, where customers want a second job (which we will call ‘Job2′ in this example) to start running as soon as the first one (which we will call Job1’) is done.
- For the ‘Start this job when’ dropdown, select ‘Job1.’
- For the other dropdown, select ‘Finishes.’ Important: Do not select Complete; if any file tagged for transfer in ‘Job1’ does not transfer for any reason, ‘Job1’ will not meet the ‘Complete’ criterion and Job2 will not run. ‘Finishes’ will trigger Job2 to run regardless of whether all files in the preceding job transferred or not.
- You may add other schedule triggers – where Job3 runs as soon as Job2 is done, and so on – to other jobs in the same manner.
- Auto-run: To make a job continue to re-try until all of your files are transferred to the target, select the Triggered by Another Job tab and select the current job from the first dropdown. Select Does not complete from the second dropdown and your job will repeat until all your files transfer successfully to the target.
- Scheduled syncs: Many people want to back up their data after business hours when there is less activity on the source and target. To do this, select the Date & Time tab and select a date and time for the first sync. If you anticipate syncing any significant amount of data and are running on a Monday – Friday business schedule, a Friday evening is suggested as a start time for your weekly sync, as that will give you the full weekend to back up your data. Select Every week from the Repeat dropdown. Because Cloud FastPath only transfers newly created or updated files to the target, your data will be synchronized. The benefit is that you are not transferring your entire source to the target each week, saving both time and data transfer costs.
About Seasonal Updates to Time
The scheduler stores all schedule times in UTC. That enables CFP to report schedules in the local time of the computer, but still trigger jobs at a consistent point in time.
The downside of this is it does not accommodate local seasonal changes to time. For example, there is an interval where the U.S. has changed to Standard time but the UK has not. What CFP will do, however, is present the scheduler for the same absolute time regardless of the local computer’s time.