How to disable the Local PostgreSQL when using an external Database?

Overview

If you prefer to connect the MetaDefender Storage Security (MDSS) application to your own remote PostgreSql database server, you can disable the built-in PostgreSql container so that it is not deployed. The bundled PostgreSQL container is tuned to use a share of the host memory (on Linux, shared buffers are set to 25% of RAM at installation), so disabling it frees those resources. Follow the steps below.

Instructions

1. Stop the MDSS Application

Before making any configuration changes, stop the MDSS services:

2. Disable the Built-in PostgreSql Container

Open the file /etc/mdss/customer.env in a text editor and add postgres to the DISABLED_SERVICES variable (create the line if it does not exist):

DISABLED_SERVICES accepts a comma-separated list, so other externally managed services can be listed alongside it, for example DISABLED_SERVICES=postgres,rabbitmq,redis. See How to Enable Specific Modules in the Configuration? for details.

3. Start the MDSS Application

Once all modifications are complete, start the MDSS services again:

Verification

After restarting, verify that:

• MDSS is running without the internal PostgreSql container.

• The application is successfully connected to your external PostgreSql server.

You can check logs or test basic application functionality to ensure a proper connection.