Please enter search query.
Search <book_title>...
Cohesity Alta SaaS Protection 2.x.x Administrator's Guide
Last Published:
2025-04-24
Product(s):
Veritas Alta SaaS Protection (1.0)
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- Manage users and roles
- What is a connector?
- Configure credentials
- Pre-requisites for Microsoft 365 connectors
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- 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
- Perform restores using Administration portal
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore Box data
- Restore Google Drive data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- About Entra ID (Azure AD) objects and records restore
- Restore dashboard
- Install services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Priority for storage Tiering
In Cohesity Alta SaaS Protection, the storage Tiering priority is organized in the following order: Hot Tier, Cool Tier, and Archive Tier. This means that the Hot Tier is given the highest priority, followed by the Cool and Archive Tiers. For example, if overlapping policies select the same data for Cool or Archive Tierings, the data is directed to the Cool Tier. The warmer Tier (Hot Tier) always takes precedence in such cases. The Stors that have Storage tiering settings overrides the tiering to the Archive Tier. These settings are based on the last accessed or captured configuration.