Upgrading Content Fusion

Pre-Upgrade Notes

System requirements: On the server running Content Fusion, you need enough disk space to create a backup. The backup file contains a compressed archive of all files located in /fusion/data/, so to be safe, the free space should be at least equal to the size of the data folder.
You cannot upgrade Content Fusion on the existing server. It needs to be installed on a new server and all tasks and configurations will be imported to the new server during the upgrade process.
Custom frameworks and plugins will need to be reinstalled manually on the new server.
The upgrade process will involve some downtime, so pick a time that does not affect the users.

Recommended Upgrade Procedure

Deploy the new version of Content Fusion on a new server according to the appropriate deployment method:
Access the Configuration Page and set the administrator password. See the configuration section for your particular deployment method:
Once the new server is ready, reinstall any custom Web Author frameworks or plugins that you were using on the old server.
Enable maintenance mode on the old server. Maintenance mode is needed to ensure that users are not making any changes to the tasks while the backup is being created.
Create a backup of the old server by running the following command on the old server:
```
sudo bash /fusion/admin/create-fusion-backup.sh
```
Important: The create-fusion-backup.sh script had an inherited critical bug in Content Fusion 2.0 and 3.0 and should be updated before attempting to create a new backup. More details can be found here: https://www.oxygenxml.com/content_fusion/critical_content_fusion_backup.html.

This will create a backup archive fusion-backup.tar.gz in the current directory. If the backup file already exists, it will be overwritten.
Copy the fusion-backup.tar.gz backup file to the newly deployed server.
On the newly deployed server, run the following command to restore the backup:
```
sudo bash /fusion/admin/restore-fusion-backup.sh /path/to/fusion-backup.tar.gz
```
where the path to the backup file is updated to match your situation.
Step Result: After restoring the backup, all the user tasks and configurations will be available in the new Content Fusion server.
Because the backup was created while maintenance mode was enabled, the new Content Fusion server will be in maintenance mode after the backup restore. Go to the Administration Page and disable maintenance mode.
To test the upgrade, check to make sure the tasks and configurations that were present on the old server are now present on the new server.
Note: Depending on the configuration, you may have to configure your mail server to accept emails from the new Content Fusion server.
Replace the old server with the new one.

Fast Upgrade Procedure

Restriction: This procedure is only available for installations created with the Linux installation kit and the version you want to upgrade from is at least 5.0.

To upgrade an installation that was created by the installation kit:

Go to the Content Fusion Download webpage.
Go to the Linux tab and download the Oxygen Content Fusion Enterprise Server installation kit.
Create a backup of your current installation.
Run the installer (the installation requires root privileges) using the -u flag.
```
sudo bash Oxygen_Content_Fusion_Enterprise.sh -u 
```

Note: When the -u flag is used, the installation kit will upgrade the current version of Content Fusion, while keeping all the existing data and configuration.