In this section we’ll review some of the things that need to take place at the end of a migration using Journal Commander.

Progress & Performance

The summary information at the top of the Progress & Performance gives a good indicator of what has progressed in the migration.

Failures

Failures during the migration are inevitable.

Assuming that the source environment is fairly healthy the actual result in most migration is just a tiny fraction of a percentage, but a small fraction can still appear to be tens of thousands of items:

In this example 140,000 failed items is actually 0.069% within the migration.

Further, with this example, most items failed to export from the source meaning that source integrity was a possible issue.

Some of the reasons that items fail include:

  • Requests timing out
  • Items too large
  • Throttling issues
  • Target unavailability
  • Item unavailable or corrupt in the source
  • Unsupported items by the target due to size, type, or other properties

Review the failed items report which by default is grouped by error hash resulting in a grouping of errors:

Many more details, grouping, and sorting is possible:

Key to the numbers in the previous screenshot:

  1. Select a source link
  2. Grouping of errors (currently showing that the page is grouped by error hash, the default)
  3. Errors
  4. An expanded error hash result
  5. Error text which was reported by the source or target module
  6. You can filter to show just export failures
  7. You can attempt to download the item from the source
  8. You can filter to show just import failures
  9. You can filter to show only permanently failed items

Permanent failures show items which have been retried 10 times.

Items can be retried manually from the failed item screen if required.

Print Friendly, PDF & Email