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 At-Rest WORM retention policies
: Before adding an Ingestion WORM retention policy, you must read the guidelines to understand its implications.
To add/edit an At-Rest WORM retention policy
- Access the Administration portal.
The home page of the Administration portal is displayed.
- Click Retention.
- On the left, click At-Rest WORM retention policies.
- Do any of the following:
To add a new policy, click New policy.
To update an existing policy, click the name of the policy.
- On the Create policy page, perform the following steps:
Enter an appropriate name for the policy.
From the Stor dropdown list, select the Stor for which the policy has to be added.
Select one of the following schedules to run the policy:
One time: This option runs the policy once, and after it has run, the schedule changes to Never.
Continuous: This option runs the policy every time the policy evaluation runs.
Date range: To schedule the policy, specify a From and To date range to run.
Never: Use this option if you are not ready to run the policy or want to stop the policy from running. The time-scheduled policies are converted to Never after they have run.
Select any of the following action modes as required:
Preview: Lists the items for retention. To ensure that you understand fully the scope of data that will be retained, 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 will not run. Toggle the Status option to enable the policy.
As soon as the policy is enabled, it runs as per the schedule that is set in the Schedule section.
Configure the policy based on any of the following criteria:
Last modified date: Select the option to create a policy based on the item's last modified date.
If a policy is set for a retention period of one month, the item cannot be deleted or modified in the Stor for one month from the last modified date.
Note:
Last modified date: The date on which a user has performed a modification to the item.
Archived date: Select the option to create a policy based on the item's archived date.
If a policy is set for a retention period of one month, the item cannot be deleted or modified in the Stor for one month from the archived date.
Note:
Archive date: The date on which the item was previously backed up to Cohesity Alta SaaS Protection.
Date item: Select this option to retain the item for a certain period from when it starts meeting the policy.
Exact date: Select this option to set a specific date for the retention period. For times when you do not want the retention calculated, and you want items to expire on a specific date.
Metadata: Select the required metadata.
When this option is selected, the available datetime or smalldatetime fields in the Stors metadata are displayed in the Metadata dropdown. To retain the item version, you can then specify the period beyond that given date.
From the Retention period dropdown list, set the required retention period (in days, months, or years).
Select the required retention period from the Retention period section. (In days, months, or years).
(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.
The policy is displayed on the page under the storage (Stor) for which you have added the policy.
When a policy is configured and enabled it enforces retention periods during which items cannot be deleted or modified.