Upgrading a CTERA Portal

CTERA strongly recommends upgrading the portal with the help of CTERA Support.

You need a zip file from CTERA support – tar xvf file – where file is the zip filename for an offline upgrade. The file contains the packages for the portal upgrade.

Make sure that the required ports are open, as described in Port Requirements.

Note

For portal version 8.3.3300.53 and later, portal servers defined with two NICs from an earlier version of CTERA Portal are upgraded and both NICs are used. The second NIC is used when enabling the CTERA MCP service.

For portal servers defined with a single NIC, the upgrade will continue with the single NIC.

Portals configured with a single NIC must have a second NIC to use the MCP service and n8n service.

Upgrading the Portal

You have to shutdown all the portal servers before upgrading the portal.

To upgrade the CTERA Portal:

First upgrade the main database server. Next upgrade all application and preview servers. Finally, upgrade the replication database server.
1. Using SSH, log in as root to the portal server.
2. Copy the upgrade zip file to the machine.
Navigate to the location of the zip file and run the following command to extract the portal file: tar xvf file where file is the zip filename. The file contains the packages for the portal.
Navigate to the directory where the unzipped file is and run the following command: chmod +x upgrade.sh
Run the command upgrade.sh

Patch upgrades are relatively quick as only the packages that have changed are updated. An upgrade to the next major version takes more time.

Notes

You can also check that the upgrade has succeeded by running portal-manage.sh status which displays the image version.

Upgrading a Portal with Subfolder Quotas Configured in an Edge Filer

Subfolder quotas defined in an edge filer that were not implemented in the portal user interface, need to be exported from the edge filer and then imported to the portal to recreate the same centralized subfolder quotas in the portal using the CTERA SDK. For details, contact CTERA Support.