2019 The current DR replication type isn't supported on the current type of partnership.

Explanation

The partnership connection type is not supported with the disaster recovery replication type that is configured for the volume group, so replication cannot be established or maintained. This issue can occur in the following scenarios.

  • The partnership was created with a connection type that does not support the selected disaster recovery topology. For example, synchronous disaster recovery requires low latency and is not supported over TCP/IP.
  • The partnership was modified or migrated and no longer supports the current replication type.
The type of disaster recovery replication and supported partnership types are:
  • Asynchronous disaster recovery (2-site-async-dr, async-dr) is supported on all partnership types.
  • Synchronous disaster recovery (sync-dr) is supported on FC and RDMA partnerships; not supported on TCP/IP partnerships.

User response

  1. Identify the configuration.
    • Use lsvolumegroup command to find the volume group’s replication_policy_id.
    • Use lsreplicationpolicy command to check the policy topology.
    • Confirm the current partnership type is supported with the type of disaster recovery replication configured for the volume group.
  2. Remediate by using one of the following options.
    • Reconfigure the partnership to a connection type that is supported by the current disaster recovery replication type.
    • Change the disaster recovery replication type to one that is supported by the existing partnership by creating a compatible replication policy and applying it to the volume group by using chvolumegroup command.
    • After the previous replication policy is no longer in use, delete it by using rmreplicationpolicy command.
  3. Verification.
    • This event is automatically marked as fixed when the volume group uses a partnership type supported with the disaster recovery replication type.