Modifying Salesforce Backup Sets to Sync to a Database

At the backup set level, you can configure Salesforce data to be backed up to a database. This configuration is also available at the instance level.

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

Before You Begin

Verify that you have the following information:

  • The type of database

  • The client that hosts the database

  • The database name

  • The credentials for a user who meets the following criteria:

    • Microsoft SQL Server: Owner permissions and if the database does not exist, has the dbcreator role

    • PostgreSQL: Super user permissions

Procedure

  1. In the CommCell Browser, expand Client Computers > client > Cloud Apps > instance.

  2. Right-click the backup set, click Properties.

    The Salesforce Backup Set Properties dialog box is displayed.

  3. On the Backup Options tab, specify the backup location:

    1. In the Download Cache Path box, type the full path for the staging location that the Commvault uses when it backs up the data.

    2. To back up Salesforce objects in a database, select the Sync To Database check box, and then provide the following information:

      • From the Database Type list, select the database type.

      • From the Database Host list, select the client that hosts the database.

      • From the Database Name list, select the database name.

      • In the Database Port box, type the port that you use to connect to the database.

      • In the User Name and Password boxes, type the credentials for a user who has permissions for the database.

        Note

        If you use Microsoft SQL Server, the user must be a SQL authentication user.

  4. Click OK.

Loading...