The CS Export Tool provides the capability to restart the Document portion of a CS to Content Engine migration.
Much of the integrity and reliability of the restart mechanism relies upon the CS Export Tool being rerun under the same circumstances as the original migration. That is, the user has not reconfigured the tool in any way such that the query that produced the original master list of documents has not changed.
NOTE The restartability functionality is provided for CS to Content Engine migrations, but not for Dry Runs.
The restart functionality allows the user the ability to manually abort a lengthy migration, and then resume processing at a later time. It can also be used to recover from an unexpected failure and continue processing from the point of the failure.
The user will have no ability to change the name or location of the restart file. It will be located in the same directory as the projects configuration file and have a name that is derived from the project name. If the project name is MyProject then the restart file will be named MyProject-Restart.rst.
The CS Export Tool will use a restart file, configured in the Project Details dialog, to store and retrieve information that will allow it to restart processing from a previous run that was not completed.
The information stored in the restart file consists of two separate CS document identifiers. One of these values is referred to as the Restart ID and is the ID of the last known successfully migrated CS document. The second value is the largest ID the application is currently processing.
As the CS Export Tool processes documents, these two values are periodically updated. Each time the tool writes out this information it simply overwrites the previous information.
NOTE Implicitly assumed is that the CS documents are processed in ascending order.
When restarting an export run, this information will be used to 1.) modify the original query into the CS database to filter the documents processed to have CS document ID’s above the restart ID and 2.) Prior to the restarted migration this information will be used to clean up any dangling documents on the Content Engine server that were not completely migrated in the original run.
NOTE This is relative to the original CS query. There can be CS documents whose ID is less then the restart ID but they were not part of the original run.
The other identifier represents an upper bound on the last CS document that the tool began processing.
Due to the multi-threaded nature of the CS Export Tool and that CS documents are processed in batches, at any instances in time the tool can be in the process of migrating a range of documents which are in various states of completion.
NOTE Implicit in the restart algorithm and the use of the terms ‘lower’ and ‘upper’ bound is the fact that CS documents are processed in CS item ID order, from lowest to highest relative to the original content selected to be migrated.
When the CS Export Tool is configured for a restart operation, it will do the following actions: