Cohesity Alta SaaS Protection Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- Cohesity Alta SaaS Protection Copilot (AI chatbot)
- Manage users and roles
- What is a connector?
- What is a connector?
- Supported SaaS workloads and backup capabilities
- Workflow to protect data using Cohesity Alta SaaS Protection
- Know your subscription details
- 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
- Backup and restore support for SharePoint Online
- Supported and unsupported SharePoint Settings and Types for backup and restore
- Supported Sites and List templates for backup and restore
- Supported SharePoint permission objects for backup and restore
- Setting up SharePoint Online protection with Cohesity Alta SaaS Protection
- Configure additional backup options for SharePoint/Teams site/ OneDrive connectors
- 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 Deletion policies
Before you implement the Deletion policy, consider the following points:
Deletion policy is used to permanently and irreversibly delete specific content from the Stors. However, this policy does not affect:
Items under legal hold.
Items within the WORM retention period.
Items tagged with behavior.
You should always run the policy in mode to review which all items will be deleted.
It is recommended that you consult with Cohesity Support before adding any policy.
The policies operate based on the configured policy evaluation interval within your Cohesity Alta SaaS Protection environment, which is typically set to every 15 minutes by default.
The deletion process within Cohesity Alta SaaS Protection occurs in two steps. Firstly, references to records are removed, followed by sending delete instructions to the underlying Stors. The periodic maintenance tasks clean up empty folders without any descendants.
Empty folders are cleaned by background maintenance.
Data becomes inaccessible immediately after deletion begins.
Garbage collection processes clean all copies of the deleted content.
Overwriting: Deleted storage blocks are eventually overwritten.
- Access the Administration portal.
The home page of the Administration portal is displayed.
- Click Retention.
- On the left, click Deletion policies.
- Do one 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 an appropriate name for the policy.
From the Stor list, select the Stor for which the policy has to be added.
Configure the schedule to run the Deletion policy based-on one of the following criteria:
One time: Runs once as per the policy interval settings, and then its schedule changes 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: If you are not ready to run the policy or want to stop the policy from running. The one time-scheduled policies is converted to Never after its runs.
Select any of the required action modes:
Preview: Lists the items, which can be deleted with this policy.
Production: Deletes the items in the scope of the policy unless it is protected by legal hold or WORM policy.
By default, the status of the policy is disabled; it is saved but cannot 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.
(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.
While you editing the policy, the Update option is displayed, click it to save the changes.
The policies are displayed on the Deletion policies page, under the storage (Stor) for which you have added the policy.