An overview of Gearset Backup
Your free 30-day trial with Gearset includes access to our backup tool. Protection against critical data loss can be as easy as a few clicks.
Simply follow our guide to creating your first data backup job or, if you have more questions, keep reading.
The first run
Once you have set up your backup job, it will start the first run, which will establish an initial baseline of data and metadata in your org.
Establishing this baseline can involve processing a large amount of data - larger orgs can have terabytes of it - which inevitably takes some time for Gearset to request and download from Salesforce.
For more information about the first run that a backup job takes see this article:
A data backup job's first run
Restoring data from a backup
Gearset offers multiple powerful ways to restore data from your backup's runs in the event of a data loss.
Due to our in depth understanding of Salesforce data, it is possible to restore data with dependent objects also included automatically.
For more information about the methods of data restoration see this article:
Data restoration using Gearset
FAQs:
What is the difference between high frequency and standard backup jobs?
What is the difference between high frequency and standard backup jobs?
Standard backup jobs run every 24 hours and can back up as many objects as are included in your backup data filter. A high frequency job runs every hour and backs up to 10 objects that you deem the most vital to be backed up in your org at a more regular cadence.
Standard jobs can be configured to back up any new objects added to your org, and will also back up all metadata from your org.
High frequency jobs will only back up the objects you select to back up, and will only back up metadata corresponding to any selected data objects.
The maximum retention policy of your data on a high frequency jobs is 1 month, whereas a standard backup job can be set to store your data for up to 99 years.
Where is the data stored?
Where is the data stored?
Your backup data is stored at the AWS data center in the region you chose for your Gearset account — either the US (US West 2), Ireland (EU West 1), Australia (AP Southeast 2) or Canada (CA Central 1).
You can check this article if you are unsure which one you chose:
Where is your backup data stored?
Who can access the backup?
Who can access the backup?
Within your team, the owner of the backup can assign granular access permissions to the other team members, namely View, Browse, Execute, Edit, Delete, Restore and Download permissions.
For more information on backup user permissions see these articles:
How to set backup job permissions
And Providing access to team members section of below article:
Creating your first data backup job
What orgs can be backed up?
What orgs can be backed up?
You can back up any kind of Salesforce org, such as dev orgs, prod orgs, sandboxes and even scratch orgs.
Is the data encrypted?
Is the data encrypted?
Your data is encrypted both in transit and at rest. Backups are encrypted with a ‘per customer key’. You can delete your encryption key at any time to make your backup data completely irretrievable.
Does Gearset back up both data and metadata?
Does Gearset back up both data and metadata?
Yes. Gearset backs up both data and metadata on every backup run. We back up the metadata because metadata represents all the Salesforce customizations that are unique to your business, it needs to be protected. Metadata often needs to be restored before data can be restored. And permissions metadata types control access to sensitive data.
What does it mean if my job is in 'maintenance'?
What does it mean if my job is in 'maintenance'?
Rarely when our engineers here at Gearset need to do vital maintenance, you'll notice a banner that states that your backup is offline for testing. During the maintenance period your backup job will not run. This will not last long and the backup will be available again shortly.
Ready to get started? Why not create your first data backup job?