Installing and Configuring Additional CTERA Portal Servers
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Installing and Configuring Additional CTERA Portal Servers

  • Dark
    Light
  • PDF

Article Summary

Installing an Additional Server

All servers except the primary server are additional servers.

Warning

You must complete the setup of each server before setting up another server.

You install additional servers using the same procedure you used to install the primary server, except for the following:

  • For messaging servers, you require 4 vCPUs, 32GB RAM, and 250GB data pool (Magnetic).
  • For a preview server, you require 4 vCPUs, 16GB RAM,and 60GB data pool (SSD).
  • For all other application servers, you require 4 vCPUs, 16GB RAM, and 100GB data pool (Magnetic).

For the installation procedure, see:

Note

For document previews to work, you must install at least one additional server as a document preview server.

After installing the additional server, continue with Setting Up an Additional Server.

In a production environment, the primary server hosts the CTERA Portal database, referred to as Main DB. In production this server and the server that hosts the replication database, referred to as Replication of main_db_server_name should not be defined as application servers. For details about editing server settings, see Editing Server Settings.

Setting Up an Additional Server

To setup an additional server:

Note

If the HTTPS administration port was changed on the primary server, you must enable the relevant port on all servers.

  1. Using a Web browser, browse to the new server, via the IP address or DNS.
    The Setup wizard opens, displaying the Select Server operation mode window.
    image.png

  2. Choose Master Server Address and enter the address of the primary server.

  3. Click NEXT.
    The Master Server Details window is displayed.

    Azure, ESXi, Hyper-V, Nutanix AHV, OpenStack/KVM PlatformsAWS, GCP Platforms
    image.pngimage.png
    Enter the root password for the primary server. The default is ctera321, but this should have been changed on first access to the server.Enter the key to access the master, primary, server. This is the master key, with PEM format, created when installing the primary server.
  4. Click NEXT.
    The wizard completes and a success message is displayed.

    Note

    Completing the procedure takes a few minutes. Once the procedure is almost complete a 60 second countdown is displayed before the server is up and running.

  5. Click OK.
    CTERA Portal opens, displaying the Administrator Login page.
    image.png

    Note

    The IP address is the IP of the additional server. The IP address of any server configured as an application server can be used to access the portal.

Configuring the Additional Server

Additional servers are configured to support different services, such as messaging, thumbnails, or document preview servers. The additional server defined with an archive pool is configured as a replication server of the primary server.

To configure the additional server:

  1. Sign in to the portal: Enter the user name and password and click SIGN IN.
    The portal opens, displaying the Main > Dashboard page. By default, CTERA Portal creates a team portal called portal. For information about how to rename, view and edit this portal, or create additional team portals, see the Global Administrator Guide.

  2. In the global administration view, select Main > Servers in the navigation pane.
    The SERVERS page is displayed, listing all the servers for the CTERA Portal.
    image.png

  3. Click the server to edit.
    The server window is displayed with the server name as the window title.
    image.png

  4. Check the boxes of the services to be provided by this server, for example, as a document preview server.
    To configure the replication server:
    In a production environment with a primary database server, secondary, replication, server and at least two application servers for HA, or three application servers when the CTERA Messaging service is enabled, you need to do the following:

    1. Designate the server on which you created an archive pool that is not the primary server, as the replication server.
    2. Uncheck Application server for the replication database server, called Replication of server in the SERVERS page.
      image.png
    3. If you have already defined another server, that is still configured as an Application server, uncheck Application server for the primary database server, called Main DB in the SERVERS page.
      image.png
      :::
    Warning

    You can only sign in to a server that is configured as an Application server, using the default portal DNS or that server IP. Once you have unchecked Application server for the primary database server and secondary, replication, server, you can no longer sign in to the CTERA Portal using either of these server IPs.

  5. Click SAVE.


Was this article helpful?