Summary

When performing a space export, we expect to only export the contents of a single space.

In certain situations where the database is corrupted in subtle ways, we will sometimes get multiple spaces exported.

The symptom is that the entities.xml file contained in the export will contain more than one space. Searching for object class="Space" will return more than one result.

Further Context

Customers using the CCMA may see some variance in both the export and import phases if they're impacted by this.

Workaround

The interim workaround to ensure that the Space export contains only the desired Space is to try the following:

1. Import the Space XML import into a temporary Confluence instance
   • This will result in the multiple spaces imported
2. From this Confluence instance, exclude the unnecessary spaces and export the desire space again out as XML
   • This should result in just the Unique Space export in the newly created XML export file
3. You can then take the newly created XML export file that should contain just the desire space to be imported into your desired Confluence instance

As always, please do take plenty of backups and test the above in a Staging Environment before doing the actual import into your target Confluence instance.