{"id":6211,"date":"2021-08-20T15:05:33","date_gmt":"2021-08-20T15:05:33","guid":{"rendered":"https:\/\/www.backupsfdc.io\/?p=6211"},"modified":"2021-08-20T15:05:33","modified_gmt":"2021-08-20T15:05:33","slug":"how-odaseva-stacks-up-against-salesforces-5-things-architects-overlook-when-choosing-a-data-backup-solution","status":"publish","type":"post","link":"http:\/\/18.233.203.232\/how-odaseva-stacks-up-against-salesforces-5-things-architects-overlook-when-choosing-a-data-backup-solution\/","title":{"rendered":"How Odaseva Stacks Up Against Salesforce\u2019s \u201c5 Things Architects Overlook When Choosing a Data Backup Solution\u201d"},"content":{"rendered":"\n

By Francois Lopitaux, Chief Product Officer at Odaseva<\/em><\/p>\n\n\n\n

The brilliant minds over at the Salesforce Architects blog (specifically Arun Sood) recently published a fantastic article<\/a>, \u201c5 Things Architects Overlook When Choosing a Data Backup Solution.\u201d\u00a0<\/p>\n\n\n\n

Arun gives an overview of why backup solutions are important to the Salesforce ecosystem:<\/p>\n\n\n\n

\u201cSalesforce customers need a data backup solution for one or more of a variety of reasons<\/strong>, including mandatory regulatory requirements, operations readiness requirements, and business continuity planning just to name a few.\u201c<\/p><\/blockquote>\n\n\n\n

He then details the 5 golden considerations<\/em> that enterprise architects tend to overlook when selecting and evaluating Salesforce data backup solutions. We couldn\u2019t agree more with each of the considerations described in the post<\/strong> – they are crucial to take into account to ensure that you have an effective, comprehensive Salesforce backup and restore solution in place.<\/p>\n\n\n\n

As the Chief Product Officer at Odaseva, I\u2019d like to expand on a few of Arun\u2019s points below and share how Odaseva\u2019s products are built to address each of the five considerations. I also added one additional consideration which is very important if it applies to your org. <\/p>\n\n\n\n

Consideration 1: Is your backup solution able to work within Salesforce constraints?<\/h2>\n\n\n\n

This consideration is all about working within Salesforce\u2019s out-of-the-box restrictions, which can become limitations when trying to restore data from a backup. Salesforce APIs must respect Salesforce workflows, which means that not every API operation is possible to set a record in the same position. <\/p>\n\n\n\n

It\u2019s an excellent point since many backup companies do not<\/strong> manage these use cases (and we\u2019ve found that many customers are not aware of this).<\/p>\n\n\n\n

Restoring data in Salesforce is not a point-and-click process. It requires a flexible solution, one that can manipulate the data both before and after restoration to handle Salesforce object workflow. <\/p>\n\n\n\n

Odaseva was designed to work within Salesforce\u2019s constraints. We built a flexible Enterprise Data Platform that accommodates Salesforce\u2019s out-of-the-box restrictions.<\/p>\n\n\n\n

For example in the scenario described in Salesforce\u2019s blog post, Odaseva works within those constraints by allowing you to transform the order before inserting it in an unactivated state, then restore the order and then reactivate it. <\/p>\n\n\n\n

Consideration 2: If you have managed packages installed in your organization, is your data backup solution able to backup and restore the managed package data?<\/h2>\n\n\n\n

This is a very important consideration that impacts not only managed packages, but also some Salesforce products like CPQ, Vlocity, Knowledge Articles, and even solutions that customers may have built which hardcode record IDs. <\/p>\n\n\n\n

Once a Salesforce object gets deleted and the recycle bin is purged, it is not possible to restore an object with the same record ID since the record ID is automatically generated by Salesforce. <\/p>\n\n\n\n

That means that each reference needs to be updated, but since some references are inside the content of the field and not declared as a standard lookup or parent-child relationship, it is much more difficult. <\/p>\n\n\n\n

Odaseva has been a pioneer of addressing issues like the one described in Salesforce\u2019s blog post, and we offer two solutions: <\/p>\n\n\n\n