Go to main content

Oracle® Solaris Cluster Geographic Edition Remote Replication Guide for Oracle ZFS Storage Appliance

Exit Print View

Updated: June 2017

How to Modify an Oracle ZFS Storage Appliance Remote Replication Component

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name, click the protection group name, in the Data Replication Components section click the remote replication component name, and click Edit. For more information about Oracle Solaris Cluster Manager, see Chapter 13, Using the Oracle Solaris Cluster GUI in Oracle Solaris Cluster System Administration Guide.
  1. Assume the root role or assume a role that is assigned the Geo Management RBAC rights profile.

    For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide.

    Note -  If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, assume the root role on the cluster node and set the correct ACLs.
    # 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 ZFS Storage Appliance software.

  2. The script-based plug-in evaluation rules for the replication component is correct in the file that is already associated with the protection group.

    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 Geographic Edition System Administration Guide.

  3. Update the ZFS appliance configuration file with the changed information for an existing replication component.

    For the parameters that you do not want to modify, specify the same values that exist in the replication component.

    Note -  You must specify existing values for unchanged parameters and new values for the parameters to be modified. Hence, it is recommended to save the configuration file after you create the replication component, so that you can edit required values when you want to modify the replication component.
    1. If you have a saved copy of the configuration file used to create the replication component, use that file.

      Otherwise, make a copy of the /opt/ORCLscgrepzfssa/etc/zfssa_geo_config replication configuration file to a different location, such as /var/tmp/geo/zfssa/zfssa_geo_config.

      # cp /opt/ORCLscgrepzfssa/etc/zfssa_geo_config /var/tmp/geo/zfssa/
    2. Edit this replication configuration file with updates for the existing replication component.

      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 user for connecting to the local and remote Oracle ZFS Storage Appliances for an existing replication component trancos in a protection group zfssa-pg configured in partnership zfssa-partnership. If the replication configuration file to use for trancos is /var/tmp/geo/zfssa/zfssa_geo_config, then set these new values in that file, keeping all other parameters unchanged.

    DESC="ZFS Storage Appliance replication protection group"
  4. On the node of the local partner having the changed replication configuration file, run the zfssa_geo_register script to modify the replication component.

    Use the zfs_snap_geo_register script with the modified configuration file.

    # /opt/ORCLscgrepzfssa/util/zfssa_geo_register -f /var/tmp/geo/zfssa/zfssa_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.

  5. Check that the new parameters reflect in the configuration of the replication component on each partner cluster.

    For example, you can type the following command on one node of paris cluster and one node of newyork cluster:

    # geopg show zfssa-pg
    SBP Script-based plug-in configurations:
    repcom1_create_config_args :