Accidental Deletion
33% of data loss in US occurs due to accidental deletion
Incorrect Overwriting
27% of data loss occurs due to overwriting of correct information with incorrect information
User Errors
70% of data loss can be attributed to user errors
Featured Webinar
7 Steps to Recovering Lost Data Using Salesforce Weekly Export
Wednesday, January 23, 2019 | 1 PM ET
Register Now
Back to the blog

With greater focus on data security, compliance, and privacy, today’s enterprises bear higher data protection liability and business risk than ever before. User-inflicted data loss can happen, so it is important to have a disaster recovery plan. As you construct your plan, you will need to define your recovery point objective (RPO) and recovery time objective (RTO).

Recovery Point Objective: The RPO is the amount of data a company can afford to lose before it begins to impact business operations. Therefore, the RPO is an indicator of how often a company should back up their data.

Recovery Time Objective: The RTO is the timeframe by which both applications and systems must be restored after data loss or corruption has occurred. The goal here is for companies to be able to calculate how fast they need to recover, by preparing in advance.

What the recovery time and recovery point end up being are deeply influenced by backup frequency, backup retention, your ability to compare current and past data, and to restore just the data that has been impacted. RTO and RPO are two parameters that help minimize the risks associated with user-inflicted data loss. 

OwnBackup-Salesforce-RTO-RPO-definition

Define Your Recovery Point Objective (RPO): 

1. Figure out how often critical data changes throughout your organization.
For many industries, including healthcare, manufacturing, and financial services companies, losing data is not an option. Consumers trust their personal data to these organizations, therefore, not having records available and up-to-date is unacceptable. If the Salesforce data is constantly changing, the frequency of Salesforce backups should match. Backing up often as every hour, for certain objects, may be warranted. It is important to prioritize protection of the data without which your business simply cannot function.

2. Decide how much data you are willing to lose.
When setting your RPO, a company should factor in how much data they are willing to lose. If, for example, your Salesforce backups are set at one per day, then the RPO of this backup solution is equivalent to one day. Therefore, if a data loss were to happen, you could roll back to the last backup representing a loss of up to one day of data. Determining the amount of data you can lose before your company begins to suffer is a crucial facet of the disaster recovery planning process.

3. Identify the required frequency of your backups.
RPO is normally calculated by analyzing the time that occurs in between data backups in relation to the potential data that could end up being lost should a data loss occur. If your backups are running on a weekly basis, for example the Salesforce Weekly Export, your company will potentially lose a week of data. Furthermore, recovering the data using Weekly Export files may be a time-consuming challenge. Therefore, it is important to establish the amount of optimal time that your business can be without certain data before operations are hit with a data loss.

Define Your Recovery Time Objective (RTO)

1. Decide on the amount of downtime your business could absorb after a data loss.
Losing data is one thing, but unscheduled downtime can send your company into chaos. With customers being unable to access your systems and employees sitting around with nothing to do, a strict limit on the amount of time it should take to recover your systems after a data loss or corruption is a necessity.

2. Estimate the cost of a data loss or corruption.
The cost of a data loss or corruption is dependent not only on the value of your data, but also on the impact of the entire company. Increased labor costs, data recovery fees, reputational damage, revenue impact, compliance fines, and a loss in productivity, all contribute to the cost of data loss and corruption.

OwnBackup-Salesforce-Cost-Data-Loss
3. OwnBackup experts say to test your disaster recovery strategy monthly to find out how long it will actually take to recover lost data.
When important Salesforce records are lost, your business will spend time and resources recreating or recovering the lost data. Depending on your recovery plan, you may not be able to locate and restore all of the lost data. The RTO metric is determined by calculating how quickly a given business needs to recover data before the company begins to suffer. This is an essential a step in establishing an appropriate disaster recovery plan.

Maintaining and testing your disaster recovery plan is critical. When accidental data loss occurs, day-to-day operations can grind to a halt. Your organization needs to be able to recover as quickly as possible to continue providing services to its clients and users.

Partnering with a comprehensive backup and recovery solution vendor, such as OwnBackup, can help you manage your RTO and RPO to effectively minimize downtime and protect your data when an user-inflicted data loss or corruption occurs.

Is your Salesforce data at high risk of data loss or corruption? Watch the OwnBackup Data Loss Risk Assessment Webinar to learn your company’s Salesforce data loss risk score.