Before You Begin
Ensure that the following conditions are met:
The Geographic Edition software is installed on the primary and secondary clusters.
You have reviewed the information in Planning Remote Replication Using Oracle Solaris ZFS Snapshot.
You have performed the prerequisites mentioned in Prerequisites for Configuring Remote Replication Using Oracle Solaris ZFS Snapshot
The local cluster is a member of a partnership.
The protection group and the replication component already exist on the local cluster.
For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
# chmod A+user:username:rwx:allow /var/cluster/geo
The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Solaris ZFS snapshot software.
The protection group configuration output of geopg show will display which file is associated with the protection group.
For more information about configuration files, see configuration_file Property in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.
For the parameters that you do not want to modify, specify the same values that exist in the replication component.
Otherwise, make a copy of the /opt/ORCLscgrepzfssnap/etc/zfs_snap_geo_config replication configuration file to a different location, such as /var/tmp/geo/zfs_snapshot/zfs_snap_geo_config.
# cp /opt/ORCLscgrepzfssnap/etc/zfs_snap_geo_config /var/tmp/geo/zfs_snapshot
Fill in the existing values for unchanged parameters and new values for the parameters that require to be modified.
For example, if you want to modify the REPLICATION_INTERVAL to 180 and NUM_OF_SNAPSHOTS_TO_STORE to 1 for an existing replication component repcom1 in a protection group pg1 configured between clusters paris and newyork. If the replication configuration file to use for repcom1 is /var/tmp/geo/zfs_snapshot/zfs_snap_geo_config, then set these new values in that file, keeping all other parameters unchanged.
PS=paris-newyork PG=pg1 REPCOMP=repcom1 REPRS=repcom1-repstatus-rs REPRG=pg1-repstatus-rg DESC="Protect app1-rg1 using ZFS snapshot replication" APPRG=app1-rg1 CONFIGFILE=/var/tmp/geo/zfs_snapshot/sbp_conf LOCAL_REP_USER=zfsuser1 REMOTE_REP_USER=zfsuser2 LOCAL_ZPOOL_RS=par-app1-hasp1 REMOTE_ZPOOL_RS=ny-app1-hasp1 LOCAL_LH=paris-lh REMOTE_LH=newyork-lh LOCAL_DATASET=srcpool1/app1-ds1 REMOTE_DATASET=targpool1/app1-ds1-copy REPLICATION_INTERVAL=180 NUM_OF_SNAPSHOTS_TO_STORE=1 REPLICATION_STREAM_PACKAGE=false SEND_PROPERTIES=true INTERMEDIARY_SNAPSHOTS=false RECURSIVE=true MODIFY_PASSPHRASE=false
Use the zfs_snap_geo_register script with the modified configuration file.
# /opt/ORCLscgrepzfssnap/util/zfs_snap_geo_register -f /var/tmp/geo/zfs_snapshot/zfs_snap_geo_config
The command modifies the replication component in a protection group on the local cluster. If the partner cluster contains a protection group with the same name, the command also propagates the new configuration to the partner cluster.
You can perform this procedure from either cluster. However, if you are using a saved configuration file that was used to create replication component from the primary cluster, perform this procedure on the primary cluster since the values in the file will be appropriate from the primary cluster.
For example, you can type the following command on one node of paris cluster and one node of newyork cluster:
# geopg show pg1 ..... SBP Script-based plug-in configurations: repcom1 ..... repcom1_create_config_args : ......,REPLICATION_INTERVAL=180,NUM_OF_SNAPSHOTS_TO_STORE=1,......
You can also check the relevant extension properties of the replication agent resource associated with the replication component to check that the new values have been set correctly. For information about extension properties of replication agent resource type ORCL.ZFSSnapRepAgent, see Geographic Edition Properties for Oracle Solaris ZFS Snapshot.
For example, you can type the following command on one node of paris cluster and one node of newyork cluster to check if the configuration is updated.
# /usr/cluster/bin/clresource show -p REPLICATION_INTERVAL -p NUM_OF_SNAPSHOTS_TO_STORE repcom1-snap-rs === Resources === Resource: repcom1-snap-rs --- Standard and extension properties --- Num_of_snapshots_to_store: 1 Class: extension Description: The number of replication snapshots to keep. Per-node: False Type: int Replication_interval: 180 Class: extension Description: The interval in seconds between ZFS snapshot replication cycles. Per-node: False Type: int