Step 1: Review Requirements and Supported Features
Review the following topics to learn more about the requirements and supported features of Salesforce:
Step 2: Review the Salesforce Prerequisites
-
The following Salesforce editions are supported:
-
Developer
-
Enterprise
-
Performance
-
Unlimited
For additional support information, see Supported Salesforce Editions and Products.
-
-
You must have a Salesforce admin user and a security token for your Salesforce account.
-
Verify that you can connect to the Salesforce login URL from the access node.
-
Review the configuration and disk requirements for the access node. For more information, see Checking the Values for Salesforce Storage Usage.
Step 3: Install the Cloud Apps Package on the Linux Access Node
Review the following topics to prepare for the installation and to select the installation method that is most appropriate for your environment.
Step 4: Configure the Salesforce Environment
-
Add permissions to Salesforce profiles for the Salesforce users who will perform the back up operations and the restore operations.
Step 5: Configure a Database Server
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:
-
Object comparisons
-
Record-level restores
-
Restore to the Salesforce cloud
-
Sandbox seeding
Microsoft SQL Server
To have a local copy of the Salesforce data, you can install Microsoft SQL server. You can also use an Amazon RDS SQL server or an Azure SQL server. For information on the requirements, see Microsoft SQL Server Requirements for Salesforce.
-
If you install Microsoft SQL Server, have the following information:
-
The Microsoft SQL server name
-
The database name, instance name, and database port
-
The credentials for a user who has owner permissions for the database and if the database does not exist, has the dbcreator role
-
-
Verify that the client where you perform the Salesforce backup operations meets the system requirements. For more information, see Checking the Values for Salesforce Storage Usage.
PostgreSQL Server
To have a local copy of the Salesforce data, you can install PostgreSQL on a server. You can also use an Amazon RDS PostgreSql server. For information on the requirements, see PostgreSQL Requirements for Salesforce.
-
If you install PostgreSQL on a server, have the following information:
-
The PostgreSQL server name
-
The database name, instance name, and database port
-
The credentials for a user who has super user permissions for the database
-
-
Verify that the client where you perform the Salesforce backup operations meets the system requirements. For more information, see Checking the Values for Salesforce Storage Usage.
Step 6: Configure the Commvault Environment
-
Open the CommCell Console.
-
Configure a storage device. For more information, see one of the following:
-
If you configured an http proxy host for internet connections, then you need to configure the clients to access internet resources through the server. For more information, see Configuring an HTTP Proxy.
-
Optional: You can modify the default subclient or create subclients.
-
To include the metadata in the backups, configure the default subclient to include the metadata. For more information, see Backing Up Salesforce Metadata
-
To have a subclient that contains specific objects, add a new subclient. For more information, see Creating Salesforce Subclients to Protect Specific Objects.
Note
If you select this option, then make sure that you have a unique backup schedule for each subclient. For information on configuring a backup schedule, see Schedule Backups.
-
-
Optional: Decide whether you want the following additional functionality:
-
To be notified of events that require attention, see Alerts and Notifications - Overview.
-
To report and analyze critical data about your CommCell operations, see Reports Overview.
-
To manage security, see User Account and Password Management.
-