Meridian Explorer repository synchronization jobs are more complex than other types of jobs and typically involve more documents. Meridian Enterprise Server is integrates deeply with Meridian Enterprise and repositories typically contain most of the documents for one more vaults. Therefore, the functionality is broader and there are more options available.
A synchronization job reads data from the Meridian Enterprise source vault and exports it to one or more intermediate data (not document content) files. A separate export is performed for each source vault that is specified for the same job name. If only one source vault is specified, then only one export is performed. If multiple source vaults are specified, each will be exported separately. The names of the intermediate files that are produced by the export conform to the following pattern: <source datastore name><job name><time of export><file number>.dat_. The data files contain: the configuration of the source vault, synchronization parameters, user data, folder data, project data, and document data. Depending on the batch size of the job, multiple data files may be created with sequential file numbers. Depending on the available hardware resources, multiple batches may be exported simultaneously for best performance. The data files are stored in a sub-folder named for each destination repository. The sub-folder also contains one baseline file per export that conforms to the following pattern: <source datastore name><job name>.baseline_. The baseline file is used to calculate incremental synchronizations.
After the first data file of the export phase of repository synchronization has been created, the job uses the names of the intermediate files to import the data that they contain (including document content) into the destination repository in the correct order. After they have been imported, the intermediate files can be moved to a configurable sub-folder where they can be re-used. Otherwise, they are deleted.
Configuring repository synchronization jobs and the export parameters is described in detail in Configure Synchronization Options.
If you run an incremental synchronization at time T1, some changed documents were processed and then documents were changed in the period [T1 - TransactionSpan, T1], the next time (T2) you run incremental synchronization, these documents are processed a second time because T1-TransactionSpan is used as a baseline to find changed documents. If you run incremental synchronization again, some documents could be processed a third time if T2-TransactionSpan is in the period [T1 - TransactionSpan, T1] and these documents were changed later than T2-TransactionSpan.
