Confluence creates a zipped backup file when exporting a space in its application data/confluencetemp/xmlexport directory when you export. This zipped backup contains metadata for every page within your space including attachments; its size can be quite large. It may also contain other temporary files like journal or application logs; if running Confluence on a cluster this backup could even be stored in shared home directories.
Application data/confluencetemp/xmlexport is a temporary directory where Confluence stores the content and attachments from pages before compressing them into an XML export file. As Confluence generates and saves copies of this XML export file, its size may quickly expand – potentially timeout or encounter out of memory errors if this directory becomes too large; to prevent this happening ensure that there is enough disk space to temporarily hold multiple copies during processing.
If you are importing into an earlier version of Confluence, make sure that the version of space that you’re importing from is compatible. Importing into an incompatible version could cause serious complications; furthermore, ensure you have permissions (for instance ‘Space admin’ roles) necessary for import into that space from which you are importing (e.g. Space administrator role is needed for successful importation).
When exporting a space, you have the option to include or exclude its marketplace and user-installed apps. If these are removed prior to importing the space, they must be re-installed upon import as they were not part of its export file.
From the Space tools menu, you can choose to back up either one or multiple spaces from within your instance of Confluence. Please refer to Backing Up a Space for more details. Confluence automatically backs up its database, installation directory and home directory at regular intervals in this location as defined by your administrator; the frequency and destination for these zipped XML backup files can be controlled via changing the value for ‘backup’ system property in your instance’s configuration file.
Confluence keeps a copy of all installed plugin JARs here for safekeeping; its contents are refreshed every time your instance restarts; thus deleting them from this directory does not uninstall them from your instance.