4451 A highly available thin clone volume could not be created.

Explanation

During HA operation, the synchronization of systems enables the synchronized creation of a thin clone volume on each system. This event is logged when the snapshot required to create a HA thin clone volume is present on the active management system but not on the partner system. The event is logged when the source volume specified has been deleted on both systems.

For HA policy, the thin clone volume is created on the active management system, but the partner system synchronizes the HA thin clone as a standard volume. It is not possible to retrospectively convert the remote standard volume into a thin clone volume. This event has the following effects:
  • High availability of the partition is suspended until the synchronization is complete.
  • The time taken to synchronize as a standard volume depends largely on its capacity and might take significantly longer than synchronizing thin clones.
  • On the partner system, the standard volume uses more pool capacity than a thin clone.
  • Some tasks cannot be performed on a standard volume that can be performed on a thin clone, for example refreshing from a snapshot. This might affect operations if the AMS is switched to the partner system.

User response

You can run the lsvolumegroup command and filtering the results by the specified partition. Then, for each volume group, run the lsvdisk command on both systems, filtering by volume group. Review the output to identify volumes that are of type thin clone on one system but appear as standard volumes (with no value in the volume_type field) on the other system.