Unable to perform XML Backup on a Large Instance of Confluence v3.1

Phillip Katzman

We are attempting to migrate away from Confluence v3.1 to the latest version on a new server. We are unable get a XML Backup to complete properly on our large instance of Confluence. We have attempted to change the JAVA Heap Size and numerous other JVM settings all to no avail.

We need to migrate off this old version of Confluence due to the security vulnerabilities that exist.

LucasA

Hi Phillip,

I'd already have this same problem when exporting large Confluence deploys. Unfortunately the only way to fix it is increasing the Confluence Xmx (max heap size) and try it all over again. There's no way to export only the spaces and import it on a new version -- Confluence 4+ has a new text format which has no compatibility with the previous versions (XHTML), so after loading your backup on a new Confluence version, it will need to convert all your content to XHMTL and more OutOfMemories may occur.

Indeed, if you are moving to Confluence 4, I could suggest you to export first from Confluence 3.1, load it on Confluence 3.5.16, then export it from Confluence 3.5.16 and import in Confluence 4.

If you need any help to correclty set the Confluence Xmx, this Confluence KB will help you on this regard.

Best regards,
Lucas Timm