Gearset's data backup jobs provide comprehensive data restore capability. In the event that any data is lost, corrupted, or otherwise changed in an org, you can easily use a snapshot from your backup job to restore that data to its previous state.
Restoring metadata before you restore data
Records can only be restored correctly if the underlying metadata (configuration) between the backup snapshot and your org is consistent. If there have been significant changes to your org's metadata and data, we recommend you restore the metadata first, before the data. This will reduce the chances of unexpected data deployment errors.
You can see how to run a metadata restore from a data backup job here.
Want to restore multiple records?
Restoring records using the quick data restore option will only restore the individual records that are selected, and won't bring in referenced objects. If you'd like to restore their full data structure, we recommend you use the
Configure restore option which will launch the full data restore flow.
See how to restore a large number of records and their full data structure here.
Restoring a single record
You can restore single records from the job history details page.
View detailson the data backup job you want to restore from.
In the job history, click
View detailsfor the data backup run that you'd like to restore a record from.
From the object overview page, select the object you'd like to restore records for.
You can switch between viewing deleted records, changed records, and new records from the data browser. Select a record to see the details.
Select a record to restore by checking the box next to its ID. Once you've selected a record (or several), the
Quick Restorebutton will become enabled.
Quick Restorebutton to begin preparing the data restore plan for the selected records.
Once the plan has generated, you'll get a chance to review the changes before they are deployed.
Restoreto run the restoration process. Once it has completed, you'll see the status.
The results of the restore will be stored in your data deployment history in the app.