Planning Your Installation
A CTERA Portal installation comprises a cluster of one or more servers. Each server can host any combination of the following services:
Main database. Only one server can host the main database. The server that hosts the main database is called the primary database server.Application service. This service accepts connections and handles requests from Web and CTTP clients.Database replication server. A passive database service set to replicate an active database server. During server installation, you can turn on the replication service and select the database server from which to replicate.Document preview server. This service is in charge of processing document preview requests. It is mandatory to launch a dedicated document preview server. The document preview service supports high availability. You can install one or more servers, in order to ensure uninterrupted document preview generation and redundancy in the event of a server failure.By default, the first installed server is the primary database server, hosting the main database and application server. In the simplest topology, there are two servers: one server that includes a main database and application service, and a second server that provides document preview services. You can install any number of additional servers, for Scalability, Sizing, and Load Balancing and for Data Replication and Failover.
Scalability, Sizing, and Load Balancing
CTERA Portal is horizontally scalable. Additional servers can be added:
As application servers, to increase client handling capacity. Any servers that are enabled as application servers automatically balance the connected clients between them, allowing for maximized capacity and availability. The number of application servers deployed depends on the use case: ROBO (remote office, branch office) use case – The users connect to the local CTERA Edge Filers, each edge filer connection to a virtual portal is one connection, even if there are thousands of users connected to each edge filer. You require one application server for every 100 edge filers.FSS (file sync and share) use case – The users connect directly to a virtual portal. You require one application server for every 10,000 users and a minimum of one virtual portal for every 100,000 users.As document preview servers.Data Replication and Failover
The main database is stateful and contains critical data. You must replicate all such servers to maintain the availability of critical data. The application service is stateless, and therefore, any dedicated application servers do not require replication or backup. Failover between application servers is automatic.
For details about replicating the database, see Backing Up the Database.
CTERA Portal includes a built-in replication function for achieving higher level of availability. Replication can be achieved using other platform dependent replication methods (such as SAN or VMWare-level replication).
Security
All internal communications between CTERA Portal servers is authenticated to prevent unauthorized access. Nevertheless, to follow the defense in-depth security philosophy, the primary database server, which stores sensitive data, should be placed in its own firewalled, isolated network, and only the application servers should be allowed to face the Internet.
Requirements
The CTERA portal image, obtainable from CTERA support at http://support.ctera.com.
Specific Platform Requirements
For AWS: m5.xlarge and at least 100GB EBS storage volume.
For ESXi: VMware ESXi 6.7U1 or later. The portal can be managed in VMware vCenter and in VMware vCloud Director.
For Hyper-V: Hyper-V for Windows Server 2012 R2 and higher.
For KVM and OpenStack: Make sure that memory overcommitting is disabled.
General Requirements for All Platforms
In a production environment, with a multi-node deployment, the application and database servers each require a 64-bit virtual machine with minimum 16GB RAM, 4 CPU cores and 110GB local hard disk drive. In a small or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with minimum 8GB RAM, 2 CPU cores and 110GB local hard disk drive.When an application server will handle up to the maximum 10,000 clients, CTERA recommends a 64-bit virtual machine with 32GB RAM and 8 CPU cores.
The size of the database should be around 2% of the target data. CTERA recommends seeking guidance from CTERA support for a more accurate estimation of the required database size.For the database server, an SSD disk with a provisioned IOPS volume with minimum 2000 IOPS.The replication database server must have the same hardware configuration as the primary database server.Access from the virtual machine to a Storage Area Network (SAN) or directly attached hard drives.The virtual disk attached to the CTERA VMs running the CTERA database, applicable for the main database, must yield a minimum of 700 TPS (transactions per second). To test the TPS on your installation, contact CTERA support at http://support.ctera.com.Preview servers require at least 16GB of RAM, 4 CPU cores, and 60GB of storage. CTERA recommends using SSD storage.Preview servers require at least 16GB of RAM, 4 CPU cores, and 60GB of storage. CTERA recommends using SSD storage.The ports listed in Port Considerations are open.Note: All resources allocated to a server must be dedicated to that server and not shared with other servers. You must not run non-CTERA applications on any of the portal servers.
Contact CTERA Support (http://www.ctera.com/support) for help sizing your environment.
Requirements for administrator device
Web browser: The latest two releases of Apple Safari, Google Chrome, Microsoft Edge, and Mozilla Firefox.SSH and SCP clients. For example, the freeware PuTTY.Other requirements
Prepare the following:
A DNS name for the CTERA Portal installation. This can be changed after the installation.An ICAP Server and license if the antivirus or data loss prevention (DLP) feature will be used.An SMTP mail server address and port for sending notifications, such as Amazon Simple Email Service (SES).Port Considerations
To allow access to and from the Internet on the firewall on each machine that will operate as an application server or database server, ensure the following network ports are open:
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
22
|
TCP
|
Inbound and Outbound
|
SSH. CTERA recommends limiting SSH access to specific IP addresses that may require access to the CTERA application servers, for example to perform scheduled maintenance and support related work.
|
|
53
|
UDP
|
Inbound and Outbound
|
DNS
|
|
80
|
TCP
|
Inbound and Outbound
|
HTTP
|
|
123
|
UDP
|
Outbound
|
NTP
|
|
443
|
TCP
|
Inbound and Outbound
|
HTTPS
|
|
995
|
TCP
|
Inbound
|
CTTP. Communications with CTERA appliances and agents.
|
|
xx1
|
TCP
|
Outbound
|
SMTP
|
1 Use the port number that is used at your site for SMTP. The default port for SMTP is 25.
The following ports must be opened towards storage nodes:
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
80
|
TCP
|
Outbound
|
CTERA Local Filesystem storage node
|
|
80 or 443 (for HTTPS)
|
TCP
|
Outbound
|
Object Storage1
|
|
111, 2049
|
TCP
|
Outbound
|
NFS
|
|
1191
|
TCP
|
Outbound
|
GPFS. Required for accessing GPFS nodes.
|
1 When Direct Mode is set for the storage node, HTTPS is set as and cannot be changed, requiring port 443.
If you are running a separated environment that consists of multiple CTERA servers residing on separate firewalled network segments (such as different AWS security groups), open the following additional ports between the CTERA servers. These ports do not need to be accessible from the Internet:
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
22
|
TCP
|
Inbound and Outbound
|
SSH management between the servers.
|
|
443
|
TCP
|
Inbound and Outbound
|
Updates between the servers.
|
|
5432
|
TCP
|
Inbound
|
PostgreSQL. Applicable for the primary database server and database replication servers only.
|
|
18682
|
TCP
|
Inbound and Outbound
|
Applicable for document preview servers only.
|
If CTERA Portal will be connected to Active Directory, open the following ports towards the Active Directory servers
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
53
|
TCP/UDP
|
Outbound
|
DNS
|
|
88
|
TCP/UDP
|
Outbound
|
If Kerberos is used
|
|
389
|
TCP/UDP
|
Outbound
|
LDAP/LDAP GC (Global Catalog)
|
|
3268
|
TCP
|
||
|
636, 3269
|
TCP
|
Outbound
|
LDAP and LDAP GC with SSL1
|
1 CTERA recommends using LDAP and LDAP GC with SSL instead of LDAP and LDAP GC.
CTERA Portal requires the following port open for RSync for database replication between the main and secondary databases. This port does not need to be accessible from the Internet:
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
873
|
TCP
|
Inbound
|
—
|
CTERA Portal requires the following port open for antivirus and DLP scanning. This port does not need to be accessible from the Internet:
|
Port
|
Protocol
|
Direction
|
Notes
|
|---|---|---|---|
|
1344
|
TCP
|
Outbound
|
—
|
Warning: CTERA Portal operates behind a firewall, and it is important to leave all other ports closed.