Gearset's data backup jobs provide comprehensive metadata restore capability. In the event that any unwanted configuration changes are made in an org, you can easily use a snapshot from your backup job to restore the org to its previous state.

Restoring data to an org

This article explains how to restore metadata to an org. If you want to restore data (records), you can see how here.

Restoring or replicating metadata

Metadata restoration or replication happens from the history of a data backup job.

  • Click View details  on the data backup job you want to restore from.

  • Choose the date of the org snapshot you'd like to restore from and click Use snapshot. Use Restore snapshot metadata to restore the metadata; or click on Replicate snapshot to restore the metadata in an org different from the one being backed-up.

  • Only if you are using Replicate snapshot, a dialogue opens up, allowing you to choose the target org where the metadata will be restored to and it confirms the date of the snapshot being used to restore from. Confirm the org you want to replicate the metadata to and click Start comparison to move to the comparison stage.

  • Gearset will run a comparison between the snapshot of your target org and its live state, and show the metadata differences.

  • From the comparison results, you can view the changes and select components to restore through the standard deployment flow. The steps to follow are listed below, but for more in-depth details on how to run a metadata deployment, see our support documents here.

  • Select an item to view the metadata differences. The diff viewer in the lower half of the screen will show the differences between the backup snapshot (on the left) and the org's live state (on the right).

  • To add an item to your deployment package, check the box next to its name. It will then appear in the Selected items tab.

  • When you've selected what you want to restore, click Next.

  • Gearset will now check your deployment package for any missing dependencies which are likely to cause your deployment to fail. If it finds anything which may cause issues, it will suggest changes to your package to fix them. These fixes are optional, but following the recommendations will make your package more likely to deploy successfully. Click Next  when you've reviewed the suggested changes.

  • The pre-deployment summary shows you key information about what you're about to deploy. This includes the metadata items and their change type, as well as confirming your source and target.

  • Clicking Deploy now will begin the deployment. Once this process begins, Gearset will upload the package to Salesforce and queue it up for release. You can also run a validation first, or specify the test level to run during the deployment from this page.

  • Once the deployment completes, it will be saved in your deployment history under the Backup type and your org will be restored to the backup snapshot state.

Did this answer your question?