Hi, We are using a similar type of replication. I assume the site B is the cold site prepared for DR
The storage layer is EMC VMAX and the LUNs are replicated with SRDF. All LUNs ( NSDs ) of the gpfs filesystem are in the same VMAX replication group to ensure consistency. The cluster name, IP addresses , hostnames of the cluster nodes are different on another site - it can be a pre-configured cluster without gpfs filesystems or with another filesystem. Same names and addresses shouldn't be a problem. Additionally to the replicated LUNs/NSDs you need to deliver copy of /var/mmfs/gen/mmsdrfs file from A to B site. There is no need to replicate it in real-time, only after the change of the cluster configuration. To activate site B - present replicated LUNs to the nodes in the DR cluster and run mmimportfs as "mmimportfs fs_name -i copy_of_mmsdrfs" Tested with multiples LUNs and filesystems on various workloads - seems to be working --Alex On Wed, Jan 24, 2018 at 1:33 AM, Harold Morales <[email protected]> wrote: > Thanks for answering. > > Essentially, the idea being explored is to replicate LUNs between > identical storage hardware (HP 3PAR volumesrein) on both sites. There is an > IP connection between storage boxes but not between servers on both sites, > there is a dark fiber connecting both sites. Here they dont want to explore > the idea of a scaled-based. > > > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at spectrumscale.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss > >
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
