Mirroring isn't backup

Mirroring isn't backup

Although data mirroring, especially remote mirroring, is an important tool in business continuity and disaster recovery, it is not a substitute for conventional backups. While the point has been frequently discussed (see for example the overview section of the Oracle/EMC white paper "No Data Loss Standby Database," which is available at

    Requires Free Membership to View

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.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 SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

www.emc.com) it isn't always appreciated by managers, users and others.

In this context mirroring refers to making a second complete copy of the data, sometimes as the data is being written ("synchronized mirroring") and often at a remote site ("remote mirroring"). In the event of a disaster or a major failure the enterprise can switch to the synchronized data and continue operating while the fault is being repaired.

Mirroring is an important tool for business continuity since the second copy of the data is available in a matter of seconds or minutes. However it offers no protection against several important causes of data loss, such as accidental deletion or virus infection. Anything that happens to the primary data happens to the secondary data.

While a backup copy's image isn't as up to date as a mirrored copy, that lag makes it possible to recognize system corruption before it affects the backup. In the worst case, the enterprise may have to go to an earlier backup to get rid of the problem.


Rick Cook has been writing about mass storage since the days when the term meant an 80K floppy disk. The computers he learned on used ferrite cores and magnetic drums. For the last twenty years he has been a freelance writer specializing in storage and other computer issues.


This was first published in March 2002

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.