Loading...

Expert Storage Configuration - Troubleshooting

Cannot update the drive [ ] information with the replaced drive [ ] because the current drive type [ ] is different from the new drive type [ ]

If you have replaced the drives of IBM ULTRIUM library and performed drive detection from Expert Storage Configuration, then the drive detection process might fail with the following error message.

Cannot update the drive [IBM ULTRIUM-TD4_1(IBM ULTRIUM-TD4, xxx)] information with the replaced drive [Drive (IBM ULTRIUM-TD5, xxx)] because the current drive type [ULTRIUM-V4] is different from the new drive type [ULTRIUM-V5].

Symptom

This error message appears and drive detection process would fail if IBM ULTRIUM library is attached to a MediaAgent running on Windows Server 2003.

Resolution

To resolve this issue:

  1. Deconfigure and delete the drives. See Deconfigure Drives for instructions.
  2. Install the Microsoft Hotfix on both MediaAgent. Refer to Microsoft KB article 9716500.
  3. Perform device detection process. See to Device Detection for instructions.

Unable to Detect Non-IBM Libraries on AIX

Symptom

By default, AIX does not have a driver that attaches to non-IBM libraries. The driver provided by IBM, Atape, attaches only to IBM libraries.

Resolution

  • If you have AIX 6.1 or AIX 7.1, use the following procedure to detect any non-IBM libraries that are not detected.
  • If you have IBM only libraries connected to the MediaAgent, install the IBM Atape driver on this MediaAgent and proceed to step 9.

    Arm-changer will be detected as smcX device (where X=1,2,3...).

  1. Ensure that no jobs are running in the CommCell Console.
  2. Stop the SnapProtect services on this MediaAgent.
  3. Run cfgmgr command to configure devices currently detected by the OS.

    If the adapter ID is known, use the -l option to limit action to adapter.

    cfgmgr -v

  4. Go to <Software_Installation_Path>/Base folder. Run the following command:

    cd <Software_Installation_Path>/Base

  5. Determine device details for currently detected devices. This information will be used to discover the library inquiry string. Run

    ./detectdevices -add tape

    Messages similar to the following will be displayed

    scsi3 rmt0.1 5 0 pthru_adapter tape
    scsi3 gnode0 5 1 pthru_adapter tape
    fscsi0 rmt1.1 131328 0 pthru_adapter tape
    fscsi0 rmt2.1 131584 0 pthru_adapter tape
    fscsi0 smc0 131584 1 pthru_adapter tape
    fscsi0 rmt3.1 131840 0 pthru_adapter tape

    Note down the above device details for drive:

    adapter - fscsi0, device - rmt1.1, target - 131328, Lun - 0

  6. Navigate to <Software_Installation_Path>/MediaAgent folder.
  7. Run test inquiry (testinq) command.
    • To determine the library's inquiry string, you may need to run the testinq command on the next or previous LUN of the drive device found.

      Run this command till the Device Type option in the result displays 8. If the Device Type is displayed as 8 then it confirms that this device is an arm-changer.

    • For example, if the drive above in step 5 was found on adapter fscsi0, target 131328, LUN 0, then the testinq command may be issued on LUN 1.

      When Device Type 8 is discovered, the library's inquiry string is defined by characters 9-24 following the ":". Within this example, inquiry string is "Scalar i500     ".

    • It may be necessary to run the testinq command on both, the next Target and LUN for SAS devices.
    • Note that the inquiry string is case and space sensitive.

    Run

    ./testinq /dev/fscsi0 131328 1
    /dev/fscsi0@131328,1:ADIC    Scalar i500     600G|Serial# ADICA0C0035914_LLB |Device Type 8

  8. Run ./addgnodestring.ksh

    The addgnodestring.ksh script will add the inquiry string to the PdAt database. The script will pad out this string to 16 characters.

    You can run the removegnodestring.ksh to remove one specific inquiry string from the PdAt database.

    Run ./addgnodestring.ksh

    Inquiry String: Scalar i500

    The inquiry string entered was 'Scalar i500'. Is this correct y/n? y

    Inquiry string after padding to 16 characters is: 'Scalar i500     '

  9. Rerun cfgmgr command to check if the library is detected.

    Once cfgmgr has completed, check if the arm changer is detected using:

    lsdev -Cc tape command

    Arm-changers detected for non-IBM libraries are represented by gnode devices in the lsdev -Cc tape output.

    cfgmgr –v

    lsdev -Cc tape

    Messages similar to the following will be displayed

    ----------------------------------------

    Take note of the new gnodeX device listed below.

    gnode0 Available 10-70-00-5,1 Other SCSI Tape Drive

    gnode1 Available 20-58-02 Other FC SCSI Tape Drive

    rmt0 Available 10-70-00-5,0 Other SCSI Tape Drive

    rmt1 Available 20-58-02 LTO Ultrium Tape Drive (FCP)

    rmt2 Available 20-58-02 IBM 3580 Ultrium Tape Drive (FCP)

    rmt3 Available 20-58-02 Other FC SCSI Tape Drive

    smc0 Available 20-58-02 IBM 3576 Library Medium Changer (FCP)

  10. Restart the SnapProtect services on this MediaAgent.

Example

This example illustrates the procedure for the Scalar i500 library (FC adapter)

# snapprotect stop
# cfgmgr -v
# cd <Software Installation Path>/Base
# ./detectdevices -add tape
  fscsi0 rmt1.1 131328 0 pthru_adapter tape
