Veritas Alta™ SaaS Protection Administrator's Guide
- Introduction to Veritas Alta™ SaaS Protection
- 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
- Restore dashboard
- Discovery
- Add Tagging polices
- Add Tiering policy
- General administrative tasks
- Manage Stors (Storages)
- Managing Scopes
- Known Issues
Limitations of Salesforce Metadata backup and restore
The following are the limitations of Salesforce metadata backup and restore:
The metadata types listed on the following link are not supported by Salesforce; therefore, Veritas Alta SaaS Protection cannot support the backup and restore of them.
The backup and restore of the unpacked metadata are only supported as it is a common use case.
Note:
The Managed packages, such as Apex classes, Triggers, and Lightning Web Components, are accessible only to the providers of the Managed package.
After restoring a Dashboard that is created in Salesforce Lightning, its display name appears as a unique numeric ID instead of its original name.
Action Plan Template Standard Object Permission in the Profile Metadata type will not be backed up unless user has customize application permission and IndustriesActionPlans license.
The following metadata types cannot be restored properly due to Salesforce metadata API limitation:
The PathAssistant metadata type does not restore
due to Salesforce metadata API limitation.The ChatterExtension metadata type does not restore
field due to Salesforce metadata API limitation.The Sites metadata type does not restore
due to Salesforce metadata API limitation.The PresenceUserConfig metadata type does not restore
and due to Salesforce metadata API limitation.
For the objects with
enabled, the (the text fields in the object) are not restored using metadata API.The ReadOnly.profile cannot be restored due to Salesforce metadata API limitation.
The backup and restore of the following metadata components is not supported:
DataCloudCompanyMatch.cleanDataService
DataCloudLeadAppend.cleanDataService
Calendar2.sharingRules
OpportunityCompetitor.standardValueSet
The backup and restore for the following Standard Tab settings is not supported:
standard-DelegatedAccount
For more information, refer to the following link:
standard-JournalType
standard-ManufacturingProgram
standard-MfgProgramCpntFrcstFact
standard-MfgProgramVariantFrcstFact
standard-MfgProgramForecastFact
standard-RevenueAsyncOperation
standard-PromotionMarketSegment
standard-GoalAssignment
standard-GoalDefinition