> > 1. What is the primary use case - 'single shot' file-system migration > (customer is upgrading box A to Box B and wants to move data once), or > recurrent (policy-based) migration typically found in multi-tier > set-up (so that data migrates down on-line/near-line/off-line path as, > for example, it gets colder)?
single-shot. The latter scenario you describe is more of an HSM-type service. See the ADM project: http://www.opensolaris.org/os/project/adm > > 2. As described, DMM appears to assume symmetric approach with manager > active at both source and target. Asymmetric one, > with target mounting source over NFS/CIFS (and no DMM at source), extends > the reach to frequent use case of migrating data between heterogeneous > sources. DMM only has a manager active on the target. It pulls from the source, so it would be what you describe as the asymmetric approach. > > 3. Do you anticipate to use NFSv4 features supporting file-system > migration (client-side redirection based on server's 'file system > moved' response) or target activation is expected to be achieved by > other means (e.g. manually)? > Absolutely! We expect that DMM could implement the "heavy lifting" part of NFSv4 Migration. Some connecting the dots required here but we have ensured that they're compatible. Perhaps Spencer can comment further on this one. Mark This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
