Top
ETERNUS SF AdvancedCopy Manager V15.3 Operation Guide
ETERNUS
Chapter 11 Operation Maintenance > 11.3 Troubleshooting: Hardware error during backup > 11.3.2 Troubleshooting
PreviousNext

11.3.2 Troubleshooting

The following figure shows the flow of troubleshooting tasks if a hardware or similar fault occurs.

Figure 11.2 Troubleshooting flow (for faults during backup)

Note

  • Refer to "11.3.1 Overview" for details of the Status column and "fault location".

    If the Status column is "?????", check if the copy processing is in the error suspend status ("failed") or the hardware suspend status ("halt") using ETERNUS Web GUI.
    If the copy processing is in either of these states, take the action indicated in the above troubleshooting flow.
    In other cases, take the action checked in the following points.

    • If device information is unusual:

      Restore the device information.

    • If a device is not accessible:

      Check if the device exists.

    • If there is anything unusual with Managed Server, switches, etc.:

      Contact a Fujitsu system engineer.

  • Use ETERNUS Web GUI to check the copy process error codes. Use the following method to check the error codes:

    • On the [Display status] menu, click [Advanced Copy status display] in the status display.

    • At "Session status", click the "Number of active sessions" link for the relevant copy type.

    • Refer to the value in the "Error code" column of the relevant copy process.

    The following table shows the meanings of the error codes.

    Table 11.8 Meanings of error codes

    Error code

    Meaning

    0xBA

    If a) or b) below applies, a bad sector was created in the transaction volume.

    1. QuickOPC has not yet performed physical copying and tracking is in progress

    2. EC/REC is in the suspend status (replication established status)

      Note:
      If a bad sector is created in a transaction volume when a) or b) applies, the ETERNUS Disk storage system automatically changes the copy processing to the error suspend state. This prevents a restart of QuickOPC or EC/REC resume and prevents the backup volume from being overwritten with invalid transaction volume data.

    Other than 0xBA

    An error other than the above occurred.

    Error code 0xBA is returned only for the following ETERNUS Disk storage system:

    • ETERNUS4000 and ETERNUS8000 (firmware version V11L30-0000 or later)

    For ETERNUS Disk storage system other than the above, the event indicated by error code 0xBA does not occur. (When the above a) or b) apply, the copy status does not change even if a bad sector occurs in the copy source volume.)


11.3.2.1 Hardware error on a transaction volume

When a hardware fault occurs in the transaction volume, perform the repair work according to the following procedures.

Note

  • The backup history information for which a copy failed cannot be used to perform a restoration.

  • If there is no normal (that is, Status is "succeeded") backup history information, restoration is not possible.

  1. If an error occurred during physical copying, cancel the processing in which the error occurred, with one of the following commands:

  2. Execute the execution status display commands (swstbackstat (Backup execution status display command), swstsyncstat (Backup synchronous processing progress display command), swstreststat (Restore execution status display command), swsttrkstat (Tracking status display command) and swsthistdisp (History information display command)) to verify that no other errors have occurred.

  3. Fix the hardware error in the transaction volume.

  4. Execute swstrestore (Restore execution command) to restore the transaction volume.


11.3.2.2 Hardware error on a backup volume

When a hardware fault occurs in backup volume, perform repair work according to the following procedures.

  1. Cancel the processing in which the error occurred, with one of the following commands:

    If the processing cannot be cancelled using one of the above commands, use ETERNUS Web GUI to cancel it.

  2. Execute swstsrsemtch (Resource match command).

  3. Cancel the processing in which the error occurred. At this point, the execution status display commands (swstbackstat (Backup execution status display command), swstreststat (Restore execution status display command) and swsthistdisp (History information display command)) display "succeeded" in the Status column. However, because the copy processing is suspended, ensure that the commands are cancelled. If an error occurred in the synchronous processing (EC), the command has already been cancelled, so no response is required.

  4. Execute the execution status display commands (swstbackstat (Backup execution status display command), swstsyncstat (Backup synchronous processing progress display command), swstreststat (Restore execution status display command), swsttrkstat (Tracking status display command) and swsthistdisp (History information display command)) to verify that no other errors have occurred.

  5. Use swstdevinfoset (Device information setting command) to delete the backup volume in which the error occurred.

  6. Use swstdevinfoset (Device information setting command) to register a new backup volume. If the backup volume in which the error occurred is repaired and reused, execute the option [Collect or reflect the information for a specific device] from the Web Console, and store the information again in the backup volume.

  7. Re-execute the processing in which the error occurred.


11.3.2.3 Troubleshooting if a bad sector occurred in the transaction volume

If a bad sector occurred in the transaction volume, use the following procedure to restore the transaction volume:

  1. Cancel the copy processing for which the bad sector occurred.

  2. Use swstbackstat (Backup execution status display command), swstsyncstat (Backup synchronous processing progress display command), swstreststat (Restore execution status display command), swsttrkstat (Tracking status display command) and swsthistdisp (History information display command) to check for other errors.

  3. Restoration is performed by overwriting the area containing the bad sector. Select the appropriate method, in accordance with the usage or use status of the transaction volume, from the methods below.

    • Restoration method 1:

      If the area can be reconstructed from high-level software (file system, DBMS, or similar), reconstruct the area.

    • Restoration method 2:

      If the area containing the bad sector is an area that is not being used, such as an unused area or a temporary area, use a system command (for example, the UNIX dd command or the Windows format command) to write to the area.

    • Restoration method 3:

      Use swstrestore (Restore execution command) to restore the transaction volume from a backup volume. (If the backup volume for the copy processing for which the bad sector occurred contains backup history information, restoration is also possible from that backup volume.)

      Note

      The transaction volume cannot be restored by this method, if there is no backup history information.



PreviousNext
Copyright 2012-2013 FUJITSU LIMITED