Cohesity Alta SaaS Protection Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- 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 for Microsoft 365 connectors
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Add SharePoint connectors
- 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
- Configuring capture scope for SharePoint connectors
- End-user SharePoint data access in Cohesity Alta SaaS Protection
- Run the Delete and Stubbing policies to the SharePoint Online environment
- Limitations of SharePoint connector
- 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
- 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)
About the Tiering policy
You can use the following types of tiers on the storage (Stors):
Table:
Tier types | Usage | Storage cost | Access cost |
|---|---|---|---|
Hot tier | Frequently accessed or modified. Designed for data needing immediate access and frequent modifications. | Higher than Cool and Archive tiers | Lower than Cool and Archive tiers |
Cool tier | Infrequently accessed or modified data is ideal for storage in the Cool tier. This type of data may not require immediate access but should still be accessible. The data that is stored in the Cool tier should be kept for at least 30 days; otherwise, Microsoft charges a prorated penalty. Cohesity recommends using the Cool storage for the workloads that have occasional retrieval activity. | Lower than Hot and Archive tiers | Higher than Hot tiers |
Archive tier | Data that is not frequently accessed and needs to be stored for long-term retention can be stored in the Archive tier. The retrieval times may be longer. The data in the Archive tier should be stored for at least 180 days, or Microsoft charges you a prorated penalty. While you can view the content in Cohesity Alta SaaS Protection, it may take several hours to be fully retrieved and available. Initiating a request to access data on this tier starts the rehydration process. | Lower than Cool and Hot tiers | Higher than Cool and Hot tiers |
The data that is stored in the Hot or Cool tiers can be retrieved instantly. The data that is stored in the Archive tier may take several hours to be available for retrieval. For more detailed information about blob storage operations and pricing, refer to the following knowledge base article: