This looks awesome! A few comments below. - Ryan -- UNIX Administrator http://prefetch.net
On Feb 11, 2008 12:30 PM, Martie Land <[EMAIL PROTECTED]> wrote: > > > Data Migration Manager > > Purpose: > > Purpose of this effort is to provide an open source tool to > facilitate the movement of file systems from one platform to > another over the NFS and CIFS protocols. An important part of > this goal is maintaining read/write access to file system > content over the duration of the migration. > > Sponsoring Community Groups: > > Storage > > Key Partnerships: > > UFS, ZFS, and SAM/QFS discussion groups > > Initial Project Development Team: > > Mark Cruciani - Project team lead > Steven Larson - DMM Infrastructure Lead Design/Developer > David Villineau - DMM Kernel Lead Design/Developer > Matt Bailey - DMM Kernel Developer > Erick Liska - DB and Infrastructure Developer > Roy Lee - GUI Design and Developer > Murali Balusu - Mgr, Functional Verification Testing > Ray Lanza/ Spencer Shepler - DE, Architectural Oversight > Reg Gillmor - DMM Program Manager > Martie Land - Mgr, DMM project > > > Project Description: > > Today, customers choosing to adopt newer storage platforms > based on file systems different from those used in their > existing storage solutions have no easy method of transferring > data from the old to the new systems while retaining access to > these data by applications. A highly reliable, easy-to-use > migration solution which transmits all aspects of user data > will greatly simplify this task and reduce the costs associated > with transition. Will you be supporting iSCSI in addition to NFS and CIFS? > This project will deliver a two pronged approach to data > migration which will ensure data is moved as quickly and > efficiently as possible while maintaining client access to > data throughout the migration process. Will there be controls added to throttle the speed of the replication process? Will the replication tool natively support compression and encryption? Are there synchronous and asynchronous modes of operation? > In active-path migration, client file system requests for > files which have not yet been migrated will be held temporarily > while the Monarch system migrates the data from the source to > the target file system. After the data requested by the file > system operation is retrieved, the client is released and > allowed access to the data. Based on the description above, it sounds like the client will be stopped hile their data is migrated from one location to another. Is this actually the case? > In passive migration, no client file system activity is required. > Instead the Monarch system will proactively "walk" the source > file system, migrating data using heuristics or policy to ensure > that the data of highest importance is moved first to reduce > the probability of a client waiting at a later time. > > Web-based GUI and CLI interfaces will be offered. > > This project will be associated with (and endorsed by) the Storage > Community and cross-posted to the UFS-discuss, SAM/QFS discuss, and > ZFS-discuss . > > > Project Needs: > > OpenSolaris Project Page > > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > > _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
