Using the primary fileset to make changes to the secondary fileset

  1. Replace the secondary with a new empty secondary where the new target uses NFS/NSD/mapping.
    The administrator must run the mmafmctl changeSecondary with --inband option to point to the new secondary. The new secondary is expected to be empty. If the new target is a mapping, changeSecondary does not split I/Os and queues them as normal requests without parallel data transfer.
  2. Replace any of the following on an existing secondary:
    • Replace the communication protocol (NSD/NFS):
      The administrator must run the mmafmctl changeSecondary with --inband option by using the new target protocol.
      Note: Only the protocol changes and not the secondary path.
    • Enable or disable parallel data transfer PIO by shifting between NFS/NSD and a mapping:
      The administrator must run the mmafmctl changeSecondary with --inband option, by using the new target protocol or mapping.
      Note: Only the protocol changes and not the secondary path.
    • Replace only the IP address or NFS server by using the same communication protocol and secondary path:
      The administrator must run the mmafmctl changeSecondary command with the –target-only option.
      Note: Only the IP or NFS server changes. The IP/NFS server must be on the same secondary cluster and must be of the same architecture as the old NFS server.