It’s all about recovery.

Jul 2010

It’s all about recovery.


Enterprises and vendors alike often focus so much on data backup that sometimes they forget about the reason that they backup the data. Customer's focus should be on data Recovery not data backup.

All vendor solutions in the marketplace backup customer data but it requires real data stewardship to ensure that the data can be restored when needed. Over our 24-year history, Asigra has developed best practices around data stewardship to ensure data restorability if the customer looses a file, disk, machine or the entire facility.

The data has to be conditioned constantly to ensure restorability. The following factors can cause data corruption:

  1. Disc malfunction
  2. Disc controller malfunction
  3. Bad sectors on the disc
  4. Filesystem corruption

Access to metadata is not sufficient because bad sector on a disc can render metadata unreadable.

Following data integrity and consistency check functionality is embedded in Asigra software to ensure, data restorability:

  1. Ensuring data consistency – this process ensures that all the data components have been collected sequentially by the DS-Client (the data collector at the enterprise customer’s premises) before sending the data to the DS-System.
  2. Ensuring all data has arrived offsite before storage – Asigra’s DS-System (the online data repository) writes all the data being backed up offsite to a temporary location, checks and ensures that all the data has arrived before storing it.
  3. Restore validation – this is an actual restore simulation that conducts an actual data restore to a temporary location to ensure data restorability. Think of it as the data restore dry run to prepare for the actual disaster.
  4. Autonomic healing – this automated process runs on the DS-System in the background, scans the entire storage to ensure data integrity. Since the data at the DS-System is encrypted, the “Autonomic Healing“ process checks links between the data blocks, compares digital signatures between different components for inconsistencies. When corrupted data is uncovered, it is marked as corrupted and a notification is sent to the DS-Client to resend the portion of that data that was marked corrupted. This ensures that the data is always recoverable in case of a disaster.
  5. Backing up the DS-Client database to the DS-System – this ensures that if the DS-Client is lost it can easily be rebuilt with the appropriate backup structure.

When you're shopping for a backup solution, please inquire from your vendor to ensure that the functionality they provide will restore your data, not just during a Disaster Recovery (DR) drill but in the event of an actual disaster (accidently deleted file, damaged hard drive, machine loss or lost site).

Spice IT Email Post

You've got to be kidding

You've got to be kidding me-it's so tarnspaenrtly clear now!

For more information

Get insights about cloud backup and recovery direct to your inbox every month.
Subscribe to our Newsletter
Stay connected to the latest data protection insights – subscribe to our blog.
Subscribe to our blog
Got questions for one of our recovery specialists?
Need Answers to your Questions?
Print this page
Email this page