About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
Here is the overview on the restore procedure for you need to perform for Salesforce Data, Metadata, CRM Content, and Sandbox seeding.
Table:
| This procedure restores structured data that includes standard and custom objects, its associated records, nested child objects and records, and linked files, attachments, documents, and notes. You can restore the structured data in two ways:
|
This procedure restores unstructured data, such as files and documents that are not linked to structured data. It includes files and documents from public/shared libraries created using the tab tab. It also includes restoring all public/shared libraries. See Restore Salesforce CRM Content (Unstructured data restore). | |
This procedure restores the metadata such as profiles, roles, settings, and so on associated with the data. |
Note:
Restoring the Connected app removes the ConsumerKey from the .zip file before restoring, as a new ConsumerKey is generated at the destination organization.
You can restore the Salesforce data and metadata to the same or another Salesforce instance. Restoring data and metadata to another instance is also referred as Sandbox seeding. Cohesity Alta SaaS Protection supports the following configurations for Sandbox seeding:
Production to Sandbox
Sandbox to Sandbox
The following are the prerequisites to perform Sandbox seeding:
Configure a separate export location for the target Salesforce organization.
Note:
You are required to add a Salesforce connector for the target Salesforce organization. This process auto-creates an export location for it.
Note:
To restore an inactive owner, refer to the link: https://help.salesforce.com/s/articleView?id=000386875&type=1