To store a local copy of the Salesforce data and to perform certain functions, store your Salesforce data in a database. Each Salesforce organization needs a separate database. For example, if you back up two production organizations and one sandbox organization, configure three databases.
The following functions require a database:
Restore to the Salesforce cloud
Amazon RDS for PostgreSQL
Amazon Aurora for PostgreSQL version 11.9
Azure Database for PostgreSQL
The Commvault Salesforce application connects to a database with default options such as connection timeout, host, instance, and so on. If your setup requires additional connection properties, configure the sf_dbConnectionProperties additional setting.
If TLS is enabled for your database, you must use the sf_dbConnectionProperties additional setting to add the sslmode connection setting with a value of sslmode=require to the server that acts as the access node for Salesforce. For more information about adding a setting, see Adding a Setting for a CommCell Entity.
You must have a user who has NOSUPERUSER, CREATEDB, CREATEROLE, INHERIT, NOREPLICATION permissions. For example, you can create a user with these permissions using the following command:
CREATE USER sf_user WITH NOSUPERUSER CREATEDB CREATEROLE INHERIT NOREPLICATION PASSWORD 'sf_user';
You must be able to access the database from the internal network.
For operations that restore data from the PostgreSQL database, such as record-level restores, the database must be accessible from the Web Server on default port 5432.
Important: If you are not using the default port, you must open the port that you configured.
Hardware and Software Requirements
The PostgreSQL version must be V9.3 or higher.
The database host must have at least 8 CPUs/processors and 16 GB of memory. We recommend 32 GB of memory.
The database host must have free space that is at a minimum equal to four times the size of the Salesforce used data storage. This amount of free space accounts for the following:
Salesforce data change frequency because the database maintains all versions
Data used space
Additional table size, such as share and history tables
Additional space is needed for out-of-place restore operations. When you perform an out-of-place restore, the source data is copied, the copy is used for the restore, and then the copy is removed.
For instructions about checking the storage usage values, see Checking the Values for Salesforce Storage Usage.
Best Practice: To avoid filling the disk with transaction logs during the Salesforce backup, disable Write-Ahead Logging (WAL).