---
title: "Moving From a Single Server Environment to a Multiple Server Environment"
slug: "moving-from-a-single-server-environment-to-a-multiple-server-environment-4"
tags: ["8.2", "Portal"]
updated: 2026-05-18T11:35:37Z
published: 2026-05-18T11:35:37Z
canonical: "kb.ctera.com/moving-from-a-single-server-environment-to-a-multiple-server-environment-4"
---

> ## 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.

# Moving From a Single Server Environment to a Multiple Server Environment

In production with the CTERA messaging service, CTERA recommends a production installation that comprises of five servers: Two database servers (primary and secondary), and three application servers that also function as messaging servers. Therefore, to move from a single server test environment to a multiple server production environment requires adding at least four servers: one for replicating the primary database server and three as messaging servers.

**Notes**

- In a production environment, with more than one server, you can still set just one server.
- The servers for messaging require 4 vCPU, 32GB RAM, 250GB data pool (Magnetic) each. For details, refer to [Production Deployment Blueprint under General Requirements](/v1/docs/planning-general-and-port-requirements-2).

**To move to a production environment:**

1. Add the additional servers, defining one server as a replication server, as described in [Installing and Configuring Additional CTERA Portal Servers](/v1/docs/installing-and-configuring-additional-ctera-portal-servers-5).
2. Configure two servers as messaging servers.
**Note**

When setting up the messaging service, as described in [Setting Up the CTERA Messaging Service](/v1/docs/setting-up-the-ctera-messaging-service-3), you have to add two servers so that the total messaging servers are three. You cannot add one server at a time to the existing messaging server.
3. Replace the messaging service from the original primary database server with the third application server, as described in [Replacing a Messaging Server](/v1/docs/replacing-a-messaging-server-4).

**Note**

All existing messaging data from the single messaging server is erased.