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)
General tab
The General tab displays the following options:
Table: General tab options
Fields | Description | |
|---|---|---|
| | ||
| Displays the name of the Stor. | |
Displays the type of the Stor. | ||
Displays one of the following states of the Stor: | ||
| ||
| ||
| ||
| ||
Displays the size of the Stor that is same as the total size of the Blob. | ||
Select the check box to enable Personal Identifiable Information (PII) detection. If PII is enabled, the Stor is evaluated according to the policy interval and the content indexing scope. | ||
Select the check box to enable file versioning for the Stor. | ||
Select the check box to encrypt the data at rest. Note: Data in the rest is the data that is stored for later use. | ||
Select the check box to support the storage tierings for the Stor. | ||
Select the check box if the Stor supports pre-ingest encryption. The metadata field is added to the Stor. Note: If the pre-ingested encryption is enabled, the data in any Blobs gets decrypted during the export. | ||
Select the check box to hide the Stor from the End-User portal. | ||
Select the check box to enable Stor-level WORM for the Stor. Stor-level WORM provides a single WORM retention period for all content in the Stor. This setting is optionally configured on a Stor at the time of provisioning the Stor. Before performing the process of provisioning, you are required to discuss with the Cohesity Alta SaaS Protection technical support team. After a Stor is provisioned in WORM mode, the settings cannot be changed. Specify a retention period for WORM. The specified WORM retention protection is applied to all data that is archived in the Stor. After the WORM retention period is completed, the content is deleted. | ||
Select the check box to enable Item-level WORM for the Stor. Item-level WORM supports one or more WORM retention periods on the Stor. Item-level WORM retention periods are driven by the document-level policies that are run in real time during the write process. Multiple item-level WORM policies can be used within a Stor. The setting for item-level WORM is configured on the Stor at the time of provisioning the Stor, the settings cannot be modified. | ||
Select this option to enable Locally Redundant Storage for the Stor. LRS is the default Blob replication configuration that Cohesity Alta SaaS Protection provides. Three synchronous copies of the data are maintained in a single datacenter. LRS replicates the data within the region of the customer. To maximize durability, every request that is made for the content is replicated thrice. These three replicas are each placed in Fault Domains (FD) and Upgrade Domains (UD). The three replicas are spread across UDs and FDs to ensure that data is available even if hardware failure affects a single rack or when nodes are upgraded during a rollout. | ||
Select this option to enable Geo Redundant Storage for the Stor. Six copies of the data are made (three synchronous copies in one datacenter + three asynchronous copies in a second datacenter). GRS replicates the data to a secondary region that is hundreds of miles away from the primary region. The data is durable even in the case of a complete regional outage or a disaster in which the primary region is not recoverable. An update is first committed to the primary region, where it is replicated three times. Then the update is replicated to the secondary region, where it is also replicated three times, across separate FDs and UDs. | ||
Select this option to enable Read-Access Geo Redundant Storage for the Stor. Six copies are replicated to a second datacenter. RA-GRS maximizes availability for the storage account, by providing read-only access to the data in the secondary location, in addition to the replication across two regions that are provided by GRS. If data becomes unavailable in the primary region, the application can read data from the secondary region. | ||
For more details, refer to the following topic: | ||
Displays an interval to auto-run the policies defined for this Stor. By default, it is 15 minutes. You can edit the values as required. Note: Each Stor have its policy evaluation interval setting. Stor that contain data, which is accessed rarely may not need frequent policy evaluation. Stor that contain data, which is accessed actively by users and has indexing, and security requirements may need a policy evaluation interval to ensure policies run closer to real time. | ||
Displays the time when the policy evaluation was last run. | ||