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)
Version control settings
This feature lets you gradually reduce the number of backed up versions over time to optimize storage within Cohesity Alta SaaS Protection.
By default, all versions are retained in Cohesity Alta SaaS Protection unless you enable the Version control feature.
Version control feature optimizes backup storage by keeping only the most relevant backed up versions and removing older, redundant ones.
The following retention settings are used to configure this feature for the selected Stor:
You must click this option to enable the version control feature.
Once this feature is enabled and the configuration is saved, it cannot be disabled. Also, the following default settings can only be edited once.
Table:
Settings | Time period | Pruning action | Retention strategy |
|---|---|---|---|
: | First 14 Days | No pruning occurs. | All newly added versions are retained. |
: | Day 15 to Day 105 (Next 90 Days) | Pruning starts; scans from feature enablement date. | Only one daily version is retained. |
: | Day 106 to Week 52 (Next 52 Weeks) | Further pruning occurs. | Only one weekly version is retained. |
: | After 52 Weeks to 240 Months | Final pruning phase. | Only one monthly version is retained for long-term storage. |
After 240 months, for versions beyond all retention periods (daily, weekly, and monthly), only the latest version will be retained, and all other versions will be pruned based on the last modified date.
Starting from Cohesity Alta SaaS Protection version 2.36.2, version pruning for versions beyond all retention periods is disabled for SharePoint Online.
Note:
For each time period, the backed-up version retained depends on whether the Stor supports versionings at the source. In Cohesity Alta SaaS Protection, SharePoint and Box are the two Stors that can have backed up items which are versioned at source. For example, a SharePoint Stor can have backup copies all versions of an item that are also present in a SharePoint Document Library that supports versioning.
: For a given time period, the most recent backed-up version (based on the archived time) is retained, and the rest are pruned.
Example: From day 15 to day 105, when only one version is retained per day, the most recent backed-up version from all item modifications on that day is retained.
: For a given time period, the version with the highest version number, as per the source, is retained, and the rest are pruned.
Example: From day 15 to day 105, when only one version is retained per day, the version with the highest version number from all item modifications on that day is retained.
SharePoint scenario: If a file in a versioned SharePoint Document Library was modified three times in a day, creating versions 8, 7, and 6, and all these versions were backed up, the Version Control feature in Cohesity Alta SaaS Protection will retain only version 8 for that day.
This behavior applies from the Cohesity Alta SaaS Protection 2.36.2 release.
Note:
For SharePoint, for a given time period, if the version to be considered for retention is less than 1 KB, pruning action is not done for all the versions in that batch for the item, when executing the retention strategy. This behavior is applicable from 2.36.2.
Note:
If a file is modified multiple times within the same day and the most recent changes occur within a span of a minute, Cohesity Alta SaaS Protection may retain any one of those versions. This behavior is applicable for any version control behavior before the Cohesity Alta SaaS Protection 2.36.2 release.