Enterprise Vault.cloud™ Folder Sync 1.12 Administration Guide
- Requirements for Folder Sync
- Preparing the service accounts
- Installing and configuring Folder Sync
- Running and scheduling Folder Sync synchronizations
- Performing a "Run Now" Folder Sync synchronization
- Monitoring and managing Folder Sync
- Troubleshooting Folder Sync
About Folder Sync scheduling and choosing a scheduling strategy
Folder Sync lets you configure folder synchronization events to run on a schedule. Note the following about the scheduled synchronization events:
Each scheduled synchronization event runs once a week, on the day and time that you specify. For example, if you schedule an event to run on Wednesdays at 9:00 P.M., the event runs every Wednesday at that time until you remove the event. To configure Folder Sync to run on multiple days of the week you can create a separate synchronization event for each day.
For each scheduled synchronization event you must define a duration period, which can be up to 23 hours and 59 minutes.
We recommend that you avoid periods when the Folder Sync server is busy with system tasks, such as backup.
The time that Folder Sync takes to complete the processing of all of the mailboxes depends on several factors, including:
The number of selected mailboxes.
The size of the mailboxes.
The duration period that you set for the scheduled synchronization events.
The processing may take a considerable time to complete if you synchronize a large number of mailboxes, or if the mailboxes hold a lot of items.
If the Item Synch task fails to process all of the mailboxes within the event duration period, it resumes the synchronization where it left off in the next scheduled event.
If the Item Synch task completes the processing of all the mailboxes within the event duration period, it pauses for a set time and then begins to process the mailboxes again from the beginning. The pause period is referred to as the iterative restart period. The default value of the iterative restart period is 60 minutes. You can change this period if you want.
You cannot select different mailboxes for different scheduled synchronization events. If you want to perform a synchronization for an extemporary list of mailboxes, perform a Run Now synchronization.
Folder Sync processes the selected mailboxes in alphabetical order, as shown in the ArchiveTools Management Console. You cannot prioritize mailboxes for synchronization.
The following example illustrates the behavior of Folder Sync with a single scheduled synchronization. Suppose that you configure a single synchronization event to run on Mondays starting at 2:00 A.M. and with a duration of 2 hours. Suppose also that the iterative restart period is set to the default value of 60 minutes. The processing proceeds as follows:
The Folder Sync Item Synch task begins the synchronization at 2:00 A.M. on Monday.
Suppose that it takes the task 45 minutes to complete the processing of all of the selected mailboxes. The task completes the synchronizations at 2:45 A.M.
The Item Synch task then pauses processing for the iterative restart period of 60 minutes.
At 3:45 A.M. the task begins a rerun of the mailbox synchronizations again, from the beginning.
At 4:00 A.M. the end of the event duration period is reached, so the Item Synch task stops processing the mailboxes. Only some of the mailboxes were processed for a second time.
At the beginning of the next scheduled synchronization event on the following Monday, the Item Synch tasks restarts the synchronization from the mailbox where it left off previously.
In practice you need to set an aggressive synchronization strategy to ensure that new emails are synchronized from the Exchange folders to the archive folders without much delay. For example you can:
Create a synchronization event for every day of the week.
Configure each synchronization event to run with a duration period that is as long as possible. You can configure a duration of up to 23 hours and 45 minutes.
Avoid periods when the Folder Sync server is busy with system tasks such as backup.
Reduce the iterative restart period to 30 minutes.