C.2 Resolving Hardware Error

If, as a result of a hardware error, the advanced copy cannot continue, the ETERNUS disk storage systems will automatically suspend it.

If a problem occurs, check the copy status and error code, and take action.

Procedure for checking copy status
Use either A.7.2 acopc query (OPC/QuickOPC copy status display command) or A.8.2 acec query (Synchronous high-speed copy status display command).
If the copy is suspended, then its status will be changed to one of the following:
- OPC Error Suspend
- EC Error Suspend
- EC Hardware Suspend
- EC Hardware Suspend (Use REC DISK) [Excluding Linux 5 for Intel Itanium]
- Snap Error Suspend [Excluding Linux 5 for Intel Itanium]
Procedure for checking error code
Use ETERNUS Web GUI to check error codes:
1. In the ETERNUS Web GUI [Status display] menu, click [Advanced copy status display].
2. In "Session status", click the "Number of active sessions" link for the relevant copy type.
3. Refer to the value of the "Error Code" column for the relevant copy process.

This section explains how to resolve problems.

Table C.1 Causes and Action in response to Hardware Error
Advanced copy status	Error code	Cause / Action
OPC Error Suspend	0xBA	[Cause] QuickOPC has not finished physical copy, and a bad sector occurred in the logical volume of the copy source during tracking processing. [Action] Use A.7.3 acopc cancel (OPC/QuickOPC copy stop command) to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. The bad sector area is recovered by overwriting it. Select an appropriate recovery method from the methods below, according to the usage status of the copy source volume. Recovery method 1 If the area can be recovered from the parent software (for example, the file system or DBMS), then recover it. Recovery method 2 Use a dedicated tool (for example, UNIX dd command) to perform write in the case of an unused area. For example, if the bad sector area has not yet been used, or if it is a temporary area. Recovery method 3 Copy in the reverse direction, and recover data from the logical volume of the copy destination (it is also possible to perform recovery from the copy source volume of the copy process where the bad sector occurred).
OPC Error Suspend	Other than 0xBA	[Cause] An error other than 0xBA occurred. For error details, confirm with a Fujitsu SE. [Action] Use A.7.3 acopc cancel (OPC/QuickOPC copy stop command) to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. Use A.6.6 acpair remove (Copy pair deletion command) to remove the copy pair. Use A.6.5 acpair add (Copy pair addition command) to add a new copy pair.
EC Error Suspend	0xBA	[Cause] EC/REC is in suspend status (copy establishment status) and a bad sector has occurred in the logical volume of the copy source. [Action] Use A.8.7 acec cancel (Synchronous high-speed copy stop command) to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. The bad sector area is recovered by overwriting it. Select an appropriate recovery method from the methods below, according to the usage status of the copy source volume. Recovery method 1 If the area can be recovered from the parent software (for example, the file system or DBMS), then recover it. Recovery method 2 Use a dedicated tool (for example, UNIX dd command) to perform write in the case of an unused area. For example, if the bad sector area has not yet been used, or if it is a temporary area. Recovery method 3 Copy in the reverse direction, and recover data from the logical volume of the copy destination (it is also possible to perform recovery from the copy source volume of the copy process where the bad sector occurred).
EC Error Suspend	Other than 0xBA	[Cause] An error other than 0xBA occurred. For error details, confirm with a Fujitsu SE. [Action] Use A.8.7 acec cancel (Synchronous high-speed copy stop command) to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. Use A.6.6 acpair remove (Copy pair deletion command) to remove the copy pair. Use A.6.5 acpair add (Copy pair addition command) to add a new copy pair.
EC Hardware Suspend	---	[Cause] An all path halt occurred. [Action] The REC resume procedure varies according to the REC Recovery mode. [In Automatic Recovery mode] Remove the cause of the all path halt. The ETERNUS disk storage systems automatically resume REC. [In Manual Recovery mode] Remove the cause of the all path halt. Forcibly and temporarily suspend the REC by specifying the "-force" option for A.8.3 acec suspend (Synchronous high-speed copy temporary suspension command). Resume the REC using A.8.4 acec resume (Synchronous high-speed copy restart command)
EC Hardware Suspend (Use REC DISK)	---	[Cause] An all path halt occurred while transfer data was in the saved state in the REC Disk buffer. [Action] The method for REC restart (resume) depends on the REC recovery mode. [For Automatic Recovery mode] Remove the cause of the all path halt. REC is automatically restarted (resumed) by the ETERNUS disk storage system. [For Manual Recovery mode] Remove the cause of the all path halt. Use "A.8.3 acec suspend (Synchronous high-speed copy temporary suspension command)" with the -force options specified to forcibly suspend REC. Use "A.8.4 acec resume (Synchronous high-speed copy restart command)" to restart (resume) REC.
Snap Error Suspend	0xBB	[Cause] A capacity shortage occurred for a Snap Data Volume or a Snap Data Pool. [Action 1 (Snap Data Volume capacity shortage recovery method)] Use "A.7.6 acsnap cancel (SnapOPC+ copy stop command) [Excluding Linux 5 for Intel Itanium]" to cancel the process for which the error occurred. If this command cannot be used to cancel the process, cancel it from the ETERNUS Web GUI. The following are possible causes of a Snap Data Volume capacity shortage: The estimate for the physical capacity of the Snap Data Volume is not suitable. The estimate for the physical capacity of the Snap Data Volume is suitable, but a large number of updates were performed for the Snap Data Volume at a time when SnapOPC+Session did not exist. This caused excessive consumption of the Snap Data Volume physical capacity. Use "A.9.5 acsdv stat (Snap Data Volume status display command) [Excluding Linux 5 for Intel Itanium]" to check the Snap Data Volume usage state. In the case of a, above, re-estimate the Snap Data Volume physical capacity and create the Snap Data Volume again. In the case of b. above, use the ETERNUS Web GUI or "A.9.4 acsdv init (Snap Data Volume initialization command) [Excluding Linux 5 for Intel Itanium]" to initialize the Snap Data Volume. Note that, after a Snap Data Volume is re-created and initialized, partitions (slices) must be created again. [Action 2 (Snap Data Pool capacity shortage recovery method)] Use "A.7.6 acsnap cancel (SnapOPC+ copy stop command) [Excluding Linux 5 for Intel Itanium]" to cancel the process for which the error occurred. If this command cannot be used to cancel the process, cancel it from the ETERNUS Web GUI. The following are possible causes of a Snap Data Pool capacity shortage: The estimate for the capacity of the Snap Data Pool is not suitable. The estimate for the capacity of the Snap Data Pool is suitable, but large numbers of updates were performed for the Snap Data Volume at a time when SnapOPC+Session did not exist. This caused excessive consumption of the Snap Data Pool capacity. Use "A.9.6 acsdv poolstat (Snap Data Pool status display command) [Excluding Linux 5 for Intel Itanium]" to check the Snap Data Pool usage state. In the case of a. above, re-estimate the Snap Data Pool capacity and increase the capacity, and then create the Snap Data Volume again. In the case of b. above, use the ETERNUS Web GUI or "A.9.4 acsdv init (Snap Data Volume initialization command) [Excluding Linux 5 for Intel Itanium]" to initialize the Snap Data Volume. Note that, after a Snap Data Volume is re-created and initialized, partitions (slices) must be created again.