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
- Your Salesforce governance has suffered a massive failure / breach, or
- 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
Post a Comment