Sync Online to Staged

[former_member1336901]

Let's assume you have a Staged catalog version and an Online catalog version for a product catalog, and the Staged catalog version got corrupted (and cannot be easily fixed manually), but Online still contains good data.

What is the easiest way to do a full catalog sync from Online to Staged (as a one-time measure)? What is the easiest way to create a sync job from the existing Staged->Online sync job which syncs in the opposite direction?

Cloning the sync job and changing it to sync in the opposite direction works, but you get a ton of errors, because the items already exist in the target catalog version (Staged) and there are no ItemSyncTimestamp items yet that indicate that a sync was already done.

Clearly, for syncing from Online to Staged, the flag to remove items in the target catalog version if they are not in the source catalog version must be activated, and a forced update would need to be used.

[former_member387866]

Hi Thomas,

There are better practices to avoid the corrupted Staged catalog:

1. Back up the database regularry

2. Or, use a CronJob to export the Catalog to ImpEx every so often.

Regards,
Luke

[former_member1336901]

A database backup doesn't really help here, does it? How exactly would you get the data from a database dump back into the Staged catalog? How would you know how all required data is distributed among database tables (including relations, data stored out-of-band in generic tables, etc.), and how would you know how to filter what so only data related to the Staged catalog version is restored? A full database restoration (all tables) is not feasible for obvious reasons.

[former_member1336901]

When exporting the data in the catalog version version to ImpEx, how would you make sure that reimporting that data back into the Staged catalog results in the original data? For example, newly created items in the Staged catalog (which are not in the export) would not be removed when reimporting the data.