Salesforce Data Protection Best Practices


Verify the Connection to Salesforce

When you perform any of the following operations, click Test Connection to verify that you can connect to Salesforce or the local database:

  • Creating an app

  • Performing a restore operation to the database, or Salesforce

Creating New Users for Backup and Restore Operations

If you create a new user for backup and restore operations, verify that the new user exists in both production and sandbox environments. Additionally, verify that the new user's Community Nickname is the same in all environments.

Use the Simple Recovery Model for the SQL Database

We recommend that you use the SQL Simple Recovery Model for the SQL database so that the disk does not get filled up with transaction logs during backup operations.

Backup Schedules

Use the following schedule strategy because the catalog/sync database only contains the latest data cycle:

  • Schedule daily incremental backups

  • Schedule monthly or quarterly full backups depending on your RPO

Incremental Backups

Scheduling: The Salesforce replication API does not hold changes more than 30 days, so schedule daily incremental jobs.

Restoring: If you restore the data to a database, or the Salesforce cloud, and you changed data during the full backup, then you might need to restore additional incremental jobs so that you minimize data inconsistencies.

API Calls for Salesforce Backups

Calculate the percentage of API calls needed for backup operations, and if needed, adjust the percentage. For information, see Optimizing the API Calls for Backup Operations.