Disk Space Requirements for Content Fusion

How Oxygen Content Fusion Uses Disk Space

Oxygen Content Fusion uses disk space for several purposes:

1. It stores most of the data generated by users in the /fusion/data/ folder.
   • Review Tasks:
     • When a user uploads a review task, all the files linked from the context DITA map are uploaded, even if only a few files are sent in the task.
     • To reduce the disk space usage, Oxygen Content Fusion stores review tasks in groups of 100 and tries to store just one copy of a file uploaded as part of multiple review tasks within the same group. Therefore, you may notice a steeper increase in disk space usage after 100 tasks are created.
   • Projects:
     • When users create a new project based on a Git repository, a clone of that repository is stored.
     • Review tasks created within a project stores only files that were changed since the review task started.
   • Deliverables:
     • For projects that have deliverables, Oxygen Content Fusion stores an additional clone of the Git repository for each deliverable. It also stores an output for each deliverable associated with the last successful build.
2. Docker stores server logs outside the /fusion/data/ folder.
   • Make sure you configure limits on the amount of logs that are stored.
3. When an administrator runs a backup script, it stores the backup archive on the server's file system. The size of the backup archive is similar to the size of the /fusion/data/ directory.
   Note: It is important to move the backups to a different server, ideally in a different geographic region.

Disk Space Recommendation

It is recommended to have at least 100GB disk space on the server where you want to install Content Fusion. After that, monitor the available disk space for the /fusion/data/ folder and increase it as needed.