Key considerations and prerequisites for adding Salesforce connectors

::Key considerations for adding Salesforce connectors

Consider the following points before adding Salesforce connectors to ensure a seamless setup:

Implement all the prerequisites
Ensure you have the following information ready:
- User name: The name of the Backup Admin user you have created within the targeted Salesforce organization.
- Instance URL: The instance URL of the targeted Salesforce organization.
- Consumer Key: The Consumer Key is generated when you add a Connected App to the targeted Salesforce organization.
  See Configure User, Profile, and Connected App for Salesforce.
Consider the default connector configuration
By default, Salesforce connectors back up all objects except for Feed, History, and Share, as these objects are not typically critical for business continuity. However, you can enable backups for these objects based on your specific needs, considering the following:
- History objects:
  These objects cannot be restored. Select them for backup only if retaining historical information on record or field-level changes is necessary for auditing purposes.
- Share objects:
  Only manual Share objects can be restored. Other types of Share objects cannot be restored due to Salesforce API limitations.
  Note:
  During the Salesforce restore, Share tables are automatically created unless they contain manual Share rules.
- Feed objects:
  Feed objects are views into the FeedItem object. Cohesity Alta SaaS Protection backs up only the FeedItem object to avoid duplication. Due to Salesforce API limitations, only specific types of FeedItem records can be restored.
Skipping these objects accelerates the backup process and reduces the storage required for Cohesity Alta SaaS Protection recovery points.

::Prerequisites for adding Salesforce connectors

Following are the prerequisites to add Salesforce connectors:

Table:

Prerequisite	Description
Connector per organization	You need to create a separate connector for each Salesforce organization you want to back up.
Structured Stor, SalesforceFiles Stor, Connector service, and Export service	Cohesity handles this prerequisite for your tenant as part of the provisioning process. Cohesity provides structured Stors, SalesforceFiles Stor, and one or more VMs (with preinstalled Connector and Export services) within your Cohesity Alta SaaS Protection tenant. Depending on the Salesforce organization, one or more Connector VMs and SalesforceFiles Stors may be provisioned. Cohesity provisions one structured Stor per targeted Salesforce organization; the SalesforceFiles Stor is shared across Salesforce connectors. If a connector using a structured Stor is deleted, you can create a new connector using the same structured Stor. Ensure that the URL and type (Production or Sandbox) of the Salesforce organization match those of the original structured Stor. . Note: The Connector and Export service are hosted on a single VM, which can support multiple connectors depending on the size of the Salesforce organization and its data. The Connector/Export service VM may host multiple connectors based on the size of the Salesforce organization we need to protect. For larger Salesforce organizations (with more data), the connector may be hosted independently on a separate Connector/Export service VM. Note: When these Stors are configured together for a connector, retain versions of backup data and metadata to protect the Salesforce organization.
Profile (Backup Admin), user (Backup Admin), and Connected App setup within the Salesforce organization	You are required to create a user, a profile, and a Connected app in each Salesforce organization that is to be backed up. See Configure User, Profile, and Connected App for Salesforce. For backing up unstructured data objects, the Backup Admin must have the Query All Files permission. Note: A Connected App is a mechanism that securely links external applications to Salesforce, enabling controlled access to Salesforce data and metadata through OAuth authentication, with customizable permissions and settings.
Sharing of public library	To protect the public libraries in the target organization, they must be shared with Backup Admin with Library Administrator access permission.
Auto-number field	If you want to restore Auto-number field with the same value as it was backed up. Salesforce's standard Auto-number fields (for example, Case Number) come with an additional restriction - their field type cannot be modified. Uploading data to a standard Auto-number field requires that the standard field be replaced with a copy used in place of the standard field. To set up a copy of the standard/custom field: Create a new custom field to hold the Auto-number data. Use the following trigger to populate the new custom field: trigger PopulateCustomAutonumberForCase on Case (after insert, after update) { List<Case> casesToUpdate = new List<Case>(); for (Case c : Trigger.new) { // Handle after insert and after update // Check if the custom autonumber field is null if (String.isBlank(c.CustomAutonumber__c)) { // Collect the IDs of cases that need updating casesToUpdate.add(c); } } if (!casesToUpdate.isEmpty()) { List<Case> casesToEdit = [SELECT Id, CustomAutoNumber__c, CaseNumber FROM Case WHERE Id IN :casesToUpdate]; for (Case c : casesToEdit) { // Populate the custom field with the standard case number field c.CustomAutonumber__c = c.CaseNumber; } update casesToEdit; } } For objects that already have an auto-number field in your Salesforce organization, you must first add the custom field manually.
Marketing User permission	If you want to restore the Campaign object, the Backup Admin user must have the Marketing User permission.

Key considerations and prerequisites for adding Salesforce connectors

Feedback

Feedback