# cd <Software Installation Path>/MediaAgent
# ./testinq /dev/fscsi0 131328 1
  /dev/fscsi0@131328,1:ADIC    Scalar i500     600G|Serial# ADICA0C0035914_LLB |Device Type 8
  * Will need to provide the addgnodestring.ksh script with inquiry "Scalar i500".
# ./addgnodestring.ksh
  Inquiry String: Scalar i500
  The inquiry string entered was 'Scalar i500'. Is this correct y/[n]? y
  Inquiry string after padding to 16 characters i: 'Scalar i500     '
# cfgmgr -v
# lsdev -Cc tape
  gnode1 Available 20-58-02 Other FC SCSI Tape Drive
  rmt1 Available 20-58-02 LTO Ultrium Tape Drive (FCP)
# snapprotect start

INCOMPATIBLE_MEDIUM_INSTALLED

Symptom

When mounting a media for a Backup or Auxiliary Copy operation the following error message appears.

Error Code 62:715 :
INCOMPATIBLE_MEDIUM_INSTALLED. SCSI Error - ASC[0x30], ASCQ[0x00]

The Auxiliary Copy operation fails with one of the following error messages.

Error Code 32:23:
Failed to mount media with barcode [...], side [...], into drive [...], in library [...] on MediaAgent [...].

Error Code 64:232:
Move Media From Slot To Drive

Possible Causes

  1. The media attempting to be loaded into a drive is not a compatible media type for the drive type or it is loaded into the wrong drive type.
  2. If the wrong barcode is being used for the media. The media is rejected because the wrong media type is loaded into a drive.

    For example if an LTO1 tape has a LTO3 barcode, for example L3 extension instead of L1. (Applies to LT0x media)

  3. There may be media in the wrong scratch pool and an attempt was made to load this media into the wrong drive type.

    For example if an LTO3 tape was put into an LTO1 scratch pool to be used by an Ultrium1 Drivepool. (Applies to all LT0x media)

Resolution

  • Verify that the tape drives which are configured are in the appropriate drive pools within Expert Storage Configuration in the Console Console. For more information, see Device Detection.

    Verify if / when the library was detected and configured:

    • If the option to Auto Create DDS Drive Pools was selected and the library has mixed drive types then drives may have been placed into the wrong drive pools.
    • When configuring a library with mixed drive types, all drives must be checked to ensure they are in the appropriate drive pools before completing the configuration of the library.

      See Configuring Libraries with Mixed Drive Types for more information.

  • Verify that the correct barcode is being used for the media.

    Refer to the library manual or contact your hardware vendor to configure the library so that the barcode that is being used is correct for the media type.

The media in the drive already have a valid On Media Label and is not a spare

Symptom

When Mounting Media for backup or Auxiliary copy job, the following error occurs:

Error Code 62:280
Failed to mount media with barcode [...], side [...], into drive [...], in library [...] on host [...]. Reason: The media in the drive already has a valid On Media Label and is not a spare. Advice: Please check to see if the Library configuration is correct.

Cause

This means that the physical barcode and the On Media Label (OML) written to the media does not match. This could happen for one of the following reasons:

  1. Media has been re-labeled with a different barcode and the software reads the old media label on the media from when it had a different physical barcode.
  2. Environment issues occurred which caused the SCSI access path to change to the tape drives so while media was mounted in the drives the SnapProtect software was looking at the wrong media while performing the comparison of the physical barcode and the media label written to the tape.
  3. Slow mapping for the tape library was not accurate at the time the tape was mounted in the drive.
  4. A standalone tape drive is used and the media that is being used already has an On Media Label (OML) and is not a spare.

Resolution

To resolve issue, perform one of the following:

  • If this is a Standalone drive and this error is received then replace the media with a new spare media.
  • If this is a Library then first perform a full scan on the library to make sure that the slot mappings have been updated in the CommVault Software.

    Once the scan is complete, verify the Media Label written to the media matches the physical barcode of the media by performing the steps described in TapeToolGui utility.

    If the Media Label written to the tape matches the barcode

    If the media label written to the tape matched the barcode on the media then the media can be marked appendable again if it was previously marked bad with Media Label errors. To mark a tape appendable:

    1. From the CommCell Browser, select Storage Resources | Libraries | <Library Name> | Media by Location | Media in Library.
    2. Right-click the media, point to Options, and then click choose the Mark Appendable.
    3. A message appears, that asks you to confirm whether you wish to mark the media as appendable. Click Yes.
    4. The media status is changed to Appendable with the reason stating User marked appendable. (Media status can be viewed in the <Media ID> tab of the Media Properties dialog box.)
    5. The media will display a blue and yellow icon.

    If the Media label written to the tape does not match the barcode

    If the Media label written to the tape does not match the barcode on the tape because the media was re-labeled or if the tape has invalid data, use TapeToolGui utility to format the media.

    If the tape has valid data then contact your software provider.

    Misuse of the TapeToolGui utility can result in data loss. We recommend you to contact your software provider to resolve this issue.

Backup Goes to a Pending State with “Encountered an I/O error while performing the operation” Error on a Solaris MediaAgent

Symptom

On a Solaris MediaAgent with attached SAS-2 libraries, the backup job might go into a pending state with the following error:

Error Code: 62:342
Encountered an I/O error while performing the operation

Cause

This problem occurs when the properties of a Solaris MediaAgent with attached SAS-2 libraries are set to use the native device driver for data transfer.

Resolution

  1. From the CommCell Browser, expand Storage Resources | MediaAgents.
  2. Right-click the appropriate MediaAgent, and click Properties.
  3. On the Control tab, clear the Use Native device driver for data transfer for tape media check box, and click OK.