A campus cluster is also known as a stretch cluster or remote mirror configuration. In a campus cluster, the hosts and storage of a cluster span multiple sites separated by a few miles.
Keep in mind the following best practices when you configure a Storage Foundation campus cluster:
Campus cluster sites are typically connected using a redundant high-capacity network that provides access to storage and private network communication between the cluster nodes. A single DWDM link can be used for both storage and private network communication.
Tag the disks or enclosures that belong to a site with the corresponding VxVM site name. VxVM allocates storage from the correct site when creating or resizing a volume and when changing a volume's layout if the disks in the VxVM disk group that contain the volume are tagged with the site name.
Tag each host with the corresponding VxVM site name. Make sure the read policy of the volumes is set to SITEREAD. This setting ensures that the reads on the volumes are satisfied from the local site's plex.
Turn on the allsites attribute for all volumes that have data required by the application, to make sure they are evenly mirrored. Each site must have at least one mirror of all volumes hosting application data, including the FlashSnap log volume.
Turn on the siteconsistent attribute for the disk groups and the volumes to enable site-aware plex detaches. Snapshot volumes need not be site-consistent.
In the case of a two-site campus cluster, place the third coordinator disk on the third site. You may use iSCSI disk on the third site as an alternative to Dark Fiber connected FC-SAN or a Coordination Point Server (CPS), as a third coordination point.
Make sure that a DCO log version 20 or higher is attached to the volumes to enable Fast Resync operations.
Set the CVM disk detach policy as global or local for all disk groups containing data volumes.
For OCR and voting disk, it is recommended to have the disk group policy as local detach policy.