You can restore all of the organization data from production to a full Salesforce sandbox or from one sandbox to other sandbox. Cross organization restores are supported from full backups only.
Tip: Due to the complexity and nature of Salesforce, some objects and records might not restore successfully. Issues that can block records from being restored include API limitations, data integrity, complexity in hierarchical relationships, and automation processes that utilize triggers, flows, and rules. To avoid errors or for faster results, disable the validation rules, Apex triggers, flows, and workflows. For the same benefits for managed packages, uninstall the packages. (Managed packages cannot be disabled using APIs.)
Due to the complexity and nature of Salesforce, some objects and records might not restore successfully. Issues that can block records from being restored include API limitations, data integrity, complexity in hierarchical relationships, and automation processes that utilize triggers, flows, and rules. For more information about why some objects and records do not restore successfully, see Troubleshooting General Salesforce Errors and Troubleshooting Salesforce Restore Operations.
Before You Begin
Verify that the Salesforce user who performs the restores has the required permissions.
In Salesforce, create a destination Sandbox that contains the same metadata as your source organization. The Commvault software does not restore metadata as part of a Sandbox restore.
For information about creating sandboxes, go to the Salesforce help site, Create a Sandbox.
Add an app for the destination organization.
Review the objects that are not supported for restores.
To regain space or to prevent duplicate records after the restore is complete, reset the destination organization.
Verify that you have enough free space (it must be the size of the data that you want to restore):
If you restore from media, then the free space must be available on the staging database.
If you restore from the database, then the free space must be available on the catalog database.
You must have enough data and file storage space on your destination Salesforce environment.
Verify that the destination profile, users (communityNickName), and RecordType match the source profile, users (communityNickName), and RecordType.
Verify that the objects exist on the destination organization.
If you want to mask sensitive data during the restore, configure data-masking policies.
From the navigation pane, go to Protect > Applications > Salesforce.
The Salesforce page appears.
Click the action button , and then click Restore.
The Select restore type page appears.
Select Object level restore.
The Backup content page appears.
Optional: In the upper right of the page, select the backups that you want to view.
To use the most recent backup, click Show latest backups.
To use a backup from a specific date, click Show backups as of a specific date, select a date, and then select the backup.
To use a backup from a date range, click Show backups for a date range, select a date range, and then select the backup.
Select the data that you want to restore:
To restore files, select the check box next to Files.
To restore objects, select the check box next to Objects.
To restore both files and objects, select both check boxes.
Note: For a full sandbox restore, do not select individual files or objects.
The Salesforce restore options dialog box appears.
Next to Restore target, select Salesforce.
Under Destination details, from the Destination organization list, select the Salesforce destination.
Under Options, set the restore options:
Note: The Parent objects to restore and Child objects to restore options are ignored because for a full sandbox restore, all objects are restored.
To disable the Salesforce triggers and rules, select the Disable triggers and rules check box.
After the restore is complete, the workflows and triggers are automatically enabled.
To apply data masking, select the Apply masking on destination check box, and then from the Select data masking policy list, select the data-masking policy.
Note: Data masking can be applied when a cross-instance restore is run and data masking policies are defined.