--- title: "Editing Server Settings" slug: "editing-server-settings-5-1-1" tags: ["Portal"] updated: 2026-11-10T07:35:35Z published: 2026-11-10T07:35:35Z canonical: "kb.ctera.com/editing-server-settings-5-1-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Editing Server Settings **To edit server settings:** 1. 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](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-3AJPDF0I.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) 2. Click the server to edit. The server page is displayed with the server name as the page title. 3. Edit and monitor the following settings: - [General Settings](/v1/docs/editing-server-settings-5-1-1#general-settings) - [Clients](/v1/docs/editing-server-settings-5-1-1#clients) - [Address Mappings](/v1/docs/editing-server-settings-5-1-1#address-mappings) - [DB Replication](/v1/docs/editing-server-settings-5-1-1#db-replication) – This option is only available for the main database and database replication servers. 4. Click **Save**. ## General Settings You can edit server settings, including configuring a server as an application server, setting the public IP address of the server, and the IP address to which each virtual portal's DNS should resolve. This allows you to restrict specific portals to be accessible only from a specific network interface. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-YO5COF6B.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) **Note** The **DB Replication** option is only available for the main database and database replication servers. In the **General Settings** option, you can edit the **Name**, which is the unique name of the server. ### Services and Functionalities **Note** CTERA recommends the following when configuring server services: - When possible, for high availability, HA, configure at least two servers for each server functionality. - Do not overload the application servers by configuring too many server functionalities on the same server. - Note specific requirements specified for each server functionality. - **Application server** – The server is an application server. An application server accepts CTTP connections from CTERA Edge Filers and CTERA Drive Share/Protect (Agents) and HTTPS connections from end users and CTERA Drive Mobile. If off, this server does **not** allow any logins. CTERA recommends designating at least two servers to act as application servers, for high availability. For details about CTTP, see [What is the CTTP Transport Protocol](/v1/docs/what-is-the-ctera-cttp-transport-protocol). 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. - **Antivirus Background Scanner** – An antivirus background scan runs on this server. **Note** CTERA recommends that the background scanning servers are not application servers. - **Document preview server** – The server is a document preview server. CTERA recommends designating at least two servers for generating document previews, for high availability. When a server is defined as a document preview server, the other server type options are disabled. Document previews are requested by end users from the end user portal's Web interface, the Cloud Drive, and backup folders. When a user clicks on a file’s name or icon in one of these locations, the file is displayed in the online viewer. **Note** You have to uncheck **Application server** before you can check **Document preview server**. After checking **Document preview server**, you need to restart the server. - **S3 Endpoint** – The server supports access to cloud drive folders from an S3 browser. For details, see [Setting Up Access to Content From an S3 Browser](/v1/docs/setting-up-access-to-portal-content-using-the-s3-api-ctera-fusion-1-1). **Note** Enabling the S3 Endpoint is required on only one server. For high availability, you can set the S3 Endpoint on more than one server. - **Messaging Server** – The server will also act as a messaging server. For details about the CTERA Messaging service and server requirements, see [Managing the CTERA Messaging Service](/v1/docs/managing-the-ctera-messaging-service-3-1-1). - **Thumbnail Server** – The server will also act as a thumbnail server. For details about the Thumbnail service, see [Managing the Thumbnail Service](/v1/docs/managing-the-thumbnail-service-1-1-1). ### Network - **Default Address** – The default IP address of the server. - **Public NAT Address** – The default IP address has a public Network Address Translation (NAT). Specify the public IP address. This controls the default IP address of this server that is exposed using DNS. - **Custom Address Mapping** – By default, CTERA Portal listens to team portals on the default address. You can optionally bind specific team portals to other interfaces (specified by IP address) of the server, which will cause this IP address to be published by the DNS server, and will prevent access to the specified portal via other IP addresses of the server. #### Address Mapping By default, CTERA Portal listens to team portals on the default address. You can optionally bind specific team portals to other interfaces (specified by IP address) of the server, which will cause this IP address to be published by the DNS server, and will prevent access to the specified portal via other IP addresses of the server. **To set custom address mappings:** 1. Slide **Custom Address Mappings** on under **Network** in the **General Settings** tab. The **Address Mapping** tab is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-XTI9UYE8.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) 2. Click the **Address Mapping** tab. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-TMINZ9SD.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) 3. Select the portal you want to specify address mapping. 4. Click **Add**. You can edit the following settings: - **IP Address** – The IP address for the team portal bound to an IP address of the server. If the virtual portal uses the default IP address, `Using main IP address` is displayed. You can change this to an IP address of the local interface to accept connections for clients. - **NAT IP Address** – If NAT is used, and the public IP address of the interface differs from the private IP address, specify the IP address to which the original IP address should be translated. This public address will be published by the CTERA Portal DNS server. To bind this team portal to the default IP address, do not enter a value in this field. To specify that the public IP address is equal to the private IP address, do not enter a value in this field. 5. To edit an **IP Address**, or **NAT IP Address** setting in a folder, select the folder, and click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-QLHW14H9.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D). 6. Select the required address to edit, to confirm the changes, click ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-VTCPJHW8.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D). 7. To delete an address mapping, select the address mapping, and click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-G3TDWJ56.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D). The address mapping is deleted. 8. Click **Save**. ### Advanced - **Read Cache Size Limit** – The maximum amount of server RAM to allocate to the read cache that is used to accelerate reads from the storage nodes. Recently read blocks are kept in the cache to avoid repetitive requests from the storage node. When the cache fills up, the blocks that have been in the cache the longest are removed. ## Clients You can view information about a server's currently connected devices. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-PJ074RNN.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) **Note** The **DB Replication** option is only available for the main database and database replication servers. In the **Clients** option, you can view settings for currently connected devices: - **Name** – The name of the client device. - **Owner** – The name of the client device's owner. - **Total In** – The total CTTP traffic sent from the client device to the virtual portal. - **Total Out** – The total CTTP traffic sent from the virtual portal to the client device. - **Average In** – The average speed, throughput, of traffic sent from the client device to the virtual portal in bytes/second. - **Average Out** – The average speed, throughput, of traffic sent from the virtual portal to the client device in bytes/second. - **In Backup** – The client device is currently backing up files to the CTERA Portal. Devices in backup display ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-BDXEIG5G.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D), otherwise, no icon is displayed. - **Connected Since** – The date and time when the connection started. ## DB Replication **Note** This option is only available for the main database and database replication servers. You can monitor the performance of the database backup and replication by selecting the **DB Replication** tab in the server page. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-2IURFWDU.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A41%3A28Z&se=2026-11-11T05%3A41%3A28Z&sr=c&sp=r&sig=Ss3jB2yw%2BSH2v3U%2BILeDOOwMLS%2BQTmtB2gRmrwh9nTo%3D) The portal reports the status of its scheduled base backups and transaction log archiving process, and whether [backing up to an S3 bucket](/v1/docs/backing-up-the-ctera-portal-database-to-an-s3-bucket) has been configured. Additional metrics to help detect when database replication falls behind due to lags in the process are also reported. In the event that replication falls behind, portal administrators are notified via email. The relevant email templates are *Replication setup failed* and *Replication has errors*.