> Essential > Applications > Salesforce > Restores

Seeding a Salesforce Sandbox

Salesforce provides a sandbox that you can use for testing and demo purposes. You can populate (seed) the sandbox with a Commvault backup from your production Salesforce data or another Salesforce sandbox. Data is restored from a local (sync) database.

Perform granular or bulk seeding by configuring rules or templates that specify the objects that you want to seed and the object records to use for the seeding. If you want to seed multiple objects that are not related, these objects need to be included in the seeding template. The seeding templates will be saved for immediate or future use, consistent reseeding of development or training sandboxes, or to be edited to create new templates.

You can specify any of the following records:

  • All records

  • Records that are returned from a user-defined SQL query

  • Records that have been backed up in the last N number of days

  • The most recently backed up N records

Tip

Due to the complexity and nature of Salesforce, some objects and records might not restore successfully. Issues that can block records from being restored include API limitations, data integrity, complexity in hierarchical relationships, and automation processes that utilize triggers, flows, and rules. To avoid errors or for faster results, disable the validation rules, Apex triggers, flows, and workflows. For the same benefits for managed packages, uninstall the packages. (Managed packages cannot be disabled using APIs.)

Before You Begin

  • Verify that the Salesforce user who performs the restores has the required permissions.

  • In Salesforce, create a destination Sandbox that contains the same metadata as your source organization. The Commvault software does not restore metadata as part of a Sandbox restore.

    For information about creating sandboxes, go to the Salesforce help site, Create a Sandbox.

  • Add an app for the destination organization.

  • Review the objects that are not supported for restores. For sandbox seeding, you cannot restore objects such as attachments and ContentVersion.

  • Verify that you have enough free space (it must be the size of the data that you want to restore):

    • If you restore from media, then the free space must be available on the staging database.

    • If you restore from the database, then the free space must be available on the catalog database.

    • You must have enough data and file storage space on your destination Salesforce environment.

  • Verify that the profile, users (communityNickName), and RecordType are the same on the destination and the source.

  • Verify that the objects exist on the destination organization.

  • If you want to mask sensitive data during the restore, configure data-masking policies.

  • Verify that you have the following database information:

    • The type of database

    • The client that hosts the database. The access node is able to connect to the database instance using JDBC URL.

    • 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

  • Verify that the Web Server can communicate with the sync database by opening the necessary default ports.

Procedure

  1. From the navigation pane, go to Protect > Salesforce.

    The Salesforce Overview page appears.

  2. Go to the Organizations tab.

  3. In the Name column, click the app.

    The app details page appears.

  4. On the Sandbox seeding tab, click the action button action_button for the template, and then click Seed sandbox.

    The Seed sandbox dialog box appears.

  5. In the Destination details section, from the Destination sandbox organization list, select the Salesforce organization.

  6. To disable the Salesforce triggers, flows, workflows, and rules only for the restore, select the Disable triggers and rules check box.

    After the restore completes, the flows, workflows, and triggers are automatically enabled.

  7. To restore empty and null values for a backup, select the Restore empty fields check box.

    • To associate all restored records in the destination org with the logged-in user as the record owner (if a record owner does not exist in the destination org), select the Associate ownership to the logged-in user check box.

  9. To apply data masking, move the the Apply masking on destination toggle to the right, and then from the Data masking policy list, select the data-masking policy.

    Note

    You can apply data masking when you run a cross-instance restore and data masking policies are defined.

  10. Click Run.

  11. Click Confirm.

Result

  • After the operation completes, the destination sandbox contains the records that meet the rules that you configured.

  • To troubleshoot errors that occur during a restore operation, see Troubleshooting Salesforce Restore Operations.

Loading...