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/edit Tiering policies
See About the Tiering policy .
To add/edit a Tiering policy
- Access the Administration portal.
The home page of the Administration portal is displayed.
- Click Tiering.
- On the left, click Cool storage tier policies or Archive storage tier policies as required.
Cool tier
Cool tier is an online tier optimized for storing the data that is infrequently accessed. Data in the Cool tier should be stored for a minimum of 30 days. The Cool tier has lower storage costs and higher access costs as compared to the Hot tier.
Archive tier
Archive tier is an offline tier optimized for storing the data that is not accessed frequently and that has flexible latency requirements on the order of hours. Data in the Archive tier should be stored for a minimum of 180 days.
- Do any of the following:
To add a new policy, click New policy.
To update existing policy, click the name of the policy.
- On the Create policy page, do the following:
Enter a descriptive name for the policy. This name is displayed in policy dropdown lists on several pages.
From the Stor name dropdown list, select the Stor where you want to create the tier policy.
Select any of the following schedules to run the policy:
One time: Runs once as per the policy interval settings, and then its schedule gets changed to Never.
Continuous: Runs as per the policy interval settings.
Date range: Lets you specify a From and To date range to run the policy.
Never: Set this option if you are not ready to run the policy or want to stop the policy from running. The One time scheduled policies gets converted to Never after its runs.
Select any of the following modes as required:
Preview: Lists the items for tiering.
To ensure that you understand fully the scope of data that will be tiered, run the policy in Preview mode initially.
Production: Retains the items as per policy.
By default, the status of the policy is disabled; it is saved but cannot not run. Toggle the Status option to enable the policy.
As soon as the policy is enabled, it runs as per the schedule set in the Schedule section.
(Optional) Configure filters to include or exclude specific locations or data from having the policy applied.
See How to add a Location filter?.
See How to add a filter?.
Click Create to add a policy or click Update to save the changes.
For Cool tier policies, it can be useful to add a clause for Archived At while adding a filter. It is the date the file was uploaded to Cohesity Alta SaaS Protection. The default or older than one month is typically sufficient as it ensures that the data has time for any post-processing, such as full-text indexing; while on the Hot tier where the data has the lowest access costs.
Archive tier policies automatically exclude data based on the Stors storage tiering settings for the last accessed and items captured in the last N days. The policy runs according to the Policy Evaluation Interval for the selected Stor.
Warning:
Removing a Cool or Archive tier policy causes the data to be moved back to the Hot tier unless there is an overlapping Cool or Archive tier policy. Unwanted access and transaction costs incur and also could charge deletion costs if the data hasn't been on the tier long enough.
See How to add a Location filter?.
See How to add a filter?.