18 citations found. Retrieving documents...
PATTERSON, H., MANLEY, S., FEDERWISCH, M., HITZ, D., KLEIMAN, S., AND OWARA, S. Snapmirror: File system based asynchronous mirroring for disaster recovery. In Proc. of the 1st USENIX Conference on File and Storage Technologies (Jan. 2002).

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Metadata Efficiency in Versioning File Systems - Soules, Goodson, Strunk, Ganger (2003)   (9 citations)  (Correct)

.... and roll forward concepts to ensure consistency during transactions with commit and abort [14] Several systems have used copy on write and differencing techniques that are common to versioning systems to decrease the bandwidth required during system backup or distributed version updates [4, 6, 26, 31, 32]. Some of these data differencing techniques [5, 26, 31] could be applied to CVFS to reduce the space utilization of versioned data. 8 Conclusion This paper shows that journal based metadata and multiversion b trees address the space inefficiency of conventional versioning. Integrating them into ....

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies, pages 117--129. USENIX Association, 2002.


Seneca: Remote Mirroring Done Write - Ji, Veitch, Wilkes (2003)   (2 citations)  (Correct)

....the secondary copy as soon as they are received in the secondary host (a special case of the volatile immediate report of section 2. 5) Network Appliance SnapMirror: this product uses asynchronous, write coalescing batched file system updates that are applied atomically at a remote file server [Patterson2002] The WAFL file system is used to keep track of the blocks that have been updated, including which blocks are still in use and worth propagating. The WAFL file system always operates in a no overwrite mode, so it readily supports applying a coordinated set of updates atomically. 3 The Seneca ....

....from the active server to the semi active (once failed) server, and maintained a water mark to indicate which blocks had been copied and which had not. Mime [Chao1992] a shadow writing storage system, avoided synchronous metadata updates using a log and barriers. The SnapMirror paper [Patterson2002] contains some similar observations to ours, but its focus was on execution performance, rather than the details of the protocol or its correctness; long batch lengths tens of minutes to hours, rather than seconds; and the support needed in the WAFL nooverwrite file system for block coalescing, ....

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: file-system-based asynchronous mirroring for disaster recovery. In Proc. FAST (Monterey, CA) pages 117--129 Jan. 2002. USENIX.


StarFish: highly-available block storage - Eran Gabber Jeff (2002)   (1 citation)  (Correct)

....and limited bandwidth, which alleviates the necessity of dedicated communication links to all replicas. 1 Introduction It is well understood that important data need to be protected from catastrophic site failures. High end and midrange storage systems, such as EMC SRDF [4] and NetApp SnapMirror [17], copy data to remote sites both to reduce the amount of data lost in a failure, and to decrease the time required to recover from a catastrophic site failure. Given the plummeting prices of disk drives and of high speed networking infrastructure, we see the possibility of extending the ....

....2 way replication, and uses an all or none assignment of the blocks of a logical volume to SEs, rather than a declustering scheme. StarFish uses a single HE (on a quasi static basis) to manage any particular logical volume, and thereby avoids distributed consensus. Network Appliance SnapMirror [17] generates periodic snapshots of the data on the primary filer, and copies them asynchronously to a backup filer. This process maintains a slightly out of date snapshot on the backup filer. By contrast, StarFish copies all updates on the fly to all replicas. The iSCSI draft protocol [19] is an ....

H. Patterson et al. SnapMirror: File system based asynchronous mirroring for disaster recovery. In Proceedings of the UESNIX Conference on File and Storage Systems, pages 117--129, Jan. 2002.


Metadata Efficiency in a Comprehensive Versioning File.. - Soules, Goodson, Strunk, .. (2002)   (4 citations)  (Correct)

.... systems also use the roll back and roll forward concepts to ensure consistency during transactions [13] Several systems have used copy on write and differencing techniques that are common to versioning systems to decrease the bandwidth required during system backup or distributed version updates [4, 6, 25, 30, 31]. Specifically, some of these data differencing techniques [5, 25, 30] could be applied to CVFS to reduce the space utilization of versioned data. 7 Conclusion This paper shows that journal based metadata and multiversion b trees address the space inefficiency of comprehensive versioning. ....

Hugo Patterson, Stephen Manley, Mike Federwisch, Dave Hitz, Steve Kleiman, and Shane Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies (Monterey, CA, 28--30 January 2002.


Towards a Semantic, Deep Archival File System - Mahalingam, Tang, Xu (2002)   (Correct)

....requires some level of support from the applications. Also, these two systems do not address deep archival capability and availability. venti [4] provides versioning capability through a block level interface. It uses block level hashing to avoid storing redundant copies of block data. SnapMirror [5] provides versioning by taking advantage of meta data stored in the underlying file system. The Elephant file system [6] provides versioning capability and retention policies that can be applied at a file level. However, none of the above techniques provide semantic storage and retrieval ....

Patterson, R.H., et al. SnapMirror: File-System-Based Asynchronous Mirroring for Disaster Recovery. in First USENIX conference on File and Storage Technologies. 2002. Monterey, CA, USA.


Efficient Replica Maintenance for Distributed Storage Systems - Ung-Gon Chun Frank (2006)   (Correct)

No context found.

PATTERSON, H., MANLEY, S., FEDERWISCH, M., HITZ, D., KLEIMAN, S., AND OWARA, S. Snapmirror: File system based asynchronous mirroring for disaster recovery. In Proc. of the 1st USENIX Conference on File and Storage Technologies (Jan. 2002).


VERSIONFS: A Versitile and User-Oriented Versioning File System - Muniswamy-Reddy (2003)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleinman, and S. Owara. SnapMirror: File System Based Asynchronous Mirroring for Disaster Recovery. In Proceedings of the First USENIX Conference on File and Storage Technologies (FAST 2002.


A Framework for Evaluating Storage System Dependability - Kimberly Keeton And (2004)   (Correct)

No context found.

R. H. Patterson et al. SnapMirror: file-system-based asynchronous mirroring for disaster recovery. In Proc. 1st Conf. File and Storage Technologies (FAST), pp. 117--129, Jan. 2002.


A Versatile and User-Oriented Versioning File System - Muniswamy-Reddy, Wright.. (2004)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleinman, and S. Owara. SnapMirror: File System Based Asynchronous Mirroring for Disaster Recovery. In Proceedings of the First USENIX Conference on File and Storage Technologies (FAST 2002.


A Framework for Building Unobtrusive Disk.. - Thereska.. (2003)   (4 citations)  (Correct)

No context found.

Hugo Patterson, Stephen Manley, Mike Federwisch, Dave Hitz, Steve Kleiman, and Shane Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies (Monterey, CA, 28--30 January 2002.


Designing for Disasters - Kimberly Keeton Cipriano (2004)   (2 citations)  (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: file-systembased asynchronous mirroring for disaster recovery. Proc. File and Storage Technologies (FAST), pp. 117--129, Jan. 2002.


Snapshots in a Distributed Persistent Object Storage System - Moh (2003)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: File System Based Asynchronous Mirroring for Disaster Recovery. In CA, USA, January 2002.


Snapshots in a Distributed Persistent Object Storage System - Moh (2003)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: File System Based Asynchronous Mirroring for Disaster Recovery. In CA, USA, January 2002.


Self-* Storage: Brick-based storage with automated.. - Ganger, Strunk, Klosterman (2003)   (Correct)

No context found.

Hugo Patterson, Stephen Manley, Mike Federwisch, Dave Hitz, Steve Kleiman, and Shane Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies (Monterey, CA, 28--30 January


A Framework For Building Unobtrusive Disk.. - Thereska.. (2004)   (4 citations)  (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies, pages 117--129. USENIX Association, 2002.


Ext3cow: The Design, Implementation, and Analysis of Metadata .. - Peterson, Burns (2003)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: File system based asynchronous mirroring for disaster recovery. In Proceedings of the Conference on File and Storage Technologies (FAST), pages 117--129, Jan 2002.


Clotho: Transparent Data Versioning at the Block I/O Level - Flouris, Bilas (2004)   (Correct)

No context found.

R. H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: File-System-Based Asynchronous Mirroring for Disaster Recovery. In Proceedings of FAST '02. USENIX, Jan. 28--30 2002.


Self-* Storage: Brick-based storage with automated.. - Ganger, Strunk, Klosterman (2003)   (Correct)

No context found.

H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman, and S. Owara. SnapMirror: file system based asynchronous mirroring for disaster recovery. Conference on File and Storage Technologies (Monterey, CA, 28--30 January 2002.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC