Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Troubleshooting TrueCopy

When issues occur with TrueCopy, there are a number of different troubleshooting options you can try.

General troubleshooting

The following table provides a list of general error conditions and provides recommended action for each condition.

Error

Corrective action

The Device Manager - Storage Navigator computer or management client hangs, or TrueCopy operations do not function properly.

  • Make sure that the problem is not being caused by the computer or Ethernet hardware or software, and restart the computer. Restarting the Device Manager - Storage Navigator computer or management client does not affect storage system operations.
  • Make sure that all TrueCopy requirements and restrictions are met (for example, same LU type).
  • Make sure that the primary and secondary systems and data paths are powered on and fully operational (NVS, cache).
  • Check all input values and parameters to make sure that you entered the correct information about the Device Manager - Storage Navigator computer (for example, remote storage system S/N and ID, path parameters, P-VOL and S-VOL IDs).

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

Contact customer support.

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

Make sure that the correct CU is selected.

A TrueCopy error message is displayed on the Device Manager - Storage Navigator computer or management client.

Resolve the error, and then try the TrueCopy operation again.

The remote system or secondary storage system path status is not normal.

Check the path status (View Remote Connection Properties window of HDvM - SN, or the raidcom get rcu command of CCI ), 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, call service personnel, 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 pair's status.

    - If status 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. Retry the operation when the system has a lighter workload.

  • A communication error may have occurred between the Device Manager - Storage Navigator computer or management client and SVP. See the System Administrator Guide for your storage system for information and instructions.

There is a pinned track on a TrueCopy volume.

See for more information.

Monitoring data is not updated though the Monitoring Switch option is set to Enable.

Because the time setting of SVP is changed, the monitoring data might not be updated. Disable Monitoring Switch, and then enable again. For more information about Monitoring Switch, see the Performance Guide of your storage system.
A pair cannot be created or resynchronized. Check if the controller board is blocked on the primary storage system. Restore the blocked controller board, and then retry the operation.

Remote path status problems

Problems that you might encounter with remote path status are displayed by Device Manager - Storage Navigator. By understanding the displayed status, you can take the appropriate corrective action.

The following table provides a list of remote path status problems.

Path status

Description

Corrective action

Normal

This remote path has been successfully established and can be used for TrueCopy copy activities.

None required.

Initialization Failed

The link initialization procedure to the remote storage system failed because the physical path connection was missing between the local and remote storage system or between the local storage system and the switch.

  • Make sure that the local and remote storage systems or the local storage system and the switch are physically and correctly connected.
  • Make sure that you entered the correct remote storage system S/N, model name, and local and remote storage system port numbers.
  • Make sure that topologies (Fabric, FC-AL, Point-to-point) for the local and remote storage system ports are configured correctly.

Communication Time Out

Communication between the local and remote storage systems timed out.

  • Make sure the remote storage system is powered on and that NVS and cache are fully functional.
  • Make sure that network relay devices are properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Port Rejected

The local or remote storage system rejected the logical path link control function because all logical path resources in the local or remote storage system are used for other connections.

  • Delete all remote paths not in use in the Remove Remote Paths wizard of HDvM - SN, or by the raidcom delete rcu_path command of CCI.
  • (VSP 5000 series) Make sure that all local and remote storage system ports are properly configured as Bidirectional ports. If necessary, change to the correct port attribute.
  • Remove all remote storage systems currently not in use in the Remove Remote Connection window of HDvM - SN, or by the raidcom delete rcu command of CCI.

Serial Number Mismatch

The primary storage system's S/N does not match the specified S/N.

  • Make sure that you entered the correct remote storage system S/N and model name, and local and remote storage system port numbers.
  • Make sure that topologies (Fabric, FC-AL, Point-to-point) for the local and remote storage system ports are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Invalid Port

The specified local storage system port is in the following status:

  • Not mounted.

  • (VSP 5000 series) The port attribute is not Bidirectional.
  • A remote path is already added.
  • (VSP 5000 series) Make sure the correct port on the local storage system is installed or set to the initiator attribute.
  • Make sure that no two paths between local and remote storage system ports have the same settings.
  • Make sure that you entered the correct remote storage system S/N and model name, and local and remote storage system port numbers.
  • Make sure that topologies (Fabric, FC-AL, Point-to-point) for the local and remote storage system ports are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

Pair-Port Number Mismatch

