Veritas Alta™ SaaS Protection Administrator's Guide
- Introduction to Veritas Alta™ SaaS Protection
- EDB and EDB compliance
- Active Directory synchronization
- Manage users and roles
- API permissions
- Add connectors
- Overview of adding connectors
- Add Exchange Online connectors
- Configure the capture scope for Exchange connectors
- Configure the capture scope for Exchange connectors
- Add SharePoint Online connectors
- Configuring the capture scopes for SharePoint connectors
- Add Teams site collections connectors
- Add OneDrive connectors
- Add Teams chat connectors
- Add Audit Log connectors
- Add Google Drive connectors
- Add Gmail connectors
- About the Salesforce connector
- Add Entra ID (Azure AD) connectors
- Add Box connectors
- Add Email/Messages
- Apps Consent Grant Utility
- Add Retention policies
- Perform backups
- Manage backed-up data
- 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 the Salesforce Data, Metadata, and CRM Content restore
- Limitations of Salesforce Metadata backup and restore
- About Entra ID (Azure AD) objects and records restore
- Perform restores using Export Utility
- Restore dashboard
- Install services and utilities
- Discovery
- Add Tagging polices
- Add Tiering policy
- General administrative tasks
- Manage Stors (Storages)
- Managing Scopes
- Known Issues
Storage tiering and full-text search
Veritas Alta SaaS Protection search cluster can perform full-text indexing of content, item-level metadata, folders, and access rights. This indexing enables the searchability of all data based on metadata.
Initially, data chosen for the Cool or Archive tiers is stored on the Hot tier to reduce access and transaction charges. This placement facilitates tasks like full-text search, data classification, and using Microsoft Cognitive Services.
Data accessed from the Cool tier remains in the same tier and is not recalled to the Hot tier. Accessing data from the Archive tier first needs to be changed to the Hot or Cool tier from the archive. The Read operations on the Cool tier may incur higher costs. Also, changing the tier, also called rehydration, involves additional Azure costs. Once data is indexed, it remains searchable regardless of the storage tier. To avoid early deletion fees from Azure, it's recommended to maintain data on the Cool tier for a minimum of 30 days and 180 days for the Archive tier.