Before You Begin

Before you install Veeam Backup Enterprise Manager, check the following prerequisites:

A machine on which you plan to install Veeam Backup Enterprise Manager must meet the system requirements. For more information, see System Requirements.
A user account that you plan to use for installation must have sufficient permissions. For more information, see Permissions.
Backup infrastructure components communicate with each other over specific ports. These ports must be open. For more information, see Ports.
Local antivirus or antimalware software can interfere with Veeam Backup Enterprise Manager installation. If you receive the Failed to create website 0x80070020 message, disable your local antivirus or antimalware software and run the installation process again. You can re-enable your antivirus software once the installation completes. For more information, see this Veeam KB article.
.NET 3.5.1 WCF HTTP Activation Windows component prevents Veeam Backup Enterprise Manager from functioning. Make sure there is no .NET 3.5.1 WCF HTTP Activation Windows component on the Veeam Backup Enterprise Manager server prior to the installation.
Make sure there is no Microsoft Search Server installed on the machine. If you have Microsoft Search Server, uninstall it prior to the Veeam Backup Enterprise Manager installation.

If you want to use an already installed PostgreSQL instance for the Enterprise Manager configuration database, make sure the instance can use sufficient resources. For more information, see Configuring PostgreSQL Instance.
If you want to use an already installed PostgreSQL instance for the Enterprise Manager configuration database, make sure the instance contains the default postgres database. If you allow the setup to install a new PostgreSQL instance, the postgres database will be created on the instance automatically.

Since Enterprise Manager connects to the postgres database to access the configuration database, do not rename the postgres database upon the Enterprise Manager installation.

Check the Known Issues section of the Veeam Backup & Replication 12.3 Release Notes.

Configuring PostgreSQL Instance

When you create a new PostgreSQL instance, the default setup is configured to consume a minimum amount of resources, which may not be enough for Enterprise Manager performance.

When installing Veeam Backup Enterprise Manager, you can choose what PostgreSQL instance to use for the Enterprise Manager configuration database. You can use an existing PostgreSQL instance or create a new one.

If you let the setup create a new PostgreSQL instance, it will be configured automatically.
If you want to use an existing PostgreSQL instance, make sure that the instance configuration is sufficient for the Enterprise Manager performance.

To adjust the configuration of an existing PostgreSQL instance, take the following steps before you install Enterprise Manager:

On a backup server, run the Set-VBRPSQLDatabaseServerLimits cmdlet. The cmdlet generates the necessary PostgreSQL configuration and saves it to a dump SQL file.

Set-VBRPSQLDatabaseServerLimits -OSType <String> -CPUCount <number of CPU cores> -RamGb <RAM in GB> -DumpToFile <file path>

For example:

Set-VBRPSQLDatabaseServerLimits -OSType Windows -CPUCount 16 -RamGb 32 -DumpToFile "C:\config.sql"

On the machine with the PostgreSQL instance where you want to deploy the Enterprise Manager configuration database, use the psql tool to apply the configuration from the dump file.

The tool is located in the PostgreSQL installation folder.

psql -U <user> -f <file path>

For example:

psql -U postgres -f "C:\config.sql"

Include the pg_stat_statements library to the PostgreSQL configuration. To add the library, you can manually edit the shared_preload_libraries option in the postgres.conf file.

Alternatively, you can do it by by executing the SQL code:

Check the content of the shared_preload_libraries variable.

SELECT * FROM pg_settings
WHERE name = 'shared_preload_libraries';

Add the pg_stat_statements library to the shared preloaded libraries.

If the shared_preload_libraries value is empty, assign pg_stat_statements to the shared_preload_libraries variable.

ALTER SYSTEM SET shared_preload_libraries = pg_stat_statements;

If the shared_preload_libraries value is not empty, add pg_stat_statements to the current value separated by comma.

ALTER SYSTEM SET shared_preload_libraries = <existing libraries>, pg_stat_statements;

Restart the PostgreSQL service for the new configuration to take effect.
Install the pg_stat_statements extension. The extension is used to analyze the PostgreSQL performance.

CREATE EXTENSION IF NOT EXISTS "pg_stat_statements";