Hello @Mordechai Cikk ,
Currently the migration assistant doesn't do a check for free space before running. Its requirements are not large; it generates XML from the database similar to how a regular XML backup would function, then uploads the XML and your attachments to Confluence Cloud. The attachments are not duplicated on-disk before upload, so the space required to run the assistant is about what you'd need for a regular XML backup. Once the migration assistant has completed, the export it made locally is removed from disk.
Confluence does have a disk space healthcheck that runs on a regular schedule, so if you're not getting warnings from the healthcheck already, you are probably in good shape to run the migration assistant. If I had to throw out a random number for a Server instance that had maybe 30 fairly active spaces, I would guess that 5 GB of disk space would be the most I would expect the migration assistant to use. This is going to vary based on the number of spaces and how many pages / edits there are, but this is all text and doesn't consume a ton of disk space.
We do recommend that your heap for Confluence is at least 4GB to ensure the migration assistant doesn't encounter an out-of-memory error when generating the export however. If you need more information about checking and increasing the memory allocation, that's Step 12 in the pre-migration checklist.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.