Migration App Scheduler

Audience

Any user of the Migration App.

Context

Migration Operators can schedule a given migration job to run one time in the future or to run at regular intervals at specific times.

Setting a Scheduled Job

Go to the Migration Job Details page. In the left column, click Advanced options. Clicking on Scheduler brings up a configuration page.

Switch Enable Scheduler to ON and then choose between scheduling the job to run once in the future, or to run at regular intervals.

If the first option run once in the future is selected, a calendar picker is offered to select a date and time. The date and time selected must be in the future. Time slots are at :15 intervals, are presented in military time, and reflect the clock on the host where the agent is installed. If no time is selected, time will default to 00:00.

Selecting the second option run at regular intervals, prompts a frequency selection as well.

In either case – running one time in the future or running at intervals – additional queries will be revealed in the dialog, prompting the user to make selections regarding Empty Folders, Sanitizing and Syncing Deletes.

Click Save after making the selections. The configuration details will be confirmed at the top of the page in the blue box. In the example below, the scheduled job will run for two days at 2:00 AM, starting on the date specified.

In the right column, under Other Details, hovering over the clock icon next to Scheduler will reveal the next scheduled run.

When Scheduler has been enabled for a job, on the Migration Dashboard a clock icon will appear next to the status of the job. Hovering over the clock icon reveals the scheduled run time for the job.

Maximum Recurrence

By default, the schedule recurrence is set to 20, allowing a migration job to run for a maximum of 20 days, weeks, or months. Requests to increase the maximum can be submitted to the support team. Different use cases may demand different parameters:

• Change the maximum recurrence to 365 so that it can run daily for a year. 
• Change it to 52 so that jobs can be scheduled to run weekly for a year.
• Change it to 30 so that a job can run daily for a month.
• Change it to Infinite so that it will run daily, weekly, or monthly indefinitely.

If the maximum recurrence for a domain is updated, the drop-down menu on the Scheduler Page will display options ranging from 1 to 20, along with the newly configured maximum. For example, the image below shows what the User Interface will display if the domain is set to allow Infinite recurrence of scheduled jobs.

The corresponding confirmation message will read as follows:

Email Notifications

Users will receive email notifications for scheduled jobs under the following circumstances:

• Confirmation of a scheduled job, whether it is scheduled to run once, for multiple recurrences, or indefinitely.
• If a job is scheduled to run indefinitely, they will receive monthly emails to confirm that it is running. 
• If a job is scheduled to run for longer than one month and over 20 recurrences, they will receive monthly confirmation emails plus one final notification prior to the last scheduled recurrence.
  Examples: 
  • If a job is set to run daily for a total of 365 times, the user will receive 1 initial confirmation email, then 11 monthly confirmation emails, and 1 final email notifying them that the scheduled job run is set to expire.
  • If it is set to run weekly for a total of 52 times, the user will receive 1 initial confirmation email, then 11 monthly confirmation emails, and 1 final email notifying them that the scheduled job run is set to expire.
  • If is set to run monthly for a total of 24 times, the user will receive 1 initial confirmation email, then 23 monthly confirmation emails, and 1 final email notifying them that the scheduled job run is set to expire.

Considerations

• It is not possible to schedule a job to run more than once per day. Jobs can be scheduled to run once per day, week, or month, up to a default limit of 20 occurrences. For scheduling beyond 20 instances, refer to the Maximum Recurrence section.
• If a job has been scheduled but has not yet been executed, the user may change the date and time to another point in the future.
• If a scheduled job has run, the user may always schedule a subsequent execution.
• If the Agent was disconnected from the cloud when a job was scheduled to run, the command will not be triggered. A notification message will appear on the Scheduler Page to indicate that the job did not run as scheduled.
  
  
• If both Scheduling and Unattended Mode are enabled, Unattended Mode will take precedence and the Scheduled job will not run.

Questions? Feature Requests? Other Feedback?

Scheduling is a complex proposition. Egnyte is aware that there are numerous ways to improve this feature and would appreciate the end-users' inputs in determining their priorities. To weigh in on what features are important from the user’s perspective, feel free to comment on Product Portal.

For any other feature suggestions or requests, feel free to submit them here, and  mention Migration App in the text.

For more complex requests that would benefit from providing screenshots or other attachments, submit them to support@egnyte.com. Be sure to include Migration App in the email title. The Support team will push the comments to the Product team for consideration.