The specified port in the remote storage system is physically disconnected from the local storage system.

  • Make sure that you specified the correct remote storage system port number. Correct the port number if necessary.
  • Make sure that the cables between the local and remote storage system ports and between the remote storage system and the switch are connected correctly.
  • Make sure that the topology settings (Fabric, FC-AL, point-to-point) of the local and remote storage system ports are correct.

Pair-Port Type Mismatch (VSP 5000 series)

The specified remote storage system port is not configured as a Bidirectional port.

Make sure that the remote storage system port is configured as a Bidirectional port.

Communication Failed

The local storage system connected to the remote storage system successfully, but logical communication timeout occurred.

  • Make sure that the remote storage system port and the relay equipment are configured correctly.
  • Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.

In Progress

Remote paths are being created or deleted.

(VSP 5000 series) The port attribute is being changed.

Wait until processing is completed.

Path Blockade

Blockaded due to continual path or link failure.

See the corrective actions for the other path blockade issues.

The local storage system port does not work.

Repair the port on the local storage system, and then restore the path if this problem occurs again after the repair.*

The remote storage system port does not work.

Repair the port on the remote storage system, and then restore the path if this problem occurs again after the repair.*

The path relay equipment does not work.

Repair the path relay equipment, and then restore the remote path if this problem occurs again after the repair.*

The connection cable is physically broken.

Replace the broken cable, and then restore the remote path if this problem occurs again after the replacement.*

Program Error

A program error is detected.

Restore the remote path.*

* To restore a remote path, it might be necessary to delete and then add the path again.

To delete the remote system or path, see Deleting remote connections or Deleting remote paths. To re-register, see Adding remote connections. If you cannot restore the path after performing these operations, contact customer support.

Split pair problems

Problems that you might encounter with split pairs are displayed by Device Manager - Storage Navigator. By understanding the displayed pair status, you can take the appropriate corrective action.

The following table provides a list of split pair problem types.

Pair status/split type

Applies to

Description

Corrective action

PSUE/by RCU)

P-VOL

The primary system detected an error condition at the secondary system, which caused the primary system to split the pair. The S-VOL split type is S-VOL Failure.

Clear the error condition at the secondary system or S-VOL, and then resynchronize the pair from the primary system in the Resync Pairs window of HDvM - SN, or by the pairresync command of CCI.

If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions from S-VOL, re-create the pair.

PSUE/Secondary Volume Failure

P-VOL

The primary system detected an error during communication with the secondary system, or detected an I/O error during update copy. In this case, the split type for the S-VOL is usually S-VOL Failure.

Check the path status in the Remote Connections window of HDvM - SN, or by the raidcom get rcu command of CCI. If errors occurred on the path, clear the error conditions.

  • Clear any error conditions at the secondary system or S-VOL, and then resynchronize the pair from the primary system.
  • If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions, recreate the pair.

PSUE/MCU IMPL

P-VOL, S-VOL

The primary system could not find valid control information in its nonvolatile memory during the IMPL procedure. This error occurs only if the system is without power for more than 48 hours (for example, power failure or fully discharged batteries).

Resynchronize the pair from the primary system. An entire initial copy operation will be performed in response to the pairresync request.

PSUE/Initial Copy Failed

P-VOL, S-VOL

The primary system split this pair during the initial copy operation. The data on the S-VOL is not identical to the data on the P-VOL.

Release the pair from the primary system. Clear all error conditions on the primary system, P-VOL, secondary system, and S-VOL. Resume the initial copy operation.

Service information messages (SIMs)

The storage system generates a service information message (SIM) to notify users of a possible service requirement. The SVP reports all SIMs related to TrueCopy operations.

SIMs are classified according to the following severities: service, moderate, serious, or acute.

All SIMs are recorded on the SVP or storage system and displayed in the Alert tab of the Device Manager - Storage Navigator Storage System window.

For more information, see the System Administrator Guide.

During TrueCopy operations, the primary and secondary system generate a service SIM when P-VOL or S-VOL pair status changes for any reason, including normal status transitions (for example, COPY to PAIR).

  • SIMs generated by the primary system include the P-VOL device ID (byte 13).
  • SIMs generated by the secondary system include the S-VOL device ID (byte 13).

If SNMP is installed and operational on the storage system, each SIM results in an SNMP trap being sent to the appropriate hosts.

For further information about SNMP operations and SIMs, see the System Administrator Guide, Hitachi Alert Notification Guide, SIM Reference Guide, or contact customer support.