---
title: "Start-Up Order for Servers and Services"
slug: "start-up-order-for-servers-and-services"
tags: ["order", "start", "services", "servers"]
updated: 2025-04-25T06:44:02Z
published: 2025-04-25T06:44:02Z
canonical: "docs.revealdata.com/start-up-order-for-servers-and-services"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Start-Up Order for Servers and Services

Use the following guidelines when starting up Brainspace servers and services.

> [!NOTE]
> **Note**
> 
> See [***Brainspace 6.6 Implementation Guide***](/brainspace/docs/brainspace-implementation-guide) for more information.

1. If you are using NFS to share the /data volume from the Analytics server to other servers in your environment, the NFS service on the Analytics server must be started before NFS client instances. This typically means you would start your Analytics server first, and all required services should start automatically (especially NFS, analysisserver).
2. Start the Postgres database next if Postgres is deployed on a dedicated server (not on the Application server).
3. If Postgres is installed on the Application server, start the Application server, and all required services should start automatically (especially Postgres, NFS client, and brainspace-platform).
4. Start the On-Demand Analytics server next, and all required services should start automatically (especially NFS and brainspace-analysis).
5. If you have multiple, redundant Analytics or On-Demand Analytics servers, those should be started at this point.

### Brainspace Components and Service Names

The following is a list of critical Brainspace components and service names:

- **Brainspace Application Service** *brainspace-platform* (Runs only on Application server; Brainspace Application runs as a custom service inside of tomcat web service).
- **Brainspace Analysis** *brainspace-analysis* (Runs only on Analytics and On-Demand Analytics servers).
- **Brainspace Proxy** *haproxy* in versions 6.0 & 6.1 and *brainspace-haproxy* in version 6.2 and newer. See https://docs.brainspace.com/knowledge-base/custom-ssl-for-services-replacing-self-signed-certificates/#brainspace-version-ssl-configuration-changes for more details.
- **Brainspace Database** *postgresql* (Postgres is installed on Application server by default. Be sure to check your specific configuration if Postgres is running on another server).
- **Important**
- Ensure no CMML, Predictive Coding or builds are actively running before stopping services.

### Start and Stop Procedures

The current stop/start procedures are as follows:

**Brainspace Application**

*systemctl stop|start|restart brainspace-platform* (use argument *stop*, *start*, *status* or *restart*).

**Brainspace Analysis**

*systemctl stop|start|restart brainspace-analysis* (use argument s*top,* *start*, *status* or *restart*).

## Related

- [Installation & Upgrade](/installation-upgrade.md)
- [Preinstallation Script: Server Configuration Audit](/preinstallation-script-server-configuration-audit.md)
- [Brainspace System Health Checks](/brainspace-system-health-checks.md)
- [Services](/services.md)