Once the planning for the cutover completes and a date is chosen for the event, a pre-cutover delta sync should occur so that as much of the recent changes can be brought forward before the sync. This reduces immediate post-cutover reactions by end-users of missing or incorrect data.
As already mentioned, it may be impossible to reach 100% convergence between the source and target public folders before cutover due to the fact that users and applications could still be making changes during and through the cutover period.
The determination of when to run this delta sync should be based on one of two things:
- Duration to run the consistency report plus duration of last folders synced
- Duration to run a delta sync across the entire hierarchy
It is expected that at least one previous delta sync has occurred using one of the two patterns above before reaching this point in the project. If not, it may be best to start this sync many days before the cutover event since there may be a substantial amount of deltas to process.
The delta sync at this stage, step #9, should be started at an appropriate number of hours or days before the start of the cutover process so that there is sufficient time for the delta sync to complete just at the start of the cutover tasks.
It is also ok if the sync overlaps into the cutover period and no harm will come from doing so.
This delta sync should be for all elements of the sync: structure, contents, and permissions.
