Cohesity Alta SaaS Protection 2.x.x Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- Manage users and roles
- What is a connector?
- Configure credentials
- Pre-requisites for Microsoft 365 connectors
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Protect Teams sites
- Protect OneDrive data
- Protect Teams chats
- Protect GoogleDrive data
- Protect Gmail data
- Protect Audit logs
- Protect Salesforce data and metada
- Protect Entra ID objects
- Protect Box data
- Protect Slack data
- Protect Email/Message data
- Configure Retention policies
- Perform backups
- View and share backed-up data
- Analytics
- Perform restores using Administration portal
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore Box data
- Restore Google Drive data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- About Entra ID (Azure AD) objects and records restore
- Restore dashboard
- Install services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Key considerations and prerequisites for adding Salesforce connectors
Consider the following points before adding Salesforce connectors to ensure a seamless setup:
: The name of the Veritas Backup Admin user you have created within the targeted Salesforce organization.
: The instance URL of the targeted Salesforce organization.
: The Consumer Key is generated when you add a Connected App to the targeted Salesforce organization.
For more information, visit the knowledge base article Obtain user details, consumer key, and URL.
By default, Salesforce connectors back up all objects except for
, , and , 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: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.
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.
objects:
Feed objects are views into the
object. Cohesity Alta SaaS Protection backs up only the 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.
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. |
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. | |
You are required to create a user, a profile, and a Connected app in each Salesforce organization that is to be backed up. For procedure, refer to the following knowledge base article: Adding a user, profile, and Connected App within the Salesforce organization. For backing up unstructured data objects, the Veritas Backup Admin must have the 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. | |
To protect the public libraries in the target organization, they must be shared with with access permission. | |
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:
For objects that already have an auto-number field in your Salesforce organization, you must first add the custom field manually. | |
permission | If you want to restore the Campaign object, the user must have the permission. |