VTL - Tape caching job for <tape vol#> fails to run, it cannot find the corresponding physical tape. (Doc ID 1421414.1)

Last updated on MARCH 11, 2012

In this Document
  Goal
  Solution


Goal

Getting error in VTL Console GUI and /var/adm/messages file:

Tape caching job for tape <tape volume number>  fails to run because it cannot find the corresponding physical tape.
Example:
IPSTOR||0||W|+|0x00009cb0||Tape caching job, physical tape not available||NW2222||4
TLE_INFO: Tape Caching job, physical tape with barcode NW2222 is not available in physical library vid 4

The above error can come in the following scenarios:

1. The VTL not releasing the disk space of the virtual volume after the backup is complete. The usual process with a VTL is that the virtual volume will be exported to tape and the disk space released based on a policy

2. The physical tapes were not available in the physical library.

3. After the back up, the virtual data still remains at the disk

4. Tape caching stops.

5. Even though there have been no recent changes to the system,
The issue can surface out when  the system is booted and restarted the tape caching, this tape error message can surfaced out after the tape re-inventory during the boot process.


Cause:  Tape caching job for tape <tape volume number>  fails to run because it cannot find the corresponding physical tape.  If the tape is removed from certain pool and then put back physically to a different pool(pool mismatch), this document explains how to troubleshoot that scenario. 

Additional Configuration info: VTL is configured to utilize ACSLS server (with multiple pools) that is connected to SL8500 physical library.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms