Veritas Alta™ SaaS Protection Administrator's Guide
- Section I. Introduction to Veritas Alta™ SaaS Protection
- Section II. Administration portal
- Section III. Manage users and roles
- Section IV. Manage searches/eDiscovery/cases
- Section V. Configure policies
- Section VI. Perform restores
- About restore
- Prerequisites for restore
- Restore dashboard
- Restore Exchange Online mailboxes
- Restore SharePoint Online Sites and data
- Restore SharePoint/OneDrive/Teams Sites and 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 Entra ID objects
- Restore Slack data
- Restore data to File server
- Restore options
- Section VII. Perform data share
- Section VIII. Perform data downloading
- Section IX. Add and configure connectors
- About connectors
- About connectors
- Overview of connectors
- Configuring the capture scope
- Configuring credentials
- Apps Consent Grant Utility
- Exchange Online connector
- Adding Exchange Online connectors
- Configuring the capture scope for Exchange connectors
- Configuring the capture scope for Exchange connectors
- SharePoint Online connector
- Teams Sites collections connector
- OneDrive connector
- Teams chat connector
- Audit log connector
- Google Drive connector
- Gmail connector
- Salesforce connector
- Entra ID (Azure AD) connector
- Box connector
- Slack connector
- EML connector
- Managing connectors
- About connectors
- Section X. Perform backups
- Section XI. Backup limitations
- Section XII. Events
- Section XIII. Manage Stors (Storages)
- Section XIV. Manage Scopes
- Section XV. Manage auditing
- Section XVI. Known Issues
Architecture of Veritas Alta SaaS Protection
The components in the Veritas Alta SaaS Protection architecture are:
An Azure account established for Veritas Alta SaaS Protection provides a dedicated single-tenant instance. This setup ensures the segregation of data and supports secure multi-region data storage while adhering to data residency requirements.
Each tenant incorporates a single Hub database that contains global configuration details.
Depending on requirements, a Hub may have one or multiple StorSites. While most tenants have a single StorSite, organizations with multiple office locations in different countries may have multiple StorSites aligned with Microsoft Azure regions to enhance scalability. Each StorSite includes at least one app service.
A target storage repository located within a StorSite. A StorSite may encompass one or multiple Stors, each featuring two dedicated Blob storages with tiering. The workloads of each tenant are allocated to one or more Stors as necessary. Blob storage supports data deduplication and encryption at rest, with the option for data redundancy through storage replication as preferred by customers.
Each tenant connects to a dedicated SQL database, complete with distinct settings for policies, storage redundancy, storage tier, encryption, and metadata.
Each Stor includes at least one App service, facilitating user access to the web UI. Veritas Alta™ SaaS Protection offers two web UI alternatives: The Administration portal and the End-User portal.
Veritas Alta SaaS Protection is integrated with Microsoft Entra ID. Veritas Alta SaaS Protection supports multifactor authentication, Enterprise Single Sign-On (SSO), Access Control Lists, and granular role-based access control (RBAC).
Workflow for data back up and restore in Veritas Alta SaaS Protection:
Backup data flow:
The required data is fetched by the Connector service installed on the Windows server from SaaS applications.
The Connector service establishes communication with the App service to acquire a token, enabling the App service to store data in the Blob Storage. Initially, data is written to the staging area, also referred to as 'Blob storage,' where the App service performs an integrity check before transferring it to the actual Stor.
The data is written to the Blob storage, and the App service performs deduplication before writing the data to the Blob storage.
The App service updates the database with essential metadata information.
The App service signals the preparation of indexes of the backed-up items within the Search Cluster.
Restore data flow:
The App service and the database connect to initiate a request for the necessary data.
The App service retrieves data from the Blob storage.
The data is transferred by the Export service to the target workload.
The Export service prepares a job and transfers the data into the SaaS applications according to the specified restore locations.
For additional information on managing Stors,