As part of your overall data protection planning, plan your Salesforce restore operations according to your requirements.
After the restore is complete, you can view all the associated details of the restore job. For more information, see Viewing Restore Operation Details.
You can restore Salesforce records to a file system or to the Salesforce cloud.
When you perform a record-level restore, you can view all versions of a Salesforce object record.
If you have triggers or workflows that are associated with the unmanaged package and the restore destination is a Salesforce instance, then you can have the Commvault software disable the workflows or triggers before the restore, and then activate them after the restore completes (Disable triggers and rules check box). Use this option to improve load performance and minimize errors.
You can restore the Salesforce data the following destinations:
A file system path that you specify when you perform the restore
A relational database management system that you specify when you perform the restore
The Salesforce cloud
You can restore Salesforce metadata to a file system or to the Salesforce cloud. All metadata supported by the Salesforce API is supported for restore operations.
Seeding a Salesforce Sandbox
You can perform a restore to seed a Salesforce sandbox.
Perform granular or bulk seeding by configuring rules or templates that specify the objects that you want to seed and the object records to use for the seeding. If you want to seed multiple objects that are not related, these objects need to be included in the seeding template. The seeding templates will be saved for immediate or future use, consistent reseeding of development or training sandboxes, or to be edited to create new templates.
You can specify any of the following records:
Records that are returned from a user-defined SQL query
Records that have been backed up in the last N number of days
The most recently backed up N records