ownbackup logo
Back to the blog

It may seem like a brilliant idea to you and your Salesforce excellence team to set up a do-it-yourself (DIY) backup and recovery strategy. Doing so would ensure your company can keep complete control of its data and prevent data from going through an additional third party. In reality, attempting to implement your own backup and recovery solution could waste weeks to months of your employees’ time as they try to develop, maintain, monitor, troubleshoot, and store all of your backups.

Using standard Salesforce functionality, there are several DIY Salesforce backup options, but all of them have inherent challenges; and none are a complete solution or strategy. These include:

Salesforce backup DIY options

Building a DIY Salesforce backup solution consists of many moving parts and unexpected considerations.

First of all, building a proprietary backup solution has hidden costs, including the cost of:

  • Securing backups efficiently and effectively, using encryption in-transit and at rest.

  • Implementing auto-discover to support custom objects.

  • Keeping up with new API versions, while supporting metadata, attachments, table-data, Chatter, customer objects.

  • Implementing a notification system for when a backup fails or completes with errors.

  • Troubleshooting backup failures and errors.

  • Making sure that the backup is efficient in terms of runtime and API consumption.

  • Maintaining all the related code.

  • Maintaining on-premise storage and backup files outside of your Salesforce database.

And that’s just the backup...what about the recovery?

How will you identify the changes/deletions across your backups? If you have many custom objects and applications and a lot of data, this could be tricky.

Will your restore strategy work with parent-child relationships? It is common for a cascading delete to occur when data is deleted in Salesforce. When a parent object (or account) is deleted, all the children records related to that parent object are also deleted. Given that you cannot set a record’s ID via the Salesforce APIs/tools, and relationships are based on the record ID, restoring relationships can be very complex.

Does your restore strategy meet your recovery time objective and recovery point objective? Typically, organizations will document a recovery point objective (RPO), for example to be able to recover to a point not more than a day ago. With the Weekly Export, your RPO will be up to seven days because you are only backing up weekly. It can take time to prepare records to reinsert into Salesforce. When you are finally back up and running, this is your recovery time objective (RTO), which dictates how often you need to backup and what tools you need to use to recover. If you do decide to implement your own backup and restore tools, you should test it in your sandbox to make sure the process meets your RTO, the time you are willing to be down, and RPO, how much data are you willing to lose.

Does your restore functionality recover lost data at any level of granularity? Can your custom tool support bulk Updates/Inserts? Will you be able to easily extract only the corruption that started and ended last month without overwriting all the unaffected data?

Does you backup strategy help you remain compliant with industry and governmental regulations?

Not having an effective backup and recovery strategy in place could lead to large non-compliance fines. The GDPR, HIPAA, SEC Rule 17a-4, and other regulations have stringent requirements related to what data you save and for how long, including in backups and archives. In some cases, such as HIPAA, you’re required to maintain data for long periods of time in case a data loss should occur. In others, such as GDPR, you are only allowed to keep data for the maximum time deemed necessary for the consented business purpose. Either way, a customizable backup and recovery strategy is important for regulatory compliance.

What about Salesforce development excellence and productivity?

The most useful backup tools include replication and sandbox seeding to help speed development operations. With these tools, developers and admins can:

  • Seed developer and full sandboxes on-demand to speed up development cycles.

  • Set up test environments with relevant, sized-to-fit test data.

  • Test more completely and frequently with an easier process to prepare test environments.

  • Manage demo and training environments.

A basic backup strategy is unlikely to include the above valuable time-saving development and QA capabilities.

Consider the opportunity cost you may incur in attempting to implement a DIY backup and recovery solution.

Think about the time and money your technology team will invest in developing, maintaining, monitoring, troubleshooting and storing all your backups. It may be more prudent to focus your company’s valuable resources on core business, rather than taking on developing a backup and restore tool. Isn’t that why you moved to the cloud in the first place? Don’t compromise your data.

Let OwnBackup protect your Salesforce data from user-inflicted data loss and corruption. For over three years, our expert team has been working with some of the world’s largest organizations to perfect enterprise-scale Salesforce backup and recovery. With OwnBackup, you can schedule full Org backups, including metadata. Recovering your data is just as simple. Visual tools help you find and isolate deleted/corrupted data, restore parent/child relationships, and restore only the corrupted data, leaving everything else intact. On top of that, OwnBackup’s Sandbox Seeding and regulatory compliance support capabilities ensure you have the most comprehensive Salesforce data protection strategy available today.