Skip to main content

How can I do a total Salesforce restore?



My mom posted this article on her LinkedIn, and I think that it is so clever!  I'm proud of you mommy!  This is also my "thank you" for taking me to breakfast on Saturday when I woke up at 4:30am.  I just wasn't tired! I appreciate that you shared your coffee and let me eat pancakes off of your plate after I threw my egg onto the floor.



The Capstorm team is asked on a weekly basis: What happens if I need to do a full restore of my Salesforce? All data...all metadata.
A complete restore is not possible.
 With a traditional database, you can easily disable access and replace the database image with a backup. This approach can put a database into a known state at any desired point in time. This can not be done with Salesforce.
Why not? A few reasons...

Theoretically the need for a complete restore is possible....thousands of tables, millions of records, and all custom Salesforce configuration. This would, however, indicate that either

  1. Your Salesforce governance has suffered a massive failure / breach, or
  2. The Salesforce infrastructure has failed.

Capstorm's team has been involved in Salesforce disaster recovery since 2011 and has yet to see this happen despite partnering with hundreds of businesses, many with multiple production instances.

A few of the worst production data disasters that we have seen:

  • A Salesforce data center failure lost 6 hours of production updates
  • A key logger corrupted specific fields over a period of two months
  • An overzealous programmer deleted a large set of attachments
  • A mistake in a trigger corrupted a known set of fields

Each of these cases required precise surgical restores to recover specific data. In each case the corrupted or missing data could be identified and restored.


Comments

Popular posts from this blog

Process Automation Specialist Superbadge - 5

A project with Daddy: My favorite daily process! Making dinner for Mom! Tonight's challenge involves the creation of two processes.   Processes.  Have you guessed the theme of the photos that go along with the Trailhead - Process Automation Specialist Superbadge series?They are a few of my favorite day to day processes!  You, my amazing reader, get more than tips for a Salesforce Superbadge.  You also get personal insight into the life of a Trailhead Baby!  I hope that you feel inspired. Process Builder sketch Last night, I drew a rough sketch of my process: Was it pretty?  No. Did it help?  Yes! The sketch allowed me to organize all of the instructions into a reasonable order before I started clicking.  It also removed the approval steps from Process Builder and highlighted (with *'s) the prerequisite items to building my process. * Email Alerts I needed the Email Alerts set up before I could create either the process or ...

Service Cloud Specialist Superbadge - 1,2,3

A confession - I know next to nothing about service cloud.  While I was excited that a new superbadge was available, it made me a little nervous that I had to do all of the prerequisites and tackle new things like macros.  New things - new year - let's get started! (Right after I finish guitar practice) If you are also a service cloud novice, the Omni-Channel Basics is a crucial prerequisite even though it is not officially required. Challenge 1 App Appearance  This, like all superbadges, requires a careful read through the instructions prior to any clicking.  I found it helpful to take a separate notebook and write down the steps that I would need for each challenge step - for example -  My rough notes for challenge 1: Create 2 profiles  Tweak service Console 3 new items on utility bar Allow access for new profiles Create User  Beware - After editing the service console, you might have to edit the new profiles.  I found i...

Lightning Experience Specialist Superbadge - 8

The best present? Santa says that I am getting a little brother in April! Let's import some data!  It's simple to mass delete the records if there are inserted incorrectly - and you have me to help!  The goal with this post is to move beyond the "how" of data import and explain the "why."  The challenge makes more sense when you think about the relationships between the objects.  I'll explain more below. First: A confession I, the Trailhead Baby, am not a perfect Salesforce admin.  Even though I completed this entire Superbadge in 2017, I still messed up the data import badly enough that I had to mass delete all of my records and start over.   Quick tip: It may help to delete the existing data before you start the import.  This way, when you extract recordID's, you only extract the ID's of the records that you have already imported vs. the records that were already in the Trailhead Playground by default. You can use many da...