Code42 vs. Druva fastest recovery

Prioritize Time-to-Recovery Over Backup Speed–Here’s Why

Achieving success in your business is a moving target. It’s important to periodically question your assumptions about how you define success.

Case in point: backup and restore capabilities. It used to be that backup speed was the most important specification for endpoint backup solutions.

A lot has changed since then:

  • Backup intervals have become more frequent, decreasing the amount of incremental data being backed up at any one time. The best solutions back up continuously, reducing the number of incremental file changes even further.
  • Modern backup solutions capture block-level changes, not full files. This reduces backup sizes even further.
  • Backups are now performed in the background. Device, network and storage performance have increased so that incremental backups don’t impact work and are virtually invisible to employees.

At the same time, the importance of time-to-recovery has increased:

  • Unlike backups occurring invisibly in the background, restores by definition stop work from proceeding. Restore time equals user downtime.
  • The impact of lost data is higher. Business is moving faster, and your teams are more dependent on their data than ever. According to Deloitte, 80 percent of a company’s value is now in its information.
  • The longer data is lost, the more the business is exposed to risk. A ransomware attack includes a deadline; GDPR requires full disclosure of breaches within 72 hours.

Given this new reality, time-to-recovery has replaced backup speed as a priority performance measure for backup and recovery solutions. What does this mean for your business?

Know your time-to-restore. Conduct real-life tests of your restore performance under various conditions, including a range of restores from single file to full device restores. Also test cyber threat scenarios; 48 percent of companies in a recent Code42 survey have been breached in some way in the last 18 months.

Identify opportunities to improve. From your testing, identify the biggest opportunities to shorten time-to-recovery. The most valuable changes could be people, process or technology-related, so take a wide view.

Prioritize and act. Once you’ve defined your time-to-recovery improvement options, act immediately on those that are “free.” For example, something as simple as a setting change may offer significant improvements. Prioritize more significant changes, and build a business case if significant change is required.

Time-to-recovery is a key to your business continuity plans. If it’s not a priority for you today, it should be.