|
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. 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.
- 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 Pinned track recovery
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. |
The pair status remains unchanged as follows when creating a pair
or resynchronizing a pair:
- 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.
- 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 remains on the volume after trying to delete the
pair, even if the pair is not created using the volume. The pair
information remaining means that the volume cannot be used as a
volume of a different pair.
|
If the pair cannot be deleted or if the pair remains when the pair status
is verified after the pair deletion, perform the following
procedure:
- 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.
- 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.
|