Versions

Version History

Metadata Version 1

SnapMirror: File System Based Asynchronous Mirroring for Disaster Recovery

user correction - Legacy Corrections

AUTHOR NAME

Hugo Patterson

user correction - Legacy Corrections

AUTHOR NAME

Stephen Manley

user correction - Legacy Corrections

AUTHOR NAME

Mike Federwisch

user correction - Legacy Corrections

AUTHOR NAME

Dave Hitz

user correction - Legacy Corrections

AUTHOR NAME

Steve Kleiman

user correction - Legacy Corrections

AUTHOR NAME

Shane Owara

user correction - Legacy Corrections

ABSTRACT

Computerized data has become critical to the survival of an enterprise. Companies must have a strategy for recovering their data should a disaster such as a fire destroy the primary data center. Current mechanisms offer data managers a stark choice: rely on affordable tape but risk the loss of a full day of data and face many hours or even days to recover, or have the benefits of a fully synchronized on-line remote mirror, but pay steep costs in both write latency and network bandwidth to maintain the mirror. In this paper, we argue that asynchronous mirroring, in which batches of updates are periodically sent to the remote mirror, can let data managers find a balance between these extremes. First, by eliminating the write latency issue, asynchrony greatly reduces the performance cost of a remote mirror. Second, by storing up batches of writes, asynchronous mirroring can avoid sending deleted or overwritten data and thereby reduce network bandwidth requirements. Data managers can tune the update frequency to trade network bandwidth against the potential loss of more data. We present SnapMirror, an asynchronous mirroring technology that leverages file system snapshots to ensure the consistency of the remote mirror and optimize data transfer. We use traces of production filers to show that even updating an asynchronous mirror every 15 minutes can reduce data transferred by 30% to 80%. We find that exploiting file system knowledge of deletions is critical to achieving any reduction for no-overwrite file systems such as WAFL and LFS. Experiments on a running system show that using file system metadata can reduce the time to identify changed blocks from minutes to seconds compared to purely logical approaches. Finally, we show that using SnapMirror to update every 30 minutes...