Content store migration

This feature helps the administrator copy content that already exists on the filesystem backend into S3, for each content store Purpose independently: DATASTORE, CACHE, EXTRACTION, and OCR_TEMPLATE — across every shard at once. To move a single shard’s already-existing content to a different backend without migrating every shard, use Shard Backend Migration instead.

Caution

Running this migration does not switch the active backend: it stays on the filesystem until the repository..type configuration property is manually changed to s3 and the application is restarted. Run the migration for a purpose, and run it again right before the switch to pick up anything written in between. Content marked for deletion (pending purge) is not migrated, so purge the trash before the final switch.

Global Content Migration is shown in a table, one row per purpose, with its status (Never run, Running, or Finished) and counters: Found, Copied, Already in S3, Skipped (.bak), and Errors.

Run a migration

• Click the Start button of the desired purpose (Run again if it has already finished once).
• The migration runs in the background and can take minutes or hours, depending on the volume of data. The progress page refreshes automatically every 2 seconds, showing the same counters plus the current tenant/shard being processed and the last error.

Note

While a purpose is running, its row shows a View progress link instead of the Start button. The detailed log can also be followed from the progress page, filtered by ContentStoreMigrator.