Hi All, Is there a bandwidth efficient way (downtime is allowed) to reverse the relationship between HOME and CACHE in a single writer AFM relationship?
If it is not immediately obvious why this might be useful, see the following scenario: Fileset A is a GPFS fileset which is acting as CACHE for a single writer HOME on fileset B located on a separate filesystem. The system hosting A fails and all data on fileset A is lost. Admin uses fileset B as a recovery volume and users read and write data to B until the system hosting A is recovered, albeit without data. Admin uses mmafmctl to “failover” AFM relationship to a new fileset on A, all data are copied from B to A over time and users continue to access the data via B. So is there a bandwidth efficient way (downtime is allowed) to reverse the relationship between A and B such that the replication flow is as it was to start with? Cheers, Vic
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
