Installing CTERA Portal Instances

Use the following workflow to install CTERA Portal.

1. Creating a Portal Instance.
2. For the primary database server and secondary, replication, server Logging in to the Server to Create the Archive Pool.
3. Optionally, configure a default gateway.
4. For the first server you install, follow the steps in Configuring the Primary Server.
5. For any additional servers beside the primary server, install the server as described below and configure it as an additional server, as described in Installing and Configuring Additional CTERA Portal Servers.
6. Make sure that you replicate the database, as described in Configuring the CTERA Portal Database for Backup.
7. Backup the server as described in Backing Up the CTERA Portal Servers and Storage.

Creating a Portal Instance

To create a portal instance:

1. Log in to your Azure portal and access the Images service.
   The list of available images is displayed.

2. Select the CTERA Portal image created in Creating a Portal Image.
   The image details are displayed.
   

3. Click Create VM.
   The Create a virtual machine page is displayed.
   
   Resource group – The resource group to be used. The resource group used to create the image is the default group. The resource group must use premium storage.
   Virtual machine name – A name to uniquely identify the virtual machine.
   Region – The region to host the virtual machine.
   Size – Click See all sizes to display the available VM sizes.
   The Select a VM size page is displayed.
   

   1. Select a VM size that matches your requirements.
      The VM size depends on the type of server you want. For details, see Requirements
   2. Click Select.
      
      

   Authentication type – Choose Password.
   Username – A name to access the virtual machine. This is an administrator name to access the portal for initial configuration.

   Note

   Once the virtual machine has been fully configured, CTERA provides a user name and password, but this user name can also be used.

   Password – Enter a password to access the instance.
   Confirm password – Reenter the password.
   Select inbound rules – Select HTTPS (443) from the drop-down list.
   Licensing type – Select Other.
   Leave the other values with their defaults.

4. Click the Disks tab or Next: Disks.
   

5. For the primary CTERA Portal database server and the secondary, replication, server, click Create and attach a new disk to create the disk for archive storage.
   

   Note

   For all other servers, application and preview, you do not need to add an archive pool disk. CTERA recommends adding archive storage on both the primary and secondary database servers.

   1. Click Change size.
      The Select a disk size page is displayed.
      
   2. For the Disk SKU change Premium SSD (locally-redundant storage) to Standard HDD in the drop-down box.
   3. Under Custom disk size (GiB) enter the archive pool disk size.
      See Requirements for disk sizing. Prior to going to production, contact CTERA Support to evaluate whether the attached drive's performance meets CTERA's performance requirements.
      Note

      The minimum archive pool should be 200GB but it should be sized around 2% of the expected global file system size.

   4. Click OK.

6. Click OK.

7. Change Host caching for the disks to Read/write for the added disks.

8. Click Review + create.

   Note

   If validation does not pass, click Review + create again.

9. Review the virtual machine details and click Create.
   The machine is deployed and started automatically.

10. Click Go to resource to display its details.
    The virtual machine includes the OS disk which is used for root, and a data disk, which is used to store the CTERA Portal database.

    Note

    Note the Public IP address. You access the server using this address. When connecting to the server using SSH for the first time, use the root user and ctera321 password. You are prompted to change the password.

11. Click Networking under Settings in the navigation menu to add inbound and outbound port rules.

12. In the Inbound port rules tab, click Add inbound port rule.
    The Add inbound security rule window is displayed.

13. Click Add inbound port rule to add the inbound port rules, incrementing the Priority for each rule by ‘10‘ and clicking Add after adding each rule. The ports required are listed in Port Tables. For example:

    Service	Destination port ranges	Protocol	Priority	Name
    Custom	995	TCP	330	CTTP
    Custom	18682	TCP	350	Preview

14. Select the Outbound port rules tab and click Add outbound port rule.
    The Add outbound security rule window is displayed.

15. Add the ports listed in Port Tables.

    Note

    You need to change the Name field, if it was used for the inbound port. For example:

    Service	Destination port ranges	Protocol	Priority	Name
    Custom	18682	TCP	110	Preview1
    Custom	123	UDP	130	NTP
    SMTP	—	—	140	SMTP

16. For the primary database server and the secondary, replication, servers, continue with Logging in to the Server to Create the Archive Pool.

Logging in to the Server to Create the Archive Pool

You need to create an archive pool on the primary database server, and when PostgreSQL streaming replication is required, also create an archive pool on the secondary, replication, server. See Using PostgreSQL Streaming Replication for details about PostgreSQL streaming replication.

To log in to the CTERA Portal server:

• Log in as root, using SSH or through the console.
  The default password is ctera321

You are prompted to change the password on your first login.

To create the archive pool:

1. Log in as root, using SSH or through the console.
2. Run fdisk -l to identify the disk to use for the data pool and archive pool.
3. Run the following command to create the archive pool: portal-storage-util.sh create_db_archive_pool Device
   Where Device is the Device name of the disk to use for the archive pool.
   For example: portal-storage-util.sh create_db_archive_pool sdd
   This command creates both a logical volume and an LVM volume group using the specified device. Therefore, multiple devices can be specified if desired. For example: `portal-storage-util.sh create_db_archive_pool sdd sde sdf'
4. Start CTERA Portal services, by running the following command: portal-manage.sh start