In the event of database corruption, it may be necessary to run a perform a Recovery Procedure on the connection. The one thing you ’lose’ when running the Recovery Procedure are any Deletes that have occurred on the source since the last successful sync was run. Generally, the next time a Sync is run any Source deletes will be propogated to the destination. Since SimpleSync can only track deletes based on its data file, if you delete the data file, we don’t know if a delete is required.

** To avoid leaving orphaned objects on the destination when running the Recovery Procedure, if possible, you should run a regular sync immidiately prior to the Recovery Procedure. If this isn’t possible, you’ll need to manually delete the orphaned objects following the Recovery sync. This is easy to do by sorting your destination directory by Modified Date following the Recovery Procedure. The Recovery Procedure modifies all objects, so any object that wasn’t modified is orphaned and may be deleted.

Sync Recovery Procedure:

1. Delete the data directory for your connection. \SimpleSync-v4\Connections\YourConnectionName\data.
    
2. Run a sync. (When running v4, Discovery and Sync should both be enabled.) This will perform a full sync to the destination system. Any pre-existing records will be ’linked’ in the connections’s new data files.
    
3. Run the sync a second time. (When running v4, only the Sync Phase need be enabled here.) This will modify all ’linked’ records to make sure that their attributes are populated with current information.
    
4. Run the sync a third time. (When running v4, only the Sync Phase need be enabled here.) This will perform like a normal sync. You should not see many changes here. 5. If you disabled Discovery, be sure to re-enable Discovery now to resume normal syncing.