Demo of Gearset’s Salesforce backup solution

Share with

Description

In this video, we dive into a comprehensive run-through of Gearset’s backup and recovery solution and how it can help you avoid a data disaster.

Find out how:

  • Gearset backups your data alongside your metadata for complete piece of mind
  • You can monitor changes to your environment over time with the backup job history feature
  • Gearset allows your to quickly rollback changes to your metadata
  • Gearset keeps you up to date with any unusual changes to your data with smart alerts

Find out more:

Relevant webinars:

Transcript

This is Gearset

Gearset sits externally to Salesforce, hosted on AWS, actually leveraging many of the same data centers and servers that Salesforce use for their own processing too. But crucially, Gearset is separate to Salesforce.

Fundamental for any backup and recovery solution is to have that data sort off platform.

We can see here then that I have one single pane of glass to view all of my environments, whether it's a production or maybe Sandbox environment backed up daily or even hourly.

So Gearset gives me that higher frequency of backup availability for my most critical object.

Maybe I have patient records or transactional information that I need to keep that hourly snapshot of. And that's where Gearset can support me.

Jumping into any of these backup jobs, because Gearset believes that data and metadata are so intrinsically linked.

We combine not only data, but metadata in each of these jobs.

Data here is obviously including files and attachments, so they're all backed up, stored, and restorable when required.

You'll see this visual graph, which shows how my environment is evolving over time and shows me any new, changed, or deleted records on a snapshot by snapshot basis.

Metadata deletion, or corruption, as we mentioned earlier, is often the cause of data loss. And many teams don't actually have a way to either identify or restore metadata corruption.

So by jumping into the metadata tab here, Gearset is running a continual daily monitoring on each of my orgs, so he's taking a snapshot of all of the metadata that sits in these environments.

And will present to me if the metadata is changed, or it's just the same as it was before.

If in any particular scenario, the metadata has been seen as changed, we'll highlight a difference here. And by simply viewing the changes, This will then be able to show me exactly what was changed or removed since that previous snapshot run.

This is great so that I can see exactly, is this what I expected? Maybe I was running a deployment. Or something untoward taking place.

But not only can I identify this, and I get the granularity to see right down to the fields view on this layout as an example, what's been deleted?

But if something undrawed has occurred, I simply want to roll this back.

And by rolling back then, I get the full ability because Gearset has a such a fundamental understanding of Salesforce metadata.

I can roll back all metadata supported via the Salesforce metadata API, and I can do this one by one. Maybe I just want to restore a few pieces.

That have been changed, or maybe I wish to roll back everything.

The Gearset enables me to do this. And once I've selected the items, that I wish to roll back.

I simply can select next to restore this metadata, those foundational building blocks for my org.

But Gearset is built in proprietary problem analysis, and he's saying to me, Lawrence, this is going to be unsuccessful.

And it's showing me exactly why with this problem analysis.

I'm immediately told that I've actually not included the opportunity marketing layout that is fundamental for this restoration to be successful. However, Gearset streamlines this for me.

At this point then, I can simply move to the pre deployment summary, give this a name, Any notes as well associated with this rollback, as well as tying to a Jira ticket, if I wish.

I can then validate and simply deploy that metadata back into my environment to get back to the state that I was before any corruption occurred.

That's great, though, to restore the metadata, but then what about my data from there?

Data loss can be identified here by any of these red elements that highlight to me that some records have been deleted.

But additionally, smart alerts can be configured to proactively notify you via email or even Slack or Microsoft Teams channels when specific criteria are triggered.

So this means that you're practically notified and can take the meet appropriate remediation actions immediately.

But often with data loss or corruption, you may not know when this occurred.

So having a powerful search capability is fundamental.

So GISSA enables me to search across all of my backup runs for a term, whether it matches the entire account, field or not in this instance, and I can see here that I have an account called Millie Morris that was added captured again, couple of changes occurred, and then a deletion actually occurred yesterday morning at two AM.

To restore this, it's a matter of clicks with Gearset. By viewing this back up run, I get taken straight to the snapshot where the deletion occurred. I don't have to try and find that myself.

I can then either restore en masse or just the records that I wish to restore.

Gearset understands that Salesforce is a hierarchical database. So when you delete a parent account, that Millie was in that in that example, a cascade deletion will occur in Salesforce. So any child objects, relationships, and associated records will also be deleted.

But guess it understands those relationships, and will show those to me here and enable me to selectively pick those up and choose those as part of my restoration.

On the right hand side, I can preview the records if I wish to check what these are. But when I'm ready, I can simply continue.

When we were looking at the metadata, we saw a Gearset as built in proprietary problem analysis to ensure that this restoration is successful.

That's great for metadata, but what we're seeing here is the same is built for data, meaning that I don't need a full understanding of my Salesforce data structure because Gearset will identify this for me.

So here I'm showing that again, Florence, this is going to be unsuccessful.

You've trying to you're trying to deploy a contact role, without the associated opportunity, and again, an account without its parent account.

But because This understands this data structure, I can simply bring those along with one click.

From here then, I can simply move ahead disable any validation rules, triggers, or workflows if required, and then deploy that data back into my environment.

So it's just the number of clicks to restore any deleted data, but the same is true for changed data as well.

Maybe an integration is gonna arrive or a deployment. So here we can see I have a post deployment snapshot, and I can jump in here to view any changes.

I get my new, changed, and deleted records highlighted to me immediately.

And for any of my objects, I can view these records, and then jump to the changed records if I wish to investigate some potential corruption.

At this point, ma'am, I can make I can choose as many records as I wish to restore, and then select just the fields that I wish to roll back.

Here, I know for as part of my deployment, I accidentally updated all of the names on my records, so I choose the name field.

The phone number changes. They're legitimate so I can leave those alone.

I can again then plan this restoration to revert this data back to how it was before the corruption occurred.

So it's just a matter of clicks then as we've seen. To not only restore data from a deletion scenario, but also from a corruption scenario too.

Additionally, Gearset supports a more big bang approach.

So for any of these snapshots, I can go back in time.

A customer I'm speaking to just earlier today, actually, described this as Gearset time machine feature.

So here, I've got a free deployment snapshot, and I can simply restore all of my data back to that point in time if I wish to roll this back to get all of that data back into my org. And the same can be said for metadata. I could download this if I wish. Or maybe I wish to just push this data or metadata into a separate environment just to make sure that the restoration is, as I expected, before I proceed.

Gearset supports all of these options, giving me full control of how I wish to do that restoration.

So I appreciate that was a very quick overview on some of Gearset's backup, solution. However, I hope that's given you a good flavor on how we can not only provide data and metadata backup, as well as those really simple restoration pathways.