Set Up Continuous Data Protection in Backup & Recover for Salesforce

Set Up Change Data Capture in Salesforce

1. Navigate to Setup, Integrations, Change Data Capture.
2. Add the nominated objects.
   

   Note Recommendation - how to nominate the objects?:

   • Do you have any data in Salesforce that changes more rapidly than the rest? (“high velocity”)
   • Is this data mission-critical? (“high value”)
   • How many Salesforce objects are used to capture this high-velocity, high-value data?
3. Click Save.
4. Save the object list. This will be used in the Continuous Backup Service generation.

Set Up a Continuous Data Protection Service

1. In the top-right corner of the application screen, click the User icon.
2. select Account Settings.
3. Select the Overview tab.
4. Review the Plan Features section.

Create a Continuous Data Protection Service

Note After a Continuous Data Protection Service is created, it can't be modified.

1. Go to the Backup tab and Click New Service.
2. Select the Salesforce icon.
3. Select from:
   • Production Data
   • Sandbox Data
4. Turn on Continuous Data Protection.
5. In the Objects field, enter the objects, corresponding to their Salesforce API name.

   Keep in mind that the API name is case-sensitive. For example:

   • Account
   • Contact
   • CustomObject__c

   Continuous Data Protection comes in multiples of five objects up to a maximum of 40 objects. The same object quota is available for both Sandbox and Production.

   The upper right corner displays [added objects]/[object quota].

   

   Note The object name entered must match the Salesforce API naming convention. If the name entered is not an exact match, the relevant Continuous Data Protection service will not be added.
6. The frequency is fixed at 24 hours, and can't be changed.
7. Click Add Service. You are prompted to authenticate with Salesforce, authorizing access to your org.
   A confirmation message ribbon appears at the top of the screen, confirming that a new Salesforce Partial Data (or Partial Sandbox Data) service has been added.
8. After the initial backup is complete, go to Backup Now and select Create Point-in-time Backup.

Identify Stream Statuses and Errors

1. Error: Failed to capture events due to an authentication error. Reauthenticate the service.

   How to solve the issue: Reauthenticate the service. Once the service is reauthenticated, click Retry to get the stream back online.

2. Error: Failed to capture events due to configuration of: [object]. Check your CDC entities in Salesforce.

   How to solve the issue: Go to Salesforce > Change Data Capture and add the missing entities. After adding the entities back in CDC, click Retry to get the stream back online.

   

   Note The object name entered in Own must match the Salesforce API naming convention. If the name entered isn't an exact match, this error will be raised.
3. Error: Failed to capture events. Pub/Sub API limit reached.

   How to solve the issue:

   • The stream will return online when the Pub/Sub API quota is reset.
   • If you raised the Pub/Sub API quota, click Retry to get the stream back online.
4. Error: Failed to capture events. REST API limit reached.

   How to solve the issue:

   • The stream will return online once the REST API quota is reset.
   • Click Retry to check if the stream back.
5. Error: Internal Error

   How to solve the issue: Contact Own Support.

Create a Point-in-Time Backup

Note Up to 30 PIT backups can be created in a rolling 30 day period.

1. Select the Continuous Backup service.
2. Click the arrow next to Back Up Now and then Create Point-in-time Backup.
   1. Add a Label to the backup (not mandatory).
   2. Choose the Requested Snapshot Time (date and time) from before the data corruption. Choose a specific date and time after the data corruption, then click Apply.
3. Click Create and a new Point-in-time Backup will start.
   

   Note Events are stored up to 30 days; therefore a PIT backup can only be generated up to the last 30 days. To increase how long events are stored, please contact support.

Identify Point-in-Time Backups