Cohesity Alta SaaS Protection Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- Cohesity Alta SaaS Protection Copilot (AI chatbot)
- Cohesity Alta SaaS Protection Administrator portal (Web UI)
- Supported SaaS workloads
- Workflow to protect data using Cohesity Alta SaaS Protection
- Manage users and roles
- API permissions
- What is a connector?
- What is a connector?
- About transient errors
- Overview of adding connectors
- Configure General settings
- Configure Capture scope
- Configure User filter
- Configure Group filter
- Configure Folder filter
- Configure credentials
- Configure Custom backup policy and guidelines
- Configure Delete policy for SharePoint Online and guidelines
- Configure Stubbing policy
- Guidelines to configure Stubbing policy for SharePoint Online
- Schedule a backup
- Configure email addresses to get notifications
- Review configuration and edit/save/initiate backup
- Connectors page
- Connector status
- Edit connector configuration
- Delete connectors
- Pre-requisites to setup protection for M365
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Setting up SharePoint Online protection with Cohesity Alta SaaS Protection
- Backup and restore support for SharePoint Online
- End-user SharePoint data access in Cohesity Alta SaaS Protection
- Run the Delete and Stubbing policies to the SharePoint Online environment
- Backup limitations for SharePoint Online
- 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
- About analytics
- Analytics page and refresh behavior
- Aggregation buckets
- Gain insights into storage utilization
- Gain insights into storage utilization for Entra ID and Salesforce connectors
- Gain insights into blocked activities, most active users, and more
- Gain insights into data volume (size and item count) on legal hold
- Gain insights into data volume (size and item count) saved in different Enhanced cases
- Gain insights into data volume (size and count) under different policies
- Gain insights into data volume (size and item count) under different Tags
- Gain insights into data volume (size and item count) under different Tags behaviors
- Gain insights into storage savings after deduplication and compression
- Gain insights into data ingestion trends
- Perform restores using Administration portal
- About restore
- Prerequisites for restore
- Restore Exchange Online mailboxes
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore O365 audit logs
- Restore Box data
- Restore Google Drive data
- Restore Gmail data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- Guidelines for Schema changes in Salesforce organization to prevent restore failures
- Restore Standard and Custom objects (Structured data restore)
- Custom Object restore - post processing steps
- Restore specific Records (Structured data) using Query filters
- Restore Salesforce CRM Content (Unstructured data restore)
- Restore Salesforce files/documents in Public/Shared libraries (Unstructured data restore)
- Limitations of Salesforce Data restore
- Salesforce Objects not supported for restore
- Key considerations for Salesforce Metadata restore
- Restore Salesforce Metadata
- Limitations of Salesforce Metadata backup and restore
- About Entra ID (Azure AD) objects and records restore
- Restore Slack data
- Restore data to File server
- Set default restore point
- Configure Restore all, Restore all versions, Point-in-time, and Specific range restore options
- Configure email addresses for notifications
- Downloading an item
- Restore dashboard
- Install services and utilities
- About services and utilities
- Pre-requisites to download and install services and utilities
- Downloading services and utilities
- Where to install the services and utilities
- Installing or upgrading services and utilities
- Configuring service accounts for services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Add Salesforce connectors
You need to create a separate connector for each Salesforce organization you want to back up. Each connector backs up data, files, attachments, CRMs, and metadata. Cohesity Alta SaaS Protection uses two different storages: one for unstructured content like files, attachments, and metadata, and another for structured content like objects and records.
Before adding a connector, refer to the following topic for prerequisites and to understand the key considerations:
See Key considerations and prerequisites for adding Salesforce connectors.
To add a Salesforce connector to back up data and metadata
- Access the Cohesity Alta SaaS Protection Administration portal.
The home page of the Administration portal is displayed.
- On the Backup card, click Connectors.
- Click New backup connector.
- Click Salesforce.
- On the General tab, do the following:
In the Name field, enter a name for the connector.
Note:
The Type field displays the connector type.
From the Stor for unstructured data (files, attachments and metadata) dropdown list, select the SalesforceFiles Stor provided by Cohesity as a prerequisite for connector creation.
Note:
The same Stor can be used for multiple connectors. If unavailable, contact Cohesity Support.
From the Stor for structured data (objects and records) dropdown list, select the SalesforceFiles Stor provided by Cohesity as a prerequisite for connector creation.
If the Stor is not available, contact Cohesity Support.
The Machine field displays the Connector service to host this connector.
You can change the selected one from the list if required.
(Optional) Enable the Enable email notification option to receive backup job status email notifications.
Click Next.
- On the Capture scope tab, configure your backup scope.
By default, Salesforce connectors back up all Standard objects, Custom objects, files, attachments, CRMs, and metadata from the targeted Salesforce organization except for Feed, History, and Share objects, 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.
Refer to the following topic to know the backup limitations of Salesforce connectors.
See Limitations of Salesforce connectors.
While backing up a Salesforce organization, a field length mismatch may sometimes occur, resulting in a backup failure. Check the error logs to identify the fields that have returned more data than current field length. It is recommended to widen the field length of these fields in your Salesforce organization to prevent backup failures and ensure that all data is backed up. If widening the field length of these fields is not possible, enable the Allow backup of fewer characters if data returned by API is more than Field length checkbox to back up only the initial characters that fit within the current field length. Note that the remaining characters will not be backed up.
- On the Credentials page, do the following:.
From the Salesforce organization type dropdown list, select the required type: Production or Sandbox.
In the Salesforce organization user name field, enter the name of the Veritas Backup Admin user you have created within the targeted Salesforce organization as pre-requisites.
In the Salesforce organization instance URL field, enter the URL of the targeted Salesforce organization.
In the Consumer key field, enter the key, which is generated while adding the Cohesity Alta SaaS Protection Connected app to the targeted Salesforce organization.
Click Generate certificate.
A success message is displayed.
Note:
Certificate is used for OAuth-based authentication.
On the pop-up, click Keep to download the certificate.
Save the certificate to the local computer.
Click Next.
- On the Scheduling tab, schedule backup jobs.
See Schedule a backup.
- On the Email notifications tab, configure email addresses to receive notifications about backup activities.
- On the Review tab, save the settings and initiate the backup.
- Go to the targeted Salesforce organization, upload the generated certificate.
Setting up a Connected App in Salesforce for use by Cohesity Alta SaaS Protection
Uploading a certificate to the Salesforce organization establishes secure communication and authenticates the connection between the targeted Salesforce organization and Cohesity Alta SaaS Protection. The process uses certificate-based OAuth authentication, linking the certificate to the Connected App in Salesforce organization to securely access Salesforce data and metadata with user consent.
Key points to remember:
Always upload the certificate after completing the connector creation process.
A new certificate is created if you accidentally click the Generate Certificate option on the Credentials tab. In such cases, replace the existing certificate with the new one.
If you edit the connector configuration, generate a new certificate and re-upload it.