commvault.com commvault.com
Question

Auxillary copy jobs getting hung with error

  • 14 February 2024
  • 3 replies
  • 72 views
A
Userlevel 1
Badge +7

Hi Team,

While running the scheduled auxillary copy, we are getting the below error and hanging the jobs

please find the below error share any solution for the below issue

“Error code:[13:138]

Description: Error occured while proccessing chunk [2639669] in meida [v_280641] at the time of error in library[disklib01[ and mount path [MA01]\\IP\ITshare\NAS_drive03] for storage policy[storage policy name] copy [tape copy] meid agent [MA02] backup job [312270] unable to setup the copy pipeline”

“Failed to mount media with barcode(RL774L8] side[A_408] into drive [HPE ultrium 8-SCSI_1] in library [HPE MSL 3040] om [MA] while accessing a drive then serial number obtained is different from expected SCSI identifier supplied by the medium changer”

 

after getting this error, everyday we reboot the media agents and commserve then only the backup will normal

current commserve version:11.28.24

3 media agent(physical)

2 commserve server(VMs) 

please share any solution for the above issue

 

3 replies

S
Rank
Userlevel 2
Badge +8

Hi @Adarsh.op ,

There error usually occurs when there has been drive replcament happened in the past.  Can you please confirm if there was any drive replacement ? if yes, then we will have to run exhaustive detection which will pick up the correct serial number of the drive and we can amrk it has drive replacament.

 

Also another way to identify this is by checking the drive serial number on the commcell console and veriify from tape library GUI if the serial number for the drive matches. If it does not then we will have to run exhuastive detection.

 

Steps for exhuastive detection:

 

  1. On the ribbon in the CommCell Console, click the Storage tab, and then click Expert Storage Configuration. 

  2. Under Available MediaAgents, select the MediaAgents that are attached to the library and on which the library needs to be configured and then click Add >>.

    Click OK.

  3. If a library is already configured, this message does not appear. Subsequently, the detected devices are displayed with the detection status detect success in the Expert Storage Configuration dialog box.

  4. On the Expert Storage Configuration dialog box, click the Start menu and choose Detect/Config Devices.

  5. In the Detect Library dialog box, choose the appropriate options:

    • SCSI Devices - If your library is attached to the SCSI or Fibre Channel (FC) Adapter.

    • Detect on Selected MediaAgents in Parallel - If you are performing the detection for multiple MediaAgents.

    • Exhaustive Detection - Only for libraries without Drive IDs support.

    Click OK.

  6. Optionally, from the Processing dialog box you can perform the following operations:

    • Click Abort to stop the exhaustive detection operation and then unmount any mounted media from the drives.

    • Click View Log to display the Log dialog box that reports the status of each task that is performed during the exhaustive detection operation.

  7. When the detection process is completed, the log file is displayed. Click Close to proceed.

  8. A message appears, that asks you to right-click the device for configuration. Click OK. and then pop appears if the drive serial number as changed. Select replacement option, select the drive which was replaced and we are set.

ref: Expert Storage Configuration - Advanced (commvault.com)

 

If you have any confusions, would recomend to create a support incident.

 

Regards,

Suleman 

A
Userlevel 1
Badge +7

Hi@ SMD

Thanks for your valuable reply

we didn’t replace the Drive in this tape library Also the  drive serial number on the commcell console and tape library GUI both Serial number of the drive is same.

recently we upgrade the firmware of tape library only.

please share any other solution for this issue

 

 

S
Rank
Userlevel 2
Badge +8

@Adarsh.op  Thank you for confirming, in that we will have to reboot the library once and then monitor. Issues continue to appear then we would need to analyse logs and understand what is the cause and hence an incident for it.

 

Regards,

Suleman

Reply


Terms & ConditionsCookie settings