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 Delete and Stub policies
- Apps Consent Grant utility
- Backup Exchange Online mailboxes
- Adding connectors for Exchange Online data
- Configuring the capture scope for Exchange connectors
- Configuring the capture scope for Exchange connectors
- Backup SharePoint Online
- Supported SharePoint Online sites and data for backup and restore
- Adding backup jobs (connectors) for SharePoint Online sites and data
- 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 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 and Metadata
- Restore Salesforce Metadata to the same or another organization
- Restore 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
- Configuring 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 when configuring policies for SharePoint environments
The Delete and Stub policies are applied to the following workloads:
SharePoint Online
OneDrive for Business
Teams Site
The Delete and Stub policies are applied starting from the second full backup, after all the data is successfully backed up during the first full backup. When you run the second backup, select the
option.The Delete and Stub policies are applied to full backups only and do not affect the incremental backups that occur between two full backups.
When the Delete and Stub policies target the same item, the Delete policy takes precedence, permanently deleting the item from the source SharePoint environment.
The policy criteria can be customized based on the
, , and of the items. You can define any or all of these criteria according to your specific data retention requirements. When configuring the exclusion based on , you must configure either the or criteria for that policy.The Stub and Delete policies apply to files within user libraries that are exclusively based on document libraries and not any other library type.
The Stub policy specifically applies to items derived from the document content type.
The Stub and Delete policies do not apply to ASPX files.
In a versioned document library, an item is stubbed only if all its versions also meet the policy criteria. For example, if the policy is based on the last modified date, all versions of the item must have been modified before the date specified in the policy.
When a document library in SharePoint has the
setting enabled, items are not stubbed by default.
For more information on the end-user workflow when an end-user clicks on a stub, refer to the topic Restore OneDrive/SharePoint stubbed items in the Veritas Alta™ SaaS Protection End User Guide.
As an administrator, you can control the options available to the end-user. You can direct them to the End User portal to restore the specific item or initiate the download when a stub is clicked. You can use the following permissions to manage the experience of the end user in restoring or downloading the stubbed items:
: With this permission, when an end-user clicks on the stubbed item, they are redirected to a webpage. On this webpage, an option is available to restore the item to its original location at the time of backup.
: With this permission, when an end-user clicks on the stubbed item, they are redirected to a webpage. On this webpage, an option is available to download the last backed-up version of the SharePoint file to the local computer.
If only this permission is assigned, the download starts when the user clicks the stub.
See Assigning permissions to users.
Both of these permissions are inherently included in the
role.
You can monitor the restore progress on the
.
A SharePoint user with the View permission can restore the file. The user retains the same permissions for the file after restoration as they had on the stub.
If a stub is moved from its original location, the restore fails. An Administrator needs to restore it from the Administration portal.
The last modified date is updated to the current time after restoration or download. This should prevent the item from being picked up by the configured Stub policy if configured based on the last modified time.
Only the last backed-up version of the SharePoint item before the stubbing occurred is restored.
You can monitor the restore progress on the Restore dashboard, but you cannot rerun the restore.
If your tenant is Scope enabled, then clicking on a stub always download the last backed-up version of the SharePoint file to the local computer.