Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-60389

As an admin I want to migrate a large Confluence space to another instance without size limitations

    XMLWordPrintable

    Details

    • UIS:
      1
    • Feedback Policy:
      We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      Problem Definition

      A huge space migration can translate also into even greater pain - spaces can get so big that will cause attempts to do the XML export/import to crash.

      For a huge space, admins have to devise their own migration tools or suffer from long and painful migration steps (long-running exports, for invalid characters in the files inside the backup zip file, long-running import, etc).

      Suggested Solution

      Today the XML format is used for the main file (entities.xml - which can take an absurd side) and a few other files/directories and the attachments directory.

      The suggestion is that this process can be refactored to bypass file sizing limitations by

      • using other formats (non-XML), easier to parse and work with (and potentially smaller in size)
      • implementing a wire migration tool that'd allow a space to be transported to another instance

      Essentially the way to improve it is not the main thing - the main ask is to actually improve the space migration task to make it easier and faster for really large instance admins.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            omedeiros@atlassian.com Osimar Medeiros
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: