Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1421414.1
Update Date:2012-03-11
Keywords:

Solution Type  Technical Instruction Sure

Solution  1421414.1 :   VTL - Tape caching job for fails to run, it cannot find the corresponding physical tape.  


Related Items
  • Sun StorageTek VTL Plus Storage Appliance
  •  
  • Sun StorageTek VTL Storage Appliance
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VTL
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Tape>Tape Virtualization
  •  




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

Have customer try the following:
Check the ACSLS logs and see if it finds any access denied messages. ACSLS could also have volume ownership issues that would prevent the VTL server from accessing it. 

Check the acsss_event.log file for access denied messages.

Check VTL console to see if the Volume is NOT in the vault.

Verify if the Volume is in the same pool on both the ACSLS server and VTL. If the pools are different, put the volumes in the same pool and then do another inventory and see if that fixes the problem.

See if the volume can be mounted/dismounted  from SL8500, VTL, and ACSLS server.

Run audit  on the ACSLS server to check if the volume is there

Run an inventory on the VTL console.

Reset the physical library via the VTL console to see if VTL console shows the physical tape in the physical tape database.

Check if the library is online.
Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback