File System-Based Data Protection Approach

Authors: Jaechun No

Abstract:

As data to be stored in storage subsystems tremendously increases, data protection techniques have become more important than ever, to provide data availability and reliability. In this paper, we present the file system-based data protection (WOWSnap) that has been implemented using WORM (Write-Once-Read-Many) scheme. In the WOWSnap, once WORM files have been created, only the privileged read requests to them are allowed to protect data against any intentional/accidental intrusions. Furthermore, all WORM files are related to their protection cycle that is a time period during which WORM files should securely be protected. Once their protection cycle is expired, the WORM files are automatically moved to the general-purpose data section without any user interference. This prevents the WORM data section from being consumed by unnecessary files. We evaluated the performance of WOWSnap on Linux cluster.

Keywords: Data protection, Protection cycle, WORM

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1083655

References:

[1] A. Buldas, P. Laud, H. Lipmaa and J. Villemson, "Time-Stamping with Binary Link-ing Schemes," In Advances on Cryptology (CRYPTO-98), LNCS 1462, 1998, pp.486-501.
[2] S. L. Garfinkel and J.S. Love, "A File System for Write-Once Media," MIT Technical report, 1986.
[3] A. Apvrille and J. Hughes, "A Time Stamped Virtual WORM System," Securite des Communications sur Internet (SECI02), 2002.
[4] A. Sweeney, D. Doucette, W. Hu, C. Anderson, M. Nishimoto and G. Peck, "Scalability in the XFS File system," USENIX 1996 Annual Technical Conference, 1996.
[5] J. Mostek, W. Earl, and D. Koren, "Porting the SGI XFS File system," Linux 6th Linux Kongress: The Linux Storage Management Workshop (LSMW), 1999.
[6] Z.N.J. Peterson and R.C. Burns, "Ext3cow: The design, implementation, and analysis of metadata for a time shifting file system," Technical report, Department of Computer Science, The Johns Hopkins University, 2003.
[7] Z.N.J. Peterson and R.C. Burns, "Ext3cow: A Time-Shifting File System for Regulatory Compliance," ACM Transactions on Storage, vol. 1, no. 2, 2005, pp.190-212.
[8] S. Shim, W. Lee and C. Park, "An Efficient Snapshot Technique for Ext3 File System in Linux 2.6," Technical report, Pohang University of Science and Technology, 2005.
[9] American Megatrends. Inc., "AMI Snapshot Technology," Technical report, 2005.
[10] B. Mary and D. Peterson, "Integrating Network Appliance Snapshot and SnapRestore with Veritas Netbackup in an Oracle Backup Environment," Technical report 3394, Network Appliance, 2006.
[11] H. Patterson, S. Manley, M. Federwisch, D. Hitz, S. Kleiman and S. Owara, "SnapMirror: File System based Asynchronous Mirroring for Disaster Recovery," Proc. of the FAST-02 Conference on File and Storage Technologies, 2002.
[12] J. Piernas, T. Cortes and J. Garcia, "DualFS: A New Journaling File System without Meta-Data Duplication," Proc. of the 2002 International Conference on Supercomputing, 2002.
[13] D. Santry, M. Feeley, N. Hutchinson and A. Veitch, "Elephant: The File System that Never Forgets," Proc. of IEEE Hot Topics in Operating Systems, 1999.
[14] D. Santry, M. Feeley, N. Hutchinson, R. Veitch, R. Carton and J. Ofir, "Deciding when to forget in the Elephant file system," Proc. of 17th ACM Symposium on Operating Systems Principles (SOSP-99), 34(5),1999, pp.110-123.
[15] S. Quinlan, "A Cached WORM File System," Software Practice and Experience, Vol. 21, No. 12, 1991, pp.1289-1299.