After a data migration policy has been defined, it must be scheduled. The decision on how often to run a policy may be affected by the rules selected in this policy. For example:
- A policy with a single rule to migrate all .mp3 files may be scheduled to run once every month.
- Another policy, used to archive a working /project directory once the project is complete, may be scheduled as a Once Only Schedule.
- Other policies which migrate based on various Pre-conditions, and are triggered on available free space, may be scheduled to run every week.
When planning migration schedules, schedule migrations during off-peak times, such as evenings and weekends.
After a data migration has begun, additional data migrations for the same policy cannot be started until the current one has completed. However, it is possible to start multiple concurrent data migrations if each have its own policy.