Installing and Configuring Additional CTERA Portal Servers

Installing an Additional Server

All servers except the primary server are additional servers.

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

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

For the installation procedure, see:

• AWS
• Azure
• ESXi
• Hyper-V
• KVM
• Nutanix AHV

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

Changing the IP address after installing a portal server, but prior to the full deployment of portal services like Nomad and Consul, causes the deployment to fail.

Wait until all the portal services have been loaded before changing the IP address. If you changed the IP address after the installation but before the full deployment of portal services like Nomad and Consul, run portal-manage.sh resetdb

You must run portal-manage.sh resetdb before initializing the portal or joining it to an existing portal cluster.

To setup an additional server:

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.
   

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, KVM, Nutanix AHV Platforms	AWS Platforms
   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 server is initialized including testing the connection to the primary server. When the initialization finishes, a 120-second countdown is displayed.

   Note

   Completing the procedure can take a few more minutes before the Administrator Login page is displayed.

5. Click Finish.
   CTERA Portal opens, displaying the Administrator Login page.
   

   Notes

   The first access to the Administrator Login page can take a few minutes as dockers are loaded to the data pool.

   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.