How does data deduplication affect disaster recovery (DR)?

How does data deduplication affect disaster recovery (DR)?

How does data deduplication affect disaster recovery (DR)?

    Requires Free Membership to View

    Login

    When you register for SearchDisasterRecovery.com, you’ll also receive targeted emails from my team of award-winning editorial writers. As you know, an interruption can threaten your organization at any time – and it’s our goal to ensure you’re armed with the right tips and information to help you ensure a swift recovery.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchDisasterRecovery.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDisasterRecovery.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

From my perspective I think data deduplication affects disaster recovery (DR) in two ways:

1) Helps speed up the data recovery process.
2) Helps ensure that you have the right data to move forward with. There's hardly anything that can get in the way of doing business than restoring the wrong dataset after a problem and then realize you have to restore the data all over again.

What is data deduplication?

Data deduplication is a data backup process that eliminates redundant data, therefore reducing the amount of data that needs to be backed up. And using data deduplication has many benefits. Less data to store often leads to lower storage costs, and efficient use of disk space often allows for longer disk retention periods.

What to learn more about data deduplication? Check out some of our tips and tutorials:

This was first published in November 2009

Back to top