Veritas Alta™ SaaS Protection Administrator's Guide
- Section I. Introduction to Veritas Alta™ SaaS Protection
- Section II. Administration
- Section III. Manage backups (connectors)
- Overview
- About backup jobs (connectors)
- Overview for adding backup jobs (connectors)
- Configuring the capture scope
- Configuring credentials
- Configuring or updating backup policies
- Configuring or updating Delete and Stub policies
- Apps Consent Grant utility
- Backup Exchange Online mailboxes
- Backup SharePoint Online
- Backup Teams Sites collections
- Backup OneDrive for Business
- Backup Teams chats
- Backup Audit logs
- Backup Google Drive data
- Backup Gmail data
- Backup Salesforce data
- Backup Microsoft Entra ID (Azure AD) objects
- Backup Box data
- Backup Slack data
- Backup EML data
- Managing backup jobs (connectors)
- Backup jobs (connectors) statuses
- Browsing the backed-up data
- Events
- Overview
- Section IV. Manage restores
- About restore
- Prerequisites for data restore
- Restore dashboard
- Restore Exchange Online mailboxes
- Restore SharePoint Online data
- Restore Teams chats and Teams Channel conversations
- Restore Audit logs
- Restore Box data
- Restore Google Drive data
- Restore Gmail data
- Restore Salesforce data
- Restore Microsoft Entra ID objects
- Restore Slack data
- Restore data to File server
- Restore options
- Section V. Manage data sharing
- Section VI. Manage data downloads
- Section VII. Manage Stors (Storages)
- Section VIII. Policies to manage the backed-up data
- About policies in Veritas Alta™ SaaS Protection
- Confguring policies for data retention (WORM policies)
- Configuring policies for data deletion (Deletion policy)
- Configuring policies for data tiering (Tiering policy)
- Configuring Tagging polices
- Managing policies
- Section IX. Manage users and roles
- Section X. Manage Discovery cases and searches
- Section XI. Manage Scopes
- Section XII. Manage auditing
Points to consider before adding retention policies
When implementing retention policies on Veritas Alta SaaS Protection, you should remember these points:
Items with a retention period cannot be deleted.
Retention periods can only be extended, not reduced.
If an item has multiple retention periods, the longest one takes priority, except for WORM Pending status.
The policy indicating WORM pending status plus the one based on last modified or archival date takes priority if an item falls under multiple retention policies.
Event-based retention applies retention periods to existing item versions, with new versions checked periodically.
Item-level WORM policies apply retention periods during the write process for new items and versions, without affecting existing versions in storage (Stor).
Deleting a policy does not affect existing items already under the retention period.