5.2 Resolving Hardware Error

If, as a result of a hardware error, the Advanced Copy cannot continue, the ETERNUS Disk storage system automatically suspends it.

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

Procedure for checking copy status
If the copy is suspended, then its status is changed to one of the following:
- OPC Error Suspend
- EC Error Suspend
- EC Hardware Suspend
- EC Hardware Suspend (Use REC DISK)
- EC Hardware Suspend (Use REC BUFFER)
- Snap Error Suspend
To check the status of the Advanced Copy processing, use the acopc query, acec query, or acsnap query command.
Procedure for checking error code
Use ETERNUS Web GUI to check error codes:
1. From the Display status menu, click Advanced Copy status display in the status display.
2. At Session status, click the Number of active sessions link for the relevant copy type.
3. Refer to the value in the Error code column of the relevant copy process.

This section explains how to resolve problems.

Table 5.1 Causes and Action in Response to Hardware Error
Advanced Copy Status	Error Code	Cause / Action
OPC Error Suspend	0xB2	[Cause] As the Storage Cluster Continuous Copy sessions on the Primary Storage and Secondary Storage cannot be synchronized, the Advanced Copy could not be continued. [Action] Refer to "3.12.11 When Recovering Storage Cluster Continuous Copy Function".
	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] When the Storage Cluster Continuous Copy function is used, refer to "3.12.10.1 Recovery from Hardware Failure". In cases other than the above, take the following measures. Execute the acopc cancel 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 system command (for example, the UNIX dd command or the Windows format 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).
	Other than 0xBA	[Cause] An error other than 0xBA occurred. For error details, confirm with Fujitsu Technical Support. [Action] When the Storage Cluster Continuous Copy function is used, refer to "3.12.10.1 Recovery from Hardware Failure". In cases other than the above, take the following measures. Execute the acopc cancel command to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. Execute the acpair remove command to remove the copy pair. Execute the acpair add command to add a new copy pair.
EC Error Suspend	0xB2	[Cause] As the Storage Cluster Continuous Copy sessions on the Primary Storage and Secondary Storage cannot be synchronized, the Advanced Copy could not be continued. [Action] Refer to "3.12.11 When Recovering Storage Cluster Continuous Copy Function".
	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] When the Storage Cluster Continuous Copy function is used, refer to "3.12.10.1 Recovery from Hardware Failure". In cases other than the above, take the following measures. Execute the acec cancel 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 system command (for example, the UNIX dd command or the Windows format 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).
	Other than 0xBA	[Cause] An error other than 0xBA occurred. For error details, confirm with Fujitsu Technical Support. [Action] When the Storage Cluster Continuous Copy function is used, refer to "3.12.10.1 Recovery from Hardware Failure". In cases other than the above, take the following measures. Execute the acec cancel command to cancel the copy. If it cannot be cancelled using commands, then use ETERNUS Web GUI. Execute the acpair remove command to remove the copy pair. Execute the acpair add 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. REC is automatically restarted (resumed) by ETERNUS Disk storage system. [In Manual Recovery mode] Remove the cause of the all path halt. Execute the acec suspend command with the -force option to forcibly and temporarily suspend the REC. Execute the acec resume command to resume the REC.
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] Remove the cause of the all path halt. REC is automatically restarted (resumed) by ETERNUS Disk storage system.
EC Hardware Suspend (Use REC BUFFER)	-	[Cause] An all path halt occurred while transfer data was in the saved state in the REC transfer buffer. [Action] Remove the cause of the all path halt. REC is automatically restarted (resumed) by ETERNUS Disk storage system.
Snap Error Suspend	0x1E, 0x2E, 0xBB	[Cause] A capacity shortage occurred in the copy destination volume of SnapOPC+. [Action] Execute the acsnap cancel command to cancel the process for which the error occurred. If this command cannot be used to cancel the process, cancel it from ETERNUS Web GUI. Check the status of the copy destination volume and initialize it. If the copy destination volume is TPV Use Storage Cruiser or ETERNUS Web GUI to check the status of the destination volume and initialize it. For the operation procedure when using Storage Cruiser, refer to "Display Volume" and "Delete Reserved Volume or Forcible Delete/Format Volume" in the ETERNUS SF Web Console Guide. If the copy destination volume is FTV Use Storage Cruiser or ETERNUS Web GUI to check the status of the destination volume and initialize it. For the operation procedure when using Storage Cruiser, refer to "Display FTV" and "Format FTV" in the ETERNUS SF Web Console Guide. If the copy destination volume is SDV Use Storage Cruiser, the acsdv command, or ETERNUS Web GUI to check the status of the destination volume and initialize it. For the operation procedure when using Storage Cruiser, refer to "Display Volume" and "Delete Reserved Volume or Forcible Delete/Format Volume" in the ETERNUS SF Web Console Guide. The operation procedure when using the acsdv command is as follows: Execute the acsdv stat command and check the status of the SDV. Execute the acsdv init command and initialize the SDV. Recreate partitions (slices) in the copy destination volume. The following factors may have caused a capacity shortage of the physical space in the copy destination volume of SnapOPC+: The estimate of the required physical space for the copy destination volume is not adequate. Although the estimate of the required physical space for the copy destination volume is adequate, because large amounts of updates have been performed in the copy destination volume in which SnapOPC+ session does not exist, the physical space of the copy destination volume is being wasted. When corresponding to the above "a", re-estimate the physical space required for the copy destination volume and consider the disk expansion. If TPV is used as the copy destination volume Use Storage Cruiser or ETERNUS Web GUI to check the status of the Thin Provisioning Pool and expand the capacity of the Thin Provisioning Pool. For the operation procedure when using Storage Cruiser, refer to "Display Thin Provisioning Pool" and "Expand Capacity of/Format/Change Threshold Value of/Delete Thin Provisioning Pool" in the ETERNUS SF Web Console Guide. If FTV is used as the copy destination volume Use Storage Cruiser or ETERNUS Web GUI to check the status of the Tier pool and expand the sub-pool capacity of the Tier pool. For the operation procedure when using Storage Cruiser, refer to "Display Tier Pool" and "Expand Capacity of Sub-Pool in Tier Pool" in the ETERNUS SF Web Console Guide. If SDV is used as the copy destination volume Use the acsdv poolstat command or ETERNUS Web GUI to check the status of the SDP and expand the SDP capacity. Creating an exclusive volume named Snap Data Pool Volume (SDPV) enables the SDP and the created SDPV is automatically incorporated in the SDP. Creating an SDPV of the physical capacity that is assigned to a copy destination volume expands the SDP capacity. The operation procedure when using the acsdv poolstat command is as follows: Execute the acsdv poolstat command and check the status of the SDP. Create the SDPV with ETERNUS Web GUI.