Oracle^® Solaris Cluster Data Replication Guide for ZFS Snapshots

Configuring Oracle Solaris ZFS Snapshot Replication for ZFS-based Cluster Filesystems in Zone Clusters

To configure ZFS snapshot replication for ZFS-based cluster filesystems in zone clusters, the ZFS snapshot protection groups must run on the global clusters. This is because the zpool for globally mounted filesystems is only available in the global cluster. The ZFS-based cluster filesystem is loopback mounted to the zone cluster nodes and these zone clusters will be in a partnership with protection group of type NONE.

This appendix contains the following sections:

• Configuration Requirements

• Use Case: Configuring Oracle Solaris ZFS Snapshot Replication for ZFS-based Cluster Filesystems in Zone Clusters

Configuration Requirements

1. Partnership between global clusters containing ZFS snapshot replication protection group to manage replication of the filesystem(s) in zpool for globally mounted filesystems.

2. On each global cluster, the ZFS-based cluster filesystem is loopback mounted to zone cluster. A partnership between these zone clusters with protection group of type NONE for managing the application using the ZFS-based cluster filesystem in the zone clusters.

3. Application resource group on the global clusters with HAStoragePlus resource that contains zpool for globally mounted filesystems in its globalzpools property. This resource group is added to ZFS snapshot replication protection group in the global clusters.

4. Application resource group in the zone clusters with HAStoragePlus resource containing loopback mounted filesystem(s) in its filesystemmountpoints property. This resource group has ++ rg_affinity with the resource group (from item 3 above) on its global cluster. The HAStgoragePlus resource in this resource contains global cluster HAStoragePlus resource (from item 3 above) in its resource_dependencies_offline_restart property.

5. On each site a disaster recovery framework site is created that contains the global cluster and the zone cluster in the site.

6. A multigroup is added to each site that contains the global cluster protection group and the zone cluster protection group. The zone cluster protection group has a dependency on the global cluster protection group.

7. To manage start, stop, switchover, and takeover of the configuration, use the geomg command on the multigroup.

The following use case illustrates the procedure for bringing up this configuration.