Problem

Customers are reporting issues while trying to import an XML Site Backup back into a Confluence Vanilla instance (same version for instance LTS 7.4.3 ). This should not happen:

• the end-user experience can be improved by adding upfront checks directly in Confluence XML Backup code.
• the end-user experience is currently impacted by such failure

Suggested Solution

The Confluence site XML backup and restore processes should have a consistent level of data integrity checking so that Confluence administrators and end-users can be confident to restore their Backup successfully. This can be improved by:

• Either Adding data integrity checking to the backup process so backups fail with a warning about data integrity issues
• Or Remove data integrity checking in user_mapping from the restore process - even with duplicate user mappings Confluence ran fine

Why This Is Important

Having a look at these 2 Knowledge-Based articles:

• Restore of a site XML backup fails due to duplicate entry '' for key 'unq_lwr_username' error
• Confluence site XML import fails with "duplicate key" error
  And the number of support tickets that have been resolved thanks to them can give you an idea of how this had (and keep) affect the Confluence end-users experience in recent history.

Workaround

• Follow Confluence site XML import fails with "duplicate key" error or Restore of a site XML backup fails due to duplicate entry '' for key 'unq_lwr_username' error until complete resolution of errors