General troubleshooting

TrueCopy operations do not function properly.

• Make sure that all TrueCopy requirements and restrictions are met (for example, same LU type).
• Make sure that the primary and secondary systems are powered on and fully operational (NVS, cache).
• Make sure that all values ​​and parameters you have entered are correct , and then run the raidcom get rcu, raidcom get ldev, or pairdisplay command, or verify the contents of the configuration definition file to check the serial number, ID, path parameters, P-VOL ID, S-VOL ID, and so on of the remote storage system.

An initiator channel-enabled LED indicator (on the storage system control panel) is off or flashing.

Contact customer support.

The pairs or paths to the remote storage system are not displaying correctly.

Make sure that the correct CU is selected.

The status of the path to the remote storage system is not normal.

Check the path status by using the raidcom get rcu command, and see Remote path status problems.

Pair status is PSUE.

See Split pair problems.

The paircreate or pairresync operation resulted in a timeout error.

• Hardware failure: If the timeout error was caused by a hardware failure, a SIM is generated. If this occurs, contact customer support, and then retry TrueCopy operations after the problem is fixed.
• Heavy workload: If no SIM was generated, wait 5 or 6 minutes then check the status of the pair to be created or resynchronized..

  If the pair status has changed correctly, the failed operation completed after the timeout message was issued.

  If the pair status did not change as expected, heavy workload might have prevented the operation from being completed. The heavy workload might be caused by one of the following conditions. Solve any of the following problems, and then retry the TrueCopy operations.

  • On the primary storage system, the utilization ratio of the processor in the MP unit containing the P-VOL is 70% or higher.
  • On the primary storage system, the amount of update I/O transferred to the P-VOL is large.
  • On the secondary storage system, the write pending (WP) rate of the MP unit containing the S-VOL is 65% or higher.

There is a pinned track on a TrueCopy volume.

See Pinned track recovery for more information.

• The pair status remains COPY.
• The pair resynchronization rate remains 0%.

• If a hardware failure occurs, a SIM is generated. Contact customer support, and take the following actions after the problem is solved.
  • If you run the paircreate command without specifying the -nocopy option and the failure shown on the Error column occurs while a pair is created between DP-VOLs, delete the pair and then re-create it.
  • In other cases:

    Suspend the pair and then resynchronize it.

• Heavy workload: If no hardware failures occur, the heavy workload might be caused by one of the following conditions. Solve any of the following problems, and then retry the TrueCopy operations.
  • On the primary storage system, the utilization ratio of the processor in the MP unit containing the P-VOL is 70% or higher.
  • On the primary storage system, the amount of update I/O transferred to the P-VOL is large.
  • On the secondary storage system, the write pending (WP) rate of the MP unit containing the S-VOL is 65% or higher.
• If the pair status remains unchanged when no hardware failure occurs (no SIM is generated) and the processing load is low, contact customer support.

The pair information remaining means that the volume cannot be used as a volume of a different pair.

1. Retry the normal pair deletion according to the following conditions:
   • If the pair to be deleted remains on both of the primary and secondary storage systems, perform the normal pair deletion on the primary storage system first.
   • If the pair to be deleted remains on either of the primary and secondary storage systems, perform the normal pair deletion on the storage system on which the pair remains.
2. Verify the pair status.
   • If the pair has been successfully deleted, skip this step.
   • If the normal pair deletion cannot be performed or the pair status remains, perform the forced deletion of the remaining pair. See Forcibly deleting pairs.