Please enter search query.
Search <book_title>...
Veritas Alta™ SaaS Protection Administrator's Guide
Last Published:
2024-09-27
Product(s):
Veritas Alta SaaS Protection (1.0)
- 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
Best practices to restore Entra ID objects
When performing a restore, there can be a case where a set of entities have a relationship with each other. In this case, the restore for that set of entities needs to happen within the same restore job because, during the restore of permanently deleted items, new Entra IDs are generated.
Performing the restore of a subset of these entities in two separate jobs is not supported, as there is no way for the other restore job to identify the corresponding new IDs that have been generated against the ones in the backup.